fix(packaging): add hermes_cli.* to setuptools include so proxy subpa…

[LifeJiggy]

fix/proxy-wheel-missing → fixes #27938

fix(packaging): add hermes_cli.* to setuptools include so proxy subpackage ships in wheel

After compression, last_prompt_tokens was set to estimate_request_tokens_rough() which overcounts by 30-50% for tool-heavy sessions (tool schemas counted twice). This inflated value caused should_compress() to return True on the very next turn, triggering compression every 1-2 turns in a never-ending loop.

Setting to 0 forces the preflight to recalculate from the actual compressed messages on the next turn, which produces a value well below threshold_tokens. Real API response usage data overwrites last_prompt_tokens via update_from_response() on the next API call. Fixes #27938.

Related Issue
Fixes #27938

Type of Change

• 🐛 Bug fix

Changes Made

• pyproject.toml:217 — Added "hermes_cli." to [tool.setuptools.packages.find] include list. Every other top-level package (agent., gateway., tui_gateway., etc.) already had its recursive glob; hermes_cli.* was the only one missing, causing hermes_cli/proxy/ and all subpackages to be excluded from the wheel.

How to Test

1. pip install "hermes-agent @ git+https://github.com/NousResearch/hermes-agent.git@v2026.5.16"
2. Run hermes proxy providers
3. Expected: shows nous — Nous Portal (not ModuleNotFoundError: No module named 'hermes_cli.proxy')

[alt-glitch]

Duplicate of #27728 which is the omnibus packaging fix (superset — covers hermes_cli., acp_adapter., MANIFEST.in, and Homebrew). Both fix #27938/#27664. Closed #27726 was also a strict subset of #27728.

[austinpickett]

Please use PULL_REQUEST_TEMPLATE.md

[Copilot]

Pull request overview

This PR updates the Python packaging configuration so hermes_cli subpackages, including hermes_cli.proxy, are included in built wheels.

Changes:

• Adds hermes_cli.* to setuptools package discovery.
• Addresses the missing proxy subpackage reported in issue #27938.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[BoardJames-Bot]

BoardJames triage: uv lock --check is a real branch issue, but I can’t push the safe fix to the contributor fork (git push https://github.com/LifeJiggy/hermes-agent.git HEAD:fix/proxy-wheel-missing returned 403 for BoardJames-Bot). Source: the failing job says the merged PR state needs uv.lock updated; local reproduction in .triage/wt-28060 also fails uv lock --check. I synced the branch with current origin/main, ran uv lock, and uv lock --check then passed locally; that produced only a uv.lock refresh after the main sync (local commit 73c4df00c, not pushed). Exact upstream action needed: someone with write access to LifeJiggy:fix/proxy-wheel-missing should sync with main and commit the regenerated uv.lock (or cherry-pick the local lock refresh from this triage workspace). The separate Tests / test job is still in progress; e2e and all other non-lock checks are green so far.