/docs reads the forge's documentation on the forge itself: an index and each doc rendered, with no hop to the code host #11081

/docs now renders the forge's documentation on the forge itself instead of redirecting to the code host. tsc --noEmit, scripts/gate.ts, scripts/design-lint.ts and the two test files (test/docs-link.test.ts, test/security-floor-routes.test.ts) passed. I didn't run the full suite, and I didn't check the 20 ms target; server-timing is untested. The security-floor test only requests /docs/:file with a placeholder name, so the floor is directly asserted on /docs/VISION.md alone. I didn't call keep_plan; I had no such tool here.

• GET /docs: a server-rendered index of docs/*.md, with each file's title (its first # line) and a link.
• GET /docs/<NAME>.md: renders the file with renderMarkdown inside the layout. The name must match ^[A-Za-z0-9][A-Za-z0-9._-]{0,80}\.md$ and appear in the folder listing. Anything else, .. and %2e%2e%2f included, is a 404. Request text is only looked up in the listing and never joined into a path.
• Links between docs: OTHER.md and ./OTHER.md (with an optional #anchor) become /docs/OTHER.md.
• Source and cache: files are read from the release checkout, never from FORGE_APP_DATA. The listing and each rendered doc are kept in memory for the life of the process.
• Tests and docs: test/docs-link.test.ts is rewritten for the index, one doc, traversal and a missing name, plus unit checks for title extraction and relinking. docs/features/docs-link.md is rewritten. The code is in src/web/pages/docs_link.ts; src/http/server.ts already routed to it.
• Pre-push hook: it asked for a "Try:" commit line, so there is an empty commit carrying one.

Not done:

• Subfolders (docs/design/, docs/features/) are not served, since a name cannot contain a slash.
• A doc link into a subfolder, such as features/x.md, stays relative and ends in a 404. I did not rewrite those.
• I dropped the old test assertions for the footer and ? sheet "Docs" links. The links still exist in the layout.

To try it, open /docs, then /docs/VISION.md.

Closes #11067

/docs now renders the forge's documentation on the forge itself instead of redirecting to the code host. tsc --noEmit, scripts/gate.ts, scripts/design-lint.ts and the two test files (test/docs-link.test.ts, test/security-floor-routes.test.ts) passed. I didn't run the full suite, and I didn't check the 20 ms target; server-timing is untested. The security-floor test only requests /docs/:file with a placeholder name, so the floor is directly asserted on /docs/VISION.md alone. I didn't call keep_plan; I had no such tool here.

• GET /docs: a server-rendered index of docs/*.md, with each file's title (its first # line) and a link.
• GET /docs/<NAME>.md: renders the file with renderMarkdown inside the layout. The name must match ^[A-Za-z0-9][A-Za-z0-9._-]{0,80}\.md$ and appear in the folder listing. Anything else, .. and %2e%2e%2f included, is a 404. Request text is only looked up in the listing and never joined into a path.
• Links between docs: OTHER.md and ./OTHER.md (with an optional #anchor) become /docs/OTHER.md.
• Source and cache: files are read from the release checkout, never from FORGE_APP_DATA. The listing and each rendered doc are kept in memory for the life of the process.
• Tests and docs: test/docs-link.test.ts is rewritten for the index, one doc, traversal and a missing name, plus unit checks for title extraction and relinking. docs/features/docs-link.md is rewritten. The code is in src/web/pages/docs_link.ts; src/http/server.ts already routed to it.
• Pre-push hook: it asked for a "Try:" commit line, so there is an empty commit carrying one.

Not done:

• Subfolders (docs/design/, docs/features/) are not served, since a name cannot contain a slash.
• A doc link into a subfolder, such as features/x.md, stays relative and ends in a 404. I did not rewrite those.
• I dropped the old test assertions for the footer and ? sheet "Docs" links. The links still exist in the layout.

To try it, open /docs, then /docs/VISION.md.

/docs and /docs/<NAME>.md now render the forge's documentation on the forge itself, with no hop to the code host. The follow-up commit is pushed and fixes the server-timing-sweep failure from the check. I haven't seen the forge's check re-run on it yet.

• /docs: a server-rendered index of docs/*.md, each with its first # line as the title and a link.
• /docs/<NAME>.md: renders the file with renderMarkdown inside the layout. The name must match ^[A-Za-z0-9][A-Za-z0-9._-]{0,80}\.md$ and appear in the folder listing, so .., other extensions and missing names are a 404. Links like OTHER.md and ./OTHER.md#x resolve to /docs/OTHER.md.
• Source and cache: files are read from the release's docs/ folder, never from FORGE_APP_DATA. The listing and each rendered page are kept in memory for the life of the process.
• The server-timing-sweep failure: /docs no longer redirects, so I removed it from the sweep's list of redirecting pages. Both pages now report session and render in Server-Timing.
• The /map budgets failure: I couldn't reproduce it. The budgets test in test/snappy.test.ts passed locally and /map isn't touched here, so I treated it as load on the check machine's shard. That is an assumption.
• Local checks: bun x tsc --noEmit, test/server-timing-sweep.test.ts, test/snappy.test.ts and test/docs-link.test.ts pass. I did not check the 20 ms target.

I did not serve docs/design/ or docs/features/, since a name cannot contain a slash. Doc links into those folders stay relative and end in a 404. I also dropped the old test assertions for the footer and ? sheet "Docs" links; the links themselves are unchanged.

To try it, open /docs, then /docs/VISION.md.

All four review changes are in and pushed. tsc, scripts/gate.ts, scripts/design-lint.ts and the affected tests (docs-link, palette-roster, server-timing-sweep, security-floor-routes) pass; I did not run the full suite.

• Both doors:

- The listing and file reading moved into src/view/docs.ts, which both the page and the terminal read. - A new terminal Docs screen (src/tui/screens/docs.ts, palette command docs) lists the docs and renders one as markdown. - docs/features/docs-link.md says so, and test/palette-roster.test.ts lists the new command.

• Design principles 6 and 7:

- The index is a ul.list of rows with the title as the link. - The file name is gone from each row. - The document is <div class="prose"> with no card.

• Tests:

- The security-floor headers are asserted on /docs, /docs/VISION.md and a 404. - server-timing containing render is asserted on both 200 pages. - The footer and ? sheet Docs-link tests are restored. - A cache test requests the same doc twice and checks the bodies match. - There is also a test that the terminal's list matches the page's.

• Links: relinkDocs now rewrites a name only when it is in the listing; any other link is left as written, so links into docs/design/ and docs/features/ stay as written.

I did not serve the subfolders. The cache test only checks that repeated requests return identical bodies, so it does not prove they come from the map. I did not add a 20 ms timing assertion; the server-timing presence check stands in for it.

The failed check was the "pipeline first" rule, and I added a Direction: commit line to satisfy it. I pushed it as an empty commit (ad632c71a). bun scripts/gate.ts passes locally, and I have not seen the forge's re-run of the check.

I chose the Direction: line over changing the pipeline. This pull adds a terminal Docs screen, which the reviewer asked for, so it has no pipeline change to make. The line gives the reason in the commit's own words: #11067 asks for /docs to be read on the forge itself, and its reviewer asked for the terminal door.

The pull's content is unchanged from the previous push:

• /docs renders an index as rows (title as the link, no file name).
• /docs/NAME.md renders the document as plain prose, with no card.
• Both pages read one listing in src/view/docs.ts, and a terminal Docs screen reads the same one.
• A doc link is rewritten to /docs/NAME.md only when the name is in the listing.
• Tests cover the security-floor headers on both pages and a 404, server-timing on both, the in-memory cache, and the restored footer and ? sheet Docs links.

To try it, open /docs and then /docs/VISION.md on the preview, or run the docs command in the terminal palette.