Confirm the edge is actually running the configuration it was given#225
Draft
scotwells wants to merge 1 commit into
Draft
Confirm the edge is actually running the configuration it was given#225scotwells wants to merge 1 commit into
scotwells wants to merge 1 commit into
Conversation
Adds a check that compares what the platform intended for the edge against what the edge is actually serving, and names any gap in plain terms (missing, wrong count, wrong place, rejected, or dropped at a limit). Turns a healthy -looking response into real evidence the configuration took hold. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JbCy8vy66RdNYzGSgqH6P6
scotwells
force-pushed
the
feat/edge-config-parity-check
branch
from
0d29a7b to
39d6427
Compare
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
1 participant
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.
What this checks
A request can succeed and still hide configuration that never took effect, applied only partly, or landed in the wrong place. A green response is not proof the edge is doing what it was asked to do.
This adds a check that compares two things: what the platform intended for the edge, and what the edge is actually serving right now. When they line up, we have real evidence the configuration took hold. When they don't, the check names the gap in plain terms — missing, wrong count, applied in the wrong place, rejected, or dropped because a limit was hit — turning a surprising result into a cause instead of a guess.
Why it matters
Most of our confidence in the edge has rested on "the request worked." That misses a whole class of silent failures where the edge looks healthy but isn't actually enforcing what it should. This gives those failures a name and a place to surface, so we catch them in testing instead of in production.
Pairs with
This reads the reference point introduced alongside it — the edge's own report of the protections it was told to run.