Cairn
NousResearch/hermes-agent

Update receipt lost during stale module purge

Cluster 98436. Data as of

Nothing open on GitHub. Fix merged in #103478 on 5 Sep 2026. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #103478. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #103478. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and fixes address a bug where an active update receipt is incorrectly discarded when stale modules are purged during an update handoff. The work focuses on keeping in-flight receipts alive across the purge step.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #103478 fix(update): fleet check no longer fails with "no rows" after stopping unmapped/dashboard-only runtimes; receipts survive the module purge (#97332, #98436, salvage #97350 #92934)

    merged to main

    files: contributors/emails/[redacted:email], hermes_cli/update_cmd_fleet.py, hermes_cli/update_cmd_maint.py, tests/hermes_cli/test_update_fleet_check_fail_closed.py, tests/hermes_cli/test_update_fleet_probe_resume_token.py, tests/hermes_cli/test_update_stale_module_purge.py

3 PRs closed without merging

From the close comments: merged via another change 2 · superseded by another PR 1

  • #92934 fix(update): preserve active receipt across module purge · merged via another change → f58fcc8, #103478, #98436
  • #98449 fix(update): keep the in-flight update receipt module alive across the stale purge · superseded by another PR → #92934, #98436
  • #98454 fix(update): protect hermes_cli.update_receipt from the stale-module purge (#98436) · merged via another change → f58fcc8, #103478, #92934
Closed issues · 1
  • Closed#98436[Bug][Windows] hermes update hand-off child silently loses its update receipt after the catch-up module purge — console end state also looks hung
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.40: the share of item 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.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs
#103478
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
5 Sep 2026

For your agent

The same facts, typed.

cluster/98436.json
cluster/98436.md