Skip to content

[TS PBT] Compose campaign artifacts and existing edge guidance - #569

Open
CaelmBleidd wants to merge 4 commits into
caelmbleidd/pbt-guided-campaign-basefrom
caelmbleidd/pbt-guidance-composition
Open

CaelmBleidd wants to merge 4 commits into
caelmbleidd/pbt-guided-campaign-basefrom
caelmbleidd/pbt-guidance-composition

Conversation

@CaelmBleidd

Copy link
Copy Markdown
Member

The existing campaign artifacts, native witness results and edge-guidance stack do not compose without serialization, deadline and assertion compatibility fixes. Serialize the existing portable edge trace, map initial coverage once, preserve both caller-deadline entry points, and migrate existing assertions to native witness results. Scheduling policy is unchanged.

Own diff against the immediate assembly base: 8 files, +52/-38. This PR contains four own commits. The assembly branch contains existing dependency merges only:

Frozen assembly: 342a042ef04c5bd34f202952a7fbb4751c3982c9. Its inherited implementation is excluded from this PR diff. After the dependencies merge, move only the four own commits onto main and retarget this PR; do not merge the assembly wholesale.

Validation: 10 real backend edge/runtime regressions passed; Detekt main/test for both PBT modules reports zero findings. Existing direct campaign and edge-guidance checks also passed on the assembled dependencies before consumer behavior was added. No comparative coverage benefit is claimed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant