docs: correct web/README render model, asset pipeline, and structure

[Jose-Gael-Cruz-Lopez]

Closes #50

Summary

Picks up the four items left on #50 after criteria 1 and 2 were met, and adds drift that postdates the issue.

Every claim below was checked against the code, not assumed.

What was wrong

1. It documented a route that was deleted. app/repo-assets/[...path]/route.ts was removed by the #43 fix, but the README described it in three places. Verified gone:

$ ls web/app/repo-assets
ls: web/app/repo-assets: No such file or directory

Replaced with the real pipeline: scripts/copy-repo-assets.mjs → public/repo-assets/ → static serving, run automatically by predev and build.

2. It asserted the opposite of the render model. The README said data is baked in at build time and "changes to those files require a new deploy/build to appear on the site". Every data-backed page has exported revalidate = 3600 since the #47 fix:

$ grep -rn 'export const revalidate' web/app/
web/app/page.tsx:6:export const revalidate = 3600
web/app/globe/page.tsx:6:export const revalidate = 3600
web/app/deck/page.tsx:6:export const revalidate = 3600
web/app/my/page.tsx:6:export const revalidate = 3600
web/app/hackathons/page.tsx:7:export const revalidate = 3600

The route table now matches what next build prints — five ISR routes at 1h, /resources with no revalidation, /auth/[[...auth]] dynamic. The same false rebuild claim appeared again under Production build; fixed there too.

3. /resources was absent entirely. It shipped in #154 and appeared in none of the page list, data-source table, or tree. It is the one page backed by neither loader — its content is constants in lib/resources.ts.

4. The nav notes were a breakpoint behind. #154 moved the inline links from sm to md (adding RESOURCES made the pill wrap between 640–673px), so "inline links at sm and up" and "below 640px" both described the old layout.

5. The scripts table listed four of six. npm test — the 94-test suite CI gates on — was missing, so a contributor reading only this file had no way to run it before pushing.

Verification

• Every file path named in the README resolves on disk (checked programmatically, including the tree entries)
• Route modes taken verbatim from a fresh npm run build
• vitest 94/94 still passes; only web/README.md is touched, so nothing else can regress

Test plan

• Read Render model against next build output — the three route rows should match
• Follow Getting started from a clean clone; the globe and /resources should both come up

🤖 Generated with Claude Code

[Jose-Gael-Cruz-Lopez]

Pushed a correction to my own change on this branch — worth flagging rather than burying.

The original README claimed every data change needs a rebuild. I replaced that with "a data change does not need a rebuild to appear", which is wrong in the opposite direction.

next.config.ts bundles README.md, listings.json and geocodes.json into the deployment via outputFileTracingIncludes, so an ISR revalidation re-reads the deployed copy — not whatever is on main. Editing those files still requires a new build and deploy.

What the hour actually buys is what #47 asked for, and what the page comments say: deadline-derived state — closing-soon flags and day counts, computed from the current date — stays correct between deploys.

The Render model section now splits this explicitly, and the Production build section says to rebuild.