npm - @nzkbuild/toche - Versions diffs - 1.0.10 → 1.1.0 - Mend

@nzkbuild/toche 1.0.10 → 1.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (5) hide show

package/LICENSE CHANGED Viewed

@@ -1,201 +1,201 @@
-                                 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 Toche Contributors
-   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.
+                                 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 Toche Contributors
+   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/NOTICE CHANGED Viewed

@@ -1,18 +1,18 @@
-Toche
-Copyright 2026 Toche Contributors
-This product includes software developed by:
-- rtk-ai (https://github.com/rtk-ai/rtk) — Apache-2.0
-  Copyright 2024 rtk-ai and rtk-ai Labs
-- ryoppippi (https://github.com/ccusage/ccusage) — MIT
-  Copyright (c) 2025 ryoppippi
-- Safi Shamsi (https://github.com/Graphify-Labs/graphify) — MIT
-  Copyright (c) 2026 Safi Shamsi
-- Julius Brussee (https://github.com/juliusbrussee/caveman) — MIT
-  Copyright (c) 2026 Julius Brussee
-- multica-ai (https://github.com/multica-ai/andrej-karpathy-skills) — MIT
+Toche
+Copyright 2026 Toche Contributors
+This product includes software developed by:
+- rtk-ai (https://github.com/rtk-ai/rtk) — Apache-2.0
+  Copyright 2024 rtk-ai and rtk-ai Labs
+- ryoppippi (https://github.com/ccusage/ccusage) — MIT
+  Copyright (c) 2025 ryoppippi
+- Safi Shamsi (https://github.com/Graphify-Labs/graphify) — MIT
+  Copyright (c) 2026 Safi Shamsi
+- Julius Brussee (https://github.com/juliusbrussee/caveman) — MIT
+  Copyright (c) 2026 Julius Brussee
+- multica-ai (https://github.com/multica-ai/andrej-karpathy-skills) — MIT

package/README.md CHANGED Viewed

@@ -1,367 +1,421 @@
-<p align="center">
-  <img src="assets/branding/toche-wordmark.png" alt="Toche" width="620">
-</p>
-<p align="center">
-  <strong>Claude Code repeats less, carries less noise, and leaves you a receipt.</strong>
-</p>
-<p align="center">
-  Toche is a local gateway between Claude Code and your Anthropic API endpoint.
-  It removes avoidable work while keeping every optimization visible and reversible.
-</p>
-<p align="center">
-  <img src="assets/branding/toche-status.svg" alt="Toche 1.0.10: 65 filters, duplicate requests coalesced from many to one, zero hosted accounts, 354 Rust tests" width="820">
-</p>
-<p align="center">
-  <a href="#why-toche">Why Toche</a> ·
-  <a href="#what-changes">What changes</a> ·
-  <a href="#install">Install</a> ·
-  <a href="#how-it-works">How it works</a> ·
-  <a href="#command-reference">Commands</a> ·
-  <a href="#safety-and-control">Safety</a> ·
-  <a href="#documentation">Docs</a>
-</p>
-## Why Toche
-Claude Code sessions often pay for the same kind of waste more than once: an
-identical request is already running, a safe response was just fetched, or a tool
-prints thousands of tokens when the useful result is a few lines. Toche handles
-those cases before they consume another upstream call or more conversation space.
-The useful part is not a universal marketing percentage. Toche measures your
-actual traffic and reports what happened with `toche stats`.
-## What changes
-- **Three identical requests at the same time can become one upstream call.** The
-  first request runs while the other two wait for and share its response.
-- **An eligible local replay becomes zero new upstream calls.** Toche only replays
-  workspace-matched, text-only responses that pass its safety checks.
-- **Sixty-five command filters remove known noise.** Cargo, Git, Terraform, Helm,
-  Ansible, linters, and other supported output can be shortened while the original
-  remains recoverable with `toche expand`.
-- **Every routed request leaves a local record.** Token counts, estimated cost,
-  latency, cache decisions, coalescing, and reduction are written to a local SQLite
-  ledger instead of a Toche cloud account.
-Here is a deliberately simple example. If a supported tool prints an estimated
-10,000 tokens and its useful reduced form is 3,000, the ledger records 7,000 tokens
-removed, or 70%. That explains the measurement. It does not promise that every
-command, repository, or session will save 70%.
-Toche is most useful during long coding sessions, repeated test and diff cycles,
-parallel agent work, and projects where you want to inspect the cost of the work.
-A short conversation with no repetition or noisy tools may show little difference.
-## Install
-### Before you start
-You need:
-1. Claude Code installed and already working.
-2. Node.js 18 or newer for the npm installer.
-3. Windows x64, Linux x64, macOS Intel, or macOS Apple silicon.
-Rust is not required when installing from npm.
-### One-time setup
-1. Install Toche globally. This makes the `toche` command available anywhere.
-   ```shell
-   npm install -g @nzkbuild/toche
-   ```
-2. Import your existing Claude Code endpoint into a local Toche profile.
-   ```shell
-   toche setup
-   ```
-3. Start Toche and leave this terminal open while using Claude Code.
-   ```shell
-   toche
-   ```
-4. Open a second terminal, connect Claude Code, and verify the setup.
-   ```shell
-   toche connect
-   toche doctor
-   ```
-5. Start Claude Code normally.
-   ```shell
-   claude
-   ```
-`toche connect` creates a backup before changing Claude Code's local routing.
-### Normal daily use
-After the one-time setup, the routine is only:
-1. Run `toche` and leave it open.
-2. Run `claude` in another terminal.
-You do not need to run `setup` again. You also do not need to run `connect` again
-unless you previously used `toche disconnect`.
-### Use these only when needed
-| Command | When to use it |
-|---|---|
-| `toche stats` | You want to see requests, tokens, estimated cost, and measured savings |
-| `toche doctor` | Something is not connecting or you want a health check |
-| `toche disconnect` | You want Claude Code to bypass Toche and use its original endpoint |
-| `toche setup --force` | You intentionally want to replace the current Toche profile; a backup is created |
-To uninstall cleanly, restore Claude Code's original route first:
-```shell
-toche disconnect
-npm uninstall -g @nzkbuild/toche
-```
-<details>
-<summary><strong>Build from source instead of npm</strong></summary>
-You need Rust 1.86 or newer.
-```shell
-git clone https://github.com/nzkbuild/toche.git
-cd toche
-cargo build --release
-```
-The binary is `target/release/toche` on Linux and macOS or
-`target\release\toche.exe` on Windows. Run that binary with the same numbered setup
-steps above.
-</details>
-## How it works
-```mermaid
-flowchart LR
-    A[Claude Code] --> B[Toche on 127.0.0.1:8743]
-    B --> C{Local pipeline}
-    C --> D[Shield and safe cache]
-    C --> E[Output reduction]
-    C --> F[Efficiency and prompt cache]
-    D --> G[Configured Anthropic API endpoint]
-    E --> G
-    F --> G
-    G --> B
-    B --> H[Local ledger and content store]
-    B --> A
-```
-In plain language, Claude Code sends its normal Anthropic Messages API request to
-Toche on `127.0.0.1:8743`. Toche then:
-1. Gives the request a stable fingerprint.
-2. Shares an already-running identical request or checks for an eligible local replay.
-3. Shortens supported tool output and keeps the original locally recoverable.
-4. Applies the selected efficiency and provider prompt-cache policy.
-5. Forwards any remaining work to your configured Anthropic API endpoint.
-6. Records the outcome locally so `toche stats` can explain it.
-The exact internal order is:
-```text
-fingerprint -> shield -> safe cache -> reduce -> efficiency -> cache -> forward -> ledger
-```
-Toche fingerprints the canonical request, checks whether work can be safely shared
-or replayed, reduces known tool-output noise, applies the selected efficiency and
-prompt-cache policy, forwards the resulting request upstream, then records the
-outcome locally.
-For the module map, database schema, cache rules, and content-addressed storage
-layout, see [the architecture guide](docs/ARCHITECTURE.md).
-## Safety and control
-- The gateway binds to `127.0.0.1:8743` by default.
-- Toche configuration, its ledger, cache metadata, checkpoints, and stored content live locally.
-- Requests that require upstream work still go to the Anthropic API endpoint configured in your profile.
-- Persistent replay is limited to eligible responses. Responses containing `tool_use` blocks are rejected.
-- `toche doctor` reports configuration and integration health.
-- Every optimization stage has an explicit bypass header.
-- `toche expand <hash>` restores original tool output after reduction.
-- Cache entries can be inspected, explained, and cleared.
-- `toche disconnect` restores direct Claude Code routing.
-These controls make Toche inspectable and reversible. They are not a promise that
-every request will be cheaper or that an optimization can never affect model behavior.
-## Command reference
-<details>
-<summary><strong>Gateway, setup, and diagnostics</strong></summary>
-| Command | What it does |
-|---|---|
-| `toche` | Start the gateway on `127.0.0.1:8743` |
-| `toche setup` | Generate `profiles.toml` from Claude Code configuration |
-| `toche setup --force` | Regenerate the profile and back up the existing file |
-| `toche connect` | Route Claude Code through Toche |
-| `toche disconnect` | Restore direct upstream routing |
-| `toche doctor` | Show configuration and integration health |
-| `toche status` | Show gateway status |
-</details>
-<details>
-<summary><strong>Usage, reduction, and persistent cache</strong></summary>
-| Command | What it does |
-|---|---|
-| `toche stats` | Show a human-readable usage and cost breakdown |
-| `toche stats --json` | Print machine-readable statistics |
-| `toche stats --entries 100` | Include the last 100 ledger entries |
-| `toche expand <hash>` | Restore original tool output from a reduction hash |
-| `toche cache inspect` | List persistent safe-cache entries |
-| `toche cache clear` | Clear entries for the current project |
-| `toche cache clear --all` | Clear all persistent cache entries |
-| `toche cache why <fingerprint>` | Explain the cache decision for a fingerprint |
-</details>
-<details>
-<summary><strong>Continuity and project graph</strong></summary>
-| Command | What it does |
-|---|---|
-| `toche checkpoint save` | Save a session checkpoint |
-| `toche checkpoint list` | List saved checkpoints |
-| `toche checkpoint show` | Show the latest checkpoint |
-| `toche checkpoint delete <id>` | Delete a checkpoint |
-| `toche graph query <question>` | Query the optional knowledge graph |
-| `toche graph status` | Show graph node and edge counts |
-| `toche graph extract` | Rebuild the knowledge graph |
-</details>
-### Per-request bypasses
-Set a header to `true`, case-insensitively, to skip a stage for one request.
-The umbrella bypass takes precedence over individual bypasses.
-| Header | Skips |
-|---|---|
-| `x-toche-bypass` | The complete optimization pipeline |
-| `x-toche-bypass-shield` | Request coalescing |
-| `x-toche-bypass-safe-cache` | Persistent cache lookup and storage |
-| `x-toche-bypass-reduce` | Tool-output reduction |
-| `x-toche-bypass-efficiency` | Efficiency instruction injection |
-| `x-toche-bypass-cache` | Provider prompt-cache injection |
-## Configuration
-Profiles live in `~/.toche/profiles.toml`. Running `toche setup` generates a
-profile from your existing Claude Code configuration.
-<details>
-<summary><strong>Example profile</strong></summary>
-```toml
-default = "default"
-[[profiles]]
-name = "default"
-upstream_url = "https://api.anthropic.com"
-auth_method = { type = "api_key", header_name = "x-api-key", key = "YOUR_ANTHROPIC_API_KEY" }
-[profiles.cache]
-enabled = true
-mode = "auto"
-breakpoint = "standard"
-[profiles.reduce]
-enabled = true
-[profiles.efficiency]
-mode = "concise"
-[profiles.safe_cache]
-enabled = true
-ttl_days = 30
-max_entry_bytes = 1048576
-[profiles.graphify]
-enabled = false
-```
-</details>
-Set `TOCHE_CONFIG_DIR` to override the default `~/.toche/` directory.
-## Troubleshooting
-<details>
-<summary><strong>The gateway will not start</strong></summary>
-- Check that nothing else is listening on port 8743.
-- Run `toche doctor` to verify that `profiles.toml` exists and is valid.
-- Enable debug logging with `RUST_LOG=toche=debug toche`.
-</details>
-<details>
-<summary><strong>Claude Code cannot connect</strong></summary>
-- Start the gateway before running `toche connect`.
-- Run `toche doctor` in a second terminal after connecting.
-</details>
-<details>
-<summary><strong>Stats or cache entries are empty</strong></summary>
-- The ledger records only requests routed through the gateway.
-- The persistent cache stores only eligible text-only responses without `tool_use` blocks.
-- Use `toche cache why <fingerprint>` to inspect a cache rejection.
-</details>
-<details>
-<summary><strong>Routing still points to Toche after disconnecting</strong></summary>
-Run `toche doctor`. If `env.ANTHROPIC_BASE_URL` still points to Toche while the
-gateway is stopped, inspect `~/.claude/settings.json` and its Toche backup.
-</details>
-## Requirements
-- Rust 1.86 or newer, edition 2024
-- Claude Code or another Anthropic Messages API client
-- No hosted Toche service
-- SQLite is bundled through `rusqlite`
-## Documentation
-- [Architecture](docs/ARCHITECTURE.md): pipeline, modules, databases, and storage
-- [Changelog](CHANGELOG.md): release history from 0.1.0 through 1.0.10
-- [Bug tracker](docs/BUG_TRACKER.md): issues found and fixed during dogfooding
-- [npm publishing](docs/NPM_PUBLISHING.md): maintainer checklist for the first npm release
-- [Third-party notices](THIRD_PARTY_NOTICES.md): reused ideas, integration decisions, and attribution
-## Built from good work
-Toche's Rust implementation was informed by ideas and patterns from ccusage, RTK,
-Graphify, andrej-karpathy-skills, and caveman-claude. Their licenses and attribution
-are preserved in [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md).
-## License
-Licensed under the [Apache License 2.0](LICENSE).
+<p align="center">
+  <img src="assets/branding/toche-wordmark.png" alt="Toche" width="620">
+</p>
+<p align="center">
+  <strong>One local runtime. Multiple AI clients. Every request leaves a receipt.</strong>
+</p>
+<p align="center">
+  Toche is a local multi-client gateway that sits between your AI coding tools and
+  their upstream API endpoints. It removes avoidable work, isolates trust boundaries,
+  and keeps every optimization visible and reversible.
+</p>
+<p align="center">
+  <img src="assets/branding/toche-status.svg" alt="Toche 1.1.0: Multi-client runtime, Claude Code and Codex, 65 filters, duplicate requests coalesced from many to one, zero hosted accounts" width="820">
+</p>
+<p align="center">
+  <a href="#what-toche-is">What Toche is</a> ·
+  <a href="#what-toche-is-not">What it is not</a> ·
+  <a href="#install">Install</a> ·
+  <a href="#how-it-works">How it works</a> ·
+  <a href="#supported-clients">Supported clients</a> ·
+  <a href="#command-reference">Commands</a> ·
+  <a href="#trust-and-isolation">Trust and isolation</a> ·
+  <a href="#documentation">Docs</a>
+</p>
+## What Toche is
+Toche is a local runtime that accepts connections from multiple AI coding clients
+simultaneously and routes their requests to your configured upstream API endpoints.
+While a request passes through, Toche can:
+- **Coalesce identical in-flight requests** so N clients sharing the same upstream
+  and trust domain make one upstream call instead of N.
+- **Replay eligible responses** from a persistent cross-session cache when the
+  workspace fingerprint matches.
+- **Reduce known tool-output noise** with 65 built-in TOML-defined filters
+  while keeping the original content recoverable with `toche expand`.
+- **Inject provider prompt-cache breakpoints** to maximize Anthropic cache hits.
+- **Record every request** in a local SQLite ledger so `toche stats` can explain
+  what happened.
+Toche does not host an account, send telemetry, or require a cloud service.
+## What Toche is not
+Toche is not a provider account manager, a model load balancer, a protocol
+translator, or a hosted API gateway. It does not select providers automatically
+or fall back between them. It does not translate between Anthropic and OpenAI
+protocols. These are explicit non-goals for the 1.1.0 release.
+## Install
+### Prerequisites
+- Node.js 18 or newer for the npm installer.
+- At least one supported AI coding client already installed and working.
+- Windows x64, Linux x64, macOS Intel, or macOS Apple silicon.
+Rust is not required when installing from npm.
+### One-time setup
+```shell
+npm install -g @nzkbuild/toche
+toche setup
+toche
+```
+Then, in other terminals, run your clients normally:
+```shell
+claude
+codex
+```
+`toche setup` detects your existing client configurations, imports your current
+upstreams, and writes a local `config.toml`. It never silently sends a paid model
+request. You can run it again later to review or modify your configuration.
+### Managed mode (optional convenience)
+Instead of starting the runtime separately, you can launch a client through Toche
+in one step:
+```shell
+toche run claude -- --dangerously-skip-permissions
+toche run codex
+```
+Managed mode uses the same runtime, configuration, protocol handling, trust
+isolation, ledger, and optimization pipeline as persistent mode.
+### Normal daily use
+After setup, the routine is:
+1. Run `toche` and leave it open.
+2. Run your clients in other terminals.
+### Clean uninstall
+```shell
+toche disconnect claude
+toche disconnect codex
+npm uninstall -g @nzkbuild/toche
+```
+<details>
+<summary><strong>Build from source instead of npm</strong></summary>
+You need Rust 1.86 or newer.
+```shell
+git clone https://github.com/nzkbuild/toche.git
+cd toche
+cargo build --release
+```
+The binary is `target/release/toche` (`.exe` on Windows).
+</details>
+## How it works
+```mermaid
+flowchart LR
+    subgraph Clients
+        A[Claude Code]
+        B[Codex CLI]
+    end
+    A --> C[Toche on 127.0.0.1:8743]
+    B --> C
+    C --> D{Protocol router}
+    D --> E[Anthropic Messages pipeline]
+    D --> F[OpenAI Responses pipeline]
+    E --> G[Shield coalescing]
+    F --> G
+    G --> H[Safe cache]
+    H --> I[Output reduction]
+    I --> J[Efficiency injection]
+    J --> K[Prompt cache injection]
+    K --> L[Configured upstream APIs]
+    L --> C
+    C --> M[Local ledger and CAS]
+    C --> A
+    C --> B
+```
+In plain language, your AI clients send their normal API requests to Toche on
+`127.0.0.1:8743`. Toche then:
+1. Routes the request through the correct protocol driver (Anthropic Messages
+   or OpenAI Responses).
+2. Gives the request a stable fingerprint.
+3. Shares an already-running identical request (within the same trust domain)
+   or checks for an eligible local replay.
+4. Shortens supported tool output and keeps the original locally recoverable.
+5. Applies the selected efficiency and provider prompt-cache policy.
+6. Forwards any remaining work to your configured upstream API endpoint.
+7. Records the outcome locally so `toche stats` can explain it.
+The internal pipeline order is:
+```text
+protocol dispatch → fingerprint → shield → safe cache → reduce → efficiency → cache → forward → ledger
+```
+## Supported clients
+| Client | Protocol | Persistent mode | Managed mode | Setup |
+|--------|----------|-----------------|--------------|-------|
+| Claude Code | Anthropic Messages | `toche` + `claude` | `toche run claude` | `toche setup` |
+| Codex CLI | OpenAI Responses | `toche` + `codex` | `toche run codex` | `toche setup` |
+Multiple instances of the same client are supported. Claude Code and Codex can
+run simultaneously through the same Toche runtime.
+### Persistent vs. managed mode
+**Persistent mode** (`toche` in one terminal, client in another) is the primary
+workflow. Start Toche once and launch as many clients as you need.
+**Managed mode** (`toche run <client>`) is a convenience that starts Toche and
+the client together. It uses the exact same pipeline as persistent mode.
+## Trust and isolation
+Different credential references never share cache entries or in-flight request
+coalescing. If you configure a personal Anthropic API key and a work OpenAI key,
+their traffic is isolated by trust domain — even if they happen to target the
+same upstream URL.
+Trust domains are derived from the combination of integration identity, upstream
+identity, and credential reference. Raw credential values are never placed in
+logs, IDs, hashes, database diagnostics, or receipts.
+Attribution confidence is recorded honestly: Toche distinguishes between exact
+process identity, client-reported identity, workspace-level identity, inference,
+and unknown identity. It does not fabricate identity where it cannot be observed.
+## Data storage
+Everything lives in `~/.toche/` (overridable with `TOCHE_CONFIG_DIR`):
+| Path | Purpose |
+|------|---------|
+| `config.toml` | Runtime configuration, integrations, upstreams, policies |
+| `ledger.db` | SQLite ledger of every routed request |
+| `cas/` | Content-addressed storage for reduced originals and cached responses |
+| `runtime_id` | Persistent UUIDv7 runtime identity |
+Toche never sends your data to a cloud account.
+## Measurement confidence
+Every value reported by `toche stats` is classified by how it was obtained:
+| Confidence | Meaning |
+|------------|---------|
+| `measured` | Toche observed it directly |
+| `provider-reported` | The upstream API reported it |
+| `estimated` | Derived from available data (e.g. list-price estimate) |
+| `configured` | Comes from your configuration |
+| `unknown` | Could not be determined |
+Missing prices do not become zero. Missing usage does not become fabricated
+usage. Cost estimates are labelled as equivalent public list-price estimates,
+not your actual billed cost.
+## Command reference
+### Primary commands
+| Command | What it does |
+|---------|-------------|
+| `toche` | Start the runtime on `127.0.0.1:8743` |
+| `toche setup` | Guided, rerunnable configuration |
+| `toche setup --dry-run` | Preview changes without writing |
+| `toche setup --force` | Regenerate configuration (backup created) |
+| `toche connect [client]` | Route a client through Toche |
+| `toche disconnect [client]` | Restore direct upstream routing |
+| `toche run <client>` | Run a client in managed mode |
+| `toche doctor` | Verify installation and configuration |
+| `toche status` | Show runtime status, active flights, protocol counts |
+| `toche status --json` | Machine-readable status |
+| `toche stats` | Show usage, tokens, and cost estimates |
+| `toche stats --json` | Machine-readable statistics |
+| `toche stats --protocol anthropic` | Filter by protocol |
+| `toche stats --integration <name>` | Filter by integration |
+| `toche expand <hash>` | Restore original tool output from a reduction hash |
+### Advanced commands
+| Command | What it does |
+|---------|-------------|
+| `toche cache inspect` | List persistent safe-cache entries |
+| `toche cache clear` | Clear entries for the current project |
+| `toche cache clear --all` | Clear all persistent cache entries |
+| `toche cache why <fingerprint>` | Explain the cache decision for a fingerprint |
+| `toche checkpoint save` | Save a session checkpoint |
+| `toche checkpoint list` | List saved checkpoints |
+| `toche checkpoint show` | Show the latest checkpoint |
+| `toche checkpoint delete <id>` | Delete a checkpoint |
+| `toche graph query <question>` | Query the optional knowledge graph |
+| `toche graph status` | Show graph node and edge counts |
+| `toche graph extract` | Rebuild the knowledge graph |
+### Per-request bypass headers
+Set a header to `true` (case-insensitive) to skip a stage for one request.
+The umbrella bypass takes precedence over individual bypasses.
+| Header | Skips |
+|--------|-------|
+| `x-toche-bypass` | The complete optimization pipeline |
+| `x-toche-bypass-shield` | Request coalescing |
+| `x-toche-bypass-safe-cache` | Persistent cache lookup and storage |
+| `x-toche-bypass-reduce` | Tool-output reduction |
+| `x-toche-bypass-efficiency` | Efficiency instruction injection |
+| `x-toche-bypass-cache` | Provider prompt-cache injection |
+## Configuration
+Toche stores its configuration in `~/.toche/config.toml`. Running `toche setup`
+generates it from your existing client configurations.
+<details>
+<summary><strong>Example config.toml</strong></summary>
+```toml
+schema_version = 2
+[runtime]
+port = 8743
+listen_address = "127.0.0.1"
+request_timeout_ms = 300000
+[defaults]
+integration = "abc12345"
+[[integrations]]
+id = "abc12345"
+name = "default"
+upstream = "def67890"
+policy = "pol11111"
+[[upstreams]]
+id = "def67890"
+name = "Anthropic"
+url = "https://api.anthropic.com"
+[upstreams.auth]
+secret_ref = { type = "environment", key = "ANTHROPIC_API_KEY" }
+header_name = "x-api-key"
+[upstreams.headers]
+anthropic-version = "2023-06-01"
+[[policies]]
+id = "pol11111"
+name = "default"
+[policies.cache]
+enabled = true
+mode = "auto"
+breakpoint = "standard"
+[policies.reduce]
+enabled = true
+[policies.efficiency]
+mode = "concise"
+[policies.safe_cache]
+enabled = true
+ttl_days = 30
+max_entry_bytes = 1048576
+```
+</details>
+## Troubleshooting
+<details>
+<summary><strong>The runtime will not start</strong></summary>
+- Check that nothing else is listening on port 8743.
+- Run `toche doctor` to verify that `config.toml` exists and is valid.
+- Enable debug logging with `RUST_LOG=toche=debug toche`.
+</details>
+<details>
+<summary><strong>A client cannot connect</strong></summary>
+- Start the runtime before running `toche connect`.
+- Run `toche doctor` in a second terminal after connecting.
+- Check that `toche status` shows the expected integrations.
+</details>
+<details>
+<summary><strong>Stats or cache entries are empty</strong></summary>
+- The ledger records only requests routed through the runtime.
+- The persistent cache stores only eligible text-only responses without `tool_use` blocks.
+- Use `toche cache why <fingerprint>` to inspect a cache rejection.
+</details>
+<details>
+<summary><strong>Routing still points to Toche after disconnecting</strong></summary>
+Run `toche doctor`. If environment variables or settings still reference Toche
+while the runtime is stopped, run `toche disconnect` for each affected client.
+</details>
+## Upgrading from 1.0.x
+Toche 1.1.0 migrates your existing `profiles.toml` to the new `config.toml`
+format automatically on first load. The migration:
+- Converts each profile into separate Integration, Upstream, and Policy entries.
+- Backs up `profiles.toml` to `profiles.toml.v1.bak`.
+- Preserves your ledger, safe-cache metadata, CAS, checkpoints, and Graphify data.
+- Is idempotent — running it again is a no-op.
+- Fails safely on malformed configuration without modifying anything.
+An older binary encountering a newer schema version will refuse to modify it.
+## Requirements
+- Rust 1.86 or newer (edition 2024) when building from source
+- At least one supported AI coding client
+- No hosted Toche service
+- SQLite is bundled through `rusqlite`
+## Documentation
+- [Architecture](docs/ARCHITECTURE.md): system design, crate map, data flow, decision records
+- [Changelog](CHANGELOG.md): release history from 1.0.0 through 1.1.0
+- [Contributing](CONTRIBUTING.md): setup, conventions, and PR workflow
+- [Code of Conduct](CODE_OF_CONDUCT.md): Contributor Covenant
+- [Bug tracker](docs/BUG_TRACKER.md): issues found and fixed during dogfooding
+- [npm publishing](docs/NPM_PUBLISHING.md): maintainer checklist for npm releases
+- [Third-party notices](THIRD_PARTY_NOTICES.md): reused ideas, integration decisions, and attribution
+## Built from good work
+Toche's Rust implementation was informed by ideas and patterns from ccusage, RTK,
+Graphify, andrej-karpathy-skills, and caveman-claude. Their licenses and attribution
+are preserved in [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md).
+## License
+Licensed under the [Apache License 2.0](LICENSE).

package/THIRD_PARTY_NOTICES.md CHANGED Viewed

@@ -11,7 +11,7 @@ copyright notices, project links, and integration decisions are preserved here.
 | Project | License | Clone commit | Integration | Purpose |
 |---------|---------|-------------|-------------|---------|
 | [ccusage](https://github.com/ccusage/ccusage) | MIT | `ba99c0d` | Reference: adapt pricing/reporting patterns | Usage ledger concepts, pricing models, reporting |
-| [RTK](https://github.com/rtk-ai/rtk) | Apache-2.0 | `5d32d07` | Reference: adapt filter and hook architecture | Command/tool-output reduction, Claude Code hook integration |
+| [RTK](https://github.com/rtk-ai/rtk) | Apache-2.0 | `5d32d0736f686b69d1e8b9dc45c007d4eb77a0a2` | Reference: adapt filter and hook architecture | Command/tool-output reduction, Claude Code hook integration |
 | [Graphify](https://github.com/Graphify-Labs/graphify) | MIT | `43b2aff` | External CLI/MCP adapter | Local project graph and query service |
 | [andrej-karpathy-skills](https://github.com/multica-ai/andrej-karpathy-skills) | MIT | `2c60614` | Reference: adapt policy rules | Careful-work policy profile (Section 0.6.0) |
 | [caveman-claude](https://github.com/juliusbrussee/caveman) | MIT | `0d95a81` | Reference: adapt concision patterns | Concise response profile, token reduction strategies |

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@nzkbuild/toche",
-  "version": "1.0.10",
+  "version": "1.1.0",
   "description": "Local efficiency gateway for Claude Code",
   "license": "Apache-2.0",
   "repository": {