feat(network): assemble bounded WebDriver BiDi text messages - #246
Draft
seonghobae wants to merge 59 commits into
Draft
feat(network): assemble bounded WebDriver BiDi text messages#246seonghobae wants to merge 59 commits into
seonghobae wants to merge 59 commits into
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Signed-off-by: Seongho Bae <me@seonghobae.me>
Signed-off-by: Seongho Bae <me@seonghobae.me>
Signed-off-by: Seongho Bae <me@seonghobae.me>
…json-envelope feat(network): validate WebDriver BiDi JSON envelopes
Integrate the owning connection-lifetime fixture repairs while preserving the message-assembly and JSON-envelope implementations. Record exact predecessor and parent evidence without claiming a newly reproduced socket failure. Commit-Message-Assisted-by: Codex (via Codex) Signed-off-by: Seongho Bae <me@seonghobae.me>
seonghobae
added a commit
that referenced
this pull request
Sep 5, 2026
Bind the #246 parent integration and complete local coverage to its exact head. Record #141's unchanged-head cleanup diagnostics and informational thread resolution without promoting cancelled hosted checks or local tests to protected delivery. Commit-Message-Assisted-by: Codex (via Codex) Signed-off-by: Seongho Bae <me@seonghobae.me>
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.
Boundary
Adds bounded RFC 6455 text-message assembly above PR #243 and preserves the JSON-envelope delta previously integrated from PR #247. The frame layer owns wire validation; the assembler owns fragmentation and bounded UTF-8 text; JSON envelopes remain protocol data, not received-connection provenance or browser authority.
Implemented contract
Current exact-head integration and evidence — 2026-09-08
Current head
585791f3641fbe757c3bd9fd36d5316adcc78d63is an ordinary, non-force merge of frame parent97fab641ed9d76e6c515eadcef0629edfc8064a3into predecessorb87191bcb6a95dfd7e0ed234e600639a1093c43a. The message/JSON source and test blobs are unchanged. Inherited opening-exchange fixture lifetimes match their verified owner repair.Hosted CI
33953247053is now terminal success on this unchanged exact head. Rust contracts job101271826592passed Python repository contracts, canonical formatting, workspace check, full tests, strict Clippy and warnings-denied API documentation. Production coverage job101271826759passed measurement, diagnostics upload and exact production coverage enforcement. The older body statement that fresh hosted checks still had to finish was stale and is superseded by this evidence.This remains repository-quality evidence for the bounded message/JSON slice only. It does not establish received-connection provenance, browser-process authentication, action post-condition evidence, protected-main integration or release acceptance. Earlier CI
33272665984remains historical evidence forc3165309...only.Stack and authority
Draft on PR #243 at
97fab641ed9d76e6c515eadcef0629edfc8064a3; prerequisite and exact-head policy gates remain mandatory. No DNS, reconnect, proxy, TLS, browser, origin, policy, secret, model, unrestricted JavaScript or workflow authority is added. No force push, self-approval, workflow/ruleset weakening, tagging, publication or release is part of this integration.