[gael-obin]

A browser hop could retain a Work Context after the live authority refused it, causing later explicit calls to reuse that same stale context. The gateway now observes the hop's existing Check result and evicts only the matching cached context on authority refusal.

Classification: fix at the gateway cache owner. The current response is returned unchanged, with no replay. A later explicit request may obtain a new context. A downstream refusal after a successful Check does not evict, and concurrent replacement entries are preserved. Authority remains the only decision-maker.

The three-file publication includes the implementation, revision-probe tests and precise operating guidance. It matches the source exercised in a persistent local composition; independent publication review verified the source hashes and excluded unrelated host changes.

Merge/release qualification remains pending clean dependency/owner CI qualification. Recovery is per-instance best effort, not cross-replica or guaranteed next-request success. This does not fix the separate browser token-refresh problem where an intended authentication 401 is serialized as Connect 403. That finding remains open and must be addressed at its status-mapping owner without refreshing all permission failures.

CI and review follow-up

Opened for review at the author’s request. Removing draft status does not certify merge or release readiness. This follow-up inspected the published head and logs; it made no implementation changes and did not rerun tests.

All reported applicable checks passed. This does not fix the separate authentication-status mapping/token-refresh issue, qualify a combined setup cohort, or establish cross-replica recovery.

No submitted GitHub reviews, inline review comments, or conversation comments were present in the captured state. Independent publication/status audits are scoped evidence, not owner approval.

[gael-obin]

@antoinetoussaint-byte Please review this gateway-cache fix at 218188168050c3b5ace314aba4e632cea65b2b4a for the normal merge queue. All 22 applicable hosted checks pass (four other checks skipped). The bounded behavior is cache eviction after live authority refusal without replaying the request; the separate authentication status-mapping issue remains open as described above.

The receipt-verification change at 8c4d97dfb7d4a2e67eeb1331315ded411e661a22 also has 22 passing checks, including corrected audit policy and regenerated SDKs. Please include it in owner merge-queue review. The former fencing blocker was stale: accepted owner work already integrated the invocation fencing. Independent source comparison verifies the invocation implementation/tests and SDK fencing regression are preserved by the receipt change. The PR body now records that reconciliation. Matching SDK/server release adoption and combined consumer qualification remain separate from merging these generic owner fixes.

This account cannot merge/enqueue upstream or formally request a reviewer, so this is the approval handoff. No queue membership, merge, release or combined deployment qualification is claimed.