Repository navigation
Drain the original browser sampler before its parent retires - #708
Merged
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
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.
The exact retained-candidate journey failed after its inner observation completed because the browser companion kept sampling while its original parent and browser retired. At the proven contract terminal boundary, drain and reap that original companion before the parent returns, retain bounded stop/reap evidence, and require that evidence in the final browser binding. Live birth-change and active-failure guards remain enforced.
Validation: maintained-owner pure/static sweep passes 149 browser controls (including23 terminal-stop cases),121 contract controls,39 INFO controls and31 event controls;25 public-reference tests and existing workflow controls pass. The assembled lifecycle checks stop/reap before inner success. Pipeline preflight reuses those existing composition/refusal controls and the unchanged Node drain implementation; a new custom model is deferred because this orders an existing transition, with no retry or failure-suppression change. Required exact-head source CI and a separately root-admitted new native journey remain pending. Original candidate9b/0.32.2 bytes and failed run38210437244/a1 remain retained.