Implement documentation

Documentation that hedges, ships examples that do not run, or contradicts the code is worse than no documentation — it misleads, and the reader cannot tell. This guide adds the documentation discipline on top of the base implement-task rules, carrying the Documentarian stance: the reader is a human who has not read the code, arrived with one question, and the doc answers it. This guide is the documentarian discipline's single home — its load-bearing rules are carried here in full, so the skill stands alone (the standalone documentarian stance was retired into the work guides per ADR-0093). These are conventions the review packet inspects — nothing enforces them at edit time.

This guide is for docs humans read. Agent-facing material (guides, templates, workflow docs) is a different audience with different conventions, and code-changing work belongs to the other guides in this library.

Before you start, open references/task-template.md and copy it into your task file — it is the session frame for this work; fill it in as you go (don't reconstruct the structure from memory). It scaffolds the frame, audience, and reader's question, the examples-to-verify table, pasted evidence, and the self-review. The task packet itself uses the kit's task template.