fix: confirm task cancellation after owned group settlement (#90) #93
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-90-owned-cancellation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
Implements Kernel issue #90 for the existing foreground trusted-development task path. Persists the exact owned Codex process-group identity with the runtime receipt, coordinates cancellation with bounded
CodexStdiocleanup, and reports confirmed cancellation only when the result is reconciled and that exact group is settled. Mismatched/unobservable groups and incomplete receipts remain uncertain; no uncertain interrupt is replayed. Cancellation remains distinct from rollback and universal descendant containment.Adds explicit
cancel_requested,cancel_in_progress,cancelled,cancelled_no_dispatch, andcancel_uncertainreporting with durable settlement evidence and recovery behavior. Legacy v1 runtime receipts remain decodable but do not certify a group identity. Cleanup also continues bounded group escalation when the original process-group leader has already exited.Validation
make check: 1457 passed, 85 skipped, 106 subtests; Ruff, basedpyright, import-boundary, secret-scan, and diff checks passed.make package-check: reproducible wheel/sdist, isolated install, and CLI/intake/source smoke checks passed.Refs
Refs #90
Base:
40eea02cee517f7b31da01173739b23c510779b0Head:
085c5c43f22da3e6b0ec61cce4d2914e5d018d36No live inference was run. Strict native-effect expiry, rollback, and universal descendant containment remain outside scope.