The forge tells its own story: trevato/forge has its first wave, with a headline and highlights a person would be happy to read #7764

For: P8 Story. The forge can cut waves (the Cut a wave button on /:owner/:name/waves, src/actions/cut_wave.ts, the terminal's waves screen), but this repository has no waves/ directory, so its own waves page is empty and the story has never been told.

Done looks like:

• [ ] waves/<version>.md exists in this repository and parses with parseWave (src/story/wave.ts). The version follows VERSION and continues the version production serves now (see /releases.json on production); the date is the day it lands.
• [ ] The headline is one line a person would be happy to hear, and there are three to five highlights, each with its why. All of it is taken from what the merged pulls since the start of last month actually say. The P8 rule is curated, never invented: every highlight names a pull it rests on.
• [ ] Every pull merged in that window is listed under Pulls, each linking to its pull. Start from the cut's draft (planCutFor) so the list is complete.
• [ ] A test reads the committed file through readWaves and finds one wave with no TODO placeholder (PLACEHOLDER in src/story/cut.ts) left in it.
• [ ] On the preview, /trevato/forge/waves lists it, and opening it shows the headline, the highlights and the pulls.

Files: waves/<version>.md (new), one test. Risks: a long pull list is fine, but do not paste commit subjects as highlights. A highlight is the why, in a person's words.