hermes-context-tuner 0.2.0b1__tar.gz

hermes_context_tuner-0.2.0b1/.github/workflows/tests.yml

@@ -0,0 +1,22 @@
+name: tests
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ['3.10', '3.11', '3.12']
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: python -m pip install --upgrade pip build pytest
+      - run: python -m pip install -e .
+      - run: PYTHONPATH=src python -m pytest tests -q -o 'addopts='
+      - run: python -m build

hermes_context_tuner-0.2.0b1/.gitignore

@@ -0,0 +1,9 @@
+__pycache__/
+*.py[cod]
+*.sqlite
+*.db
+.venv/
+build/
+dist/
+*.egg-info/
+.pytest_cache/

hermes_context_tuner-0.2.0b1/CONTRIBUTING.md

@@ -0,0 +1,37 @@
+# Contributing
+
+Thanks for helping improve Hermes Context Tuner.
+
+## Development setup
+
+```bash
+git clone https://github.com/tier4research/hermes-context-tuner.git
+cd hermes-context-tuner
+python -m pip install -e .
+PYTHONPATH=src python -m pytest tests -q -o 'addopts='
+```
+
+## Design principles
+
+1. **Do not fork Hermes compression.** Delegate to Hermes' built-in compressor unless there is a very explicit reason not to.
+2. **Do not monkey-patch Hermes private methods.** Use the `ContextEngine` seam.
+3. **Audit must never block compression.** Recovery/audit sidecar writes are best-effort.
+4. **Store metadata, not raw transcript content.** Raw session data belongs to Hermes `state.db`.
+5. **Prefer upgrade resilience over cleverness.** A small shim that can be reinstalled after updates is better than a broad core patch.
+
+## Tests
+
+```bash
+PYTHONPATH=src python -m pytest tests -q -o 'addopts='
+python -m build
+```
+
+## Commit style
+
+Use short conventional-ish messages:
+
+```text
+feat: add recovery pointer listing
+fix: keep audit failures non-blocking
+docs: clarify Hermes integration
+```

hermes_context_tuner-0.2.0b1/LICENSE

@@ -0,0 +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 [yyyy] [name of copyright owner]
+
+   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.

hermes_context_tuner-0.2.0b1/PKG-INFO

@@ -0,0 +1,163 @@
+Metadata-Version: 2.4
+Name: hermes-context-tuner
+Version: 0.2.0b1
+Summary: Audit trail and token-budget planning for LLM context compression. See what your agent summarized away and where to find it.
+Project-URL: Homepage, https://github.com/tier4research/hermes-context-tuner
+Project-URL: Documentation, https://github.com/tier4research/hermes-context-tuner#readme
+Project-URL: Source, https://github.com/tier4research/hermes-context-tuner
+Project-URL: Changelog, https://github.com/tier4research/hermes-context-tuner/blob/main/RELEASE_NOTES.md
+Project-URL: Issues, https://github.com/tier4research/hermes-context-tuner/issues
+Author-email: Tier 4 Research <mjohnson@novacoresystems.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agent-tools,ai-agents,audit-log,context-compression,context-management,context-window,hermes-agent,llm,observability,python,sqlite,token-budget
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+
+# Hermes Context Tuner
+
+[![Tests](https://github.com/tier4research/hermes-context-tuner/actions/workflows/tests.yml/badge.svg)](https://github.com/tier4research/hermes-context-tuner/actions/workflows/tests.yml)
+[![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)
+[![Status: Beta](https://img.shields.io/badge/status-beta-green.svg)](RELEASE_NOTES.md)
+
+**Know what your agent's compressor threw away.**
+
+[Hermes Agent](https://hermes-agent.nousresearch.com) is an open-source agent framework. Like every long-running agent, it compresses session history when context gets tight — and like every compressor, it sometimes summarizes away the wrong thing. A key instruction, a project spec, a user preference. Then the agent starts answering confidently wrong, and you have no record of what was dropped.
+
+Context Tuner doesn't replace that compressor. It wraps it and writes down what it did: which messages were kept raw, which were summarized, which were flagged as oversized tool output, and which session each compressed segment came from. Then it exposes that history to you *and to the agent itself*, so the agent can check its own context hygiene mid-run.
+
+```bash
+pip install hermes-context-tuner
+hermes-context-tuner install-hermes --set-config
+hermes gateway restart
+```
+
+Then, inside any session:
+
+```
+/context-tuner
+
+Hermes Context Tuner recent compression events:
+- #1 messages 120 -> 24; ~182000 tokens; externalize_hint=8, keep_raw=12, summarize=100
+```
+
+---
+
+## What "recovery" means here — and what it doesn't
+
+Context Tuner's sidecar stores metadata and pointers, not message text. For each compression event it records the counts, the token estimates, the per-message decision, and the source session ID.
+
+So it can tell you that messages 40–90 were summarized in session `abc123`, and it can point you at that session. It does **not** restore the original text into your context automatically, and it is **not** a backup of your conversation. If you need the raw messages, you go read the session log — Context Tuner tells you which one and which range.
+
+That's a narrower promise than "recoverable memory," and it's the one the tool actually keeps. The audit trail is the product; the pointers are a convenience on top of it.
+
+---
+
+## What it adds
+
+**A budget plan you can inspect before compression happens.** Protect the first N messages, protect the last M tokens, mark large tool outputs for externalization, flag the middle for summarization. The plan is advisory — it shows what would happen before it does.
+
+**An audit trail.** Every compression event lands in a SQLite sidecar with per-message decisions and reasons. Writes are best-effort: if the audit DB fails, compression still succeeds. Observability never blocks the agent.
+
+**Something the agent can operate itself.** The `context_tuner_status` tool and the `/context-tuner` command let the agent inspect its own compression history. The bundled `optimize-context` skill gives it a procedure: audit → compress targeted → verify → hand off. No external dashboard.
+
+**No monkey-patching.** Context Tuner attaches through Hermes' official `ContextEngine` interface and introspects the live compressor's constructor at runtime, passing only the kwargs it supports. A Hermes upgrade that changes that signature doesn't break you; one that removes the shim needs a single reinstall command.
+
+---
+
+## Upgrade resilience
+
+| Risk | Mitigation |
+|------|------------|
+| Hermes update changes compressor constructor | Introspects live signature, passes only supported kwargs |
+| Hermes update changes compression internals | Delegates through public `compress()` contract |
+| Hermes update removes shim | Rerun `hermes-context-tuner install-hermes --set-config` |
+| Audit DB failure | Compression succeeds; audit is best-effort |
+| ContextEngine API breaks | Failure at import/startup — explicit, not silent |
+
+---
+
+## How it works
+
+```
+┌─────────────────────────────────────────────────────┐
+│                  Context Tuner                       │
+│  ┌──────────────┐  ┌──────────────┐  ┌───────────┐  │
+│  │ Budget Plan  │  │ Compression  │  │ Recovery  │  │
+│  │ (advisory)   │──▶│  (delegated  │──▶│  Store    │  │
+│  │              │  │   to Hermes) │  │  (audit)  │  │
+│  └──────────────┘  └──────────────┘  └───────────┘  │
+│                              │                       │
+│                              ▼                       │
+│                     ┌──────────────┐                 │
+│                     │ Status Tool  │                 │
+│                     │ /command     │                 │
+│                     └──────────────┘                 │
+└─────────────────────────────────────────────────────┘
+```
+
+1. Build an advisory `BudgetPlan` — protected head + tail, summarize middle, externalize large tool outputs
+2. Delegate actual compression to Hermes' built-in `ContextCompressor`
+3. Record decisions in the recovery sidecar (best-effort, never blocks compression)
+4. Expose status via `/context-tuner` command and `context_tuner_status` tool
+
+---
+
+## Developer use
+
+```python
+from hermes_context_tuner.engine import ContextTunerEngine
+
+engine = ContextTunerEngine()
+engine.on_session_start(session_id="example")
+
+if engine.should_compress(prompt_tokens):
+    messages = engine.compress(messages, current_tokens=prompt_tokens)
+
+print(engine.get_status())
+```
+
+---
+
+## Status
+
+**Beta** (v0.2.0-beta.1). Budget planning, the audit trail, status commands, and the Hermes integration are working and tested. Recovery is currently pointer-level only. Tested against Hermes v0.4.x — a CI matrix across versions is planned, so compatibility with other releases is unverified. 7 commits, 0 external stars.
+
+---
+
+## FAQ
+
+### What is Hermes Context Tuner?
+Hermes Context Tuner is a Python library that wraps an agent's context compressor and records what it did: which messages were kept raw, which were summarized, and which session each compressed segment came from. It provides an audit trail, a token-budget planner, and a status tool the agent can call itself.
+
+### Does Context Tuner replace the built-in compressor?
+No. It delegates compression to the agent's native `ContextCompressor`. What it adds is observability: a budget plan you inspect beforehand, an audit trail afterward, and recovery pointers to the original session logs.
+
+### Can Context Tuner recover compressed messages?
+It provides pointers — session ID and message range — not the raw text. If you need the original messages, you read the session log that Context Tuner points to.
+
+### Does it break when Hermes updates?
+This is explicitly designed not to. Context Tuner introspects the live compressor's constructor at runtime and passes only the kwargs it supports. If a Hermes update changes the interface, the tool fails at import/startup rather than silently corrupting the session.
+
+### Does it work with agents other than Hermes?
+Not currently. The integration is through Hermes' `ContextEngine` interface. A generic `ContextTunerEngine` core is feasible — the audit trail, budget planner, and recovery store are agent-agnostic — but the adapter layer is Hermes-specific today.
+
+### What's the relationship with Memorant?
+[Memorant](https://github.com/tier4research/memorant) is a separate project for *long-term* agent memory: claims with provenance, trust tiers, and atomic corrections in a single SQLite file. Context Tuner handles *short-term* working context compression. [Expectation Ledger](https://github.com/tier4research/expectation-ledger) is a circuit breaker for agent control loops — predict, compare, and self-block on divergence. All three are designed to complement each other — see the [Memorant suite workflow](https://github.com/tier4research/memorant#suite-workflow).
+
+---
+
+## License
+
+Apache License 2.0.

hermes_context_tuner-0.2.0b1/README.md

@@ -0,0 +1,137 @@
+# Hermes Context Tuner
+
+[![Tests](https://github.com/tier4research/hermes-context-tuner/actions/workflows/tests.yml/badge.svg)](https://github.com/tier4research/hermes-context-tuner/actions/workflows/tests.yml)
+[![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)
+[![Status: Beta](https://img.shields.io/badge/status-beta-green.svg)](RELEASE_NOTES.md)
+
+**Know what your agent's compressor threw away.**
+
+[Hermes Agent](https://hermes-agent.nousresearch.com) is an open-source agent framework. Like every long-running agent, it compresses session history when context gets tight — and like every compressor, it sometimes summarizes away the wrong thing. A key instruction, a project spec, a user preference. Then the agent starts answering confidently wrong, and you have no record of what was dropped.
+
+Context Tuner doesn't replace that compressor. It wraps it and writes down what it did: which messages were kept raw, which were summarized, which were flagged as oversized tool output, and which session each compressed segment came from. Then it exposes that history to you *and to the agent itself*, so the agent can check its own context hygiene mid-run.
+
+```bash
+pip install hermes-context-tuner
+hermes-context-tuner install-hermes --set-config
+hermes gateway restart
+```
+
+Then, inside any session:
+
+```
+/context-tuner
+
+Hermes Context Tuner recent compression events:
+- #1 messages 120 -> 24; ~182000 tokens; externalize_hint=8, keep_raw=12, summarize=100
+```
+
+---
+
+## What "recovery" means here — and what it doesn't
+
+Context Tuner's sidecar stores metadata and pointers, not message text. For each compression event it records the counts, the token estimates, the per-message decision, and the source session ID.
+
+So it can tell you that messages 40–90 were summarized in session `abc123`, and it can point you at that session. It does **not** restore the original text into your context automatically, and it is **not** a backup of your conversation. If you need the raw messages, you go read the session log — Context Tuner tells you which one and which range.
+
+That's a narrower promise than "recoverable memory," and it's the one the tool actually keeps. The audit trail is the product; the pointers are a convenience on top of it.
+
+---
+
+## What it adds
+
+**A budget plan you can inspect before compression happens.** Protect the first N messages, protect the last M tokens, mark large tool outputs for externalization, flag the middle for summarization. The plan is advisory — it shows what would happen before it does.
+
+**An audit trail.** Every compression event lands in a SQLite sidecar with per-message decisions and reasons. Writes are best-effort: if the audit DB fails, compression still succeeds. Observability never blocks the agent.
+
+**Something the agent can operate itself.** The `context_tuner_status` tool and the `/context-tuner` command let the agent inspect its own compression history. The bundled `optimize-context` skill gives it a procedure: audit → compress targeted → verify → hand off. No external dashboard.
+
+**No monkey-patching.** Context Tuner attaches through Hermes' official `ContextEngine` interface and introspects the live compressor's constructor at runtime, passing only the kwargs it supports. A Hermes upgrade that changes that signature doesn't break you; one that removes the shim needs a single reinstall command.
+
+---
+
+## Upgrade resilience
+
+| Risk | Mitigation |
+|------|------------|
+| Hermes update changes compressor constructor | Introspects live signature, passes only supported kwargs |
+| Hermes update changes compression internals | Delegates through public `compress()` contract |
+| Hermes update removes shim | Rerun `hermes-context-tuner install-hermes --set-config` |
+| Audit DB failure | Compression succeeds; audit is best-effort |
+| ContextEngine API breaks | Failure at import/startup — explicit, not silent |
+
+---
+
+## How it works
+
+```
+┌─────────────────────────────────────────────────────┐
+│                  Context Tuner                       │
+│  ┌──────────────┐  ┌──────────────┐  ┌───────────┐  │
+│  │ Budget Plan  │  │ Compression  │  │ Recovery  │  │
+│  │ (advisory)   │──▶│  (delegated  │──▶│  Store    │  │
+│  │              │  │   to Hermes) │  │  (audit)  │  │
+│  └──────────────┘  └──────────────┘  └───────────┘  │
+│                              │                       │
+│                              ▼                       │
+│                     ┌──────────────┐                 │
+│                     │ Status Tool  │                 │
+│                     │ /command     │                 │
+│                     └──────────────┘                 │
+└─────────────────────────────────────────────────────┘
+```
+
+1. Build an advisory `BudgetPlan` — protected head + tail, summarize middle, externalize large tool outputs
+2. Delegate actual compression to Hermes' built-in `ContextCompressor`
+3. Record decisions in the recovery sidecar (best-effort, never blocks compression)
+4. Expose status via `/context-tuner` command and `context_tuner_status` tool
+
+---
+
+## Developer use
+
+```python
+from hermes_context_tuner.engine import ContextTunerEngine
+
+engine = ContextTunerEngine()
+engine.on_session_start(session_id="example")
+
+if engine.should_compress(prompt_tokens):
+    messages = engine.compress(messages, current_tokens=prompt_tokens)
+
+print(engine.get_status())
+```
+
+---
+
+## Status
+
+**Beta** (v0.2.0-beta.1). Budget planning, the audit trail, status commands, and the Hermes integration are working and tested. Recovery is currently pointer-level only. Tested against Hermes v0.4.x — a CI matrix across versions is planned, so compatibility with other releases is unverified. 7 commits, 0 external stars.
+
+---
+
+## FAQ
+
+### What is Hermes Context Tuner?
+Hermes Context Tuner is a Python library that wraps an agent's context compressor and records what it did: which messages were kept raw, which were summarized, and which session each compressed segment came from. It provides an audit trail, a token-budget planner, and a status tool the agent can call itself.
+
+### Does Context Tuner replace the built-in compressor?
+No. It delegates compression to the agent's native `ContextCompressor`. What it adds is observability: a budget plan you inspect beforehand, an audit trail afterward, and recovery pointers to the original session logs.
+
+### Can Context Tuner recover compressed messages?
+It provides pointers — session ID and message range — not the raw text. If you need the original messages, you read the session log that Context Tuner points to.
+
+### Does it break when Hermes updates?
+This is explicitly designed not to. Context Tuner introspects the live compressor's constructor at runtime and passes only the kwargs it supports. If a Hermes update changes the interface, the tool fails at import/startup rather than silently corrupting the session.
+
+### Does it work with agents other than Hermes?
+Not currently. The integration is through Hermes' `ContextEngine` interface. A generic `ContextTunerEngine` core is feasible — the audit trail, budget planner, and recovery store are agent-agnostic — but the adapter layer is Hermes-specific today.
+
+### What's the relationship with Memorant?
+[Memorant](https://github.com/tier4research/memorant) is a separate project for *long-term* agent memory: claims with provenance, trust tiers, and atomic corrections in a single SQLite file. Context Tuner handles *short-term* working context compression. [Expectation Ledger](https://github.com/tier4research/expectation-ledger) is a circuit breaker for agent control loops — predict, compare, and self-block on divergence. All three are designed to complement each other — see the [Memorant suite workflow](https://github.com/tier4research/memorant#suite-workflow).
+
+---
+
+## License
+
+Apache License 2.0.

hermes_context_tuner-0.2.0b1/RELEASE_NOTES.md

@@ -0,0 +1,49 @@
+# v0.2.0-beta.1
+
+Context compression audit, recovery pointers, and agent-operable context hygiene — stable beta.
+
+## What's new since alpha
+
+- **Sales-forward README.** Rewritten to lead with the problem (invisible compression, no recovery path, blind token pressure) and highlight what makes it different: budget-aware packing plans, compression audit trail, agent-operable commands, and upgrade resilience.
+- **Stability improvements.** Recovery store hardened against SQLite lock contention from concurrent cron sessions. Context engine tool schema aligned with Hermes' `agent_init` contract (no double-wrapped function schemas).
+- **Production data available.** 78 real compression events recorded across daily use, 10,565 recovery pointers — decision distribution: `keep_raw=6789`, `summarize=3592`, `externalize_hint=184`.
+
+## Known limitations
+
+- No CI matrix against multiple Hermes versions yet — currently tested against Hermes main.
+- Externalization hints for large tool outputs are advisory only; actual pruning depends on the Hermes built-in compressor.
+- Recovery pointer store is a sidecar SQLite file, not yet integrated with Hermes' session DB.
+
+---
+
+# v0.1.0-alpha.1
+
+Initial public alpha of Hermes Context Tuner.
+
+## What it is
+
+Hermes Context Tuner is an upgrade-resilient wrapper around Hermes Agent's built-in context compressor. It keeps standard Hermes compression, but adds the operational pieces agents need during long sessions:
+
+- budget-aware context pack plans
+- compression/recovery audit metadata
+- `context_tuner_status` context-engine tool
+- `/context-tuner` command
+- `optimize-context` skill example
+- reinstallable Hermes context-engine shim
+
+## Included
+
+- `hermes_context_tuner.budget` advisory budget-plan library
+- `RecoveryPointerStore` SQLite sidecar for compression audit/recovery metadata
+- `ContextTunerEngine`, an official Hermes `ContextEngine` wrapper that delegates to the live built-in compressor
+- `hermes-context-tuner install-hermes --set-config` installer for the Hermes context-engine shim
+- `examples/skills/optimize-context/SKILL.md`
+- integration and architecture docs
+
+## Upgrade posture
+
+The package does not patch Hermes core or monkey-patch private methods. It uses the official context-engine seam and can be reinstalled after Hermes updates by rerunning:
+
+```bash
+hermes-context-tuner install-hermes --set-config
+```

hermes_context_tuner-0.2.0b1/SECURITY.md

@@ -0,0 +1,42 @@
+# Security Policy
+
+Hermes Context Tuner is a local Hermes Agent context-engine wrapper. It does not make network calls and does not execute tools by itself.
+
+## Data handling
+
+Context Tuner writes audit/recovery metadata to:
+
+```text
+~/.hermes/context_tuner/recovery.sqlite
+```
+
+The sidecar database records metadata such as:
+
+- session IDs
+- message counts
+- rough token estimates
+- budget-plan decisions
+
+It should not store raw message contents, API keys, tokens, passwords, or tool outputs.
+
+## Reporting issues
+
+For public issues, avoid posting:
+
+- API keys
+- auth tokens
+- private `config.yaml` or `.env` content
+- raw transcripts containing sensitive data
+
+Open a GitHub issue with a sanitized reproduction, Hermes version, Context Tuner version, and the relevant traceback.
+
+## Threat model
+
+This package is designed to be low-risk:
+
+- no network calls
+- no shell execution except the explicit installer command
+- no raw transcript storage
+- audit writes are best-effort and non-blocking
+
+The main security risk is accidental leakage through bug reports or logs. Sanitize before sharing.