validate-repository.sh check 9: the paths sibling repositories link into. LOKF Curator and LOKF Registrar deep-link files here and their link checks follow those URLs for real, so moving one passed every check here and broke their builds; the check now fails instead, and confirms its list is complete when the siblings are cloned alongside.
docs/releasing.md and docs/signing-commits.md carry the release pipeline, the repository settings it depends on, and the signing walkthrough once for all four repositories; every CONTRIBUTING.md links there instead of repeating them. Check 10 holds this repository’s CONTRIBUTING.md to a word budget, and CI fails an action not pinned to a commit.
docs/three-lines.md maps the cast onto the three lines of defence for readers who work under that model, and says what an auditor can check and what the evidence does not show; the README and both plugins link to it.
templates/scripts/knowledge-conventions.sh, and the registrar gate runs it. It checks what lokf validate cannot: one ISO-date log heading per day, quoted timestamps, verified as a list, and open questions in the curator’s shape. knowledge-registrar.yaml runs it on every .lokf/** pull request, and check 11 proves it fails on each broken rule.
Fixed
The librarian now lints the Markdown it writes. Its rule against letting a wrapped punctuation dash start a line was advice only, and a pass tripped MD032 in a host’s lint gate anyway; the audit step now runs the host’s markdownlint config over the bundle, since lokf validate reads a concept body as an opaque string and cannot see this class of fault at all.
One log.md heading per day, the bare date. A suffixed heading such as ## 2026-09-14 (2) is not the ISO-date heading OKF §9 requires, and the curator plugin cannot find the day through it. The librarian and the curator now reuse the day’s heading.
The librarian’s open questions take the curator’s shape, - YYYY-MM-DD, process:lokf-librarian: ..., so the date and actor lead and the first bullet the curator reads is the question.
The docent no longer takes a reader’s identity from git config user.name for a feedback entry - gh api user or nothing, the same rule the curator holds to.
