doc-enforce-shapelisted

# Documentation Enforcement — Structural shape Validate the repeated records that a lane owns. Do not force every heading in a file into one shape. Preambles, collection headings, narrative explanations, aliases, source maps, and unrelated tables remain exempt unless another rule governs them. ## Inputs - `purpose`: `review` | `clean` - `diff`: bounded patch - `scope`: `all` | `diff` - `mode`: `interactive` | `auto` | `unleashed` - `files`: canonical lane files selected by `doc-enforce` - `layout`: nested `documentation/lanes/` or flat legacy `documentation/` Review is report-only. Clean may normalize a recognized record only when every load-bearing clause, link, diagram, compatibility fragment, requirement, and source anchor has a destination. ## Output Return findings and any permitted clean actions. Populate: - `Pass 5 — Format-template field presence` - `Pass 6 — Collection rendering consistency` - `Pass 7 — API contract rendering` ## Canonical lane records | Lane | Positively recognized record | Required canonical fields | |---|---|---| | `architecture.md` | H3 component dossier under `Components` or `System Components` | `Responsibility`, `Inputs`, `Outputs`, `Source` | | `api-reference*.md` | Table carrying `Method` and `Path` | `Method`, `Path`, `Auth`, `Implements`; canonical templates also include `Description` | | `configuration.md` | Table carrying `Variable` | `Variable`, `Purpose`, `Default`, `Required`, `Consumed by`, `Implements` | | `configuration.md