knodin 0.5.0

package/docs/SIGNED-UPDATES.md

@@ -0,0 +1,146 @@
+# 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.
+
+## 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/SYSTEMS-AND-RELATIONSHIPS.md

@@ -0,0 +1,45 @@
+# Systems and relationships
+
+A system is an explicitly configured set of cooperating components. Components
+may represent APIs, resources, repositories, or artifacts. Unrelated
+repositories remain separate even when they share a parent directory or match
+the same search query.
+
+Team configuration belongs in repository-root `reckon.yaml` and contains stable
+identities without local absolute paths. Personal checkout paths belong in:
+
+```text
+$XDG_CONFIG_HOME/knodin/repositories.yaml
+```
+
+Commands:
+
+```bash
+knodin system list
+knodin system show <system-id>
+knodin system validate <system-id>
+knodin system query <system-id>
+```
+
+The existing single MCP gateway exposes the same `system` operation with
+`systemAction=list|show|validate|query`.
+
+Relationship types include dependency, API provider/consumer, deployment,
+provisioning, output/config/path references, events, images, and provenance.
+Every relationship carries its target identity, exact evidence location,
+adapter, evidence kind, confidence, freshness, and index generation when one
+exists.
+
+Declared relationships have highest confidence. Extracted package/contract/
+infrastructure relationships are source-evidenced. Inferred literal or key
+matches remain labeled and cannot silently create system membership. Optional
+runtime evidence corroborates static evidence; it does not replace canonical
+source.
+
+`.reckon/federation.json` remains a compatibility input and is never silently
+discarded. Loaded entries are labeled `legacy-federation` until migrated to
+stable identities.
+
+System validation fails closed for unresolved repository identities or missing
+required checkouts. Partial query behavior must be explicit and name every
+omitted component; absent evidence is never reported as zero.

package/docs/TELEMETRY.md

@@ -0,0 +1,42 @@
+# 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 `.reckon/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 `.reckon/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.

package/docs/releases/0.3.0.md

@@ -0,0 +1,46 @@
+# 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

@@ -0,0 +1,68 @@
+# 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

@@ -0,0 +1,28 @@
+# 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

@@ -0,0 +1,27 @@
+# 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

@@ -0,0 +1,23 @@
+# 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

@@ -0,0 +1,29 @@
+# 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/package.json

@@ -0,0 +1,110 @@
+{
+	"name": "knodin",
+	"version": "0.5.0",
+	"description": "knodin — source-evidenced local code intelligence with known bounds. Stable identity, fresh evidence, truthful budgets, and recoverable bounded views.",
+	"license": "MIT",
+	"repository": {
+		"type": "git",
+		"url": "git+https://github.com/knowdin/knodin.git"
+	},
+	"homepage": "https://github.com/knowdin/knodin#readme",
+	"bugs": {
+		"url": "https://github.com/knowdin/knodin/issues"
+	},
+	"publishConfig": {
+		"access": "public",
+		"registry": "https://registry.npmjs.org/"
+	},
+	"type": "module",
+	"bin": {
+		"knodin": "./dist/bin/cli.js",
+		"reckon": "./dist/bin/cli.js"
+	},
+	"files": [
+		"dist",
+		"docs/DEAD-CODE-AND-IMPACT.md",
+		"docs/DOCTOR-AND-UPDATES.md",
+		"docs/INDEXING-POLICY-AND-PROVENANCE.md",
+		"docs/INSTALLATION.md",
+		"docs/MCP.md",
+		"docs/COMMAND-OUTPUT-COMPRESSION.md",
+		"docs/CLI.md",
+		"docs/PT-ACCESS-RECOMMENDATION.md",
+		"docs/REPOSITORIES-AND-WORKTREES.md",
+		"docs/RELEASE-0.3-EVIDENCE.md",
+		"docs/SIGNED-UPDATES.md",
+		"docs/releases/0.3.0.md",
+		"docs/releases/0.4.0.md",
+		"docs/releases/0.4.1.md",
+		"docs/releases/0.4.2.md",
+		"docs/releases/0.4.3.md",
+		"docs/releases/0.5.0.md",
+		"docs/SYSTEMS-AND-RELATIONSHIPS.md",
+		"docs/TELEMETRY.md",
+		"schemas/release-attestation-v1.schema.json",
+		"*.wasm"
+	],
+	"engines": {
+		"node": ">=24.0.0"
+	},
+	"scripts": {
+		"prepack": "npm run build",
+		"hooks:install": "tsx scripts/prepare-hooks.ts",
+		"dev": "tsx watch src/server.ts",
+		"start": "tsx src/server.ts",
+		"cli": "tsx bin/cli.ts",
+		"clean": "node scripts/clean-dist.mjs",
+		"build": "npm run clean && tsc -p tsconfig.build.json",
+		"typecheck": "tsc --noEmit",
+		"test": "tsx scripts/run-vitest-shards.ts",
+		"test:handles": "vitest run --reporter=verbose --reporter=hanging-process",
+		"test:watch": "vitest --watch",
+		"test:coverage": "tsx scripts/run-vitest-shards.ts --coverage",
+		"scan:sonar": "npm run test:coverage && sh scripts/run-sonar-scan.sh",
+		"test:pack-install": "tsx scripts/pack-install-smoke.ts",
+		"test:package-managers": "tsx scripts/package-manager-smoke.ts",
+		"test:naming-screen": "node --test scripts/naming-screen.test.js",
+		"measure:schema": "tsx scripts/measure-tool-schema.ts",
+		"check:dependency-deprecations": "tsx scripts/check-dependency-deprecations.ts",
+		"check:hygiene": "node scripts/check-repository-hygiene.mjs",
+		"bench:ann": "bun scripts/ann-bench.ts",
+		"bench:perf": "tsx scripts/perf-bench.ts",
+		"bench:competitive": "tsx scripts/competitive-bakeoff.ts",
+		"bench:token-optimizer": "tsx benchmarks/evaluations/token-optimizer-20260730/runner.ts",
+		"audit:token-optimizer": "tsx scripts/token-optimizer-source-audit.ts",
+		"release:attestation": "tsx scripts/release-attestation.ts",
+		"lint": "biome check .",
+		"lint:fix": "biome check --write ."
+	},
+	"dependencies": {
+		"@huggingface/transformers": "^4.2.0",
+		"@modelcontextprotocol/sdk": "^1.30.0",
+		"chokidar": "^5.0.0",
+		"commander": "15.0.0",
+		"gpt-tokenizer": "3.4.0",
+		"ora": "9.4.1",
+		"re2-wasm": "1.0.2",
+		"tree-sitter-wasms": "^0.1.13",
+		"web-tree-sitter": "0.20.8",
+		"web-tree-sitter-sfapex": "2.4.1",
+		"yaml": "2.9.0",
+		"zod": "^4.3.6"
+	},
+	"overrides": {
+		"@hono/node-server": "^2.0.5",
+		"adm-zip": "^0.6.0",
+		"fast-uri": "^4.1.1",
+		"sharp": "^0.35.3"
+	},
+	"devDependencies": {
+		"@biomejs/biome": "2.4.6",
+		"@types/bun": "^1.3.14",
+		"@types/node": "^24.10.0",
+		"@vitest/coverage-v8": "^4.1.10",
+		"ajv": "8.20.0",
+		"lefthook": "^2.1.5",
+		"tsx": "^4.21.0",
+		"typescript": "^5.9.3",
+		"vitest": "^4.1.3"
+	}
+}