You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Browser: prove admission retirement across record cleanup and session end #438
Runtime owns the Browser operator grant lifecycle. Verify that repeated handoffs release retired grants and preserve active grants and pending release work.
Source at #412 head 1b9cf8e: gateway_browser_operator.rs calls grant_request at lines 556–559, gives its token an explicit expiry at 552–554, and calls pending.cleanup_old(60) at 334. Eligible admission records are removed after 120 seconds at 319–324. Operator requests allow 2–30 seconds. Thus the reported missing grant_request call is not present on this head; the complete retirement journey needs proof.
Done means:
Exercise approval, action exhaustion, expiry, explicit takeback, session end and the 120-second record cleanup through the real operator service.
Retired grants leave the pending/session indexes; active grants remain listed and revocable. Busy and release-pending records retain their reconciliation duties.
Repeated handoffs admit a fresh request after retirement. Controlled clock and race tests prove the boundary; reverting the responsible retirement behavior causes an assertion failure.
Keep the existing Runtime principal/page/generation checks and typed provider path. Verify human and agent handoff on the accepted installed Browser target.
Related: #290 owns operator parity; #177 owns broader real-stop authority. This is a requested follow-up to #412.
Activity