test(browser): isolate and await the real zoom extension
This commit is contained in:
@@ -30,6 +30,8 @@ The initial zoom recovery run passed both admin cases but was stopped while wait
|
||||
|
||||
## Scope and gates
|
||||
|
||||
Later integration replay found a remaining zoom-extension lifecycle race after the first four-case pass. The original `integration-03/` attempt was stopped and remains incomplete; its runtime hashes stayed unchanged and its test-source change is explicit. A direct trace records the worker closing before evaluation. The final test harness verifies the generated worker has executed before installing its network guard, permits only that exact local worker URL in addition to its original local routes, and uses short owned temporary paths with cleanup. `zoom-lifecycle-04.json` records all six repeated EN/light and NB/dark real-zoom cases passing with retries disabled. The interrupted `zoom-lifecycle-03` attempt remains partial. No application or geometry assertion changed.
|
||||
|
||||
The sealed security scan through `d52403d` does not include this later delta. Its bounded filters, rate policy, failure-event query and UI were reviewed separately; no new security blocker was identified. This is source review, not a new sealed scan or production acceptance.
|
||||
|
||||
Full cumulative ordinary/specialized browser, final Docling, PDF fidelity, source/runtime closure and local C/D activation remain pending. Historical PDF coordinate-oracle failures, human/device/language/print checks, real AI extraction qualification and production infrastructure debt remain open. No production operation, main merge, deployment or Phase 10 cleanup occurred.
|
||||
|
||||
Reference in New Issue
Block a user