captures: regen scribe --help captures after the WRITING-006 help rewrite #14
Loading…
Reference in a new issue
No description provided.
Delete branch "help-writing-006"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closing item of the docs program (armada issue #19): the scribe CLI help text was rewritten per canon WRITING-006 (help states what/how/when — no history, no provenance); this re-walks the scribe captures from the rebuilt 0.4.7 binary so the manual's command reference carries the new text. Surface unchanged — 14 capture files, text-only.
ditc and dito captures stay pinned (ditc@2.4.4, dito@4.1.12-rc.1): the shipping binaries moved past the committed surfaces and a re-walk adds uncovered groups (ditc session/mcp, dito state) and drops a covered one (ditc skills) — check-coverage fails both directions until the content waves for those surfaces land. Recorded in the commit message.
Gates: build-docs.py OK (coverage OK, link-check OK), check-prose clean (ditc/dito/scribe), check-lockstep --synthesize 0 fail ×3, check-coverage OK.
0658b16273tod0603fc4b0