Every preview of the forge shows the seeded pull page, repository head, home with pins and /flow, looked at as the owner #8875

Every preview of the forge now takes owner looks of the seeded repository's home (/preview-admin/sample) and its seeded pull (/preview-admin/sample/pulls/3). /, /flow and /talk are still listed in forge.json's app.looks and app.looksAsOwner.

• Pull number: the seed opens two issues before the pull, so the pull is #3. src/spawn/preview-seed.ts exports this as PREVIEW_PULL, and the seed fails if the pull gets any other number, so the look can't silently land on a 404.
• Blank looks fail the check: a new block in test/looks-owner.test.ts boots the seed and loads each owner-look page as the preview admin (via the parent's signed identity). It looks for:

- pins on /: the slot on home, then "Pinned panels" with "Runs by kind" in the /live/home/panels fragment that fills it after the first paint; - a pipe on /flow; - the h1.repo-title naming sample on the repository home; - the primary Ship button inside #decide on the pull page.

It also checks that forge.json lists all four pages in both fields.

• Look cap raised (src/apps/manifest.ts), worth a look: app.looks was already at its cap of 24, the forge's own top-level pages. LOOKS_MAX is now 26, room for exactly these two, so the next page added is still a deliberate choice. docs/APPS.md and the cap tests in test/apps-adversarial.test.ts now say 26; the tests were not wrong, the cap moved.
• test/forge-looks.test.ts: it still holds the top-level looks to exactly the router's top-level pages. Any deeper look must now be a preview-seed path that is also in looksAsOwner; its own run has no seed, so it doesn't load those pages itself.
• Docs: docs/design/areas/pull.md and docs/design/areas/repo-head.md each say, under their opening line, that every forge pull's preview carries desk and phone owner looks of that page.

Not done:

• Looks on this pull: the forge takes them once this pull's preview is up; the builder doesn't take or attach looks, so they'll show under Looks on this pull.
• The plan on #8865: the issue asked for a keep_plan tool, but this run had no such tool, so no plan was kept there.

Checks:

• bun scripts/gate.ts and bun x tsc --noEmit pass.
• scripts/fast.ts said the diff was too broad (exit 2), so I ran these by hand: test/looks-owner.test.ts, forge-looks, apps-adversarial, looks, refresh-meta, pull-looks, fuzz-parsers and preview-spec. All pass except three tests in test/looks.test.ts that drive a real /usr/bin/chromium. They fail the same way without this change, because the sandbox can't run Chromium; the forge's check runs them.

To try it: bun test test/looks-owner.test.ts. Once the preview is up, its Looks should show desk and phone pictures of /, /flow, /preview-admin/sample and /preview-admin/sample/pulls/3, taken as the owner.

🤖 Generated with Claude Code

Closes #8865

Every preview of the forge now takes owner looks of the seeded repository's home (/preview-admin/sample) and its seeded pull (/preview-admin/sample/pulls/3). /, /flow and /talk are still listed in forge.json's app.looks and app.looksAsOwner.

• Pull number: the seed opens two issues before the pull, so the pull is #3. src/spawn/preview-seed.ts exports this as PREVIEW_PULL, and the seed fails if the pull gets any other number, so the look can't silently land on a 404.
• Blank looks fail the check: a new block in test/looks-owner.test.ts boots the seed and loads each owner-look page as the preview admin (via the parent's signed identity). It looks for:

- pins on /: the slot on home, then "Pinned panels" with "Runs by kind" in the /live/home/panels fragment that fills it after the first paint; - a pipe on /flow; - the h1.repo-title naming sample on the repository home; - the primary Ship button inside #decide on the pull page.

It also checks that forge.json lists all four pages in both fields.

• Look cap raised (src/apps/manifest.ts), worth a look: app.looks was already at its cap of 24, the forge's own top-level pages. LOOKS_MAX is now 26, room for exactly these two, so the next page added is still a deliberate choice. docs/APPS.md and the cap tests in test/apps-adversarial.test.ts now say 26; the tests were not wrong, the cap moved.
• test/forge-looks.test.ts: it still holds the top-level looks to exactly the router's top-level pages. Any deeper look must now be a preview-seed path that is also in looksAsOwner; its own run has no seed, so it doesn't load those pages itself.
• Docs: docs/design/areas/pull.md and docs/design/areas/repo-head.md each say, under their opening line, that every forge pull's preview carries desk and phone owner looks of that page.

Not done:

• Looks on this pull: the forge takes them once this pull's preview is up; the builder doesn't take or attach looks, so they'll show under Looks on this pull.
• The plan on #8865: the issue asked for a keep_plan tool, but this run had no such tool, so no plan was kept there.

Checks:

• bun scripts/gate.ts and bun x tsc --noEmit pass.
• scripts/fast.ts said the diff was too broad (exit 2), so I ran these by hand: test/looks-owner.test.ts, forge-looks, apps-adversarial, looks, refresh-meta, pull-looks, fuzz-parsers and preview-spec. All pass except three tests in test/looks.test.ts that drive a real /usr/bin/chromium. They fail the same way without this change, because the sandbox can't run Chromium; the forge's check runs them.

To try it: bun test test/looks-owner.test.ts. Once the preview is up, its Looks should show desk and phone pictures of /, /flow, /preview-admin/sample and /preview-admin/sample/pulls/3, taken as the owner.

🤖 Generated with Claude Code

Previews of the forge now take two more pictures as the owner, using the preview seed: the seeded repository at /preview-admin/sample and its pull at /preview-admin/sample/pulls/3. Both are listed in app.looks and app.looksAsOwner in forge.json. The seed refuses a pull of any number other than 3. test/looks-owner.test.ts boots the seed and renders each owner look as the preview admin, checking the pins on home, a pipe on /flow, the repository head's title and the Ship decision.

The first push failed at deploy, not in the tests: "forge.json: app.looks may name at most 24 paths". The forge that deploys a preview checks forge.json with main's limit, so raising LOOKS_MAX to 26 on this branch could never get a preview up. The limit stays at 24. Instead, /boards and /changelog give up their pictures; /board and /releases are still pictured. Both move to NOT_A_PAGE in test/forge-looks.test.ts with that reason, and test/boards-page.test.ts and test/changelog.test.ts still cover them. That test's limit check went back from 26 to 24, and it now also requires any deeper look to be one of the seed's owner looks.

Gate, tsc --noEmit, and test/forge-looks.test.ts, test/looks-owner.test.ts and test/apps-adversarial.test.ts (76 tests) pass locally.

To try it: open the preview's pictures for this pull and find the owner looks of /preview-admin/sample and /preview-admin/sample/pulls/3.

🤖 Generated with Claude Code

Left #8865 open: 1 unticked item remain (The builder's pull lists, from its own preview's Looks, the desk and phone looks of these four pages.).