Ignore navigation-aborted requests in live ops sweep
This commit is contained in:
@@ -71,6 +71,7 @@ Completion criteria:
|
||||
| 2026-03-10 | Full rebuild and redeploy completed cleanly, but the deeper live `ops/policy` action sweep stalled after authentication without writing a result file. This iteration is hardening the sweep itself with per-action watchdogs, progress persistence, and explicit failure semantics so the next scratch loops do not burn hours on a silent Playwright hang. | Developer |
|
||||
| 2026-03-10 | Completed the hardening pass on `live-ops-policy-action-sweep.mjs`: the script now persists progress while it runs, reports blocked actions with step-level snapshots, and exits non-zero on action/runtime failures. After the policy frontdoor fix, the same sweep completed cleanly on the rebuilt stack with zero runtime issues. | Developer |
|
||||
| 2026-03-10 | Hardened `live-frontdoor-auth.mjs` so it waits for a real authority transition or established shell session before declaring authentication complete. This prevents false-positive sign-in clicks on rebuilt stacks where the login form appears asynchronously or the welcome page lingers after the CTA. | Developer |
|
||||
| 2026-03-10 | Tightened `live-ops-policy-action-sweep.mjs` runtime accounting to ignore browser-level `net::ERR_ABORTED` request failures caused by intentional page-to-page navigation. Live rerun confirmed the quotas alerts navigation no longer registers a false runtime issue while the same page/action coverage stays intact. | Developer |
|
||||
|
||||
## Decisions & Risks
|
||||
- Decision: keep this sprint focused on broad route-level live verification and action inventory, not on fixing specific route defects before the rebuilt stack is actually exercised.
|
||||
|
||||
Reference in New Issue
Block a user