The preview seed holds a wave and a milestone, so the Story pages are seen filled on every preview #8892

The preview seed now writes a wave and a milestone, and /waves and /milestones are in the preview looks, so the Story pages show filled. The type check, the gate and the affected test files pass. I did not run the full suite; the forge runs it on this push.

What changed

• Wave: the seed commits waves/0.1.0.md to the sample repository's default branch. It has three highlights and lists the seeded pull (#3), so /waves shows "0.1.0 · … · The sample says hello · 1 pull".
• Milestone: the first seeded issue ("The home page says hello") now waits for three other issues, two finished "Done work" ones and one open one. /milestones shows it at "2 of 3 done". The seed adds no new issues, so the issue counts stay as they were.
• forge.json: app.looks and app.looksAsOwner both gain /preview-admin/sample/waves and /preview-admin/sample/milestones.
• Tests:

- test/looks-owner.test.ts checks that both pages are in the manifest. - It renders both as the preview admin and finds the wave's version, its headline and "1 pull" on /waves. - It finds the milestone's title and "2 of 3 done" on /milestones.

Why the earlier try (#8884) was red: app.looks was already at its cap of 24 paths, so adding two broke the manifest parse and forge.json no longer loaded. I raised the cap to 26 in src/apps/manifest.ts and updated the two tests that pin it (test/forge-looks.test.ts and test/apps-adversarial.test.ts).

What I chose not to do: I did not drop existing looks to stay under 24. test/forge-looks.test.ts requires every top-level page to be listed, so dropping any would have meant also adding it to that test's list of exemptions.

Try it: open a preview of this pull and look at /preview-admin/sample/waves and /preview-admin/sample/milestones as the owner. Locally, run bun test test/looks-owner.test.ts.

Closes #8868

The preview seed now writes a wave and a milestone, and /waves and /milestones are in the preview looks, so the Story pages show filled. The type check, the gate and the affected test files pass. I did not run the full suite; the forge runs it on this push.

What changed

• Wave: the seed commits waves/0.1.0.md to the sample repository's default branch. It has three highlights and lists the seeded pull (#3), so /waves shows "0.1.0 · … · The sample says hello · 1 pull".
• Milestone: the first seeded issue ("The home page says hello") now waits for three other issues, two finished "Done work" ones and one open one. /milestones shows it at "2 of 3 done". The seed adds no new issues, so the issue counts stay as they were.
• forge.json: app.looks and app.looksAsOwner both gain /preview-admin/sample/waves and /preview-admin/sample/milestones.
• Tests:

- test/looks-owner.test.ts checks that both pages are in the manifest. - It renders both as the preview admin and finds the wave's version, its headline and "1 pull" on /waves. - It finds the milestone's title and "2 of 3 done" on /milestones.

Why the earlier try (#8884) was red: app.looks was already at its cap of 24 paths, so adding two broke the manifest parse and forge.json no longer loaded. I raised the cap to 26 in src/apps/manifest.ts and updated the two tests that pin it (test/forge-looks.test.ts and test/apps-adversarial.test.ts).

What I chose not to do: I did not drop existing looks to stay under 24. test/forge-looks.test.ts requires every top-level page to be listed, so dropping any would have meant also adding it to that test's list of exemptions.

Try it: open a preview of this pull and look at /preview-admin/sample/waves and /preview-admin/sample/milestones as the owner. Locally, run bun test test/looks-owner.test.ts.

The preview seed now holds a wave and a milestone, and the preview looks take /waves and /milestones of the sample repository, as the owner. The type check, the gate and the tests that cover this (looks-owner, forge-looks, apps-adversarial) pass. I did not run the full suite. The check on the new push has not reported yet.

What the failure was: the pull's preview deploy failed with "app.looks may name at most 24 paths". The running forge reads the pull's forge.json with its own parser, so raising the cap inside this pull could never let the preview deploy. I took the cap raise out, and src/apps/manifest.ts is back as on main. I did not see a failing test in the check log.

What changed:

• Seed: src/spawn/preview-seed.ts commits waves/0.1.0.md to the sample repository, with three highlights and the seeded pull #3. It also makes "The home page says hello" a milestone that waits for two finished "Done work" issues and one open issue, so /milestones reads "2 of 3 done".
• forge.json: app.looks and app.looksAsOwner gain the sample's /waves and /milestones. To stay at 24 paths I dropped /forges and /family from app.looks. In test/forge-looks.test.ts they are now in the not-a-page list, each with a reason.
• Tests: test/looks-owner.test.ts checks both pages are in the manifest and render as the preview admin. /waves shows 0.1.0, the headline and "1 pull". /milestones shows the milestone's title and "2 of 3 done".

Not done: /forges and /family are no longer pictured. To restore them, raise LOOKS_MAX in src/apps/manifest.ts (and the two tests that pin it) in a pull of its own that merges first. After that, a second pull can list them again.

To try it: open /preview-admin/sample/waves and /preview-admin/sample/milestones on this pull's preview as the owner. Locally, run bun test test/looks-owner.test.ts.