Waves, first step: a wave is a file in git, and /:owner/:name/waves renders each one as a note #1125

Pillar: P8 Story (umbrella #1081). This replaces #1082, cut to the part one run can finish. The chronicler run and RSS come after.

Intent. The owner can read what landed between two releases as one short note, kept in git, on one page.

Done looks like.

• [ ] waves/<version>.md has one shape: front matter (version, date, headline), then three to five highlights, each with its why, then the full list of merged pulls as links. src/story/wave.ts parses and writes it as plain data, and refuses a malformed file with a plain reason.
• [ ] Cut a wave (Settings, admin only, same-origin POST) writes a draft waves/<next>.md as a pull. Its full list comes from the pulls merged since the last wave, and its headline and highlights are left for a person or the crew to write. No model call.
• [ ] /:owner/:name/waves lists the waves newest first, and /:owner/:name/waves/<version> renders one. Everything is escaped and server-rendered. A private repository's waves follow its visibility.
• [ ] Tests: the parse/write round trip; Cut a wave's list matches the merged pulls; the page renders and escapes; a private repository's page is refused to an outsider.

Left for later (on #1081): a chronicler run that writes the headline and highlights on each tag, milestones moved, RSS, and the home's link.

Files. src/story/wave.ts (new), a Settings action, a page under src/web/pages/, a test.

Risks. None to data. It reads merged pulls and writes through a pull like any change.

Suggested: quill.

Parked by the crew: the check failed ("waves in a forge > a wave that does not parse stops the cut, naming the file") and the decider saw no point in another try (pull #1364 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Parked by the crew: the check failed ("waves in a forge > the waves tool lists and opens waves, and keeps a private app private") and the decider saw no point in another try (pull #1450 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the check failed ("waves in a forge > a wave that does not parse stops the cut, naming the file") and the decider saw no point in another try (pull #1364 closed)
2. the check failed ("waves in a forge > the waves tool lists and opens waves, and keeps a private app private") and the decider saw no point in another try (pull #1450 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Split into #1506 (the wave file format, parsed and written as plain data), #1507 (the waves pages) and #1508 (Cut a wave). Both parked pulls went red on their own new tests while doing all of it at once, and #1450 added an MCP waves tool this issue never asked for. Each piece is now one run with its own tests, and each names its test file in scripts/gate.ts. #1084 now waits on #1508. P8 Story (#1081) waits on all three.