token-harness 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Giulio Ardoino
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+

package/README.md

@@ -0,0 +1,289 @@
+# Token Harness
+
+> One control plane for token-efficient coding agents.
+
+Token Harness is an open-source orchestrator for token-saving tools used by coding
+agents. It detects the active coding harness, installs compatible optimization
+providers, prevents conflicting integrations, verifies that the resulting pipeline
+works, and reports savings through one normalized metrics model.
+
+Token Harness is not another compressor. It coordinates specialized projects at
+different layers of the agent pipeline. This is the current integration landscape;
+"candidate" means researched, not supported or installed by this release.
+
+| System | Layer and added value | Token Harness state |
+| --- | --- | --- |
+| [RTK](https://github.com/rtk-ai/rtk) | Command rewriting and shell-output reduction | **Integrated today** for Claude Code |
+| [HarnessTrim](https://github.com/giuliastro/HarnessTrim) | Deterministic reducers, harness adapters, skills, pipes, and MCP integration | **MVP provider in progress**: detection, adoption, conflict reconciliation, and metrics |
+| [Dejavu](https://github.com/Salnika/dejavu) | Emits only the delta when a command produces repeated output | Priority candidate; requires an RTK ordering fixture and native-Windows work |
+| [Lazy MCP](https://github.com/voicetreelab/lazy-mcp) | Loads MCP tool schemas only when the agent needs them | Priority, largely orthogonal candidate |
+| [repowise](https://github.com/repowise-dev/repowise) | Retrieves task-shaped repository context instead of repeated grep/read loops | Priority candidate; response bounds and attribution must be verified |
+| [LiteLLM](https://github.com/BerriAI/litellm) | Self-hosted model gateway, fallbacks, load balancing, budgets, and usage telemetry | Routing foundation candidate; it does not by itself prove token savings |
+| [RouteLLM](https://github.com/lm-sys/RouteLLM) | Routes easier requests to a cheaper model through an OpenAI-compatible endpoint | Learned-routing candidate; needs coding-agent quality benchmarks |
+| [vLLM Semantic Router](https://github.com/vllm-project/semantic-router) | Routes by task, complexity, tools, and deployment locality for self-hosted inference | Alternative routing candidate for local inference fleets |
+| [Headroom](https://github.com/headroomlabs-ai/headroom) | Compresses tool, MCP, file, and RAG payloads and can lower effort on routine turns | Broad-context candidate; alternative to Context Mode, with overlap tests required |
+| [Context Mode](https://github.com/mksglu/context-mode) | Keeps raw tool/MCP results outside context and restores compact session memory | Broad-context candidate; alternative to Headroom, source-available under ELv2 |
+| [LLMLingua](https://github.com/microsoft/LLMLingua) | Model-based prompt compression engine for long context | Engine candidate, not yet a direct harness adapter |
+| [Caveman](https://github.com/JuliusBrussee/caveman) | Steers shorter visible model replies | Opt-in candidate; output savings only, with quality and prompt-overhead checks |
+
+The evidence, licenses, conflicts, and recommended admission order are recorded in the
+[provider landscape](docs/provider-landscape.md). Routing savings are reported as cost or
+quality trade-offs, never silently added to exact token savings.
+
+Upstream tools remain independent. Token Harness installs supported releases through
+their official distribution channels and never silently vendors or forks them.
+
+## Product identity
+
+| Surface | Value |
+| --- | --- |
+| Product name | Token Harness |
+| Repository/package slug | `token-harness` |
+| CLI command | `token-harness` |
+| License | Apache-2.0 |
+| Runtime | Node.js 22.13.0+ |
+| Language | TypeScript |
+| Package manager | pnpm |
+
+## Core principles
+
+1. **Plan before apply.** Every mutation is represented as a reviewable plan. Dry-run
+   is the default, and no flag skips planning.
+2. **One owner per interception surface.** The planner prevents two providers from
+   rewriting or compressing the same payload unless that exact chain is validated — and
+   it keeps checking after installation, because config files keep changing.
+3. **Upstreams stay upstream.** Providers wrap official installers and APIs instead
+   of copying their implementations.
+4. **Measured, not marketed.** Exact, estimated, and counterfactual savings are
+   reported separately and never summed into one headline number.
+5. **Proven, not assumed.** Verification states its tier: presence, config-only, or an
+   observed canary. A configuration that looks correct is never presented as proof that
+   the harness reaches the provider.
+6. **Reversible by construction.** Configuration edits are marker-owned, backed up,
+   journaled, and removable.
+7. **Local-first.** No account or telemetry is required. Usage data stays local unless
+   the user explicitly enables an upstream service.
+8. **Cross-platform.** Windows, macOS, Linux, and WSL are first-class targets, with
+   unsupported combinations surfaced before installation.
+
+## Initial user experience
+
+```text
+token-harness doctor
+token-harness plan
+token-harness apply --yes
+token-harness verify
+token-harness metrics --since 7d
+token-harness status
+token-harness rollback --yes
+```
+
+Existing installations are adopted, not replaced. If RTK or HarnessTrim is already
+configured by hand, Token Harness detects it, plans around it, and leaves it in place on
+uninstall.
+
+`0.1.0` supports Codex, Claude Code, and OpenCode. RTK is managed end to end: detected,
+configured, verified, measured. HarnessTrim is detected, adopted, reconciled against RTK's
+ownership, and measured — but not installed, because at its current release no configuration
+exists that would let both tools reduce output without contesting the same surface. Token
+Harness reports that contest instead of hiding it.
+
+Additional tools, and joint reduction by two providers, are introduced only after
+compatibility and attribution tests prove they compose safely.
+
+## Status
+
+**Version `0.1.0`.** PLAN §16 defines that number as: RTK and HarnessTrim, three harnesses,
+transactional install, verification with declared tiers, metrics, and brownfield adoption. All
+of it is here, and a test refuses the version string unless the registries and the command
+surface actually back it.
+
+### The nine criteria
+
+PLAN §2 lists what makes `0.1.0` useful. Measured, not estimated:
+
+| # | Criterion | State |
+| --- | --- | --- |
+| 1 | `doctor` detects Codex, Claude Code, or OpenCode | **done** — all three |
+| 2 | RTK and HarnessTrim: available, installed, configured, broken | **done** |
+| 3 | Dry-run plan for a compatible setup | **done** |
+| 4 | Apply that plan transactionally | **done** |
+| 5 | Verify the integration, with the tier stated | **done** |
+| 6 | Inspect normalized savings | **done** — both providers |
+| 7 | Uninstall or roll back without damage | **done** |
+| 8 | Adopt an existing hand-configured installation | **done** — both providers |
+| 9 | Windows, macOS, Linux | **done** — CI on all three, every commit |
+
+### What it looks like on a real machine
+
+```text
+$ token-harness doctor
+Harnesses
+  claude      configured  ~/.claude/settings.json
+  codex       configured  ~/.codex/config.toml
+  opencode    detected    ~/.config/opencode/opencode.jsonc
+
+Providers
+  rtk           configured    0.42.0  configured for claude (adopted, not managed)
+  harnesstrim   configured            configured for codex (adopted, not managed)
+```
+
+```text
+$ token-harness verify
+rtk — claude — adopted, not managed — declared tier: canary
+  pass           canary-intercepted         494 commands intercepted on 2026-07-31
+harnesstrim — codex — adopted, not managed — declared tier: config-only
+  not-exercised  canary-intercepted         no telemetry file exists, so no interception has been recorded
+```
+
+That second line is the point of the whole verification model: the hook is correctly
+configured, and it has never run. RFC 0007 exists because "configured" and "working" are
+different claims, and `not-exercised` is neither a pass nor a failure.
+
+`metrics` on the same machine reports **91,600 tokens saved over 2,847 intercepted
+commands** — exactly what `rtk gain` reports independently.
+
+### The full command surface
+
+```text
+token-harness doctor                  what is here, and what is broken
+token-harness plan                    what would change; nothing is written
+token-harness apply --yes             write it, inside a reversible transaction
+token-harness verify                  is it actually intercepting, at which tier
+token-harness metrics --since 7d      what it saved, by measurement class
+token-harness status                  drift, and competing hooks on owned surfaces
+token-harness uninstall --yes         remove only what Token Harness owns
+token-harness rollback --yes          restore the files a transaction changed
+token-harness update                  what a newer version would be, per channel
+```
+
+That is all nine commands RFC 0001 declares. `update` was the last one missing.
+
+It asks each provider's own installation channel what version it offers and compares that with
+what is installed — the installed side comes from the provider, the available side from the
+channel, because `winget` knows what exists for `rtk-ai.rtk` and RTK's adapter does not. Reaching
+the channel is a network read and it happens on a dry run too, since a target version cannot be
+named without asking, so the destinations are reported.
+
+It updates and nothing else. A provider that is not installed is left alone, a channel offering
+something older is not acted on, and a channel that cannot be read produces *unknown* rather than
+the far more comfortable *up to date*. A pinned provider is skipped and its pin is named; a pin
+written inside a repository is reported and not honored, because a repository may not choose which
+version of a tool you run.
+
+And the honest limit, printed rather than implied: an updated package is not restored by a
+rollback. Rollback restores files, and a package is not a file.
+
+### Guarantees worth knowing before you run `apply`
+
+- **Dry-run by default.** Without `--yes`, mutating commands display the plan and exit 8.
+- **One appended entry, not a rewritten list.** Your other hooks keep their content and their
+  order; a test asserts your entry is still first afterwards.
+- **Every file is snapshotted first**, including files that did not exist, so a rollback can
+  restore their absence. The restoration is verified by reading the files back — which is what
+  separates exit 6 (rolled back) from exit 7 (did not fully restore).
+- **Token Harness removes only what a committed journal records as its own.** Not what merely
+  looks like its own: an entry whose bytes match what it would have written is still yours if
+  it did not write it, and `uninstall` says so and declines.
+- **A change you did not ask for is reported.** Editing a hand-formatted JSON file reformats
+  it, and that warning reaches you rather than only the journal.
+- **A competing hook on an owned surface is reported, never removed.** `status` names the file,
+  the surface, and the competing command, and exits 3.
+
+### What is honest about the limits
+
+- **HarnessTrim is never installed**, by design rather than omission. RFC 0003 §Resolution at
+  0.1.0 checked its installer at `0.0.5` and found no configuration that lets it and RTK reduce
+  output without contesting the same surface. So it is detected, adopted, reconciled, and
+  measured — and left alone. Under `profile: custom` you may hand it the scope instead of RTK.
+- **An installed package cannot be rolled back.** `apply` can now run a package manager, but a
+  package is not a file and there is no snapshot of one, so a later failure restores your files and
+  leaves the package installed. The report says so rather than letting "rolled back" imply the
+  machine is as it was. Elevation is refused outright, with the exact command to run yourself.
+- **A provider that cannot report its version is still adopted.** Older HarnessTrim builds reject
+  `--version`; Token Harness asks, falls back, and reports the tool as installed with no version
+  rather than as missing. It never reads the reachable `package.json`, which names the monorepo
+  rather than the CLI.
+- **Codex hooks cannot be proven to run.** Enablement and trust are persisted separately from
+  `hooks.json`, in state no adapter can read, so Codex tops out at `config-only` and says why.
+- **Two measurement findings that change how a number reads.** 75% of RTK's interceptions save
+  nothing, and RTK sometimes makes output *larger* while flooring its own counter at zero — so
+  its total is a sum of clamped values. Token Harness reports the net effect and names the
+  inflation separately.
+
+### Installing 0.1.0
+
+A single self-contained ESM artifact with **no dependencies at all**. Not on npm — publishing
+is PLAN §8.3, with provenance, SBOM, and signing — but it installs from a tarball you build
+yourself, and CI proves that on Windows, macOS, and Linux on every commit:
+
+```bash
+pnpm install && pnpm build && pnpm package
+npm install -g ./dist/package
+token-harness doctor
+```
+
+To run it without installing:
+
+```bash
+node dist/bundle/token-harness.mjs doctor
+```
+
+Every read-only command is safe to run first. `doctor`, `plan`, `status`, `verify` and
+`metrics` never touch a harness configuration, and `--project <dir>` retargets the
+project-scoped half if you want to watch it work against a scratch directory.
+
+## Development
+
+```bash
+pnpm install
+pnpm typecheck
+pnpm lint
+pnpm test
+pnpm build
+pnpm smoke
+pnpm package
+pnpm smoke:install
+```
+
+`pnpm build` produces the self-contained artifact at `dist/bundle/token-harness.mjs`;
+`pnpm smoke` runs it from a temporary directory outside the repository, so anything
+that failed to inline shows up as a resolution failure rather than as a passing test.
+CI runs all of it on `windows-latest`, `macos-latest`, and `ubuntu-latest`, in that
+order and without fail-fast, because the failures this project exists to prevent are
+mostly Windows-specific and finding them after two green jobs is how they become
+workarounds instead of design.
+
+## Release gates
+
+| Version | Gate |
+| --- | --- |
+| `0.0.x` | Internal architecture and fixtures. No stability promise. |
+| `0.1.0` | RTK and HarnessTrim, three harnesses, transactional install, verification with declared tiers, metrics, brownfield adoption **← here** |
+| `0.2.0` | A third provider, goal-based profiles, the A/B benchmark matrix |
+| `1.0.0` | Stable provider and harness contracts, two release cycles with no configuration-loss defects, published benchmark results |
+
+`PLAN.md` §16 is the authority; this table is a summary of it.
+
+`pnpm golden` regenerates the derived halves of the golden fixtures. It never
+touches the five human transcripts transcribed from RFC 0006 — see
+[tests/fixtures/README.md](tests/fixtures/README.md).
+
+CI runs Windows, macOS, and Linux, with Windows first in the matrix and the
+matrix set not to fail fast.
+
+Releases publish on a `v*` tag through npm trusted publishing: OIDC, no token in the repository
+secrets or anywhere else, and provenance signed by npm. A tag that does not match the staged version
+is refused before the publish rather than discovered by whoever installs it.
+
+- [Compatibility, verification tiers, and known limitations](docs/matrices.md) — the tables are
+  generated from the manifests and a test fails if they drift; the limitations below them are prose,
+  and a test checks that every limitation the code declares appears there
+- [Development plan](PLAN.md)
+- [Foundation decisions](docs/rfcs/0001-foundation.md)
+- [Provider contract](docs/rfcs/0002-provider-contract.md)
+- [Capability and conflict model](docs/rfcs/0003-capabilities-and-conflicts.md)
+- [Safety and installation model](docs/rfcs/0004-safety-and-installation.md)
+- [Metrics and attribution](docs/rfcs/0005-metrics-and-attribution.md)
+- [CLI contract](docs/rfcs/0006-cli-contract.md)
+- [Live verification](docs/rfcs/0007-live-verification.md)

package/package.json

@@ -0,0 +1,36 @@
+{
+  "name": "token-harness",
+  "version": "0.1.0",
+  "description": "One control plane for token-efficient coding agents.",
+  "license": "Apache-2.0",
+  "type": "module",
+  "engines": {
+    "node": ">=22.13.0"
+  },
+  "bin": {
+    "token-harness": "./token-harness.mjs"
+  },
+  "files": [
+    "token-harness.mjs",
+    "sbom.json",
+    "README.md",
+    "LICENSE"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/giuliastro/token-harness.git"
+  },
+  "homepage": "https://github.com/giuliastro/token-harness#readme",
+  "bugs": {
+    "url": "https://github.com/giuliastro/token-harness/issues"
+  },
+  "keywords": [
+    "tokens",
+    "llm",
+    "coding-agent",
+    "claude-code",
+    "codex",
+    "opencode",
+    "cli"
+  ]
+}

package/sbom.json

@@ -0,0 +1,89 @@
+{
+  "bomFormat": "CycloneDX",
+  "specVersion": "1.5",
+  "version": 1,
+  "metadata": {
+    "component": {
+      "type": "application",
+      "bom-ref": "token-harness",
+      "name": "token-harness",
+      "version": "0.1.0",
+      "description": "One control plane for token-efficient coding agents.",
+      "licenses": [
+        {
+          "license": {
+            "id": "Apache-2.0"
+          }
+        }
+      ],
+      "hashes": [
+        {
+          "alg": "SHA-256",
+          "content": "5189fd514cc13d0d291588962f83608f249ebed06d118524bc3bbda8e54092db"
+        }
+      ]
+    },
+    "tools": [
+      {
+        "name": "scripts/package.mjs"
+      }
+    ]
+  },
+  "components": [
+    {
+      "type": "library",
+      "bom-ref": "@token-harness/core",
+      "name": "@token-harness/core",
+      "version": "0.1.0",
+      "scope": "required",
+      "licenses": [
+        {
+          "license": {
+            "id": "Apache-2.0"
+          }
+        }
+      ],
+      "description": "first-party workspace package, inlined into the published bundle"
+    },
+    {
+      "type": "library",
+      "bom-ref": "@token-harness/platform",
+      "name": "@token-harness/platform",
+      "version": "0.1.0",
+      "scope": "required",
+      "licenses": [
+        {
+          "license": {
+            "id": "Apache-2.0"
+          }
+        }
+      ],
+      "description": "first-party workspace package, inlined into the published bundle"
+    },
+    {
+      "type": "library",
+      "bom-ref": "@token-harness/adapters",
+      "name": "@token-harness/adapters",
+      "version": "0.1.0",
+      "scope": "required",
+      "licenses": [
+        {
+          "license": {
+            "id": "Apache-2.0"
+          }
+        }
+      ],
+      "description": "first-party workspace package, inlined into the published bundle"
+    }
+  ],
+  "dependencies": [
+    {
+      "ref": "token-harness",
+      "dependsOn": [
+        "@token-harness/core",
+        "@token-harness/platform",
+        "@token-harness/adapters"
+      ]
+    }
+  ]
+}