Skip to content

Fix bounded Chrome CDP startup - #230

Draft
docxology wants to merge 10 commits into
mainfrom
codex/chrome-startup-budget-20261028
Draft

docxology wants to merge 10 commits into
mainfrom
codex/chrome-startup-budget-20261028

Conversation

@docxology

Copy link
Copy Markdown
Collaborator

Chrome can remain alive while its CDP port becomes usable after the previous 15-second startup window. That can fail a mandatory live capture before navigation begins.

Raise the startup window to 30 seconds while retaining one monotonic deadline and one browser launch. Add deterministic controls for delayed CDP availability, expiry, and early process exit, and refresh the generated bridge custody and Q7 receipt for the changed source.

Validation:

  • Six new deterministic cases and fifteen existing focused controls passed with zero skips; Ruff and the selected mypy check passed. These local controls use a private resolver harness and do not claim live-browser acceptance.

  • Current bridge custody refresh, Q7 compile, and retained check passed in the fourteen-command profile at source commit 2ebf52a with GNN c08ca28e67bee1b54db33d00489f1acceab8e77b. The receipt references twenty-six existing cached native objects and records twelve fresh probe axiom checks; it does not claim twenty-six fresh cache builds.

  • Integrated main's one-file manual qualification workflow through an ordinary two-parent merge. Four real read-only bridge/emission/Q7 checks passed at 54cfbd4 with tracked bytes unchanged; the native receipt retains its C6 origin.

  • Full automatic PR and merged-main CI, including the mandatory real Chrome cases, remain pending.

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