# 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.