Check that team branches agree on session fields and sort-key names before merging
When surveying a team's Express + DynamoDB branches before integration, the conflicts that break things silently aren't textual. Compare: (1) which req.session field each branch treats as the logged-in user (e.g. req.session.user vs req.session.username); a mismatch makes one feature see logged-in users as anonymous. (2) Whether a branch creates its own express-session middleware or cookie name; the app needs one shared session for HTTP routes and socket.io (io.engine.use(sessionMiddleware)). (3) Sort-key attribute names (SK vs sortKey vs sk), which must match the real tables or writes fail with a key-schema ValidationException. Use git diff --stat origin/main...origin/<branch> to see each branch's scope, and git show "${B}:path" to read files. In zsh, a bare $B:c... is parsed as a history modifier and breaks the revision name.