# NousResearch/hermes-agent · Snapshot restore falsely reports success on refusal

## Open now

- Nothing open on GitHub.

These issues address a bug where the snapshot restore command prints a success message even when the database restore is refused, particularly when holder scans are incomplete. The fixes prevent destructive restores in that scenario and correct the misleading output.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## 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

- #95763: \[Bug\]: /snapshot restore prints success when the DB restore was refused

## Prior & competing PRs

- **#95764: fix(state): do not print success when snapshot DB restore is refused**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `1f7cb4f871`, `e907a9a14b`, `44248a0b39`
- **#97499: fix(state): refuse destructive restore on incomplete holder scans**. closed without merge
  - maintainer direction: category `stale_abandoned`; implication `active`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`