c142 · Documents and the summary of work: the plan, as built (2026-11-12)

From the prompt. Built the same turn on c133 as the first example. Every cycle gets the Documents part; the summary of work appears only where a story has one.

Documents, one link

• The tab: /cycles/<project>/<id>/docs on every cycle (app/pages/cycles/[project]/[id]/docs.vue). CyclesViewTabs now reads Story · Record · Documents. A cycle with no story gets Record · Documents, where it had no tabs before.
• The list: app/components/cycles/Documents.vue. Every top-level .md in the cycle directory, labelled by its first heading with the cycle's own prefix dropped, in four groups. Start here: initial prompt, kick-off prompt, plan, shape, pickup note, story, which keep fixed names. Then Documents, Reviews (review in the name), and Threads (*-prompt / *-plan pairs). Last come the pages the captures came from, one line per path with a count of captured states. The link opens the first state, without demo=1.
• The data: documents (file + title) added to /api/cycles/<p>/<id> beside threads and otherDocs, which the Record tab still uses.
• On the story: a Documents section under In short (#documents), the same list without file names, linking to the tab.
• Links stay extension-less, so the deploy crawler prerenders each document (CLAUDE.md, c130).

The summary of work

• The shape: WorkItem { problem, resolution, tried?, href? } and an optional work on the story module (app/data/cycle-stories-mock.ts). Each line is a micro-problem and how it was resolved, in a few words. What didn't hold on the way goes under it as "Tried:". The resolution links to where to see it.
• On the story: "Summary of work" (#work), right under In short and above Documents and At a glance. Two columns with an arrow on wide screens, one column on a phone.
• c133's twelve lines, written from its record and voice-checked (zero violations).

Open

1. Rolling the summary of work out to other cycles: by hand per story, or drafted from Key Changes and reviewed like c124's survey drafts.
2. Whether "Tried" also takes the attempts that were only considered (for example, scenes as asset files, which authoring.md weighs and rejects). For now it holds only attempts that were built.
3. Sub-directories of a cycle (c125/mcp-guide-u4/, c140/specs/) aren't listed yet.
4. Whether the Record tab's Artifacts section should now just link to Documents.