Repository navigation
fix(frontdoor): carry a route's model choice back through the headroom hop - #510
Merged
Merged
Conversation
…m hop A choice a route noted while serving behind the headroom hop (the antigravity tier alias above all) never reached the usage record, so the statusline showed the virtual name alone with no arrow: the route notes the choice on the response of the direct listener that served it, and the direct pipeline deliberately runs no response observers, so the choice died with the head it was noted before. The direct pipeline now exposes the noted choice on its response head as an internal header, whose only consumer is this door's own hop: the hop reads it off the daemon's relayed head, notes the choice on the client-facing response before that response's head is written (which is where the usage middleware observes it), and leaves the header out of what the client receives. A header value that is not the exact shape this door writes is dropped rather than trusted.
Codex Review SummaryThis 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix(frontdoor): carry a route's model choice back through the headroom hop
A choice a route noted while serving behind the headroom hop (the
antigravity tier alias above all) never reached the usage record, so the
statusline showed the virtual name alone with no arrow: the route notes
the choice on the response of the direct listener that served it, and
the direct pipeline deliberately runs no response observers, so the
choice died with the head it was noted before.
The direct pipeline now exposes the noted choice on its response head as
an internal header, whose only consumer is this door's own hop: the hop
reads it off the daemon's relayed head, notes the choice on the
client-facing response before that response's head is written (which is
where the usage middleware observes it), and leaves the header out of
what the client receives. A header value that is not the exact shape
this door writes is dropped rather than trusted.