The pinned toolkit is lokf 0.8.0, and a malformed by, sources[].author, http_method or email is now an error, as lokf validate rejects each. stale_after accepts a datetime as well as a bare date, and the missing recommended fields setting no longer lists http_method.
npm run build-vocab reads the schema from the sidecar’s pinned toolkit, not a sibling ../lokf checkout; LOKF_SCHEMA still overrides it.
The settings merge rule moved into the pure vocab.ts (mergeSavedSettings, with vocabFromManifest for the malformed-manifest fallbacks), so the smoke test covers what sat untested in main.ts. No behaviour change.
The smoke test asserts more and characterises less. The two golden fixtures pin their warning counts, so a rule that starts or stops firing fails the build, and a drift guard catches a settings control naming a setting that does not exist.
The Known LOKF types setting is documented as the extension point for a bundle validated against a domain schema (lokf validate --schema <file>): list that schema’s classes there, since the plugin cannot read a schema outside the vault. Settings tab, README and docs/for-the-curious.md; no behaviour change.
README rewritten around how to use the plugin, as an extension of the lokf-agent-skills: the two-vault story, a four-step Quick start, Using it, the command table, Which folder is the bundle, Install and Settings. Shared material - the role table, the library metaphor, the trust ladder - now lives in the skills’ README and is linked once; no plugin change.
This repository’s own sidecar repaired by ktl-sidecar: the knowledge_bundle doorway link is now committed at the root, .lokf/justfile regains the template’s lokf-check-refs recipe, and markdownlint and lychee skip the link’s duplicate path. No plugin change.
CONTRIBUTING.md is a checklist again, with the release pipeline and the signing guide documented once in the skills repository’s docs/ and linked from here. npm run check runs build, lint and smoke test together, the settings-tab and createEl lint rules are errors rather than warnings, and CI fails an action not pinned to a commit; no plugin change.
The README says which line of defence this plugin’s work is, and points readers who work under that model at the skills’ page on the rest; no plugin change.
The registrar gate checks what lokf validate cannot: .lokf/scripts/knowledge-conventions.sh from the sidecar templates (one ISO-date log heading per day, quoted timestamps, verified as a list, open questions in the curator’s shape) and the justfile’s lokf-check-refs, on every .lokf/** pull request; no plugin change.
SECURITY.md is a policy, not a threat model: a surface table that links to the skills repository’s docs/threat-model.md instead of restating it, held to a word budget by npm run check. It now lists the plugin’s write paths as the README’s Privacy section does, where it had named only the header command; no plugin change.
