# NousResearch/hermes-agent · FTS rebuild write path corruption and data loss

## Open now

- Nothing open on GitHub.

These items concern a scenario where a corrupt state.db causes FTS rebuilds to falsely report success, leading to silent data loss as the pending queue rotates transcripts away. The group covers the problem report and related fixes addressing write path verification and handling of pending-cap overflow.

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

- #78182: Gateway writes through a corrupt state.db indefinitely: one-shot FTS rebuild reports success without verifying the write path, then the 200-cap pending queue silently rotates transcripts away

## Prior & competing PRs

- **#82719: fix(state): keep canonical writes available when FTS is corrupt (#78182)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_state.py`, `hermes_state_common.py`, `hermes_state_schema.py`, `hermes_state_search.py`, `tests/state/test_fts_runtime_rebuild.py`
- **#78323: fix(state): verify FTS rebuild write path; spool pending-cap overflow**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#82719`, `#84785`

## Fix status

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