context-v Docs Carry the Kit's Metadata Template
Every LFM context-v doc already had the kit's baseline fields. Ten listed their AI tooling as a bare string; now it's a list.
context-v Docs Carry the Kit’s Metadata Template
Why Care?
The context-vigilance kit names a small set of frontmatter fields every doc
should carry: a title, its creation and modification dates, a stable
site_uuid and citation hex_code, and its human authors. Phase 2 of the
tree-wide retrofit fills those from facts (git history, the doc’s own H1,
minted IDs) and brings existing values up to the standard spelling.
LFM’s docs were already in good shape. All fifteen carried every baseline field, so nothing was added. The one change is shape, not content.
What’s New?
augmented_withis a list everywhere. Ten docs named their AI tooling as a bare string (augmented_with: "Claude Code on Opus 5"). Each is now a one-item YAML list with the same string, matchingauthorsand the changelog convention. Anything that reads the field as a list, including this repo’s splash, now gets one without coercion.
Under the Hood
- Every edit was made by hand, one doc at a time. No script touched any frontmatter, and no date, version, status, or body line changed.
- One doc,
Maintain-Conditional-Components-on-Render.md, still carries the legacydate:key. It was left alone: the splash readsdate:, and the doc already has adate_authored_initial_draftwith the same value. Workspace-vs-JSR-for-LFM-Consumers.mdkeepssemantic_version:, which is a permanent alias ofat_semantic_version.