The update path reports success and then says it cannot confirm which version is running, because the messaging process never reports its running version set. The statement is truthful but the verification is unreachable, so it reads as a failure on every success.
Acceptance criteria
The messaging process reports its running version(s) so a successful update can confirm it; a genuine mismatch still reports unconfirmed; test both
Close reason
Closed
Imported from beads archie-core-ot33 · GitHub #1491 · type bug · priority P3 · created 2026-10-02 · closed 2026-10-02
The update path reports success and then says it cannot confirm which version is running, because the messaging process never reports its running version set. The statement is truthful but the verification is unreachable, so it reads as a failure on every success.
### Acceptance criteria
The messaging process reports its running version(s) so a successful update can confirm it; a genuine mismatch still reports unconfirmed; test both
### Close reason
Closed
---
_Imported from beads `archie-core-ot33` · GitHub #1491 · type bug · priority P3 · created 2026-10-02 · closed 2026-10-02_
sam
added the lowbug labels 2026-10-27 13:40:37 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The update path reports success and then says it cannot confirm which version is running, because the messaging process never reports its running version set. The statement is truthful but the verification is unreachable, so it reads as a failure on every success.
Acceptance criteria
The messaging process reports its running version(s) so a successful update can confirm it; a genuine mismatch still reports unconfirmed; test both
Close reason
Closed
Imported from beads
archie-core-ot33· GitHub #1491 · type bug · priority P3 · created 2026-10-02 · closed 2026-10-02