Open-source AI browser agent for Chrome and Firefox (monorepo) π§
WebBrain quality audit β 2026-10-07 onward
Publication note for the proposed 40.2.0 release: this is the complete dated audit, with personal-contact/draft identifiers generalized and local evidence links rendered as archive references. Raw traces, credentials, screenshots and private receipt archives remain local and are not included in Git. Historical references to uncommitted changes, source revisions and line numbers describe their recorded snapshots. The isolated regression sources are included; run npm run test:coverage to reproduce the default suite. This documentation entry does not publish a release or change the tested 40.0.8 runtime version.
Updated 2026-10-11 (Europe/Istanbul). The user's latest instruction authorizes fixing the already established open defects and directly related findings encountered while fixing them. It supersedes the earlier report-only freeze. No new broad defect search is being conducted. The historical failed tests, live traces and HOLD results below remain preserved; they are not relabelled as passes for the new code.
October 11 authorized fixes and current validation
The current working tree includes the following paired Chrome/Firefox fixes. They are general workflow, ownership, completion and data-delivery changes; none is a special-case patch for one Bluesky button or one test account.
| Established problem | Resulting behavior | Focused evidence |
|---|---|---|
| Reused chat drafts reported an uncertain Enter submission as not uncertain | Public dispatch and uncertainty reflect the actual submission; pending-send and duplicate-send protections remain | 10/10 causal regression cases; 215/215 related cases |
| Native commit acknowledgement lost completion provenance after an interrupted observation | Exact acknowledged dispatch provenance survives for independent read-only reconciliation; acknowledgement alone still cannot prove a remote effect | 110/110 related checks; 16/16 installed historical editor, deletion and navigation cases |
| Planner reference history contaminated the current task with a previous arithmetic goal | A fresh, task-bound alignment check permits at most one replan, with normal non-execution routing and cancellation/steering checks | 308/308 related checks; 102/102 planner cases |
| Native chat pane/alias repair instructions could be ignored and a finished partial run promised an unscheduled continuation | App-owned one-use read preparation runs through ordinary guarded tools; partial/failed unscheduled chat endings state that the run ended, in all 23 UI languages | 84/84 current actual-loop cases; 246/246 related chat/steering cases; 291/291 earlier related cases |
| Complete table answers sampled rows and changed literal Unicode | Native table projection preserves document order and literal strings, issues a task-owned reference, and rereads the source before complete JSON delivery | 32/32 paired schema/native browser tests; all 172 literal rows checked through ordinary Agent extraction and terminal batch |
| Privacy text implied settings/default data behavior inconsistent with the product | 22 localized landing pages disclose local/cloud choices, default eligible-data sharing and its Settings opt-out | All 22 pages generated; 9/9 web build tests |
The table repair also closes directly related presentation defects. Verified JSON bypasses display-text repair, progress-ledger prose, partial-chat prose and the publication disclaimer; ordinary prose summaries retain those notices. Partial/failed exact-table endings still expose truthful runEnded/autoResumeScheduled flags. Complete JSON is explicitly limited to the existing 30,000-character terminal capacity, including escaping; oversized results fail before a complete reference is issued. The native scan remains bounded to 10,000 rows and 2,000,000 cell characters. Complete table JSON within the delivery bound survives tight persistence and cold replay unchanged. The journal's 64/64 tests passed; recognition changes formatting retention only, never success or execution authority. A late awaited chat-model refresh now rechecks the original document/thread authority before repair scroll or identity-click dispatch; its whole-file causal result was 70/78 before and 78/78 after. Before the final task-ownership correction, the combined table, native browser, chat-repair and journal files passed 174/174, without skips or cancellations. The final ownership-related chat/steering run below passed 246/246.
The final ordinary unfiltered npm.cmd run test:coverage completed with exit 0 at 2026-10-11 01:47:53 UTC. It passed 9,765/9,765 Node/main cases (7,315 Node cases across 23 groups plus 2,450 main cases), with no failures, skips or cancellations, plus 14 UI checks, 80 custom recipient checks and the separate 60-case security corpus. All 21 installed browser stages and all 54 selected fresh siblings passed, including the complete 15-case WhatsApp matrix. Selection restoration and the offline relevance benchmark also completed; measured relevance remains 55.4% at rank 1, 87.5% at rank 5 and MRR 0.685, with 21 top-five misses. Full-chain C8 coverage is 65.16% lines/statements, 78.74% branches and 87.25% functions; 518 authored entries are inventoried and 106 remain uncovered. All 18,077 source/test/package inputs and authority stayed stable, all 1,182 current product files match the frozen source map, and complete before/after archive inventories (946/951 files) verify byte-for-byte. Post-test shipping parity separately matches all 603 Chrome and 579 Firefox source/build files. Independent finite full7 review is CLEAN: all 54 fresh siblings, 1,897 archived files, raw counters, coverage inventory and source/authority joins match the saved evidence. This qualifies the current default isolated suite, build and measured coverage; it does not qualify a real-model user-Chrome task, two-hour conversation endurance or a new GitHub scan of uncommitted changes. The earlier aborted/failed invocations below remain preserved with their original results. Final full-suite terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-consolidated-full-coverage-final7-20261011-3dfe863b-f8fa-437c-84de-891f51ae7164/terminal.json), complete current stage/coverage/archive qualification (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-consolidated-full-coverage-final7-20261011-3dfe863b-f8fa-437c-84de-891f51ae7164/finite-full7-coverage-qualified-readonly.json).
The current whole 15/15 installed WhatsApp matrix passed once in 222.312 seconds with zero external messages. Both latest-read variants consume exactly one app-owned AX/scroll/observation sequence, with one actual scroll and a certified skipped model scroll counted separately in the prepared variant. Existing one-reply, one-submission, native delivery receipt, pending-null, successful completion, Stop, steering, peer switch, floor and restart assertions remain. All 18,077 source/test/package inputs, 1,182 products and authority stayed stable. The fixture manifest retains 147 of 148 original assertion lines verbatim; only model-proposal counting became actual-execution counting, with stricter ownership/phase checks added. This qualifies the isolated 15-case matrix; it is not an authenticated-account, endurance or full coverage claim. The final current-source CI command also passed its 14 scenarios and cloud capture with the same complete stable maps. Independent matrix closure review is CLEAN. The ordinary unfiltered full6 coverage invocation naturally closed with exit 1: all 7,315 Node tests across 23 groups, 14 UI checks, 80 custom recipient checks and all 21 installed stages passed, including all matrix siblings. The 2,450-case main file then returned 2,448 passes and two failures: its English/Turkish trust-rail expectation still required the inaccurate old no-telemetry claim, and its static done-summary matcher still required the old unconditional display-repair line. Independent bounded source review confirms both are obsolete test contracts, with all raw semantic gates and current verified-data-reference authority intact. Only those three exact expectation strings in test/run.js changed; every other byte and assertion is retained and the inverse is verified. The ordinary whole main file then passed 2,450/2,450 once with all 18,077 source entries, 1,182 products and authority stable. Current whole-main receipt (local evidence: ci/artifacts/quality-audit-2026-10-07/known-current-terminal-privacy-main-green-3e761337-0c0e-4cfe-ada4-0b1eaf183bc3/terminal.json). Independent exact-edit and whole-main closure review is CLEAN. The distinct ordinary unfiltered full7 capture subsequently closed with exit 0 and passed the complete default chain, as recorded above, with product/test/package inputs frozen. Full7 invocation (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-consolidated-full-coverage-final7-20261011-3dfe863b-f8fa-437c-84de-891f51ae7164/invocation.json). Source/product/authority maps were stable throughout full6; all 836 before and 946 after archived files and exact filesets verify. Its coverage 65.12% lines/statements, 78.67% branches and 87.25% functions is partial because restoration, benchmark and security tails were not reached. Preserved failed full6 terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-consolidated-full-coverage-final6-20261011-d8aa6c5d-c4e6-4376-9ed8-13538ad2491f/terminal.json), finite stages, archives and exact two causes (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-consolidated-full-coverage-final6-20261011-d8aa6c5d-c4e6-4376-9ed8-13538ad2491f/finite-failed-full6-stages-archives-and-main-causes-readonly.json), reversible three-string main fixture manifest (local evidence: ci/artifacts/quality-audit-2026-10-07/known-current-terminal-privacy-main-fixture-9421f1ef-0513-479b-b321-8cfeb824958b/recorded-current-contract-edits.json). Qualified matrix and reversible fixture proof (local evidence: ci/artifacts/quality-audit-2026-10-07/known-whatsapp-current-contract-full-matrix-ebea9539-d0bf-4a30-a3af-759b666313a9/fixture-and-full-matrix-qualified-v2.json), final V2 fixture manifest (local evidence: ci/artifacts/quality-audit-2026-10-07/known-whatsapp-latest-repair-current-contract-fixture-fd8d2556-90f3-47e0-8b6e-76674588285e/recorded-current-contract-edits-v2.json), current final CI terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-final-current-ci-80889a4c-1943-4860-b0c7-8ce3edbacf73/terminal.json).
The ordinary unfiltered npm.cmd run test:coverage final3 attempt closed with exit 1 after 7,011/7,011 Node tests, 14 UI checks and 80 recipient/upload checks passed. Installed full-form stage 1 submitted exactly once through 97 passive counter ticks. Installed mid-run stage 2 exposed a directly related task-ownership defect: after accepted task replacement, a stale private chat-read repair synthesized a skipped result for the first revised calculation, causing two calculation proposals/results instead of one. Only one original native observation and one actual calculation dispatch occurred; no chat mutation occurred. The exact-one fixture is unchanged. Paired Agent now retires private read preparation at applied steering and checks the private record's current ownership, document/thread, original signal, age and unused state before all three preemption paths. Stale admission only clears the pending repair, preserving same-task once history and pending-send receipts. The related paired chat/steering files passed 246/246, including six new ordinary-batch task-replacement and stale-document cases. Stages 3β21 and later default tails were not reached by the preserved failed invocation. All 18,077 source/test/package inputs and 1,182 product files stayed stable during that invocation. Coverage 40.91% lines/statements, 69.97% branches and 57.70% functions is partial, not a full-suite qualification. Preserved failed terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-consolidated-full-coverage-final3-20261011-4908d171-cd2b-4c50-b17b-60d1553ce52e/terminal.json), independent saved cause evidence (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-consolidated-full-coverage-final3-20261011-4908d171-cd2b-4c50-b17b-60d1553ce52e/finite-failed-coverage-and-stage2-cause-readonly.json), 246-case related log (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-stale-read-repair-final-related.log).
After the ownership correction, the unchanged installed mid-run fixture passed once: two original task requests, one original native read, exactly one revised calculation proposal/result, then done; revised calls and results are exactly calculate, done. Both live and persisted success flags are true, discarded old proposal IDs remain absent, and mutation counters remain zero. Complete source/product maps and authority remained stable. Qualified focused stage 2 receipt (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-focused-installed-midrun-after-repair-20261011-ef5af229-8562-481f-9b44-ee9ad3201137/focused-stage2-qualified.json). The distinct ordinary unfiltered final4 coverage run closed with exit 1 after all 7,017 Node tests, 14 UI checks and 80 recipient/upload checks passed. Installed stages 1 and 2 passed; stage 3 retained its original native read but failed the older one-read count after app-owned alias preparation produced three reads and two private read-only click acknowledgements. Menu opening occurred once, mutation counters were zero, and both success flags remained false. A separate evidence-only focused RED retained every original assertion and captured exact open_menu β open_self_settings β already-consumed Settings phase/ref transitions. Two distinct first-use private bindings, unchanged owner, stable monitor UUID and separate AX document token, plus identical native URL/epoch/peer/empty composer establish a legitimate bounded recovery. The diagnostic cross-namespace document comparison remained false in that preserved RED and is corrected in the fixture comparator; it is not a production document-mismatch finding. Independent review concurred with exact three-read/two-control assertions, preserving one menu opening, zero mutations and false success flags. Stages 4β21 and default tails were not reached. All source/product bytes and authority remained stable. Its 40.91% line/statement, 69.99% branch and 57.72% function coverage is partial. Preserved failed final4 terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-consolidated-full-coverage-final4-20261011-7f650cab-572c-4a1c-9879-a1601fe8d2f5/terminal.json). Preserved diagnostic RED (local evidence: ci/artifacts/quality-audit-2026-10-07/known-cold-native-repair-contract-focused-red-88fdb996-5d9f-4c7c-97a3-67a990d0a5e9/terminal.json).
The final cold-start fixture passed once after the test-only current-contract update. It asserts exactly three observations and two distinct, once-used private controls, stable AX and monitor namespaces separately, identical native document/peer/empty composer, the first original observation retained, stale model proposals not dispatched, one menu opening, zero mutations and false completion flags. Of the original 18 assertion code-lines, 16 remain verbatim; only the exact read/control counts changed, with stricter phase/reference/ownership assertions added. Provider outcomes and product code were unchanged. All 18,077 inputs, 1,182 products and authority remained stable during execution. Qualified focused stage 3 receipt (local evidence: ci/artifacts/quality-audit-2026-10-07/known-cold-native-repair-contract-focused-green-87a9c75a-e93e-46df-8b9f-fd1e85b2919b/focused-stage3-qualified.json), reversible fixture/assertion manifest (local evidence: ci/artifacts/quality-audit-2026-10-07/known-cold-native-repair-current-contract-fixture-f053a177-7879-4e22-817e-62f328eb84df/recorded-current-contract-edits.json). The fresh ordinary unfiltered final5 coverage run closed with exit 1 after all 7,017 Node tests, 14 UI checks, 80 recipient/upload checks and installed stages 1β5 passed. Stage 6 WhatsApp matrix passed its first two cases, then its native_scroll_latest fake provider asserted that its last result must still be get_accessibility_tree. The recorded app-owned sequence had already completed the exact issued-pane AX read, one bottom scroll and a fresh same-thread observation of two current incoming messages with no remaining repair hint. The obsolete model handoff failed before any send; no reply, Enter, send-button click or pending clear occurred. The final V2 fixture consumes only this exact already-executed recovery and counts the one actual recorded scroll, distinguishing the certified skipped model proposal, while preserving every delivery, pending-send, one-submission and completion requirement. The remaining 12 matrix cases and installed stages 7β21 were not reached. Complete source/product maps and authority remained stable. Coverage 40.91% lines/statements, 69.99% branches and 57.72% functions remains partial. Preserved failed final5 terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-consolidated-full-coverage-final5-20261011-bc1a60b4-fe03-461e-bbdd-3b9e474bd876/terminal.json), sealed stage6 cause and complete archive review (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-consolidated-full-coverage-final5-20261011-bc1a60b4-fe03-461e-bbdd-3b9e474bd876/finite-failed-coverage-and-stage6-cause-readonly.json).
Two earlier October 11 attempts were explicitly aborted for related table presentation corrections, with their stable source maps and outputs retained; neither is a full-suite pass or a test-failure qualification. Current standalone release checks passed: DOM fixtures 283/283, CI 14 scenarios plus cloud capture, web build 9/9 and the 22-page landing build. No tests or package scripts were removed or disabled. The latest normal npm.cmd run build:all passed with complete matching source/build inventories: 603 Chrome and 579 Firefox files, all 1,182 pairs byte-identical and source/package/lock/protected script hashes stable. This is build evidence, not a loaded-user-runtime claim.
Focused evidence: table/chat/journal 174-case log before the last ownership correction (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-final-table-chat-journal-green.log), current paired normal build receipt (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-final-normal-build-05dfd144-31b9-4887-a5ab-e980cc64f9e5/receipt.json), chat submission causal proof (local evidence: ci/artifacts/quality-audit-2026-10-07/chat-send-submission-outcome-fix-f2c144c3-8b6d-432a-a11f-29f19e6fdc40/proof.json), completion historical regression receipt (local evidence: ci/artifacts/quality-audit-2026-10-07/known-completion-fixes-historical-20261011-1/validation-final.json), chat ownership await-boundary proof (local evidence: ci/artifacts/quality-audit-2026-10-07/owned-chat-read-repair-await-boundary-9d8b3593-498e-43a6-8a1c-9552d0fc5950/proof.json), CI log (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-20261011-ci.log), unstarted real-model replay closure (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-live-table-actual-kfix_ac2f9e920e2a4bc681ad7cf211e80605/closed-without-submission.json).
The new real-model table replay was not submitted. Computer Use stopped because it could not confidently determine the current Windows Chrome URL. No alternate control route was attempted. Its observer remained unarmed and its owned local fixture listener was closed. Accordingly, the isolated native browser/ordinary Agent tests qualify code behavior; they do not establish that the new code has completed a real-model task in the user's loaded Chrome. The previous two-hour Telegram producer remains HOLD before the timed phase, with zero timed questions/replies; it was not restarted or claimed as a pass.
Final authenticated read-only GitHub verification at 2026-10-11 01:46:15 UTC still shows 77 open high-severity Code Scanning alerts, all on scanned main commit 6da190593be3990dceb83396fb42b9e779ef9f1e. A fresh remote-main lookup returns that same commit. Final read-only alert/main receipt (local evidence: ci/artifacts/quality-audit-2026-10-07/known-fixes-final-code-scanning-readonly-828f199c-9dd9-4b2a-a793-1365ff17495b/receipt.json). The earlier per-alert review records 36 locally addressed/mitigated findings and 41 conditional trust cases. GitHub has not scanned these uncommitted fixes, and no alert was dismissed or closed. GitHub Code Scanning.
No new account, external message, post, channel or avatar change was made in this repair turn. The earlier authorized avatar change was to Vatansever Cephe, channel UCVB3sGJ6VIKsYN4W2SeTMgQ. The originally supplied UC2nx channel remained inaccessible and unchanged. Existing owned QA accounts and the Telegram producer's once guard remain tracked in the historical evidence below. Nothing has been staged, committed, pushed, released or deployed.
Historical validation through Source71
Statements below about a report-only freeze, unapplied candidates, current Source71, open code defects or earlier coverage failures describe the historical audit state. The October 11 fix and validation section above supersedes that state; all old trace evidence retains its original qualification.
The branch is codex/quality-audit-2026-10-07. HEAD and remote main remain 6da190593be3990dceb83396fb42b9e779ef9f1e, verified by read-only upstream lookup on October 10. Nothing has been staged, committed, pushed, released or deployed. The original index, protected check-seventeen.mjs, package script contract and user changes are preserved.
ProductSource71/RepositorySnapshot79 is the latest applied and normally built snapshot. Four reviewed files changed: the Chrome CDP client, paired page monitors and the native preparation ownership fixture. Native no-button movement can remain preparation while its acknowledgment is pending; a privately guarded selector scroll can precede it without pretending that a real button press occurred. Existing complete target/action checks remain, and real-input history survives finish and later fences. The exact same159-test file reproduced five passive-preparation failures plus the parent on Source70 (153 passed) and passed159/159 on the candidate, with no skips, cancellations, filters or retries. One historical held-counter refusal leaf was intentionally amended; all original bytes outside that leaf remain. Root and an independent reviewer verified all18 byte regions before application. Normal build exited zero with all602 Chrome and578 Firefox build files matching source bytes; all18,074 recorded inputs and original authority remained stable. Ordinary unfiltered full C8 execution9 exited1 at installed stage12 after stages1β11 passed. All6,882 Node cases,14 UI checks and80 recipient-upload checks passed; the full suite is not qualified. Source71 has now been normally reloaded and bound to the user Chrome runtime; the current native mid-run replacement independently passed; owned-bot bootstrap failed without a send and real120 was not started.
Source71 four-file application (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-reviewed-pointer-preparation-actual-045f3043-6e92-455e-a471-a693d855e46e/actual-application.json), Source71 normal paired build (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-normal-build-only-actual-26a7d036-5145-4f61-b071-67baeb0825df/result.json), independent physical application/build review (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-application-and-normal-build-independent-recent-readonly.json), same-file causal evidence (local evidence: ci/artifacts/quality-audit-2026-10-07/native-pointer-preparation-phase-candidate/proof-final-v9.json), independent candidate review (local evidence: ci/artifacts/quality-audit-2026-10-07/native-pointer-preparation-phase-independent-historical-readonly-final-v9.json), execution9 failed terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-isolated-normal-coverage-before-real120-execution9-actual-bdc4e8c0-d121-48b0-a7a9-1d539af67201/terminal.json).
Source71/Repository79 C8 execution9 ran from17:37:29.438 to17:56:32.294UTC. The formerly failing full form submitted exactly once while159 passive counter ticks occurred. The complete15-case WhatsApp matrix, saved-byte and file-accept upload checks, and20-row Stop/Continue workflow also passed. Stage12 stopped in the first rich-editor case of the literal/frame fixture: its native Save click was acknowledged, but subsequent observation reported a nonretryable unknown outcome. Actual isolated evidence contains one application save and matching authorized, persisted and rendered body SHA256; the fake provider stopped on the uncertain tool result before independently reconciling that receipt. The provider treats every tool error as fatal, including this exact read-only recovery instruction; a narrow fixture-only reconciliation is prepared but remains unapplied under the user constraint. The nested frame and Trusted Types cases were not reached. Later nine installed stages and main/security tails were not reached by this C8 invocation. All18,074 input bytes and authority stayed unchanged. Coverage40.66% lines/statements,69.45% branches and57.32% functions is partial and does not qualify the full suite. The failed result and original stage outputs are preserved; no unchanged retry is running. An independent review verified1,672 preserved files (822 before and850 after), fresh stage outcomes and exact source/authority stability. Later installed stages were checked through separate ordinary diagnostics, each stopping on its first failure; these cannot turn the failed C8 invocation into a pass.
Independent execution9 review (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-isolated-c8-execution9-independent-historical-readonly.json).
The separate ordinary installed-tail diagnostic passed stage13 (publication) and failed stage14 (deletion), with stages15β21 not reached by that invocation. Only one actual owned DELETE occurred; a subsequent resource read returned404 and a fresh profile showed no post. The independent completion judge returned succeeded. However, the fully acknowledged native confirmation click had an interrupted-observation unknown result, so semantic submission tracking omitted its dispatch record. Completion consequently treated the unrelated persistent composer as an unverified relevant form and restricted success. The deterministic provider also ignored the current tool schema and repeatedly emitted done(success), ending with invalid arguments. This is a WebBrain completion/provenance mismatch plus non-adaptive fake-provider recovery; neither is being changed under the latest user constraint. All source/authority bytes remained unchanged;46 archived files preserve the separate diagnostic.
Separate tail13β21 review (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-isolated-installed-tail13-21-actual-review-historical.json).
Root normally reloaded Source71 in the user Chrome session after verifying21 idle tabs and zero active jobs. The previous Main8215 closed, new Main8307 has timeOrigin1791655714556, and bot148 was refreshed normally. Actual served30 module hashes plus a separate same-epoch Scheduler hash match all corresponding source/build bytes. The pure physical verifier confirmed all1,180 product and18,074 repository inputs, with602 Chrome/578 Firefox files and unchanged before/after Main identity. An independent reviewer confirmed the runtime binding. It establishes loaded-source correspondence; task success is separately measured.
Actual Source71 runtime binding (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-main8307-source-proof-actual-89524793-1835-4e02-aef9-477e352781b3.json).
The separate later diagnostics reproduce the same completion/provenance false negative in stages16 (first dropdown-menu case),17 (deletion followed by navigation), and18 (first delayed semantic-navigation case). Each genuinely deleted the owned fixture item once and reached current404/profile absence with a positive judge, but interrupted native readback left submission provenance missing. Stages14/16 fake providers ignored the restricted tool schema; stages17/18 ended normally with partial. Stage15 anchored-action passed, including zero foreign menu clicks. Matrix siblings not reached remain untested. No outcomes or source/model/default-fixture behavior were changed.
Stage14 causal diagnosis (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-native-deletion-completion-mismatch-readonly-diagnosis.json), stage16 causal note (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-dropdown-menu-completion-mismatch-readonly-note.json), separate15β21 review (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-isolated-installed-tail15-21-actual-review-historical.json), separate17β21 review (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-isolated-installed-tail17-21-actual-review-historical.json), separate18β21 review (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-isolated-installed-tail18-21-actual-review-historical.json).
Later installed stages19β21 passed separately once: four workflow cases, three media-upload cases and worker restart/ownership checks. Stage21 recorded two attempted external requests, both route-aborted, and zero external messages. Separate normal main/security tails passed2,450/2,450 main checks, Chrome/Firefox selection restoration, offline benchmark existing floors and60/60 security corpus cases. Benchmark retains21 top-five misses across168 queries/251 passages (55.4%R1,87.5%R5,MRR0.685). One QA runner initially stopped before the benchmark because that script was intentionally outside the18,074-input map; the error remains preserved, the script was separately pinned, and already-passed main/restoration checks were not repeated. All four normal commands ran once and current product/source/index/protected authority stayed unchanged. These passes do not relabel failed full C8 execution9 or the failed deletion/completion cases.
Separate installed19β21 review (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-isolated-installed-tail19-21-actual-review-historical.json), separate main/security tail review (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-separate-main-security-tail-independent-historical-readonly.json).
Current Source71 native task replacement passed independently in17.787 seconds (18:20:33.505β18:20:51.292UTC). Root physically entered the270-character own-bot inspection task, then197-character replacement with Alt+Enter after an actual MAIN thinking event. Exactly one revision applied, zero old tools executed, and calculate returned86419752308641975230.125 before a separate normal done. Live and persisted status both show successful completion. Before/after native reads retain the same bot document, only Start message6672 and an empty editor. One original Return/one correction Alt+Return and zero public business requests are independently pinned. The raw observer/input passed:false fields remain intact; the qualified result adds independent evidence. Root callback result assignment failed after both inputs and exclusive ledger writing; the written ledger was read without retry. Accepted RPC timestamp/original MAIN response ordering and protected Saved Messages drafts are not separately qualified.
Current native replacement (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-native-midrun-attempt1-root-qualified-actual-94194c47-b2ed-4f9e-b885-2dd0b0c5b7b1.json), independent native replacement review (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-native-midrun-attempt1-independent-recent-readonly.json), independent loaded-source review (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-main8307-source-binding-independent-historical-readonly.json).
The current owned-bot bootstrap ran once for27.050 seconds, with the newly authored task anchor preserved. The freshly generated approved plan combined the previous arithmetic goal with the new bootstrap marker; that marker did not exist in prior messages. This is observed new planner wrong-goal/history contamination, amplified by confidence0.99 automatic approval. The main model followed that plan and first tried done(success) with the old arithmetic answer plus the new marker, which the completion judge correctly rejected. It then ignored the exact native alias-repair instruction (read and open the current profile), placed the issued profile ref in rebind_thread_key, repeated chat_observe and ended failed with the old arithmetic answer. Source resets of steering/current task and retirement of the earlier approved plan were retained; stale privileged steering state is not established. Exact raw planner provider request/response was not retained, so precise model causation or prompt weighting remains an inference. There were zero chat_send calls, zero physical submissions and no new native bot message; the same native document remains Start-only with empty composer. Failed evidence and private raw responses are preserved. No planner/model/product repairs, retry, API delivery receipt or real120 controller were attempted. Full C8 PASS was an earlier scheduling preference, not a bootstrap/controller guard; actual bootstrap success remains the unfulfilled prerequisite for the legacy strict real120 route. The distinct normally submitted UI test has separate prospective ownership and receipt checks.
Current bot bootstrap failure (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-bot148-bootstrap-public-safe-actual-ba410f89-303c-4469-97fe-a5ff6170684a.json), report-only bootstrap diagnostic (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-bot148-bootstrap-report-only-diagnostic-actual-4eae5bd6-dacb-406d-a22d-d511dc5e0100.json), independent wrong-goal planner diagnosis (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-bot-wrong-goal-report-only-diagnosis-historical.json).
Current Source71 WhatsApp self-chat read-only testing independently qualified one native Return, one fresh chat_observe with empty rebind/pending keys and reconciliation disabled, then a separate normal done. Actual saved tool results show current self thread dom:whatsapp:self:c14943a7, available empty composer, no pending outbound and done=true/outcome=success; the exact completion decision is llm/succeeded, vision, openai/gpt-5.4-mini. Both live and stored successfulDone/runSucceeded are true. Native Return acknowledgment to run_complete took27.220 seconds. Before/after native reads retain the same document, epoch, self header, newline editor digest and three mounted message IDs at the latest viewport. After was captured296.021 seconds after run_complete, so this proves snapshot preservation, not an immediate terminal or full-history trace. No messages were sent. The raw observer passed:false/protocol:false fields are preserved: the QA observer missed the stored untrusted_page_content wrapper and omitted the positive succeeded enum. Root and an independent reviewer separately decoded the exact paired wrappers and verified the original fields without changing the executed observer or rerunning the task. This qualifies current read-only identity/observation/completion only, with31 served hashes and1,180/18,074 source/build inputs bound; no delivery, endurance or full C8 claim.
Current WhatsApp Root qualification (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-whatsapp-self-readonly-root-qualified-actual-9dbce3a9-c1a7-4121-baf5-6b919502ee4e.json), independent WhatsApp review (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-whatsapp-self-readonly-independent-recent-readonly.json), preserved raw observer (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-whatsapp-self-observer-terminal-actual-101a8a7d-962f-41c4-bfba-641082084c20.json).
Source70/RepositorySnapshot78 is prior evidence. Seven reviewed files changed: paired Agent/Scheduler implementations, appended lifecycle regressions and two existing download/upload fixtures. The normal build exited zero with exact602/578 parity. Ordinary unfiltered full C8 execution8 exited1 at the first installed form test, despite all6,849 Node,14 UI and80 recipient-upload checks passing. This failure remains preserved.
Source69/Repository77 remains prior evidence. Repository77 changed only the installed download fixture. Its general arithmetic-task replacement classifier recognizes a complete explicit replacement instruction and narrowly negative chat restrictions, after the existing planner read-scope and deliverable gates. It adds no receipt, permission or completion evidence. The whole same-source regression reproduced six failures (392/398 passed) before the repair and passed398/398 afterward, preserving prior tests and no-receipt negatives. The actual Source69 user-Chrome runtime served30 matching modules and was physically bound to the complete1,180-product/18,074-input maps. Its actual native mid-run task replacement passed; this does not establish Source70 loaded execution or endurance.
Source70 seven-file application (local evidence: ci/artifacts/quality-audit-2026-10-07/product70-repository78-reviewed-scheduling-and-fixtures-actual-6f04bc8e-383d-41b0-8bc0-3eda2cb77666/actual-application.json), Source70 normal paired build (local evidence: ci/artifacts/quality-audit-2026-10-07/product70-repository78-normal-build-only-actual-146cf2a6-7546-423e-aba0-09a724ecc284/result.json), independent physical application/build review (local evidence: ci/artifacts/quality-audit-2026-10-07/product70-repository78-application-and-normal-build-independent-recent-readonly.json).
Source68 remains prior evidence. RepositorySnapshot75 additionally applied one fixture-only verification phase correction; all1,180 product files stayed unchanged from the Source68/Repository74 normal build. Its two-file repair keeps app-owned contact read-repair actions on the existing private content path even when the Close control is a native BUTTON. The corrected paired ownership fixture passed28/28; its same-source baseline failed the new Chrome leaf and its parent. Normal npm.cmd run build:all exited zero, all602 Chrome and578 Firefox files matched their source bytes, and18,074 recorded inputs and original authority remained stable. The complete isolated installed WhatsApp contact matrix passed15/15 in227.345 seconds, with603 source files stable and zero external messages. This qualifies the controlled matrix, not an authenticated WhatsApp account or endurance.
Source67 remains separate prior evidence: the applied installed full-form submitted exactly once while99 passive counter updates occurred; its normally reloaded runtime had30 served hashes bound to the complete1,180-file source/build maps, and native download615 preserved the exact requested filename and PNG bytes. Source67 C8 execution4 exited1 at installed WhatsApp stage6 after stages1β5 passed. The prior normal Source68 user-Chrome reload and Main8205 were verified:30 served hashes match source/build bytes and the full1,180-product/18,074-input maps, with unchanged document identity and authority. This is runtime binding, not successful task execution. Full C8 execution5 exited1; the real120-minute run has not started.
Source66/Repository70 ordinary unfiltered core validation remains separate prior evidence:40 planner,98 URL/recipient security,117 default network/download lifecycle and2,450 main checks passed. Repository71/72 only corrected two existing test fixtures; its1,180 product files and normal build bytes were reverified unchanged. These results are not relabelled as Source67.
Source68 actual contact-routing application (local evidence: ci/artifacts/quality-audit-2026-10-07/product68-repository74-reviewed-contact-routing-source-only-actual-1ef5bfb9-0b25-4e7a-ab45-e5c7aa17da08/actual-application.json), independent application and security review (local evidence: ci/artifacts/quality-audit-2026-10-07/code-scanning-product68-repository74-current-local-reconciliation-independent-historical-readonly.json), Source68 normal paired build (local evidence: ci/artifacts/quality-audit-2026-10-07/product68-repository74-normal-build-only-actual-ca63221d-25d9-4e0b-9eca-5c8fd27d5da7/result.json), independent build review (local evidence: ci/artifacts/quality-audit-2026-10-07/product68-repository74-normal-build-independent-recent-readonly.json), derived build-bound product map (local evidence: ci/artifacts/quality-audit-2026-10-07/product68-repository74-derived-build-bound-product1180-map-readonly.json), complete installed WhatsApp matrix (local evidence: ci/artifacts/quality-audit-2026-10-07/product68-repository74-whatsapp-contact-matrix-actual/summary.json). The derived map is not a served/runtime proof.
Applied pointer preparation repair (local evidence: ci/artifacts/quality-audit-2026-10-07/product67-repository73-reviewed-pointer-completion-source-only-actual-9eb5a286-e6e6-4103-844f-12d8b06e7162/actual-application.json), Source67 normal paired build (local evidence: ci/artifacts/quality-audit-2026-10-07/product67-repository73-normal-build-only-actual-c6c611f7-9daf-4b8f-bdc0-0c49ff437bca/result.json), independent two-file review (local evidence: ci/artifacts/quality-audit-2026-10-07/native-button-pointer-operation-independent-historical-readonly-final-v2.json).
Prior Source66 ordinary core (local evidence: ci/artifacts/quality-audit-2026-10-07/product66-repository70-ordinary-core-actual-a96a213a-0534-42fe-bf89-64cd28d9d1a3/result.json), normal paired build (local evidence: ci/artifacts/quality-audit-2026-10-07/product66-repository70-normal-build-only-actual-2a4bbc88-4dbf-44d4-a82f-85902ceb7d9d/result.json), independent validation (local evidence: ci/artifacts/quality-audit-2026-10-07/product66-repository70-ordinary-core-and-normal-build-independent-recent-readonly.json).
Source65 affected page-feedback validation remains separate historical evidence: 2,446 Node checks, 36 WhatsApp Node checks and 80 recipient-upload browser checks passed. Its native draft-recovery run passed 108 Node and five installed cases with zero external messages. These were not rerun or relabelled as Source66.
The last complete coverage qualification remains historical Product45/Repository49: 6,706 Node cases, 2,448 main checks, 60 security checks and all 21 installed stages passed. Coverage across 514 authored files was 64.99% for lines/statements, 78.44% for branches and 87.10% for functions. These percentages remain historical. The first Source66/Repository70 normal coverage command exited1 with four obsolete fake-model prose response failures. Its nine completed Node groups totalled 4,500 cases, 4,496 passed and four failed, with no skips or cancellations; none of the 21 installed stages was reached. Partial coverage was 37.73% lines/statements, 67.34% branches and 56.19% functions across 516 authored files and cannot qualify the whole suite. Only the fake model response was updated to the existing strict final_text envelope, preserving all 164 assertion-containing lines. The whole lifecycle file then passed 80/80. Execution2 on Repository71 passed 6,713 of 6,714 Node cases plus 14 separate UI lifecycle checks; it stopped before installed stages because an iframe fixture read the previous preparation reply before an asynchronous dispatch callback. That failure occurred before the production fallback or its scrolling checks ran. Repository72 replaces a fixed 150ms setup delay with observed DOM feedback and awaits the actual prepare/dispatch callbacks, retaining all 325 assertion lines and adding two readiness assertions. Execution3 passed all 6,750 Node cases, 14 UI lifecycle checks and 80 recipient-upload browser checks, including the corrected iframe leaf. It then failed the first installed full-form stage: no submission occurred after native-button reprobe rejected preparation. Later 20 installed stages and remaining main/security stages were not reached. Partial coverage was 40.52% lines/statements, 69.29% branches and 57.07% functions; no current whole-suite success is claimed. A capture-only ordinary reproduction and a separate C8-wrapped reproduction both submitted exactly once and passed, with matching native preparation fields; the initial failure did not record those fields, so its exact cause remains under investigation.
Historical complete coverage (local evidence: ci/artifacts/quality-audit-2026-10-07/product45-repository49-normal-coverage-execution2-actual-97db1f11-20de-48a1-9fab-48a6c745e40d/observed-summary.json).
Source68/Repository74 full C8 execution5 ran the ordinary unfiltered command from14:13:04.559 to14:21:30.755UTC. Node totals were6,729:6,727 passed and two failed (one Firefox leaf and its parent), with14 separate UI checks passed and zero skips/cancellations. The custom recipient80, all21 installed stages and main/security tails were not reached. All18,074 inputs and original authority remained stable. Partial coverage is40.47% lines/statements,69.06% branches and57.06% functions; it does not qualify the whole suite. The failing test injected physical type-and-Backspace before confirming native30ms verification had reached the later80ms stage; production correctly refused unverified rich-text. Repository75 holds only that actual outer callback after its real80ms delay, performs real keyboard input, then releases once. The unfiltered whole candidate passed58/58 across Chrome and Firefox, retaining all80 original assertion-containing lines and all1,180 product bytes. Complete coverage after this fixture correction remains unfinished.
Prior Source68 loaded runtime (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product68-repository74-main8205-source-proof-actual.json), independent runtime binding (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product68-repository74-main8205-source-binding-independent-historical-readonly.json), execution5 failed terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/product68-repository74-isolated-normal-coverage-before-real120-execution5-actual-bf47c764-f2ce-4a29-ab56-f3b0e1451cce/terminal.json), independent execution5 review (local evidence: ci/artifacts/quality-audit-2026-10-07/product68-repository74-isolated-c8-execution5-independent-historical-readonly.json), whole fixture58/58 (local evidence: ci/artifacts/quality-audit-2026-10-07/native-draft-outer-verification-fixture-candidate/whole-file-root-actual.json), independent fixture review (local evidence: ci/artifacts/quality-audit-2026-10-07/native-draft-outer-verification-fixture-candidate/whole-file-root-independent-historical-readonly.json), actual fixture-only application (local evidence: ci/artifacts/quality-audit-2026-10-07/product68-repository75-reviewed-fixture-only-actual-e9bfea81-a10d-4974-b09e-19058d61b562/actual-application.json).
Source69/Repository76 ordinary unfiltered C8 execution6 ran from14:55:28.736 to15:10:15.772UTC and exited1. All6,773 Node cases in11 groups passed, with14 separate UI and80 recipient-upload checks passed and zero skips/cancellations. Installed stages1β7 passed, including the complete15-case WhatsApp matrix; stage8 download-upload failed and the later13 installed stages plus main/security tails were not reached. All18,074 input bytes and authority remained stable. Partial coverage is40.56% lines/statements,69.32% branches and57.13% functions; whole-suite coverage remains unfinished. The failing fixture searches Chrome DownloadItem.url for the original HTTP URL, whereas current staged downloads use a local blob and return the original URL alongside downloadId. This stale predicate cannot identify the native download; the failed run did not retain its browser download rows, so actual successful bytes/upload are not inferred. Repository77 applies the fixture-only receipt/ID correlation repair. The same current Source69 standalone baseline reproduced the exact missing-download assertion; the candidate passed with two native receipt-bound downloads, exact68-byte PNG and611-byte PDF contents/MIME, one remote GET per asset, one exact PDF upload and normal successful completion. All14 original assertion calls remain, with14 added checks and six complete byte inverses. This fixture does not assert saved basename. Root applied only this one fixture, preserving all1,180 product files and every other recorded input/authority. Normal build on Repository77 exited zero with exact602/578 source/build parity.
Repository77 ordinary unfiltered C8 execution7 ran from15:30:37.206 to15:45:46.636UTC and exited1. All6,773 Node,14 UI and80 recipient-upload checks passed, followed by installed stages1β8. The corrected stage8 verified two actual native downloads with exact PNG/PDF bytes and MIME, one PDF upload and normal completion. Stage9 failed the same obsolete native DownloadItem URL predicate in the saved-byte fixture; later12 installed stages and main/security tails were not reached. The whole18,074-input map and authority stayed unchanged. Partial coverage remains40.56% lines/statements,69.32% branches and57.13% functions, without a whole-suite qualification. The remaining saved-byte and upload-accept fixtures were subsequently checked together; the failed stage9 did not preserve sufficient native rows to infer its byte assertions passed.
Execution7 actual failed terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/product69-repository77-isolated-normal-coverage-before-real120-execution7-actual-0191e7e6-bce0-404f-a3e5-7410ed34ad70/terminal.json), independent execution7 review (local evidence: ci/artifacts/quality-audit-2026-10-07/product69-repository77-isolated-c8-execution7-independent-historical-readonly.json).
Source70/Repository78 full C8 execution8 exited1. All6,849 Node cases in11 groups,14 UI checks and80 recipient-upload checks passed, with no skips or cancellations. Installed stage1 failed: the unchanged native Submit button was prepared successfully, but later preparation reported a page-feedback change and no form submission occurred. Stages2β21 and the main/security tails were not reached. Partial coverage is40.61% lines/statements,69.47% branches and57.27% functions; it does not qualify the full suite. This historical recurrence was investigated as a general preparation-timing defect; the unchanged failed result remains preserved. A capture-only isolated diagnostic reproduced initial native preparation success followed by reprobe failure; its first local-veto log was read from the wrong JavaScript world and is not clause-level evidence. A separate corrected ISOLATED reader reproduced the failure and captured one existing beforeLocalDispatch refusal: model binding was invalid with a pending DOM change classified unknown, while layout, prepared binding, user input and local/current/prepared revision remained unchanged. All original production inputs and authority stayed unchanged; the copied monitor differs only by diagnostics inserted after an existing veto is selected. This is a disposable headless form test, not an authenticated account run. The controlled held-pointer-ACK regression and narrow preparation-phase repair were reviewed and applied in Source71 before the latest no-fix instruction. Source71 full C8 subsequently passed this form and failed at stage12, as recorded above.
Execution8 failed terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/product70-repository78-isolated-normal-coverage-before-real120-execution8-actual-4552cd4a-6f69-4d8d-a76f-cbb6f0505cfb/terminal.json), independent execution8 review (local evidence: ci/artifacts/quality-audit-2026-10-07/product70-repository78-isolated-c8-execution8-independent-historical-readonly.json), first preserved diagnostic (local evidence: ci/artifacts/quality-audit-2026-10-07/source70-native-local-preparation-veto-capture-actual-85902406-3864-45f7-85cf-4b0af71916d1/result.json), corrected isolated-world veto (local evidence: ci/artifacts/quality-audit-2026-10-07/source70-native-local-preparation-veto-capture-actual-a65c8537-d62f-4937-8f4c-850868d80e22/evidence/local-veto-log.json), independent corrected diagnostic review (local evidence: ci/artifacts/quality-audit-2026-10-07/source70-native-local-preparation-veto-capture-independent-historical-readonly.json).
Standalone fixture proof (local evidence: ci/artifacts/quality-audit-2026-10-07/staged-download-owned-id-fixture-candidate/candidate-proof-final.json), actual fixture-only application (local evidence: ci/artifacts/quality-audit-2026-10-07/product69-repository77-reviewed-download-fixture-only-actual-9a5ba887-b3a5-4df3-9010-a54e85f5bdb1/actual-application.json), Repository77 normal build (local evidence: ci/artifacts/quality-audit-2026-10-07/product69-repository77-normal-build-only-actual-5822b175-e885-4016-9873-ba16c5b6c278/result.json).
Source69 actual application (local evidence: ci/artifacts/quality-audit-2026-10-07/product69-repository76-reviewed-calculation-replacement-only-actual-97b4facc-ee38-4bef-91da-57f9cc3224f3/actual-application.json), 398/398 same-source regression (local evidence: ci/artifacts/quality-audit-2026-10-07/explicit-calculation-replacement-candidate/revision3/root-whole-literal-execution/green-terminal-actual.json), independent classifier review (local evidence: ci/artifacts/quality-audit-2026-10-07/explicit-calculation-replacement-independent-historical-readonly-revision3.json), normal build (local evidence: ci/artifacts/quality-audit-2026-10-07/product69-repository76-normal-build-only-actual-1714c726-b31a-4c82-bbab-894566dbef36/result.json), actual loaded runtime (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product69-repository76-main8215-source-proof-actual.json), independent loaded-code review (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product69-repository76-main8215-source-binding-independent-historical-readonly.json), execution6 failed terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/product69-repository76-isolated-normal-coverage-before-real120-execution6-actual-8b8a8bc7-aa19-4589-b0ee-94171e1d82ee/terminal.json), independent execution6 review (local evidence: ci/artifacts/quality-audit-2026-10-07/product69-repository76-isolated-c8-execution6-independent-historical-readonly.json).
General repairs
The DOM monitor repairs apply across control families and websites. Existing regressions cover decorative SVG changes, unchanged native controls, app-owned preparation and acknowledged native input amid unrelated rendering changes. Source70 full C8 exposed a remaining false refusal when a passive counter changes while preparatory pointer movement is awaiting its native acknowledgment. Source71 repairs that interval for an exact existing model-bound operation and privately distinguishes its selector pre-scroll from consequential input. The159-case same-file causal comparison passes, including unchanged ordinary buttons and field focus, immediate unreported private-value drift, prior finished input, native wheel, concurrent input and forged public phase arguments. Queued unknown feedback during selector scrolling itself remains conservative; this repair never clears it. Material target, document, recipient, task, frame and human-input changes still invalidate stale authority. Source65 closes an exactly owned, fully acknowledged native press/release operation before read-only network settling; unknown or blocked dispatch does not gain that completion authority. There is no Bluesky-button exception. Current full C8 execution9 failed. Source71 loaded user-Chrome binding, current native task replacement and current WhatsApp self read-only completion are separately qualified; Telegram bootstrap and real-account endurance remain unqualified.
Other applied repairs cover mid-run task corrections, exact calculation completion, current-run output evidence, owned draft recovery before Enter, pending delivery retention, numeric native message floors, scheduler/lifecycle recovery, provider schema handling, and generic file-input ownership/chooser handoff. Localized planner display text no longer becomes executable authority. Earlier failed attempts remain preserved.
A general scheduling cancellation race is repaired in Source70. Agent tools could create a new durable job and alarm after Stop or accepted task replacement during asynchronous tab lookup, conversation persistence or the scheduler storage queue. The repair captures the original run/task owner and serializes new-job persistence, alarm creation and exact-new-job cancellation within the existing queue. Early alarms wait for this commit or rollback before tab setup. If both cancellation persistence and alarm clearing fail, a private hold on only the newly created job blocks waiting and later alarms and manual Run now in that manager; uncertainty remains explicit. An acknowledged cancellation/delete releases the hold. Previously valid duplicate jobs and direct UI scheduling remain covered. The initial146-test causal checkpoint reproduced56 failures on Source69 and passed after its candidate; delivered-alarm regressions then reproduced four more failures before the barrier, and the final combined-cleanup cases reproduced four failures on frozen V4 (152/156) before V5 passed156/156, with no skips or cancellations. All original46,425 test bytes and164 assertion-containing lines remain, plus the earlier new regressions. Root and an independent reviewer checked all51 exact byte regions and closed causal evidence before application. If all durable cleanup operations fail and the worker restarts, durable cancellation cannot be guaranteed; this is explicitly reported rather than silently retried. These isolated checks do not qualify loaded Source70 execution or real120.
Frozen final scheduling regression proof (local evidence: ci/artifacts/quality-audit-2026-10-07/scheduled-creation-cancellation-candidate/candidate-proof-final-v5.json), Root independent candidate review (local evidence: ci/artifacts/quality-audit-2026-10-07/scheduled-creation-cancellation-final-v5-root-independent-readonly-review.json), independent final candidate review (local evidence: ci/artifacts/quality-audit-2026-10-07/scheduled-creation-cancellation-independent-historical-readonly-final-v5.json).
Authenticated generic downloads now validate every literal redirect destination before contacting it, refuse private literal destinations and return cross-origin destinations for a fresh normal permission decision. Chrome saves only the staged local blob after the authenticated stream is bounded and written to disk. Stop releases the in-progress stage. DNS resolution/private DNS rebinding is still outside this literal URL check, and full Firefox authenticated native transport remains unqualified.
A real Chrome regression in Source65 changed the requested filename wb_qa_download_20261010.png to a blob UUID despite correct PNG bytes. Source66 applies the general repair: remove the global Chrome filename listener and resolve known filenames before each native download. Empty preferences preserve the requested name; invalid paths remain native errors. A related Stop boundary now checks the actual linked run signal after the asynchronous filename preference read for screenshot, full-page screenshot and crop; cancelled crop cannot fall through to a different downloader. The existing default network test import is retained. Isolated naming validation passed19/19; production Stop tests first reproduced three unwanted saves and then passed. Applied-source default network117 and main2,450 checks passed. The Source67 user-browser retest passed: exactly one download, ID615, saved the requested wb_qa_download_20261010.png; actual disk bytes were258,958,512Γ512, SHA256 505f8b0e6603b308bed4e7796a5cedb5783611f84828ac10e75bec09142fbf38. Both live/stored success flags were true, with15.422 seconds elapsed and zero Root business inputs after native submission.
Real filename failure (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product65-repository69-main-native-download614-actual.json), applied filename and Stop patch (local evidence: ci/artifacts/quality-audit-2026-10-07/product66-repository70-reviewed-filename-routing-source-only-actual-aebd09ca-6385-4cc0-b510-27a9b6c0afe0/actual-application.json), independent final patch review (local evidence: ci/artifacts/quality-audit-2026-10-07/download-filename-linked-stop-final11-independent-historical-readonly.json).
Practical results
| Flow | Evidence and limits |
|---|---|
| Native download filename | Source67 normal user-Chrome Act passed with download615 and the exact requested filename. Actual PNG bytes, both success flags and one physical submission were independently verified; earlier UUID failure remains preserved. |
| Exact calculation | Source65 used actual calculate and done tools, returned 69135802476913580247.125, and finished in 13.237 seconds with live and stored success both true. |
| Native mid-run task change | Current Source71 independently passed in17.787 seconds with one correction, zero old tool actions, exact arithmetic and separate normal done; current before/after bot native snapshots match. Historical Source69 owned-bot retake passed its native completion checks in19.501 seconds. One original Return and one correction Alt+Return were physically entered; correction applied once after actual MAIN thinking, and only calculate then separate done executed. Both live and stored successfulDone/runSucceeded flags were true, the exact result matched, and the observer closed without a pending run. Fresh read-only native evidence confirmed the same bot document, empty editor, Start6672 only and zero new messages. Loaded source proof was fresh at input and completion. This qualifies this owned-bot replacement; accepted-RPC timestamp, original MAIN payload ordering and separate Saved Messages draft preservation are not independently claimed. An earlier Source69 attempt missed the Root bridge deadline before correction; collector/post-input setup errors were also preserved, without repeating business inputs. The prior Source68 actual retest failed: the one native correction was applied at revision1, zero superseded tool actions occurred and one actual calculation returned the exact 86419752308641975230.125, but first done incorrectly entered LLM verification and both terminal success flags were false. An unwanted later chat_observe was refused by the normal recipient binding guard. A fresh native bot read confirmed only the original Start6672, empty editor and zero bootstrap bodies. Source69 applies the general task-classification repair and passed the actual retake; this prior product failure remains preserved. Source61 passed: an in-flight Telegram inspection was replaced by calculation, with revision1, zero superseded tool actions, correct arithmetic, separate done, both success flags true and preserved foreign [protected draft content] drafts. The Source65 retake did not start a WebBrain request because Root's asynchronous window focus raced physical input. One accidental QA self-message was deleted; both [protected draft content] drafts and original video4082 were independently verified unchanged afterward. This is an unqualified Root input attempt, not a product pass or failure. |
| YouTube avatar | Source57 completed the exact canonical avatar prompt on Vatansever Cephe, UCVB3sGJ6VIKsYN4W2SeTMgQ, including product Publish and both success flags true. A fresh native reload verified the brain avatar persisted and Publish was disabled. The originally supplied UC2 channel was inaccessible and was not modified; no new channel was created. This is historical live evidence, not a Source65 retake. |
| Current Source71 own-self read-only observation independently qualified in27.220 seconds: one native Return, one chat_observe and separate successful done, both success flags and matching native snapshots; no sends. Raw QA observer false fields and its wrapper/enum measurement defects are preserved and separately explained. Source71 isolated contact matrix passed15/15; earlier Source68 evidence is retained. Two historical self messages and one explicitly authorized personal-contact message remain tracked. No current two-hour WhatsApp run or new delivery proof is qualified. | |
| Telegram owned bot | One QA bot exists and was started once. No bootstrap body has yet been delivered or independently verified. The real 120-minute run has not started. Earlier failures were before physical Enter and retained as failures. |
| Long local chat | A historical isolated two-hour native-chat fixture covered restarts, compaction and Stop/Continue. It is not authenticated Telegram or WhatsApp endurance. |
| Firefox | Paired source/build and fixtures are qualified. Optional Firefox148 BiDi never reached trusted interaction because native tab creation timed out even without the extension. |
Source65 calculation (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product65-repository69-main-native-calculate-actual.json), Source65 Root focus error and verified cleanup (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product65-repository69-root-focus-race-and-saved-cleanup-actual.json). Detailed earlier attempts remain in the preserved chronological reports and their exact traces; passing newer evidence does not relabel old failures.
GitHub Code Scanning
The earlier authenticated read-only GET completed on October10 at18:41UTC against current Source71/Repository79 and contained115 alerts:77 open,38 fixed and none dismissed; all77 open findings are high severity. Raw alerts and analyses are byte-identical to the prior authenticated Source66 capture. The latest main analyses use CodeQL2.27.2 against6da190593be3990dceb83396fb42b9e779ef9f1e, with69 JavaScript/TypeScript findings, eight Python findings and zero Actions findings, with no analysis errors. These refer to committed code and do not scan or qualify the uncommitted repairs. All77 open findings retain per-alert review:36 locally addressed/mitigated cases and41 conditional trust cases. No remote alert was dismissed or closed by this audit.
Source66 local comparison completed for all 77 findings and 80 named supporting files, with two stable reads and no missing or ambiguous inherited anchors. That historical Source66/Repository72 independent reconciliation joined all 77 alert IDs to its fresh remote capture and rehashed all 80 pins twice against Repository72, plus an additional Firefox staging mirror. Alert states, rules, messages, locations and reported commits were unchanged; only newer analyses and the CodeQL version changed. This preserves the prior 36/41 dispositions; matching code anchors alone does not close a vulnerability. Direct review of the new authenticated download sink verified the per-hop literal URL restrictions and retained the DNS/SameSite/Firefox limitations. The Repository71 and Repository72 test fixture corrections change no product or named security source bytes. Coverage, loaded-user-runtime, bootstrap and endurance remain separately unqualified in the security record. The download repair does not automatically close unrelated plain-text decoder, research-link metadata, serializer, vendor or conditional HTML trust findings.
Source66 per-alert source comparison (local evidence: ci/artifacts/quality-audit-2026-10-07/code-scanning-product66-repository70-local77-actual.json), direct authenticated download sink review (local evidence: ci/artifacts/quality-audit-2026-10-07/product65-repository69-authenticated-download-sink-readonly-note.json). The private web page's earlier404 response was not interpreted as zero findings; authenticated gh api access is available.
Saved authenticated capture (local evidence: ci/artifacts/quality-audit-2026-10-07/code-scanning-final-repository72-20261010T125456340Z-009be199/code-scanning-final-capture-manifest.json), prior Source69 per-alert reconciliation (local evidence: ci/artifacts/quality-audit-2026-10-07/code-scanning-product69-repository76-current-local-reconciliation-independent-historical-readonly.json), current Source70 local application/security reconciliation (local evidence: ci/artifacts/quality-audit-2026-10-07/code-scanning-product70-repository78-current-local-and-application-independent-historical-readonly.json).
The Source70 independent local review rehashed the inherited80 supporting files plus both Scheduler implementations twice. All37 alert-referenced files,104 inherited support anchors and48 contexts remain stable; all77 saved remote IDs remain mapped. The four new product changes add no recipient exception or permission grant. The same36 local mitigation/41 conditional dispositions remain explicit, alongside the scheduler restart and DNS/SameSite/Firefox limits. This historical local reconciliation is superseded by the final Source71 authenticated GET and independent77-ID join below; real-account endurance was not achieved.
The Source71 current local/application reconciliation (local evidence: ci/artifacts/quality-audit-2026-10-07/code-scanning-product71-repository79-current-local-and-application-independent-historical-readonly.json) and final authenticated independent reconciliation (local evidence: ci/artifacts/quality-audit-2026-10-07/code-scanning-final-product71-repository79-independent-historical-readonly.json) join the exact77 open IDs to the fresh remote capture and rehash83 current named/support pins twice (80 inherited files, both Scheduler implementations and CDP). All37 alert-referenced files,104 support lines and48 contexts remain bound. State/rule/path/location/commit are unchanged. The36 local mitigation/41 conditional dispositions remain explicit, alongside DNS/rebinding, privileged authored/system HTML trust, SameSite/referrer and full Firefox transport limits. The four-file preparation-phase change adds no sink, recipient grant, completion proof or unknown-feedback clearing. Remote scans cover committed main; normal source binding, selected live checks and separate60-case security PASS do not constitute remote closure or full C8/endurance qualification.
Final authenticated capture (local evidence: ci/artifacts/quality-audit-2026-10-07/code-scanning-final-repository79-20261010T184126293Z-14381bb5/code-scanning-final-capture-manifest.json).
Historical scope and tracked effects
Historical analysis covered 33 reports, 20 prioritized families and 4,657 traces across 208 journeys. These were analyzed and linked to regressions; they were not all replayed live against original recipients.
- Only the YouTube channel Vatansever Cephe was changed.
- Retained Telegram bot:
wb_quality_20261009_2312_bot; one manual Start, zero verified bootstrap deliveries so far. Credentials are outside Git. - Retained Bluesky QA account:
webbrainqa1008.bsky.social; no posts, DMs, likes or follows. - Retained Mastoturk QA account:
webbrain_qa_20261007; ten QA posts were deleted and deletion verified. - WhatsApp: two historical self messages and one authorized personal-contact message; no other real-person DMs.
- Source65 accidentally created one QA Saved Messages self-message during Root setup, then deleted it and restored the protected draft. No message was sent to another recipient.
- Download615 is retained as
wb_qa_download_20261010.pngin the local Downloads directory, with the exact requested name and verified canonical PNG bytes. - Download614 is retained as the UUID-named 512Γ512 PNG, 258,958 bytes, SHA256
505f8b0e6603b308bed4e7796a5cedb5783611f84828ac10e75bec09142fbf38. - The temporary trace-access credential was revoked; the user's original credential was not revoked.
The intermittent full-form failure was reproduced again in an ordinary installed run with capture-only diagnostics: initial native preparation succeeded, but the read-only reprobe returned pageFeedbackPending before any button press. A neutral regression reproduced how the dispatched, unfinished preparation movement can make a later unrelated counter update become unknown feedback. Source67 closes only the acknowledged preparation movement before reprobe and retains the original private model certificate. The first reproduction did not record the exact mutation timing inside its108ms preparation interval; that limitation remains explicit. The126/126 candidate checks cover passive updates after completion and retain queued unknown feedback during a held ACK, lost ACK, private field changes, replaced target objects, point changes, trusted human input, stale owner/document, Stop and steering. A real content deadline refusal now retains its error instead of claiming that the button changed. The applied installed form passed. Execution4 then passed all6,763 Node cases,14 UI checks,80 recipient-upload browser checks and installed stages1β5, but failed stage6 on WhatsApp contact identity after an acknowledged native Close. The remaining15 installed stages and main/security tail were not reached. A separate ordinary positive diagnostic repeated the same canonical-contact failure with zero messages. Source68 applies the private contact read-preparation routing repair; its complete isolated15-case matrix now passes. This scoped result does not relabel the failed Source67 coverage command or qualify full C8 execution5.
The current report-only verification pass is closed. Separate remaining installed/main/security diagnostics, current WhatsApp self read-only testing, final authenticated Code Scanning reconciliation and temporary tracing cleanup completed with their actual outcomes preserved. Source71 normal full C8 execution9 failed and was not repeated unchanged; the held stage12 fake-provider candidate remains unapplied. The newly generated wrong-goal Telegram plan and the general native-completion false negatives remain open product/model findings under the latest no-fix instruction. Native task replacement and WhatsApp own-self read-only completion passed. The one current owned-bot bootstrap failed without any chat_send or physical Enter, so real120 prerequisites were not met and no120-minute real-account run started. Historical controlled soaks cannot qualify real-account endurance. The quality goal remains unmet; this report does not claim a bug-free release.
Temporary tracing was restored after explicit idle checks on all16 open HTTP tabs and zero active jobs. Only losslessTrace and tracingEnabled were removed, matching the saved originally-absent baseline; every other local setting retained an identical digest and key count. Current QA observers/listeners are closed. The exact active identity of the Root-created Main8307 was verified, then that sole temporary tab was closed with one native Ctrl+W; user/unknown tabs were retained. Chrome was left on the completed WhatsApp own-self task. Owned Main cleanup (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-main8307-native-close-actual-4256487d-c809-42fa-8e8d-efca5812f799.json). Actual tracing restoration (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-temporary-tracing-restored-actual-f8bc5afb-bc4b-4adb-a89f-a6c9968e65c6.json). Final read-only upstream check still returned main6da190593be3990dceb83396fb42b9e779ef9f1e; local HEAD matches. Original index SHA7b96d37839cac8822737c3741404636980138a1b729bd9174492901a9ba24e46, package/lock and protected authority remain unchanged. No staging, commit, push, reset or stash was performed.
Source69 actual native completion qualification (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product69-repository76-bot148-native-midrun-retake2-root-qualified-actual.json), Source69 raw observer (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product69-repository76-bot148-native-midrun-retake2-observer-terminal-actual.json), independent native qualification (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product69-repository76-bot148-native-midrun-retake2-independent-historical-readonly.json), preserved Source68 native failure (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product68-repository74-bot148-native-midrun-observer-terminal-actual.json), native input record (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product68-repository74-bot148-native-midrun-input-actual.json), fresh bot state after failure (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product68-repository74-bot148-native-after-midrun-readonly-actual.json).
Source67 user-runtime binding (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product67-repository73-main8199-source-proof-actual.json), actual native filename success (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product67-repository73-main8199-native-download615-actual.json), independent download615 filename and disk-byte verification (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product67-repository73-main8199-native-download615-independent-historical-readonly.json), execution4 raw failed terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/product67-repository73-isolated-normal-coverage-before-real120-execution4-actual-82e6bf20-05c2-4956-9b42-e1d0f8a59063/terminal.json).
Historical Source68/Source69 security work: Source68 local review rehashed all80 named/support pins plus the Firefox staging mirror twice and bound the exact two-file application. All37 alert-referenced files,77 saved remote alert IDs and104 inherited support lines retain current anchors. The contact-routing repair adds no sink, permission grant, recipient exception or waiver of unknown feedback. The saved authenticated capture remains115 alerts:77 open and38 fixed; it was captured against Source66/Repository72 and committed main, with no new GET or remote closure claimed for Source68. The36 local mitigations/41 conditional dispositions, DNS resolution and Firefox transport limits remain explicit. Source69 independently reconciled all77 saved alert IDs and80 supporting pins twice; only the paired classifier support files changed. All37 alert-referenced files and104 supporting source anchors remain stable. The new grammar introduces no sink, authority grant or receipt waiver, preserving the36/41 dispositions and stated DNS/SameSite/Firefox/privileged authored-HTML trust limits. Source69 loaded runtime and actual owned-bot mid-run completion are verified; C8 execution6 failed at the stale download fixture. Bootstrap, real120 and overall END qualification remain separate and unfinished. No new authenticated GET or remote closure is claimed for Source69.
Additional report-only scope closure β October 10
A requirement-by-requirement audit found20 ordinary default commands after the runtime-lifecycle group and before node test/run.js that had not run on Source71. The failed C8 invocation stopped inside runtime-lifecycle; the separately passed main/restoration/benchmark/security tail did not include these20 commands. All20 have now run once, unchanged, through two disjoint ordinary diagnostics: original commands1β9 passed,10 failed, and previously unstarted11β20 passed. No failed command was repeated. This is19 passing commands and one failing command; raw Node summaries total298 cases,296 passed and two failed, with zero skips/cancellations. Custom PDF, accessibility/UI, toolbar and attachment assertions are separate from those Node totals. Both runs preserve all18,074 inputs, all1,180 physical source/build pairs, original authority and separately pinned support files. The default suite and full C8 still fail.
Both failures are in test/cloud-run-outcomes.mjs:131. That test extracts _scheduleAutoProgressResume and calls it on a fake receiver that lacks _scheduleCreationContext. The current real Agent defines that helper in both browsers. TypeError occurs before the cloud/native routing assertions, so this establishes an obsolete extracted-test dependency, not a reproduced production Cloud scheduling failure. The default test remains unchanged under the report-only constraint. Profile sync2/2 and MemCode recall3/3 now pass their whole offline test files; real sync/OAuth, user preference recall and large grounded extraction remain separate missing qualifications.
First10 raw result (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-unreached-default-tail-actual-a6159b69-b692-483b-9671-23ba727a2cac/result.json), first10 independent causal review (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-default-tail-first10-independent-recent-readonly-4b02de0e-6e9e-4525-9984-cb56381b36bc.json), remaining10 raw result (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-unreached-remaining-default-tail-actual-a11261e6-a850-446f-a93f-c385530977d4/result.json), remaining10 independent review (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-default-tail-remaining10-independent-recent-readonly-b9889d20-e95e-444e-a225-d2fd7137114b.json).
The unchanged optional installed Watch test now passes current Source71 in160.391 seconds. Five actual automatic alarms have intervals31.422,39.861,33.112 and40.910 seconds. The baseline causes no acknowledgment; release11 and release12 are each acknowledged once; actual worker stop/restart discards its globals and preserves the prior event; duplicate acknowledgment is suppressed. Stop removes the owned helper/alarm and permits zero late mutations. Three subsequent failure checks retain their baseline and stop terminally with helper/alarm cleanup and no revival. The model and local application are fixtures; the MV3 scheduler, alarms, native actions and worker restart are real. There are no external messages/accounts. This is controlled scheduler qualification, not real-account endurance. The raw wrapper qualified:false remains unchanged; the actual assertion evidence and independent review establish the narrow pass separately.
Current Watch terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-optional-watch-actual-40f974d6-71e3-4048-aeaa-c63c48e80e8f/terminal.json), current Watch actual evidence (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-optional-watch-actual-40f974d6-71e3-4048-aeaa-c63c48e80e8f/watch-artifacts/evidence.json), independent current Watch review (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-optional-watch-independent-historical-readonly.json).
The unchanged optional WebMCP test also passes once in a disposable Chrome154.0.8037.97 context with extension40.0.8. Actual CDP discovers, invokes, rejects and removes tools (three added/three removed); current Agent/CDP assertions exercise feature/mode gates, paginated and cross-frame catalogs, forged metadata refusal, invocation failures and stale IDs. Source/build/authority remain exact, and the historical355-byte log is retained byte-for-byte. The test does not attach to user Chrome or use accounts/providers. It does not establish runtime default settings, a global network firewall or packet census, all-site success, remote security closure or full C8 qualification.
Current WebMCP terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-optional-webmcp-actual-d7a6e0dd-2d5f-4c5e-8392-f489d2a6b7de/terminal.json), unchanged-command actual output (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-optional-webmcp-actual-d7a6e0dd-2d5f-4c5e-8392-f489d2a6b7de/run.log), independent current WebMCP review (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-optional-webmcp-independent-recent-readonly-acd5473d-c649-4ad0-9535-8a4ceb30b454.json).
A new static disclosure finding remains report-only: web/index.html3797/3842 makes blanket no-telemetry/zero-leakage claims, while privacy documentation and the default Compass configuration describe enabled Help Improve collection and operational metadata. Client config, provider manager, settings and request-header code agree on default-on Compass Help Improve. This is a marketing/disclosure inconsistency; no undisclosed exfiltration or actual server retention was reproduced. Local/BYO sharing has a separate default-off policy. No marketing text, settings, provider/model behavior or product/default test was changed. Pinned disclosure finding (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-advertised-privacy-claim-default-compass-report-only-77b2dc3f-2afc-4891-aae2-22ed2cfb9bf8.json).
The17-row advertised-feature matrix and independent historical requirement audit preserve the original scope. The4657 analyzed checkpoints,208 journeys,20 failure families and27 schema replays do not establish that every historical journey was executed again. The new default-tail and optional passes add bounded current evidence; the failed C8, general completion/provenance failures, wrong-goal Telegram plan and missing real Telegram/WhatsApp hours remain unresolved. No product/model/default-fixture repair was applied during this continuation. Existing accounts, messages, avatar and cleanup ledgers above remain the effect record; these new tests created no accounts or user messages.
Final advertised-feature matrix (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-advertised-runtime-claims-readonly-final-matrix-5ec5d160-6bd7-44d2-bd4d-228568bf97ba.json), original-scope historical gap audit (local evidence: ci/artifacts/quality-audit-2026-10-07/product71-repository79-original-scope-historical-replay-gap-independent-historical-readonly.json).
Source71 real-model large-table extraction and separate follow-up β report-only
After the user manually opened the extension Main page, Root re-established safe Chrome access and verified extension40.0.8,31 served module hashes, all18,074 repository inputs, all1,180 source/build pairs, and authority pins. The owned static loopback page contained172 inventory rows in shuffled document order plus a separate distractor table. The frozen oracle was outside the served directory and never exposed to the model. Root submitted each of the following two distinct questions once through the normal Ask composer and native Return, with no launch RPC, repair prompt, model/provider change or retry of the first extraction.
| Actual question | Delivered result | Qualification |
|---|---|---|
| Extract every inventory row and preserve all four fields exactly | 20 of172 rows,152 missing; numeric columns correct for the20 returned rows; every literal changed U+00B5 Β΅ to U+0575 Υ΅;0 fully correct rows;10.075s | FAIL. The response was the first20 rows in document order, with no duplicate or distractor rows. Stored Ask state was completed/runSucceeded=true; the requested all-row extraction was unmet. |
| A new question for10 specified IDs outside that prefix, in the same conversation | 0 requested rows; candid inability to verify the values;2.999s;0 dispatched tool calls | No data delivered. No values were fabricated. This is a separate post-terminal question with its own task/request/run, not Continue, mid-run steering, a repaired first answer or an endurance test. |
The first run dispatched get_accessibility_tree(page1,maxChars12000), inspect_viewport and done. The full2,081-character incorrect JSON was already present in done.args.summary and matched the public terminal, stored finalContent and captured assistant text;13 public events were contiguous. The wrong glyph therefore predates display. The follow-up had50 contiguous public events and a complete241-character limitation response.
The source review shows that generic Ask success checks a nonempty response without listed runtime errors; it does not validate arbitrary table row coverage or exact literal correctness. Normal Ask retains conditional reading tools. The complete provider-facing request, actual tool schema/options, full AX response and hasMore/error fields were not captured, so the exact upstream cause of the20-row window and glyph substitution, and the follow-up reason for dispatching no tools, remain unproven. The known extract_data budget was not an actual cause in this run because no extract_data call occurred.
Public run_complete omits the stored success flags. The passive observer coerced those absent fields to false, while the later matching Ask journal/state reported runSucceeded=true. Both raw representations remain intact; successfulDone=false is recorded and is not required for Ask. The observer host was a separate Main realm, so exactTaskMatched=false and the SDK supplied no separate native action acknowledgment; ownership is supported by the exact task SHA/native-input ledger, owned tab, request/run and source identity, not a host-DOM user-message match.
Source and build hashes, index, protected helper and authority remained unchanged after both questions. The owned table1858378353 and Main1858378344 were independently read back as absent; both passive listeners were removed and the local server stopped. Unknown tab1858378339 was retained and the temporary readback console closed. No account, recipient, webpage setting, upload or message was changed in this scope. The latest read-only upstream lookup returned6da190593be3990dceb83396fb42b9e779ef9f1e; an explicit metadata erratum withdraws an unrecorded exact lookup second.
Evidence: Root actual closure (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-large-table-actual-99c94c87-fdfb-4bb7-bcc4-ded0be1529eb/root-closed-qualification.json), all172-row gold comparison (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-large-table-actual-99c94c87-fdfb-4bb7-bcc4-ded0be1529eb/gold-comparison.json), distinct follow-up outcome (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-large-table-actual-99c94c87-fdfb-4bb7-bcc4-ded0be1529eb/followup-outcome.json), independent original-failure peer (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-large172-independent-historical-readonly.json), independent follow-up/source/cleanup peer (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-large172-followup-and-cleanup-independent-historical-readonly.json), source-level causal review (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-large172-and-followup-source-causal-readonly.json), source preservation (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-large-table-actual-99c94c87-fdfb-4bb7-bcc4-ded0be1529eb/source-after-verification.json), timestamp qualification correction (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-large-table-actual-99c94c87-fdfb-4bb7-bcc4-ded0be1529eb/remote-timestamp-qualification-correction.json), and server/tab/listener cleanup (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-large-table-actual-99c94c87-fdfb-4bb7-bcc4-ded0be1529eb/fixture-server-closed.json).
These are newly reproduced product/model deliverable failures, left unchanged under the current user constraint. They do not qualify a full C8 pass, every historical journey, hours of Telegram/WhatsApp chat, or a bug-free product.
Native Telegram delivery after normal New chat β current Source71, no fixes
A materially distinct ordinary Act test passed after the normal New chat confirmation cleared only tab1858378148's WebBrain QA history. Telegram's bot conversation and prior /start remained intact. A scoped native baseline independently bound numeric bot[owned QA bot ID], the current header/composer, document3769C03B16953F8758C7562703F0DF1F and epoch1791655714151.8. The composer was empty and only delivered /start ID6672 was mounted. New chat did not privately reset the agent or remove the old bootstrap driver's once key. The older failed wrong-goal run stays preserved and failed.
Root entered one366-character task through the actual Act sidebar and submitted one normal Return. The new request was req_1858378148_1791663591541_buz2pv, run run_1791663592090_nqh6z3, conversation conv_1858378148_1791663591543_uzsapnflb2gl. It completed after67.624s from the request timestamp, or67.725s from native Return completion. All96 public events were contiguous. The model dispatched17 public tools; the exact authorized body appeared in both of its two chat_send calls. The stored normal completion flags were both true.
Recovery was rough: two initial observations refused an unbound username route. The model followed the exact native profile repair, then tried generic controls and put the QA nonce in Telegram's search field. A click reported βBrowser changed during action preparation.β The first send reported that the exact owned draft was verified but Enter was not dispatched. A pending-key observation followed; the second send reported that no new matching outgoing bubble had yet been observed. The model observed again and finished successfully, with no additional send after that uncertain result.
The independent native after-snapshot was captured28.941s after the terminal event. It retained the original document/epoch/numeric peer, latest viewport and empty composer. Its strict mounted window contained only /start ID6672 and one new delivered outgoing ID6679. That new message exactly matched the87-character authorized body, SHA 59c71693867de761720e91f9067940e8502fa8d8f8dd24fddca4fde407a063b5; no second matching body was present. This supports one observed native delivery, not a measured total physical submission count or all-history coverage. The inactive Main observer could not match the submitting sidebar's user DOM; the exact Root task/hash/one-Return ledger and new owned request provide the task binding.
The official recorder had128 metadata events and18 recorded LLM requests/responses. Its tool arguments/results and provider wire were not recorded; tracing settings were not changed. Existing diagnostic notes show that all six intervention_or_document decisions retained documentMatches/currentRun/stateCurrent/sameDocument=true. Unknown same-document navigation or scroll can produce that generic classification. These notes do not prove human intervention or document replacement. The failed click was pre-dispatch, with zero trusted inputs and no synthetic dispatch. The exact veto operand, affected DOM targets and navigation URLs were not retained, so a specific false-positive monitor bug remains unproven. No Root content inputs occurred between native task Return and terminal completion.
At the original capture, internal pendingOutbound and retained document debt were NOT_EXPOSED. The later persisted-evidence section supersedes the pending/count limitation only. The first pending-key observation's reconcile_pending_outbound:true alone proves neither clearing nor bypass: current source also has a read-only branch for a privately known pre-Enter draft that retains pending state. Neither this single delivery nor both normal success flags qualifies the old strict bootstrap contract or a real120-minute run. No endurance controller was started. This test does not classify the previous wrong-goal failure as fixed.
Both source captures and all1180 source/build pairs matched the full18074-input Source71/Repository79 map before and after. HEAD/main/index/protected/package authority stayed unchanged. No product, model or default-test repair was applied. Only the originally reviewed c53a9cae/c4b2c850 QA definitions were invoked; later rewritten preparations were excluded. The original digest reader has a possible peer-switch race between its guarded reads; no actual switch or foreign draft read was established, and this result does not certify that reader across a conversation switch. Withdrawn QA metadata projections/filename guesses are separately corrected in the case directory.
Cleanup removed the listener and Root reader/preparation/raw-event globals, closed Root's DevTools Console, cleared the nonce search and closed the search/profile panels. Unknown Main8339 was retained, with one inert nonconfigurable resolved observation handle remaining in document memory. No new account, tab, bot API call, credential read or other-person message occurred in this case. The authorized QA bot message6679 is intentionally retained and tracked. Saved Messages' pre-existing protected draft was not edited.
Independent delivery/source review also completed in text. The attempt to write its new exclusive QA JSON receipt was automatically rejected as βblocked by policyβ, without further explanation. No file was created and the rejected write was not retried. The linked independent review below covers invoked assets and the saved baseline only, rather than a new saved delivery certification.
Evidence: sealed one-delivery result (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-telegram-fresh-chat-actual-6d07ab12-5b78-4986-8e4a-c3616a232dd7/root-one-native-delivery-closure.json), public terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-telegram-fresh-chat-actual-6d07ab12-5b78-4986-8e4a-c3616a232dd7/public-observation-terminal-actual.json), same-document native after (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-telegram-fresh-chat-actual-6d07ab12-5b78-4986-8e4a-c3616a232dd7/native-after-actual.json), exact diagnostic notes (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-telegram-fresh-chat-actual-6d07ab12-5b78-4986-8e4a-c3616a232dd7/official-exact-owned-run-diagnostic-notes-actual.json), independent invoked-asset/baseline review (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-telegram-fresh-chat-actual-invoked-assets-independent-historical-readonly.json), cleanup and retained effects (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-telegram-fresh-chat-actual-6d07ab12-5b78-4986-8e4a-c3616a232dd7/native-cleanup-and-effects-final.json).
Persisted Telegram evidence and shared send-result inconsistency β report-only
On October10 at20:43β21:03UTC, Root read only the owned tab's official session keys agentConv:1858378148 and runUi:1858378148, paired with the public run state. The persisted, compacted39-message conversation retained eight intact relevant assistant/tool pairs. The genuine366-character user task, resume-task ID and delivery receipt match the original request, exact87-character body and native message6679. The original case files and recorder remain unchanged; this later evidence strengthens that single existing delivery.
The unchanged inert protocol dcccfe9c verifies two chat_send calls/results, one explicit submissionDispatched:false plus submissionOutcomeUnknown:false, and one later nested submissionDispatched:true. Its repair protocol passed. This is the contract's Enter-dispatch count; it is not a trusted hardware-keystroke measurement. A final same-thread observation verified the exact outgoing body, empty composer and pending:false. The saved current pendingOutbound field is explicitly null; stored and live completion flags are both true. Blanket absence of private editor-debt records remains unproven.
Root then made one bounded getMe β getWebhookInfo β getUpdates chain. All three returned200; identity matched the owned bot and the webhook was empty. The complete responses were saved privately before receipt inspection. Only one owner/private-chat update was present: update781136474, API message2, exact body SHA59c716β¦, server20:20:58UTC. That server timestamp numerically lies between the local native task timestamps20:19:51.312β20:20:59.165UTC, but the clocks were not calibrated contemporaneously. A later one-off unauthenticated HEAD (redirects disabled) measured HTTP Date approximately12.4 seconds ahead of the local Node/Chrome clocks. Numerical interval membership therefore does not establish chronological task-window containment; the exact body and owned identity joins remain valid. Native message6679 and API message2 are separate identifiers. No offset, allowed_updates, acknowledgement, retry or API message send was issued. Omitting offset avoids advancing the acknowledgement cursor; omitting allowed_updates preserves the existing filter. Telegram Bot API.
A shared source-supported result bug is now confirmed in _sendChatWorkflow. On the second attempt the already verified draft needed no new draft dispatch, so nested dispatch.dispatched was false and success was true, while submissionDispatched was true and nested outcomeUnknown was true. The public dispatched flag correctly became true through success, but the unverified-delivery outcomeUnknown calculation used only draft dispatched/noDispatch and became false. The same calculation appears in the failed-read branch. It therefore reports an unverified Enter submission as not uncertain when an owned draft is reused. This is common chat-workflow logic, with no website-specific condition in the faulty calculation. No duplicate or unsafe actual retry was observed here: pending state remained and the model resolved delivery through observation. No repair was applied under the user's current constraint. shared result calculation (recorded line 25671).
Fresh read-only checks again matched all18074 recorded inputs,1180 source/build pairs and31 Chrome-served files to Source71/Repository79. HEAD and remote main remained6da1905; the index and protected script contract remained unchanged. A prospective baseline hashed40 explicit provider/execution keys without exporting values or writing settings. It does not retroactively prove provider settings unchanged in the original task. Both scheduling keys were absent, which the actual scheduler interprets as enabled and confirmation required, rather than disabled. scheduler defaults (recorded line 663).
The old literal bootstrap sealer and old controller were not invoked. Their original configuration still references retired tab7253, has a null root-proof path, and lacks the new typed bindings. Its scenario-specific body/prefix and15-minute API-inspection window also do not match this late receipt. The unchanged endurance core accepts a separately qualified body hash, but every ownership, source, prospective settings, pending, submission and receipt requirement must remain intact. A separate normal-UI long-session preparation was later submitted once; its timed question/reply phase did not start. The prior wrong-goal bug and exact monitor veto operand remain unresolved. See the final preparation closure below.
This diagnostic added zero tasks, messages or accounts. It read the owned credential privately for the finite API chain; the credential was never printed and its Root memory reference was cleared afterward. Private metadata, ledger and old once reservations were not changed. The existing QA bot message6679 remains the only new retained message from the previous case. Historical and Recent independently reviewed the saved evidence in text; no new peer receipt file was written.
Evidence: enhanced one-message closure (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-session-dispatch-proof-actual-80d3d761-a04a-4c74-9b74-573bd4bf2f81/root-enhanced-one-message-closure.json), persisted tagged results (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-session-dispatch-proof-actual-80d3d761-a04a-4c74-9b74-573bd4bf2f81/owned-tagged-tool-results.json), unchanged protocol evaluation (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-session-dispatch-proof-actual-80d3d761-a04a-4c74-9b74-573bd4bf2f81/unchanged-protocol-evaluation.json), genuine task/receipt binding (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-session-dispatch-proof-actual-80d3d761-a04a-4c74-9b74-573bd4bf2f81/genuine-task-receipt-binding.json), independent API receipt (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-session-dispatch-proof-actual-80d3d761-a04a-4c74-9b74-573bd4bf2f81/independent-api-receipt-proof.json), fresh native identity (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-session-dispatch-proof-actual-80d3d761-a04a-4c74-9b74-573bd4bf2f81/current-native-readonly.json), prospective settings baseline (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-session-dispatch-proof-actual-80d3d761-a04a-4c74-9b74-573bd4bf2f81/prospective-execution-settings-baseline.json), explicit scheduler presence (local evidence: ci/artifacts/quality-audit-2026-10-07/auth-product71-repository79-owned-session-dispatch-proof-actual-80d3d761-a04a-4c74-9b74-573bd4bf2f81/prospective-scheduler-setting-presence.json).
Final distinct normal-UI Telegram preparation β HOLD before timed phase
Root submitted one new ordinary1082-character Act task through the actual sidebar after normal New chat. The exact native Return occurred at21:41:46.610β21:41:46.739UTC on October10. The authored request is req_1858378148_1791668506837_341fua, conversation conv_1858378148_1791668506840_cnzezw2sclmq and run run_1791668507501_6w6dbz, with genuine resume_task_b7a6c13e-7e43-42fa-aa32-cc39e2d65a9b. This was a distinct public-UI preparation, not a rerun or forged seal for the older strict bootstrap. No business/scheduler RPC, private Agent invocation or conversation-state write was used by Root.
The producer stopped HOLD before startedAt was assigned:0 questions,0 replies, no END notice, no Bot API send, no getUpdates, no offset change and no uncertain API write. Only getMe and getWebhookInfo were called, once each, both200. The lifetime once guard remains retained; this producer will not be restarted to bypass its stop. This is neither a timed two-hour pass nor a timed two-hour failure.
A separate model trajectory weakness is established. The successful chat_observe issued an exact read_latest repair: read the accessibility tree for pane ref_44433172736041, scroll that pane to bottom, then observe. The model instead read the global tree and clicked the pane twice. Both clicks were refused with native_telegram_latest_required. It then called done(partial), promising continuation when the composer became ready, without a schedule_resume call. Raw and live state independently ended completed with runSucceeded=false and successfulDone=false, zero owned jobs and zero owned alarms. No chat_send occurred. The scoped required-pane accessibility read and bottom-scroll were never issued. This is a model instruction-following and unscheduled-continuation finding, left unchanged under the user constraint.
The producer's HOLD was independently triggered by a successful generic anchor click lacking the app-private native read-repair marker. The anchor was the owned numeric bot route, but its result was verified:false/trusted:false with unchanged URL and scroll. This supports a conservative fixture stop, not proof of unsafe recipient interaction. The later native snapshot reports latest:true; it does not recover the earlier refused action's geometry or native end marker. A false latest/page-monitor predicate and its exact cause therefore remain unproven. No model/provider/tool workaround was applied to make the test pass.
Cleanup was independently read back. The producer exited normally and closed the local bridge; the passive collector removed its listener and timer, and only an inert once descriptor remains. DevTools closed, unknown Main8339 was retained, and no product run or owned scheduled job/alarm remains. The owned bot still contains exactly the previously observed /start native6672 and earlier87-character QA message native6679, with empty composer and no native pending message. No new account, bot message, webpage setting or other-person message was created by this preparation. Provider/settings hash6334e5f0b2a6c6e50b0476e94dc065f58a583df94b22f3612c2382ccb93602eb stayed identical; the whole private editor-debt map remains NOT_EXPOSED.
All18,074 source inputs, authority/index/protected files,1,180 physical Chrome/Firefox source/build pairs and31 actually served module hashes stayed identical before and after. No new product/model/default-fixture change, build or test rerun occurred. Both independent reviewers confirmed the finite public trajectory and the model/measurement distinction in text; no new peer receipt file is claimed.
Evidence: Root closed qualification (local evidence: ci/artifacts/quality-audit-2026-10-07/owned-telegram-distinct-normal-ui-real120-PREPARED-87a8c77d4a30ec5a2d4a/root-closed-qualification.json), actual repair and model calls (local evidence: ci/artifacts/quality-audit-2026-10-07/owned-telegram-distinct-normal-ui-real120-PREPARED-87a8c77d4a30ec5a2d4a/actual-owned-repair-and-model-actions.json), producer terminal (local evidence: ci/artifacts/quality-audit-2026-10-07/owned-telegram-distinct-normal-ui-real120-PREPARED-87a8c77d4a30ec5a2d4a/producer-terminal-summary.json), native after-snapshot (local evidence: ci/artifacts/quality-audit-2026-10-07/owned-telegram-distinct-normal-ui-real120-PREPARED-87a8c77d4a30ec5a2d4a/native-after-actual.json), stored/live/jobs/settings cleanup (local evidence: ci/artifacts/quality-audit-2026-10-07/owned-telegram-distinct-normal-ui-real120-PREPARED-87a8c77d4a30ec5a2d4a/public-jobs-settings-after-actual.json), and collector cleanup (local evidence: ci/artifacts/quality-audit-2026-10-07/owned-telegram-distinct-normal-ui-real120-PREPARED-87a8c77d4a30ec5a2d4a/collector-cleanup-actual.json).
Last read-only upstream and Code Scanning confirmation
The final saved alerts/analyses reads confirm115 alerts:77 open, all high severity,38 fixed and none dismissed. All115 reviewed state/rule/message/location/commit fields match the18:41UTC capture. Latest main CodeQL2.27.2 analyses still cover6da190593be3990dceb83396fb42b9e779ef9f1e with69 JavaScript/TypeScript,8 Python and0 Actions findings and no analysis errors; a separate read-only upstream lookup confirms the same main commit. The prior per-alert Source71 reconciliation therefore remains applicable:36 locally addressed/mitigated findings and41 conditional trust cases, with unchanged source bytes. These dispositions do not close remote vulnerabilities. GitHub has not scanned the uncommitted repairs; no alert was dismissed or closed and no GitHub write occurred.
Final saved security summary (local evidence: ci/artifacts/quality-audit-2026-10-07/owned-telegram-distinct-normal-ui-real120-PREPARED-87a8c77d4a30ec5a2d4a/final-github-code-scanning-summary.json) retains exact private raw-file pins and sanitized alert locations. The remote source is GitHub Code Scanning. The complete C8/default suite, real-account endurance and bug-free objective remain unqualified. Newly established product/model defects are reported without fixes as requested.
Publication and first fresh PR CodeQL review β October 11
The fixes and public audit were committed as 50c8d73ad54190e61b1a7255e11af792ff42adf3, pushed to codex/quality-fixes-40.2.0, and submitted as PR #408. The commit contains 391 reviewed files. All 29 excluded local files remain unchanged; private traces, credentials, account files and receipt archives were not committed. The 40.2.0 changelog entry remains Unreleased and the tested product runtime remains 40.0.8. A publication-only blank-line whitespace cleanup in the trusted preparation regression was independently rerun: 159/159 passed, with no skips or cancellations.
On the exact PR head 50c8d73a, Website Check and WebMCP E2E passed. All three CodeQL analysis jobs also completed successfully, using CodeQL 2.27.2 without analysis errors. The separate CodeQL findings check failed, reporting 32 alerts in changed code: 31 high and one medium. Analysis execution success is not a clean findings result.
The authenticated PR-head analyses use refs/pull/408/head, not main or the synthetic merge commit. JavaScript/TypeScript analysis 1930333320 reports 60 results; Python analysis 1930324174 and Actions analysis 1930323569 report zero. The current PR-ref alert inventory contains 60 open alerts, 59 high and one medium. Main still contains 77 open high-severity alerts. Forty-five numeric alert IDs persist from main; 32 main IDs are absent from this PR result and 15 IDs appear only on the PR ref. These are scan comparisons, not remote closure or exploit-safety claims. No alert was dismissed or waived.
The bounded comparison covered the 32 changed-code annotations against the earlier 77-finding review. Nineteen annotations reproduce previously reviewed semantic findings and 13 are newly flagged test/harness conditions. Thirteen of the 19 retain their conditional trust assessment; two are website text-decoder paths whose final JSON script serialization encodes HTML-significant characters, and four are previously hardened report-rendering paths using escaped labels and finite/numeric cells. This does not grant those files a blanket security qualification.
The two new numeric product IDs, #241/#242, reproduce old #24/#31 at the paired AX option-value formatter. The option text/value formatting block and flagged quote-escaping source line are byte-identical to main; that source-line SHA-256 remains fb4830809d4764fa0df9a2cf249c0406c39a231ddbc13145b733674b11c1cc8b. Private formatter-origin tracking changed, and the scanner reidentified the existing representation warning. The AX text-ambiguity condition remains documented; this comparison does not fix or dismiss it.
The contextual review retains the following explicit limits:
- XML/article/network decoders produce readable text; they are not general HTML sanitizers. Recipient display normalization and CSS-selector fallback do not establish HTML safety.
- The JavaScript-scheme predicate participates in native anchor classification followed by URL/document checks; it is not a general safe-URL policy. Authored system HTML in the side panel remains a privileged trust boundary.
- WhatsApp fixture identity restoration writes character data. Script-extraction/replacement regexes operate on controlled checked-in fixtures and can require maintenance when templates change; they are not general HTML parsers.
- The
--onlyfilters intentionally accept regular expressions from the local test operator. The fake completion predicate is not production URL authorization. The dropdown probe uses fixed fixture markup; its current input origin is part of the assessment. - The report-rendering and website-builder dispositions follow the final escaped/serialized sink, not an assumption that intermediate decoded text is sanitized.
One newly flagged condition exposed a concrete injection path in the disposable loopback workflow QA server: URL query values were interpolated into HTML and inline JavaScript, and JSON.stringify alone did not protect the script boundary. The follow-up restricts generation to the five existing fixture presets and mode to normal/uncertain, returning canonical constant literals. Invalid values receive a static 400 JSON response without reflection. Valid workflow fixtures retain their prior markup and replay semantics. This is a test-server boundary repair; no public-product or real-account compromise was established.
The whole installed workflow test completed once with exit 0 at 2026-10-11 02:28:34 UTC. All five cases passed, including six once-navigated malicious/unknown query browser/server checks and the original four workflow replay, Stop and uncertainty cases. All 34 original assertion-containing lines are retained. All 12 valid preset/default HTML combinations remain byte-identical. The 1,182 product files, fixture, package, lock and index stayed stable during execution; provider fallback requests and external calls were zero. The fixture SHA-256 is 02766f9c98ea758197586c49e213ca5ec85bb54c4c4b1901e714da3f41eab87c. Local proof: ci/artifacts/quality-audit-2026-10-07/publication-workflow-fixture-injection-fix-4d8e4c59-82d3-4f15-b0fc-27dbf4eac751/fix-proof-final.json, SHA-256 1cb662d4da3ccd38428a1398bb44dbfcb4ab6e73ba71861d031b0c976895fe43.
This follow-up changes the workflow fixture and audit documentation only. The previously completed unfiltered C8 run and its coverage percentages remain dated evidence for the frozen audited product; they are not relabelled as a new full-suite run after the fixture edit. The initial PR-head security failure remains recorded. Further remote checks may run on the follow-up commit, and their actual results must be reported separately. Real-account two-hour endurance and the bug-free objective remain unqualified.
PR #408 Codex review follow-up β October 11
Codex's first review, on 50c8d73a, identified concurrent cold UI snapshot reads cancelling one another. An agent_run_state read overlapping beginContinuationRunUiSnapshot after a service-worker restart could make the continuation treat a saved journal as absent and discard its progress and events. The correction is general and applies to both Chrome and Firefox.
getRunUiSnapshot now shares one in-flight storage read per tab. Starting a new journal or clearing a conversation still invalidates that read; a late result respects a newer live journal and cannot resurrect cleared state. A failed shared read releases its slot so a later read can retry. Only the paired snapshot-reader functions changed in shipping code.
Meaningful regression proof: with the added tests and original code, 64/72 passed and eight failed; after the fix, 72/72 passed, with no skips or cancellations. The cold continuation reproduction previously replaced persisted sequence 2 with sequence 0. It now preserves sequence 2, acknowledged sequence 1 and the retained event, then appends sequence 3. The tests also cover both original read completion orders, shared-read failure/retry and the existing clear/new-run fences.
Validation on the corrected source:
node --test test/run-ui-scheduled-lifecycle.mjs: 72 passed.- Ten neighbouring persistence, startup, continuation, transport, CDP restart/clear and assistant UI test files: 155 passed, with no failures, skips or cancellations.
node test/run.js: 2,450 passed, zero failed.- Normal
npm run build:all: both browser builds passed; all 1,182 source/build files matched. - Syntax and whitespace checks passed. Main remained
6da190593be3990dceb83396fb42b9e779ef9f1e, with no new upstream commits or merge conflicts. The 29 unrelated local files were preserved.
The full 9,765-case coverage run above belongs to the original audited source, before this follow-up. It was not rerun for this focused change. These results do not add a real-account endurance or fresh model-reliability claim. Runtime version remains 40.0.8.
Local evidence: ci/artifacts/quality-audit-2026-10-07/pr408-cold-run-ui-snapshot-7f40172c-9f97-48e2-bdf7-6d22bf10069f/green-result.json (SHA-256 5f1f32a8e5a650dda11171f861dc8787981be3db90b01ff0e36b7a587e1a437f) and the neighbouring/main logs under ci/artifacts/pr408-review-cycle/. Private artifacts are not published.
The completed scan of the preceding exact head fa49ffef now confirms workflow fixture alert #234 fixed. Its PR inventory contains 59 open alerts and one fixed alert among the same 60 IDs; no new alert IDs appeared. JavaScript analysis returned 59 findings without analysis errors, while Python and Actions returned zero. The separate findings check still reports 31 changed-code annotations: 30 high and one medium.
The bounded review finds no additional confirmed actionable regression in the 18 test/report/builder annotations: current paths use text-node assignment, escaped or numeric output, HTML-safe JSON serialization, trusted fixture parsing or intentional operator-authored CLI regexes. The 13 shipping annotations retain their inherited conditional trust/fidelity assessments; their flagged statements are also present on main, but that comparison does not close vulnerabilities. No findings were dismissed or waived, and this is not a security-clean claim.
This correction requires a fresh Codex review. Merge readiness must use that review and the resulting head's checks; the earlier review and scan do not qualify a later revision.