fix(managed_uv): add missing hermes_state_* modules to py-modules for replacement env smoke tests

[webtecnica]

Problem

The replacement environment smoke test (_smoke_candidate_venv) runs
python -I -c "import ... hermes_state" in isolated mode on the
candidate venv. hermes_state.py imports four sibling top-level
modules:

• hermes_state_common
• hermes_state_portability
• hermes_state_schema
• hermes_state_search

These were NOT listed in pyproject.toml's py-modules, so
setuptools/uv never installs them into the venv's site-packages, and
the editable finder's MAPPING dict doesn't cover them. In normal CLI
usage (no -I), the current directory's sys.path[0] entry lets
Python resolve them. But in isolated mode (-I), the current
directory is not searched, producing ModuleNotFoundError: No module named 'hermes_state_common' — causing the entire replacement
environment to be rejected.

Fixes #74479

Root Cause

hermes_state.py imports hermes_state_common, hermes_state_portability,
hermes_state_schema, and hermes_state_search at the top of the file.
These are top-level .py files in the repository root (not part of any
package). The pyproject.toml [tool.setuptools] py-modules list tells
setuptools which standalone modules to include in the distribution. Any
module not listed there is never installed into the venv.

When uv sync creates an editable install, it generates an
__editable___hermes_agent_0_19_0_finder.py file with a MAPPING dict
that translates module names to filesystem paths. Only modules listed
in py-modules appear in MAPPING. Modules that are missing from
MAPPING but are imported by other modules in MAPPING fail with
ModuleNotFoundError in isolated mode.

Changes

1. pyproject.toml: Added hermes_state_common, hermes_state_portability,
   hermes_state_schema, and hermes_state_search to the py-modules list.

2. hermes_cli/managed_uv.py: Log the full smoke stderr output at debug
   level (logger.debug) so future failures include the complete traceback
   instead of just the last line of the error.

Verification

Before the fix, running python -I -c "import hermes_state" from the
repository root fails with:

ModuleNotFoundError: No module named 'hermes_state_common'

After the fix (after uv sync regenerates the editable finder),
hermes_state_common and the other three modules will be in the
MAPPING and the import will succeed in isolated mode.

[teknium1]

Thanks — the managed-UV packaging diagnosis is valid on current main, and the stacked config fix is also still needed.

Problems

• 9526ebb6de5abc90f1e6d502a81a5f43c09f9f61 is redundant: current main already has the lock-patience implementation in hermes_state.py:1920-1959, 2317-2396, and 5607-5614, shipped by 8da8a7887d06373e169af6e431ec52ebb439ec7a.
• The pyproject.toml correction has no regression that exercises the isolated candidate/editable import path. Current main still omits the four imported state modules from py-modules at pyproject.toml:349, while hermes_state.py:45 and 70-72 import them.

Suggested changes

• Salvage the packaging commit and the still-needed duplicate-URL header fix (0984788bd187d8b373f2d544567d26d317215e50) independently; omit the already-implemented SessionDB commit.
• Add a temporary isolated-environment smoke regression for import hermes_state.

Automated hermes-sweeper review.

[GottZ]

This was generated by AI during triage.

Summary

One PR, #74506, references #74479. Its pyproject.toml change directly addresses the isolated-import failure by packaging the four hermes_state_* modules, while its managed-UV logging is diagnostic and its custom-provider-header and SessionDB changes address separate concerns.

Related pull requests

• fix(managed_uv): add missing hermes_state_* modules to py-modules for replacement env smoke tests #74506 best fix — (+308/-34) — keep open with a salvage path: the py-modules addition matches the reported ModuleNotFoundError, but the issue close verdict records that this packaging fix already landed through fix(nix): include new flat modules at the root #74362 at 36e41c0. Consistent with the keep_open review on fix(managed_uv): add missing hermes_state_* modules to py-modules for replacement env smoke tests #74506, the still-needed duplicate-URL header fix can be salvaged independently; the redundant SessionDB changes should be removed, and any retained packaging work needs an isolated candidate-environment import regression.

Duplicates

The pyproject.toml portion of #74506 duplicates the packaging correction already applied by #74362; no competing open PR duplicates the remaining custom-provider-header fix.

Suggested consolidation

Keep #74506 open with a salvage path: rebase it onto current main and split out the duplicate-URL custom-provider-header fix, retain the managed-UV diagnostic only if independently justified, and drop both the packaging hunk already supplied by #74362 and the SessionDB work already supplied by 8da8a78. The automated keep-open review supports this extraction rather than closing the entire PR.

Complex graph

flowchart LR
    classDef open fill:#dbeafe,stroke:#1d4ed8,color:#1e3a8a
    classDef merged fill:#dcfce7,stroke:#15803d,color:#14532d
    classDef closed fill:#e5e7eb,stroke:#6b7280,color:#1f2937
    classDef unverified fill:#f3f4f6,stroke:#9ca3af,color:#374151
    classDef best stroke-width:3px,stroke:#b45309
    classDef target stroke-width:3px,stroke:#4338ca
    I74479(["issue #74479 (closed)"])
    P74506["PR #74506 (open)"]
    P74506 -->|best fix| I74479
    class I74479 closed
    class P74506 open
    class P74506 best
    class P74506 target
    click I74479 "https://github.com/NousResearch/hermes-agent/issues/74479"
    click P74506 "https://github.com/NousResearch/hermes-agent/pull/74506"

Loading

Graph: solid arrow = fixes / best fix, dashed arrow = partial or unverified (see edge label); boxed group = PRs duplicating each other; amber border = best fix; indigo border = target; gray node = closed (state tag in the node label).

Cross-PR triage: Reviewed 1 pull request and 1 issue in this complex. Each diff was read against this issue; Assessment working set: 21 kB of PR diffs, 7 kB of issue/PR text, 1 kB of discussion (1 comments), 2 verify verdicts. verdicts reflect diff content, not PR titles. Part of an automated triage batch.