feat(integration): add pre-execution plugin delivery revocation fence

[seonghobae]

Buyer gap

Advances #130 immediately after #256 with the next LifeOS-owned delivery-lifecycle boundary: an exact per-attempt revocation fence immediately before provider execution. The fence revalidates the worker's active finite claim together with the exact active delivery-origin grant and active owning installation under the same workspace/user scope.

This slice remains Integration-owned. Passing the fence is not outbound-network authorization, does not materialize provider credentials, and does not authorize DNS/IP/redirect/proxy/connect behavior. A later executor must still consume only immutable released/versioned canonical egress authority and otherwise remain fail closed.

RED → causal repair → exact GREEN

Direct parent is #256 exact 0c6221e1fe32bf6594784219a7bd710ad0c1a993. The original regression lineage beginning d2dee04c791dcd31f8ff136fb8686fae302c013a establishes the missing execution-fence capability. The retained implementation binds exact delivery/workspace/requesting-user identity and claim-token digest, requires an unexpired active claim, and joins the exact active delivery-origin grant plus active owning installation. Real PostgreSQL acceptance proves success while all authority remains active and fail-closed rejection after grant or installation revocation without mutating the accepted claim.

Exact 61c179a5886a79e2fa6bbca53b704275bcb3a0ea, run 34266240410, job 102196214538, completed GREEN on Ubuntu 24.04/PostgreSQL 16 across exact checkout, frozen install, canonical repository formatting, Plugin SDK build, focused execution-fence/PostgreSQL acceptance, Integration typecheck and the complete Integration service suite.

Fresh authority review then found a separate opaque-capability defect: the application parsed the raw UUIDv4 claim token with a case-insensitive UUID validator and lowercased it before SHA-256 hashing. A hex-case alias could therefore acquire the same durable claim digest even though the contract calls this an exact raw-claim-token-bound capability. Regression-only 48b823903d14c3ca0c868bf335d023904b2dcf9d requires a case-aliased raw token to fail before the store receives any durable-authority lookup. Hosted run 34267014048, job 102198804685, acquired a real Ubuntu 24.04/PostgreSQL runner, passed exact checkout, frozen install, formatting and Plugin SDK build, then failed at the focused execution-fence acceptance as intended; typecheck/full suite were skipped after that RED.

Minimum causal repair a40098db19ea9830367b6cabd1bc552a019a990a changes only raw claim-token handling: the token must already be canonical lowercase UUIDv4 text and its exact bytes are hashed without normalization. Other UUID identity normalization and the repository SQL/durable schema remain unchanged. Exact run 34267152261, job 102199270687, completed GREEN across exact checkout, frozen install, formatting, Plugin SDK build, focused execution-fence/PostgreSQL acceptance, Integration typecheck and the complete Integration suite. Current exact 5ac3d2fcdf30e97be006405cf599f3d666cf5946 removes only the now-purpose-complete verifier; production/test/repository evidence is unchanged from the proven head.

Deliberate boundary

This fence does not consume provider credentials or authorize outbound HTTPS. Durable origin/delivery/claim/retry/outcome/control/fence identity is not DNS/IP/redirect/proxy/connect-time network authority. A later executor must consume an immutable released/versioned canonical egress contract and retain finite I/O, retry/outcome, revocation, recovery and operator evidence.

Keep Draft. #256 must integrate normally first and the unchanged descendant must satisfy current repository/security/central workflow evidence plus independent review/thread authority after prerequisite integration. No self-approval, administrator bypass, force-push, destructive rebase, mutable dependency, source copy, cross-service SQL, stale evidence reuse or gate weakening.

Refs #130, #252, #253, #254, #255, #256; ContextualWisdomLab/EgressWeave.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}