knodin 0.7.5 → 0.7.6

package/docs/RELEASE-0.3-EVIDENCE.md

@@ -1,73 +0,0 @@
-# Reckon Graph 0.3 evidence ledger
-
-This ledger freezes the field and competitor evidence used to define the 0.3
-release. Historical observations are not rewritten as current measurements.
-
-## Minions field observation
-
-The prior 0.1.22 field run recorded:
-
-- 3,006 source files;
-- 2,949 indexed files and 157 health findings before repair;
-- 3,006 indexed files after repair;
-- current HEAD `cbf058aa...`;
-- recorded indexed HEAD `4d45fe02...`;
-- a 16-commit distance while 0.2.0 status incorrectly reported healthy;
-- 195 repair operations, including reconciliation of stale/orphaned state and
-  regeneration of 1,874 symbol embeddings.
-
-The workload fast-forwarded main across 15 merged commits and removed 16 linked
-worktrees. The checked-in lifecycle regression recreates those lifecycle
-shapes, including additions, edits, renames, deletions, policy transitions,
-overlapping hook workers, immediate queries, and cleanup.
-
-The Minions checkout is a read-only field fixture for this release. Its current
-HEAD on 2026-07-30 was `44c91f6d013fd8d6f4e106d063a87eab94b19866`;
-the historical SHAs above belong to the original observation, not that later
-checkout state. Existing modified and untracked Minions files were left intact.
-
-## Token Optimizer observation
-
-The complete 102.8-second demo artifact has SHA-256
-`a8085ec26d56ab220f3b31578f818a911caf277e604ed9f8d46c0d9f31fbb60d`.
-It demonstrates seven named surfaces: file outline, symbol extraction, symbol
-find, batch outline, project overview, output compression, and command running.
-It describes Python AST parsing and heuristic/regular-expression coverage for
-other languages.
-
-At release time, no authorized immutable source commit, packaged executable,
-README, version, or raw measurement data was available, so the original
-observation was `demo-only`. A post-release source audit now pins the authorized
-GHES implementation at
-`a2b9cef5efdfcf0393e9e7a5ded229ffd9f613d7`. It verifies the source inventory
-and selected implementation observations, including a behavioral compression
-budget probe. Equivalent end-to-end measurements remain incomplete, and the
-displayed savings remain hypotheses: the demo showed two calls, used a bytes/4
-token estimate, and showed inconsistent 83% and 93% targeted-lookup figures.
-
-The reproducible comparison contract is
-[`../benchmarks/evaluations/token-optimizer-20260730/comparison-manifest.json`](../benchmarks/evaluations/token-optimizer-20260730/comparison-manifest.json).
-The immutable source result is
-[`../benchmarks/evaluations/token-optimizer-20260730/raw-source-audit-20260730.json`](../benchmarks/evaluations/token-optimizer-20260730/raw-source-audit-20260730.json).
-Missing behavioral measurements are `null`, never zero.
-
-The later C56 replay now executes all seven pinned workflows with shared
-fixtures, real-token counts, 20 warm samples, five cold-process samples, and
-explicit correctness oracles. Both products pass the five structural oracles.
-The result is intentionally `complete-with-gaps`: Token Optimizer is smaller
-and faster on all five small-fixture structural calls, Reckon has no output
-compressor yet, and command execution remains containment-gated. See
-[`../benchmarks/evaluations/token-optimizer-20260730/summary.md`](../benchmarks/evaluations/token-optimizer-20260730/summary.md).
-
-## Implemented and deferred
-
-Reckon now provides parser-grounded bounded file and batch outlines, compact
-source-only extraction, deterministic project overview, natural-prompt routing,
-real-token local telemetry, and a static local report through the existing
-single `reckon` gateway.
-
-`reckon run` is not shipped. A no-shell launcher alone could not prove portable
-hard memory limits and process-tree termination across POSIX and Windows. The
-full gate and adversarial fixtures remain documented in
-[`COMMAND-OUTPUT-COMPRESSION.md`](COMMAND-OUTPUT-COMPRESSION.md). This is a
-security decision, not a claim that the competitor implementation is unsafe.

package/docs/SCIP-IMPORT.md

@@ -1,57 +0,0 @@
-# Optional SCIP import
-
-knodin can add compiler-produced SCIP facts to its local graph without running a
-language server. The tier is deliberately opt-in:
-
-```sh
-knodin index --scip path/to/index.scip
-```
-
-The input must be a regular file inside the repository. knodin never discovers,
-downloads, or produces a SCIP index, and a normal `knodin init` or `knodin
-index` does not import one. Repositories without the flag keep the existing
-native and LSIF behavior byte-for-byte at the command boundary.
-
-## Evidence and conflicts
-
-Imported definitions use stable repository/file/range identities, `SCIP_*`
-kinds, a summary containing the original SCIP symbol and `scip` provenance,
-`scip_reference`, `scip_relationship_reference`, `scip_implementation`,
-`scip_type_definition`, or `scip_definition` reference kinds, and `scip_import`
-file edges. Native and LSIF facts are not deleted or overwritten. If two tiers
-define the same name, normal ambiguity-safe resolution returns all candidates
-and requires a file, kind, or identity selector. A stale SCIP input is refused
-rather than replacing fresher source-derived evidence.
-
-Every successful index result includes the producer name/version and represented
-languages from the SCIP file plus the exact limits used. Defaults are 64 MiB,
-10,000 documents, 250,000 decoded facts, and 30 seconds. Inputs that are
-missing, malformed, oversized, stale relative to a represented source file, or
-contain absolute, traversal, missing, symlink, or non-file document paths fail
-before the SCIP tier is replaced.
-
-## Known bounds and limitations
-
-- The importer supports standard SCIP `Index`, `Document`, `Occurrence`,
-  `SymbolInformation`, and `Relationship` fields needed for definitions,
-  references, source ranges, and relationships. Unknown protobuf fields are
-  skipped, but unsupported wire types and malformed ranges fail closed.
-- Precision and coverage are bounded by the producer. Checked-in coverage is
-  npm-integrity-pinned `@sourcegraph/scip-typescript@0.4.0` over TypeScript. Its
-  emitted documents omit the optional language field, so the import report says
-  `unknown`; other conforming producers and languages are not certified by C84.
-- The index mtime must be at least as new as every represented source file.
-  This is a conservative local freshness check, not a claim that the producer
-  indexed the exact Git commit or compiler configuration.
-- An import replaces the prior SCIP tier as one snapshot. It does not merge
-  multiple SCIP files, watch an index, start a daemon, or provide live LSP.
-  Live LSP requires a separately approved roadmap item.
-- SCIP local symbols are scoped by document. Relationship flags remain distinct
-  (`reference`, `implementation`, `type-definition`, or `definition`); only an
-  actual cross-file occurrence reference contributes a `scip_import` file edge.
-- The checked-in replay is synthetic and authorizes no superiority,
-  production-readiness, trusted-distribution, or cross-platform claim.
-
-The replay, verifier, raw results, and resource report live under
-`benchmarks/evaluations/c84-scip-import/`; run `npm run verify:c84` entirely
-offline to reproduce them.

package/docs/SIGNED-UPDATES.md

@@ -1,151 +0,0 @@
-# Signed update metadata trust
-
-knodin's update trust is local and channel-independent. npm, Homebrew,
-Artifactory, GitHub SaaS, and GHES may transport metadata and artifacts, but no
-one transport is an authority to install code.
-
-`src/update-trust.ts` is the pure verification boundary. It performs no network
-request, package-manager command, filesystem activation, or telemetry write.
-`src/update-policy.ts` composes that verifier with bounded HTTPS fetching,
-private monotonic state, policy, channel cross-checking, quarantine, exact local
-manager artifacts, health validation, and rollback. C64 adds the release-time
-CycloneDX/Sigstore evidence and fail-closed five-channel attestation machinery;
-C65 must still certify the smoke sandbox and recovery drills, and a real release
-must produce verified evidence before activation is enabled.
-
-## Trust model
-
-The metadata model has four disjoint Ed25519 roles:
-
-| Role | Purpose | Maximum signed lifetime | Required threshold |
-| --- | --- | ---: | ---: |
-| `root` | Delegates keys and rotates trust | 366 days | At least 2 |
-| `targets` | Authorizes immutable release artifacts and channels | 93 days | At least 2 |
-| `snapshot` | Binds an exact targets version, length, and digest | 32 days | At least 1 |
-| `timestamp` | Publishes the current snapshot and bounds freezes | 8 days | At least 1 |
-
-Root and targets thresholds prevent one stolen signing key from authorizing a
-release. All four roles must use separate, content-addressed keys. A root
-rotation is accepted one version at a time and only when both the previously
-trusted root threshold and the candidate root threshold sign the new root.
-
-The initial root envelope is trusted only when its SHA-256 matches an
-independently pinned digest shipped by a previously trusted knodin build. The
-pin must never be learned from fetched metadata or a package registry.
-
-Metadata is signed over deterministic UTF-8 JSON: object keys use ECMAScript
-code-unit ordering, arrays retain order, and undefined, cyclic, non-finite, or
-non-plain values are rejected. Key IDs are the SHA-256 of the canonical public
-key record.
-
-## Verification order
-
-The verifier fails closed in this order:
-
-1. Validate the installed trusted root and its independent digest pin.
-2. Verify the trusted root's own threshold signatures.
-3. Accept the same root byte-for-byte, or verify a one-step rotation under both
-   old and new root thresholds.
-4. Validate role separation, schema, generation time, expiry, and maximum
-   metadata lifetime.
-5. Verify threshold signatures for targets, snapshot, and timestamp.
-6. Bind timestamp to the exact canonical snapshot envelope by version, byte
-   length, and SHA-256.
-7. Bind snapshot to the exact canonical targets envelope the same way.
-8. Compare every role's version and digest with durable prior state. Lower
-   versions are rollback; changed bytes at the same version are equivocation.
-9. Select only the requested relative target path.
-10. Before quarantine, compare the downloaded artifact with its signed byte
-    length and SHA-256.
-
-The successful result returns the exact verified root envelope. C63 persists it
-for evidence, but never promotes a root merely because mutable local state says
-it is trusted: each check and rollback remains anchored to the independently
-shipped initial root and pin. When more than one rotation was missed, the client
-fetches each numbered intermediate root, bounds one check to 32 rotations,
-cross-checks every intermediate across configured mirrors, and advances only
-one dual-threshold version at a time. A skipped, substituted, malformed, or
-wrong-version intermediate root fails closed without persisting new trust.
-
-The signed target also carries the semantic version, release channel, full
-source commit, and digests for build provenance, the CycloneDX SBOM, its signed
-attestation, and the cross-channel release attestation. Metadata validation
-accepts these fields so notify-only clients can read a staged repository, but
-download/apply refuses when any digest is absent. The verifier does not invent
-missing provenance or promote a merely claimed channel result.
-
-## Defenses and limits
-
-Executable tests cover valid threshold authorization, missing threshold
-signatures, signed-field mutation, artifact substitution, expired timestamp
-freeze, rollback, same-version equivocation, mix-and-match metadata, role-key
-reuse, root-pin substitution, future metadata, and root rotation without the
-old threshold. Recovery tests additionally cover missed sequential rotations,
-skipped roots, intermediate mirror disagreement, and malicious version jumps.
-
-An isolated 0.4.3 adversarial drill executed the trust, policy, CLI, and release-
-attestation suites together: 4 files and 52 scenarios passed on macOS with Node
-26. Its machine-readable record is
-`docs/evidence/0.4.3-update-defense-drill.json`. The record separately identifies
-the post-tag commit from which the drill executed and the immutable 0.4.3 source
-commit whose implementation it exercised, plus the environment, command,
-defenses, and exclusions. Injected transport, package-manager, smoke, and health
-adapters make this repeatable evidence of the verification and recovery logic;
-they do not certify a real npm/Homebrew mutation path or replace the production
-ceremony and live drills.
-
-The verifier cannot make the first installation trustworthy by itself. A
-production release still requires an offline root-key ceremony, independent
-pin distribution, durable trusted-state storage, compromised-key rotation
-drills, and verified artifacts on every approved channel. Until that ceremony
-and C64–C65 are complete:
-
-- the former npm `latest` hint is not used by doctor, status, MCP, or update commands;
-- no release is authorized by `src/update-trust.ts` in production;
-- no automatic update may be enabled; and
-- a registry, formula, release page, or mutable URL must not be treated as a
-  root of trust.
-
-## Production key ceremony gate
-
-Private root keys must be created and retained offline under separate
-custodians. No production private key or recovery secret belongs in this
-repository, CI variables, npm, Homebrew, GitHub, GHES, or Artifactory. Before
-activating signed checks, the release owners must record:
-
-- custodians and a two-person approval path;
-- public key IDs and the independently reviewed root-envelope digest;
-- offline backup and recovery controls;
-- online targets/snapshot/timestamp key storage and rotation periods;
-- emergency revocation and root-rotation rehearsal evidence; and
-- the exact knodin source commit that first embeds the trusted root pin.
-
-This external ceremony is deliberately a release gate rather than generated
-test material masquerading as production trust.
-
-The fail-closed preparation contracts and multi-custodian rehearsal procedure
-are in [`ROOT-CEREMONY-RUNBOOK.md`](ROOT-CEREMONY-RUNBOOK.md). Their import seam
-accepts public material only and always returns `productionActivation: false`;
-it does not alter the production `trust-unconfigured` behavior.
-
-## Client policy and recovery
-
-The implemented policy modes are `notify-only`, `download-verify-only`,
-`apply-patch`, and `apply-minor`; major updates always require manual approval.
-Policies also bound release age, approved channels, enterprise mirror origins,
-optional exact metadata/artifact cross-checks, and UTC maintenance windows.
-
-`knodin update status` and `explain` are offline reads. `check` uses no
-repository context. `apply` first quarantines and verifies the candidate plus a
-signed artifact for the currently installed version. A missing rollback target,
-provenance object, SBOM, release attestation, smoke sandbox, manager adapter, or
-health check is a refusal, not a warning. Explicit rollback re-verifies the
-stored signed metadata, artifact, provenance, SBOM, both attestations, and every
-quarantine path before invoking the manager; nested symlink redirection is a
-hard refusal. Apply also requires the candidate attestation's rollback version,
-path, and derived digest to match the separately downloaded and verified rollback
-artifact. Signed
-non-SemVer target versions are ineligible before path construction; quarantine
-uses fresh exclusive files under a symlink-rejecting private root; and automatic
-rollback succeeds only after a second health check validates the restored
-installation.

package/docs/TELEMETRY.md

@@ -1,46 +0,0 @@
-# Local savings telemetry
-
-knodin's optional telemetry is local, metadata-only, and disabled by default.
-It uses `gpt-tokenizer@3.4.0` with the `o200k_base` encoding and records:
-
-- the actual optimized response contract, bytes, and tokens;
-- an executed full-file baseline only when the operation identifies bounded
-  repository-contained files;
-- byte and token savings, including negative savings;
-- latency p50/p95 inputs, process RSS, cold/warm operation state, success/error
-  outcome, agent round trips, truncation, detail mode, and MCP schema token cost;
-- freshness failures, compression-fidelity samples, indexing time, and current
-  local index storage where those measurements are available;
-- a one-way SHA-256-derived repository identifier for per-repository grouping.
-
-Unknown baselines remain `null`; knodin does not invent a full-file comparison.
-Persisted records contain no source or file paths. Enable persistence for an MCP
-call with `persistTelemetry: true`. Records default to 30-day retention and are
-stored mode `0600` with atomic replacement. Inspect and manage them with:
-
-```text
-knodin telemetry status
-knodin telemetry report
-knodin telemetry export
-knodin telemetry clear
-```
-
-`--retention-days 1..3650` changes the read/persistence window. `--input` and
-`--output` accept only repository-contained, non-symlink paths. `clear` is the
-only command that deletes the private JSONL file; report and export never do.
-
-The default report is `.knodin/telemetry-report.html`. It includes summary,
-operation, time-series, private repository, indexing-cost, latency, freshness,
-and fidelity views with light/dark styling. The default machine-readable export
-is `.knodin/telemetry-export.json` and labels measured, modeled, and unknown
-baselines explicitly. Neither artifact needs a daemon, hosted service,
-authentication, or source egress.
-
-Telemetry never persists source, raw tool output, command text, usernames, or
-absolute paths. A measured baseline is an executed, bounded, repository-local
-full-file read; it is not inferred from file counts. Unsupported baselines and
-metrics remain `null` or are counted as unavailable instead of being modeled.
-
-ROI telemetry is separate from troubleshooting diagnostics. Telemetry measures
-product behavior; `knodin diagnostics` retains sanitized failure envelopes and
-creates a user-inspectable support bundle. See `docs/DIAGNOSTICS.md`.

package/docs/assets/knodin-favicon.svg

@@ -1,4 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 64 64" width="64" height="64">
-  <path d="M46,6 L4,32 L46,58 L46,44 L26,32 L46,20 Z" fill="#130032" />
-  <path d="M58,24 L58,40 L34,32 Z" fill="#4C00FF" />
-</svg>

package/docs/releases/0.3.0.md

@@ -1,46 +0,0 @@
-# Reckon Graph 0.3.0 release notes
-
-Reckon Graph 0.3.0 makes graph freshness revision-truthful and closes the
-lifecycle and completion-audit gaps observed in a large multi-worktree field
-run. It is a backward-compatible minor release.
-
-## Freshness and lifecycle
-
-- Every graph answer carries a canonical current/indexed revision and
-  dirty-working-tree freshness envelope.
-- Durable, coalescing hook events survive contention and failures; status,
-  `wait --fresh`, and `status --watch` expose queue progress.
-- Deep repair binds a revision only after complete content verification.
-- Worktree status, reconciliation, and safe dry-run removal expose per-worktree
-  graph ownership and detect removed worktrees.
-
-## Diagnostics and completion audits
-
-- Doctor reports separate Claude, Codex, Gemini, and Antigravity configuration,
-  protocol checks, and active-session evidence.
-- Repair plans distinguish health findings from planned operations.
-- PR listing and audits return explicit repository/login/error/zero-result
-  context, reviews, threads, checks, merge commits, branches, and graph impact.
-
-## Bounded structural context
-
-- File and batch outlines include stable identity, signatures, ranges,
-  visibility, containment, and parser evidence.
-- Source-only explain and deterministic project overview reduce unnecessary
-  full-file reads.
-- Go and Rust outlines use checked-in local Tree-sitter grammars.
-- Optional local telemetry uses
-  `gpt-tokenizer@3.4.0:o200k_base`, preserves negative savings, measures schema
-  cost, and can render a static repository-local report without egress.
-
-Command execution/output compression was evaluated but is not shipped because
-portable hard memory and process-tree containment were not proven. Competitor
-behavioral measurements remain incomplete without an authorized packaged
-release or raw usage dataset. A post-release audit now pins and verifies the
-authorized source revision without treating source inspection as end-to-end
-performance evidence. See
-[`../RELEASE-0.3-EVIDENCE.md`](../RELEASE-0.3-EVIDENCE.md) and
-[`../COMMAND-OUTPUT-COMPRESSION.md`](../COMMAND-OUTPUT-COMPRESSION.md).
-
-No tag, npm publication, Homebrew publication, or P&T mirror is created by this
-release PR; each remains a separately authorized release action.

package/docs/releases/0.4.0.md

@@ -1,68 +0,0 @@
-# Reckon Graph 0.4.0 release notes
-
-Reckon Graph 0.4.0 delivers the implemented portions of the Token Optimizer
-parity program and adds trusted-update, release-attestation, large-portfolio,
-and compact-response capabilities. It is a backward-compatible minor release.
-
-## Compact structural and diagnostic context
-
-- Compact file and batch outlines, symbol extraction, symbol search, and
-  project overview reduce response tokens while retaining stable identity,
-  source locations, parser evidence, ambiguity, and freshness.
-- Deterministic log compression preserves diagnostic structures, enforces hard
-  budgets, records omissions, and supports bounded retrieval without rerunning
-  the original command.
-- Failure diagnosis links log evidence to files, symbols, callers,
-  dependencies, tests, and recent changes in the local graph.
-- The checked-in Token Optimizer replay and evidence-linked scorecard pin the
-  competitor and Reckon revisions and keep unsupported claims explicit.
-
-## Portfolio and lifecycle reliability
-
-- Repository filters are applied before inventory, large `git ls-files`
-  responses are supported, and selected repositories are processed
-  sequentially.
-- Portfolio initialization is bounded, resumable, and truthful in dry-run
-  mode, including nested repositories and noisy Salesforce metadata.
-- Lifecycle queues, `wait --fresh`, and installed-versus-active client status
-  provide revision-truthful observability.
-- Terminal help uses a declarative command model and the available terminal
-  width while remaining snapshot-testable.
-
-## Private ROI evidence
-
-- Local, opt-in telemetry uses a real tokenizer and records bounded operation,
-  latency, indexing, schema, fidelity, and savings metrics without source,
-  command text, absolute paths, usernames, or network egress.
-- The self-contained dashboard and export bundle distinguish directly measured
-  observations from modeled counterfactuals.
-
-## Trusted distribution and updates
-
-- Signed-only update status, check, explain, apply, and rollback policies bind
-  artifact length/digest, channel, provenance, SBOM, release age, maintenance
-  window, and rollback state.
-- TUF-inspired root, targets, snapshot, and timestamp verification detects
-  rollback, freeze, mix-and-match, expiry, threshold, and compromised-channel
-  failures. Bounded sequential root recovery handles missed rotations.
-- The release workflow builds one tarball, creates and independently verifies
-  provenance and CycloneDX SBOM attestations, then publishes the exact bytes to
-  npm and Docusign Artifactory.
-- Final certification additionally requires byte-identical GitHub SaaS, GHES,
-  and Homebrew observations plus the machine-readable cross-channel release
-  attestation.
-
-## Intentional boundary
-
-Reckon does not expose unrestricted shell execution. Portable process-tree,
-filesystem, network, credential, and resource containment has not been proven,
-so command execution remains an explicit safety-based non-goal. Existing
-trusted execution tools can pass their output to Reckon's compression and
-failure-diagnosis operations.
-
-Version preparation does not itself publish any channel. The release is
-certified only after the separately authorized tag workflow and five-channel
-verification complete. Production offline root custody, compromised-runner
-drills, automated non-personal GHES mirroring, timed onboarding, and native
-Windows named-client certification remain documented limitations until their
-evidence is recorded.

package/docs/releases/0.4.1.md

@@ -1,28 +0,0 @@
-# Reckon Graph 0.4.1 release notes
-
-Reckon Graph 0.4.1 is the publishable patch release of the 0.4 line. It contains
-all functionality described in the 0.4.0 release notes plus a fail-closed
-release-verification compatibility fix.
-
-## Release verification fix
-
-- The workflow now verifies signed provenance and the CycloneDX SBOM using the
-  exact certificate identity together with repository, source digest, source
-  ref, predicate type, and GitHub Actions OIDC issuer constraints accepted by
-  the current GitHub CLI.
-- The release-attestation CLI test double now runs with `set -eu`, ensuring an
-  assertion mismatch actually fails the test instead of continuing to a later
-  successful command.
-
-## Why 0.4.0 was not published
-
-The immutable `v0.4.0` tag reached the signed-evidence stage, then failed closed
-before npm or Artifactory publication because the installed GitHub CLI rejects
-combining `--cert-identity` with `--signer-workflow`. The tag remains unchanged
-for auditability and 0.4.0 was not published to any package channel. This patch
-release contains the corrected workflow rather than rewriting the existing
-tag.
-
-As with every release, version preparation alone does not certify distribution.
-Certification requires the tag workflow and byte-for-byte verification across
-npm, Docusign Artifactory, GitHub SaaS, GHES, and Homebrew.

package/docs/releases/0.4.2.md

@@ -1,27 +0,0 @@
-# Reckon Graph 0.4.2 release notes
-
-Reckon Graph 0.4.2 is the publishable patch release of the 0.4 line. It contains
-all functionality described in the 0.4.0 and 0.4.1 release notes plus a
-canonical CycloneDX attestation-predicate fix.
-
-## CycloneDX attestation verification fix
-
-- The release workflow and final cross-channel verifier now use the canonical
-  `https://cyclonedx.org/bom` predicate type emitted by GitHub's SBOM
-  attestation action. The CycloneDX document's `specVersion` remains validated
-  independently as 1.4, 1.5, or 1.6.
-- Regression tests require the canonical attestation predicate for SBOM bundles
-  and reject accidental coupling to a document-version URI.
-
-## Why 0.4.1 was not published
-
-The immutable `v0.4.1` tag produced a verified release tarball, signed SLSA
-provenance, and a signed CycloneDX SBOM, then failed closed before npm or
-Artifactory publication. Inspection of the signed bundle proved that GitHub
-emitted `https://cyclonedx.org/bom`, while the verifier requested
-`https://cyclonedx.org/bom/v1.5`. The tag remains unchanged for auditability;
-this patch release corrects the verifier instead of rewriting it.
-
-Version preparation alone does not certify distribution. Certification still
-requires the tag workflow and byte-for-byte verification across npm, Docusign
-Artifactory, GitHub SaaS, GHES, and Homebrew.

package/docs/releases/0.4.3.md

@@ -1,23 +0,0 @@
-# Reckon Graph 0.4.3
-
-Reckon Graph 0.4.3 corrects the approved Docusign Artifactory channel identity
-used by final release attestation.
-
-## Release-integrity correction
-
-- Final channel evidence now requires the authoritative
-  `artifactory-corp.docusignhq.com` host returned by Docusign Artifactory.
-- The obsolete `artifactory.docusignhq.com` alias is rejected. It does not
-  serve the published raw artifact and must not appear in a verified release
-  record.
-- Regression fixtures cover the production host and prevent the obsolete alias
-  from returning.
-
-Version 0.4.2 was successfully published to npm, Artifactory, GitHub SaaS, and
-Homebrew, but its final five-channel attestation was intentionally withheld when
-the real Artifactory observation exposed this host mismatch. No mismatched
-artifact was installed: all four observed 0.4.2 artifacts had identical bytes.
-
-As with every release, 0.4.3 is certified only after the tag workflow and final
-cross-channel verification complete successfully. Preparing this version does
-not itself publish it.

package/docs/releases/0.5.0.md

@@ -1,29 +0,0 @@
-# knodin 0.5.0
-
-knodin 0.5.0 completes the public product and package rename from Reckon Graph.
-
-## New identity
-
-- The unscoped npm package is `knodin`.
-- The canonical executable is `knodin`.
-- The MCP server and its single gateway tool are named `knodin`.
-- The display name is always lowercase, with the caret-beak mark as the
-  canonical logo and `<◀  knodin` as the terminal lockup.
-
-## Compatibility
-
-- The package still exposes `reckon` as a compatibility executable.
-- Existing `.reckon/` state, `reckon.yaml`, and `RECKON_*` environment
-  variables are retained so the rename does not force a reindex or invalidate
-  local configuration.
-- `knodin init` migrates managed MCP registrations and recognizes lifecycle
-  hooks created by Reckon Graph.
-- Historical benchmark and release evidence retains its original product name
-  and source identities.
-
-## Distribution
-
-Public npm is the initial supported installation channel. The previous
-`reckon-graph` package remains available as a deprecated compatibility
-signpost; it is not unpublished. The legacy Homebrew formula is not a supported
-knodin 0.5.0 channel.

package/docs/releases/0.5.1.md

@@ -1,17 +0,0 @@
-# knodin 0.5.1
-
-knodin 0.5.1 makes the lowercase product name canonical across every public
-distribution surface.
-
-## Canonical identity
-
-- The GitHub organization and repository are `knodin/knodin`.
-- Package metadata, release attestations, documentation, and planned Homebrew
-  paths no longer use the temporary `knowdin` organization spelling.
-
-## npm branding
-
-- The caret-beak SVG is included in the published package.
-- The README loads the logo through the public npm CDN, so it renders on npm
-  even while the source repository remains private.
-

package/docs/releases/0.6.0.md

@@ -1,18 +0,0 @@
-# knodin 0.6.0
-
-This release completes the operational product rename.
-
-- Repository-local graph, hook, lifecycle, telemetry, and generated state now
-  lives under `.knodin/`.
-- Team system configuration is now `knodin.yaml`.
-- Runtime environment variables use the `KNODIN_` prefix.
-- Managed Git hooks, agent instructions, MCP registrations, and configuration
-  markers use only `knodin` identifiers.
-- The package installs only the `knodin` executable; the former command alias
-  has been removed.
-- The npm README is reorganized around product value, measured competitive
-  results, installation, first use, and capability reference.
-
-Existing local graph directories must be renamed from the former hidden-state
-path to `.knodin` before using this release. Re-run `knodin init` afterward to
-refresh managed hooks and agent configuration.

package/docs/releases/0.7.0.md

@@ -1,24 +0,0 @@
-# knodin 0.7.0
-
-This release is the dogfood-readiness release for local code intelligence with
-bounded, user-controlled troubleshooting evidence.
-
-- Adds `knodin diagnostics enable|status|collect|inspect|clear|disable` with a
-  private, bounded local failure journal and redacted support bundles. Nothing
-  is uploaded automatically.
-- Captures sanitized CLI and MCP failure correlation IDs without retaining
-  source, queries, arguments, environment values, credentials, or raw paths.
-- Adds contained execution profiles with explicit platform support and
-  fail-closed behavior when the requested containment cannot be established.
-- Adds structural cold-start routing and checked-in C87 latency evidence while
-  preserving truthful response budgets and freshness metadata.
-- Integrates lifecycle refresh through hook-manager-native Lefthook routing,
-  while preserving repository-owned configuration and distinguishing graph
-  repair from lifecycle reinitialization.
-- Tightens freshness proof, response-budget accounting, package smoke coverage,
-  and roadmap evidence for the completed local feature set.
-
-This ordinary 0.x release is intended for normal installation, including the
-initial Docusign rollout. The external evidence and signed-release gates in
-`roadmap/competitive-roadmap.md` remain open and continue to block GA and
-trusted-distribution claims; publication does not waive or simulate them.

package/docs/releases/0.7.1.md

@@ -1,21 +0,0 @@
-# knodin 0.7.1
-
-This is the first normally published 0.7 release of knodin. It provides local,
-opt-in diagnostics that users can collect and deliberately share when they
-need troubleshooting help; it is not a special dogfood build or prerelease.
-
-- Adds `knodin diagnostics enable|status|collect|inspect|clear|disable` with a
-  private, bounded local failure journal and redacted support bundles. Nothing
-  is uploaded automatically.
-- Captures sanitized CLI and MCP failure correlation IDs without retaining
-  source, queries, arguments, environment values, credentials, or raw paths.
-- Adds contained execution profiles, structural cold-start routing, lifecycle
-  refresh improvements, tighter freshness proof, and truthful response-budget
-  accounting.
-- Corrects the release test suite so the competitive sandbox contract is
-  verified on systems both with and without Bun installed.
-
-This ordinary 0.x release is suitable for installation through npm,
-Artifactory, and Homebrew, including use by Docusign employees. The external
-evidence and signed-release gates recorded in `roadmap/competitive-roadmap.md`
-remain open and continue to block GA and trusted-distribution claims.