Home's Now line and the account menu's Repositories go where they say #8757

Both fixes are in: the account menu's Repositories now opens a list of repositories, and each word of home's Now line opens the rows it counts. The new test file and the home, studio and hunt tests pass, and gate.ts, tsc and design-lint are clean. I did not run the whole suite, because scripts/fast.ts found the diff too broad to name tests; the forge's check runs it on push.

• Account menu: "Your repositories" (which went to /) is now "Repositories" and goes to /repos. The page lists the repositories you may write, yours and your organizations', newest first, archived ones left out.
• Now line: check, review, land and live link to /now/check, /now/review, /now/land and /now/live, replacing /boards and /releases. Each page shows its count and one row per item, with a link to the pull, run or repo.

- check and review list runs. - land lists open pulls whose latest review is an approval. - live lists production deploys from the last 24 hours. - The rows come from src/flow/now_rows.ts, which uses the same conditions pipeline.ts counts with, and the test checks each list's length against the number on home. - Like the line itself, the pages are for site admins. Everyone else, and agent admins, get a 404.

• Test: test/now-links.test.ts seeds one item per stage and follows each Now link. It checks the page title, that its count matches home's number, and that it lists that many rows. It also walks every account-menu link as an admin, requiring a 200 and, for the five pages whose titles I mapped, a matching title (Repositories, Apps, Explore, Boards, Settings). The other menu links only have to answer 200. I updated test/home-living.test.ts for the live link.

What I left out:

• Checks without a pull: a main-branch check has no pull, so it links to its run.
• Live is not the releases page: it counts deploys in the last 24 hours, so the old /releases link would not have matched the number. /releases is unchanged.
• Row cap: the Now pages have no pagination or row cap.
• Docs: docs/features/now-pages.md is new.

To try it, sign in as a site admin, open home and click each Now word. The account menu's Repositories item is the other check.

🤖 Generated with Claude Code

Closes #8743

Both fixes are in: the account menu's Repositories now opens a list of repositories, and each word of home's Now line opens the rows it counts. The new test file and the home, studio and hunt tests pass, and gate.ts, tsc and design-lint are clean. I did not run the whole suite, because scripts/fast.ts found the diff too broad to name tests; the forge's check runs it on push.

• Account menu: "Your repositories" (which went to /) is now "Repositories" and goes to /repos. The page lists the repositories you may write, yours and your organizations', newest first, archived ones left out.
• Now line: check, review, land and live link to /now/check, /now/review, /now/land and /now/live, replacing /boards and /releases. Each page shows its count and one row per item, with a link to the pull, run or repo.

- check and review list runs. - land lists open pulls whose latest review is an approval. - live lists production deploys from the last 24 hours. - The rows come from src/flow/now_rows.ts, which uses the same conditions pipeline.ts counts with, and the test checks each list's length against the number on home. - Like the line itself, the pages are for site admins. Everyone else, and agent admins, get a 404.

• Test: test/now-links.test.ts seeds one item per stage and follows each Now link. It checks the page title, that its count matches home's number, and that it lists that many rows. It also walks every account-menu link as an admin, requiring a 200 and, for the five pages whose titles I mapped, a matching title (Repositories, Apps, Explore, Boards, Settings). The other menu links only have to answer 200. I updated test/home-living.test.ts for the live link.

What I left out:

• Checks without a pull: a main-branch check has no pull, so it links to its run.
• Live is not the releases page: it counts deploys in the last 24 hours, so the old /releases link would not have matched the number. /releases is unchanged.
• Row cap: the Now pages have no pagination or row cap.
• Docs: docs/features/now-pages.md is new.

To try it, sign in as a site admin, open home and click each Now word. The account menu's Repositories item is the other check.

🤖 Generated with Claude Code

Red since 17:20 and nothing has moved, so here is the failure, Scout: your new top-level /repos route trips "every top-level page has an entry in the audit", "every GET page names session and render in Server-Timing, bar the listed debt", and "reserved names > every top-level page of the forge...". Add /repos to the page audit and the reserved names, and name its session and render phases. 6 tests fail in all: run those test files, then push.

The six failing tests now pass locally, and I've pushed the fix to the same branch. I ran the six failing files plus now-links and home-living; none of the full suite.

The cause was that /repos and /now/:stage were new routes the sweep tests didn't know about. What I changed:

• Audit: added a /repos entry to docs/design/audit.md.
• Reserved names: added now, since /now/... makes it a top-level name. repos was already reserved.
• Server-Timing: /repos and /now/:stage now record a render phase as well as the session phase.
• Looks (test/forge-looks.test.ts): I put /repos in the not-a-page list instead of forge.json's app.looks, because app.looks is already at its 24-path cap. This is a judgement call. Swapping in /repos would mean dropping an existing look.
• Security-floor sweep (test/security-floor-routes.test.ts): one of the six failures was here, not in your list. /now/:stage is now listed as a pattern the seed can't fill, since the stage is one of four fixed words.

I think the 11 failures aren't from this change, so I merged origin/main into the branch and pushed. I haven't confirmed that the forge's check now passes.

• Shared reds: render-image and sentinel-shared-settle pass here, 12 and 9 tests, with no failures. Main has since landed fixes for two of the reds: e00c14a1 for the byte-budget one and e3c4f7f8 for the PNG one.
• Not reproduced: I couldn't find any test containing "a row wears a dot", so I couldn't reproduce that one.
• After the merge: tsc is clean and these pass: now-links, design-audit, reserved-names, server-timing-sweep, forge-looks, security-floor-routes.
• If it's still red: send me the failing log and I'll look at the specific test.

All four points are addressed and pushed. tsc is clean, and now-links (7 tests), the palette-roster, forge-looks, design-audit, reserved-names, server-timing-sweep, security-floor-routes and home-living tests pass. I did not run the full suite.

1. Terminal door:

- src/tui/screens/nowlist.ts is the Now screen. 1–4 switch between check, review, land and live, and Enter opens a row on the web. It reads readNowRows and uses the page's gate, mayReadNow: a site admin who is a person. A non-admin or an agent gets no palette entry, and the screen says "Now is a site admin's." - src/tui/screens/repolist.ts lists listReposWritableTo, and Enter opens a repository the way the dashboard does. - Both are in ENTRIES. I updated the pinned palette roster to match.

1. Test strictness:

- Every account-menu label must map to its page's exact title, and a label with no mapping fails the test. - A new test asserts the four Now links are exactly /now/check, /now/review, /now/land and /now/live, so none can land on boards or releases. - Signed-out /repos must be a 303 to the sign-in page. - The terminal test checks the Now screen shows home's number for a site admin, shows nothing for others, and lists the same repositories as the page.

1. Bounded read:

- readNowRows now returns { total, rows }. It reads at most 200 rows, and total is a separate COUNT, so the list length equals home's number whenever it is under the cap. - The page and the screen both say "Showing the newest 200." when the list is cut. A test queues 205 checks to cover this.

1. Look and design: /repos gets a look in forge.json, and its false not-a-page entry is gone. The cap is 24 (LOOKS_MAX in src/apps/manifest.ts, a platform limit I did not raise), so /migrate gave up its slot. It is now listed as not-a-page, "an import form, nothing to picture until a job runs". /now/* has no look: the looks test only takes static top-level paths. The empty /repos page now shows one New repository button.

If you'd rather keep /migrate's look, one of the other 24 has to go or the platform cap has to be raised.

🤖 Generated with Claude Code

I merged main into the branch, resolved the two conflicts, and pushed. tsc is clean, and the palette-roster, forge-looks, now-links, design-audit and reserved-names tests pass. I did not run the full suite.

• forge.json: I took main's app.looks list, which now has /flow where it had /pipeline, and swapped /migrate for /repos. That keeps the list at 24 entries, and /migrate stays in NOT_A_PAGE with its reason.
• test/palette-roster.test.ts: I kept both new entries, main's "Pinned panels" and my "Now". "Pinned panels" comes first, matching what the palette actually offers.