# NousResearch/hermes-agent · SessionDB close poisoning FTS/write handles bug fixes

## Open now

- Nothing open on GitHub.

These items concern a bug where a clean SessionDB close incorrectly poisons optimize_fts, rebuild_fts, vacuum, and related write handles, along with fixes to serialize and reopen those handles in affected code paths.

## 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 #116748. Verify it addresses your case.
- **Recommended:** read PR #116748 (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-116748`. 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 `0.67`: 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

- #116244: \[Bug\]: clean SessionDB.close() still poisons optimize_fts and _execute_write error handles after #108082/#110544

## Prior & competing PRs

- **#116748: fix(state): a clean close no longer poisons optimize_fts/rebuild_fts/vacuum handles (#116244, salvage #116298)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_state.py`, `hermes_state_fts.py`, `hermes_state_maintenance.py`, `hermes_state_search.py`, `tests/hermes_state/test_clean_close_residual_poison.py`
- **#116298: fix(state): serialize replaced probe and reopen on close in residual entry points (#116244)**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `26955efb535a`, `#116748`, `#116244`, `#116298`

## Fix status

- Merged to main in PR #116748 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-20`.