Qualify packaged worker hostile inputs and cancellation - #53
Merged
Conversation
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.
Summary
--caseselector for targeted gate reruns.Why this is needed
The prior qualification proved only the happy-path transform. It did not establish that hostile decoder bytes are rejected inside the signed worker or that cancellation reaches an active packaged transform. During this work the expanded gate also caught a real harness framing defect: a 48 KiB worker chunk expands beyond the broker frame limit after base64 and envelope overhead. The qualification harness now exercises the worker through the corrected transport bound and preserves failure details without exposing payloads.
Validation
--json --strict): all four cases passed, includingcancel_ackafterinput_complete.compileallandgit diff --checkpassed.Release-gate status
This closes the packaged hostile-decoder and cancellation qualification evidence. Parser fuzzing, resource/watchdog accounting, artifact security review, external review, and production lifecycle health/wiring remain explicit blockers before provider enablement.
Cortex.pyprojwas intentionally excluded because it contains an unrelated user edit.Builds on the merged worker transport fix in #52.