The sidecar copies and the skills pin match v0.42.0. Conventions rule 13 no longer reads a move of the bundle’s base_iri as an edit of every confirmed concept. No plugin change.
The sidecar copies and the skills pin match v0.41.0. The scheduled librarian takes an agent that wants its prompt somewhere other than after -p, named by the repository variable AGENT_PROMPT_FLAG. It writes its patch with the agent’s own file tool, so an agent refused a shell write no longer gives up. Both came with the v0.40.0 copies, which 1.3.16 included without an entry; v0.41.0 changes only ktl-website, which this repository does not use. No plugin change.
The architecture and for-the-curious pages lose their dead sentences. The host-by-host section and the independence paragraph say each fact once, and link what the skills’ pages already record. No plugin change.
The README is a doorway, in the style of Knowledge Trust Ladder’s. It keeps the poem, the opening paragraph and the agents note, and links the quick start, the architecture and the usage pages. What a bundle is, the two vaults, which folder is the bundle, privacy, the development layout and the credits moved to docs/architecture.md; the quick start and the install routes to docs/install.md; the panel, the review card and its five verbs, the commands and the settings to docs/using.md. No plugin change.
The sidecar copies and the skills pin match v0.39.0. The preflight looks for ktl-website among the installed skills. The librarian and release workflows say their variables go under Repository variables, never on an environment, which neither job can read, and the scheduled librarian installs a ktl-librarian whose setup page says the same. No plugin change.
The sidecar’s README links OKF’s specification in its own repository. Google moved the Open Knowledge Format to GoogleCloudPlatform/open-knowledge-format and froze the copy under knowledge-catalog/okf/.
Security
The sidecar copies and the skills pin match v0.38.2. The registrar, librarian and release workflows run the justfile’s lokf-check-refs recipe, and their actions move to newer pinned releases. The docent’s Copilot instructions prefer a retelling for a younger reader, and give the adult concept’s label with it. The pen no longer adds a second “edited since” note to a log line that already has one. The scheduled librarian installs a ktl-librarian that retells a confirmed concept for younger readers when the curation policy declares a band. No plugin change.
The sidecar copies and the skills pin match v0.37.1. The provenance gate reads a verified or generated event that spans lines, or that sits behind a byte order mark or CRLF line endings, so a forged confirmation cannot hide in either. The unattended check follows a renamed concept. The pen refuses a provenance key in any letter case, and keeps a curator’s send-back. The report reads every timestamp and event layout, names a retired concept’s successor, marks a concept a reader disputed, and counts reliance through all thirteen relation fields, as this plugin now does. Conventions rule 14 refuses a commit that records a person’s confirmation and also changes what the concept says. No plugin change.
“N other concepts rely on this” counts a Metric’s measures and a Role’s memberOf and holder, counts each relying concept once, and leaves retired concepts out. The LOKF schema ranges thirteen slots over Concept and the plugin’s list had the first ten. The list now comes from the pinned schema manifest, as the classes do, with the hard-coded list as the fallback, and the smoke test holds both to the manifest. A concept that named one target through two fields counted twice, and a retired concept counted and was counted; ktl-curator’s trust-fields.md says once and neither, and the sidecar’s knowledge-report.sh applies that rule, so the card and the report now agree. scripts/build-vocab.mjs keeps each slot’s range and cardinality in the manifest.
The sidecar copies and the skills pin match v0.34.2. The preflight reads the CI variables by indirect expansion rather than eval, so a scanner that searches for eval finds none, and its output is unchanged. When knowledge-feedback.sh or knowledge-report.sh is missing, it names ktl-curator and an earlier ktl-docent as the skills that need it, since ktl-docent now runs its own copies. The scheduled librarian installs a ktl-librarian that reads LOKF’s schema from a commit rather than a tag (Snyk W012). No plugin change.
A concept whose verified list is empty reads as nobody has checked this yet. The plugin counted any verified key as a check, so verified: [] or a bare verified: showed as checked by automation only in the concept’s label and the health line, and came later in the review queue than an unchecked concept. KTL’s trust-fields.md and its report script count events, not the key, and the plugin now does too. docs/for-the-curious.md states the rule the same way.
