Skip to content

Open-source AI browser agent for Chrome and Firefox (monorepo) 🧠

docs: add fresh PR scan results to the 40.2.0 audit

Emre Sokullufa49ffefda21
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 9b18626a9..a7bb519da 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -12,7 +12,7 @@ This changelog was generated from the repository Git history and release tags. V
- Mid-run task changes, Stop, durable chat recovery, Telegram/WhatsApp observation, recipient ownership and completion receipts are covered by causal and installed-browser regressions.
- File download/upload ownership, literal editor input, exact calculation and complete literal table delivery are repaired across Chrome and Firefox.
- The final unfiltered suite passed 9,765 Node/main cases and all 21 installed browser stages. Coverage: 65.16% lines/statements, 78.74% branches, 87.25% functions. Both browser builds passed.
-- Real-account two-hour endurance remains unverified. The last remote scan still had 77 open alerts on main; these local fixes require a new GitHub scan. This entry records the proposed release; the audited runtime remains 40.0.8.
+- Real-account two-hour endurance remains unverified. The first fresh PR CodeQL findings check flagged 32 changed-code alerts (31 high, one medium); the comparison and directly related QA fixture repair are recorded in the appendix. This entry records the proposed release; the audited runtime remains 40.0.8.
The complete dated audit, including earlier failures, tracked effects and verification limits, is copied in the [40.2.0 appendix at the end of this changelog](#appendix-4020-quality-audit). A standalone copy is available in [the audit report](docs/quality-audit-2026-10-07.md).
@@ -23,6 +23,7 @@ The complete dated audit, including earlier failures, tracked effects and verifi
- Added a full-suite Node coverage command and optional live-model browser checks.
### Fixed
+- Reject injected URL parameters in the disposable workflow QA server without changing valid fixtures or weakening replay checks.
- Keep Enter-dispatch uncertainty truthful when reusing an owned chat draft, without weakening pending-send or duplicate-send guards.
- Preserve exact native commit acknowledgement provenance for independent completion reconciliation after interrupted observation.
- Bind planner reference-history repair to the current task, permit at most one verified replan, and recheck Stop/steering authority.
@@ -4916,3 +4917,29 @@ Evidence: Root closed qualification (local evidence: `ci/artifacts/quality-audit
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](https://github.com/esokullu/webbrain/security/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](https://github.com/esokullu/webbrain/pull/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](https://github.com/esokullu/webbrain/runs/114367191053) **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 `--only` filters 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.
diff --git a/docs/quality-audit-2026-10-07.md b/docs/quality-audit-2026-10-07.md
index c4af8f076..78c9e35a2 100644
--- a/docs/quality-audit-2026-10-07.md
+++ b/docs/quality-audit-2026-10-07.md
@@ -305,3 +305,29 @@ Evidence: Root closed qualification (local evidence: `ci/artifacts/quality-audit
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](https://github.com/esokullu/webbrain/security/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](https://github.com/esokullu/webbrain/pull/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](https://github.com/esokullu/webbrain/runs/114367191053) **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 `--only` filters 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.