Repository navigation
Expose trusted HTTP executor dispatch receipts - #5483
Conversation
📦 Client bundle boundary
A server module in a client graph aborts hydration in the browser. New leaks fail CI; known leaks are tracked in |
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@codex review |
|
Codex Review: Didn't find any major issues. More of your lovely PRs please. Reviewed commit: ℹ️ About Codex in GitHubCodex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback". |
|



The HTTP broker can reuse one authenticated executor for several requests, but its attachment identity was unavailable to a trusted request observer. Add an opt-in dispatch receipt that pairs each host trace parent with the actual allocation, generation, invocation, Pod UID, node, and declared image.
The observer runs before dispatch and receives an immutable projection without credentials or connection addresses. Failed authentication produces no attachment receipt. Warm requests retain distinct trace parents while sharing one authenticated attachment.
Validation: 13 focused tests and 144 steps passed, including warm reuse and rejection of the caller trace header as receipt authority. Frozen type checks, formatting, and branch review passed.
The deployed collector and the join to Pod image ID and effective policy remain part of the live staging proof. Tracks #1378 in veryfront-issue-inbox.