# NousResearch/hermes-agent · Profile state.db backup coverage during updates

## Open now

- Nothing open on GitHub.

These issues and pull requests concern a gap where pre- and post-update state.db emergency backup logic applied only to the root database, leaving per-profile databases unprotected. The work addresses extending that guard to cover every profile.

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

- #97994: \[Bug\]: pre-update state.db guard (#68474) covers only the root DB — profile databases get no emergency backup

## Prior & competing PRs

- **#100643: fix(update): post-update state.db guard covers every profile (salvage #99954)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/update_cmd.py`, `tests/hermes_cli/test_update_state_autorestore.py`
- **#98121: fix(desktop): snapshot every profile state.db before update (#97994)**. closed without merge
  - maintainer direction: category `stale_abandoned`; implication `active`; refs `#99513`, `#98017`
- **#99954: fix(update): post-update state.db guard covers every profile, not just the root**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#100643`, `#68474`

## Fix status

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