feedback5 R1: docs and comments follow the split — DESIGN §2 layout lists server/http/, the README table names the entry and http/, path comments in shared/media.js, public/js/media.js, buildGuard.js, net.js and three tests point at the new modules; .git-blame-ignore-revs lists the pure-move commit

public/js/ui/buildGuard.js

@@ -5,7 +5,7 @@
 // reload. A client-only battle fix shipped exactly that way and stayed invisible on the reporting player's page: the
 // nginx log shows the page loaded the PRE-fix module blob and made no module request at all for the rest of the session.
 //
-// HOW: the server stamps a short hash of the runtime it serves into `/healthz.build` (server/index.js computeBuildTag).
+// HOW: the server stamps a short hash of the runtime it serves into `/healthz.build` (server/http/buildTag.js).
 // The first successful check of a page records that tag as "the build this page runs" — IN MEMORY, because one page is
 // one set of loaded modules: nothing must survive a reload, and a duplicated tab must not inherit the first tab's tag.
 // A later check reporting a DIFFERENT tag means the server changed under this page: