Repository navigation
test(companion): cover token revocation during network rebind - #406
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Oct 24, 2026
This branch was successfully deployed
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.
Adds the missing #109 regression for revocation during a network rebind. The test removes the original address, pauses a real replacement HTTPS listener before publication, revokes pairing access, and confirms the old token is rejected while the new token works with the same pinned certificate. Production behavior and address policy are unchanged.
The test passes on existing production code. A generated-code negative control captured authorization at listener startup and failed with
200 !== 401for the revoked token; the original generated bytes were restored. Focused companion tests passed 27/27 with no skips, including LAN-gated cases. Full build, unit tests (2,085 passed, 22 skipped, zero failures), and typecheck passed. Independent review approved the test and cleanup. No local UI E2E was needed for this test/documentation change; hosted checks are pending.The evidence and physical acceptance procedure maps existing coverage and preserves the pending physical secondary-LAN and VPN-policy gates. #109 remains open. No physical DHCP acceptance, new interface policy, wildcard binding or broader qualification is claimed.
Signed head:
0acf12dc88e17e7033b0acc5b167870df8486c67, based on maine3527f457842c6eff9c793f8efe7883013954d93. Raw first-pass, negative-control and full validation receipts are preserved outside the worktree.