fix: distinguish safe host authority guard denials #220
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/safe-host-guard-codes"
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
Expose fixed host-created deadline_expired, execution_cancelled, ownership_lost and parent_mandate_missing codes at wait, worker/subagent and result guard sites. Keep authority_revoked for unclassified revocations and invalid wait deadline metadata. No arbitrary error messages forwarded; WeakMap provenance and fixed rendering remain.
Authority predicates, status exemptions, persisted receipts and storage schema remain unchanged. No deadline extension, automatic approval, task reopening or global build/deployment ban. Builds do not activate this change.
Verification
Independent dedicated review via the normal persistent ReviewService, exact fingerprint ca2aa568d7c79bf7f50d62acdbf8ce7d0679a71e7e2d9c09b5b4b03fe9f78e52: passed in round 1, no findings. Existing budgets preserved.
Existing PR #156 supplies receipts only and #85 supplies generic safe rendering; neither supplies these distinctions. No duplicate receipt solution. Foreign dirty core checkout untouched.
Integration
Source PR only. No merge/image/deployment/GitOps changes. External maintainer integration and authorized image rollout/restart are required for activation.