# NousResearch/hermes-agent · Test fixture leaking into production state database

## Open now

- Nothing open on GitHub.

A bug where test sessions escape their fixture isolation and pollute the developer's live state.db with junk rows. The associated fixes address the isolation guard using process ancestry checks and subprocess-surviving markers to prevent fixture escape.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #86861. Verify it addresses your case.
- **Recommended:** read PR #86861 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-86861`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `1.00`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #82770: Test sessions leak into the developer's production state.db (fixture-escape class) — 700+ junk open keyed rows

## Prior & competing PRs

- **#86861: fix(state): close the #82770 test-fixture escape — ancestry guard + subprocess-surviving isolation marker + never-active prune**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/main.py`, `hermes_cli/sessions_cmd.py`, `hermes_state.py`, `tests/conftest.py`, `tests/hermes_state/test_isolation_marker_env.py`, `tests/hermes_state/test_live_db_guard_ancestry.py`, `tests/hermes_state/test_live_db_isolation_guard.py`, `tests/hermes_state/test_never_active_keyed_prune.py`
- **#82803: fix(state): arm the live-DB guard by process ancestry, not env alone**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `62d3ef683c52`, `#86861`

## Fix status

- Merged to main in PR #86861 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-08-15`.
- Subsystem: `agent`