# NousResearch/hermes-agent · Fresh state.db FTS setup corruption and serialization fixes

## Open now

- Nothing open on GitHub.

A bug where a freshly created state.db becomes corrupted during full-text search bootstrap, and several fixes aimed at serializing or locking the FTS setup process to prevent concurrent corruption.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #106311. Verify it addresses your case.
- **Recommended:** read PR #106311 (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-106311`. 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.50`: 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

- #105790: \[Bug\] Fresh state.db corrupted within ~70 min of creation by gateway's own FTS setup — quick_check passes, integrity_check cannot prepare, doctor surgery fails

## Prior & competing PRs

- **#106311: fix(sessions): a fresh state.db no longer publishes FTS tables before owning the rebuild lock (#105790; salvage #105805)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_state_schema.py`, `tests/state/test_fts_fresh_bootstrap_admission.py`
- **#105805: fix(sessions): prevent fresh state.db corruption during FTS setup**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `19c9734021`, `#106311`
- **#105948: fix(state): serialize fresh FTS bootstrap**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`

## Fix status

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