Repository navigation
Emergency Hyprland release changes quarantined recovery into an invalid paused durable state #511
Description
Activity
Keeping this open: a release that leaves the store unable to reopen is a real defect. A constraint for the fix, from the maintainer's standing computer-use rule: on Wayland/Hyprland the default leans toward working. A guard stays only where it protects real safety: input that is genuinely held, or a wrong or unauthorized target. What the guardian's own ledger says was released proceeds, even when the compositor can't confirm it. Don't resolve this by keeping the session quarantined or by requiring operator reconciliation because a release can't be confirmed.
- added a commit that references this issue
on Sep 29, 2026 Validated as fixed on
campaign/v4.10.0-review(PR #629) at3047c46c: the fix was reviewed against the final code, and its regression tests pass on the branch and in CI. Round-1 correctionf293b000: a ledger-confirmed emergency release of anunknown_releaseincident archives the incident atomically and leaves the session paused with renewed consent required;native_continuity_loststays quarantined, and the store reopens cleanly. It is not merged to master yet. Closing per the maintainer's instruction; reopen if a later change regresses it.
Severity: P2
Verified at v4.10.0,
55c15761845b00931ab2ea4aa184a7797dfd0614.Locations
src/computer/controller.py:2012-2056; src/computer/store.py:549-589Failure scenario and affected installations
Hyprland unknown-release incident with retained adapter and recovery pending. Emergency owned-release unconditionally persists paused but leaves unknown_release/native_continuity_lost pending fence; successful release then leaves cross-field invariant invalid and next store reopen fails provisioning.
Verification
Independently traced state change preserving pending record versus schema validator. Reviewer real disposable store/controller fixture returned paused pending unknown_release then reopen storage_schema_unsupported.
Correction and tests
Preserve quarantine/recovery lineage until supported reconciliation transaction; never manufacture resumable paused grant from release attempt. Regress reopen after emergency release.
Duplicate screening
Checked open/closed inventory and GitHub title/body searches, no matching root. #404 concerns known-refusal classification, not these paths. No live desktop/operator APIs or native input used.