# NousResearch/hermes-agent · Gateway inbound gate wedged by startup-restore replay error

## Open now

- Nothing open on GitHub.

These issues and PRs concern a bug where a single failing or raising replay during startup-restore causes the gateway's inbound latch/gate to remain permanently closed. The work focuses on ensuring the gate is \`released\` even when restore \`fails\`.

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

- #116514: One raising startup-restore replay wedges the inbound gate closed forever

## Prior & competing PRs

- **#116654: fix(gateway): one raising startup-restore replay no longer wedges the inbound gate (#116514, salvage #116516)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/run_startup.py`, `tests/gateway/test_restart_resume_pending.py`
- **#116516: gateway: one raising startup-restore replay must not wedge the inbound gate**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `07c7dabd1430`, `#116654`, `#116514`, `#116516`
- **#116539: fix(gateway): release startup-restore inbound latch on restore failure**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `07c7dabd1430`, `#116654`, `#116514`, `#116516`

## Fix status

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