v3.2.2

v3.2.2 - Release cleanup and bridge integrations

v3.2.2 cleans the public install surface and adds explicit bridge support for OpenClaw and Hermes.

Install note: Do not use GitHub "Download ZIP" as the install package. Use the release asset only.

Added

• --runtime openclaw installs AGENTS.md plus .agents/skills/.
• --runtime hermes installs the generic AGENTS.md bridge without creating an unconfirmed vendor folder.
• Quick-Start and integration docs now list OpenClaw and Hermes directly while Pi remains a manual bridge target.

Changed

• Active version and schema markers are updated to 3.2.2.
• Release artifact commands and validation examples now point to dist/knowledge-v3.2.2.zip.
• Graphiti and Zep are described as not bundled in the free/core install asset.

Removed

• Stale debug/pro export commands and marketing-pack generation from the public release line.
• Source runtime proof folders that are not part of the install asset.

v3.2.1

v3.2.1 - Free Core trust graph hardening

v3.2.1 turns the free Visual Inspector graph into an actionable trust/routing view instead of a sparse wiki-only diagram.

Install note: Do not use GitHub "Download ZIP" as the install package. Use the release asset only.

Added

• free_core_trust_graph output in maps/wiki_graph.json.
• Source-of-truth order nodes: code, tests, evidence, modules, decisions, wiki, sessions, external memory.
• Inferred module/wiki/source-truth edges for fresh installs with no typed wiki links yet.
• Inspector graph metrics, relation legend, lane labels, and diagnostics.
• Focused free-core graph self-test.

Changed

• Version/schema markers now target 3.2.1.
• The Inspector graph section is labelled Free Core Trust Graph.
• Wiki lint ignores non-wiki graph nodes when checking orphan wiki pages.

Fixed

• Fresh free-core graph no longer renders as disconnected dots with zero relations.
• Release packaging excludes both old and current generated QA maintenance records.
• External memory remains visible as advisory-only in the graph and cannot raise trust.

v3.2.0

v3.2.0 - Universal final-report hardening

Packaging maintenance note (2026-06-29): The uploaded install asset was refreshed as a packaging-only cleanup. The tag and source history were not changed. Do not use GitHub "Download ZIP" or autogenerated "Source code" archives as install packages. Use the uploaded GitHub Release asset only.

v3.2.0 lifts the active release line to 3.2.0 and makes post-work reporting consistent across installed agent integrations.

Install note: Do not use GitHub "Download ZIP" as the install package. Use the release asset only.

Added

• A shared final-report contract for installed agents after meaningful work or before handoff.
• A decision record that makes metrics and token-savings reporting part of the expected .knowledge workflow when data exists.
• v3.2.0 knowledge-log and release-note bootstrap records.
• Inspector update UI: automatic release check on local server launch, dry-run plan, report view, and explicit apply gated by --allow-local-actions.
• Updater preflight, migration-default creation, post-upgrade health reporting, and verify coverage for older bootstrap installs.
• Shared memory adapter contract plus explicit Mem0 and Pinecone adapter CLIs that keep external memory advisory-only.

Changed

• Active version and schema markers are updated to 3.2.0.
• Quick-Start.md now requires agents to report doctor status, wiki lint status, suspect or low-confidence areas, repair queue state, routing bundle path, PR summary path, metrics path, and token-savings data when available.
• Installed AGENTS.md, CLAUDE.md, Codex skills, Claude skills, and OpenCode commands now reinforce the same final-report expectations.
• Update checks are enabled for Inspector launch, while update apply remains explicit and telemetry-free.
• Memory provider status now reports adapter commands, offline status behavior, and explicit-live-call boundaries.

Fixed

• Final reports no longer depend on which agent happened to do the work.
• Missing or stale metrics are now called out explicitly instead of being silently omitted from the final response.
• Old installs missing required external_memory defaults no longer become broken after system update; missing defaults are created without overwriting curated knowledge.
• Filesystem permission/report failures are detected before apply so updates stop before partial backup/copy work.
• Graphiti and Zep provider manifests are not included in the free/core release artifact.

v3.1.9 - Install and Git policy hardening

v3.1.9 - Safer install, update, and Git policy

Historical install note: For installation, use the uploaded GitHub Release asset attached to this release. Do not use GitHub "Download ZIP" or autogenerated "Source code" archives as install packages. New installs should prefer the latest release.

v3.1.9 makes .knowledge safer to install, update, package, and commit.

Added

• tools/package-release.js builds the curated install artifact dist/knowledge-v3.1.9.zip with .knowledge/ as the archive root.
• tools/install-check.js validates fresh installs, detects nested .knowledge/.git, identifies accidental source-repo copies, and emits JSON for agents and CI.
• tools/update-system-files.js updates only framework and system files while preserving project-specific knowledge.
• tools/git-policy.js, docs/git-policy.md, and Git policy templates for installed .knowledge/.gitignore and optional .gitattributes.
• tools/self-test-install-policy.js provides reproducible install, update, and Git policy checks.

Changed

• Release packaging now excludes source metadata, runtime state, logs, generated reports, caches, temp files, local archives, and backups.
• Installed .knowledge/.gitignore now comes from templates/git-policy/.knowledge.gitignore, separate from the source repository .gitignore.
• Packaged text files are LF-normalized.
• README and Quick-Start now document fresh install, existing .knowledge update, and migration from non-.knowledge.
• Version and seed schema markers are updated to 3.1.9.

Fixed

• install-check --fix --yes now reports consistent post-fix status and writes pre_fix, fixes_applied, and post_fix.
• Nested .knowledge/.git repair is explicit and backup-based, not a silent deletion.
• Generated and runtime files are ignored by default in installed repositories.

Upgrade

Do not overwrite an existing .knowledge/ folder. Extract the new release artifact to a temporary folder and run:

node .knowledge/tools/update-system-files.js --from <new-knowledge-root> --dry-run

node .knowledge/tools/update-system-files.js --from <new-knowledge-root> --apply --yes

The updater preserves project knowledge and trust state unless the user explicitly chooses a reset.

QA

• JavaScript syntax checks
• JSON parse checks
• Package release build
• Install policy self-test
• Fresh artifact smoke test
• Bad install repair smoke test
• Existing update preservation smoke test
• git add smoke test

Assets

• knowledge-v3.1.9.zip
• knowledge-v3.1.9.zip.sha256

Known Limitations

• update-system-files.js intentionally does not prune deprecated system files automatically. Safe pruning should be done as a separate reviewed cleanup.

v3.1.8 — First public release

.knowledge v3.1.8 — First public release

Historical install note: For installation, use the uploaded GitHub Release asset attached to this release. Do not use GitHub "Download ZIP" or autogenerated "Source code" archives as install packages. New installs should prefer the latest release.

.knowledge is an open local control plane for AI coding agents.

It gives Codex, Claude Code, OpenCode and custom agents one repo-local memory layer: routing bundle, trust and freshness status, repair queue, scoped local search, source-of-truth rules and Visual Inspector.

Highlights

• One first-read routing bundle
• Trust and freshness status
• Repair queue
• Scoped local search
• Source-of-truth rules
• Visual Inspector
• Cookbook flows
• Official templates
• Codex, Claude Code and OpenCode integrations
• Pinecone Local / Cloud bridge, disabled by default
• Optional advisory update checks, disabled by default
• Apache-2.0 core

Install

Download .knowledge.zip, extract it into your repository root, then tell your agent:

Read `.knowledge/Quick-Start.md` and execute it for this repository.

Manual setup:

node .knowledge/tools/install-agent-integrations.js
node .knowledge/tools/flow.js import
node .knowledge/tools/flow.js release --no-color

After setup, the first operational file an agent reads is:

.knowledge/maintenance/routing_bundle.json

Quick metrics

In a synthetic SaaS-shape fixture:

• 14 orientation files → 1 routing bundle
• ~22% less first-orientation context
• Doctor: healthy 90–93 depending on scenario

These numbers are order-of-magnitude estimates from one local estimator, not tokenizer-verified production benchmarks. Tiny repositories may show overhead because the routing bundle has fixed structure cost.

Update checks

Update checks are disabled by default.

.knowledge does not run a background updater, does not send telemetry and does not apply updates automatically.

Manual check:

node .knowledge/tools/check-updates.js

Optional weekly advisory checks:

node .knowledge/tools/check-updates.js --enable --interval=7d

Notes

• External memory is a bridge, not source of truth.
• Current source code and tests always beat summaries.
• The bundled Visual Inspector is local, static and free.
• Pro2Pilot Inspector will be the future interactive/team layer.