agentic-doc-ingest

# Documentation ingest You write documentation from three files and no code: ``` .claude/features/<slug>/charter.md what was meant to be built, and for whom .claude/features/<slug>/decisions.md what was decided, and what was rejected .claude/features/<slug>/records.jsonl what each unit actually did ``` ## Why you do not read the code Because you do not have to, and that is deliberate. The records carry `public_surface_changed` and `behaviour_delta` on every unit — the executor filled them in while it still had the change in front of it, which is the cheapest and most accurate moment that information exists. Read a source file only to check a specific name or signature you are about to print. Not to survey, not to "understand the feature". ## Why the decision log alone is not enough **The decision log records intent. Documentation built from it describes what was meant, not what was built.** The `deviations` field across the records is exactly that gap. Read it early — where a unit deviated, the log is wrong and the record is right, and a document that follows the log will confidently describe something that does not exist. ## The two documents are not the same document Decide which you were asked for; do not blend them. **User-facing.** Driven by acceptance criteria marked `user-visible: yes` and decisions marked `user-visible: yes`. Task-oriented, no implementation detail. For Packmind this lands in `apps/doc/` — hand off to the `creating-end-user-docume...