Skip to content
KTL Curator

Releases

All versionsAll versions forward

Version 0.1.0

Added

  • Initial ktl-curator, a fresh identity forked from KTL Registrar release/0.3.0 (manifest, package, and plugin id all its own): a read-only trust report (health line, ranked “worth ten minutes today” queue, open questions) and a one-concept-at-a-time review session writing Confirm / Send back / I corrected it / Retire / Later into frontmatter and log.md, per the skill’s trust-fields.md / review-session.md. Adds the Create curation policy and Record something missing commands and multi-bundle-root scope (from KTL Registrar’s bundle.ts).
  • npm run smoke-test: runs bundle.ts / trust.ts / edits.ts under plain Node against a fixture bundle covering every trust-label state, including the guardrail that each verb touches only its own keys.

Fixed

Pre-release, from reviewing the first implementation against the plan:

  • Verdicts silently no-op’d for any concept outside the top-queueSize queue (the card looked its record up in the queue, not among all scanned concepts).
  • The Due soon window setting was ignored (30-day window hardcoded); reliance counting ran per-bundle so cross-bundle citations counted for nobody (now one IRI-keyed id map across every bundle); a cached base_iri was never invalidated after a root index.md edit.
  • The day’s **Curation** tally resumed from an earlier day’s line; a https:// source was mangled on resolve (the : read as a line separator); “N more not yet checked” over-counted; body edits used read-then-write instead of atomic vault.process.

Changed

  • Verbs refuse to write to index.md / log.md and say why; “Wrong - I corrected it” asks “the note hasn’t changed - did you mean Confirm?” instead of staying disabled; the review card shows every recorded source, fields/distribution counts for tables, and a collapsible open-questions list; the feedback line reports how many entries wait, or “not reachable from this vault”.