feat(readiness): --no-browser flag — skipped browser gates FAIL, never pass #5528
ccantynzAI Reviewcommented 8d ago
AI Triage
(no summary)
Priority: medium Risk area: mixed
Suggested labels: (no label suggestions) Suggested reviewers: (no reviewer suggestions)
Suggestions only — nothing has been applied. The PR author stays in control.
gluecron[bot]🤖 botAI Reviewcommented 8d ago
AI review unavailable
The platform's AI balance is exhausted, so AI generation is temporarily unavailable. Nothing was lost. You can queue this as a repair for the internal agent from the repository's Health page, or try again once the balance is restored. The PR is otherwise unchanged.
Cross-repo impact
See what breaks downstream if this PR merges.
⮌ Merged
This pull request was merged into main.
c comment · e edit title · m merge · a approve · r request changes · ? shortcuts
The owner's Windows box can't launch headless Chromium (180s launch timeout — AV-class interference), which crashed the whole readiness gate. With
--no-browser, render/overflow report FAILED-unverified with an explicit note — deliberately the opposite of the pass-by-skipping trap the privacy/authz gates once had. Today's armed run against live production: provenance, api-json, auth-gate, privacy (3 surfaces), and authz-matrix (142 routes × 3 identities) all genuinely PASS; the two browser gates await a machine with working Chromium.🤖 Generated with Claude Code