v0.10.0

Codex and Claude Code now start vault activation on the first substantive request in a
vault-linked directory and keep it for the session. Existing installations receive the new skills
through release maintenance, but must re-run
setup
to add the UserPromptSubmit hook and the new routing text. Codex then asks the user to trust the
new hooks on its first interactive start.

Added

• Deliver an applicability notice through runtime hooks: after the routing text at SessionStart,
  and alone on every UserPromptSubmit. It names the vault, its root, and the selection source, and
  asks for the use-knowledge-vault skill call when a substantive request arrives before vault
  activation. See ADR 0001.
• Add the UserPromptSubmit hook to Codex and Claude Code in setup preview and apply. Setup rewrites
  an existing managed instruction block in place and preserves the surrounding text.

Changed

• Run the maintenance route on every vault access, but reread the contract and instruction roots
  only when it reports vault status integrated or release status updated. The routing text and
  the protocol now agree.
• Lead the use-knowledge-vault description with an imperative trigger for substantive work in a
  vault-linked directory, and name the skill call as the start of vault activation.

Safety and compatibility

• The notice is stateless and computed only from the event's cwd, the registry, and the selected
  contract, with no network call, vault access, or note read. With no applicable vault or any
  resolution error, it adds nothing and never blocks a prompt.
• The applicability probe remains authoritative for vault selection; a registry change takes effect
  at the next prompt. Runtimes without hooks keep the instruction-file route.
• Preserve contract schema version 1, existing CLI commands, and read-only resolver and audit
  behavior.

v0.9.0

Knowledge Loom now provides a shared maintenance entry point for stable skill releases and vault
freshness in Codex and Claude Code. Existing installations need a one-time
setup and ownership migration; publishing this release alone does
not activate maintenance in existing sessions.

Added

• Check published stable skill releases on use, with a shared seven-day interval, explicit version
  pins, atomic bundle replacement, and recovery that preserves a usable installation.
• Check authorized vault remotes on access at a shared 24-hour interval. Safely fast-forward clean
  checkouts and report observed, integrated, deferred, and unavailable states separately.
• Preserve local reads, edits, and commits during remote failures. Retain pending synchronization
  and use bounded evidence-based reconciliation after rejected pushes, even inside the daily cache.
• Add previewable, idempotent Codex and Claude Code setup with shared skills, explicit duplicate
  ownership migration, external access routing, and startup context without maintenance networking.
• Run maintenance before Claude native reads within the applicable vault. Native Skill invocation
  checks releases; explicit routing retains vault selection and publication.

Safety and compatibility

• Preserve unfinished edits, live writers, existing configuration, and installation backups.
  Maintenance contention does not block otherwise authorized local reads.
• Assess verified integrity advisories before affected vault mutations; keep installed versions
  separate from instructions already loaded in a session.
• Preserve contract schema version 1 and read-only resolver/audit behavior. Inbound synchronization
  requires explicit contract configuration; provider-specific backup adapters remain external.
• Keep arbitrary shell reads and opt-out tools outside automatic interception. Hosted standalone
  invocation, independent Codex startup-hook acceptance, hot reload, and hosted semantic
  reconciliation remain unverified; see the runtime verification record.
• Report missing Git in the runtime tool PATH as a dependency error, rather than a vault-lock conflict.

v0.8.0

init-knowledge-vault can now turn existing authorized work into a populated vault without first
asking the user to define a topic, source list, taxonomy, or evaluation questions.

Added

• Added zero-input source-assisted bootstrap through active and recent source views already
  available to the agent.
• Added source-linked Project and workstream notes, relevant People, Decisions, reusable Reference
  knowledge, INDEX.md, and a current-focus view. Categories without sourced content are omitted.
• Added one preview for the contract, source boundaries, planned notes, focus, registration,
  project association, privacy, lifecycle, and known gaps.
• Added behavior coverage for setup with multiple unrelated registered vaults and no project
  association.

Safety and compatibility

• Distinguished source authority from tool reachability and retained source references, capture
  times, and explicit coverage gaps.
• Stopped before creating an empty placeholder vault when no useful authorized source is available.
• Preserved contract schema version 1, existing CLI commands, explicit contract-only initialization,
  conservative adoption, registration, and project association.

v0.7.1

Linked Git worktrees now reuse the vault association registered for their main checkout.

Fixed

• Added a git rev-parse --git-common-dir fallback when no project association matches the
  current worktree path directly.
• Preserved direct worktree associations as the higher-priority match.
• Added a regression test through the public probe command with a real linked worktree.

Compatibility

• Preserved registry schema version 1 and all existing project associations.
• Required no registry migration or per-worktree entries for temporary checkouts.

v0.7.0

Durable vault notes and navigation pointers now have an agent-readable writing gate with optional
support for Matt Pocock's unmodified writing-for-agents skill.

Added

• Added protocol-owned checks for one source of truth, co-located rationale and provenance, stable
  terminology, conditional navigation pointers, lifecycle state, and duplicate pruning.
• Added optional writing-for-agents invocation after write authorization when Distill will create
  or restructure an agent-consumed note or navigation pointer.
• Added a self-contained built-in authoring fallback when the companion skill is unavailable.
• Added hermetic Codex and Claude behavior coverage for companion availability, retrieval-only
  work, and authority boundaries.

Compatibility and safety

• Kept writing-for-agents optional rather than making it an installation prerequisite.
• Kept authority, evidence, privacy, subject isolation, validation, Git, sync, backup, and lifecycle
  behavior under the Knowledge Vault Protocol.
• Preserved contract schema version 1 and all existing installation routes.

Maintenance

• Added agent-neutral contributor guidance for issue tracking, triage labels, and domain docs.
• Updated GitHub Actions to actions/setup-node@v7.

v0.6.0

All handwritten contributor code now uses strict TypeScript while every installation route
continues to ship one self-contained JavaScript runner.

Changed

• Migrated deterministic parsing, resolution, initialization, audit, content-check, and CLI source
  modules to strict TypeScript.
• Migrated build, installation, release, validation, behavior-evaluation, and test code to strict
  TypeScript.
• Added explicit internal types for contracts, registries, findings, vaults, CLI options, and
  content-check results while keeping YAML and JSON inputs runtime-validated from unknown.
• Added all handwritten code to the standard TypeScript validation path on Node.js 20, 22, and 24.

Compatibility

• Preserved the protocol, contract schema, CLI commands, output, exit statuses, and Node.js 20+
  requirement.
• Kept installed skills independent of TypeScript, tsx, node_modules, and repository checkouts
  by generating the same self-contained .mjs distribution boundary.

v0.5.0

Applicable vaults now participate automatically in substantive project work and preserve durable
knowledge without requiring users to know a skill name.

Added

• Added a successful no-op probe command so agents can test vault applicability before asking the
  user to choose one.
• Added route-first retrieval for current attention, governance, lifecycle, and protected-data
  evidence before general relevance ranking.
• Added automatic use guidance for Codex and Claude integrations, including post-task durable
  capture and current-focus maintenance.

Changed

• Defaulted newly initialized and conservatively adopted vaults to
  proactive-durable-capture writes and maintain-after-material-change current-state upkeep.
• Kept explicit-only available as an explicit contract override; existing vault contracts retain
  their declared policies.

Safety

• Projects without an ancestor vault contract or registered project association remain a silent
  no-op instead of triggering vault selection.
• Automatic use still honors deterministic vault and subject selection, privacy boundaries,
  preview requirements, lifecycle actions, and backup declarations.

v0.4.0

One audit can now enforce both portable vault structure and local content rules.

Added

• Added optional content_checks.adapter declarations to vault contracts and trusted executable
  mappings to the local user registry.
• Merged declared checker results into the existing knowledge-loom audit report with observable
  adapter source, validation date, file path, and line information.
• Documented one checker result interface for vault-specific rules without adding a second audit or
  validation command.

Safety

• Kept executable commands and private paths outside vault contracts and reusable skill packages.
• Started checkers directly without a shell and bounded their runtime and output.
• Failed closed when a checker is missing, invalid, timed out, inconsistent, or requested by an
  invalid contract.
• Kept compatibility requirements in skill bodies so every package uses portable skill
  frontmatter.

v0.3.0

Projects can now select their registered vault automatically.

Added

• Added preview-first associate CLI support for binding a canonical project directory to a
  registered vault ID.
• Added deterministic project-aware resolution: explicit selectors still win, a vault's own
  nearest contract stays authoritative, and the nearest nested project association wins before the
  single-vault fallback.
• Added direct invocation examples for standalone and plugin installs in Codex and Claude Code.

Safety

• Kept project associations in the local user registry instead of modifying project repositories.
• Invalid or conflicting associations fail closed and do not expand a vault's declared authority.

v0.2.0

The deterministic tooling now runs on JavaScript instead of Python.

Changed

• Replaced the source package, CLI, builders, installer, tests, and CI with Node.js modules.
• Bundled the YAML parser into each skill's single knowledge-loom.mjs runner, so installed skills
  do not run npm install, depend on a repository checkout, or fetch code on first use.
• Declared the Node.js 20+ runtime requirement in every command-capable skill while keeping the
  instruction-only Claude Desktop ZIP free of executable runtime requirements.

Compatibility

• Preserved the init, audit, resolve, and register CLI commands, contract schema, exit
  statuses, safety boundaries, and agent-neutral installation routes.