# NousResearch/hermes-agent · SQLite WAL-reset bug detection and mitigation

## Open now

- Nothing open on GitHub.

These members address a corruption bug in SQLite 3.50.4 related to WAL (Write-Ahead Logging) reset behavior. The work involves detecting affected SQLite builds and refusing WAL mode on them as a safeguard.

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

- #69784: \[Bug\]: Bundled SQLite 3.50.4 hits upstream WAL-reset corruption; clean on 3.51.3

## Prior & competing PRs

- **#70055: fix(state): refuse WAL on SQLite builds with the WAL-reset bug**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `agent/verification_evidence.py`, `cron/executions.py`, `gateway/delivery_ledger.py`, `hermes_cli/doctor.py`, `hermes_state.py`, `plugins/platforms/discord/recovery.py`, `tests/test_hermes_state.py`, `tests/test_hermes_state_wal_fallback.py`, `tests/test_sqlite_wal_reset_gate.py`, `tools/async_delegation.py`
- **#69981: fix(state): refuse WAL on SQLite builds with the WAL-reset bug**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#70055`

## Fix status

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