From 4a89782ff60cb45c166f967140b6581ac3d716d8 Mon Sep 17 00:00:00 2001
From: Bikebrainz <133275931+Bikebrainz@users.noreply.github.com>
Date: Tue, 29 Sep 2026 02:34:45 -0600
Subject: [PATCH 1/9] Document build follow-ups and correct roadmap evidence

---
 CHANGELOG.md                               |   6 +
 docs/changelog.html                        |   1 +
 docs/reviews/2026-09-29-build-follow-up.md | 150 +++++++++++++++++++++
 docs/reviews/README.md                     |   1 +
 docs/roadmap/index.html                    |  13 +-
 docs/roadmap/parity.json                   |  25 ++--
 scripts/parity_report.py                   |  11 +-
 7 files changed, 184 insertions(+), 23 deletions(-)
 create mode 100644 docs/reviews/2026-09-29-build-follow-up.md

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 0fb52563..cb587b7c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,12 @@ developer-facing record.
 
 ## [Unreleased]
 
+### Build follow-up
+- Add the September 29 to-do list with reproduced gaps and acceptance checks.
+- Correct stale scope-enforcement evidence and distinguish native QML Send
+  behavior from asynchronous browser/API/CLI sends.
+- Label roadmap grade changes as changes, including downward corrections.
+
 ### Repeater CLI and roadmap
 - Report response presence per tab instead of treating missing response text as
   a completed response. Clear elapsed-time and byte-count metadata on duplicated
diff --git a/docs/changelog.html b/docs/changelog.html
index 0361e1a4..07034909 100644
--- a/docs/changelog.html
+++ b/docs/changelog.html
@@ -52,6 +52,7 @@ <h1 class="h1-page grad-text" style="margin:10px 0 0;">What shipped</h1>
         <div class="rel-body">
           <p class="rel-note">Security checks now distinguish effective response headers from malformed lookalikes. These changes are in the development build; v3.8.0 remains the latest release listed below.</p>
           <ul>
+            <li><span class="tag fix">fix</span> <strong>Build follow-up and roadmap corrections.</strong> The <a href="https://github.com/Bikebrainz/Nullock/blob/Nullock/docs/reviews/2026-09-29-build-follow-up.md">September 29 checklist</a> records remaining byte-fidelity, HTML-context, cancellation, fixture-isolation and certificate-lifecycle work. Scope enforcement evidence is refreshed, and the native window's blocking Send path is called out separately.</li>
             <li><span class="tag fix">fix</span> <strong>Request files keep their binary bodies.</strong> Repeater CLI file and stdin loading preserves NUL bytes, non-UTF-8 data and trailing newlines. Invalid input leaves the draft unchanged; an empty file explicitly clears it. Tab summaries distinguish fresh tabs from completed responses, and duplicated tabs clear their old response metadata.</li>
             <li><span class="tag fix">fix</span> <strong>Repeater CLI loads the right request and waits for sends.</strong> History IDs select the complete captured request, including binary bodies. Send polling handles pending responses and reports refusals or unfinished waits. The new <code class="inline">repeater stop</code> command stops after the current response. The roadmap now distinguishes working views and responsive sends from the remaining byte-fidelity and immediate-cancellation gaps.</li>
             <li><span class="tag fix">fix</span> <strong>Reflected-XSS checks respect HTML tag boundaries.</strong> Iframe fallback text stays inert; custom tag names and abruptly closed comments no longer hide reflections. The roadmap now marks this probe as partial because template and SVG/MathML context handling still needs work.</li>
diff --git a/docs/reviews/2026-09-29-build-follow-up.md b/docs/reviews/2026-09-29-build-follow-up.md
new file mode 100644
index 00000000..36919fe7
--- /dev/null
+++ b/docs/reviews/2026-09-29-build-follow-up.md
@@ -0,0 +1,150 @@
+# September 29 build follow-up
+
+Owner: Bikebrainz. This is the next-work checklist from the September 29 build
+and verification pass. The [capability register](../roadmap/parity.json) remains
+the full roadmap; this list prioritizes gaps reproduced or inspected during the
+session. An unchecked item is not implemented.
+
+## Changes from this build
+
+| Change | Pull request | Status |
+| --- | --- | --- |
+| Effective security headers and strict TLS certificate compatibility | [#21](https://github.com/Bikebrainz/Nullock/pull/21) | Merged |
+| Reflected-XSS media types and HTML boundaries; certificate-cache validation | [#22](https://github.com/Bikebrainz/Nullock/pull/22) | CI pending |
+| Stable history IDs, asynchronous CLI send polling and Stop | [#25](https://github.com/Bikebrainz/Nullock/pull/25) | CI pending |
+| Binary file/stdin requests and accurate tab response indicators | [#26](https://github.com/Bikebrainz/Nullock/pull/26) | CI pending |
+
+Every implementation PR also updates the public changelog and roadmap. These
+are development changes; they do not create a release or change the latest
+published version. Certificate details from #23 and HTML-context details from
+#24 were incorporated into #22.
+
+## Next work, in priority order
+
+### 1. Preserve response bytes through Repeater and Hex views
+
+- [ ] Carry the original response bytes through the tab model, snapshot and
+  per-tab history, with a separate decoded display representation.
+- [ ] Make request Hex honor the request's actual UTF-8 or Latin-1 encoding.
+- [ ] Make response Hex and binary export use the selected byte representation.
+
+**Evidence:** a loopback response body `00 ff 80 41` becomes
+`00 U+FFFD U+FFFD 41` in Repeater. `Repeater::send` converts the raw or decoded
+body with `QString::fromUtf8`; `toHexDump` then UTF-8-encodes the display text.
+The original bytes cannot be recovered from that string. A Latin-1 request can
+send correctly while its Hex view shows different bytes.
+
+**Done when:** all 256 byte values survive send, snapshot, history navigation,
+project save/reload and export; Hex matches the fixture bytes. Compressed
+responses distinguish original wire bytes from decoded body bytes. Include
+empty bodies, invalid UTF-8, NULs and bodies larger than the preview limit.
+
+### 2. Correct the remaining reflected-XSS HTML contexts
+
+- [ ] Handle inert template contents and SVG/MathML parsing contexts.
+- [ ] Expand the pinned-browser corpus before changing the parser or its grade.
+
+**Evidence:** after the tag-boundary fixes, a 97-context browser comparison left
+two mismatches for the marker `<nlk0a1b2c3d>`:
+
+| HTML | Native marker classification | Chromium element present |
+| --- | --- | --- |
+| `<template><nlk0a1b2c3d>` | true | false |
+| `<svg><title><nlk0a1b2c3d>` | false | true |
+
+The browser result describes this marker's parsed context, not a proof that an
+arbitrary script payload executes. Existing committed browser coverage lives in
+`Tests/ui/xss_context_browser_test.cjs` and `xss_media_types_browser_test.cjs`.
+
+**Done when:** the corpus covers nested templates, foreign-content integration
+points, malformed nesting and script/raw-text states, with native results
+matching the pinned browser. Keep XML execution, stored XSS and DOM XSS outside
+the claim unless they receive their own implementation and verification.
+
+### 3. Finish Repeater cancellation and native-window responsiveness
+
+- [ ] Route the native QML Send button through the asynchronous send path and
+  expose the same Stop state as the browser.
+- [ ] Add cancellation to the socket-owning worker during connection, TLS,
+  header and body waits.
+- [ ] Keep concurrent sends from separate tabs as a separate design task.
+
+**Evidence:** browser/API/CLI sends use `sendAsync`, but `Src/App/app.qml` still
+calls `repeater.send()` directly. Current Stop sets an atomic flag checked
+between responses and redirects; it does not interrupt a stalled socket.
+`HttpClient` uses per-wait timeouts and a five-minute total read budget.
+
+**Done when:** a controlled stalled connection, TLS handshake, header, fixed body
+and chunked body can each be stopped promptly without cross-thread socket use.
+The native window and browser remain responsive, no extra redirect is sent,
+newer edits survive completion, and shutdown joins the worker cleanly.
+
+### 4. Isolate OAST smoke fixtures and retain callback diagnostics
+
+- [ ] Allocate separate HTTP and DNS sink ports for each smoke run, alongside
+  the control/proxy ports, and verify startup on the requested listeners.
+- [ ] Report callback failures from the mock instead of discarding exceptions.
+- [ ] Check concurrent isolated runs and deliberate port conflicts.
+
+**Evidence:** one integrated run passed 193 checks and missed three HTTP OAST
+callbacks (SSRF, RCE and XXE); an isolated retry passed all 196. The cause of
+that first failure is not established. `scripts/probe_smoke.sh` uses the default
+OAST ports and suppresses exceptions from its HTTP callback mock.
+
+**Done when:** concurrent runs do not share sinks or state, listener failures
+produce a clear startup error, and callback diagnostics identify the failed
+operation. Retain token-specific positive assertions and safe-target negative
+controls; do not replace them with longer blind waits or automatic pass-on-retry.
+
+### 5. Complete CA and certificate-cache lifecycle controls
+
+- [ ] Revalidate expiry before returning an in-memory leaf.
+- [ ] Define explicit CA/key validation and repair, including operator-visible
+  trust changes.
+- [ ] Add supported CA replacement and leaf-cache clearing/eviction controls.
+
+**Evidence:** `CertAuthority::leafCertFor` returns an in-memory cache hit before
+checking dates or the current CA. Disk-cache reuse after restart now checks the
+CA signature, private key, DNS/IP SAN, dates and key identifiers. That fix does
+not provide live CA replacement or repair of a broken root/key pair.
+
+**Done when:** a controlled clock test refreshes an expired memory entry; valid
+entries remain reusable; CA rotation cannot leave mixed old/new leaves; failures
+are actionable without silently replacing a trusted root. Preserve owner-only
+key permissions and test both OpenSSL and LibreSSL certificate generation.
+
+### 6. Keep roadmap evidence specific and current
+
+- [ ] Audit remaining entries whose gap text contradicts their current state or
+  cites superseded line numbers and behavior.
+- [ ] Give browser, CLI and native-window behavior separate descriptions when
+  their implementations differ.
+- [ ] Require a runnable regression or a precise source reference for each
+  reconciliation; retain limitations instead of inferring full parity.
+
+This pass corrects the obsolete Repeater scope-bypass claim: the shared
+`HttpClient` checks outbound scope before connecting, including redirects, and
+the API snapshots the request synchronously before scheduling its worker.
+The 41-check outbound-scope regression passes. The native window's remaining
+blocking Send behavior is a separate issue described above.
+
+## Verification to carry forward
+
+- Native suites: 102 passed on the combined XSS/certificate implementation.
+- Public probe smoke: 196 passed on the isolated rerun; the earlier OAST misses
+  remain recorded above.
+- Strict TLS and runtime regressions: 64 checks with the native-window option;
+  the later CLI build also passed 62 headless runtime checks.
+- Pinned Chromium: 72 media-type and 95 HTML-context comparisons passed. An
+  additional 1,238 generated media-type comparisons found no mismatches.
+- CLI fixtures and real-app checks cover stable IDs, binary history bodies,
+  multiple busy polls, refusal/timeouts, Stop, binary files/stdin, UTF-8, invalid
+  base64 and fresh/completed/duplicated tab indicators.
+- Website checks cover links, script integrity, generated-page freshness and
+  desktop/mobile roadmap and changelog layout.
+
+For each follow-up, update `CHANGELOG.md`, `docs/changelog.html` and the affected
+roadmap evidence together. Run `python scripts/parity_report.py` after changing
+the register, then `python scripts/check_web_assets.py` and the relevant
+application/browser regression. Cross-platform CI must pass on the exact PR
+head before an implementation merge.
diff --git a/docs/reviews/README.md b/docs/reviews/README.md
index 183bd5c6..93350970 100644
--- a/docs/reviews/README.md
+++ b/docs/reviews/README.md
@@ -4,3 +4,4 @@ Keep dated engineering reviews here. These describe the repository at the time
 of review; historical paths and findings may differ from the current code.
 
 - [2026-08-11 HTTP security review](2026-08-11-http-security.md)
+- [2026-09-29 build follow-up and to-do list](2026-09-29-build-follow-up.md)
diff --git a/docs/roadmap/index.html b/docs/roadmap/index.html
index ecc3850b..8195eb5e 100644
--- a/docs/roadmap/index.html
+++ b/docs/roadmap/index.html
@@ -43,19 +43,20 @@ <h1 class="h1-hero grad-text" style="max-width:20ch;">Every Burp feature, graded
 
 <main class="wrap-wide" style="padding:30px var(--pad-x) 72px;display:flex;flex-direction:column;gap:30px;">
 
-  <section class="rm-verdict"><div class="rm-cell"><span class="rm-num s-absent">72</span><span class="rm-lab mono">absent</span></div><div class="rm-cell"><span class="rm-num s-stub">6</span><span class="rm-lab mono">stub</span></div><div class="rm-cell"><span class="rm-num s-partial">95</span><span class="rm-lab mono">partial</span></div><div class="rm-cell"><span class="rm-num s-present">215</span><span class="rm-lab mono">present</span></div><div class="rm-cell"><span class="rm-num s-exceeds">22</span><span class="rm-lab mono">exceeds</span></div><div class="rm-cell"><span class="rm-num">58%</span><span class="rm-lab mono">at parity</span></div></section>
+  <section class="rm-verdict"><div class="rm-cell"><span class="rm-num s-absent">72</span><span class="rm-lab mono">absent</span></div><div class="rm-cell"><span class="rm-num s-stub">6</span><span class="rm-lab mono">stub</span></div><div class="rm-cell"><span class="rm-num s-partial">95</span><span class="rm-lab mono">partial</span></div><div class="rm-cell"><span class="rm-num s-present">216</span><span class="rm-lab mono">present</span></div><div class="rm-cell"><span class="rm-num s-exceeds">21</span><span class="rm-lab mono">exceeds</span></div><div class="rm-cell"><span class="rm-num">58%</span><span class="rm-lab mono">at parity</span></div></section>
 
   <section class="panel">
     <h2>Where the work is</h2>
+    <p>Start with the <a href="https://github.com/Bikebrainz/Nullock/blob/Nullock/docs/reviews/2026-09-29-build-follow-up.md">September 29 build follow-up</a> for reproduced gaps, priorities and acceptance checks.</p>
     <p class="muted" style="font-size:13.5px;">One bar per functional area, ordered worst-first. Click an area to filter the register.</p>
-    <div class="rm-matrix"><button class="rm-row" data-area="extender" aria-pressed="false"><span class="rm-name mono">Extender</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:48.98%" title="24 absent"></i><i class="rm-seg s-stub" style="width:6.12%" title="3 stub"></i><i class="rm-seg s-partial" style="width:24.49%" title="12 partial"></i><i class="rm-seg s-present" style="width:18.37%" title="9 present"></i><i class="rm-seg s-exceeds" style="width:2.04%" title="1 exceeds"></i></span><span class="rm-tot mono">49</span></button><button class="rm-row" data-area="platform" aria-pressed="false"><span class="rm-name mono">Platform</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:20.00%" title="10 absent"></i><i class="rm-seg s-stub" style="width:2.00%" title="1 stub"></i><i class="rm-seg s-partial" style="width:32.00%" title="16 partial"></i><i class="rm-seg s-present" style="width:38.00%" title="19 present"></i><i class="rm-seg s-exceeds" style="width:8.00%" title="4 exceeds"></i></span><span class="rm-tot mono">50</span></button><button class="rm-row" data-area="proxy" aria-pressed="false"><span class="rm-name mono">Proxy</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:18.00%" title="9 absent"></i><i class="rm-seg s-stub" style="width:2.00%" title="1 stub"></i><i class="rm-seg s-partial" style="width:32.00%" title="16 partial"></i><i class="rm-seg s-present" style="width:44.00%" title="22 present"></i><i class="rm-seg s-exceeds" style="width:4.00%" title="2 exceeds"></i></span><span class="rm-tot mono">50</span></button><button class="rm-row" data-area="sequencer" aria-pressed="false"><span class="rm-name mono">Sessions</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:17.24%" title="10 absent"></i><i class="rm-seg s-partial" style="width:25.86%" title="15 partial"></i><i class="rm-seg s-present" style="width:51.72%" title="30 present"></i><i class="rm-seg s-exceeds" style="width:5.17%" title="3 exceeds"></i></span><span class="rm-tot mono">58</span></button><button class="rm-row" data-area="target" aria-pressed="false"><span class="rm-name mono">Target</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:16.28%" title="7 absent"></i><i class="rm-seg s-partial" style="width:25.58%" title="11 partial"></i><i class="rm-seg s-present" style="width:53.49%" title="23 present"></i><i class="rm-seg s-exceeds" style="width:4.65%" title="2 exceeds"></i></span><span class="rm-tot mono">43</span></button><button class="rm-row" data-area="scanner" aria-pressed="false"><span class="rm-name mono">Scanner</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:8.70%" title="4 absent"></i><i class="rm-seg s-stub" style="width:2.17%" title="1 stub"></i><i class="rm-seg s-partial" style="width:26.09%" title="12 partial"></i><i class="rm-seg s-present" style="width:63.04%" title="29 present"></i></span><span class="rm-tot mono">46</span></button><button class="rm-row" data-area="repeater" aria-pressed="false"><span class="rm-name mono">Repeater+</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:7.69%" title="5 absent"></i><i class="rm-seg s-partial" style="width:16.92%" title="11 partial"></i><i class="rm-seg s-present" style="width:61.54%" title="40 present"></i><i class="rm-seg s-exceeds" style="width:13.85%" title="9 exceeds"></i></span><span class="rm-tot mono">65</span></button><button class="rm-row" data-area="intruder" aria-pressed="false"><span class="rm-name mono">Intruder</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:6.12%" title="3 absent"></i><i class="rm-seg s-partial" style="width:4.08%" title="2 partial"></i><i class="rm-seg s-present" style="width:87.76%" title="43 present"></i><i class="rm-seg s-exceeds" style="width:2.04%" title="1 exceeds"></i></span><span class="rm-tot mono">49</span></button></div>
+    <div class="rm-matrix"><button class="rm-row" data-area="extender" aria-pressed="false"><span class="rm-name mono">Extender</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:48.98%" title="24 absent"></i><i class="rm-seg s-stub" style="width:6.12%" title="3 stub"></i><i class="rm-seg s-partial" style="width:24.49%" title="12 partial"></i><i class="rm-seg s-present" style="width:18.37%" title="9 present"></i><i class="rm-seg s-exceeds" style="width:2.04%" title="1 exceeds"></i></span><span class="rm-tot mono">49</span></button><button class="rm-row" data-area="platform" aria-pressed="false"><span class="rm-name mono">Platform</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:20.00%" title="10 absent"></i><i class="rm-seg s-stub" style="width:2.00%" title="1 stub"></i><i class="rm-seg s-partial" style="width:32.00%" title="16 partial"></i><i class="rm-seg s-present" style="width:38.00%" title="19 present"></i><i class="rm-seg s-exceeds" style="width:8.00%" title="4 exceeds"></i></span><span class="rm-tot mono">50</span></button><button class="rm-row" data-area="proxy" aria-pressed="false"><span class="rm-name mono">Proxy</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:18.00%" title="9 absent"></i><i class="rm-seg s-stub" style="width:2.00%" title="1 stub"></i><i class="rm-seg s-partial" style="width:32.00%" title="16 partial"></i><i class="rm-seg s-present" style="width:44.00%" title="22 present"></i><i class="rm-seg s-exceeds" style="width:4.00%" title="2 exceeds"></i></span><span class="rm-tot mono">50</span></button><button class="rm-row" data-area="sequencer" aria-pressed="false"><span class="rm-name mono">Sessions</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:17.24%" title="10 absent"></i><i class="rm-seg s-partial" style="width:25.86%" title="15 partial"></i><i class="rm-seg s-present" style="width:51.72%" title="30 present"></i><i class="rm-seg s-exceeds" style="width:5.17%" title="3 exceeds"></i></span><span class="rm-tot mono">58</span></button><button class="rm-row" data-area="target" aria-pressed="false"><span class="rm-name mono">Target</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:16.28%" title="7 absent"></i><i class="rm-seg s-partial" style="width:25.58%" title="11 partial"></i><i class="rm-seg s-present" style="width:53.49%" title="23 present"></i><i class="rm-seg s-exceeds" style="width:4.65%" title="2 exceeds"></i></span><span class="rm-tot mono">43</span></button><button class="rm-row" data-area="scanner" aria-pressed="false"><span class="rm-name mono">Scanner</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:8.70%" title="4 absent"></i><i class="rm-seg s-stub" style="width:2.17%" title="1 stub"></i><i class="rm-seg s-partial" style="width:26.09%" title="12 partial"></i><i class="rm-seg s-present" style="width:63.04%" title="29 present"></i></span><span class="rm-tot mono">46</span></button><button class="rm-row" data-area="repeater" aria-pressed="false"><span class="rm-name mono">Repeater+</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:7.69%" title="5 absent"></i><i class="rm-seg s-partial" style="width:16.92%" title="11 partial"></i><i class="rm-seg s-present" style="width:63.08%" title="41 present"></i><i class="rm-seg s-exceeds" style="width:12.31%" title="8 exceeds"></i></span><span class="rm-tot mono">65</span></button><button class="rm-row" data-area="intruder" aria-pressed="false"><span class="rm-name mono">Intruder</span><span class="rm-bar"><i class="rm-seg s-absent" style="width:6.12%" title="3 absent"></i><i class="rm-seg s-partial" style="width:4.08%" title="2 partial"></i><i class="rm-seg s-present" style="width:87.76%" title="43 present"></i><i class="rm-seg s-exceeds" style="width:2.04%" title="1 exceeds"></i></span><span class="rm-tot mono">49</span></button></div>
     <div class="rm-legend"><span><i class="rm-dot s-absent"></i>absent</span><span><i class="rm-dot s-stub"></i>stub</span><span><i class="rm-dot s-partial"></i>partial</span><span><i class="rm-dot s-present"></i>present</span><span><i class="rm-dot s-exceeds"></i>exceeds</span></div>
   </section>
 
   <section class="panel">
     <h2>Recently updated</h2>
-    <p class="muted" style="font-size:13.5px;">Capabilities reconciled since the audit, including closed gaps and corrections, newest first. Each entry records its date and implementation commit. Showing the 24 most recent of 410 reconciled since the audit; the full set is in the capability table below.</p>
-    <ul class="rm-recent"><li><span class="mono rm-commit">0665e41b</span> <span class="mono rm-date">2026-09-29</span> <strong>[A4] Passive audit: missing security headers (CSP/HSTS/XFO/XCTO/RP/Permissions-Policy/COOP</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Hardened active and passive security-header parsing for repeated fields, fallback policies and malformed whitespace. Native regressions and pinned Chromium comparisons cover effective values. Existing capability remains present.</span></li><li><span class="mono rm-commit">b392a63b</span> <span class="mono rm-date">2026-09-29</span> <strong>[A12] Active audit: reflected XSS</strong> <span class="rm-move mono">present &rarr; partial</span><br><span class="muted">Correct 66 browser/analyzer mismatches involving custom tag names, iframe fallback text and abrupt comment closure. Add 95 pinned-browser context comparisons and five public-API fixtures. Downgrade present to partial after separately reproducing template and SVG context gaps; those cases remain follow-up work.</span></li><li><span class="mono rm-commit">784284db</span> <span class="mono rm-date">2026-09-29</span> <strong>Proxy listener &gt; Certificate &gt; Generate CA-signed per-host certificate (per-host leaf mint</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Declare leaf key identifiers explicitly so strict TLS clients accept LibreSSL-generated certificates. Runtime regression exercises real proxy HTTPS with strict validation enabled on every Python version.</span></li><li><span class="mono rm-commit">4c44d3c0</span> <span class="mono rm-date">2026-09-29</span> <strong>CA certificate: leaf caching across restarts</strong><br><span class="muted">Verify the current CA, private key and requested DNS/IP subject alternative name before disk-cache reuse. Strict HTTPS regressions cover wrong and missing SANs; focused checks retain valid DNS, IPv4 and IPv6 leaves.</span></li><li><span class="mono rm-commit">c2af0a33</span> <span class="mono rm-date">2026-09-29</span> <strong>CA private key hardening on disk</strong> <span class="rm-move mono">exceeds &rarr; present</span><br><span class="muted">Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits. Grade changed from exceeds to present.</span></li><li><span class="mono rm-commit">697499b7</span> <span class="mono rm-date">2026-09-29</span> <strong>Repeater: send a captured message to Repeater from other tools</strong><br><span class="muted">CLI file and stdin input preserve raw body bytes. Empty input clears the draft, omitted input preserves it, and invalid base64 is rejected before mutation. Existing missing tool pivots keep the grade partial.</span></li><li><span class="mono rm-commit">f5dcae31</span> <span class="mono rm-date">2026-09-29</span> <strong>Repeater: headless / scriptable driving of the tool</strong> <span class="rm-move mono">exceeds &rarr; present</span><br><span class="muted">Verified the CLI through owned API fixtures and a real app: history IDs, asynchronous sends, Stop, binary file/stdin input and tab response state. Replaced stale defect descriptions and removed an unverified exceeds comparison.</span></li><li><span class="mono rm-commit">c2af0a33</span> <span class="mono rm-date">2026-09-29</span> <strong>Repeater: message editor views — Pretty / Raw / Hex for both request and response</strong> <span class="rm-move mono">absent &rarr; partial</span><br><span class="muted">Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits. Grade changed from present to partial.</span></li><li><span class="mono rm-commit">c2af0a33</span> <span class="mono rm-date">2026-09-29</span> <strong>Repeater: automatic &quot;Update Content-Length&quot; when the body is edited</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits.</span></li><li><span class="mono rm-commit">c2af0a33</span> <span class="mono rm-date">2026-09-29</span> <strong>Repeater: &quot;Unpack gzip / deflate&quot; in the response view</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits.</span></li><li><span class="mono rm-commit">c2af0a33</span> <span class="mono rm-date">2026-09-29</span> <strong>Repeater: cancel an in-flight request; non-blocking send</strong><br><span class="muted">Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits. Grade changed from absent to partial.</span></li><li><span class="mono rm-commit">76c583ff</span> <span class="mono rm-date">2026-09-11</span> <strong>Save/Resume attack</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Existing manual SAVE/LOAD/RESUME is retained. Project switch and clean exit now save automatically; restoration remains idle and pending rows still need explicit Resume. CLI adds save/load/reset.</span></li><li><span class="mono rm-commit"></span> <span class="mono rm-date">2026-09-11</span> <strong>[A36] Authenticated scanning: session-handling rules (macros)</strong><br><span class="muted">HTTP authenticated scan workflows verified, including form CSRF replacement, compressed token extraction, refresh cooldown, request fidelity and project isolation. Browser login execution remains a separate gap.</span></li><li><span class="mono rm-commit"></span> <span class="mono rm-date">2026-09-11</span> <strong>[A37] Out-of-scope handling during scans</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Full outbound scope boundary, live policy updates, full-URL redirect/crawler checks and visible validation errors.</span></li><li><span class="mono rm-commit">17d6c051</span> <span class="mono rm-date">2026-09-11</span> <strong>Cookie jar and session rules persist in the project file / user settings across restarts</strong> <span class="rm-move mono">absent &rarr; present</span><br><span class="muted">Cookie jars and session rules persist per project. Cookie changes autosave every two seconds and after shutdown workers drain; session-rule edits save when applied. Failed workspace writes remain visible and block project switching. Transient extracted session variables are intentionally cleared when changing projects.</span></li><li><span class="mono rm-commit"></span> <span class="mono rm-date">2026-09-11</span> <strong>Recorded login sequences (browser-recorded login replayed by the scanner) for authenticate</strong><br><span class="muted">HTTP authenticated scan workflows verified, including form CSRF replacement, compressed token extraction, refresh cooldown, request fidelity and project isolation. Browser login execution remains a separate gap.</span></li><li><span class="mono rm-commit">63ecda0e</span> <span class="mono rm-date">2026-09-11</span> <strong>Annotations: per-item Notes column and colour highlighting on Proxy history / any message </strong> <span class="rm-move mono">partial &rarr; partial</span><br><span class="muted">Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action.</span></li><li><span class="mono rm-commit">f24543d3</span> <span class="mono rm-date">2026-09-11</span> <strong>Project files: Repeater tabs, Intruder attack config and Sequencer state saved in the proj</strong> <span class="rm-move mono">absent &rarr; partial</span><br><span class="muted">Intruder configuration and result rows persist per project on switch/clean exit and restore idle. Browser drafts survive stale polls; rules/grep settings synchronize and stale project edits are refused. Runtime, browser and CLI checks pass. Sequencer persistence remains outstanding.</span></li><li><span class="mono rm-commit">63ecda0e</span> <span class="mono rm-date">2026-09-11</span> <strong>HTTP history filter bar (in-scope only / hide items without responses / MIME / status / re</strong><br><span class="muted">Annotation persistence caveat removed; unrelated filtering gaps remain documented.</span></li><li><span class="mono rm-commit">63ecda0e</span> <span class="mono rm-date">2026-09-11</span> <strong>HTTP history annotations: per-item highlight colours and comments, plus filter-by-annotati</strong> <span class="rm-move mono">partial &rarr; present</span><br><span class="muted">Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action.</span></li><li><span class="mono rm-commit">c30a3eae</span> <span class="mono rm-date">2026-09-11</span> <strong>Repeater: multiple concurrent request tabs</strong><br><span class="muted">The GUI/control Repeater runs one request at a time on a worker, preserving UI responsiveness and edits made during a send. Busy/Stop states are exposed; Stop prevents subsequent redirects after the current response. Browser mutations are serialized and stale polls cannot overwrite pending edits. Tabs autosave per project. Independent concurrent sends across multiple tabs remain unavailable.</span></li><li><span class="mono rm-commit">17d6c051</span> <span class="mono rm-date">2026-09-11</span> <strong>Repeater: tab state persisted in the project file and restored on reopen</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Repeater tabs save per project every two seconds when changed, before project switching, and after shutdown workers drain. Failed writes retain the current project and retry. Per-tab request history remains a separate capability.</span></li><li><span class="mono rm-commit">63ecda0e</span> <span class="mono rm-date">2026-09-11</span> <strong>Site map filter — by MIME type (HTML/Script/XML/CSS/Other text/Images/Flash/Other binary),</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Annotation persistence caveat removed; unrelated filtering gaps remain documented.</span></li><li><span class="mono rm-commit">63ecda0e</span> <span class="mono rm-date">2026-09-11</span> <strong>Site map / history annotations: per-item Comment and Highlight (six colours), used to driv</strong> <span class="rm-move mono">partial &rarr; present</span><br><span class="muted">Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action.</span></li></ul>
+    <p class="muted" style="font-size:13.5px;">Capabilities reconciled since the audit, including closed gaps and corrections, newest first. Each entry records its date and source or verification commit. Showing the 24 most recent of 410 reconciled since the audit; the full set is in the capability table below.</p>
+    <ul class="rm-recent"><li><span class="mono rm-commit">0665e41b</span> <span class="mono rm-date">2026-09-29</span> <strong>[A4] Passive audit: missing security headers (CSP/HSTS/XFO/XCTO/RP/Permissions-Policy/COOP</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Hardened active and passive security-header parsing for repeated fields, fallback policies and malformed whitespace. Native regressions and pinned Chromium comparisons cover effective values. Existing capability remains present.</span></li><li><span class="mono rm-commit">b392a63b</span> <span class="mono rm-date">2026-09-29</span> <strong>[A12] Active audit: reflected XSS</strong> <span class="rm-move mono">present &rarr; partial</span><br><span class="muted">Correct 66 browser/analyzer mismatches involving custom tag names, iframe fallback text and abrupt comment closure. Add 95 pinned-browser context comparisons and five public-API fixtures. Downgrade present to partial after separately reproducing template and SVG context gaps; those cases remain follow-up work.</span></li><li><span class="mono rm-commit">784284db</span> <span class="mono rm-date">2026-09-29</span> <strong>Proxy listener &gt; Certificate &gt; Generate CA-signed per-host certificate (per-host leaf mint</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Declare leaf key identifiers explicitly so strict TLS clients accept LibreSSL-generated certificates. Runtime regression exercises real proxy HTTPS with strict validation enabled on every Python version.</span></li><li><span class="mono rm-commit">4c44d3c0</span> <span class="mono rm-date">2026-09-29</span> <strong>CA certificate: leaf caching across restarts</strong><br><span class="muted">Verify the current CA, private key and requested DNS/IP subject alternative name before disk-cache reuse. Strict HTTPS regressions cover wrong and missing SANs; focused checks retain valid DNS, IPv4 and IPv6 leaves.</span></li><li><span class="mono rm-commit">c2af0a33</span> <span class="mono rm-date">2026-09-29</span> <strong>CA private key hardening on disk</strong> <span class="rm-move mono">exceeds &rarr; present</span><br><span class="muted">Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits. Grade changed from exceeds to present.</span></li><li><span class="mono rm-commit">697499b7</span> <span class="mono rm-date">2026-09-29</span> <strong>Repeater: send a captured message to Repeater from other tools</strong><br><span class="muted">CLI file and stdin input preserve raw body bytes. Empty input clears the draft, omitted input preserves it, and invalid base64 is rejected before mutation. Existing missing tool pivots keep the grade partial.</span></li><li><span class="mono rm-commit">927aed0e</span> <span class="mono rm-date">2026-09-29</span> <strong>Repeater: out-of-scope send guard</strong> <span class="rm-move mono">exceeds &rarr; present</span><br><span class="muted">Rechecked the existing shared scope implementation and reran 41 live scope checks. Removed obsolete API-only and queued-tab-switch claims; use present rather than an unverified comparison-based exceeds grade.</span></li><li><span class="mono rm-commit">f5dcae31</span> <span class="mono rm-date">2026-09-29</span> <strong>Repeater: headless / scriptable driving of the tool</strong> <span class="rm-move mono">exceeds &rarr; present</span><br><span class="muted">Verified the CLI through owned API fixtures and a real app: history IDs, asynchronous sends, Stop, binary file/stdin input and tab response state. Replaced stale defect descriptions and removed an unverified exceeds comparison.</span></li><li><span class="mono rm-commit">c2af0a33</span> <span class="mono rm-date">2026-09-29</span> <strong>Repeater: message editor views — Pretty / Raw / Hex for both request and response</strong> <span class="rm-move mono">absent &rarr; partial</span><br><span class="muted">Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits. Grade changed from present to partial.</span></li><li><span class="mono rm-commit">c2af0a33</span> <span class="mono rm-date">2026-09-29</span> <strong>Repeater: automatic &quot;Update Content-Length&quot; when the body is edited</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits.</span></li><li><span class="mono rm-commit">c2af0a33</span> <span class="mono rm-date">2026-09-29</span> <strong>Repeater: &quot;Unpack gzip / deflate&quot; in the response view</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits.</span></li><li><span class="mono rm-commit">c2af0a33</span> <span class="mono rm-date">2026-09-29</span> <strong>Repeater: cancel an in-flight request; non-blocking send</strong><br><span class="muted">Reconciled browser/API/CLI asynchronous sends and Stop, while recording the native QML synchronous-send path separately. Immediate socket cancellation and concurrent sends remain incomplete; grade stays partial.</span></li><li><span class="mono rm-commit">76c583ff</span> <span class="mono rm-date">2026-09-11</span> <strong>Save/Resume attack</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Existing manual SAVE/LOAD/RESUME is retained. Project switch and clean exit now save automatically; restoration remains idle and pending rows still need explicit Resume. CLI adds save/load/reset.</span></li><li><span class="mono rm-commit"></span> <span class="mono rm-date">2026-09-11</span> <strong>[A36] Authenticated scanning: session-handling rules (macros)</strong><br><span class="muted">HTTP authenticated scan workflows verified, including form CSRF replacement, compressed token extraction, refresh cooldown, request fidelity and project isolation. Browser login execution remains a separate gap.</span></li><li><span class="mono rm-commit"></span> <span class="mono rm-date">2026-09-11</span> <strong>[A37] Out-of-scope handling during scans</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Full outbound scope boundary, live policy updates, full-URL redirect/crawler checks and visible validation errors.</span></li><li><span class="mono rm-commit">17d6c051</span> <span class="mono rm-date">2026-09-11</span> <strong>Cookie jar and session rules persist in the project file / user settings across restarts</strong> <span class="rm-move mono">absent &rarr; present</span><br><span class="muted">Cookie jars and session rules persist per project. Cookie changes autosave every two seconds and after shutdown workers drain; session-rule edits save when applied. Failed workspace writes remain visible and block project switching. Transient extracted session variables are intentionally cleared when changing projects.</span></li><li><span class="mono rm-commit"></span> <span class="mono rm-date">2026-09-11</span> <strong>Recorded login sequences (browser-recorded login replayed by the scanner) for authenticate</strong><br><span class="muted">HTTP authenticated scan workflows verified, including form CSRF replacement, compressed token extraction, refresh cooldown, request fidelity and project isolation. Browser login execution remains a separate gap.</span></li><li><span class="mono rm-commit">63ecda0e</span> <span class="mono rm-date">2026-09-11</span> <strong>Annotations: per-item Notes column and colour highlighting on Proxy history / any message </strong> <span class="rm-move mono">partial &rarr; partial</span><br><span class="muted">Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action.</span></li><li><span class="mono rm-commit">f24543d3</span> <span class="mono rm-date">2026-09-11</span> <strong>Project files: Repeater tabs, Intruder attack config and Sequencer state saved in the proj</strong> <span class="rm-move mono">absent &rarr; partial</span><br><span class="muted">Intruder configuration and result rows persist per project on switch/clean exit and restore idle. Browser drafts survive stale polls; rules/grep settings synchronize and stale project edits are refused. Runtime, browser and CLI checks pass. Sequencer persistence remains outstanding.</span></li><li><span class="mono rm-commit">63ecda0e</span> <span class="mono rm-date">2026-09-11</span> <strong>HTTP history filter bar (in-scope only / hide items without responses / MIME / status / re</strong><br><span class="muted">Annotation persistence caveat removed; unrelated filtering gaps remain documented.</span></li><li><span class="mono rm-commit">63ecda0e</span> <span class="mono rm-date">2026-09-11</span> <strong>HTTP history annotations: per-item highlight colours and comments, plus filter-by-annotati</strong> <span class="rm-move mono">partial &rarr; present</span><br><span class="muted">Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action.</span></li><li><span class="mono rm-commit">c30a3eae</span> <span class="mono rm-date">2026-09-11</span> <strong>Repeater: multiple concurrent request tabs</strong><br><span class="muted">The GUI/control Repeater runs one request at a time on a worker, preserving UI responsiveness and edits made during a send. Busy/Stop states are exposed; Stop prevents subsequent redirects after the current response. Browser mutations are serialized and stale polls cannot overwrite pending edits. Tabs autosave per project. Independent concurrent sends across multiple tabs remain unavailable.</span></li><li><span class="mono rm-commit">17d6c051</span> <span class="mono rm-date">2026-09-11</span> <strong>Repeater: tab state persisted in the project file and restored on reopen</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Repeater tabs save per project every two seconds when changed, before project switching, and after shutdown workers drain. Failed writes retain the current project and retry. Per-tab request history remains a separate capability.</span></li><li><span class="mono rm-commit">63ecda0e</span> <span class="mono rm-date">2026-09-11</span> <strong>Site map filter — by MIME type (HTML/Script/XML/CSS/Other text/Images/Flash/Other binary),</strong> <span class="rm-move mono">present &rarr; present</span><br><span class="muted">Annotation persistence caveat removed; unrelated filtering gaps remain documented.</span></li></ul>
   </section>
 
   <section class="panel">
@@ -83,7 +84,7 @@ <h2>How this stays true</h2>
   <div>nul&middot;lock &#9656; audited 2026-07-30 &middot; reconciled through 2026-09-29 &middot; generated from parity.json</div>
 </footer>
 
-<script type="application/json" id="rm-data">[{"a":"intruder","f":"Attack type: Sniper","s":"present","i":"low","e":"hours","g":"None -- a MODE select in the Intruder target row (tabs.jsx) lets the user pick sniper explicitly, and the pane-head label reflects the live selection.","w":"Closed 2026-08-09: added an attack-type <select> (tabs.jsx target-row) bound to intruder.attackType, dispatching intruder-set{attackType} -> POST /api/intruder/set. Sniper is option 0.","v":"ui-v2/tabs.jsx ATTACK_TYPES select in IntruderTab's target-row; control_server.cpp:3209-3215 already parsed attackType (int or name).","o":"present","r":"Intruder wave: MODE selector (sniper/battering-ram/pitchfork/cluster-bomb) closes the GUI-reachability gap for all four attack types."},{"a":"intruder","f":"Attack type: Battering ram","s":"present","i":"low","e":"hours","g":"None -- selectable via the same MODE select as Sniper (option 1).","w":"Closed 2026-08-09: same MODE <select> as item 0; battering-ram is option 1, no backend change needed.","v":"ui-v2/tabs.jsx ATTACK_TYPES select; control_server.cpp:3209-3215 attackType parsing.","o":"present","r":"Intruder wave: MODE selector closes the GUI-reachability gap for all four attack types."},{"a":"intruder","f":"Attack type: Pitchfork","s":"present","i":"medium","e":"days","g":"None -- the MODE select plus a per-position PAYLOAD SETS column editor (shown when pitchfork/cluster-bomb is picked and the template has >1 §marker§) let the user fill payloadSets[i] per position from the GUI.","w":"Closed 2026-08-09: added a per-position multi-column payload-set editor (tabs.jsx IntruderTab, isMultiSet branch) that renders one textarea per §marker§ pair, dispatching intruder-set{payloadSets} -> POST /api/intruder/set. No backend change; setPayloadSets/syncSetsToPositions already existed.","v":"ui-v2/tabs.jsx PAYLOAD SETS pane (isMultiSet && posCount>1); control_server.cpp:3221-3232 payloadSets accepts one array per position; intruder_engine.cpp:86-104 zip-by-index engine.","o":"present","r":"Intruder wave: per-position payload-set editor closes Pitchfork's GUI-reachability gap."},{"a":"intruder","f":"Attack type: Cluster bomb","s":"present","i":"medium","e":"days","g":"None -- same per-position PAYLOAD SETS editor as Pitchfork (item 2); Cluster bomb is MODE option 3.","w":"Closed 2026-08-09: same multi-set editor as item 2; the engine's odometer/cartesian product was already complete, only the GUI to enter one set per position was missing.","v":"ui-v2/tabs.jsx PAYLOAD SETS pane; control_server.cpp:3221-3232 payloadSets; intruder_engine.cpp:105-129 odometer cartesian product.","o":"present","r":"Intruder wave: per-position payload-set editor closes Cluster bomb's GUI-reachability gap."},{"a":"intruder","f":"Payload positions (§marker§) + insertion","s":"present","i":"low","e":"hours","g":"","w":"Re-read findMarkers/applyPayloads; scan-and-splice with null=default confirmed. Template textarea and § counter present in GUI.","v":"intruder_engine.cpp:15-32 findMarkers scans U+00A7 pairs; :134-148 applyPayloads splices, `out += p.isNull() ? m.def : p;`. tabs.jsx:620 `(intruder.template.match(/§/g)?.length||0)/2` shows insertion-point count.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Auto-mark payload positions (Add/Clear/Auto §)","s":"present","i":"medium","e":"days","g":"None -- + § wraps the current template-textarea selection in markers, CLEAR § strips every marker, and AUTO § auto-marks every query-string, form-body and Cookie value via a new pure autoMarkTemplate() helper (idempotent: already-marked values are left alone).","w":"Closed 2026-08-09: added +§/CLEAR §/AUTO § buttons to the TEMPLATE pane header. AUTO § parses the raw request (request-line query string, Cookie header, x-www-form-urlencoded body) and wraps each value; verified with a Node functional test (request-line, Cookie, form-body, idempotency, CRLF and LF templates).","v":"ui-v2/tabs.jsx autoMarkTemplate() (pure, exported for testing) + IntruderTab TEMPLATE pane-head buttons.","o":"partial","r":"Intruder wave: +§/CLEAR §/AUTO § close the auto-mark gap (partial -> present)."},{"a":"intruder","f":"Payload type: Simple list","s":"present","i":"low","e":"hours","g":"","w":"Re-read parseSet and the payloads textarea/presets. Fully GUI-reachable.","v":"intruder.cpp:20-27 parseSet splits the newline block, trims, drops empties. tabs.jsx:699-704 payloads textarea; PAYLOAD_PRESETS tabs.jsx:339-447 curated lists.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Payload type: Numbers (range/step/hex/padded)","s":"present","i":"medium","e":"days","g":"None -- a GENERATOR dialog in the Intruder PAYLOADS pane (numbers/dates/brute tabs, discovered from /api/intruder/generator-types) offers from/to/step/width/hex fields with a live count+sample preview, applying via /api/intruder/set{generator}.","w":"GUI closed: engine+API were already complete (re-read 2026-08-02), the only gap was that ui-v2 never called them. Generator dialog now covers all three types.","v":"intruder_generators.cpp:23-39 numbers(from,to,step,width,hex), stops before qint64 wrap. control_server.cpp:3143-3147 expandGen wires it; /api/intruder/generate previews. GUI: ui-v2/tabs.jsx IntruderTab GENERATOR dialog (buildGenSpec numbers branch); ui-v2/real-data.js intruderGenerate/intruderGeneratorTypes actions.","o":"present","r":"Intruder generator-dialog wave: numbers/dates/brute-forcer payload generation is now reachable from the GUI (was API-only)."},{"a":"intruder","f":"Payload type: Dates","s":"present","i":"low","e":"days","g":"None -- same GENERATOR dialog (dates tab: from/to ISO, stepDays, format), live preview via /api/intruder/generate.","w":"GUI closed alongside Numbers/Brute in the same dialog; no backend change needed.","v":"intruder_generators.cpp:76-87 dates(fromIso,toIso,stepDays,format) via QDate::addDays. control_server.cpp:3151-3154. GUI: ui-v2/tabs.jsx IntruderTab GENERATOR dialog (buildGenSpec dates branch).","o":"present","r":"Intruder generator-dialog wave: numbers/dates/brute-forcer payload generation is now reachable from the GUI (was API-only)."},{"a":"intruder","f":"Payload type: Brute forcer","s":"present","i":"low","e":"days","g":"None -- same GENERATOR dialog (brute tab: charset/minLen/maxLen), live preview shows count + capped flag before apply.","w":"GUI closed alongside Numbers/Dates in the same dialog; no backend change needed.","v":"intruder_generators.cpp:41-74 brute(charset,minLen,maxLen) over `charset.toUcs4()`, `kMaxChars = kMaxCount*64` (~6.4M) cap. control_server.cpp:3148-3150. GUI: ui-v2/tabs.jsx IntruderTab GENERATOR dialog (buildGenSpec brute branch).","o":"present","r":"Intruder generator-dialog wave: numbers/dates/brute-forcer payload generation is now reachable from the GUI (was API-only)."},{"a":"intruder","f":"Processing rule: Add prefix","s":"present","i":"low","e":"hours","g":"None -- the RULES bar (tabs.jsx IntruderTab) is an ordered rule-chain editor (op select populated from GET /api/intruder/rule-ops, +/-/reorder) covering prefix as one op.","w":"Closed 2026-08-09: added a RULES bar with add/remove/reorder rows, an op <select> per row (arg inputs for prefix/suffix/match-replace), dispatching intruder-set{rules} -> POST /api/intruder/set. rules is UI-only client state (not echoed by the snapshot), matching the existing grepMatch/grepExtract pattern.","v":"ui-v2/tabs.jsx RULES bar in IntruderTab; control_server.cpp:3247-3260 rules parsing (op+arg); intruder_rules.cpp:13 prefix op.","o":"present","r":"Intruder wave: RULES bar closes the processing-rule-chain GUI gap for prefix/suffix/encode/hash/case/reverse/match-replace at once."},{"a":"intruder","f":"Processing rule: Add suffix","s":"present","i":"low","e":"hours","g":"None -- same RULES bar as item 10 (suffix is one op in the dropdown).","w":"Closed 2026-08-09: same RULES bar as item 10; suffix is a listed op with a text arg input.","v":"ui-v2/tabs.jsx RULES bar; intruder_rules.cpp:14 suffix op.","o":"present","r":"Intruder wave: RULES bar closes the processing-rule-chain GUI gap for prefix/suffix/encode/hash/case/reverse/match-replace at once."},{"a":"intruder","f":"Processing rule: Match/replace","s":"present","i":"low","e":"hours","g":"None -- regex-replace matches a regex and replaces every occurrence with Burp-style back-references ($0/$1..$9/$$); the literal match-replace op remains for exact-string replaces.","w":"Re-read intruder_rules.cpp:28-39. The op does a LITERAL QString::replace only. Burp's match/replace processing rule is regex-based; the defining capability (regex) is absent, so this is a lookalike, not the Burp rule. Downgraded present->partial.","v":"intruder_rules.cpp:36-37 `QString s=value; s.replace(find, repl); return s;` — QString::replace(QString,QString) is a literal substring replace; there is no QRegularExpression path.","o":"present","r":"Added a `regex-replace` processing-rule op (arg 'pattern\\x1freplacement'): matches a QRegularExpression and replaces every occurrence, with Burp-style back-references $0/$1..$9/$$ expanded manually. The literal match-replace op stays for exact-string replaces. Pure + mutation-proven; fail-safe on invalid regex."},{"a":"intruder","f":"Processing rule: Modify case","s":"present","i":"low","e":"hours","g":"None -- uppercase/lowercase PLUS propername (Titlecase) and propername-keep (upper-first, keep rest) processing-rule ops cover Burp's Modify-case modes.","w":"Closed 2026-08-12: added the propername ops to applyRule (see reconciled).","v":"intruder_rules.cpp:15-16 `if(op==\"uppercase\") return value.toUpper(); if(op==\"lowercase\") return value.toLower();`.","o":"present","r":"Added propername + propername-keep processing-rule ops (upper-first / lower-or-keep-rest, code-point-safe, reusing the casemod generator's proper-case semantics) alongside the existing uppercase/lowercase; pure + mutation-proven. Reachable via the rule chain like every other processing op."},{"a":"intruder","f":"Processing rule: Encode (URL/HTML/Base64/hex)","s":"present","i":"low","e":"hours","g":"None -- same RULES bar; the encode ops (base64/base64url/url/hex/html/unicode-escape/rot13) are listed in the op <select>, sourced live from GET /api/intruder/rule-ops.","w":"Closed 2026-08-09: same RULES bar as item 10; encode ops need no arg input, just the op selection.","v":"ui-v2/tabs.jsx RULES bar + RULE_OPS_FALLBACK; intruder_rules.cpp:42-46 delegates encode ops to Transcode::apply.","o":"present","r":"Intruder wave: RULES bar closes the processing-rule-chain GUI gap for prefix/suffix/encode/hash/case/reverse/match-replace at once."},{"a":"intruder","f":"Processing rule: Hash","s":"present","i":"low","e":"hours","g":"None -- same RULES bar; md5/sha1/sha256/sha512 are listed hash ops in the <select>.","w":"Closed 2026-08-09: same RULES bar as item 10.","v":"ui-v2/tabs.jsx RULES bar; intruder_rules.cpp:67-68 hash ops via Transcode::apply.","o":"present","r":"Intruder wave: RULES bar closes the processing-rule-chain GUI gap for prefix/suffix/encode/hash/case/reverse/match-replace at once."},{"a":"intruder","f":"Grep - Match","s":"present","i":"low","e":"hours","g":"Single boolean 'any hit' column; Burp adds one flag column per configured expression.","w":"Re-read grep + computeGrep + GUI input. Works and is GUI-reachable, but collapses to one boolean column.","v":"intruder_grep.cpp:19-36 grepMatch tries each needle as regex else literal contains(). intruder.cpp:89 computeGrep() runs it over grepScanText(resp) (headers+decoded body). tabs.jsx:2264-2271 GREP·MATCH input; tabs.jsx:2691-2693 single ✓/· column (r.matched ternary), still one boolean flag, not one column per expression.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Grep - Extract","s":"partial","i":"low","e":"days","g":"Backend supports both regex and start/end-delimiter extract, but an attempt stores only ONE extracted value and the UI exposes a single regex Extract column -- Burp allows multiple grep-extract items per attack.","w":"Corrected from 'present' on independent re-derivation (2026-08-02): intruder.cpp:143 returns a single m_extracted QString (one ExtractedRole), so multi-extract parity with Burp is not met.","v":"intruder.cpp:162 `case ExtractedRole:return a->m_extracted;` (single QString); intruder_grep.cpp implements regex+delimiter extract modes (grepExtract); tabs.jsx:2558-2562 sends only {regex} to grepExtract, one Extract column (tabs.jsx:2273).","o":"partial","r":"Wave 0 register-accuracy audit: audited_state was stuck at \"present\" (the pre-correction grade the \"why\" field already says was corrected to partial on 2026-08-02) which rendered backwards on the roadmap page (\"closed since audit: present -> partial\" reads as a regression, not a correction) -- reset it to match the current, re-verified state. No code change; single-value extraction (m_extracted, one Extract column) still holds."},{"a":"intruder","f":"Resource pool: concurrent requests","s":"present","i":"low","e":"hours","g":"","w":"Re-read runWorker + pool_logic; semaphore-bounded concurrency and 1..64 clamp confirmed. GUI CONC field present.","v":"intruder.cpp:550 `m_pool.setMaxThreadCount(concurrency);`; :556 `QSemaphore inFlight(concurrency);`. intruder_pool_logic.cpp:5-8 clampConcurrency 1..kMaxConcurrency. tabs.jsx:2285-2292 CONC input (min=1 max=64, dispatches intruder-set{concurrency}).","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Resource pool: throttle / delay","s":"present","i":"low","e":"hours","g":"Fixed delay only; no randomized/variable delay (Burp offers a delay with random variance).","w":"Re-read dispatch loop + clamp + rps alias + GUI. Fixed inter-dispatch delay confirmed.","v":"intruder.cpp:730 `if (throttleMs > 0) interruptibleSleep(throttleMs, m_stopRequested);` in the main dispatch loop (a second site at :708 covers the recursive-grep pipe branch). intruder_pool_logic.cpp:11-14 clampThrottleMs 0..kMaxThrottleMs; :28-30 rpsToDelayMs. tabs.jsx:2294-2301 THROTTLE·MS input.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Results table: filtering","s":"present","i":"medium","e":"days","g":"None -- the RESULTS pane gained 2xx/3xx/4xx/5xx toggle chips, min/max response-length filters, and a regex (with leading '-' negation) search box over payload+extracted text, composed with the existing hide-404 checkbox via a new pure intruderRowVisible() predicate.","w":"Closed 2026-08-09: replaced the single hardcoded hide-404 checkbox with a full filter bar; all fields were already client-side (intruder.results), so this is a pure ui-v2 predicate change verified with a Node functional test covering every filter dimension plus fail-open on an invalid regex.","v":"ui-v2/tabs.jsx intruderRowVisible() (pure, exported for testing) + IntruderTab RESULTS filter bar.","o":"partial","r":"Intruder wave: results filter bar closes the filtering gap (partial -> present)."},{"a":"intruder","f":"Save/Resume attack","s":"present","i":"medium","e":"days","g":"None — loadRun restores every row's raw combo + completion flag, and resume() re-fires ONLY the never-completed rows over the same worker (completed rows keep their results). Exposed as Q_INVOKABLE resume(), POST /api/intruder/resume, and a ▷ RESUME button next to SAVE/LOAD.","w":"Closed 2026-08-29: added Intruder::resume() + a skipRows filter on runWorker's dispatch loop; the pure resume decision (IntruderPersist::planResume — recursive-grep unresumable, all-complete = nothing to resume, else skip the completed indices) is unit-tested + mutation-proven, and the firing reuses the proven start()/runWorker path over the round-trip-restored combos.","v":"Src/Core/Networking/intruder.cpp: saveRun/loadRun/resume; ui-v2/tabs.jsx: SAVE/LOAD/RESUME; bin/nullock: intruder save/load/reset; Tests/intruder_persist_logic/intruder_persist_logic_test.cpp; scripts/intruder_workspace_regression.py: project restoration remains idle and preserves completed/pending rows.","o":"present","r":"Existing manual SAVE/LOAD/RESUME is retained. Project switch and clean exit now save automatically; restoration remains idle and pending rows still need explicit Resume. CLI adds save/load/reset."},{"a":"intruder","f":"Resend / re-issue a single result row","s":"present","i":"low","e":"hours","g":"","w":"Re-read resend(); re-fires the stored combo through the current template on a separate worker. GUI ↻ button present.","v":"intruder.cpp:749-787 Intruder::resend(row) re-applies m_payloadRules to a->m_combo and runs it through m_resendWorker on a QtConcurrent worker. tabs.jsx:2699-2705 per-row ↻ button calling NL.actions.intruderResend(i).","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Send to Intruder from other tools","s":"present","i":"low","e":"hours","g":"None -- a + § button in the TEMPLATE pane wraps the current textarea selection in §markers§, matching Burp's Add-§ control; manual placement by editing the textarea was already possible.","w":"Closed 2026-08-09: added the +§ button (reads templateRef.current.selectionStart/End) alongside the pre-existing send-to-intruder auto-mark and editable template textarea.","v":"ui-v2/tabs.jsx IntruderTab TEMPLATE pane-head +§ button; app.jsx:77 send-to-intruder auto-mark (pre-existing).","o":"present","r":"Intruder wave: +§ selection-wrap button closes the interactive marking gap."},{"a":"intruder","f":"Full-speed Intruder (no artificial throttle)","s":"exceeds","i":"low","e":"hours","g":"","w":"Re-read fire loop; no time-throttle unless the user sets one, concurrency defaults to 10 and dispatches immediately. Genuinely beats Burp Community's deliberate rate limit.","v":"intruder.cpp:724-730 dispatch loop fires each combo via QtConcurrent::run immediately; throttle only applied `if (throttleMs > 0) interruptibleSleep(...)`. intruder_pool_logic.hpp:18 kDefaultConcurrency=10. No artificial per-request delay unless the user sets one.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Interruptible attack + safe shutdown mid-run","s":"present","i":"low","e":"hours","g":"","w":"Re-read stop(), the sliced sleeps, and the destructor join. All confirmed.","v":"intruder.cpp:419-422 stop() sets m_stopRequested; :724-727 dispatcher checks before and after acquire; :110-118 interruptibleSleep slices the wait; :125-139 ~Intruder sets stop then waitForFinished on worker+resend+pool before qDeleteAll.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Payload type: Runtime file","s":"absent","i":"medium","e":"days","g":"No way to stream payloads line-by-line from a large file; everything must be loaded into the textarea/memory.","w":"Re-grepped intruder sources for QFile/readFile/fromFile/runtime — nothing. types() lists only numbers/brute/dates. Confirmed absent.","v":"intruder_generators.cpp:337-344 types() now returns 13 generator types (numbers/brute/dates/null/frobber/blocks/casemod/charsub/bitflip/username/illegal-unicode/ecb-shuffle/iterator), up from the 3 last cited here -- still none reading from a file. No QFile/file-streaming reference anywhere in intruder*.cpp/hpp.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Payload type: Custom iterator","s":"present","i":"low","e":"days","g":"Implemented as a positional cartesian-product generator: IntruderGenerators::customIterator(positions, separator) emits every combination pos[0][i]+sep+pos[1][j]+... in odometer order (last position varies fastest), reachable via type \"iterator\" on /api/intruder/generate and /api/intruder/set. Matches Burp's core custom-iterator behaviour; the only nicety not carried is a DISTINCT separator per position (one shared between-positions separator instead) -- noted as a possible enhancement, not a gap that blocks the use case.","w":"Implemented + mutation-proven, following the exact pattern the other 12 payload generators use (all marked present): a pure Qt6::Core-linkable IG function + expandGen dispatch + types() entry. Bounded at kMaxCount by capping the working set after EACH position, so a huge product truncates in COUNT while every emitted payload stays a COMPLETE combination (never a length-truncated fragment) and never OOMs.","v":"intruder_generators.cpp:314 customIterator(); types() (:344) lists \"iterator\"; control_server.cpp:3648 expandGen `if (t == \"iterator\")` parses positions (arrays or newline-joined) + separator. Tests/intruder_generators/intruder_generators_test.cpp (107 pass): odometer order + separator, no-separator concat, single-position no-sep, 3-position join, empty/empty-factor -> empty, and 47^3 capped at kMaxCount with every payload complete; M1 (drop separator) + M2 (drop cap) each fail only their targeted case. Live: POST type=iterator positions=[[a,b],[1,2,3]] sep=- -> a-1..b-3 (count 6).","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Payload type: Character substitution","s":"present","i":"low","e":"hours","g":"Cannot emit progressive substrings of a value as payloads.","w":"Grep over intruder sources for substring returns nothing; no generator emits progressive substrings.","v":"intruder_generators.cpp only defines numbers/brute/dates; intruder_rules.cpp operations() (55-70) has no substring.","o":"present","r":"Closed 2026-08-12. NAME CORRECTED: the audit labelled this 'Character substring' with a 'progressive substrings' gap, but Burp Intruder has no 'substring' payload type -- its documented type is 'Character substitution' (leetspeak). Implemented that (the real Burp feature): IntruderGenerators::charSub(items, subs) emits, per item, all 2^k permutations of applying-or-not each substitutable character position (e.g. peter + {e:3,t:7} -> peter/p3ter/pe7er/p37er/pet3r/p3t3r/pe73r/p373r), enumerated leftmost-position-as-LSB to match Burp's order. Verified against the PortSwigger docs. Wired into control_server expandGen (t==charsub, items from array/newline, subs from a {char:char} object) + types(). Unit- + mutation-tested (linearising the 2^k enumeration fails the multi-position cases)."},{"a":"intruder","f":"Payload type: Case modification","s":"present","i":"low","e":"hours","g":"No payload type that expands one word into its case permutations.","w":"Confirmed: case exists only as a processing rule (uppercase/lowercase), not as a payload generator that expands one word into case variants.","v":"intruder_generators.cpp:89-91 types() has no 'case'; intruder_rules.cpp:15-16 has the global uppercase/lowercase rules only.","o":"present","r":"Closed 2026-08-11: added IntruderGenerators::caseMod(items, modes) -- for each item, one payload per enabled case option in canonical order, item-major, no dedup. The FIVE Burp options confirmed from the PortSwigger docs (a vetting-agent 4-mode proposal was wrong): No change / lower / upper / Propername (first cp upper, rest LOWER) / ProperName (first cp upper, rest UNCHANGED). Distinct from the 1:1 intruder_rules uppercase/lowercase transforms -- this is a list-multiplying payload TYPE. First char upper-cased by code point (non-BMP safe). Wired into control_server expandGen (t==casemod, items from array/newline-split, modes from a token array defaulting to all five). Unit- + mutation-tested (collapsing Propername's lower-rest fails the lower-rest cases; the Propername vs ProperName distinction is the docs' 'critical difference')."},{"a":"intruder","f":"Payload type: Recursive grep","s":"partial","i":"high","e":"weeks","g":"No chaining an extracted value into the next request; blocks CSRF-token/nonce walking and stateful sequences.","w":"Re-read the fire loop. computeGrep results are stored on the row and never fed forward into the next request's payload. Confirmed absent.","v":"intruder.cpp:445-507 fireOne computes grep (484-487) and posts it to the row; combos are pre-generated at :376-378 before firing — no path takes a response-N extract into request N+1.","o":"absent","r":"ENGINE done (the hard part the audit called 'weeks'): the extract IS now fed forward. Recursive grep runs as a SERIAL branch in Intruder::runWorker -- each request's payload is the value the grep-EXTRACT spec pulls from the PREVIOUS response, walked from a `seed` for `count` requests, stopping early when a response yields no extract (chain ended). fireOne was refactored to RETURN its extracted value (it already computed it for the result column) and to record the runtime-discovered payload into the row; start() reserves `count` placeholder rows and forces concurrency 1 (the run is inherently serial -- each request depends on the prior response); it reuses the existing IntruderGrep::grepExtract spec as the payload source, so no new extraction code. Config via /api/intruder/set { recursiveGrep, recursiveGrepSeed, recursiveGrepCount }; snapshot exposes intruder.recursiveGrep. VERIFIED e2e against a chaining mock: a 5-request walk carried exactly [seed, TOK0, TOK1, TOK2, TOK3] (each request carried the PRIOR response's extracted token -- the chain proven), result rows recorded the extracted token + the payload used, `count` bounded the run, and a dried-up token stopped the chain early (fired 3 of 10). Gauntlet ctest 98/98 + probe_smoke 156/156. This is the classic anti-CSRF-bruteforce / one-time-nonce / state-machine walk. REMAINDER (-> stays partial): the ui-v2 payload-type selector + seed/count fields (concurrent-agent lane), save/resume (RunConfig) of a recursive attack, and multi-position recursive (only position 0 carries the recursive value today, Sniper-style)."},{"a":"intruder","f":"Payload type: Illegal Unicode","s":"present","i":"low","e":"hours","g":"None -- an overlong-UTF-8 payload generator emits the illegal 2..6-byte encodings of a target character (WAF / path-normalization bypass).","w":"Closed 2026-08-12: added IntruderGenerators::illegalUnicode (overlong UTF-8 of the target code point at each 2..6-byte length, hex/%-prefixed, semantics confirmed vs PortSwigger), advertised in types() + dispatched by control_server expandGen ('illegal-unicode'); pure + mutation-proven.","v":"intruder_generators.cpp illegalUnicode + types(); control_server.cpp expandGen illegal-unicode branch; Tests/intruder_generators (+7 cases incl. the exact '/' overlong ladder, mutation-proven lead prefix + continuation marker).","o":"present","r":"Intruder wave: Illegal Unicode payload type -- overlong UTF-8 encodings (2..6 bytes) of a target char, %C0%AF-style (PortSwigger-verified); pure + mutation-proven, no engine wiring."},{"a":"intruder","f":"Payload type: Character blocks","s":"present","i":"low","e":"hours","g":"No generator producing blocks of a repeated character at increasing sizes (buffer/limit testing).","w":"Grep for char-block returns nothing; no repeated-character block generator.","v":"intruder_generators.cpp:89-91 types() lists only numbers/brute/dates.","o":"present","r":"Closed 2026-08-11: added IntruderGenerators::charBlocks(base,minMult,maxMult,step) -- one payload per multiplier k in [minMult,maxMult] step, each `base` repeated k times (base x k). Semantics verified against the PortSwigger docs: Burp MULTIPLIES/whole-repeats the base, it does NOT truncate to a length (my first guess was truncate -- the docs corrected it). Wired into control_server expandGen (t==blocks) + types()={numbers,brute,dates,null,frobber,blocks}. Bounded in count + total chars, refuses to build an over-cap block (no OOM). Unit- + mutation-tested (replacing repeated(k) with left(k) fails the exact-output cases)."},{"a":"intruder","f":"Payload type: Null payloads","s":"present","i":"medium","e":"hours","g":"Cannot fire the same base request N times (session/CSRF/timing tests) without a real payload list.","w":"Confirmed: the only 'null' concept is the null-combo default for unfilled markers, not a null-payloads type that fires the base request N times.","v":"intruder_engine.cpp:64 `const QString def = QString(); // null => use the marker's own default`; no null-payloads generator in types().","o":"present","r":"Closed 2026-08-11: added IntruderGenerators::nullPayloads(count) -- emits `count` empty payloads so a position is filled with nothing and the base request is re-sent unchanged N times (Burp's Null payloads: rate-limit / race / non-determinism probing). Wired into control_server expandGen (/api/intruder/generate + /set) and advertised by types()={numbers,brute,dates,null}. count<1 -> empty; capped at kMaxCount. Unit- + mutation-tested (emitting a non-empty payload fails the emptiness assertions; the size/count checks pass)."},{"a":"intruder","f":"Payload type: Character frobber","s":"present","i":"low","e":"hours","g":"No type that increments each character of the base value in turn.","w":"Grep 'frobber' over the whole repo returns nothing. Confirmed absent.","v":"No match for 'frobber' in Src/Core/Networking; intruder_generators.cpp types() has none.","o":"present","r":"Closed 2026-08-11: added IntruderGenerators::frob(base) -- one payload per code-point position, each the whole base with that position's code point +1 (Burp Character frobber). Code-point safe (toUcs4; surrogate-range bump -> 0xE000, past 0x10FFFF -> 0) and bounded in count + total chars (O(L^2)). Wired into control_server expandGen (t==frobber -> g[base]) + types()={numbers,brute,dates,null,frobber}. Semantics verified against PortSwigger docs by the vetting workflow's adversarial pass; unit- + mutation-tested (a +2 increment fails the exact-output cases)."},{"a":"intruder","f":"Payload type: Bit flipper","s":"present","i":"medium","e":"days","g":"No bit-flipping type for CBC/padding-oracle and encrypted-token fuzzing.","w":"Grep 'bit.?flip' over the repo returns nothing. Confirmed absent.","v":"No bit-flip generator in intruder_generators.cpp; types() lists numbers/brute/dates only.","o":"present","r":"Closed 2026-08-12: added IntruderGenerators::bitFlip(base) -- per byte of the base (its UTF-8 bytes), one payload per bit position 0..7 with that single bit XOR-flipped, byte order left-to-right, bit order LSB(0x01)->MSB(0x80). Matches Burp's documented output exactly (ab -> `b,cb,eb,ib,qb,Ab,!b,ab-with-0xE1, ac,a`,af,aj,ar,aB,a-quote,a-with-0xE2), verified against the PortSwigger docs; flipped bytes render via Latin-1 as Burp displays them. Wired into control_server expandGen (t==bitflip) + types(). Unit- + mutation-tested (OR-instead-of-XOR fails the exact-output list). Caveat noted in the header: an MSB flip yields a >=0x80 byte that a string payload re-encodes to two UTF-8 bytes on the wire; the 7 lower-bit flips are byte-exact."},{"a":"intruder","f":"Payload type: Username generator","s":"present","i":"low","e":"hours","g":"None -- a name/email -> username permutation generator produces the common schemes (concatenations, dot/underscore/hyphen separated, reversed order, first/last-initial combos).","w":"Closed 2026-08-12: added IntruderGenerators::usernameGen (semantics confirmed vs PortSwigger), advertised in types() and dispatched by control_server expandGen ('username', arg 'name'); pure, deduped, capped, mutation-proven.","v":"intruder_generators.cpp usernameGen + types(); control_server.cpp expandGen username branch; Tests/intruder_generators (+17 cases, mutation-proven initial + email handling).","o":"present","r":"Intruder wave: Username generator payload type -- name/email -> username candidates via common schemes (PortSwigger-verified), lower-cased/deduped/capped; pure + mutation-proven, no engine wiring."},{"a":"intruder","f":"Payload type: ECB block shuffler","s":"present","i":"low","e":"days","g":"None -- a hex ciphertext is split into blockSize-byte blocks and the block-permutation variants are emitted (deduped, capped). The classic ECB token-forgery shuffle.","w":"Closed 2026-08-12: added ecbBlockShuffle (see reconciled).","v":"intruder_generators.cpp ecbBlockShuffle + types(); control_server.cpp expandGen ecb-shuffle branch; Tests/intruder_generators (+9 cases, mutation-proven align guard + dedup).","o":"present","r":"Added IntruderGenerators::ecbBlockShuffle -- hex ciphertext -> blockSize-byte blocks -> the complete deduped block-permutation set (capped), dispatched via expandGen ('ecb-shuffle'); pure + mutation-proven, fail-safe on non-hex/misaligned input. (Burp's optional 'additional encrypted strings' block-pooling is a future refinement.)"},{"a":"intruder","f":"Payload type: Extension-generated (payload provider)","s":"absent","i":"medium","e":"weeks","g":"Extensions cannot supply Intruder payloads or attack types (no payload-provider API wired to Intruder).","w":"Re-read the entire intruder.cpp; start()/runWorker/fireOne never call any extension hook. No IIntruderPayloadGenerator equivalent exists.","v":"intruder.cpp:437 start() and :613 runWorker build combos purely from m_payloadSets + generators; `grep -n extension Src/Core/Networking/intruder.cpp` returns no hits -- no extension hook anywhere on the payload path.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Processing rule: Substring / Reverse substring","s":"present","i":"low","e":"hours","g":"None -- substring (0-indexed start offset + optional length) and reverse-substring (end offset + length counted from the end) are both processing ops, code-point-safe and fail-safe.","w":"Closed 2026-08-12: added substring + reverse-substring ops to applyRule (arg = 'offset' or 'offset,length', semantics verified vs PortSwigger), advertised in operations(); pure + mutation-proven. No engine wiring needed -- rules round-trip as {op,arg} via the control API.","v":"intruder_rules.cpp applyRule substring/reverse-substring branch + operations(); Tests/intruder_rules (+12 cases, mutation-proven start-offset + reverse end-offset).","o":"present","r":"Intruder wave: substring + reverse-substring payload-processing ops (PortSwigger-verified semantics), code-point-safe, fail-safe on out-of-range; pure + mutation-proven, no engine wiring."},{"a":"intruder","f":"Processing rule: Decode","s":"present","i":"low","e":"hours","g":"MISCLASSIFICATION. The decode capability already EXECUTES: applyRule delegates any non-local op to Transcode::apply (intruder_rules.cpp:45-46), and Transcode::apply supports base64-decode/base64url-decode/url-decode/html-decode/hex-decode/jwt-decode (transcode.cpp:243-248). So passing op=\"base64-decode\" as a rule already decodes today. Only the discovery list operations() deliberately omits them (","w":"Reclassified absent -> partial (2026-08-02): independent triage + adversarial-verify agreed; cited files re-confirmed to exist. See PARITY-BACKLOG.md.","v":"intruder_rules.cpp:45-46 fallthrough to Transcode::apply(op,value); transcode.cpp:229-235 ops() and :243-248 apply() implement base64/url/html/hex/jwt decode; intruder_rules.cpp:56-58 comment excludes them from the advertised list only.","o":"present","r":"Closed 2026-08-11: operations() now advertises the decode inverse of each advertised reversible encode -- base64-decode/base64url-decode/url-decode/hex-decode/html-decode -- matching Burp's Decode payload rule. The ops already executed (applyRule -> Transcode::apply) and fail safe (a decode of non-decodable input is a no-op), so this only closes the discoverability gap; /api/intruder/rule-ops (control_server.cpp:3305) serves operations() verbatim so the UI dropdown picks them up. The prior blanket exclusion ('payloads are authored, not received') was re-derived as incomplete -- payload lists routinely arrive pre-encoded. Round-trips unit- + mutation-tested. Non-payload decodes (jwt-decode multi-line JSON; octal/binary-decode, no advertised encoder) stay unadvertised but still run if named."},{"a":"intruder","f":"Processing rule: Add raw payload","s":"present","i":"low","e":"hours","g":"None -- add-raw-payload is a new local op in the processing-rule chain: it appends the ORIGINAL, pre-chain payload value regardless of what earlier rules already did to the running value, so e.g. [sha256] -> [add-raw-payload] yields \"<hash><rawvalue>\" for sign-then-send patterns.","w":"Closed: applyRule/applyRules only ever saw the current running value, with no way to reach back to the pre-chain original once an earlier rule had transformed it. Gave applyRule a third `original` parameter (the 2-arg overload defaults it to `value` itself, preserving every existing call site and test) and had applyRules thread the constant pre-chain value through as `original` on every step, so add-raw-payload works correctly no matter where it sits in the chain or how many times it repeats.","v":"Src/Core/Networking/intruder_rules.hpp:56-57 (applyRule 3-arg + 2-arg overloads), intruder_rules.cpp:28-35 (add-raw-payload op + original threading), :169-172 (applyRules passes the constant original), operations() now advertises add-raw-payload; ui-v2/tabs.jsx RULE_OPS_FALLBACK includes it (the live list already comes from GET /api/intruder/rule-ops -> IntruderRules::operations(), control_server.cpp:3635-3639); Tests/intruder_rules/intruder_rules_test.cpp adds 5 checks (standalone self-append, appends original past an earlier transform, sha256-then-raw sign-then-send pattern, repeated add-raw-payload chain, operations() advertisement).","o":"absent","r":"absent -> present. Burp Payload Processing rule \"Add raw payload\": re-inserts the unmodified original payload at that point in the chain, most commonly used after a hash/encode step to build a sign-then-send value (hash+raw). The engine (intruder_rules.cpp) previously threaded only the running value through each rule with no notion of the untouched pre-chain original, so there was no way to get back to it once an earlier rule (e.g. sha256) had overwritten the running value. Added a third `original` parameter to applyRule (2-arg overload defaults it to value, so every existing call site and the 40+ existing unit tests are untouched) and have applyRules thread the constant pre-chain payload through as `original` on every step of the loop, so add-raw-payload appends the true original no matter where it sits in the chain or how many times it repeats. New op registered in operations() (auto-flows to the GUI dropdown via the existing /api/intruder/rule-ops -> ruleOps live-fetch, ui-v2/tabs.jsx:1642-1648) plus added to the static RULE_OPS_FALLBACK for when that fetch fails. 5 new unit tests in Tests/intruder_rules/intruder_rules_test.cpp lock the standalone self-append semantics, correct original-vs-running-value behavior after an earlier transform, the sha256-then-raw sign-then-send pattern named in the prior gap text, a repeated-in-chain case, and operations() advertisement. Backend C++ change this cloud session cannot build locally -- pushed and will be confirmed against a green GitHub Actions ctest run (ctest -R intruder_rules) before being called fully verified; documented here as the honest state at push time per this file's convention for cloud session C++ waves."},{"a":"intruder","f":"Processing rule: Skip if matches regex","s":"present","i":"low","e":"hours","g":"None -- a `skip-if-matches` processing rule (arg = regex) drops any payload whose transformed-so-far value matches, before the request is fired. The skip-aware applyRules(value, rules, bool* skipped) overload signals the drop; Intruder::start() filters skipped combos out before result rows are built, so the sent-request count and the table reflect only surviving payloads (Burp's behaviour). An empty/invalid pattern never skips.","w":"Closed 2026-08-24: added the skip signal to the rule chain (skip-aware applyRules overload; the 2-arg path is a safe no-op so a payload never vanishes where a caller cannot honour a skip) and the combo filter in Intruder::start(). Advertised in operations() for UI discovery. Mutation-proven.","v":"intruder_rules.cpp:174-195 applyRules(value,rules,bool*): a `skip-if-matches` rule (op registered :219) matching the running value sets *skipped and returns; intruder.cpp:460-475 Intruder::start() drops combos whose processed payload skips, before beginResetModel (:479)/row build. Tests: intruder_rules_test.cpp:208-237 -- a payload matching the regex is skipped, a non-match is kept, the plain 2-arg path never drops, the match is against the TRANSFORMED value, and empty/invalid patterns never skip.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Processing rule: Invoke extension","s":"absent","i":"low","e":"weeks","g":"No extension-backed payload processing.","w":"Confirmed: applyRule op set is fixed; no branch calls into an extension.","v":"intruder_rules.cpp:32-172 applyRule's op dispatch is a fixed if-chain (add-raw-payload/prefix/suffix/uppercase/lowercase/propername/reverse/match-replace/regex-replace/url-encode-chars/substring/reverse-substring) falling back to Transcode::apply for everything else; no extension call anywhere on the rule path.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Payload encoding (global 'URL-encode these characters')","s":"present","i":"medium","e":"hours","g":"None -- the global 'URL-encode these characters' safety net is implemented: a configured character set is percent-encoded in every payload.","w":"Closed 2026-08-12: added a code-point-safe `url-encode-chars` payload-processing op (percent-encodes ONLY the listed chars, byte-by-byte over UTF-8) and wired Intruder::setGlobalEncodeChars to append it as the FINAL step of every payload's chain (full run + single-row resend), configured via `encodeChars` on /api/intruder/set. Off by default so existing attacks are unchanged.","v":"intruder_rules.cpp url-encode-chars op + operations(); intruder.cpp setGlobalEncodeChars + effective-chain append at the run and resend sites; control_server.cpp /api/intruder/set encodeChars; Tests/intruder_rules (+11 cases, mutation-proven).","o":"present","r":"Intruder wave: global URL-encode-these-characters safety net via a code-point-safe url-encode-chars op appended to every payload's processing chain; opt-in (empty=off), mutation-proven."},{"a":"intruder","f":"Grep - Payloads (flag reflected payloads)","s":"present","i":"medium","e":"hours","g":"None -- an automatic reflection column flags a row when one of its submitted payloads echoes literally in the response.","w":"Closed 2026-08-12: added IntruderGrep::payloadReflected (LITERAL substring, bounded, never regex -- a payload is data not a pattern) and wired it into computeGrep as a per-row `reflected` flag driven by the row's combo, exposed via a ReflectedRole/Q_PROPERTY, toggled by `grepPayloads` on /api/intruder/set, and persisted across save/resume. Off by default.","v":"intruder_grep.cpp payloadReflected + Tests/intruder_grep (+11, mutation-proven); intruder.cpp computeGrep reflected-out + ReflectedRole + setGrepPayloadReflection + run/resend compute; intruder_persist_logic AttackRow.reflected + RunConfig.grepPayloadReflection JSON round-trip; control_server.cpp grepPayloads.","o":"present","r":"Intruder wave: automatic reflected-payload column via a literal (non-regex) payloadReflected predicate; per-row flag, persisted, opt-in, mutation-proven."},{"a":"intruder","f":"Follow redirections (never/on-site/in-scope/always)","s":"present","i":"medium","e":"days","g":"","w":"Re-read Intruder::resend() after wiring the redirect-follow block into it and diffed it line-by-line against fireOne(); both now build the same RL::requestUrl/resolveRedirect/followAllowed/mergeSetCookies/buildFollowRequest chain off identical captured state. Confirmed present.","v":"intruder.cpp fireOne() (attack-fire path) and resend() (single-row re-fire path, intruder.cpp:640-745) both now call the shared RedirectLogic chain-follow block on a 3xx result -- resend mirrors fireOne exactly (same requestUrl/resolveRedirect/followAllowed/mergeSetCookies/buildFollowRequest sequence, up to kMaxRedirectHops), using the same m_followPolicy/m_followCookies/m_inScope state the /api/intruder/set FOLLOW select and COOKIES checkbox (fcbe737) already drive.","o":"present","r":"Closes the one remaining gap this item named after fcbe737: Intruder::resend() (the single-row re-fire path off a completed attack) now runs the same redirect-follow block as fireOne() (the attack-fire path) -- built from a captured-by-value copy of m_followPolicy/m_followCookies/m_inScope, identical chain-walk logic (isRedirectStatus / resolveRedirect / followAllowed / mergeSetCookies / methodAfterRedirect / redirectPreservesBody / buildFollowRequest), capped at kMaxRedirectHops. A resent row now grades against the same final page a first-pass fired row does. No new pure logic was added -- this reuses RedirectLogic, already unit-tested + mutation-proven by the Repeater wave -- so no new unit tests were required; the change is a direct structural mirror of the already-verified fireOne() block, confirmed line-by-line against it. Backend-only, no frontend change (the FOLLOW/COOKIES controls already apply to every resend since resend reads the same m_followPolicy/m_followCookies instance fireOne does). This cloud session cannot build/run the C++ side itself; will confirm the next GitHub Actions ci run is green before treating this as fully closed CI-wise (same honest-partial pattern this file has used before for backend-only changes)."},{"a":"intruder","f":"Resource pool: retries on network failure","s":"present","i":"low","e":"hours","g":"None -- a RETRIES field (0..5, backend-clamped) in the Intruder target row lets the operator configure a resend count for a NETWORK-level failure only (connect refused/timeout/reset); an HTTP error status is never retried since it's a real result, not a transport failure. Resent on the same pool thread so it never blocks other in-flight requests, and stops early on Stop so a cancelled attack doesn't burn through every retry against a dead target first.","w":"Closed 2026-08-25: added Intruder::setMaxRetries/maxRetries (clamped via a new IntruderPool::clampRetries, 0..kMaxRetries=5) threaded through runWorker/fireOne -- on !result.ok (network failure, not an HTTP status), fireOne re-sends via the same HttpClient up to `retries` more times, checking m_stopRequested between attempts. Wired through /api/intruder/set{retries} and the snapshot's intruder.retries field, a RETRIES number input next to CONC/THROTTLE·MS in the Intruder target row (ui-v2/tabs.jsx), and saveRun/loadRun (IntruderPersist::RunConfig.retries) so a saved attack round-trips it too.","v":"Src/Core/Networking/intruder_pool_logic.{hpp,cpp} kMaxRetries/clampRetries; Src/Core/Networking/intruder.{hpp,cpp} m_maxRetries/setMaxRetries/maxRetries, runWorker's new `retries` parameter, fireOne's retry loop around client.send, saveRun/loadRun; Src/Core/Networking/intruder_persist_logic.{hpp,cpp} RunConfig.retries; Src/BackEnd/Control/control_server.cpp intruder[\"retries\"] snapshot field + set-handler's bodyJson.contains(\"retries\") branch; ui-v2/tabs.jsx RETRIES field in IntruderTab's pool-config row.","o":"present","r":"Intruder resource-pool batch: RETRIES (0..5, network-failure-only resend, HTTP status codes never retried) closes the last 'hours'-effort intruder pool-config gap."},{"a":"intruder","f":"Results table: sortable columns","s":"present","i":"high","e":"days","g":"None -- every results-table header is click-to-sort (numeric-aware for status/size/ms/matched, string-aware for payload/extracted/err), tracked via a new pure intruderSortValue() accessor; the resend button still targets the original row index after sorting/filtering.","w":"Closed 2026-08-09: added sortKey/sortDir state and onClick handlers to every <th>, sorting a derived {p,i,r} row list (i = original index, preserved through filter+sort) rather than intruder.payloads directly. Verified with a Node functional test including a numeric-vs-lexicographic ordering check.","v":"ui-v2/tabs.jsx intruderSortValue() (pure, exported for testing) + IntruderTab RESULTS <thead> onClick handlers.","o":"absent","r":"Intruder wave: sortable results columns close the sortable-columns gap (absent -> present)."},{"a":"scanner","f":"[A1] Crawl: build site map by link-following (spider)","s":"partial","i":"medium","e":"weeks","g":"Static HTML only (crawler.cpp:154 'Doesn't run JS'); no navigation-graph diffing, no volatile-content handling. The GUI-reachability half of this gap is closed: the DISCOVER tab (ui-v2/app.jsx DiscoverTab) has a start/stop crawl control (seed URL + max-pages/max-depth/throttle-ms) wired to /api/crawler/start,stop, with crawled pages feeding straight into Proxy history. Remaining gap is the JS-rendering/diffing engine work itself, not GUI wiring.","w":"Register-accuracy fix: this item's gap text still said \"Also API-only: no crawl button/tab in the shipped UI\", stale since a prior Wave 2 batch (3494297, 2026-08-13) added the DISCOVER tab's crawl-config UI on top of an already-existing crawl start/stop control -- confirmed live by grep of ui-v2/app.jsx (DiscoverTab startCrawl/stopCrawl calling NL.actions.crawlerStart/crawlerStop) and TABS (discover entry, chrome.jsx render switch). State stays partial: the crawler is still static-HTML-only with no JS execution or diffing (crawler.cpp:154), the real remaining gap; only the previously-stale GUI-reachability clause is corrected.","v":"crawler.cpp:84 `m_worker = QtConcurrent::run([this]() { while (... m_visited < m_maxPages && !m_queue.isEmpty()) { ... crawlOne(u); ...}});`  crawler.cpp:163-166 refs += extractSrcset/extractMetaRefresh/extractFormGets","o":"","r":"Register-accuracy fix: corrected stale \"no crawl button/tab in the shipped UI\" gap text -- the DISCOVER tab has shipped a full crawl start/stop + config UI since 3494297 (2026-08-13). State unchanged (partial); only gap/why corrected to reflect the true remaining gap (no JS rendering/diffing)."},{"a":"scanner","f":"[A2] Crawl: automatic form submission / registration during crawl","s":"stub","i":"medium","e":"weeks","g":"No form is submitted with generated data, no auto-fill, no account registration to reach deeper states. Burp submits forms to expand coverage; Nullock only appends GET-form param names to the crawl frontier.","w":"Downgraded partial->stub. Re-read crawler_logic.cpp:90-116: extractFormGets only turns GET-form field NAMES into empty-valued query strings ('?n1=&n2=') to crawl as URLs. Nothing is ever SUBMITTED: no POST, no value generation, no registration. Line 103 explicitly '(a POST form isn't a URL surface)'. So the capability 'automatic form submission' is not implemented; only GET-form param-name surfaci","v":"crawler_logic.cpp:111 `for (const QString &n : names) q += (q.isEmpty() ? \"?\" : \"&\") + n + \"=\";`  line 103 `if (!methodGet.match(attrs).hasMatch()) continue;   // GET forms only`","o":"","r":"Wave 0 register-accuracy audit: held at stub. Re-verified crawler_logic.cpp:90-114 extractFormGets -- GET forms only (methodGet.match guard at :103), field NAMES turned into empty-valued query params (:111 `q += ... + n + \"=\";`), never a POST, never a filled value, no registration flow. Line numbers unchanged, content unchanged. No code change this pass."},{"a":"scanner","f":"[A3] Crawl configuration: max depth, max locations, crawl limits","s":"partial","i":"low","e":"days","g":"No max-unique-locations, per-directory limits, crawl-budget, or coverage-strategy toggles -- Nullock's crawler only exposes three knobs (max pages, max depth, per-request throttle), matching a small slice of Burp's crawl-configuration surface. Still partial for that reason, but the three existing knobs are now settable from the Discover tab's GUI instead of only the raw /api/crawler/start JSON body.","w":"Re-read crawler.cpp:67-69: qBound(1,maxPages,5000), qBound(0,maxDepth,10), qBound(0,throttleMs,60000) -- exactly three knobs, as claimed. GUI-reachability gap closed 2026-08-13: the Discover tab's crawler control row gained max-pages/max-depth/throttle-ms number inputs (defaulting to the backend's own defaults 200/4/200), wired through NL.actions.crawlerStart's existing seed/maxPages/maxDepth signature plus a new throttleMs 4th argument, straight to the already-complete /api/crawler/start {seed,maxPages?,maxDepth?,throttleMs?} contract (control_server.cpp:4092-4101). No backend touched -- the contract already accepted all three fields, only the GUI to set them was missing.","v":"crawler.cpp:67 `m_maxPages = qBound(1, maxPages, 5000); m_maxDepth = qBound(0, maxDepth, 10); m_throttleMs = qBound(0, throttleMs, 60'000);`","o":"","r":"Discover tab's crawler control row (ui-v2/app.jsx DiscoverTab) gains max pages / max depth / throttle (ms) number inputs, disabled while a crawl is running, passed through a new 4th throttleMs argument on NL.actions.crawlerStart (ui-v2/real-data.js) to the existing /api/crawler/start contract. Still partial: Burp's fuller crawl-configuration surface (max-unique-locations, per-directory limits, crawl-budget, coverage-strategy) has no Nullock equivalent at all, backend or frontend -- that remains a real gap, not just a GUI one."},{"a":"scanner","f":"[A4] Passive audit: missing security headers (CSP/HSTS/XFO/XCTO/RP/Permissions-Policy/COOP/COEP/CORP)","s":"present","i":"low","e":"hours","g":"","w":"Passive checks run on proxied responses. XCTO and Referrer-Policy now use shared effective-value parsing: the first nosniff token controls MIME protection, and the last recognized referrer policy survives unknown fallback keywords. Malformed tokens and nonbreaking spaces cannot count as configured protection.","v":"Src/Core/Networking/passive_scanner.cpp; response_header_values.cpp; networking_logic.cpp; Src/BackEnd/Proxy/proxy_logic.cpp; Tests/scanner_regression/scanner_regression_test.cpp; Tests/header_audit/header_audit_test.cpp; Tests/ui/header_values_browser_test.cjs; scripts/probe_smoke.sh.","o":"present","r":"Hardened active and passive security-header parsing for repeated fields, fallback policies and malformed whitespace. Native regressions and pinned Chromium comparisons cover effective values. Existing capability remains present."},{"a":"scanner","f":"[A5] Passive audit: cookie security flags + prefixes","s":"present","i":"low","e":"hours","g":"","w":"Re-read passive_scanner.cpp:249-260 (no-httponly/no-secure gated on wasTls/no-samesite) and 456-488 (__Secure- prefix, __Host- prefix with tokenized Path=/ check, broad-path-no-samesite). Present and live per response.","v":"passive_scanner.cpp:250 cookie-no-httponly; :457 cookie-secure-prefix-violation; :476 cookie-host-prefix-violation; :485 cookie-broad-path-no-samesite (uses tokenized pathRoot, not substring)","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A6] Passive audit: CORS misconfiguration","s":"present","i":"low","e":"hours","g":"","w":"Re-read passive_scanner.cpp:283-292 (wildcard+creds high / wildcard info) and 766-793 (origin-reflection-with-creds high, null-origin medium, ACAM/ACAH wildcard). All present and live.","v":"passive_scanner.cpp:284 cors-wildcard-creds; :771 cors-origin-reflection (high); :777 cors-null-origin; :785 cors-methods-wildcard; :790 cors-headers-wildcard","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A7] Passive audit: information disclosure","s":"present","i":"low","e":"hours","g":"","w":"Re-read passive_scanner.cpp:266-277 (server-version-leak, x-powered-by), 700-711 (internal-ip-leak/internal-hostname-leak), 733 (html-comment-leak), plus grep confirmed source-map-exposed:568, exposed-dev-file:671, phpinfo-output:936, server-timing-leak:843. All present.","v":"passive_scanner.cpp:268 server-version-leak; :700 internal-ip-leak; :733 html-comment-leak; grep: :568 source-map-exposed, :671 exposed-dev-file, :936 phpinfo-output","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A8] Passive audit: secrets / sensitive data in URL and body","s":"present","i":"low","e":"hours","g":"Body/secret battery only runs via the API deep-audit (/api/audit/*), not passively and not from any GUI button; the live passive check is URL-query only.","w":"Re-read passive_scanner.cpp:296-311 (secret-in-url over query keys, LIVE per response). Body secret battery SecretScanner::scan confirmed in runDeepAudit control_server.cpp:769-784 emitting secret-exposed with per-type severity. URL check is live; body check is API-only (audit path).","v":"passive_scanner.cpp:346 `addFinding(rowId, req, resp, \"medium\", \"secret-in-url\", ...)` -- live, per response, query keys only. control_server.cpp:786-802 deep-audit block runs `SecretScanner::scan(ssr)` and emits a `secret-exposed` finding with per-type severity -- API-only (/api/audit/*), not passive and not from any GUI button.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A9] Passive audit: tech/CMS fingerprint with CVE correlation","s":"present","i":"low","e":"hours","g":"Passive fingerprints carry no CVE; CVE correlation runs via /api/assess, which now has a GUI trigger (SCANS tab's Assess target panel) but still depends on the bundled cve_database.cpp table, not a live advisory feed.","w":"Re-read passive_scanner.cpp:1394-1523: ~13 CMS + ~8 frameworks emit info-only 'cms-*'/'fw-*' findings with NO CVE; CVE correlation lives only in assessWebTarget (control_server.cpp:396-470), reachable via /api/assess. That endpoint was API-only through 2026-08-10; the SCANS tab's new Assess & audit section (ui-v2/app.jsx) wires a URL input -> /api/assess -> host/port/tls/tech/findingCount display, closing the GUI-reachability half of the gap. The static-DB-vs-live-feed caveat is unchanged and still holds 'present' rather than 'exceeds'.","v":"control_server.cpp:432 `for (const auto &m : Nullock::Core::CveDatabase::lookup(t.cveKind, t.name + \" \" + t.version)) addF(... \"cve-correlated\" ...)`; passive_scanner.cpp:1394 flagCms(...\"cms-wordpress\"...) emits info, no CVE; ui-v2/app.jsx ScansTab's 'Assess target' Section calls NL.actions.assess(url) -> POST /api/assess.","o":"present","r":"Unified scan/audit runner batch: SCANS tab's Assess & audit section adds a GUI trigger for /api/assess, closing the 'no GUI' half of this gap; the live-feed caveat stands untouched."},{"a":"scanner","f":"[A10] Passive audit: DOM-XSS source/sink detection","s":"partial","i":"medium","e":"months","g":"No live DOM taint tracking (no browser); misses runtime-reached sinks and external JS. Regex over the first 1MB of inline HTML only.","w":"Re-read passive_scanner.cpp:1076-1099: static regex over inline scripts for innerHTML<-location, eval<-location, postMessage '*', eval-of-responseText. Regex-only, no runtime taint. Claim holds.","v":"passive_scanner.cpp:1196 `R\"(\\.innerHTML\\s*=\\s*[^;]*(?:location|document\\.referrer|window\\.name))\"` (block starts :1188, body slice :1189-1190)","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified passive_scanner.cpp -- the DOM-XSS sink block (line drift 1076-1099 -> 1188-1213) is still a static QRegularExpression table (innerHTML<-location, eval/setTimeout<-location, postMessage '*', eval-of-responseText) run over `scanBody.left(1MB)` when `html` is true (:1189), gated by `scanBody.size() < 1MB` (:1189). No live DOM taint tracking, no runtime-reached-sink coverage, no external-JS fetch. Claim holds; evidence line refreshed 1083 -> 1196."},{"a":"scanner","f":"[A11] Active audit: SQL injection (error/boolean/blind time-based)","s":"present","i":"medium","e":"days","g":"Boolean/differential blind SQLi is not implemented (Burp does it). Time-based is opt-in only. Dedicated multi-technique module is API-only; GUI users get single-quote error detection via the probe path only.","w":"Re-read sql_injection.cpp end-to-end. Error-based with balanced-payload corroboration (lines 92-124) and blind time-based per-DBMS SLEEP with SLEEP(0) control (131-175) are real. But BOOLEAN-based (true/false differential) is ABSENT -- no such phase exists in the 185-line file. The claim's 'boolean' sub-claim is false. Also: the dedicated module is only reached via /api/audit/* (no GUI); the GUI '","v":"sql_injection.cpp is still 185 lines; error-based phase around line 123 (`QStringLiteral(\"error-based\")`), blind time-based SLEEP-per-DBMS with a SLEEP(0) control around lines 131-175 (`QStringLiteral(\"time-based\")`). No 'boolean' technique string or differential true/false phase anywhere in the file -- claim unchanged.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A12] Active audit: reflected XSS","s":"partial","i":"low","e":"hours","g":"The reduced HTML tokenizer still misclassifies inert template content and some SVG/MathML contexts; it is not a complete browser parser. XML document execution, stored XSS and DOM XSS remain outside this probe. Document sniffing models Chromium 151; older browsers can differ on combined nosniff values.","w":"The public API and deep audit detect reflected tags using effective Content-Type/nosniff values and HTML context checks. Exact raw-text tag names, iframe fallback content and abrupt comment endings now match pinned Chromium comparisons. Confirmed template and foreign-content mismatches prevent a full-parity claim.","v":"Src/Core/Networking/xss_logic.cpp effectiveMediaType/canExecuteHtml/inExecutingHtmlContext; Tests/xss_reflected/xss_reflected_test.cpp; Tests/ui/xss_context_browser_test.cjs; Tests/ui/xss_media_types_browser_test.cjs; scripts/probe_smoke.sh xss-context, xss-media and xss-nosniff fixtures.","o":"present","r":"Correct 66 browser/analyzer mismatches involving custom tag names, iframe fallback text and abrupt comment closure. Add 95 pinned-browser context comparisons and five public-API fixtures. Downgrade present to partial after separately reproducing template and SVG context gaps; those cases remain follow-up work."},{"a":"scanner","f":"[A13] Active audit: OS command injection (incl. blind/OAST)","s":"present","i":"low","e":"hours","g":"GUI probe cmdi is output-channel only (no blind/time). Dedicated CmdInjection module is API-only.","w":"Re-read control_server.cpp:739-747 (CmdInjection::test -> command-injection critical) and GUI probe cmdi at :2325-2339 ('; id' output-channel, uid= regex). OAST infra exists (Src/Core/APIs/Oast/). Present.","v":"control_server.cpp:756-764 deep-audit block: `CmdInjection::test(cir)` -> critical `command-injection` finding (API-only, /api/audit/*). GUI probe cmdi is output-channel only: control_server.cpp:2564-2578, payload `\";id;#\"`, `QRegularExpression rxUid(\"uid=\\\\d+\\\\(.+\\\\) gid=\\\\d+\")` at :2576-2577 -- no blind/time-based leg in the GUI path. OAST infra exists at Src/Core/APIs/Oast/ (oast_server.cpp, oast_correlator.cpp, dns_sink.cpp).","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A14] Active audit: path traversal / LFI","s":"present","i":"low","e":"hours","g":"","w":"Re-read control_server.cpp:749-757 (PathTraversal::test -> path-traversal critical) and GUI probe traversal at :2304-2317 (etc/passwd marker). Present on both surfaces.","v":"control_server.cpp:753 `const auto res = Nullock::Core::PathTraversal::test(ptr);`; :2309 `if (body.contains(\"root:x:0:0:\") ...)`","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A15] Active audit: XXE injection","s":"present","i":"medium","e":"hours","g":"Reachable via /api/audit/run|all. /api/audit/run now has a GUI trigger (SCANS tab's Audit run panel with per-tester include checkboxes) but XXE is still not part of the TESTS tab's uniform battery or the 'Probe all rows' quick action.","w":"Re-read control_server.cpp:655-668: XxeInjection::test, content-type/body-gated to XML, emits xxe-injection critical. Module file xxe_injection.cpp (91 lines) exists. Was present but fully API-only through 2026-08-10; the SCANS tab's new Audit run panel now POSTs url/method/body/include (xxe among the checkboxes) to /api/audit/run and renders the per-tester hit summary + raw response.","v":"control_server.cpp:663 `const auto res = Nullock::Core::XxeInjection::test(xrr);` gated by :658 `if (ctl.contains(\"xml\") || bt.startsWith(\"<?xml\") ...)`; ui-v2/app.jsx ScansTab's 'Audit run' Section include-checkbox list contains \"xxe\", posting to NL.actions.auditRun -> POST /api/audit/run.","o":"present","r":"Unified scan/audit runner batch: SCANS tab's Audit run panel adds a GUI trigger for /api/audit/run (include-checkbox battery, xxe among them); still absent from TESTS' uniform battery and Probe-all, called out honestly."},{"a":"scanner","f":"[A16] Active audit: server-side template injection","s":"present","i":"medium","e":"hours","g":"API-only (/api/audit/*); not in the GUI probe battery, so a GUI-only user never runs SSTI.","w":"Re-read control_server.cpp:786-801: iterates up to 5 query params, Ssti::test, emits ssti-confirmed critical with engine names. Present but API-only.","v":"control_server.cpp:796 `const auto res = Nullock::Core::Ssti::test(sr);` :797 `if (res.confirmed) { ++hits; engines << res.engines; }`","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A17] Active audit: SSRF (cloud metadata + OAST)","s":"present","i":"low","e":"hours","g":"","w":"Re-read control_server.cpp:704-714 (SsrfScan::test, ssrf-cloud-metadata escalated to critical) and the GUI probe SSRF at :2181-2274 (6 cloud-metadata probes with shaped controls + OAST token minting/correlation). Present and strong on both surfaces.","v":"control_server.cpp:725 `const auto res = Nullock::Core::SsrfScan::test(srr);`; :2426-2486 GUI probe (6 cloud-metadata endpoints with shaped-control suppression) reports critical ssrf-cloud-metadata; :2494-2512 OAST mintToken/registerToken+fire-and-forget.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A18] Active audit: LDAP injection","s":"present","i":"medium","e":"hours","g":"The high-fidelity engine is reachable from the GUI two ways: the per-row live probe fires an ldap-injection-suspect heuristic, and the full LdapInjection::test now also runs via the Findings tab's 'Deep audit all rows' button (POST /api/audit/all, default sweep). No remaining GUI gap.","w":"Re-read control_server.cpp:684-692 (LdapInjection::test -> ldap-injection high). Module ldap_injection.cpp (111 lines) exists. Present but API-only.","v":"control_server.cpp:688 `const auto res = Nullock::Core::LdapInjection::test(lrr);`","o":"present","r":"The Findings tab's new 'Deep audit all rows' button (real-data.js NL.actions.auditAll -> POST /api/audit/all {fromHistory:true}) runs the default deep-audit sweep -- which already includes LdapInjection::test -- against every history row with params/body. Closes the 'API-only' gap."},{"a":"scanner","f":"[A19] Active audit: XPath injection","s":"present","i":"medium","e":"hours","g":"No longer API-only: the Findings tab's 'Deep audit all rows' button runs the default sweep (which includes XpathInjection::test) against every history row with params/body. No per-row probe-battery entry exists, but the high-fidelity tester is now one click away in the GUI.","w":"Re-read control_server.cpp:694-702 (XpathInjection::test -> xpath-injection high). Module xpath_injection.cpp (111 lines) exists. Present but API-only.","v":"control_server.cpp:698 `const auto res = Nullock::Core::XpathInjection::test(xrr);`","o":"present","r":"Closed via the same 'Deep audit all rows' button as LDAP/host-header/cache-poison/deser/nosql/mass-assign/CORS -- one frontend change (auditAll action + button, POST /api/audit/all) surfaces the whole default-sweep cluster."},{"a":"scanner","f":"[A20] Active audit: server-side code / EL / OGNL injection","s":"partial","i":"low","e":"weeks","g":"OGNL/Struts2 is now ACTIVELY probed (no longer CVE-correlation-only): the SSTI tester's two-expression arithmetic proof gained the %{ } delimiter family, which only OGNL/Apache-Struts2 evaluates, so an OGNL-parsed sink is confirmed and fingerprinted as Struts2. Remaining gap: generic non-arithmetic server-side code-eval -- SpEL class access (T(java.lang.Runtime)...), raw eval() APIs, and OGNL member-access chains beyond infix math -- is still not actively probed.","w":"Extended the proven SSTI engine rather than duplicating it: added { \"%{\", \"}\", \"OGNL (Apache Struts2)\" } to ssti_tester.cpp families(). The existing polyglot sends pre%{a*b}sep%{c*d}suf and confirmsArithmetic() requires BOTH products with the literal separator preserved and neither raw expression echoed -- so a Struts2 OGNL sink confirms while pure reflection / a single-expression calculator do not. No other family uses %{ }, so the hit's engine string uniquely fingerprints OGNL.","v":"ssti_tester.cpp families() now includes the %{ } OGNL family; hpp doc updated (\"...also covers OGNL/Apache-Struts2\"). Live-proven in scripts/probe_smoke.sh: a new ssti-ognl mock evaluates ONLY %{N*N} (not Jinja {{ }}), and /api/ssti/test confirms it with engines containing 'OGNL' AND not 'Jinja2' (2 new cases). Mutation-proven: deleting the %{ } family drops that case to confirmed:false/hits:[] while ssti-vuln/safe/calc stay correct. Gauntlet: ctest 100/100, probe_smoke 158/158.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified ssti_tester.cpp -- the `{ \"%{\", \"}\", \"OGNL (Apache Struts2)\" }` family (:32) is present and wired exactly as described, giving an active OGNL/Struts2 confirm via the arithmetic-polyglot proof. Generic non-arithmetic server-side code-eval (SpEL class access, raw eval() APIs, OGNL member-access chains) is still not actively probed -- grep for SpEL/T\\(java\\.lang\\.Runtime confirms no such family exists. Claim holds, no drift."},{"a":"scanner","f":"[A21] Active audit: HTTP request smuggling (CL.TE / TE.CL)","s":"present","i":"medium","e":"hours","g":"The per-row live probe already fires an http-smuggling-clte-suspect heuristic. The full opt-in Smuggling::test battery IS GUI-reachable: the Scans tab's 'Audit run' section has a per-tester include checkbox list with a 'smuggle (opt-in, not in default sweep)' entry that posts include:['smuggle'] to /api/audit/run. Prior gap text calling this API-only via a direct POST to /api/audit/all was stale/incorrect.","w":"Register-accuracy correction, no code change: re-verified against live source rather than trusting the prior gap text. ui-v2/app.jsx's AUDIT_INCLUDES array (Scans tab, 'Audit run' section) includes \"smuggle\", rendered as a checkbox labeled '(opt-in, not in default sweep)', wired through doAuditRun -> NL.actions.auditRun(url, {include}) -> POST /api/audit/run, which calls the identical runDeepAudit(...) helper (and its smuggle-gated branch) that /api/audit/all uses. The prior note said this was reachable 'only via a direct POST to /api/audit/all' -- that was already false by the time it was written and stayed uncorrected across several later waves.","v":"ui-v2/app.jsx:1943 AUDIT_INCLUDES array contains \"smuggle\"; :2382-2387 renders one checkbox per include name in the Audit run Section, with the smuggle checkbox specially labeled; :1945-1952 doAuditRun() builds opts.include from the checked set and calls NL.actions.auditRun; ui-v2/real-data.js:371 auditRun(url,opts) posts to /api/audit/run; Src/BackEnd/Control/control_server.cpp:6953,6991 /api/audit/run reads bodyJson.value(\"include\") and calls runDeepAudit(m_wiring.scanner, t, include, testerReports); control_server.cpp:634-642 runDeepAudit's smuggling branch is gated on include.contains(\"smuggle\").","o":"present","r":"Wave 0 register-accuracy fix: corrected stale gap text claiming the opt-in smuggling battery was reachable only via a direct POST to /api/audit/all. Live source shows it has been GUI-reachable via the Scans tab's Audit run section's smuggle checkbox (POST /api/audit/run, same runDeepAudit include-gated branch) since that section landed -- no code change, state stays present, only the gap/why/evidence text corrected."},{"a":"scanner","f":"[A22] Active audit: Host header injection / poisoning","s":"present","i":"medium","e":"hours","g":"No longer API-only: reachable from the GUI via the Findings tab's 'Deep audit all rows' button (default sweep includes HostHeader::test). The per-row live probe still only fires an X-Forwarded-Host cache-poison variant, not host-header-injection proper, but the high-fidelity tester itself is now GUI-reachable.","w":"Re-read control_server.cpp:609-629: HostHeader::test, splits high host-header-injection (Host->Location) from medium host-header-reflected-location. Present but API-only.","v":"control_server.cpp:614 `const auto res = Nullock::Core::HostHeader::test(hhr);` :620 fromHostLine && where=='Location' -> high","o":"present","r":"Closed via the shared 'Deep audit all rows' button (auditAll action, POST /api/audit/all default sweep)."},{"a":"scanner","f":"[A23] Active audit: web cache poisoning","s":"present","i":"medium","e":"hours","g":"Fully GUI-reachable: the default sweep ('Deep audit all rows') still runs the narrower X-Forwarded-Host variant per row, and the TESTS tab now also has a dedicated Web cache poisoning panel wiring the full CachePoison::test single-target probe directly (/api/cache/poison) with a free-form custom-header editor -- the confirmed/cacheable/unkeyed severity ladder, baseline status, and request count are all rendered.","w":"Re-read control_server.cpp:594-607: CachePoison::test with severity ladder confirmed(critical)/cacheable(high)/unkeyed(low). Present but API-only.","v":"control_server.cpp:599 `const auto res = Nullock::Core::CachePoison::test(cpr);` :601-604 sev/kind ladder","o":"present","r":"Wired the previously-orphaned /api/cache/poison endpoint into a dedicated Web cache poisoning panel on the TESTS tab (custom-header textarea + URL/method + confirmed/cacheable hit table), closing the last GUI-reachability gap UI-NAVIGABILITY.md tracked for this endpoint."},{"a":"scanner","f":"[A24] Active audit: open redirection","s":"present","i":"low","e":"hours","g":"","w":"Re-read control_server.cpp:575-592 (OpenRedirect::test, header-confirmed high / client-side medium) and GUI probe open-redirect at :2156-2179 (external-host canary in Location). Present on both surfaces.","v":"control_server.cpp:592-609 (OpenRedirect::test, header-confirmed high / client-side medium); :2401-2424 GUI probe emits open-redirect on external-canary Location match.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A25] Active audit: CRLF / response header injection","s":"present","i":"low","e":"hours","g":"","w":"Re-read control_server.cpp:759-767 (CrlfInjection::test -> crlf-injection high). GUI probe also has a CRLF marker probe (control_server.cpp:2341+). Present.","v":"control_server.cpp:780 `const auto res = Nullock::Core::CrlfInjection::test(cir);` (deep-audit path, note(\"crlf\", ...) -> \"high\"/\"crlf-injection\"); :2645-2663 GUI probe injects `x%0d%0aX-Nullock-Inject:%20<tag>` and reports high crlf-injection when the header is reflected verbatim in the response.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A26] Active audit: insecure deserialization","s":"present","i":"medium","e":"hours","g":"No longer API-only: DeserProbe::test is reachable from the GUI via 'Deep audit all rows' (default sweep). Still no per-row probe-battery entry.","w":"Re-read control_server.cpp:716-727: DeserProbe::test -> per-format kind critical. Module deser_probe.cpp (248 lines) exists. Present but API-only.","v":"control_server.cpp:720 `const auto res = Nullock::Core::DeserProbe::test(drr);` :726 kindForFormat(...)","o":"present","r":"Closed via the shared 'Deep audit all rows' button (auditAll action, POST /api/audit/all default sweep)."},{"a":"scanner","f":"[A27] Active audit: NoSQL injection","s":"present","i":"medium","e":"hours","g":"The per-row live probe already fires a nosql-injection-suspect heuristic, and the full NoSqlInjection::test operator battery is now also reachable from the GUI via 'Deep audit all rows' (default sweep). No remaining GUI gap.","w":"Re-read control_server.cpp:644-652: NoSqlInjection::test -> nosql-injection high. Present but API-only.","v":"control_server.cpp:648 `const auto res = Nullock::Core::NoSqlInjection::test(nrr);`","o":"present","r":"Closed via the shared 'Deep audit all rows' button (auditAll action, POST /api/audit/all default sweep)."},{"a":"scanner","f":"[A28] Active audit: mass assignment / auto-binding","s":"present","i":"low","e":"hours","g":"Only default field names, only when a body is present, no app-model awareness (inherent to blind mass-assignment testing -- Burp has the same limitation). No longer API-only: reachable from the GUI via 'Deep audit all rows' (default sweep), in addition to the existing per-row mass-assignment-suspect heuristic.","w":"Downgraded exceeds->present. Re-read control_server.cpp:558-568: MassAssign::test over default fields, only when a body is present, emits mass-assignment high. It is a real check beyond Burp core, but it is a basic default-field probe, fires only with a body, and is API-only (no GUI). 'exceeds' overstates a modest, gated, headless check.","v":"control_server.cpp:565 `const auto res = Nullock::Core::MassAssign::test(mr, Nullock::Core::MassAssign::defaultFields());` gated by :558 `&& !t.body.isEmpty()`","o":"present","r":"Closed the GUI-reachability gap via the shared 'Deep audit all rows' button (auditAll action, POST /api/audit/all default sweep)."},{"a":"scanner","f":"[A29] Active audit: CORS active probing (attacker-origin reflection)","s":"present","i":"low","e":"hours","g":"No longer API-only: CorsTester::test (worst-probe severity, real probe-kind labeling) is reachable from the GUI via 'Deep audit all rows' (default sweep). Still no per-row probe-battery entry.","w":"Re-read control_server.cpp:523-541: CorsTester::test picks the worst reflected-origin probe and reports its real kind/severity. Present but the audit path is API-only.","v":"control_server.cpp:527 `const auto res = Nullock::Core::CorsTester::test(cr);` :533 tracks worst severity/kind","o":"present","r":"Closed via the shared 'Deep audit all rows' button (auditAll action, POST /api/audit/all default sweep)."},{"a":"scanner","f":"[A30] Access-control / authz testing via multi-identity replay","s":"present","i":"medium","e":"hours","g":"Identities still supplied as manual header sets (no auto-login); divergence heuristic is status/size only (false-positives on dynamic pages).","w":"GUI-reachability gap closed 2026-08-11: an AUTHZ TEST button on Proxy history / Site map's DetailPane (ui-v2/proxy.jsx) opens a modal identity editor (name + raw \"Header: value\" lines per identity, add/remove), POSTs to the existing /api/authz-test via a new NL.actions.authzTest(rowId, identities), and renders the per-identity status/bodySize table plus a divergent/consistent verdict banner -- the server still files the authz-divergence finding into Issues independently. The remaining caveats (manual identities, naive status/size divergence heuristic) are real and unrelated to this batch, left honestly in the gap text above rather than claimed fixed.","v":"control_server.cpp:4592 POST /api/authz-test {rowId, identities:[{name,headers}]} -> {ok,divergent,results:[{identity,ok,status,bodySize,error}],row}; ui-v2/proxy.jsx AuthzTestOverlay + DetailPane's \"AUTHZ TEST\" button; ui-v2/real-data.js NL.actions.authzTest.","o":"","r":"Authz-test batch: multi-identity replay modal wired into Proxy/Site-map DetailPane, closing the GUI-reachability half of #78 [A30]."},{"a":"scanner","f":"[A31] Hidden parameter discovery (param miner)","s":"present","i":"low","e":"hours","g":"Deep-audit param-mining still uses only the first 60 wordlist entries (runDeepAudit's in-sweep variant, unchanged). The standalone /api/paramminer endpoint now has a GUI button (SCANS tab's Param miner panel, default or pasted wordlist, uncapped up to the backend's 2000-entry limit).","w":"Re-read control_server.cpp:6604-6634 (/api/paramminer, wordlist capped 2000, off-thread) and runDeepAudit:500-510 (folded in, but wordlist there is capped to only the first 60 names via .mid(0,60)) -- that in-audit truncation is unchanged. The standalone endpoint was API-only through 2026-08-10 (grep ui-v2 'parammin' was empty); the SCANS tab's new Param miner panel now POSTs url + optional pasted wordlist to /api/paramminer and renders requestsSent/candidatesTried/foundCount + the found-param list.","v":"control_server.cpp:6627 `wordlist = Nullock::Core::ParamMiner::defaultWordlist();` :6628 capped 2000; runDeepAudit:505 `ParamMiner::defaultWordlist().mid(0, 60)`; ui-v2/app.jsx ScansTab's 'Param miner' Section calls NL.actions.paramMine(url, opts) -> POST /api/paramminer.","o":"present","r":"Unified scan/audit runner batch: SCANS tab's Param miner panel adds a GUI trigger for /api/paramminer; the deep-audit in-sweep 60-entry cap remains an honest separate gap, untouched."},{"a":"scanner","f":"[A32] Scan launch modes (crawl-only/crawl+audit/audit-selected/live-passive)","s":"partial","i":"medium","e":"weeks","g":"No 'crawl then audit' pipeline, no live active scanning of proxy traffic, no named launch-mode selector.","w":"Re-read: passive is always-on live (passive_scanner.hpp:71-73), active is manual per-URL (/api/audit/run:6460) or session-wide (/api/audit/all:6513 fromHistory). Crawler is a separate endpoint. No unified crawl->audit pipe, no named launch-mode selector. Claim holds.","v":"control_server.cpp:7855 `/api/audit/all` pulls history rows; :4722 `/api/crawler/start` is separate; no code path feeds crawler output into runDeepAudit","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified control_server.cpp -- /api/crawler/start (:4722, was :3959) and /api/audit/run (:7802) / /api/audit/all (:7855, was :6513) remain three independent entry points; no code path feeds crawler output into runDeepAudit, no named launch-mode selector exists. Claim holds; evidence line numbers refreshed."},{"a":"scanner","f":"[A33] Issue severity model (High/Medium/Low/Info)","s":"present","i":"low","e":"hours","g":"","w":"Re-read passive_scanner.hpp:26 (severity 'info|low|medium|high|critical') and control_server.cpp severityRank/computePostureGrade. Adds a critical tier above Burp's High. Confirmed.","v":"passive_scanner.hpp:26 `QString severity;     // \"info\" | \"low\" | \"medium\" | \"high\" | \"critical\"`","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A34] Issue confidence model (Certain/Firm/Tentative)","s":"present","i":"low","e":"hours","g":"Confidence is derived from the kind string, not per-evidence; no user override.","w":"Re-read passive_scanner.hpp:39-47 (confidence field) and finding_enricher.cpp:463-487 confidenceForKind maps kinds -> confirmed/firm/tentative. Confirmed.","v":"finding_enricher.cpp:463 confidenceForKind(); passive_scanner.hpp:47 `QString confidence;`","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A35] Retest an individual issue","s":"partial","i":"medium","e":"weeks","g":"Cannot re-run one check for one issue; only whole-baseline diff, not tied to the original insertion point/payload.","w":"Re-read: grep for retest finds no per-issue endpoint. Only /api/baseline/save + /api/baseline/diff (control_server.cpp:4074,4147) re-run and diff the whole finding set. Claim holds.","v":"control_server.cpp:4926 `if (path == \"/api/baseline/diff\")`; no per-finding retest route exists","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified control_server.cpp -- /api/baseline/save (:4853, was :4074) and /api/baseline/diff (:4926, was :4147) remain the only baseline-related routes; grep for `retest` across control_server.cpp and ui-v2/ returns no per-issue retest endpoint or UI action. Claim holds; evidence line numbers refreshed."},{"a":"scanner","f":"[A36] Authenticated scanning: session-handling rules (macros)","s":"partial","i":"high","e":"weeks","g":"HTTP scanners and the crawler now use enabled cookies, tool-scoped session rules and recorded HTTP login macros, including expiry-triggered refresh. Browser interaction recording and JavaScript-driven login execution remain unavailable.","w":"The shared HTTP client applies Scanner-scoped session rules, captures rotated tokens/cookies and refreshes configured expired sessions. Explicit identity comparisons and recorded macro requests retain their own credentials.","v":"Src/Core/Networking/networking.cpp; session_rules.cpp; crawler.cpp; scripts/scanner_sessions_regression.py; Tests/session_rules/session_rules_test.cpp","o":"","r":"HTTP authenticated scan workflows verified, including form CSRF replacement, compressed token extraction, refresh cooldown, request fidelity and project isolation. Browser login execution remains a separate gap."},{"a":"scanner","f":"[A37] Out-of-scope handling during scans","s":"present","i":"low","e":"hours","g":"","w":"Active tools check every concrete outbound request against host, protocol, port and path scope. Raw TCP/TLS probes require an unrestricted endpoint grant. Invalid enabled rules fail closed; invalid editor saves preserve the prior policy.","v":"Src/Core/Networking/outbound_scope.cpp; HttpClient::send; raw port/TLS/WebSocket guards; Tests/scope_logic/scope_logic_test.cpp; Tests/proxy_shutdown/proxy_shutdown_test.cpp; scripts/outbound_scope_regression.py; Tests/ui/scope_browser_test.cjs","o":"present","r":"Full outbound scope boundary, live policy updates, full-URL redirect/crawler checks and visible validation errors."},{"a":"scanner","f":"[A38] Scan speed vs accuracy tradeoff settings","s":"partial","i":"medium","e":"weeks","g":"No thread-count/concurrency control; no fast/normal/thorough presets that change payload depth or retries.","w":"Re-read control_server.cpp:6524-6527 (audit/all throttleMs default 150 bounded 0..60000, limit default 50 bounded 1..200) and the sweep worker at 6584-6592 (single serial QtConcurrent::run loop). Only throttle+cap, serial, no concurrency knob, no accuracy presets. Claim holds.","v":"control_server.cpp:7947 `auditAllInFlight.storeRelease(0); // sweep done` -- single serial loop with QThread::msleep(throttleMs) between targets","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified control_server.cpp /api/audit/all -- throttleMs default 150 bounded 0..60000 and limit default 50 bounded 1..200 (line drift 6524-6527 -> ~7866-7869), sweep dispatched via QtConcurrent::run but the target loop itself is still a single serial iteration with QThread::msleep(throttleMs) between targets (no thread-count knob, no fast/normal/thorough accuracy presets). Claim holds; evidence line numbers refreshed."},{"a":"scanner","f":"[A39] Live scanning of proxy traffic (live active audit tasks)","s":"partial","i":"medium","e":"weeks","g":"No live active task; user must manually kick off /api/audit/all or GUI 'Probe all rows' after browsing.","w":"Re-read: passive is wired live on every response (app.cpp:945-946 crawler->onResponseReceived, scanner ctor). Active auditing is only user-triggered (/api/audit/run, /api/audit/all fromHistory, GUI /api/probe/all). No auto-active-scan of in-scope requests as they pass. Claim holds.","v":"app.cpp:1266 `QObject::connect(&crawler, ...entryLoaded, ...)` / :1271 `&scanner, &...::onResponseReceived)`; no live active-scan task exists","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified app.cpp -- crawler.entryLoaded is still connected straight to scanner.onResponseReceived for passive-only coverage (line drift 945-946 -> 1266-1271); active auditing remains exclusively user-triggered via /api/audit/run, /api/audit/all, or GUI /api/probe/all. No live active-scan task exists. Claim holds; evidence line numbers refreshed."},{"a":"scanner","f":"[A40] Vulnerable/outdated JS library detection","s":"partial","i":"low","e":"weeks","g":"Version-string correlation against a bundled DB, not a retire.js-style known-vulnerable-JS hash catalogue or live feed.","w":"Re-read: js_recon.cpp exists; assessWebTarget correlates detected tech+version to CveDatabase (control_server.cpp:431-435); framework fingerprints passive_scanner.cpp:1483-1517. CVE correlation is version-string based against the curated cve_database.cpp, not a retire.js hash/pattern catalogue. Claim holds.","v":"control_server.cpp:452 `CveDatabase::lookup(t.cveKind, t.name + \" \" + t.version)`; no hash/pattern library-advisory catalogue in Src/","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified control_server.cpp assessWebTarget (line drift 431-435 -> 415-452) still resolves via CveDatabase::lookup(t.cveKind, name+version) -- version-string correlation against the bundled cve_database.cpp, not a retire.js-style hash/pattern catalogue. Claim holds; evidence line numbers refreshed."},{"a":"scanner","f":"[B1] Crawl: JavaScript/SPA crawling via embedded browser","s":"absent","i":"high","e":"months","g":"No browser-driven crawl; client-rendered SPA navigation is invisible.","w":"Re-read crawler.cpp:151-183 (regex link extraction over static HTML) and grep of Src/ for headless|chromium|puppeteer|webengine|CDP returns nothing in the crawl path. Confirmed absent; task #12 headless-browser DAST still pending.","v":"crawler.cpp:154 'Doesn't run JS so heavily-SPA targets won't yield many links'; no browser engine in Src/","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-verified crawler.cpp:153 comment still reads \"Doesn't run JS so heavily-SPA targets won't yield...\" (line drift from :154); grep of Src/ for headless|chromium|puppeteer|webengine|CDP in the crawl path still returns nothing. Confirmed still absent, no drift in substance."},{"a":"scanner","f":"[B2] Active audit: stored cross-site scripting","s":"absent","i":"medium","e":"months","g":"No stored-XSS detection (needs inject-at-A / detect-at-B after re-crawl). Neither the dedicated module nor the GUI probe attempts it.","w":"Re-read xss_reflected.hpp:12 ('DOM-based, and stored XSS are out of scope') and grep 'stored.?xss' across Src/ returns only that exclusion comment. No inject-here/detect-there correlation engine. Confirmed absent.","v":"xss_reflected.hpp:12 '...DOM-based, and stored XSS are out of scope for this reflected check.'; no stored-xss correlation code exists","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-verified xss_reflected.hpp:12 still excludes \"DOM-based, and stored XSS\" from the reflected checker's scope; grep for stored.?xss across Src/ still returns only that exclusion comment. No inject-at-A/detect-at-B correlation engine exists. Confirmed still absent."},{"a":"scanner","f":"[B3] Scan configuration library (saved named configs / presets)","s":"absent","i":"medium","e":"weeks","g":"No saved/named scan configs, no built-in preset library, no import/export. Every run re-specifies include[] + throttle inline.","w":"Re-read control_server.cpp:6480-6483 (audit selection is a freeform include[] set built per-call). Grep of Src/ and ui-v2/ for scanConfig|savedConfig|config.?library|named.?config|scanProfile returns nothing. No persistence of a scan profile. Confirmed absent.","v":"control_server.cpp:6481 `QSet<QString> include;` built inline per request; grep for named/saved config returns empty","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-verified control_server.cpp /api/audit/all still builds its `include` set as a freeform QSet<QString> parsed inline per request (no persisted profile); grep of Src/ and ui-v2/ for scanConfig|savedConfig|config.?library|named.?config|scanProfile still returns nothing. Confirmed still absent."},{"a":"scanner","f":"[B4] Scan queue with per-task detail (progress, pause/resume/cancel)","s":"absent","i":"high","e":"weeks","g":"No scan queue UI/model; cannot inspect, pause, resume, cancel, or see per-target/per-insertion-point progress.","w":"Re-read control_server.cpp:6516-6519 (single global auditAllInFlight atomic flag) and 6584-6593 (one QtConcurrent::run loop, returns only a queued count). No task model, no per-item status, no pause/resume. Grep ScanQueue|scanTask|pauseScan returns only an unrelated kMaxScanTasks constant. Confirmed absent.","v":"control_server.cpp:7858 `static QAtomicInteger<int> auditAllInFlight(0);`; sweep returns only a queued count","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-verified control_server.cpp -- auditAllInFlight is still a single global QAtomicInteger<int> testAndSetAcquire gate (line drift 6516 -> 7858), the sweep still returns only a queued count, no per-task model, no pause/resume/cancel. grep for ScanQueue|scanTask|pauseScan still returns only the unrelated kMaxScanTasks constant. Confirmed still absent; evidence line refreshed."},{"a":"scanner","f":"[B5] Issue suppression / false-positive marking","s":"present","i":"high","e":"weeks","g":"None -- the ISSUES tab (ui-v2/app.jsx IssuesTab) now has per-finding fp/un-fp and del/restore buttons plus a severity-override <select>, and a per-kind mute/muted button on each kind filter chip, all calling the already-built /api/findings/mark, /delete, /set-severity, and /suppress-kind routes and reflecting the returned falsePositive/deleted/suppressed flags back onto each row.","w":"Wave 0 register-accuracy audit: the 2026-08-17 close left this PARTIAL pending the Issues-UI follow-on; that follow-on has since landed (not separately reconciled here before now). ui-v2/app.jsx:1811-1826 defines doMarkFP/doToggleDelete/doSetSeverity/doSuppressKind, and each is wired to a live control: the fp/un-fp and del/restore buttons + severity <select> on every finding row (app.jsx:2342-2377), and a mute/muted button on every kind chip in the filter row (app.jsx:2198-2208). real-data.js:595-598 posts each to its backend route. Verified end to end against control_server.cpp:6891 (/api/findings/mark), :6910 (/suppress-kind), :6922 (/set-severity, /delete) and the snapshot's falsePositive/deleted/suppressed/severity fields (control_server.cpp:1420-1429) that the UI reads back. Upgraded partial -> present.","v":"ui-v2/app.jsx:1811-1826 (doMarkFP/doToggleDelete/doSetSeverity/doSuppressKind), :2198-2208 (per-kind mute button), :2342-2377 (per-finding fp/del buttons + severity select); ui-v2/real-data.js:595-598 (findingMark/findingDelete/findingSetSeverity/findingSuppressKind); control_server.cpp:6891,6910,6922 (routes), :1420-1429 (snapshot flags).","o":"absent","r":"Wave 0 register-accuracy audit: upgraded partial -> present. The 2026-08-17 entry closed the backend (/api/findings/mark, /suppress-kind) and left the Issues-UI buttons as a named follow-on; grepping ui-v2/app.jsx today shows that follow-on is already fully wired (per-finding fp/del buttons, a severity-override select, and a per-kind mute button), calling all four persisted mutation routes and rendering their returned flags -- parity.json simply never caught up to that landing. No code changed in this commit; this is a state correction only."},{"a":"scanner","f":"[B6] Authenticated scanning: recorded login sequences","s":"partial","i":"high","e":"months","g":"Recorded steps are raw HTTP requests replayed via ChainRunner (built from Proxy history row IDs), not a browser interaction recording -- a JS-driven/SPA login that requires executing client-side script to reach the auth endpoint still cannot be captured or replayed. Also, per item #84, the deep-audit testers don't consult SessionRules directly, so a macro's re-auth only refreshes the shared variable bag, not an in-flight audit request.","w":"UPGRADED absent->partial: this grade is genuinely stale. Commit 88cbe99 (2026-08-28), after this file's audit_date (2026-07-30) and reconciled_through (2026-08-25), added SessionMacro (session_rules.hpp:93-101): a named macro combining recorded ChainRunner steps with an optional logged-out-status/body-regex auto-re-auth trigger. SessionRules::runMacro (session_rules.hpp:135) replays the steps synchronously and ingestVariables merges extracted values into the host's variable bag, which the existing session-rule injection pipeline then applies to subsequent requests -- a real login-sequence-replay auth mechanism, not just static header/cookie rules.","v":"session_rules.hpp:93 `struct SessionMacro { QString name; QString sessionHost; QList<ChainRunner::Step> steps; QString loggedOutStatus; QString loggedOutBodyRegex; };`; control_server.cpp:4555 `/api/session-macros` (get/set, persisted via projectStore->setSessionMacros) and :4574 `/api/session-macros/run` (QtConcurrent::run(sr->runMacro)); ui-v2/app.jsx:7370 \"LOGIN MACROS -- named recorded login sequences ... record steps from Proxy history\"; ui-v2/real-data.js:448-450 sessionMacrosGet/Set/Run.","o":"","r":"Wave 0 register-accuracy audit: UPGRADED absent -> partial. SessionMacro (named, recorded-from-proxy-history login sequences with ChainRunner replay and auto re-auth trigger on logged-out detection) landed in 88cbe99, after this file's prior audit_date/reconciled_through window. Fully wired: backend struct+persistence, /api/session-macros (get/set) and /api/session-macros/run endpoints, and a GUI 'Login macros' panel in app.jsx recording steps from Proxy history rows. Remaining gap: HTTP-replay only, no browser-driven capture for JS/SPA logins, and per item #84 the deep-audit path doesn't consult SessionRules mid-request."},{"a":"extender","f":"[A1] HttpHandler — handleHttpRequestToBeSent / handleHttpResponseReceived, fired for every Burp tool with the originating ToolType","s":"partial","i":"high","e":"weeks","g":"No ToolType: a handler cannot tell proxy from repeater from scan probe and cannot opt out per tool. Intruder is silently uncovered — extensions never see or influence an attack. Host/port immutable, so no redirection. Binary bodies unrepresentable (bodyText is a QString; corruption is avoided only by refusing to write back an unchanged body).","w":"CONFIRMED, every cited line re-read and correct (control_server line numbers shifted +1 for the deep-scan sites because of uncommitted marketplace code, 2105->2106 etc.; the replay sites 2875/2895 are exact). I independently re-ran the reach analysis: `grep -rn applyRequestMutation Src/` returns proxy_server.cpp {273,527,603,684} + control_server.cpp {2106,2674,2745,2780,2875} and nothing else; `g","v":"extensions_api.cpp:695-697 `// Read final mutated values back into the C++ struct. Host/port stay // immutable on purpose -- changing them mid-flight would require // reconnecting to a different upstream, which is a bigger design.`; extensions_api.cpp:720 `req.headers = headersFromJs(entry.property(\"headers\"));`","o":"partial","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[A2] ScanCheck registration — custom passive and active scan checks (registerScanCheck / doPassiveScan / doActiveScan, consolidateDuplicateIssues)","s":"partial","i":"high","e":"weeks","g":"An output channel, not a scan check. No registration, no insertion-point-driven invocation, no active checks (structurally impossible without a send API), no per-check enable/disable, no duplicate consolidation (rowId hard-coded 0). Deep-scan probes call applyRequestMutation, which only lets an extension rewrite Nullock's own probes.","w":"CONFIRMED but the claim is generous and I nearly downgraded. reportFinding at extensions_api.cpp:61-78 is verbatim as quoted and app.cpp:728 `extensions.setScanner(&scanner);` is real, and dom_taint.js is a shipped extension that genuinely lands findings in the panel, so a USER does get working extension-authored passive detection — that is more than a stub. But there is no registration API of any","v":"extensions_api.cpp:122-124 `// rowId 0 = extension-originated; the panel still renders it, the URL // makes it actionable.` then `scanner->reportFinding(0, severity, kind, summary, evidence, host, url);`; extensions_api.hpp:342 `Q_INVOKABLE void reportFinding(...)` is the only finding-related bridge method.","o":"partial","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[A3] Extension output and error streams: api.logging().output()/error(), per-extension Output and Errors tabs, redirectable to console or file","s":"partial","i":"medium","e":"days","g":"One global stream for all extensions — attribution only if the author prefixed the line. No stdout/stderr separation, no file or console redirect, no export, no scrollback. Only the newest 40 of 500 buffered lines are exposed by any API and only 30 are rendered; a chatty extension loses lines silently.","w":"CONFIRMED, and WORSE than the auditor stated in one respect I verified myself. kMaxLogLines=500 and the ring buffer are verbatim. But the 500-line buffer is not reachable: the ONLY API surface is bootInfo, which calls recentLog(40) (control_server.cpp:1226), and there is no /api/extensions/log endpoint — `grep -n '/api/extensions' control_server.cpp` returns exactly install-builtins:5272 and reloa","v":"extensions_api.cpp:27 `constexpr int kMaxLogLines = 500;`; extensions_api.cpp:485-486 `if (m_logLines.size() > kMaxLogLines) m_logLines.remove(0, m_logLines.size() - kMaxLogLines);`; control_server.cpp:1311 `for (const QString &line : m_wiring.extensions->recentLog(40))`; ui-v2/app.jsx:1393 `: extLog.slice(-30).map((line, i) => (`","o":"partial","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[A4] Extension auto-reload during development (Auto-reload checkbox; Ctrl/Cmd-click to reload a single extension)","s":"partial","i":"medium","e":"hours","g":"The auto-reload checkbox now exists and works end-to-end (toggling it in Settings' Extensions card flips the same opt-in QFileSystemWatcher the backend shipped in 5dba22c). Still missing: the Ctrl/Cmd-click-to-reload-a-single-extension gesture named in the title -- Reload (and now auto-reload) both rebuild the whole QJSEngine and re-run every script; there is no per-extension reload path, backend or frontend.","w":"Wave 2 (2026-08-23): wired the auto-reload CHECKBOX -- the ui-v2 half the prior wave (5dba22c) explicitly left as the honest remainder. Added NL.actions.setExtAutoReload (ui-v2/real-data.js, POSTs the already-existing /api/extensions/auto-reload {value}) and a checkbox in Settings' Extensions card action row (ui-v2/app.jsx), initialised from the already-published bootInfo.extAutoReload and updated optimistically with a revert-on-failure guard, matching the toggleExtensionEnabled pattern already used two rows below it. No backend change -- the endpoint and snapshot field existed and were unread, same shape as the accept-invalid-cert and CVE-overlay waves before it. Stays partial, not present: single-extension reload (the Ctrl/Cmd-click gesture) is unbuilt at any layer.","v":"ui-v2/real-data.js setExtAutoReload(value) posts /api/extensions/auto-reload {value}; ui-v2/app.jsx SettingsTab: extAutoReload state seeded from b.extAutoReload (bootInfo, control_server.cpp:1293 bootInfo[\"extAutoReload\"] = m_wiring.extensions->autoReload()), toggleExtAutoReload() calls the action and reconciles against the server's echoed autoReload; checkbox rendered in the Extensions card's action row next to the existing Install bundled / Reload buttons. control_server.cpp:6417-6421 POST handler unchanged (pre-existing). Single-extension reload: grep 'reload.*name\\|per-extension.*reload' across ExtensionsApi/ui-v2 = no match; /api/extensions/reload and setAutoReload's own reload() both call the same whole-engine rebuildEngine().","o":"partial","r":"Wave 2: wired the [A4] auto-reload checkbox into Settings' Extensions card (ui-v2/app.jsx + ui-v2/real-data.js), closing the ui-v2-reachability half the prior backend wave (5dba22c) left open. No backend change. Stays partial -- the Ctrl/Cmd-click single-extension reload gesture remains unbuilt, honestly named in the updated gap text."},{"a":"extender","f":"[A5] BApp Store: extension detail page (full description, author, version, source-code link, 'Report a bug')","s":"present","i":"low","e":"days","g":"No changelog and no screenshots (the catalog has no per-entry changelog field or images to show); everything else is closed. The Marketplace card's per-item DETAILS button opens an in-app panel with author/version/summary/categories/permissions/full sha256, a link to the published docs/marketplace/e/<id>.html detail page (rendered source), a raw-source download link, and a prefilled GitHub issue link for bug reports.","w":"Closed 2026-08-10: the prior gap was specifically the missing IN-APP detail surface (the web catalog detail pages already existed). Added a DETAILS toggle per Marketplace row (ui-v2/app.jsx Marketplace) that renders a panel from the already-fetched catalog entry -- no new fetch -- plus three links (full description & source, raw source, report a bug) built from the entry's `id`.","v":"docs/marketplace/index.html:88-91 `<p class=\"summary\">${ext.summary || \"\"}<\/p> ... <span>by ${ext.author || \"unknown\"}<\/span>` assigned via `div.innerHTML = ...` (line 81); marketplace_logic.hpp:61-63 `-- \"summary\" and \"author\" in particular are free text from a remote file and must be escaped by whoever renders them.`; EXTENSIONS.md:141-143 `the manifest's hooks is descriptive metadata for the ca","o":"present","r":"Extender/BApp-store batch: in-app extension detail panel closes #99."},{"a":"extender","f":"[A6] BApp Store: submission and review process (PortSwigger reviews source before publication)","s":"partial","i":"low","e":"days","g":"PR review is still the whole human review model and no third party has used it. No signing, no automated source review. But integrity IS pinned end to end now (manifest sha256 + CI drift check + install-time verification), which the first pass reported as absent.","w":"State CONFIRMED but the auditor's gap statement is now FACTUALLY WRONG and I corrected it. They wrote 'no signing, no hash pinning in the manifest'. The uncommitted working tree adds exactly that: every catalog entry now carries a sha256, CI fails the build on a missing/malformed digest AND on drift between the manifest hash and the committed .js. That is stronger than 'trust the PR'. Still partia","v":"extensions/marketplace.json:+ `\"sha256\": \"8c02c0578289944a6dc858726e7a1357804bff3872a80480fa606b496b554d1a\"` on each entry; .github/workflows/ci.yml `- name: every extension pins a well-formed sha256` / `(.sha256 | test(\"^[0-9a-f]{64}$\"))` and `- name: manifest hashes match the committed extensions` / `run: bash scripts/marketplace_sync.sh --check`; docs/marketplace/index.html:62 `Submit a PR to B","o":"partial","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[A7] Security model around third-party code (Burp: in-process, full JVM privileges, no sandbox, no permission model)","s":"exceeds","i":"low","e":"days","g":"Extensions still share one QJSEngine, so a loaded observe-only script can pollute globals/prototypes another relies on while both are active. reload() now DESTROYS and rebuilds the QJSEngine (rebuildEngine, extensions_api.cpp:93-107 / reload :121-146), so those effects no longer persist past an uninstall or reload. Remaining real gap (tracked separately as task #115): no per-extension execution-time bound -- grep for setInterrupted/isInterrupted/watchdog/deadline in ExtensionsAPI/ is empty, so a runaway handler freezes the main event loop, including the removal endpoint. That hardening (a watchdog thread calling QJSEngine::setInterrupted) is a separate ~1-day build, not required to keep the 'exceeds' verdict.","w":"Re-confirmed 2026-08-11 against live source: default-deny modify-requests/modify-responses grants parsed from the script (ExtensionPerms::isAllowed, enforced at onRequest registration and in doMutateResponse per-handler, extensions_api.cpp:36-59,489-491) -- a real permission model Burp lacks entirely. rebuildEngine confirmed to fully replace the QJSEngine on reload, not just clear a namespace. setInterrupted/watchdog/deadline confirmed still absent (0 grep hits in Src/Core/APIs/Extensions/).","v":"extensions_api.cpp:93-107 rebuildEngine fresh QJSEngine per reload; :36-59 grant-gated registration; :489-491 mayMutate discard; grep setInterrupted/watchdog/deadline ExtensionsAPI/ = empty (no time bound)","o":"exceeds","r":"Wave 0 register-accuracy audit: gap/evidence text was stale (referred to an earlier reload() that only cleared a namespace) -- refreshed to describe the current rebuildEngine behavior and the still-open execution-time-bound gap (task #115), re-verified against live source. State unchanged (exceeds)."},{"a":"extender","f":"[A8] Per-extension declared capability visibility (Burp shows only what the extension registered)","s":"present","i":"medium","e":"hours","g":"None -- the Extensions card in Settings now renders a per-script row with a modifies-traffic / observe-only badge sourced from bootInfo.extensionGrants (the DOWNLOADED script's own declared capabilities, not the marketplace catalog's claim).","w":"Closed 2026-08-10: bootInfo.extensionGrants was already published (control_server.cpp:1240-1244) but nothing in ui-v2 read it. Added a per-script row under the Extensions card (ui-v2/app.jsx SettingsTab) that looks up extensionGrants[filename] and flags modify-requests/modify-responses as 'modifies traffic', anything else as 'observe-only', with the full declared-capability list in a title tooltip. No backend change -- the field already existed and was unread.","v":"extensions_api.cpp:145-147 `appendLog(g.isEmpty() ? QString(\"[ext] loaded %1 (observe-only)\").arg(fi.fileName()) : QString(\"[ext] loaded %1 (granted: %2)\").arg(fi.fileName(), g.join(\", \")));`; control_server.cpp:1237-1241 `const auto &sg = m_wiring.extensions->scriptGrants(); ... bootInfo[\"extensionGrants\"] = grants;`; ui-v2/app.jsx:456-476 renders only `<Row label=\"Folder\">`, `<Row label=\"Loaded\"; ui-v2/app.jsx SettingsTab Extensions card now maps scripts to b.extensionGrants[s] per row (2026-08-10).","o":"present","r":"Extender/BApp-store batch: per-extension capability badges close #102."},{"a":"extender","f":"[B1] Montoya API (burp.api.montoya) — typed, versioned extension API; BurpExtension.initialize(MontoyaApi)","s":"absent","i":"medium","e":"months","g":"No object model, no typed events, no versioning. Extensions receive ad-hoc JS objects built in doMutateRequest/doMutateResponse. A different design rather than a smaller one.","w":"CONFIRMED. I re-ran the greps myself across Src/ ui-v2/ extensions/: montoya=0, IBurpExtender=0, registerExtension/ExtensionPoint=0. I read extensions_api.hpp end to end — the bridge really is exactly four Q_INVOKABLEs, no more.","v":"extensions_api.hpp:297-345 -- the complete bridge, `class ExtensionsApiBridge : public QObject`: `Q_INVOKABLE void log(const QString &message);`, `Q_INVOKABLE void onResponse(const QJSValue &callback);`, `Q_INVOKABLE void onRequest(const QJSValue &callback);`, `Q_INVOKABLE void reportFinding(...)`.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B2] Legacy Extender API (IBurpExtenderCallbacks) retained for backward compatibility","s":"absent","i":"low","e":"months","g":"No compatibility layer. Moot unless Nullock ever hosts a JVM.","w":"CONFIRMED by my own grep: IBurpExtenderCallbacks / registerExtenderCallbacks = 0 hits across Src/, ui-v2/, extensions/. Nothing to upgrade — there is no JVM to host it.","v":"extensions_api.hpp:297-345 defines ExtensionsApiBridge as the sole JS-facing class; no other extension entry point exists in the tree.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B3] Java extension support (load a .jar as an extension)","s":"absent","i":"high","e":"months","g":"No JVM host, so the entire BApp ecosystem is unreachable. Largest single difference in this area.","w":"CONFIRMED. loadAll globs only *.js and I re-read the line; no .jar/JVM/jni references. This is the structural fork in the road for the whole area.","v":"extensions_api.cpp:400 `const QFileInfoList files = QDir(dir).entryInfoList({ \"*.js\" }, QDir::Files, QDir::Name);` -- the only extension discovery path in the codebase.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B4] Python extension support via Jython","s":"absent","i":"high","e":"months","g":"No Python extensions; throwaway Python BApps must be rewritten as ES5-ish JS with no stdlib.","w":"CONFIRMED by my own grep (jython=0) and by the loader glob, which I re-read.","v":"extensions_api.cpp:400 `entryInfoList({ \"*.js\" }, QDir::Files, QDir::Name);` -- the only extension discovery path in the codebase.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B5] Ruby extension support via JRuby","s":"absent","i":"low","e":"months","g":"Absent. Low real-world demand.","w":"CONFIRMED (jruby=0 in my grep; same loader restriction).","v":"extensions_api.cpp:400 `entryInfoList({ \"*.js\" }, QDir::Files, QDir::Name);` -- the only extension discovery path in the codebase.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B6] Extension environment settings: library JAR folder / module import path","s":"absent","i":"medium","e":"weeks","g":"Extensions cannot share code or use libraries; primitives get inlined by hand in every script.","w":"CONFIRMED. `grep -rn installExtensions Src/` = 0 in my own run, so the engine gets no console, no require, no import — the sandbox has no module system to configure.","v":"extensions_api.cpp:253,322 -- the ONLY global installed is the bridge: `m_bridge = new ExtensionsApiBridge(this);` ... `m_engine->globalObject().setProperty(\"nullock\", nullockObj);`","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B7] ProxyRequestHandler / ProxyResponseHandler — DROP a message, force intercept, or follow intercept rules","s":"absent","i":"high","e":"days","g":"An extension cannot block a request, force interception, or annotate/highlight a history row. Rules out blockers, auto-taggers and per-request interception logic.","w":"Re-verified against live source. doMutateRequest (moved 358-379 -> 672-721 across intervening waves) still only reads back method/path/headers/bodyText -- no sentinel, no action enum, no drop path, matching the prior finding exactly. Noted for completeness: proxy.jsx has since grown a #299 per-row highlight+comment layer, but that is a *user*-driven manual UI feature, not an extension hook -- it does not touch the extension-facing gap this item grades on, which is unchanged.","v":"extensions_api.cpp:672-721 doMutateRequest -- the full read-back: `const QString m = entry.property(\"method\").toString();` ... `req.headers = headersFromJs(entry.property(\"headers\")); req.body = entry.property(\"bodyText\").toString().toUtf8();` -- no action/verdict field is ever consulted (line drift from the prior pass's 358-379 citation, content unchanged).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-read doMutateRequest's readback (line drift 358-379 -> 672-721) -- confirms no action/drop field is ever consulted, matching the prior finding exactly. No code change this pass."},{"a":"extender","f":"[B8] Intruder payload generator provider (registerPayloadGeneratorProvider)","s":"absent","i":"medium","e":"days","g":"Extensions cannot feed Intruder, and cannot influence an Intruder request by any other path either.","w":"CONFIRMED again, re-checking the whole bridge surface rather than trusting the old '164-185, four methods' citation, which has drifted -- the surface has grown substantially since (log/onResponse/onRequest/onUnload/registerUnloadingHandler/history/reportFinding/sendToRepeater/sendToIntruder on the main bridge, plus entirely new utils/collaborator/storage bridges for codecs, OOB mint-and-poll, and a KV store) -- none of it payload-generation-shaped. intruder.cpp has also grown 608->956 lines; a fresh grep still returns zero extension references anywhere in it.","v":"extensions_api.hpp:296-436 -- the complete current JS-facing surface (ExtensionsApiBridge plus the utils/collaborator/storage bridges) has no payload-generator registration of any kind; `grep -rni 'extension' Src/Core/Networking/intruder.cpp` (956 lines, up from 608) still returns nothing.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-read the whole extensions_api.hpp bridge surface (grown to 296-436, replacing the stale 164-185/four-method citation) and re-grepped intruder.cpp (now 956 lines, was 608) -- no payload-generator seam either place. No code change this pass."},{"a":"extender","f":"[B9] Intruder payload processor (registerPayloadProcessor) — transform each payload before placement","s":"absent","i":"high","e":"days","g":"The classic escape hatch for custom encodings/signing inside an attack. Without it a bespoke-signed API cannot be fuzzed.","w":"CONFIRMED. Re-read the current bridge surface (extensions_api.hpp:296-436, replacing the stale 164-185 citation) -- no processor registration exists. control_server.cpp's rule-ops handler (moved 3262 -> 3992) still exposes only the built-in transform set, unchanged in shape.","v":"extensions_api.hpp:296-436 -- no processor registration; control_server.cpp:3992 `if (path == \"/api/intruder/rule-ops\")` exposes only the built-in rule set (line drift from 3262).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-read the bridge surface and the rule-ops handler (line drift 3262 -> 3992) -- still no processor-registration seam. No code change this pass."},{"a":"extender","f":"[B10] Session handling action (registerSessionHandlingAction) — extension-provided action invocable from a session rule","s":"absent","i":"high","e":"days","g":"No extension-driven auth/login macro. Custom SSO or signature schemes must be always-on onRequest handlers instead of scoped session rules.","w":"CONFIRMED. Fresh `grep -rnia 'extension|macro|ExtensionsApi' Src/Core/Networking/session_rules*.cpp` still returns only hits for the unrelated session-macro login-flow feature (a stored request-replay macro, not an extension seam) -- zero for actual extension/ExtensionsApi wiring. extensions/aws_sigv4.js:30-36's hard-coded-creds CONFIG block is unchanged, still the only workaround an SSO/custom-signature scheme has.","v":"`grep -rnia 'extension|macro|ExtensionsApi' Src/Core/Networking/session_rules*.cpp` = 0 hits; extensions/aws_sigv4.js:30-36 `var CONFIG = { accessKey: \"\", secretKey: \"\", ...` — the workaround is an always-on onRequest handler with hard-coded creds","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-grepped session_rules*.cpp for extension/macro/ExtensionsApi -- confirms the 'macro' hits are all the unrelated session-handling-rules feature, none an extension seam. No code change this pass."},{"a":"extender","f":"[B11] Custom suite tab (userInterface().registerSuiteTab)","s":"absent","i":"high","e":"weeks","g":"Extensions are headless. Autorize / Turbo Intruder / JWT Editor / Logger++ shapes have no equivalent.","w":"CONFIRMED, and the gap has actually WIDENED in file count even though the conclusion holds: alongside the still-8-line extensions_hub.qml (blank white Rectangle) and the still-0-byte extensions_hub_model.cpp/.hpp, two MORE blank-Rectangle placeholder files have landed since -- Src/FrontEnd/GUI/ExtensionsHub/Components/extensions_console.qml and .../extensions.qml, each an identical 8-line `import QtQuick; Rectangle { ... color: \"#ffffff\" }` stub. Neither is referenced by app.qml or CMakeLists.txt -- confirmed by grep, zero hits for all three file names in both. Three orphaned placeholder shells now exist where the prior audit found one; none is wired to anything, so the mount-point gap is unchanged.","v":"Src/FrontEnd/GUI/ExtensionsHub/extensions_hub.qml (8 lines, unchanged: `Rectangle { id: extensionsHub; width: 400; height: 300; color: \"#ffffff\" }`) plus two newer siblings -- Components/extensions_console.qml and Components/extensions.qml, both identical 8-line blank-Rectangle stubs -- none referenced by grepping app.qml or CMakeLists.txt for any of the three names (0 hits); extensions_hub_model.cpp/.hpp remain 0 bytes.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Found two new but equally-orphaned blank-Rectangle QML stubs (Components/extensions_console.qml, Components/extensions.qml) alongside the original extensions_hub.qml -- none wired into app.qml or CMakeLists.txt, so the no-mount-point conclusion is unchanged, just now evidenced by three stub files instead of one. No code change this pass."},{"a":"extender","f":"[B12] Context menu items (ContextMenuItemsProvider), scoped by InvocationType","s":"absent","i":"medium","e":"days","g":"'Send to <my extension>', the most common BApp integration point, has no equivalent.","w":"CONFIRMED. Fresh repo-wide case-insensitive grep for contextMenu/ContextMenuItemsProvider/InvocationType across Src/ and ui-v2/ (vendor excluded) still returns zero hits.","v":"extensions_api.hpp:296-436 -- no UI registration method on the bridge (line drift from the stale 164-185 citation).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Fresh grep for contextMenu/ContextMenuItemsProvider/InvocationType -- still 0 hits. No code change this pass."},{"a":"extender","f":"[B13] Message editor tabs (registerHttpRequestEditorProvider / HttpResponseEditorProvider)","s":"absent","i":"medium","e":"weeks","g":"The built-in Inspector/Decoder is not extensible.","w":"CONFIRMED. Re-read the whole Settings Extensions card, which has grown substantially since the prior citation (line drift 456-477 -> 1319-1391): it now adds per-extension enable/disable checkboxes, a modifies-traffic/observe-only capability badge per script, an Auto-reload (dev) toggle, and an 'Install bundled' button -- none of it a pluggable editor-tab surface. A fresh grep for registerHttpRequestEditorProvider/HttpResponseEditorProvider still returns 0 hits -- the built-in Inspector/Decoder remains closed to extensions.","v":"ui-v2/app.jsx:1319-1391 -- the complete current extension UI: per-extension Loaded checkbox + modifies-traffic/observe-only capability badge, an Auto-reload (dev) toggle, an Install bundled button, `<Row label=\"Folder\" value={b.extensionsDir} copyable />`, and a 30-line log tail. Still a management list only -- no editor-tab mount point (line drift from the prior 456-477 citation).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. The Settings Extensions card has grown (enable checkboxes, capability badges, auto-reload toggle, Install bundled button, line drift 456-477 -> 1319-1391) but is still a management list, not a pluggable editor-tab surface. No code change this pass."},{"a":"extender","f":"[B14] Scanner insertion point provider (registerScannerInsertionPointProvider)","s":"absent","i":"medium","e":"days","g":"Custom serialization formats cannot be taught to the scanner.","w":"CONFIRMED. Fresh case-insensitive grep for insertion|injectionPoint|insertPoint across Src/ still returns only the same two non-seam hits as before, with line drift: the Intruder §payload§ marker label at Src/App/app.qml:984 (unchanged) and a prose comment in control_server.cpp, now at :7800 (was :6599).","v":"`grep -rnia 'insertion|injectionPoint|insertPoint' Src/` -> Src/App/app.qml:984 (unchanged UI label) and control_server.cpp:7800 (prose comment, drifted from 6599) -- neither is a provider seam.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Fresh grep for insertion/injectionPoint/insertPoint -- same two non-seam hits, line drift 6599 -> 7800 on the comment. No code change this pass."},{"a":"extender","f":"[B15] Extension can issue its own HTTP requests through the tool's stack (api.http().sendRequest)","s":"absent","i":"high","e":"weeks","g":"An extension is purely reactive: it cannot confirm a finding, enumerate, or re-issue a request. This is why no scan-check, macro or crawler BApp equivalent can exist.","w":"CONFIRMED, core gap unchanged -- the bridge still has no I/O-performing method. The surrounding surface has grown since the prior pass in ways worth noting so the register doesn't read as if nothing changed: ExtensionsApiBridge gained sendToRepeater/sendToIntruder (fire-and-forget pushes into those tools' UI, no response returned to the script) and a new ExtensionsCollaboratorBridge exposes generate()/interactions() (mint an OOB token, later poll for out-of-band HTTP/DNS hits). Both are genuinely useful but neither lets an extension issue a request through the tool's stack and read the reply synchronously -- re-read every one of the now much larger set of Q_INVOKABLE methods to confirm none is a disguised sendRequest. None is.","v":"extensions_api.hpp:296-436 -- the complete current bridge surface (9 ExtensionsApiBridge methods + 11 across the utils/collaborator/storage bridges); none performs synchronous request I/O. sendToRepeater/sendToIntruder (:351-354) push only, no return value; collaborator generate()/interactions() (:398,404) is async OOB polling, not request/response I/O.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent for the core ask (no synchronous send-and-read-response method), while noting two new adjacent-but-not-closing additions since the prior pass: sendToRepeater/sendToIntruder (push-only, no response) and the new collaborator bridge's generate()/interactions() (async OOB polling). Neither is I/O an extension can use to confirm a finding synchronously. No code change this pass."},{"a":"extender","f":"[B16] Extension access to Burp Collaborator (api.collaborator().createClient(), poll interactions)","s":"partial","i":"medium","e":"days","g":"No OOB payload generation or interaction polling from an extension.","w":"CONFIRMED after checking the local synonym the brief warned about — 'Collaborator' is 'OAST' here, and oast_logic.cpp does exist — but the bridge exposes none of it. There is no oast/collaborator reference anywhere under Src/Core/APIs, and the four-method bridge has no payload-generation or polling entry point.","v":"extensions_api.hpp:164-185 (complete bridge, no OAST method); the OAST subsystem lives at Src/Core/Networking/oast_logic.cpp and is wired to the scanner in app.cpp:890 `oastCorrelator.setScanner(&scanner);` — never to extensions","o":"absent","r":"absent -> partial. Both named absences closed: nullock.collaborator (Burp's api.collaborator()) now gives extensions OOB payload generation AND interaction polling. generate() mints an OAST token via OastServer::mintToken() and returns { token, hostUrl, pathUrl, port, baseHost }, recording the token; interactions() reads OastServer::hitsSince(0) (HTTP) + DnsSink::hitsSince(0) (DNS), filters to the tokens THIS collaborator minted, and returns each as { id, token, type:'http'|'dns', sourceIp, atMs, host, method, path }. Wired via ExtensionsApi::setOast(&oast,&dnsSink) in app.cpp (OAST + DNS sinks are in the same APIs lib -- no cross-lib callback interface); the collaborator bridge is CppOwned so its minted-token set survives an engine reload (a callback landing after a reload still surfaces). VERIFIED e2e (5/5): a test extension generates a token (interactions empty), a real DNS callback is fired to that token, and after reload interactions() surfaces a dns hit scoped to its token. ctest 100/100, probe 156/156. REMAINDER (why still partial): SMTP interactions (Nullock has no SMTP sink) and the full raw callback body / Burp's per-client object nesting; the core mint+poll for HTTP+DNS is done."},{"a":"extender","f":"[B17] Extension access to sitemap and proxy history (api.siteMap(), api.proxy().history()); adding issues to the sitemap","s":"partial","i":"medium","e":"days","g":"Reclassify absent->partial: the 'add issues' half IS present — reportFinding(severity,kind,summary,evidence,url) routes into the same findings/scanner sink with CWE/OWASP/CVSS enrichment (extensions_api.cpp:61-78), which is the addToSiteMap-issue equivalent. The READ half (api.siteMap()/api.proxy().history()) is still absent — extensions only see the single live entry built per request/response, n","w":"Reclassified absent -> partial (2026-08-02): triage + adversarial-verify agreed; keyed by stable roadmap id, area-guarded. See PARITY-BACKLOG.md.","v":"extensions_api.cpp:61-78 reportFinding->scanner sink (issue-add works); onResponseReceived (196-240) builds one live entry only; no history/siteMap read method on the bridge","o":"absent","r":"PROGRESS (stays partial). Closes the proxy-history READ half: new bridge invokable nullock.history(max) returns the most recent proxy exchanges (method/host/port/path/url/tls/status/responseSize/atMs), Burp's api.proxy().history() equivalent. ExtensionsApi keeps a bounded ring (kMaxHistory) recorded at the TOP of onResponseReceived -- before the no-handlers early-return -- so history is complete even for a script that registered no onResponse handler; ungated (same traffic onResponse already observes); owner-thread only (record + read on the engine thread, no mutex); not cleared on engine rebuild (history is proxy traffic, outlives a reload). e2e vs the live app (4/4): a test extension driven by real proxy traffic (curl -x) reads a history growing 1->2->3 with correct GET/200/url per entry, history(1) clamps to one. ctest 99/99, probe 156/156. With the 'add issues' half already present (reportFinding), the two remaining pieces are api.siteMap() (a distinct tree API -- though an extension can now DERIVE a sitemap from history()) and history body/header access (current entries carry metadata + size, not full bytes)."},{"a":"extender","f":"[B18] Extension can start/configure scans (startAudit / startCrawl) and read scan issues","s":"absent","i":"low","e":"days","g":"Absent.","w":"CONFIRMED. setScanner (now :121, drifted from 80-81) remains a C++-side wiring point only; the JS-facing surface (now :296-436, replacing the stale 164-185 citation) still has no startAudit/startCrawl/read-issues method. reportFinding is still write-only into the sink.","v":"extensions_api.hpp:121 `void setScanner(IFindingSink *scanner) { m_scanner = scanner; }` (line drift from 80-81) -- a C++-side wiring point, not JS-reachable; the JS surface is extensions_api.hpp:296-436.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Line drift only (setScanner 80-81 -> 121); still no scan-control or issue-read method on the JS surface. No code change this pass."},{"a":"extender","f":"[B19] Extension can send items to other tools (sendToRepeater / Intruder / Organizer / Comparer)","s":"partial","i":"medium","e":"days","g":"Extension-driven cross-tool workflow is not possible.","w":"CONFIRMED by my own greps (sendToRepeater=0, sendToIntruder=0) and by reading the bridge.","v":"extensions_api.hpp:164-185 — no cross-tool method","o":"absent","r":"absent -> partial. Cross-tool workflow from an extension is now possible for the two primary attack tools: nullock.sendToRepeater(host,port,tls,request) opens a fresh Repeater tab and populates its target + request; nullock.sendToIntruder(...) loads Intruder's base request. Since APIs deliberately does NOT link Networking, the handlers are std::function callbacks (ExtensionsApi::SendFn) wired from app.cpp with lambdas that drive repeater.addTab/setHost/... and intruder.setHost/setRequestTemplate; ungated (uses the extension's own request data + only stages a tool the user then drives). VERIFIED e2e (7/7): a test extension's sends land -- Repeater snapshot shows target.example:8443 tls + the request text, Intruder snapshot shows intr.example:9443 + the request template. ctest 100/100, probe 156/156. REMAINDER (why still partial): sendToComparer / sendToOrganizer / sendToDecoder from an extension (the '/ Organizer / Comparer' half of the title) not wired yet."},{"a":"extender","f":"[B20] Extension utilities: api.utilities() — Base64/URL/hex/gzip codecs, ByteArray, crypto helpers","s":"partial","i":"medium","e":"days","g":"Every extension re-implements primitives by hand in ES5. No base64, gzip, hashing or byte-level type.","w":"CONFIRMED. The engine setup is two lines and installs exactly one global; with installExtensions never called there is not even a console. I verified the downstream consequence in the shipped extension.","v":"extensions_api.cpp:87-88 `QJSValue nullockObj = m_engine.newQObject(m_bridge); m_engine.globalObject().setProperty(\"nullock\", nullockObj);` — the only global; extensions/aws_sigv4.js inlines SHA-256/HMAC because of it","o":"absent","r":"absent -> partial. Added nullock.utils (Burp's api.utilities() grouping): base64Encode/Decode, urlEncode/Decode, hexEncode/Decode, htmlEncode/Decode, sha256/sha1/md5 -- so an extension no longer hand-rolls base64/hex/hashing in ES5 (the aws_sigv4.js inline-SHA256 the evidence cites). Pure Qt6::Core module extensions_utils_logic.{hpp,cpp} (QByteArray/QUrl/QCryptographicHash) wrapped 1:1 by a grouped ExtensionsUtilsBridge QObject published as nullock.utils, CppOwned so it survives an engine reload() and is re-wrapped each rebuild; ungated (pure text transforms). extensions_utils_logic_test 23/23 (known base64/hex/html vectors + the sha256/sha1/md5 'abc' digests) + 2 mutations (htmlEncode < mis-map; sha256->Sha1 swap); e2e vs the live QJSEngine 12/12 (a test extension's nullock.utils.* results match the pure module). ctest 100/100, probe 156/156. REMAINDER (why still partial): gzip/compression helpers (need a zlib deflate path; extensions already get decompressed response bodies via onResponse) and a byte-array type + the broader Burp utils families (number/random/string) -- JS has no native byte type, so a ByteArray helper is a separate design."},{"a":"extender","f":"[B21] Extension unloading handler (registerUnloadingHandler) — clean teardown","s":"present","i":"high","e":"hours","g":"STALE PRIOR EVIDENCE — reclassify absent->partial. The gap's core claim ('the QJSEngine is never recreated, so an uninstalled script's globals persist in shared scope until restart') is NO LONGER TRUE: reload() now calls rebuildEngine(), which destroys the engine and constructs a fresh one, re-publishing `nullock` (extensions_api.cpp:93-107, 121-146). So the clean-slate half is DONE. What remains ","w":"Reclassified absent -> partial (2026-08-02): independent triage + adversarial-verify agreed; cited files re-confirmed to exist. See PARITY-BACKLOG.md.","v":"extensions_api.cpp:93-107 rebuildEngine() destroys+recreates the engine; reload() 121-146 calls it — the 'globals persist' concern is resolved; no onUnload/registerUnloadingHandler invokable exists (hpp:191-212)","o":"absent","r":"partial -> present. The clean-slate half (rebuildEngine on reload) was already done; this adds the missing teardown-callback half the gap called out. New bridge invokables nullock.onUnload(fn) + the Burp-name alias nullock.registerUnloadingHandler(fn) register an ungated teardown callback (a cleanup hook touches only the script's own state, never the wire -- so it registers like onResponse observation). runUnloadHandlers() fires each once on the owner thread while the engine is still alive, at the START of reload() (before rebuildEngine destroys the engine) and from the destructor (app exit); handlers are isolated (one throwing can't skip the rest) and rebuildEngine() now clears m_onUnloadHandlers too, so none leaks across a reload (QJSValue-lifetime). VERIFIED e2e vs the live app: onUnload does NOT fire on mere load, DOES fire on the next reload (teardown), the alias behaves identically, and the user's real extensions were left untouched. ctest 99/99, probe_smoke 156/156."},{"a":"extender","f":"[B22] Extension settings persistence: persistence().extensionData() / preferences()","s":"partial","i":"high","e":"days","g":"Config is still a hand-edited literal in the .js. The manifest's declared secret handling remains decorative even after the marketplace rewrite. Configuring AWS creds means editing source and reloading.","w":"CONFIRMED and REINFORCED. The obvious upgrade candidate was the new marketplace code, so I checked it specifically: `grep -n config Src/Core/Networking/marketplace_logic.cpp` = 0 hits, and the CatalogEntry struct has no config member. The manifest's config schema — including `\"secret\": true` on the AWS keys — is still read by nothing at all.","v":"marketplace_logic.hpp:64-77 `struct CatalogEntry { QString id; QString name; QString summary; QString version; QString author; QStringList categories; QString url; QString sha256; QStringList hooks; QStringList declaredPermissions; };` — no config field; extensions/aws_sigv4.js:30-36 `var CONFIG = { accessKey: \"\", secretKey: \"\", ...`","o":"absent","r":"absent -> partial. The persistence().extensionData() / preferences() API now exists: nullock.storage.set/get/has/keys/remove/clear, a JSON key/value store (strings, numbers, nested objects/arrays) an extension uses to keep settings/state. Persisted to <appData>/nullock-ext-storage.json -- deliberately a SIBLING of the extensions dir, NOT inside it, so a set() never trips the new auto-reload watcher. Grouped ExtensionsStorageBridge published as nullock.storage, CppOwned so it survives an engine reload(). VERIFIED e2e (8/8): set/get round-trips a string/number/nested-object, has()/keys() correct, the value is written to the sibling file, and after a full app RESTART the extension reads it back on boot. ctest 100/100, probe 156/156. So an extension can now stop hardcoding config (e.g. aws_sigv4's CONFIG literal) and persist it via nullock.storage. REMAINDER (why still partial): (1) the store is GLOBAL, not per-extension isolated (Nullock's shared engine has no per-extension identity at call time; extensions namespace keys) -- Burp's extensionData() is per-extension; (2) no user-facing config INPUT path yet -- Nullock extensions have no per-extension settings UI, so a user still can't enter e.g. AWS creds through the GUI (they'd call the API or the extension self-configures); the manifest's decorative 'secret:true' config schema is a separate injection mechanism, still unwired."},{"a":"extender","f":"[B23] Extensions > Installed tab: per-extension 'Loaded' checkbox to enable/disable without removing","s":"present","i":"high","e":"hours","g":"None -- the Extensions Installed card (ui-v2/app.jsx SettingsTab) now renders bootInfo.extensionAll (every .js present, loaded or disabled) as a checkbox-per-row list instead of only the loaded-scripts list; each checkbox is bound to the extension's persisted enabled state and calls NL.actions.setExtensionEnabled(name, enabled) -> POST /api/extensions/set-enabled, matching the backend contract the de0efca wave already shipped and e2e-verified.","w":"Closed the last gap on this item 2026-08-21: the backend half (de0efca, 2026-08-20) already persisted a per-extension enable/disable state and exposed it via bootInfo.extensionAll + POST /api/extensions/set-enabled, but ui-v2 still read only bootInfo.extensionScripts (loaded-only, no enabled flag, no toggle) -- a disabled extension vanished from the Installed list entirely and there was no way to flip it back on from the GUI. The Installed card now sources its row list from extensionAll ({name, enabled} for every script on disk) and renders a checkbox per row (checked = e.enabled) that calls the new ui-v2/real-data.js NL.actions.setExtensionEnabled(name, next) thin wrapper on toggle, with optimistic local state (React.useState synced from bootInfo via a JSON.stringify-keyed effect, same pattern as the existing mitmBlockedList) and a revert-on-failure fallback. A disabled row shows a plain 'disabled' badge instead of the modifies-traffic/observe-only trust badge, since a disabled script is never (re-)parsed and so carries no live grants to show. Extensions title count switched from extensionScripts.length (loaded-only) to extAllList.length (every installed extension) so a disabled extension still counts toward the header total.","v":"ui-v2/app.jsx SettingsTab: extAllList React.useState seeded from b.extensionAll, toggleExtensionEnabled(name, next) calling NL.actions.setExtensionEnabled; Extensions card row: <input type='checkbox' checked={!!e.enabled} onChange={() => toggleExtensionEnabled(s, !e.enabled)} />. ui-v2/real-data.js: setExtensionEnabled(name, enabled) { return post('/api/extensions/set-enabled', { name, enabled: !!enabled }).then(r => r.json()); }. Backend contract unchanged (already shipped/verified in the de0efca wave): control_server.cpp:1284-1293 bootInfo.extensionAll = [{name, enabled}] via m_wiring.extensions->allScripts()/isExtensionEnabled(); control_server.cpp:6404-6413 POST /api/extensions/set-enabled {name, enabled} -> extensions->setExtensionEnabled(...).","o":"present","r":"partial -> present. The only remaining gap this item named -- the ui-v2 Loaded checkbox in the Installed tab -- is now built, wired to the already-verified backend endpoint. No backend touched. The separate per-project extensionsEnabled template field remains a no-op, but that is a distinct feature (per-project extension state on project switch), not this global enable/disable checkbox."},{"a":"extender","f":"[B24] Extensions > Installed tab: Remove (uninstall) button","s":"present","i":"medium","e":"hours","g":"API only, no UI control, and only for ids that pass safeScriptFileName. Removal leaves the uninstalled script's global-scope side effects live in the shared engine until restart.","w":"UPGRADED — the first pass's evidence ('only two extension endpoints exist') is now out of date. The working tree adds POST /api/marketplace/uninstall backed by a real implementation with path confinement, a canonical-path containment check against symlink escape, and an automatic reload afterwards. It is API-reachable today. Not 'present' because no button exists anywhere: `grep -rna marketplace u","v":"control_server.cpp:5425-5438 `if (path == \"/api/marketplace/uninstall\") { ... const bool ok = Nullock::Core::Marketplace::uninstall(id, m_wiring.extensions->extensionsDir(), &err); if (ok) m_wiring.extensions->reload();`; marketplace.cpp:202-209 `const QString canonicalDir = QFileInfo(extensionsDir).canonicalFilePath(); ... if (canonicalDir.isEmpty() || canonicalFile.isEmpty() || QFileInfo(canonic","o":"partial","r":"Remove button in the marketplace panel, and reload() now REBUILDS the QJSEngine, so an uninstalled script's globals and prototype patches no longer survive. The audit's stated gap -- removal leaving side effects live until restart -- is closed and regression-tested."},{"a":"extender","f":"[B25] Extensions > Installed tab: Up/Down buttons to control invocation order","s":"absent","i":"medium","e":"hours","g":"With multiple mutating extensions the composition order is fixed by filename (alphabetical, deterministic since a QDir::Name sort was added to loadAll()) but still not user-adjustable -- two extensions rewriting the same header still fight, just predictably rather than at random.","w":"CONFIRMED the ask (no reorder control exists) but CORRECTED a stale claim in the prior audit's own 'why': loadAll() -- the call that actually determines handler registration/invocation order -- now sorts with QDir::Name (extensions_api.cpp:400, added since the prior pass), so invocation order is deterministic alphabetical-by-filename, not the arbitrary filesystem order the prior audit's 'fight non-deterministically' language implied. (A second, unsorted entryInfoList call at :298 is refreshWatch()'s file-watch registration, order-irrelevant there.) The user-facing gap is unchanged either way: there is still no Up/Down control, so two extensions touching the same header still fight -- just predictably now, in filename order, rather than at random.","v":"extensions_api.cpp:400 `QDir(dir).entryInfoList({ \"*.js\" }, QDir::Files, QDir::Name)` in loadAll() -- deterministic alphabetical load/registration order (new since the prior audit's 'no sort flag' finding); extensions_api.cpp:683 `for (QJSValue &handler : m_onRequestHandlers)` -- handlers still fire in that registration order with no reorder API or persisted override.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent, but corrected a stale claim -- loadAll() now sorts extension load order with QDir::Name (extensions_api.cpp:400), so invocation order is deterministic alphabetical, not arbitrary as the prior 'why' text implied. Gap text updated to say composition order is fixed-but-predictable rather than fixed-and-random; still no user-facing reorder control. No code change this pass."},{"a":"extender","f":"[B26] Extensions > Installed tab: Add… dialog (choose extension type, file, output/error destination)","s":"stub","i":"high","e":"days","g":"No file picker, no arbitrary local-file install, no type selection, no output/error destination. Only curated-catalog ids can be installed, and only over the API.","w":"Re-verified, held at stub. control_server.cpp's marketplace/install handler (moved 5376-5422 -> 6427ff) is unchanged in shape -- id is still the only input. marketplace.cpp:113-117's safeScriptFileName-derived-from-catalog-id evidence checked line-for-line and stands exactly as cited, no drift. Still no file picker, no arbitrary local-file install, no type selection, no output/error destination -- only curated-catalog ids, only over the API.","v":"control_server.cpp:6427 `if (path == \"/api/marketplace/install\") { ... const QString id = bodyJson.value(\"id\").toString();` (line drift from 5376-5422) -- the only input is a catalog id; marketplace.cpp:113-117 `const QString fileName = safeScriptFileName(entry.id); if (fileName.isEmpty()) { r.error = ...` -- the filename is derived from the catalog, never supplied by the user (unchanged, no drift).","o":"stub","r":"Wave 0 register-accuracy audit: held at stub. Line drift on the install handler (5376-5422 -> 6427ff); marketplace.cpp:113-117 citation unchanged and re-verified exact. No code change this pass."},{"a":"extender","f":"[B27] Extension settings: folder location, reload-on-startup behaviour, auto-update installed extensions","s":"stub","i":"medium","e":"hours","g":"No dedicated extension settings page. Cannot relocate the folder, cannot disable loading at startup, no auto-update setting. An 'Auto-reload (dev)' toggle now exists inline in the Extensions card, but it controls live file-watch reload during development, not reload-on-startup or auto-update -- it doesn't address what this item asks for.","w":"CONFIRMED at stub, with one real addition noted so the register isn't stale: an 'Auto-reload (dev)' checkbox now sits in the Extensions card (ui-v2/app.jsx ~1327), wiring a genuine settings toggle -- but it controls live file-watch reload during development, not the 'reload-on-startup' or 'auto-update installed extensions' behaviours this item specifically asks about, so it doesn't close the gap. extensionsDir() (moved 94-97 -> 352) is still a hard-coded QStandardPaths expression with no setter; loadAll() (moved :89 -> two call sites, :276 constructor and :390 setExtensionEnabled) still runs unconditionally with no startup-disable option; the path is still displayed read-only in ui-v2/app.jsx (Folder row, now :1340, was :460).","v":"extensions_api.cpp:352 `QString ExtensionsApi::extensionsDir() const { return QStandardPaths::writableLocation(QStandardPaths::AppDataLocation) + \"/extensions\"; }` (line drift from 94-97); extensions_api.cpp:276 and :390 `loadAll();` (constructor and setExtensionEnabled, drift from :89) run unconditionally with no startup-disable option; ui-v2/app.jsx:1340 `<Row label=\"Folder\" value={b.extensionsDir} copyable />` (drift from :460) still read-only; the new `Auto-reload (dev)` checkbox sits alongside it (~:1327) but is a dev-mode file-watch toggle, not a startup/auto-update setting.","o":"stub","r":"Wave 0 register-accuracy audit: held at stub. Noted a real but non-closing addition -- an Auto-reload (dev) toggle now exists in the Extensions card, but it's a file-watch setting, not the reload-on-startup/auto-update this item asks about. Line drift refreshed throughout. No code change this pass."},{"a":"extender","f":"[B28] BApp Store: browse installable extensions inside the tool, one-click install","s":"present","i":"high","e":"days","g":"None outstanding for this item's scope (browse + one-click install). BApp Store: search box/category filtering (item [B29]), ratings/last-updated sort (item [B30]), version-compatibility gating (item [B31]), and Pro-only gating (item [B32]) are tracked as separate, distinct roadmap items -- not part of this row's bar.","w":"Re-confirmed 2026-08-11 against live source, and updated for the 2026-08-10 Extender/BApp-store wave (c28f16a): the in-app Marketplace (ui-v2/app.jsx:223-385) is mounted in SettingsTab (app.jsx:639), fetches the merged catalog (NL.actions.marketplaceCatalog -> control_server.cpp:5354), renders per-extension cards with name/version/summary/categories/sha256, and now also a per-item DETAILS panel (author/full sha256/permissions/docs link/raw-source download/prefilled bug-report link). The two-step consent gate is fully wired: first install call sends confirmMutating:false, the server refuses traffic-mutating extensions with needsConfirmation:true (control_server.cpp:5455), and the UI shows the consent panel (app.jsx:315-340) built from permissions read out of the DOWNLOADED+verified bytes. Catalog now holds 14 entries (extensions/marketplace.json), not the 3 present at the original audit. With sha256 pinning + bytes-derived consent this arguably exceeds Burp's BApp store, but is graded 'present' (not 'exceeds') pending the search/ratings/version-gating items above.","v":"ui-v2/app.jsx:223-385 Marketplace component + :639 mount; control_server.cpp:5354 /catalog, :5418 /install (needsConfirmation :5455), :5467 /uninstall; extensions/marketplace.json = 14 ids; c28f16a search input + category chips + per-item DETAILS panel","o":"present","r":"Wave 0 register-accuracy audit: gap/evidence text was stale (still described the pre-c28f16a 3-entry catalog with no search/detail panel). Refreshed to match the live 14-entry catalog, search/category filter, and per-item DETAILS panel; re-verified against source. State unchanged (present)."},{"a":"extender","f":"[B29] BApp Store: search box and category filtering","s":"present","i":"low","e":"hours","g":"None -- the in-app Marketplace (ui-v2/app.jsx) now has the same filter/category-chip model as the published catalog site: a free-text search over name/summary/author/categories, and clickable category chips derived from the live catalog, both applied client-side before the item list renders.","w":"Closed 2026-08-10: ported the filter/chip logic from docs/marketplace/index.html's categories()/filtered() into the Marketplace React component as a useMemo-derived categories list and visibleItems array, with a search <input> and clickable chip row above the item list. No backend change -- all fields were already in the fetched catalog response.","v":"ui-v2/app.jsx:342 state.items.map with no predicate + no <input> in the component; docs/marketplace/index.html:46 search input, :91-113 categories()/filtered(), :183-190 sort handlers","o":"partial","r":"Extender/BApp-store batch: in-app search + category chips close #131."},{"a":"extender","f":"[B30] BApp Store: ratings/popularity, 'Last updated' column and sorting","s":"partial","i":"low","e":"weeks","g":"Two halves. LAST-UPDATED + SORTING now exist on the website store: catalog entries carry a per-entry 'updated' field (extensions/marketplace.json, e.g. dom_taint '2026-06-09') and docs/marketplace/index.html sorts by it (:107-111, sort-updated button). RATINGS/POPULARITY/installs remain absent everywhere with no backend to collect them — CatalogEntry (marketplace_logic.hpp:64-77) has no rating/ins","w":"Reclassified absent -> partial (2026-08-02): independent triage + adversarial-verify agreed; cited files re-confirmed to exist. See PARITY-BACKLOG.md.","v":"marketplace_logic.hpp:64-81 CatalogEntry has no rating/installs/updated member (id/name/summary/version/author/categories/url/sha256/hooks/declaredPermissions/minVersion only); marketplace_logic.cpp:75 only parses the catalog-level `updated` (Catalog::updated) via str(root,\"updated\",32), never a per-entry one; extensions/marketplace.json:24 dom_taint's own per-entry \"updated\":\"2026-06-09\" is present in the source JSON but dropped by the parser; docs/marketplace/index.html:57 sort-updated button, :114 `b.updated` compare.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B31] BApp Store: version-compatibility gating ('requires a later version')","s":"present","i":"medium","e":"hours","g":"RESOLVED: a catalog entry may declare minVersion; parseCatalog reads it, isVersionCompatible + merge(catalog,...,currentVersion) flag an entry needing a newer build as {compatible:false, incompatReason}, surfaced in the /api/marketplace/catalog JSON (including the raw minVersion) with NULLOCK_VERSION baked into the Control target. The in-app Marketplace (ui-v2/app.jsx) now reads compatible/incompatReason/minVersion: an incompatible entry gets a red 'incompatible' badge (title = the reason) and its Install/Update button is disabled with the same reason as its tooltip; the detail panel shows the 'Requires Nullock >= X' line, styled as an error when gated. Original gap (nothing prevented installing an extension written against a different API generation) is closed end to end.","w":"CONFIRMED both halves live. Backend (007b2b9): grep 'minVersion|compatib|incompatReason' across marketplace_logic.{hpp,cpp} + control_server.cpp now hits the full gate (isVersionCompatible, merge(...,currentVersion), the three new /api/marketplace/catalog fields). Frontend (this wave): prior to this change, grep of ui-v2/*.jsx for 'compatible|incompatReason' returned zero hits -- the wire fields existed but nothing read them, so an incompatible entry rendered identically to a normal one and Install would fail only after the click. Now Marketplace() in ui-v2/app.jsx reads x.compatible on every catalog row (badge + disabled Install/Update) and detail.compatible/minVersion in the detail panel.","v":"Src/Core/Networking/marketplace_logic.cpp:102 e.minVersion parsed; :305-311 isVersionCompatible (semver compare, empty either side = compatible); :336-338 merge() sets m.compatible=false + incompatReason = 'requires Nullock >= ' + e.minVersion. Src/BackEnd/Control/control_server.cpp:5964-5968 /api/marketplace/catalog emits minVersion/compatible/incompatReason per entry. ui-v2/app.jsx: Install/Update Btn now passes disabled={x.compatible === false} + a title (the two Btn blocks right after stateBadge/badge('modifies traffic')); an 'incompatible' badge renders next to stateBadge when x.compatible === false; the detail panel adds a 'Requires Nullock >= {minVersion}' line (error-colored when compatible === false).","o":"present","r":"Marketplace UI wave: greys/disables Install and Update on a version-incompatible catalog entry (red 'incompatible' badge + disabled-button tooltip + a 'Requires Nullock >= X' line in the detail panel), closing the frontend half of [B31] left open by 007b2b9's backend gate."},{"a":"extender","f":"[B32] BApp Store: 'Pro' gating — Pro-only BApps flagged and blocked in Community","s":"absent","i":"cosmetic","e":"hours","g":"Not applicable. Arguably an advantage: the Pro-only BApps a Community user cannot run have no analogue here.","w":"CONFIRMED, held not-applicable/absent. CatalogEntry (Src/Core/Networking/marketplace_logic.hpp, now :64-81, gained a minVersion semver-gate field since the prior pass but still no tier/licence field) and a fresh grep of Src/Core/APIs/ExtensionsAPI plus the marketplace TUs for licence/tier/pro confirm no gating concept exists anywhere near extension or marketplace code. Correctly filed as not-applicable bookkeeping rather than a defect -- Nullock is single-tier.","v":"marketplace_logic.hpp:64-81 CatalogEntry (gained a `minVersion` semver-gate field since the prior pass, still no tier/licence field); no licence check appears in Src/Core/APIs/ExtensionsAPI or the marketplace TUs (fresh grep).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent/not-applicable. CatalogEntry grew a minVersion field (unrelated to licensing) since the prior pass; still no tier/licence concept anywhere. No code change this pass."},{"a":"extender","f":"[B33] BApp Store: update notification for installed extensions (available-updates indicator, Reinstall to update)","s":"present","i":"medium","e":"days","g":"None user-facing. All 14 shipped extensions now carry a `// nullock:version` header matching their catalog entry, so the existing merge/badge/Update-button chain (previously dead code -- every install merged as plain Installed) is live: a future catalog version bump renders the update badge, and clicking Update calls the same verified marketplaceInstall() reinstall path used for a fresh install. The one remaining nuance: the separate one-shot install-builtins onboarding action still copies extensions/*.js unconditionally with no version check -- harmless (it always writes the current bundled bytes) but not itself version-aware.","w":"Closed the sole blocking defect this item's own prior wave identified: parseInstalledVersion()/UpdateLogic::compareSemver()/the ui-v2 update badge and Update button were all already correct, but `grep -n 'nullock:version' extensions/*.js` returned zero matches, so every installed extension merged as plain Installed and the whole path was dead. Added a `// nullock:version X.Y.Z` header comment to each of the 14 shipped extensions/*.js, matching that file's own catalog-declared version exactly (dom_taint 0.2.0, the other 13 at 0.1.0), then ran scripts/marketplace_sync.sh (regenerates the sha256 the header edit changed) and scripts/marketplace_site.py (regenerates the 14 published detail pages) so the manifest and site stay generated-not-hand-edited, per that script's own stated purpose. No C++ touched -- data-file-only change to already-tested machinery, so no build risk.","v":"extensions/*.js headers, e.g. aws_sigv4.js:4 `// nullock:version 0.1.0`, dom_taint.js:3 `// nullock:version 0.2.0`; marketplace_logic.cpp:298-303 parseInstalledVersion regex matches the added lines; marketplace_logic.cpp:328-332 merge() now reaches the UpdateAvailable branch once a catalog bump makes compareSemver negative; ui-v2/app.jsx:575-593 badge + Update button -> doInstall(id) -> NL.actions.marketplaceInstall (already wired, previously unreachable in practice); `bash scripts/marketplace_sync.sh --check` and `python3 scripts/marketplace_site.py --check` both green after regeneration.","o":"partial","r":"[B33] partial -> present: all 14 shipped extensions now emit the // nullock:version directive, lighting up the already-built update-available badge + reinstall-to-update flow end to end."},{"a":"extender","f":"[B34] Extension resource control — a runaway extension is killable via Unload","s":"absent","i":"high","e":"days","g":"No execution timeout, no interrupt, no per-extension kill, no unload. A runaway script freezes the main event loop — every proxied request, the UI, and the very endpoints you would use to reload or uninstall it.","w":"CONFIRMED. app.cpp still constructs both ExtensionsApi (now line 752, was 683) and ControlServer (now line 1299, was 974) on the main thread with no moveToThread anywhere in the file (fresh grep, 0 hits). extensions_api.cpp's BlockingQueuedConnection calls (now :642 and :662, was :300-302) are unchanged -- a runaway onRequest/onResponse handler still blocks the calling proxy thread AND, because the JS engine itself lives on the main/GUI thread, the whole app with it. No execution timeout, interrupt, per-extension kill, or Unload-while-running exists.","v":"Src/App/app.cpp:752 `Nullock::Core::ExtensionsApi extensions;` (drift from 683) and app.cpp:1299 `Nullock::Control::ControlServer controlServer(wiring);` (drift from 974) -- both on the main thread, no moveToThread in the file (fresh grep, 0 hits); extensions_api.cpp:642,662 `QMetaObject::invokeMethod(this, \"doMutateRequest\"/\"doMutateResponse\", Qt::BlockingQueuedConnection, ...)` (drift from 300-302).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Line drift on all three citations (683->752, 974->1299, 300-302->642/662); confirmed zero moveToThread calls in app.cpp. No code change this pass."},{"a":"extender","f":"[B35] AI extensions (api.ai() prompts, per-extension AI credit accounting, 'Use AI' toggle)","s":"absent","i":"low","e":"weeks","g":"Absent. Newest Burp axis; nothing comparable exists.","w":"CONFIRMED. Re-checked the now much larger bridge surface (extensions_api.hpp:296-436, replacing the stale 164-185 pointer that covered only 4 methods) end to end, plus a fresh case-insensitive grep for ai(/aiPrompt/api.ai across Src/Core/APIs/ExtensionsAPI -- zero hits either way. No AI surface of any kind exists for extensions, even though the backend gained its own AI surface elsewhere (payload-mutation via local Ollama, /api/payloads/generate, wired into the PAYLOADS tab per UI-NAVIGABILITY.md) -- that capability is tool-driven, not extension-invocable.","v":"extensions_api.hpp:296-436 -- complete JS-facing surface (drift from the stale 164-185 citation), no ai()/prompt method; fresh `grep -rnia 'ai\\(|aiPrompt|api\\.ai' Src/Core/APIs/ExtensionsAPI` -> 0 hits.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-checked the grown bridge surface and confirmed zero ai()/prompt hits; noted the backend's own unrelated AI feature (/api/payloads/generate) isn't extension-invocable either. No code change this pass."},{"a":"extender","f":"[B36] Bambdas: HTTP history filter written as a code snippet","s":"absent","i":"medium","e":"weeks","g":"No user-written filter expressions. Filtering is limited to the predicates the UI exposes.","w":"CONFIRMED. Fresh case-insensitive grep for bambda across Src/, ui-v2/ and extensions/ -- 0 hits, unchanged. ui-v2/proxy.jsx's history filters are still fixed controls; line positions drifted with the file's growth (host filter/search/deepSearch toggle now sit inside a much larger FilterBar after the #299 annotation and other additions) but remain fixed-field UI predicates only, no expression language.","v":"`grep -rnia bambda Src/ ui-v2/ extensions/` -> 0, unchanged; ui-v2/proxy.jsx's FilterBar (now :484-...) exposes only fixed controls -- host filter, free-text search, deepSearch toggle -- line positions drifted with the file's growth (the #299 annotation layer and other additions), unchanged in kind.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Fresh bambda grep still 0; FilterBar line positions refreshed (drifted with file growth), still fixed-field predicates only. No code change this pass."},{"a":"extender","f":"[B37] Bambdas: custom columns in the HTTP history","s":"absent","i":"medium","e":"weeks","g":"No user-computed column.","w":"CONFIRMED. customColumn/addColumn still 0 hits repo-wide. The history table gained a 12th column since the prior citation (was a fixed 11-column table, colSpan={11}; now 12, colSpan={12}, header Host/Method/Status/.../IP/Captured at proxy.jsx:404-432) plus the #299 per-row highlight applied as an inline boxShadow rather than a column -- still zero user-computed columns of any kind.","v":"`grep -rnia 'customColumn|addColumn' Src/ ui-v2/` -> 0 hits, unchanged; ui-v2/proxy.jsx's HistoryTable header (now :404-432) grew a 12th column since the prior citation (was `<td colSpan={11}`, now `<td colSpan={12}`) plus a #299 per-row highlight applied as an inline boxShadow tint (:439) rather than a column -- still zero user-computed columns of any kind.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. customColumn/addColumn grep still 0; history table grew from 11 to 12 fixed columns (colSpan drift 11->12), still no user-computed column mechanism. No code change this pass."},{"a":"extender","f":"[B38] Bambdas: highlight and annotate — colorize matching rows and auto-comment them","s":"partial","i":"high","e":"days","g":"The 'auto' half is still absent -- there is no bambda-style expression engine, so no rule can auto-colorize or auto-comment rows that match a pattern. But the manual half of this ask now exists: a per-row highlight-colour + free-text comment layer (#299) lets a user flag and annotate history rows by hand, client-side, persisted to localStorage. Neither an extension nor a user-written rule can drive it -- every flag is a manual right-click action, one row at a time -- so bulk/scripted triage across a large history still has no equivalent.","w":"UPGRADED one notch from the prior 'no row highlighting or commenting at all, neither user-scripted nor extension-driven' finding, which is now stale. I re-ran the same highlight grep the prior audit used and it still returns nothing bambda-shaped (Src/App/app.qml:306 highlightFollowsCurrentItem and a payload-preview CSS comment, both irrelevant) -- but ui-v2/proxy.jsx has since grown a real per-row annotation feature (#299): ANNOTATION_COLORS + setRowColor/setRowComment/clearRowAnnotation (:3179-3199), a right-click context-menu Highlight swatch row and an Add/Edit Comment prompt (:3482-3520), an ANNOTATED filter chip (:593), and a per-row inline boxShadow tint in the history table (:439) driven by the stored colour. I confirmed by hand that it is purely manual -- there is no matcher/rule/expression input anywhere in the feature, only a per-row click -- so it satisfies the 'colorize and comment' outcome one row at a time but not the 'auto' / rule-matching half the Bambda ask is actually about. Grading this partial rather than leaving it absent reflects that real user-facing outcome without overclaiming the scripted half, which is genuinely still missing.","v":"ui-v2/proxy.jsx:66 (feature marker comment), :3179-3199 (ANNOTATION_COLORS + setRowColor/setRowComment/clearRowAnnotation, localStorage-persisted), :3482-3520 (right-click Highlight swatches + Add/Edit Comment prompt), :593 (ANNOTATED filter chip), :439 (per-row inline boxShadow tint driven by the stored colour) -- all manual, per-row, no expression/matcher input anywhere in the feature (confirmed by reading the full block); `grep -rnia bambda Src/ ui-v2/ extensions/` still 0 hits, so the rule-driven/auto half remains completely absent.","o":"partial","r":"Wave 0 register-accuracy audit: UPGRADED absent -> partial. Found the #299 per-row highlight-colour + comment layer (ui-v2/proxy.jsx, added since this item was last audited) genuinely delivers the manual half of this ask (colorize + comment a row); confirmed by reading the full feature that it is strictly manual/per-row with no matcher or rule input, so the scripted/auto half this item is really about (Bambda-style rule-driven highlighting) remains absent. Gap/evidence/why rewritten to reflect the split honestly rather than either overclaiming or leaving a stale absent grade. No code change this pass -- this is a register correction only."},{"a":"extender","f":"[B39] Bambdas in other tables — Organizer, Logger, Intruder results, WebSockets history, Sitemap","s":"absent","i":"low","e":"weeks","g":"Absent, downstream of having no expression concept.","w":"CONFIRMED, downstream of B36/B38. Fresh grep bambda=0 repo-wide. Note the one exception is now B38 (highlight/annotate on Proxy history), which moved to partial via a manual, non-bambda feature -- but that manual pattern doesn't extend to Organizer/Logger/Intruder-results/WebSockets/Sitemap tables (none of them carry an equivalent per-row annotation layer), so this item's 'downstream of no expression engine, applies nowhere' framing still holds for every table it names.","v":"`grep -rnia bambda Src/ ui-v2/ extensions/` → 0 hits","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Cross-referenced B38's upgrade to partial (a manual, non-bambda annotation layer, Proxy history only) -- confirmed it does not extend to any of the tables this item names. No code change this pass."},{"a":"extender","f":"[B40] Bambda editor: in-place code editor with templates, autocomplete, inline errors; save/load; library repo","s":"absent","i":"low","e":"weeks","g":"Absent.","w":"CONFIRMED. bambda=0 fresh grep. ui-v2/vendor still carries only babel.min.js, react.development.js and react-dom.development.js (checked the directory listing directly) -- no monaco/codemirror or any embeddable code-editor component exists to build a Bambda editor on.","v":"`grep -rnia bambda Src/ ui-v2/` → 0 hits; no monaco/codemirror/snippet module in ui-v2 outside vendor's React+Babel bundle","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-checked ui-v2/vendor's contents directly (babel + react/react-dom only) and re-grepped for monaco/codemirror (0 hits). No code change this pass."},{"a":"extender","f":"[B41] Native GUI surface for extension management (Burp's Extensions tab in the desktop app)","s":"stub","i":"medium","e":"weeks","g":"The named, CMake-listed 'Extensions Hub' renders a blank white rectangle backed by two empty source files. All real extension UI is one card inside SettingsTab in the browser front end — and it still shows no grants, no per-extension enable, no remove, and no marketplace.","w":"CONFIRMED, and re-verified byte-for-byte again as the audit style demands for this item specifically: extensions_hub.qml is still exactly the 8-line blank Rectangle, extensions_hub_model.cpp/.hpp are still 0 bytes each -- and two MORE identical 8-line blank-Rectangle stubs have appeared since (Components/extensions_console.qml, Components/extensions.qml), neither referenced anywhere (0 hits grepping app.qml and CMakeLists.txt for all three names). All real extension UI is still the one ui-v2/app.jsx Settings card (grown since: :1319-1391, was :456-477 -- now with per-extension enable checkboxes and capability badges alongside the folder/loaded/log-tail/reload it had before) -- still no grants UI beyond a read-only per-script badge, no remove button, and the marketplace lives in its own separate Card, not this one.","v":"Src/FrontEnd/GUI/ExtensionsHub/extensions_hub.qml complete contents, unchanged: `import QtQuick` / `Rectangle { id: extensionsHub; width: 400; height: 300; color: \"#ffffff\" }`; two newer identical stubs, Components/extensions_console.qml and Components/extensions.qml, also unreferenced; `ls -la` -> extensions_hub_model.cpp/.hpp both still 0 bytes; ui-v2/app.jsx:1319-1391 (drift from 456-477) is the entire real UI -- now with per-extension Loaded checkboxes and modifies-traffic/observe-only badges alongside the Folder row, 30-line log tail, and Reload button it already had.","o":"stub","r":"Wave 0 register-accuracy audit: held at stub. Same widened-stub finding as B11 (two new orphaned blank-Rectangle QML files); ui-v2/app.jsx real-UI citation refreshed (456-477 -> 1319-1391) to reflect its since-grown per-extension checkboxes/badges. No code change this pass."},{"a":"sequencer","f":"Live capture option: \"Ignore token length differences\" (tolerate variable-length tokens)","s":"present","i":"low","e":"hours","g":"The core analysis (Shannon, char-class, hamming, LCS, sequential) already runs over the full variable-length list -- only the positional and bit-level cross-sample tests require a fixed modal width and silently drop off-width tokens (sequencer_logic.cpp:262 gate `if (modeW<8 || modeC<kDeepMinN || modeC*2<tokens.size()) return r;`), surfacing a bare `applicable:false` at :546 that is indistinguisha","w":"Reclassified stub -> partial (2026-08-02): triage + adversarial-verify agreed; keyed by stable roadmap id, area-guarded. See PARITY-BACKLOG.md.","v":"sequencer_logic.cpp:257-268 (modal-width selection + drop gate), :262 (silent early return -> applicable=false), :544-556 (caller emits only applicable + fields, no dropped count / reason); core tests at :433-539 already consume the raw variable-length list.","o":"present","r":"Closed 2026-08-12: positionalEntropy now ALWAYS reports modalWidth/atModalWidth/offWidth and, when it can't run, a skipReason (length-variance / too-few-tokens / too-few-at-width / tokens-too-short) -- so the previously-indistinguishable bare applicable:false is now diagnosable, and when the cross-sample test DOES run the count of excluded off-width tokens is surfaced instead of silently dropped. The core analysis already tolerated variable lengths (Shannon/char-class/hamming/LCS/sequential run over the raw list); this closes the remaining signal gap. Gating/applicable outcome unchanged. Unit- + mutation-tested (zeroing offWidth fails the counted cases)."},{"a":"sequencer","f":"Manual load: paste newline-delimited tokens or load from file, then \"Analyze now\"","s":"present","i":"high","e":"days","g":"None for the manual-load workflow itself: SequencerTab's textarea accepts newline-delimited pasted tokens, a LOAD FILE button reads a local .txt/.csv/.log via FileReader, a PASTE FROM CLIPBOARD button uses navigator.clipboard.readText() where available (feature-detected, fails closed with a message otherwise), and ANALYZE NOW POSTs the parsed token array to /api/sequencer/analyze. No stdin '-' equivalent in a browser context (not applicable to a GUI) and no bash-only path required anymore.","w":"Closed 2026-08-10: SequencerTab (ui-v2/app.jsx) manual-load box, wired to the pre-existing analyze endpoint.","v":"ui-v2/app.jsx SequencerTab: textarea + tokens useMemo (newline-split/trim/filter), loadFile() FileReader.readAsText, pasteFromClipboard() navigator.clipboard.readText, analyze() -> NL.actions.sequencerAnalyze(tokens) -> POST /api/sequencer/analyze","o":"present","r":"Sequencer batch: manual-load paste/file/clipboard + Analyze now, closes the pure-GUI dimension of this gap."},{"a":"sequencer","f":"Manual load sample summary (token count, shortest / longest token length) shown before analysis","s":"present","i":"low","e":"hours","g":"None: a client-side sequencerSampleSummary(tokens) helper computes token count, shortest length, longest length, and mean length from the pasted/loaded corpus and renders it live under the manual-load box BEFORE the ANALYZE NOW call -- addressing the prior gap that a summary only existed after analysis and only carried mean length (min/max were computed server-side and discarded).","w":"Closed 2026-08-10: pure client-side summary, computed and shown pre-analysis, restoring shortest/longest.","v":"ui-v2/app.jsx sequencerSampleSummary(tokens) pure helper + SequencerTab's summary useMemo/render block, shown above the ANALYZE NOW button","o":"present","r":"Sequencer batch: pre-analysis client-side sample summary (n / shortest / longest / mean), closes the reachability gap."},{"a":"sequencer","f":"Analysis Summary: overall result (entropy estimate in bits) with a stated confidence level and \"amount of data analyzed\"","s":"partial","i":"medium","e":"weeks","g":"The confidence level and the \"amount of data analyzed\" statement are now DONE: result.summary carries verdict + score + a confidence (low/medium/high driven by sample adequacy) + significanceLevel + effectiveBitsPerToken + tokensAnalyzed/avgTokenLength/decodedBits/meetsRecommendedSample/meetsFipsSample + a prose dataAnalyzed line tying n and the decoded-bit count to the estimate. Still partial for the two remaining pieces: no per-significance-level entropy CURVE (a table of the estimate/verdict across 0.1%/1%/5%), and the score deductions are still hand-tuned with no per-flag attribution in the output (three independent flags can drive a 128-bit CSPRNG token to \"predictable\" without saying which cost what).","w":"Confidence + data-analyzed implemented in analyzeTokens (result.summary) and mutation-proven: the confidence tiers are locked by Tests/sequencer/sequencer_test.cpp (10/20 tokens -> low, 150x8-hex -> medium, 200x32-hex -> high; M1 defeating the medium tier and M2 dropping the too-few gate each fail only their targeted case). Confidence is tied to SAMPLE ADEQUACY (SampleSizeGuidance), the honest limiter, not to the verdict. Held at partial only for the entropy-curve + per-flag-attribution items above.","v":"sequencer_logic.cpp:1287-1310 analyzeTokens summary block: `summary[\"confidence\"]=...; summary[\"significanceLevel\"]=alpha; summary[\"effectiveBitsPerToken\"]=effectiveBits; summary[\"tokensAnalyzed\"]=tokens.size(); summary[\"decodedBits\"]=double(bit.bits); summary[\"dataAnalyzed\"]=...` (tiers: tooFew||!estimable -> low, !fipsBitsMet -> medium, else high). Schema in sequencer.hpp:126-148. Verified: Tests/sequencer/sequencer_test.cpp confidence-tier cases at :785-804 (10/20 tokens -> low, 150x8-hex -> medium, 200x32-hex -> high).","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified sequencer_logic.cpp's analyzeTokens summary block (function drifted to :966, summary assembly now at 1287-1310) -- confidence/significanceLevel/effectiveBitsPerToken/tokensAnalyzed/avgTokenLength/decodedBits/meetsRecommendedSample/meetsFipsSample/dataAnalyzed are all present and tier-gated exactly as described (tooFew||!estimable->low, !fipsBitsMet->medium, else high). Confirmed against Tests/sequencer/sequencer_test.cpp:785-804 (10/20 tok->low, 150x8-hex->medium, 200x32-hex->high) -- tiers unchanged. No per-significance-level entropy curve and no per-flag score attribution exist anywhere in the file (grepped for 'curve'/'attribution'/'perFlag': 0 hits). Claim holds; evidence line numbers refreshed."},{"a":"sequencer","f":"Effective entropy (bits assigned per character position from that position's observed character-set size, summed across positions)","s":"present","i":"medium","e":"days","g":"None -- a per-position effective-entropy estimate now sits alongside the global one. positionalEffectiveBits() sums log2(observed alphabet size) across the modal-width cohort's columns, so a token that is hex in columns 0-7 (4 bits each) and drawn from a reduced alphabet in 8-31 is credited its TRUE region-by-region keyspace, not the blended global average. Reported as shannon.perPositionEffectiveBits.","w":"Closed 2026-08-24: added the pure positionalEffectiveBits(tokens) in sequencer_logic.cpp (per-column distinct-char count -> log2 -> sum), emitted as shannon.perPositionEffectiveBits in analyzeTokens' JSON. It is a lower bound that tightens with samples (conservative for a keyspace figure). Mutation-proven: dropping the log2 or using a global alphabet instead of per-column both fail the structured-corpus assertions.","v":"sequencer_logic.cpp positionalEffectiveBits(): modal-width cohort, per-column `QSet<QChar>` distinct count, `bits += std::log2(seen.size())` (1-symbol column adds 0); emitted at the shannon block `shannon[\"perPositionEffectiveBits\"] = positionalEffectiveBits(tokens);`. Tests: sequencer_test.cpp -- a hex-prefix + reduced-alphabet-suffix corpus scores ~56 bits (true keyspace) and BELOW the global rate*length estimate, while a uniform 32-hex corpus scores ~128 and agrees with the global estimate.","o":"present","r":"Wave 2: backfilled audited_state + reconciled -- the feat commit (a878a0e) flipped state/gap/why/evidence but never added the audited-page's reconciled block, so this closed item was invisible in the roadmap page's \"reconciled since audit\" list. No code change."},{"a":"sequencer","f":"Character-level test: Character count analysis (per-position chi-square on the distribution of characters, with a p-value per position)","s":"present","i":"medium","e":"days","g":"None -- positionalCharChiSquare() now runs a real per-column chi-square of the observed character distribution against a uniform distribution over that column's observed alphabet (dof = distinct-1), converts each column's statistic to a p-value via the exported chiSquareSurvival() (regularized upper incomplete gamma), and flags columns at a Bonferroni-corrected threshold (0.01/columns). Unlike the entropy-vs-sibling reference, this catches a generator biased UNIFORMLY across every column (each column fails against uniform on its own). Reported as positional.charChiSquare {columns, failures, minPValue, biased}.","w":"Closed 2026-08-24: added positionalCharChiSquare (modal-width cohort, per-column histogram -> chi-square-vs-uniform -> chiSquareSurvival p-value -> Bonferroni pass/fail) alongside the existing per-column entropy. chiSquareSurvival is exported and unit-tested against standard chi-square critical values (dof 1/3/10/15) on BOTH the series and continued-fraction branches. Mutation-proven: breaking either survival branch fails the critical-value table; removing the Bonferroni flags a clean corpus.","v":"sequencer_logic.cpp positionalCharChiSquare() + chiSquareSurvival(); emitted at `posObj[\"charChiSquare\"]`. Tests: sequencer_test.cpp -- chiSquareSurvival matches the chi-square table to <0.003; a corpus with one column biased ~75% toward 'a' FLAGS charChiSquare while a clean 32-hex corpus does not.","o":"present","r":"Wave 2: backfilled audited_state + reconciled -- the feat commit (9ba914e) flipped state/gap/why/evidence but never added the audited-page's reconciled block, so this closed item was invisible in the roadmap page's \"reconciled since audit\" list. No code change."},{"a":"sequencer","f":"Bit-level test: FIPS monobit test, evaluated at every bit position independently","s":"present","i":"medium","e":"days","g":"None -- bitLevelTests now runs a per-bit-position monobit over the modal decoded-byte-width cohort (iterating `per`, not the flattened `cat`): for each bit position it counts 1s across tokens and applies the erfc monobit p-value, with a Bonferroni-corrected threshold (0.01/positions) so the family-wise false-positive rate stays ~1% across all positions. A single stuck/biased bit that the aggregate monobit dilutes 1:(width*8) now fails independently and sets bitLevel.anyFail. Reported as bitLevel.perBitMonobit {positions, failures, minPValue, failed}.","w":"Closed 2026-08-24: kept the aggregate monobit and ADDED the per-position pass over the modal-width cohort. Bonferroni was essential -- a naive 0.01 over 256 positions false-positives ~2.5 times on random data (caught by a clean-corpus regression assertion + an existing strong-random test before commit). Mutation-proven: removing the Bonferroni correction reintroduces the clean-corpus false positive; disabling the threshold misses the stuck bit.","v":"sequencer_logic.cpp bitLevelTests() per-bit-position block: modal decoded-byte-width cohort, `const double alpha = 0.01 / double(positions)`, per-position `onesP` count -> `erfc(sObs/sqrt2)` -> `if (p < alpha) ++r.perBitFails`; wired into anyFail and emitted as bitLevel.perBitMonobit. Tests: sequencer_test.cpp -- a corpus with one always-1 nibble bit FLAGS perBitMonobit while the aggregate monobit passes (the dilution it catches); a clean 32-hex corpus does NOT flag.","o":"present","r":"Wave 2: backfilled audited_state + reconciled -- the feat commit (1de965a) flipped state/gap/why/evidence but never added the audited-page's reconciled block, so this closed item was invisible in the roadmap page's \"reconciled since audit\" list. No code change."},{"a":"sequencer","f":"Bit-level test: Correlation test (correlation between distinct bit positions, with significance adjusted for interdependence)","s":"present","i":"medium","e":"days","g":"None -- bitLevelTests now correlates EVERY PAIR of bit positions across the modal-width cohort (not just byte lag-1): for each pair it builds the 2x2 contingency table and computes chi-square (1 dof) = n*phi^2 -> p via chiSquareSurvival, flagging pairs at a Bonferroni-corrected threshold (0.01/pairs) -- the significance adjustment for testing every interdependent pair. A bit-3-vs-bit-47 truncated-LCG relationship (invisible to byte lag-1) is caught, and no junction pairs are involved (it iterates per-token bit columns, not the flattened stream). Reported as bitLevel.bitCorrelation {pairs, failures, minPValue, failed}, folded into anyFail.","w":"Closed 2026-08-24: added the all-pairs bit-position correlation (phi/chi-square per pair, Bonferroni over all pairs, capped at 1024 positions to bound O(positions^2*n)). The byte lag-1 serial correlation is kept as-is. Mutation-proven: disabling the flag misses a copied-bit pair; using a naive 0.01 (no Bonferroni) false-positives on a clean corpus across the ~8k pairs.","v":"sequencer_logic.cpp bitLevelTests() inter-bit-position correlation block: per-position bit columns over the cohort, 2x2 chi = num*num*N/den (num=both*N-a1*b1), p=chiSquareSurvival(chi,1), `if (p < 0.01/pairs) ++bitCorrFails`. Tests: sequencer_test.cpp -- forcing bit position 40 to equal bit 5 in every token FLAGS bitCorrelation; an independent-bit corpus does not.","o":"present","r":"Wave 2: backfilled audited_state + reconciled -- the feat commit (8502f0d) flipped state/gap/why/evidence but never added the audited-page's reconciled block, so this closed item was invisible in the roadmap page's \"reconciled since audit\" list. No code change."},{"a":"sequencer","f":"Token bit-conversion across encodings (map the token's character set to a bit sequence for the bit-level tests)","s":"present","i":"medium","e":"days","g":"CORRECTED: (a) an ODD-length hex corpus fails `(t.size() % 2) != 0`, falls through, and is silently decoded as BASE64 — the report then claims `\"scheme\":\"base64\"` for a hex corpus; (b) base32/base36/alphanumeric are silently relabelled base64 too; (c) the genuine total loss is any corpus containing a character outside `[A-Za-z0-9+/_-]` — which includes JWTs (`.`), and any decimal-with-separator or URL-encoded token: those report `applicable:false` and get ZERO bit-level analysis. Any single non-conforming token in the corpus kills the whole test via `break`.","w":"I re-read decodeCorpusBytes at :304-333 and the first pass's characterisation of the failure trigger is WRONG in a way that matters in both directions. `b64Re` is `^[A-Za-z0-9+/_-]+={0,2}$`, which MATCHES base32, base36 and alphanumeric session IDs — so those corpora are NOT lost, they are decoded (as base64) and DO get bit-tested. Conversely there are two silent-wrong paths the first pass missed.","v":"sequencer_logic.cpp:306-332: `static const QRegularExpression hexRe(\"^[0-9a-fA-F]+$\"); static const QRegularExpression b64Re(\"^[A-Za-z0-9+/_-]+={0,2}$\"); bool allHex = !tokens.isEmpty(); for (const QString &t : tokens) { if (t.isEmpty() || (t.size() % 2) != 0 || !hexRe.match(t).hasMatch()) { allHex = false; break; } } ... bool allB64 = !tokens.isEmpty(); for (const QString &t : tokens) { if (t.siz","o":"present","r":"Closed 2026-08-11: decodeCorpusBytes rewritten to pick the scheme by charset MAJORITY. Both silent-wrong paths fixed: (a) an odd-length hex corpus is now HEX (odd tokens left-padded to preserve the half-byte) instead of falling through and being decoded+labelled base64; (c) a single non-conforming token (a truncated sample, a JWT's '.') is now SKIPPED (with the count surfaced as bitLevel.skipped) instead of setting the whole corpus applicable:false and zeroing all bit-level analysis. A >=50% majority is required so a genuinely mixed corpus still reports not-applicable. Mutation-proven twice (revert-skip-to-fatal fails the (c) cases; count-even-hex-only fails the (a) case). Residual (documented, cosmetic): base32/base36/alphanumeric is decoded correctly but labelled base64 -- Qt has no base32 decoder, and Burp likewise doesn't distinguish it, so this stays at parity."},{"a":"sequencer","f":"Sequential / counter token detection (Burp infers this indirectly from low entropy; no dedicated test)","s":"exceeds","i":"medium","e":"hours","g":"Detects bare decimal/hex counters only. A prefixed counter (`sess_1001`), a suffixed one, a zero-padded-with-separator one, or a base64-wrapped one is reported `looksSequential:false, looksMonotonic:false`. Such corpora still tend to score \"predictable\" via the keyspace deduction, but the analyst is told the wrong reason — and a LONG prefixed counter (40-char prefix + 8-digit counter) clears `varLen`-based deductions too. Not an exceed over Burp: Burp's indirect low-entropy inference is encoding-agnostic and would still flag it.","w":"DOWNGRADED exceeds -> partial. The quoted code is verbatim correct, but the first pass never looked at what feeds it. `looksSequential` and `looksMonotonic` both go through `decodeNumeric` -> `parseToken`, which requires the ENTIRE token to match `^[0-9]+$` or `^(0[xX])?[0-9a-fA-F]+$`. `sess_1001`, `user-42`, `AAAAZg==` — the counter shapes that actually appear in the wild — all fail and are invis","v":"sequencer_logic.cpp:41-53 `static const QRegularExpression decRe(\"^[0-9]+$\"); static const QRegularExpression hexRe(\"^(0[xX])?[0-9a-fA-F]+$\"); ... if (decRe.match(t).hasMatch()) { out = t.toLongLong(&ok, 10); return ok; } if (hexRe.match(t).hasMatch()) { ... } return false;` — no affix stripping. Call sites pass the RAW list: :533 `const bool seq = looksSequential(tokens, delta);` and :534 `const ","o":"exceeds","r":"UPGRADED partial -> exceeds. The partial verdict was correct and its concrete reason (looksSequential/looksMonotonic route through parseToken, which rejects the whole token, so wrapped counters sess_1001/user-42 were false-negatives Burp's low-entropy inference still caught) is now FIXED: stripCommonNumericWrapper strips a shared non-numeric prefix/suffix (up to its last / from its first non-digit -- constant wrapper only, never a varying digit) before the counter tests. Prefixed/suffixed/zero-padded decimal & hex counters are now detected with their TRUE step; a bare stepped counter (100,200,300, all-digit suffix) keeps delta 100 (regression-locked); wrapped noise does not become a false counter (all mutation-proven). sequential.delta value is now locked too, not just the boolean. With the dedicated looksSequential/looksMonotonic/delta verdict -- which Burp has NO equivalent for -- now covering wrapped counters, Nullock exceeds Burp. Residual: base64-wrapped counters stay keyspace/entropy-flagged (predictable) not sequential-labelled, matching Burp's indirect approach."},{"a":"sequencer","f":"Structural / keyspace grading against a modern standard (Burp reports entropy bits but does not grade against NIST SP 800-63B)","s":"present","i":"low","e":"hours","g":"The grading is genuine but unlabelled: `effectiveBitsPerToken` is emitted, the 60/124 thresholds are not, the standard is not, and the score blends the keyspace verdict with six unrelated deductions so the user cannot recover \"this token is below the 128-bit target\" from the output. Add an explicit `keyspaceGrade` field and this becomes a true exceed.","w":"DOWNGRADED exceeds -> present. The code is verbatim as quoted and the capability is real and genuinely absent from Burp — but \"exceeds\" overstates it. There is no stated grade against a named standard anywhere in the OUTPUT: SP 800-63B appears only in a source comment at :583-585. The user receives an unlabelled 0-100 score in which the keyspace deduction is indistinguishable from the six other de","v":"sequencer_logic.cpp:1010 `shannon[\"effectiveBitsPerToken\"] = effectiveBits;`; score deductions at :1227-1237 (`if (effectiveBits < 60) score -= 55; else if (effectiveBits < 124) score -= 15;` ... `if (combinedBits < 2.0) score -= 25;` ... `if (lcs.size() > varLen / 2 && varLen > 8) score -= 30;`); the 128-bit target and NIST SP 800-63B are named only in a code comment at :1216-1218, not emitted in the JSON output -- no `keyspaceGrade` field exists.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"sequencer","f":"Session handling rules: named, ordered, individually enable/disable-able rules in a rules editor","s":"present","i":"high","e":"weeks","g":"GUI editor now ships: the SESSIONS tab (ui-v2/app.jsx SessionsTab) gains a Session handling rules section -- add/edit/delete a named rule with host+path glob, extract-from (header/cookie/JSON path/regex) + extract key + variable name, inject-into (header/cookie/body/URL query) + inject key + template, and a per-rule enable/disable checkbox, plus a live captured-variables readout with a Clear button. The bin/nullock session-rules CLI editor from the prior audit still exists too. Honest remainder: no persistence across restarts (tracked separately, see \"Cookie jar and session rules persist...\" -- state absent) and no manual drag-to-reorder control (rules apply in array/insertion order, matching how the engine evaluates them and the sibling Match & Replace RULES tab's own precedent of no reorder UI despite a ruleMove backend action existing unused).","w":"Closed 2026-08-12: /api/session-rules/set (whole-list replace) and /api/session-rules/clear-vars were fully wired in the backend and published on every snapshot poll (root[\"sessionRules\"]={rules,variables}, control_server.cpp:1587-1611) but had zero frontend callers -- confirmed by grep across ui-v2/*.jsx and real-data.js before this change. The new editor reads/writes that exact contract with no backend change.","v":"ui-v2/app.jsx SessionsTab Session-handling-rules section (sessionRuleUpsert/sessionRuleRemoveAt/sessionRuleToggle pure helpers + the editor form/list/variables readout); ui-v2/real-data.js sessionRulesSet/sessionRulesClearVars actions and NL.sessionRules snapshot field; field names (name/enabled/hostGlob/pathGlob/extractFrom/extractKey/variable/injectInto/injectKey/injectTemplate; variables as a flat string map) matched verbatim against control_server.cpp:1587-1611 (snapshot) and :3869-3895 (/api/session-rules/set, /clear-vars).","o":"present","r":"Sessions tab gains a Session handling rules editor (name/enable/host+path glob/extract/inject fields) wired to the previously-orphaned /api/session-rules/set + /clear-vars; closes the GUI-reachability gap."},{"a":"sequencer","f":"Rule scope — URL scope (all URLs / suite scope / custom include-exclude URL list)","s":"partial","i":"medium","e":"days","g":"A custom include/exclude URL list now exists per rule: SessionRule gains includeUrls/excludeUrls (JSON round-tripped via /api/session-rules), and matches() consults the pure SessionRulesLogic::urlScopeMatches (globs against host+path, query stripped; empty include => all; exclude beats include), so \"everything except /logout\" is expressible as include=[*], exclude=[*/logout*]. Still partial for the \"use suite scope\" checkbox and protocol/port matching (ui-v2 + scope wiring). Separately, the reverse problem remains: an UNCONFIGURABLE suite-scope gate is imposed upstream at proxy_server.cpp:1447 (`if (!isInScope(req.host)) return;`) BEFORE the session hooks, so an out-of-scope host gets no session handling regardless of a rule.","w":"Confirmed verbatim, both the globs and the anchoring. Held at partial. I add one finding: an implicit suite-scope gate DOES exist, but it is applied to the wrong thing and cannot be turned off (see item 22 of Group B and item 14 here).","v":"session_rules.hpp:49-50 `QString hostGlob = \"*\"; QString pathGlob = \"*\";`; session_rules.cpp:171-173 `return resolve(r.hostGlob).match(host).hasMatch() && resolve(r.pathGlob).match(stripQuery(path)).hasMatch() && SessionRulesLogic::urlScopeMatches(host, path, r.includeUrls, r.excludeUrls);`; session_rules_logic.cpp:17-24 globToRx loop (unchanged). Suite-scope gate now at proxy_server.cpp:1688 `if (!isUrlInScope(req.tls, req.host, req.port, req.path)) return;` (renamed from isInScope(host), now also protocol/port-aware, but still applied before the session hooks with no per-rule override).","o":"","r":"Wave 0 register-accuracy audit: held at partial. hostGlob/pathGlob struct fields drifted 45-46 -> 49-50 (unchanged content); matches() return drifted 65-66 -> 171-173, now a three-clause return with the previously-landed urlScopeMatches include/exclude check appended -- content matches the gap's own already-updated description verbatim. globToRx (session_rules_logic.cpp:12-25, loop body 17-23) is byte-identical, no drift in the cited lines. The upstream suite-scope gate moved from proxy_server.cpp:1447 `isInScope(req.host)` to :1688 `isUrlInScope(req.tls, req.host, req.port, req.path)` -- a real signature change (the scope engine grew protocol/port/advanced-rule matching via ProxyServer::isUrlInScope + setAdvancedScope), but the substance for THIS item is unchanged: it is still an unconditional early return applied before SessionManager::injectInto and SessionRules::applyToRequest, with no per-rule opt-out. Still no 'use suite scope' checkbox or protocol/port field on SessionRule itself. Claim holds; evidence refreshed."},{"a":"sequencer","f":"Rule action: \"Use cookies from the session handling cookie jar\"","s":"partial","i":"high","e":"days","g":"A global per-host boolean living in a different subsystem, not an orderable rule action: cannot be path-scoped, cannot be sequenced against other actions, cannot be restricted to named cookies. Two silent suppressors: (1) the host must be in scope — proxy_server.cpp:1447 returns before injection; (2) Repeater and Intruder never call applyRequestRules at all (grep for \"session\" in repeater.cpp and intruder.cpp: zero hits).","w":"Every cited line verified verbatim (the autoInject endpoint is at control_server.cpp:9489, not 9348 — minor drift, substance correct). Held at partial, and I am ADDING a second silent-failure gate the first pass missed: the scope early-return in applyRequestRules suppresses cookie injection entirely for out-of-scope hosts, before the injectInto call is ever reached.","v":"session_manager.cpp:110-119 `void SessionManager::injectInto(...) { if (req.host.isEmpty()) return; ... auto it = m_byHost.constFind(lowercaseHost(req.host)); if (it == m_byHost.constEnd()) return; if (!it->autoInject) return; use = it->cookies; }`. Toggle: session_manager.cpp:165-176 `setAutoInject`, endpoint control_server.cpp:10775 `if (path == \"/api/sessions/autoInject\") {`, UI ui-v2/app.jsx:7062-7064 the auto-inject checkbox in the Sessions panel. `grep SessionManager Src/Core/Networking/repeater.cpp Src/Core/Networking/intruder.cpp`: 0 hits -- the cookie jar still never reaches either tool.","o":"","r":"Wave 0 register-accuracy audit: held at partial (the cookie-jar-specific claim). injectInto/setAutoInject/endpoint/UI line numbers refreshed (93-103->110-119, 146-157->165-176, control_server.cpp 9489->10775, app.jsx ~190->7062). Silent suppressor (1), the scope early-return, moved 1447->1688 (see item #70/156) and still applies before injectInto. Silent suppressor (2) needed correcting, not just re-lining: the ORIGINAL 'grep session in repeater.cpp/intruder.cpp: zero hits' claim is now FALSE -- both files import session_rules.hpp and call m_sessionRules->applyToRequestBytes(..., ToolRepeater/ToolIntruder) (repeater.cpp:160-161, intruder.cpp:656-657 and :880-881), wired live via repeater.setSessionRules()/intruder.setSessionRules() in app.cpp:1108/1111. That is the SEPARATE SessionRules {{var}}-injection pipeline (item #72/159's mechanism, now scoped by a new per-rule `tools` bitmask), not this item's SessionManager cookie jar -- Repeater and Intruder still hold no SessionManager pointer at all (grep for SessionManager in both .hpp/.cpp: 0 hits), so 'use cookies from the session handling cookie jar' specifically remains Proxy-only. State holds at partial, but the supporting evidence for suppressor (2) needed retargeting to avoid citing a now-false grep result."},{"a":"sequencer","f":"Rule action: \"Set a specific cookie or parameter value\" (static or derived value)","s":"present","i":"medium","e":"hours","g":"A purely static rule (\"always set X-Debug: 1 on this host\") can never fire — line 143 bails until an unrelated extract rule has populated the host's bag. And once it can fire, a rule whose own variable was never captured injects the literal string `{{token}}` into the header, cookie, form body or query string instead of being skipped — a fail-open that corrupts the request and is invisible without a tracer.","w":"The static-rule-never-fires claim is CONFIRMED verbatim at :143. Held at partial — but I found a strictly worse companion bug the first pass missed: once ANY variable exists for the host, an unresolved `{{var}}` is injected VERBATIM rather than skipped, so the feature does not merely no-op, it puts literal template text on the wire.","v":"session_rules.cpp:141-143 verbatim: `vars = m_varsByHost.value(req.host); } if (rs.isEmpty() || vars.isEmpty()) return;`. The verbatim-injection path: :150-154 `const QString templ = r.injectTemplate.isEmpty() ? QString(\"{{%1}}\").arg(r.variable.isEmpty() ? r.injectKey : r.variable) : r.injectTemplate; const QString value = substitute(templ, vars); if (value.isEmpty()) continue;` combined with sess","o":"present","r":"Both silent-failure paths fixed. (1) Dropped the `|| vars.isEmpty()` bail in applyToRequest so a purely static rule (no {{var}}) injects regardless of the per-host bag. (2) Added the pure SessionRulesLogic::hasUnresolvedPlaceholder and skip any rule whose substituted value still holds an un-resolved {{name}} -- no more literal `{{token}}` on the wire. Unit-tested (10 cases) + 2 mutations; e2e vs a raw-socket mock captured the wire bytes proving `X-Static-Test: fixedvalue123` injects on an empty bag while a missing-var rule emits neither the header nor {{token}} garbage. ctest 99/99, probe_smoke 156/156."},{"a":"sequencer","f":"Macro item configuration: per-item custom parameter handling — derive a parameter value from a prior response (cookie / form field / custom rule), and update the final request's parameters from the macro response","s":"partial","i":"high","e":"days","g":"The extraction vocabulary is good and there IS no form-field extractor (only header/cookie/JSONPath/regex/status — no HTML form parser). Values thread forward between chain steps only; there is no \"final request\" whose parameters get updated, because the chain is attached to nothing — `ChainRunner::run` has exactly one caller (control_server.cpp:8994) and the chain's own HttpClient (chain_runner.cpp:52 `HttpClient client;`) means its responses never reach the cookie jar or the session-rules bag either.","w":"Struct verified verbatim (chain_runner.hpp:26-31). Endpoint line numbers in the first pass had drifted (~8831/8853 -> actually 8974/8994) but the substance holds. Held at partial: a user CAN accomplish \"derive a value from response 1 and apply it to request 2\" by making request 2 a chain step, which is a real if awkward version of this capability.","v":"chain_runner.hpp:27-32 verbatim: `struct Extract { QString var; enum From { Header, Cookie, Json, Regex, Status } from = Header; QString key; };`. extractOne implemented at chain_runner.cpp:20-47 covering all five. Substitution + CL repair at chain_runner.hpp:88-90; sanitization at :87 `QString sanitizeExtractedValue(const QString &v);`. Wiring: control_server.cpp:10210 `/api/chain/run` builds `steps` then :10254 `Nullock::Core::ChainRunner::run(steps, continueOnError)`. Second caller: session_rules.cpp:446 `SessionRules::runMacro` -> `Nullock::Core::ChainRunner::run(macro.steps, false)`, whose result is merged via `ingestVariables(macro.sessionHost, result.vars)` (:448) into the SessionRules variable bag that applyToRequest/applyToRequestBytes injects into Proxy, Repeater and Intruder traffic.","o":"","r":"Wave 0 register-accuracy audit: held at partial, WITH a correction to the 'why' field's central claim. Extract struct / extractOne / substitution helpers verified verbatim modulo a small line shift (26-31->27-32, extractOne 21-46->20-47). But 'ChainRunner::run has exactly one caller (control_server.cpp:8994)' is now factually wrong: SessionMacro (session_rules.hpp:93-101, landed in commit 88cbe99 -- see scanner-area item #94's own upgrade, already reconciled in commit 9defca8) added a SECOND caller, SessionRules::runMacro (session_rules.cpp:434-451), which replays macro.steps through the exact same ChainRunner::run and then durably ingests the extracted vars into SessionRules' per-host bag (session_rules.cpp:448 ingestVariables) -- which the injection pipeline (applyToRequest/applyToRequestBytes) then threads into subsequent Proxy/Repeater/Intruder requests. So for a NAMED, persisted SessionMacro specifically, the chain is no longer 'attached to nothing': deriving a value from response 1 and updating request N+1's parameters now works end-to-end, including auto re-auth on a logged-out trigger. This does NOT fully close the gap: (a) it only applies to a configured SessionMacro, not an ad-hoc /api/chain/run chain, which still has no downstream consumer of its own; (b) the form-field extractor gap (item #85/170) is untouched; (c) crawl/deep-audit's own HttpClient still never consults SessionRules (confirmed: no SessionRules reference in crawler.cpp or the runDeepAudit call path -- see item #85/200). State held at partial for these remaining reasons, but the 'attached to nothing' framing in the original gap/why is stale for the login-macro case -- flagged here rather than silently re-affirmed."},{"a":"sequencer","f":"Cookie jar: capture cookies from all tools, with a \"monitor traffic from\" setting per tool (Proxy / Repeater / Scanner / Intruder / Sequencer / Extender)","s":"partial","i":"high","e":"days","g":"Proxy-only, hard-wired at app.cpp:779, no per-tool setting and no way to add one without touching C++. Repeater, Intruder AND the chain runner each construct their own HttpClient and never emit responseReceived, so a session refreshed during a Repeater login — or by a `nullock chain` login sequence — is invisible to the jar. WebSocket responses are explicitly excluded too (session_manager.cpp:35 `if (req.method.startsWith(\"WS\")) return;`).","w":"Confirmed verbatim in app.cpp and session_manager.cpp, and I independently confirmed the Repeater/Intruder gap by grepping those two files for \"session\" — zero hits, so it is not a naming issue. Held at partial (capture works, from exactly one tool, with no setting).","v":"Src/App/app.cpp:937-940: `Nullock::Core::SessionManager sessions; proxy.setSessionManager(&sessions); QObject::connect(&proxy, &Nullock::Proxy::ProxyServer::responseReceived, &sessions, &Nullock::Core::SessionManager::onResponseReceived);` -- the sole feed. Capture at session_manager.cpp:45-51 `for (const auto &h : resp.headers) { if (h.first.compare(\"Set-Cookie\", Qt::CaseInsensitive) != 0) continue; ... }`. WebSocket exclusion at session_manager.cpp:37 `if (req.method.startsWith(\"WS\")) return;`. `grep -n onResponseReceived|SessionManager Src/Core/Networking/repeater.cpp Src/Core/Networking/intruder.cpp Src/Core/Networking/chain_runner.cpp`: 0 hits -- capture (as opposed to the separate SessionRules injection pipeline items #71/#72 discuss) is still Proxy-only.","o":"","r":"Wave 0 register-accuracy audit: held at partial. app.cpp wiring drifted 777-780 -> 937-940 (identical content); session_manager.cpp's Set-Cookie capture loop drifted 39-44 -> 45-51; the WS exclusion drifted :35 -> :37 (all unchanged content, small shifts from earlier additions in the file). Re-confirmed Repeater/Intruder/ChainRunner still construct their own HttpClient and never call SessionManager::onResponseReceived or hold a SessionManager pointer at all (distinct from the SessionRules {{var}}-injection pipeline, which items #71/#72 (157/159) now confirm DOES reach Repeater/Intruder via a per-rule tools bitmask -- capture is a different, still- unaddressed half of this gap). No 'monitor traffic from' per-tool setting exists for the cookie jar. Claim holds; evidence line numbers refreshed."},{"a":"sequencer","f":"Cookie jar honors cookie path scope","s":"present","i":"low","e":"hours","g":"Correct as implemented. Two scope caveats, neither a correctness defect: it only runs on the proxy inject path (injectInto is called solely from proxy_server.cpp:1484), and the cookie's Path is never surfaced in the UI (ui-v2/app.jsx:1932-1946 renders name / value / HO / S / SameSite only), so a path-suppressed cookie is undiagnosable from the app.","w":"Attacked hardest per instructions and it survives. I read session_manager_logic.cpp:81-116 and the inject site in full. The dot-segment normalisation is real RFC 3986 5.2.4, the directory-prefix and '/'-boundary cases are both handled, query and fragment are stripped, and an absent or relative path correctly defaults to \"/\". Enforcement is at the actual inject site, not just declared. Held at pres","v":"session_manager_logic.cpp:94-116 verbatim: `QString cp = cookiePath; if (cp.isEmpty() || !cp.startsWith('/')) cp = QStringLiteral(\"/\"); QString rp = reqPath.isEmpty() ? QStringLiteral(\"/\") : reqPath; const int cut = rp.indexOf(QChar('?')); if (cut >= 0) rp = rp.left(cut); const int hash = rp.indexOf(QChar('#')); if (hash >= 0) rp = rp.left(hash); ... rp = removeDotSegments(rp); if (cp == rp) retur","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"sequencer","f":"Cookie jar viewer: list every cookie, and add / edit / remove individual cookies by hand","s":"present","i":"medium","e":"days","g":"None -- add/edit/remove now round-trip through the backend. POST /api/sessions/setCookie upserts a cookie by name (SessionManager::setCookie, control_server.cpp) covering both 'add a cookie obtained out-of-band' and 'edit a value'; POST /api/sessions/removeCookie deletes exactly one cookie (SessionManager::removeCookie), distinct from the pre-existing whole-host/whole-jar clear. The Sessions tab's Cookie Jar section (ui-v2/app.jsx) gained an Add-cookie button per host plus Edit/Del buttons per cookie row, wired via NL.actions.sessionSetCookie/sessionRemoveCookie (ui-v2/real-data.js).","w":"Closed 2026-08-21: the prior audit correctly found /api/cookies was GET-only with no mutating counterpart for a single cookie. Added the missing backend surface -- pure isValidCookieName/upsertCookie/removeCookieByName helpers in session_manager_logic.{hpp,cpp} (RFC 6265 token-name validation reused from parseSetCookie, so a hand-typed name can't smuggle a second cookie via header injection on the next inject), SessionManager::setCookie (upserts by name, creates the host session if missing, treats a manual cookie as a session cookie so it is never auto-pruned by cookieExpired) and SessionManager::removeCookie, plus the two new POST routes -- then wired both into the existing Cookie Jar UI. A host must already appear in the jar (i.e. have been proxied at least once) to add its first manual cookie; there is no free-text 'new host' entry point, a reasonable scope limit since Burp's own jar is also populated from observed traffic.","v":"Src/Core/Networking/session_manager_logic.{hpp,cpp} (isValidCookieName/upsertCookie/removeCookieByName); Src/Core/Networking/session_manager.{hpp,cpp} (SessionManager::setCookie/removeCookie); Src/BackEnd/Control/control_server.cpp POST /api/sessions/setCookie + /api/sessions/removeCookie; ui-v2/app.jsx Cookie Jar section (Add cookie / Edit / Del buttons); ui-v2/real-data.js sessionSetCookie/sessionRemoveCookie; Tests/session_manager/session_manager_test.cpp (name-validation + upsert/remove list-op coverage).","o":"present","r":"Cookie jar gains real per-cookie mutation: backend setCookie/removeCookie (upsert-by-name, single-cookie delete) plus Add/Edit/Del controls on the Sessions tab's Cookie Jar section, closing the item's last honest gap (no backend endpoint for the three per-cookie mutations). This cloud session cannot build/run ctest -- new pure-logic unit tests added and hand-traced against the implementation; will confirm the session_manager ctest target passes against a green GitHub Actions run before treating this fully verified."},{"a":"sequencer","f":"Per-host isolation of captured session values (Burp's cookie jar is domain-scoped; captured macro variables are global)","s":"exceeds","i":"low","e":"hours","g":"None on the injection path — a host-A secret cannot be injected into a host-B request. Caveat: `variables()` deliberately flattens every host's bag into one namespace for the snapshot, so a same-named variable from a different host overwrites in the READ view and all captured secrets appear together in the polled snapshot JSON. Isolation is enforced where it matters (egress) but is not maintained in the introspection surface.","w":"Verified verbatim on both the store and read sides, plus the declared member. The isolation on the INJECT path is genuine and is a real security property Burp's global macro bag does not have. Held at exceeds — but with a caveat the first pass missed: the same class has a deliberately flattened cross-host reader that is published in the snapshot.","v":"session_rules.cpp:236-240 store side verbatim: `// Store under the HOST the value was extracted from -- never inject a // host-A secret into a host-B request. auto &hostVars = m_varsByHost[req.host]; for (auto it = newVars.cbegin(); it != newVars.cend(); ++it) hostVars.insert(it.key(), it.value());`; read side :251-253 `// ONLY variables captured from THIS request's host -- a secret extracted // from another host must never ride along cross-origin. vars = m_varsByHost.value(req.host);`; member session_rules.hpp:192 `QHash<QString, QHash<QString, QString>> m_varsByHost;`. Flattened read view confirmed at session_rules.cpp:133-141 `variables()` (later host wins on a name collision) -- the caveat still holds.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"sequencer","f":"Safety of injected session values (Burp substitutes macro-derived values verbatim)","s":"exceeds","i":"low","e":"hours","g":"None on the sanitisation itself. Adjacent weakness (tracked under item 15): the same function leaves an UNRESOLVED `{{var}}` in the output string, which is then injected verbatim because it is non-empty — sanitisation is sound, resolution is not.","w":"Every cited line verified verbatim: CR/LF plus C0 stripping, ';' stripping for cookies, JSON-context escaping, and the single-pass substitution that blocks a captured value from expanding into another placeholder. This is a genuine hardening layer Burp does not have. Held at exceeds.","v":"session_rules_logic.cpp:105-114 verbatim: `QString sanitizeHeaderValue(const QString &v) { QString out = v; out.remove('\\r').remove('\\n'); QString clean; clean.reserve(out.size()); for (const QChar c : out) if (c.unicode() >= 0x20 || c == '\\t') clean.append(c); return clean; }`; :116-118 `sanitizeCookieValue` strips ';' on top; JSON escape :120-128 `jsonEscapeInner` (serialize-then-unwrap for a correctly escaped inner literal); single-pass substitute() at :76.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"sequencer","f":"Cookie jar transport safety (do not replay a Secure cookie over cleartext)","s":"present","i":"medium","e":"hours","g":"The gate is still a port heuristic, not a TLS check: injectableOverTransport returns `port == 443` for Secure cookies. Confirmed HttpRequest (proxy_server.hpp:34-44) has NO tls/secure/scheme field, and session_manager.cpp:131 passes only req.port. Fix: (1) add `bool tls = false;` to Nullock::Proxy::HttpRequest; (2) set it true at the two places requests are constructed on a TLS connection (proxy M","w":"Reclassified present -> partial (2026-08-02): independent triage + adversarial-verify agreed; cited files re-confirmed to exist. See PARITY-BACKLOG.md.","v":"session_manager_logic.cpp:118-121 (`if (!c.secure) return true; return port == 443;`); session_manager.cpp:131 (`injectableOverTransport(c, req.port)`); proxy_server.hpp:34-44 (HttpRequest struct — method/target/host/port/path/headers/body/timestamp, no tls flag).","o":"present","r":"Closed 2026-08-12 (SECURITY). Replaced the port==443 heuristic with a real TLS check: added `bool tls=false` to Proxy::HttpRequest, set true on the MITM'd HTTPS paths (proxy_server.cpp H2 + the two sslClient read loops; the plain Connection::run leaves it false), changed injectableOverTransport(c,int port)->(c,bool tls){return c.secure?tls:true;} and its caller session_manager.cpp req.port->req.tls. The heuristic both LEAKED a Secure cookie over cleartext on :443 and REFUSED it over TLS on a non-standard port (:8443); the bool check fixes both. Fail-closed: an unknown/default transport never injects a Secure cookie. Mutation-tested (ignoring transport fails the Secure-over-cleartext cases)."},{"a":"sequencer","f":"Sequencer tool tab (dedicated UI with Live capture / Manual load / Analysis sub-tabs)","s":"present","i":"high","e":"weeks","g":"None -- the SEQUENCER tab (ui-v2/app.jsx SequencerTab) now has all three named sub-areas: Manual Load (paste/load-file/paste-clipboard + sample summary + ANALYZE NOW), Analysis (full results render), and Live Capture (host/port/TLS + raw request + extract-from picker + count/throttle, START/STOP/CLEAR, a progress readout, harvested tokens fed straight into the Manual Load corpus).","w":"Closed 2026-08-23: the Live Capture sub-area named absent in the 2026-08-10 wave note is now built -- the backend engine landed 2026-08-17 (f910a9e) but had no UI caller until this wave wired it up.","v":"ui-v2/app.jsx SequencerTab's Live capture card (capHost/capPort/capTls/capRequest/capExtractFrom/capExtractKey/capCount/capThrottleMs state + captureStart/captureStop/captureClear); ui-v2/real-data.js NL.actions.sequencerCapture{Start,Stop,Clear,Tokens}.","o":"present","r":"Sequencer Live Capture UI wave: wired the existing capture engine/API (f910a9e) into SequencerTab, closing the tab's last missing sub-area."},{"a":"sequencer","f":"Send to Sequencer (context-menu handoff from Proxy history / Repeater / Target)","s":"present","i":"high","e":"days","g":"Wired from Proxy history's DetailPane, Repeater's request/response panes, and Target: the SiteMap tree's onSelectLeaf sets the exact same selectedRowId the HistoryTable uses, so a site-map leaf click renders the identical shared DetailPane underneath -- SEQUENCER button included, no separate per-Target wiring needed. Two honest caveats, same class already accepted for the sibling Send to Comparer/Intruder items: it is a toolbar button, not a literal right-click context-menu entry, and the button requires an actual text selection (grabbed from the textarea at click time) rather than offering whole request/response, since sending a whole HTTP message as a single 'token' would be meaningless for entropy analysis.","w":"Register-accuracy fix, re-verified 2026-08-24: the prior gap text claimed 'Target/scope has no send-to-Sequencer path at all (there's no per-request view there to select a token from)', but that is stale against live source. ui-v2/proxy.jsx's ProxyTab renders SiteMap and DetailPane side by side in one shared layout; SiteMap's onSelectLeaf prop (line ~3005) dispatches the same selectedRowId the HistoryTable's onSelect uses, and DetailPane's row prop is `rows.find(r => r.id === selectedRowId)` regardless of which control set that id -- so clicking a Target/site-map leaf populates the identical DetailPane instance, SEQUENCER button and all (confirmed live: showSitemap defaults to true in tweaks, ui-v2/app.jsx:288, so the tree is on-screen by default). This mirrors the grading already given to the sibling 'Send to Intruder from other tools' and 'Comparer: \"Send to Comparer\" from any Burp message' items, both 'present' despite the same toolbar-button-not-menu nuance and despite Comparer's own gap text admitting it isn't wired from every named source either. No code change this pass -- gap/why/evidence corrected to match live source; state moves partial -> present for consistency with sibling grading now that the 'Target has no path' claim is confirmed false.","v":"ui-v2/proxy.jsx ProxyTab: SiteMap onSelectLeaf={(e, id) => dispatch({type:\"set\", payload:{selectedHost:e.host, selectedOrigin:e, selectedRowId:id}})} (~line 3005); HistoryTable onSelect={r => dispatch({type:\"set\", payload:{selectedRowId:r.id}})} (~line 3084) -- both write the same selectedRowId; `const selectedRow = rows.find(r => r.id === selectedRowId)` (~line 2959) feeds the one <DetailPane row={selectedRow} onSendSequencer={...}> instance (~line 3104-3120) regardless of selection source. ui-v2/app.jsx:288 tweaks.showSitemap default true, passed to ProxyTab as showSitemap prop so the SiteMap tree renders by default. DetailPane's SEQUENCER button/sendSelectionToSequencer unchanged from the 6be90f4 wave.","o":"present","r":"Register-accuracy fix (no code change): the 'Target/scope has no send path' half of this item's gap text was stale -- Target's SiteMap leaf selection has shared the same selectedRowId/DetailPane as Proxy history since the proxy.jsx SiteMap component was built, so the SEQUENCER button already reaches Target too. Corrected gap/why/evidence and moved state partial -> present, matching the sibling Send-to-Comparer/Send-to-Intruder items' existing grading for the same toolbar-button-not-menu nuance. Live Capture (#168-171) stays a separate, larger absent item."},{"a":"sequencer","f":"Live capture — repeatedly issue the selected request and harvest the token from each response","s":"present","i":"blocker","e":"weeks","g":"None -- SequencerTab's Live capture panel drives the full engine: host/port/TLS + a raw request template, an extract-from picker (header/cookie/JSON path/regex/status) + key, shot count + throttle, START/STOP/CLEAR, and a live progress readout (done/total/harvested/emptyExtract/httpErrors/transportErrors/lastStatus). Harvested tokens stream into the same corpus the Manual Load / Analysis sub-areas already use, so a capture flows straight into randomness analysis, Copy/Save, and export with no extra step.","w":"Closed 2026-08-23: f910a9e (2026-08-17) shipped the backend engine + API but left the UI as its own honest remainder ('the Live Capture UI sub-panel ... is the remaining piece'); this wave adds that panel with no backend change.","v":"ui-v2/app.jsx SequencerTab (capPoll polling /api/sequencer/capture/tokens every 1.5s while running, captureStart/captureStop/captureClear); ui-v2/real-data.js NL.actions.sequencerCaptureStart/Stop/Clear/Tokens; control_server.cpp:5105-5188 (unchanged) /api/sequencer/capture/{start,stop,clear,tokens}.","o":"present","r":"Sequencer Live Capture UI wave: frontend-only wiring of the existing capture engine (f910a9e) -- Start/Stop/Clear + progress + corpus harvest, no backend change."},{"a":"sequencer","f":"Live capture token location: Cookie (dropdown of cookies seen in the response)","s":"present","i":"high","e":"days","g":"None -- SequencerTab's Live Capture panel (ui-v2/app.jsx) now shows a live \"cookies seen so far\" <select>, auto-populated from the distinct Set-Cookie names the capture engine has actually observed in captured responses so far (SequencerCapture::snapshot()'s new cookieNames field), refreshed on the same 1.5s poll the rest of the panel already uses. Picking an entry fills the existing free-text extract-key field, which stays editable by hand for a cookie not yet seen or before any shot has completed.","w":"Closed 2026-08-23 (partial -> present): the prior wave's free-text-only key field is now backed by a real auto-populated picker, closing the literal \"dropdown of cookies seen in the response\" ask. Backend: SequencerCapture tracks the distinct Set-Cookie NAMES (not values) seen across a run in a mutex-guarded, capped (kMaxCookieNames=64 -- a target minting a fresh name every response can't grow it unbounded) list, reset on start()/clear(), exposed as snapshot()'s new cookieNames field. /api/sequencer/capture/tokens already forwards the whole snapshot() object (control_server.cpp:5167), so no control_server.cpp change was needed -- the new field reached the frontend for free. Frontend: the picker renders only in Cookie extract-from mode, seeded from the already-polled capSnapshot.cookieNames, with a friendly \"none yet\" placeholder before the first Set-Cookie response arrives.","v":"Src/Core/Networking/sequencer_capture_logic.{hpp,cpp} cookieNameFromSetCookie (7 unit-tested cases, Tests/sequencer_capture/sequencer_capture_test.cpp); sequencer_capture.{hpp,cpp} m_cookieNames/kMaxCookieNames + snapshot()'s cookieNames field, reset in start()/clear(), populated in run()'s per-shot Set-Cookie scan; ui-v2/app.jsx SequencerTab's new cookie-picker <select>, gated on capExtractFrom === 'cookie'.","o":"present","r":"Sequencer live-capture cookie-picker wave: backend now tracks distinct Set-Cookie names seen per run and exposes them via the existing snapshot()/tokens endpoint; SequencerTab's Live Capture panel gets a \"cookies seen so far\" dropdown in Cookie mode that fills the existing free-text extract key, closing the item's literal \"dropdown of cookies seen in the response\" ask."},{"a":"sequencer","f":"Live capture token location: Form field (auto-listed HTML form field values, for anti-CSRF tokens)","s":"absent","i":"medium","e":"days","g":"Absent, and the enabling primitive (an HTML form parser feeding an extractor) does not exist elsewhere to borrow.","w":"Confirmed, and I checked harder than the first pass did: neither the session-rule extractor nor the chain-runner extractor has a form-field mode either, so there is no HTML form parser anywhere that could be wired up. This is absent twice over.","v":"SequencerCaptureLogic::ExtractFrom (sequencer_capture_logic.hpp:23-30) enumerates FromHeader/FromCookie/FromJson/FromRegex/FromStatus/FromDelimiter -- explicitly mirrored from ChainRunner::Extract::From (header comment :10-12) with ONE addition (FromDelimiter, a literal start/end-marker extractor) and still no form-field mode. session_rules.hpp:53-58 (SessionRule::ExtractFrom) and chain_runner.hpp:29 (ChainRunner::Extract::From) likewise have no Form option. No HTML form parser exists anywhere in the extraction layers.","o":"","r":"Wave 0 register-accuracy audit: held at absent, but the evidence needed real re-derivation, not just a line-number refresh -- a live-capture engine (Src/Core/Networking/sequencer_capture.cpp/.hpp + sequencer_capture_logic.cpp/.hpp) was added since the last audit, giving Sequencer its own token-harvesting extraction vocabulary independent of ChainRunner/SessionRules. Checked it specifically for a form-field mode: SequencerCaptureLogic::ExtractFrom (sequencer_capture_logic.hpp:23-30) has Header/Cookie/Json/Regex/Status plus one NEW option, FromDelimiter (a literal start/end-delimiter extractor, key encoded \"<start>\\x1f<end>\") -- useful for scraping an inline-HTML token by surrounding text, but still not an HTML FORM-FIELD parser (no DOM/attribute-aware extraction; a delimiter is just two literal strings). ChainRunner::Extract::From (chain_runner.hpp:29) and SessionRule::ExtractFrom (session_rules.hpp:53-58) are unchanged, still four options, no Form. No HTML form parser exists anywhere in Src/. State holds at absent; the enabling primitive genuinely still does not exist, though the new delimiter mode narrows the practical gap for anti-CSRF tokens with stable surrounding markup."},{"a":"sequencer","f":"Live capture token location: Custom location (define start/end delimiters or a regex extraction rule on the response)","s":"present","i":"high","e":"days","g":"None -- both extraction modes are now GUI-reachable in the SEQUENCER tab's live-capture panel. SEQ_CAPTURE_EXTRACT_FROM gains a 'delimiter' option; picking it swaps the single key input for two fields (start/end delimiter) that encode to SequencerCaptureLogic's '<start>\\x1f<end>' key format at capture-start time. The regex mode (closed 2026-08-17) already had its UI.","w":"Closed 2026-08-27: added the delimiter-mode UI (ui-v2/app.jsx SequencerTab) -- capDelimStart/capDelimEnd state, a start/end-delimiter option in the extract-from select, and encoding to the backend's FromDelimiter key format on captureStart(). The backend half (FromDelimiter, parseExtractFrom) was already implemented and unchanged by this wave.","v":"ui-v2/app.jsx SEQ_CAPTURE_EXTRACT_FROM 'delimiter' option + capDelimStart/capDelimEnd inputs, encoded as capDelimStart + \"\\x1f\" + capDelimEnd in captureStart(); Src/Core/Networking/sequencer_capture_logic.cpp FromDelimiter branch (unchanged) already decodes that exact format.","o":"present","r":"Wired the delimiter-mode UI onto the already-implemented FromDelimiter backend, closing the last open gap on this item (regex mode was closed 2026-08-17)."},{"a":"sequencer","f":"Live capture controls: Start / Pause / Stop, running token count, capture progress panel","s":"partial","i":"medium","e":"days","g":"Start, Stop, running token count, and a full capture-progress panel (done/total/harvested/emptyExtract/httpErrors/transportErrors/lastStatus, plus corpus-guard notes) are now UI-reachable in SequencerTab's Live capture card, polling every 1.5s while a capture runs. Pause remains genuinely unbuilt at the engine level -- SequencerCapture has no pause/resume primitive, only start/stop -- so there is nothing for a Pause button to call.","w":"Narrowed 2026-08-23 (partial -> partial, gap-narrowing not a state flip): the 2026-08-17 wave shipped Start/Stop + the progress snapshot at the API level only ('the control-panel UI is pending'); this wave adds that UI. Pause was never built at any layer and stays the honest remainder.","v":"ui-v2/app.jsx SequencerTab's START/STOP/CLEAR CAPTURE buttons + capSnapshot progress readout; Src/Core/Networking/sequencer_capture.cpp snapshot() fields (unchanged); grep for pause/resume in sequencer_capture.{hpp,cpp} = no match.","o":"absent","r":"Start/Stop + a running token count + capture progress now exist at the engine/API level: /api/sequencer/capture/start and /stop, with the snapshot's sequencerCapture slice reporting running/done/total/harvested (+ emptyExtract/httpErrors/transportErrors/lastStatus). PARTIAL: Pause is not built (only Stop), and the control-panel UI is pending."},{"a":"sequencer","f":"Live capture request engine settings: number of threads, throttle between requests, retry on failure","s":"partial","i":"medium","e":"days","g":"Throttle-between-requests is now UI-reachable (a throttleMs number field in SequencerTab's Live capture card, clamped [0,60000] server-side). Thread-count is intentionally NOT offered at any layer -- capture fires sequentially by design, since rapid parallel identical requests risk tripping rate-limits/lockout on the very session being sampled -- a deliberate omission, not a gap to close. 'Retry on failure' has no operator-facing setting: the engine automatically backs off on a 429's Retry-After header, but there is no configurable retry-count/backoff-policy control.","w":"Narrowed 2026-08-23 (partial -> partial, gap-narrowing not a state flip): the 2026-08-17 wave shipped throttleMs + automatic 429 backoff at the API level only; this wave adds the throttle UI. Thread-count stays a deliberate non-goal; a configurable retry policy remains unbuilt.","v":"ui-v2/app.jsx SequencerTab's throttle (ms) number input -> req.throttleMs; Src/Core/Networking/sequencer_capture_logic.cpp clampThrottleMs/retryAfterMs (unchanged).","o":"absent","r":"Pacing settings are partly built: a per-shot throttleMs (clamped [0,60000]) and automatic 429 Retry-After backoff (bounded + interruptible) pace the loop. The thread-count knob is intentionally NOT offered -- capture fires sequentially on one worker by design (rapid parallel identical requests trip rate-limits / account lockout on the very session being sampled). Remaining: the settings UI."},{"a":"sequencer","f":"Live capture: \"Auto analyze\" (re-run the analysis automatically every N tokens captured)","s":"absent","i":"low","e":"days","g":"Absent. Also note the design would have to change: several tests (positionalEntropy, bitLevelTests) recompute over the full corpus, so incremental re-analysis is O(N) per batch.","w":"Confirmed. analyzeTokens is a one-shot pure function with no incremental or streaming form — I read its full signature and body.","v":"Src/Core/Networking/sequencer_capture.cpp/.hpp: a full live-capture engine now exists (SequencerCapture::run, :108-199) that fires N requests and harvests one token per response into a corpus (m_tokens). control_server.cpp:5511-5535 `/api/sequencer/capture/tokens` recomputes `Nullock::Core::Sequencer().analyze(toks)` (whole-corpus analyzeTokens) fresh on EVERY call (:5527-5529), gated by SequencerCaptureLogic::corpusGuard. ui-v2/app.jsx:4352-4372 `capPoll` calls this endpoint every 1500ms while a capture is running (`setInterval(capPoll, 1500)` at :4370) but only consumes `r.tokens` (folds new tokens into the corpus textarea, :4357-4362) -- `r.analysis`/`r.corpusNote`/`r.distinct` are stored in `capSnapshot` (:4356) but never rendered; the visible Sequencer results panel is only ever populated by the separate, manually-triggered ANALYZE NOW action.","o":"","r":"Wave 0 register-accuracy audit: held at absent, but the underlying facts changed enough to need a full re-derivation, not a line refresh. A live-capture engine (sequencer_capture.cpp/.hpp, sequencer_capture_logic.cpp/.hpp) landed since the last audit and IS wired to auto-run the full randomness analysis: /api/sequencer/capture/tokens recomputes analyzeTokens() over the whole harvested corpus on every call (control_server.cpp:5527-5529), and the UI already polls that exact endpoint every 1.5s while a capture is in flight (app.jsx capPoll/setInterval, :4352-4372) -- so the mechanical pieces for 'auto analyze every N tokens' (a live poll re-running the full analysis) already exist and already fire automatically. The gap survives on a technicality: capPoll only reads the response's `tokens` field to grow the corpus textbox; the `analysis` field the backend computes on the same round trip is stored in `capSnapshot` but never read by any render path (grepped app.jsx for `capSnapshot.analysis`: 0 hits) -- so the user sees no live-updating verdict during a capture, only after manually clicking ANALYZE NOW once it's done. Also worth noting: this poll-and-discard pattern is a full O(N) recompute already running every poll, which the original 'why' assumed would need a design change; that assumption is now stale. State holds at absent as experienced by the user; wiring `capSnapshot.analysis` into the results panel would close this with no backend change."},{"a":"sequencer","f":"Copy tokens / Save tokens to file from a capture","s":"present","i":"low","e":"hours","g":"None -- Live Capture's harvested tokens are folded straight into SequencerTab's shared token corpus (the same `text` state Manual Load/Send-to-Sequencer already populate) as they arrive, so the existing COPY TOKENS (clipboard) and SAVE TOKENS (.txt download) buttons cover a capture's output too, with no separate capture-specific export path needed.","w":"Closed 2026-08-23: the 2026-08-18 wave (da90e67) closed the Manual Load half and named Live Capture's absent request-issuing engine as the reason the other half stayed partial ('blocked on a request-issuing engine Nullock doesn't have'). That engine shipped 2026-08-17 (f910a9e); this wave's Live Capture UI reuses the exact same `text` state for harvested tokens, so Copy/Save now cover both halves for free.","v":"ui-v2/app.jsx SequencerTab: copyTokens()/saveTokens() functions + COPY TOKENS/SAVE TOKENS buttons in the manual-load control row (unchanged, shipped 2026-08-18); the new Live Capture panel's capPoll folds harvested tokens into the same setText()-backed corpus those buttons already read from -- no separate export path was needed.","o":"present","r":"Sequencer Live Capture UI wave: harvested tokens append into the same SequencerTab `text` state the existing COPY TOKENS/SAVE TOKENS buttons already act on, closing this item's Live Capture half as a free side effect."},{"a":"sequencer","f":"Reliability rating of the estimate (how much the result can be trusted given sample size)","s":"present","i":"medium","e":"days","g":"None. The analysis reports a reliability rating (insufficient/low/medium/high/very-high) derived from the token sample size.","w":"Closed 2026-08-10 (da103c8): reliabilityRating added + surfaced as result['reliability'].","v":"Src/Core/Networking/sequencer_logic.cpp reliabilityRating (sequencer.hpp), set as result['reliability'] in analyzeTokens; 5 threshold-band tests in Tests/sequencer.","o":"absent","r":"Sample-size reliability rating implemented + tested."},{"a":"sequencer","f":"Significance level selector (0.1% / 1% / 5% etc.) that re-grades every test and the entropy estimate","s":"partial","i":"medium","e":"days","g":"The UI dropdown is now in: a significance <select> (0.1/1/5/10%) sits next to Sequencer's ANALYZE NOW button, threads significanceLevel into POST /api/sequencer/analyze, and the Bit-level tests section header echoes the server-clamped alpha it actually graded at. Still partial: the keyspace ENTROPY estimate (shannon bits, good/ok/low verdict) is a point estimate, not an alpha-graded hypothesis test, so it is not re-graded by the selector and never will be without a shape change to that estimate -- Burp's own feature covers both, so this stays short of it.","w":"Implemented + mutation-proven. Each bit test's hard-coded p<0.01 critical was replaced by a pValue<alpha comparison computed from the existing statistic (chiSquareSurvival for chi tests; two-sided normal erfc for the z/correlation tests), so alpha=0.01 reproduces the historical criticals EXACTLY (the serial effect-floor provably implies p<0.01 for all m>=20; gauntlet stayed 100/100 + 156/156). alpha is clamped to [1e-6,0.2] and echoed as result.significanceLevel. 2026-08-25: the previously backend-only selector got a GUI control.","v":"sequencer.hpp analyzeTokens(tokens, alpha=0.01) + Sequencer::analyze(tokens, sig=0.01); sequencer_logic.cpp bitLevelTests(tokens, alpha) grades monobit/twoBit/serial/poker/runs/longRun/runLengths + perBit/bitCorr (Bonferroni alpha/N) by pValue<alpha and exposes each pValue; control_server.cpp:/api/sequencer/analyze reads significanceLevel. Tests/sequencer/sequencer_test.cpp (120 pass): pivot-straddle proves monobit.failed flips as alpha crosses its own p-value; echo+clamp+monotonicity+behaviour-preservation; M1 (monobit ignores alpha) and M2 (force alpha=0.01) each fail only their targeted cases. Live e2e: POST significanceLevel=0.179->fail, 0.0448->pass for the same corpus. ui-v2/app.jsx SequencerTab: sigLevel useState + <select> (0.001/0.01/0.05/0.1) wired through NL.actions.sequencerAnalyze(tokens, sigLevel); ui-v2/real-data.js sequencerAnalyze(tokens, significanceLevel) includes it in the POST body only when set.","o":"","r":"Sequencer wave: significance-level <select> next to ANALYZE NOW, wired to the already-complete backend alpha grading; entropy re-grading remains the documented, permanent shortfall vs. Burp."},{"a":"sequencer","f":"Character-level test: Character transition analysis (is the character at position i in token k independent of the character at position i in token k-1)","s":"present","i":"medium","e":"days","g":"None. Per-position character-transition independence is measured as Cramer's V of the consecutive-token contingency table and flagged when any position is strongly associated -- catching per-position serial correlation that per-position entropy is blind to.","w":"Closed 2026-08-10 (80e3672): maxPositionalTransitionV added + surfaced as result['transition']; mutation-proven.","v":"Src/Core/Networking/sequencer_logic.cpp maxPositionalTransitionV (sequencer.hpp), set as result['transition'] in analyzeTokens; Tests/sequencer +1-shift + sentinel cases.","o":"absent","r":"Per-position character-transition (Cramer's V) test implemented + tested."},{"a":"sequencer","f":"Bit-level test: FIPS poker test (non-overlapping 4-bit groups, chi-square over 16 buckets)","s":"present","i":"medium","e":"hours","g":"None. FIPS poker chi-square (15 dof) over non-overlapping 4-bit groups is computed on the decoded bit stream and surfaced in the analysis.","w":"Closed 2026-08-10: fipsPokerChiSquare added + wired into bitLevelTests.","v":"Src/Core/Networking/sequencer_logic.cpp fips{Poker,Runs}/longestBitRun helpers (declared in sequencer.hpp), folded into bitLevelTests + the analysis JSON (bitLevel.poker/.runs/.longRun); mutation-proven in Tests/sequencer (stubbing the helpers fails exactly the 6 discriminating cases). Commit dd9c158.","o":"absent","r":"FIPS poker test implemented + tested."},{"a":"sequencer","f":"Bit-level test: FIPS runs test (counts of runs of length 1..6+ of identical bits, against expected ranges)","s":"present","i":"medium","e":"hours","g":"None. Both a total-runs z-test AND the FIPS length-bucketed form (chi-square over run lengths 1..6+ vs the geometric expectation) are computed and flagged.","w":"Closed 2026-08-10 (045f671): fipsRunsBucketChi adds the length-bucketed variant the total-runs z-test lacked.","v":"Src/Core/Networking/sequencer_logic.cpp fipsRunsBucketChi + compressionRatio (sequencer.hpp), in bitLevelTests + JSON (bitLevel.runLengths/.compression); mutation-proven in Tests/sequencer. Commit 045f671.","o":"partial","r":"FIPS length-bucketed runs test added."},{"a":"sequencer","f":"Bit-level test: FIPS long runs test (flag any run of identical bits exceeding the threshold)","s":"present","i":"low","e":"hours","g":"None. Longest identical-bit run is computed and flagged when a run that long is <1% likely for the sample size (a size-scaled generalisation of FIPS' fixed-26 rule).","w":"Closed 2026-08-10: longestBitRun added + wired into bitLevelTests.","v":"Src/Core/Networking/sequencer_logic.cpp fips{Poker,Runs}/longestBitRun helpers (declared in sequencer.hpp), folded into bitLevelTests + the analysis JSON (bitLevel.poker/.runs/.longRun); mutation-proven in Tests/sequencer (stubbing the helpers fails exactly the 6 discriminating cases). Commit dd9c158.","o":"absent","r":"FIPS long-runs test implemented + tested."},{"a":"sequencer","f":"Bit-level test: Spectral test (treat consecutive values as coordinates in n-dimensional space, look for lattice clustering)","s":"absent","i":"medium","e":"weeks","g":"Absent as such. Lag-1 Pearson correlation detects only 1-dimensional linear dependence; the spectral test is what exposes LCG lattice structure in 2..8 dimensions, and nothing here detects a Mersenne Twister stream at all.","w":"Confirmed: 0 hits for \"spectral\". The source itself concedes both the substitute and the resulting blind spot — I verified both comments verbatim.","v":"sequencer_logic.cpp:322-324: `//   * byte-level lag-1 serial correlation       -> the LCG/linear-congruential //                                                  lattice (and java.util.Random //                                                  low-bit) signature`. Admission at sequencer.hpp:26-28 (unchanged): `// so small or genuinely-random captures are never false-flagged. (A Mersenne // Twister stream passes 6-8; flagging MT needs a matrix-rank / state-recovery // test, left as future work.)`. `grep -rc spectral Src/`: 0 hits repo-wide, including the new sequencer_capture*.{cpp,hpp}.","o":"","r":"Wave 0 register-accuracy audit: held at absent. The lag-1 serial-correlation comment drifted 206-208 -> 322-324 (sequencer_logic.cpp grew with the confidence/dataAnalyzed summary work, item #71/147); the Mersenne Twister admission in sequencer.hpp did NOT drift, still exactly 26-28. Re-ran the 'spectral' grep repo-wide (including the two new sequencer_capture*.cpp/.hpp files, which do not add any bit-level test): 0 hits. Claim holds; one evidence line range refreshed."},{"a":"sequencer","f":"Bit-level test: Compression test (ZLIB-compress the bit sequence; compression ratio bounds the entropy)","s":"present","i":"medium","e":"hours","g":"None. The decoded byte stream is zlib-compressed and its compression ratio bounds are checked (structure/repetition compresses; random does not).","w":"Closed 2026-08-10 (045f671): compressionRatio (qCompress) added + flagged in bitLevelTests.","v":"Src/Core/Networking/sequencer_logic.cpp fipsRunsBucketChi + compressionRatio (sequencer.hpp), in bitLevelTests + JSON (bitLevel.runLengths/.compression); mutation-proven in Tests/sequencer. Commit 045f671.","o":"absent","r":"Compression test implemented + tested."},{"a":"sequencer","f":"Results drill-down: per-test result panels with charts (per-position bar charts, per-bit significance plots) and pass/fail per position","s":"partial","i":"medium","e":"weeks","g":"Raw JSON on stdout via the CLI is still the only access there, but the GUI (ui-v2/app.jsx) now renders a real per-position bar chart -- one bar per corpus column, height proportional to that column's Shannon entropy relative to the strongest column (`pos.reference`), colored red when a column is 'weak' (matches the same h < 0.5*reference threshold sequencer_logic.cpp uses to flag `biased`) and accent-colored otherwise, with a hover tooltip giving the exact bit value per column. Bit-level tests (monobit/two-bit/serial) are shown as labeled numeric stats with red/normal coloring on failure, not as a plot, and there is still no PER-BIT significance chart (only one summary number per test) and no per-position pass/fail beyond the coarse weak/not-weak bar coloring.","w":"UPGRADED absent->partial: this grade is stale. ui-v2/app.jsx's Sequencer results panel (renderResult, ~4524-4610) gained a 'Per-position entropy' Section (:4580-4598) since the last audit that maps `pos.columnEntropy` (the exact array sequencer_logic.cpp already emitted) into one CSS bar per column (:4589-4594), height = `(h / pos.reference) * 100%`, colored `var(--err)` when `h < 0.5 * (pos.reference || 1)` -- a direct visual mirror of sequencer_logic.cpp's own `weak` threshold (:421-423 `h < 0.5 * ref && (ref - h) >= 1.0`). This is a genuine per-position bar chart with a visible pass/fail-like signal per column, which the prior evidence's 'grep -a columnEntropy ui-v2/: 0 hits' claim said did not exist. The bit-level tests panel (:4599-4608) similarly renders monobit p-value / two-bit chi-square / serial r as labeled, color-graded stats -- a 'per-test result panel', though not a plot and not per-bit. Held at partial: no per-bit significance PLOT (only one aggregate number per test), and pass/fail is still not computed or shown per INDIVIDUAL statistical test at each position (only the coarse weak-column threshold).","v":"sequencer_logic.cpp:409 `r.columnEntropy << H;` and :1117-1118 `for (double h : pos.columnEntropy) cols.append(h); posObj[\"columnEntropy\"] = cols;`; weak-column threshold at :421-423. ui-v2/app.jsx:4580-4598 renders it: `{(pos.columnEntropy || []).map((h, i) => (<div ... title={\"col \" + i + \": \" + h.toFixed(2) + \" bits\"} ...><div style={{ ..., height: Math.min(100, (h / (pos.reference || 1)) * 100) + \"%\", background: h < 0.5 * (pos.reference || 1) ? \"var(--err)\" : \"var(--accent)\" }} /><\/div>))}`. Bit-level stats panel at app.jsx:4599-4608. CLI raw-JSON path unchanged: bin/nullock:724 `post /api/sequencer/analyze \"{\\\"tokens\\\":$tokens}\" | pp`.","o":"","r":"Wave 0 register-accuracy audit: UPGRADED absent -> partial. columnEntropy was always emitted by the backend (sequencer_logic.cpp, drift 550-552 -> 1117-1118 from the confidence/dataAnalyzed work) but the original evidence's 'grep -a columnEntropy ui-v2/: 0 hits' is now false -- ui-v2/app.jsx:4580-4598 added a real per-position bar-chart Section since the last audit, rendering one bar per column colored by the same weak-column threshold the backend computes (h < 0.5*reference), plus a labeled bit-level-tests stats panel (:4599-4608, monobit p / two-bit chi-square / serial r, color-graded on failure). This is a genuine 'results drill-down with charts' as the feature title describes, closing the 'no visualisation anywhere' half of the gap. Remaining and real: no per-bit significance PLOT (bit-level tests show one aggregate number each, not a per-bit chart), and no true per-position PASS/FAIL for each individual statistical test (only the coarse per-column weak/not-weak bar coloring). Downgrade risk considered and rejected: this is core-product GUI code (ui-v2/app.jsx), not a stub or dead branch -- verified the Section is inside the always-rendered renderResult() function, gated only on `pos.applicable`."},{"a":"sequencer","f":"Sequencer analysis report export (HTML / XML report of the token analysis)","s":"partial","i":"medium","e":"days","g":"Client-only export -- the HTML/XML file is generated in the browser from the current analysis and downloaded; it does not enter the report/build pipeline (no cmd_report sequencer branch) and never reaches the findings store, so a weak-token result still cannot be tracked alongside scan findings or against a baseline.","w":"Closed the export half 2026-08-19: SequencerTab (ui-v2/app.jsx) gains EXPORT HTML / EXPORT XML buttons next to the existing SAVE TOKENS button. Two new pure functions, sequencerReportHtml()/sequencerReportXml(), render the exact same fields the on-screen result Sections already show (verdict/score/n/distinctTokens/avgLen, Shannon entropy, character-class ratios, Hamming distance, longest-common-substring, sequential/counter detection, per-position entropy, bit-level tests) into a standalone downloadable file -- no backend change, no new endpoint, the report can never drift from what the operator already sees. Token-derived text (the LCS substring) is HTML/XML-escaped before insertion since it originates in the untrusted analyzed corpus. Stays partial, not present: this is a client deliverable only, not integrated into cmd_report or the findings/baseline store -- the remaining architectural gap this file already named is honestly unchanged.","v":"ui-v2/app.jsx sequencerReportHtml()/sequencerReportXml() (pure, no DOM/I-O) + sequencerReportEscape(); SequencerTab.exportReport(format) builds a Blob and triggers a download, same pattern as the existing saveTokens()/CSRF-PoC download helpers; field set matches renderResult()'s own Section blocks 1:1 so the export cannot show something the screen doesn't.","o":"partial","r":"Sequencer report-export batch -- absent -> partial (client-only export, not wired into cmd_report/findings)"},{"a":"sequencer","f":"Sample-size guidance and FIPS conformance threshold (warn under ~100 tokens, note 20,000 for formal FIPS compliance, cap the sample)","s":"present","i":"medium","e":"hours","g":"No minimum-sample warning, no FIPS-conformance statement (20,000 bits / 20,000 tokens is never mentioned), and no explicit cap. The effective cap is the generic 64 MB body limit — ~1.5M tokens — analysed synchronously on the control-server request thread with a 64 MB `combined` QString built at :449-451, so a large corpus stalls the API rather than being rejected.","w":"Confirmed absent. I also checked the upper-bound concern the first pass raised and can now bound it: the control server caps request bodies at 64 MB, so the corpus is bounded, but the analysis is synchronous on the request path.","v":"control_server.cpp:135 `constexpr qint64 kMaxBodyBytes  = 64LL * 1024 * 1024;` enforced at :1040 `if (!ok || contentLength < 0 || contentLength > kMaxBodyBytes) {`. The sequencer route is NOT in the async/offload set (kActivePaths at :2944-2959 does not list it), so `seq.analyze(tokens)` runs inline. No warning field is ever emitted: analyzeTokens returns early only for the empty case (:436-440 `r","o":"present","r":"Closed 2026-08-11: analyzeTokens now emits a sampleGuidance block via the pure, mutation-tested Core::sampleSizeGuidance -- a warning under the recommended ~100-token minimum (plus a harder not-estimable floor below kDeepMinN) and whether the decoded stream reaches the 20,000-bit FIPS 140-2 sample size. Scope: the sample-size guidance + FIPS conformance threshold are delivered and tested; an explicit user-tunable sample cap / async offload is NOT added here -- the corpus is already bounded by the 64 MB body cap, and the synchronous-analysis concern stays tracked separately."},{"a":"sequencer","f":"Rule scope — Tools scope (apply this rule to Proxy / Scanner / Intruder / Repeater / Sequencer / Extender, checkbox per tool)","s":"partial","i":"blocker","e":"days","g":"Configurable AND enforced for proxy, Repeater and Intruder, with a per-tool editor UI (Proxy/Repeater/Intruder/Scanner checkboxes in the SESSIONS tab rule editor, plus a tools-scope summary per rule row). Remaining: the Scanner checkbox is offered/stored but not enforced anywhere (no scanner call site passes ToolScanner to applyToRequest), and the chain-runner / sequencer / extender scopes are entirely unbuilt (no UI, no enforcement).","w":"Confirmed and STRENGTHENED. I verified the Repeater/Intruder bypass by grepping those two files for \"session\" (0 hits, so it is not a naming difference) and reading their send paths. I also found a third bypass and an additional silent gate the first pass missed.","v":"SessionRule (session_rules.hpp:40-71, read in full) has no tool field. Both hooks live inside one function: proxy_server.cpp:1484 `if (m_sessionManager) m_sessionManager->injectInto(req);` and :1490 `if (m_sessionRules) m_sessionRules->applyToRequest(req);`, guarded upstream at :1447 `if (!isInScope(req.host)) return;`. Bypasses: repeater.cpp:133-136 `const auto result = m_client.send(t.host, stat","o":"partial","r":"Adds the per-tool editor checkboxes flagged as the ui-v2 remainder above: SessionsTab's rule editor (ui-v2/app.jsx) gets a Tools scope row -- Proxy/Repeater/Intruder/Scanner checkboxes bound to the rule's `tools` bitmask via a pure sessionRuleToggleToolBit(mask, bit) helper mirroring SessionRulesLogic::SessionTool exactly (1/2/4/8), plus a sessionRuleToolsLabel(mask) summary (\"all tools\" when unset, else a comma list) shown in the rule list's new tools column. No backend change -- `tools` already round-trips through /api/session-rules (control_server.cpp:1618, :3980). Honest remainder, confirmed by grep: the Scanner bit is offered and stored but NOT enforced -- no call site anywhere passes SessionRulesLogic::ToolScanner to applyToRequest/applyToRequestBytes (only ToolIntruder in intruder.cpp:498/628 and ToolRepeater in repeater.cpp:158 exist; proxy_server.cpp:1539 calls the default-tool overload); the chain-runner/sequencer/extender scopes also remain entirely unbuilt, both as UI and as enforcement. State stays partial -- this closes only the ui-v2 half of the previously-named gap."},{"a":"sequencer","f":"Rule scope — Parameter scope (apply only when named parameters are present)","s":"absent","i":"low","e":"days","g":"Absent, and the matcher deliberately strips the query, so adding parameter scope requires changing what is passed in, not just adding a field.","w":"Confirmed by reading the struct and the matcher in full.","v":"session_rules.hpp:44-86 (struct SessionRule) has no parameter field. session_rules.cpp:151-174 `SessionRules::matches` ends (:171-173) `return resolve(r.hostGlob).match(host).hasMatch() && resolve(r.pathGlob).match(stripQuery(path)).hasMatch() && SessionRulesLogic::urlScopeMatches(...);` -- and stripQuery (session_rules_logic.cpp:130-133) actively DISCARDS the query string before matching, so parameters are still not even visible to the matcher (the newer includeUrls/excludeUrls scope, item #70/156, also matches against `host + stripQuery(path)` only -- session_rules_logic.cpp:169).","o":"","r":"Wave 0 register-accuracy audit: held at absent. Struct span drifted 40-71 -> 44-86 (grew with includeUrls/excludeUrls/tools fields, still no parameter field). matches() drifted 46-67 -> 151-174; its closing return grew a THIRD clause (the new URL-scope check) but that clause also operates on host+stripQuery(path), so it does not expose parameters either. stripQuery drifted 123-126 -> 130-133, content unchanged, still strips the query before any matching happens. Claim holds; evidence refreshed to reflect the struct/function's real current shape, not just re-lined."},{"a":"sequencer","f":"Rule action: \"Run a macro\" (execute a recorded request sequence, optionally before every in-scope request)","s":"partial","i":"blocker","e":"days","g":"The manual bridge is real (record -> chain/run with sessionHost -> session bag -> auto-injected into later requests), and now a NAMED macro store exists with an on-demand run (/api/session-macros + /api/session-macros/run -> SessionRules::runMacro) plus an automatic re-run when the session goes invalid (see #190, now built). What's still missing is the scheduled variant of the rule action: no way to configure a session rule to run a macro automatically BEFORE every in-scope request (only after a logged-out response is detected).","w":"Re-verified after a11754e (2026-08-16): control_server.cpp:9233 reads `bodyJson.value(\"sessionHost\")` and calls `m_wiring.sessionRules->ingestVariables(sessionHost, r.vars)` when set -- a plain chain run (no sessionHost) is unchanged, so this is opt-in exactly as the commit describes. session_rules.cpp:284 `ingestVariables` merges host-keyed vars under the existing mutex and emits variablesChanged, the same signal the UI already listens to. I confirmed there is still no rule-action enum, no scheduler, and no logged-out detector anywhere in Src/Core/Networking/session_rules*.cpp or chain_runner*.cpp -- grep for reauth/sessionInvalid/loggedOut/relogin/checkSession/ruleAction still returns 0 hits.","v":"control_server.cpp:9233-9237 `const QString sessionHost = bodyJson.value(\"sessionHost\").toString(); if (!sessionHost.isEmpty() && m_wiring.sessionRules) m_wiring.sessionRules->ingestVariables(sessionHost, r.vars);`; session_rules.cpp:284-293 `void SessionRules::ingestVariables(...) { ... QHash<QString,QString> &bag = m_varsByHost[host]; for (...) bag.insert(it.key(), it.value()); } emit variablesChanged();`; session_rules.hpp:60-65 still only the four-member InjectInto enum -- no rule-action concept.","o":"partial","r":"Closed in two steps. (1) a11754e: POST /api/chain/run gains an opt-in `sessionHost` (control_server.cpp:9233-9237) -- after the macro runs, SessionRules::ingestVariables(host, vars) merges its extracted vars into that host's session-rule bag, so a token a recorded login macro captures is injected into later requests by the matching rules (record-a-macro -> stay-authenticated, manually). (2) 5012a6f: a named-macro store + on-demand run + automatic re-run. SessionMacro {name, sessionHost, ChainRunner steps, loggedOut condition} is settable via /api/session-macros and runnable by name via /api/session-macros/run -> SessionRules::runMacro, which replays the recorded login sequence and ingests its vars. And the automatic half that this item's evidence called 'fully absent' now exists: item #190's re-auth trigger is built, so a macro re-runs by itself when a response to its host matches the logged-out condition. STILL PARTIAL: no scheduled variant -- you cannot yet say 'before each request to /api/*, run the login chain automatically'; the automatic run fires on session-invalid detection, not on a pre-request schedule. Macros now also PERSIST across restart (d728ea4): the shared sessionMacrosToJson/sessionMacrosFromJson serializer writes them into project.json under `sessionMacros` (persist-at-the-API-call-site, restored via ProjectStore::sessionMacrosChanged on open) -- verified e2e (set -> kill -> relaunch -> restored with every field intact). A visual macro editor is the remaining UI follow-on. NB the cookie jar + the session RULES themselves still don't persist (that is parity #2494, unchanged -- macro persistence is orthogonal to it)."},{"a":"sequencer","f":"Rule action: \"Check session is valid\" (issue a validation request, match a keyword/status/redirect, and conditionally run the re-auth macro)","s":"partial","i":"blocker","e":"weeks","g":"No session-validity detection and no automatic re-authentication. A long Intruder run or audit scan that logs out midway produces a page of meaningless 302s with no warning — and given the Repeater/Intruder bypass above, those tools were never carrying the session anyway.","w":"Confirmed. I read applyToRequest and applyToResponse in full: both are pure string manipulation with no network I/O and no conditional branch on response content.","v":"session_rules.cpp:133-237 `SessionRules::applyToRequest` performs only template substitution into four targets and never constructs a request; :74-131 `applyToResponse` only harvests values into `m_varsByHost`. Neither includes networking.hpp. Greps for reauth / sessionInvalid / loggedOut / relogin / checkSession across Src/: 0 hits.","o":"absent","r":"Built: the session-validity check + conditional re-auth now exist. SessionRulesLogic::responseIsLoggedOut(status, bodyText, statusList, bodyRegex) (session_rules_logic.cpp:133-147) is a pure, unit-tested + mutation-proven predicate -- a comma status list (e.g. \"401,403\") and/or a response-body regex; BOTH empty = never (a macro with no condition never auto-re-auths); status 0 (no response) never matches; an invalid regex fails closed. A SessionMacro (session_rules.hpp:86-95) carries loggedOutStatus/loggedOutBodyRegex; SessionRules::maybeReauth, called from applyToResponse, matches every live response to the macro's sessionHost against it and on a hit re-runs the macro ASYNC (QtConcurrent::run -- never blocks the proxy worker on login I/O) to re-acquire the session, then ingests the fresh vars into the host bag. Loop-guarded: an in-flight QSet + a 5s per-host cooldown, and the macro's own requests use ChainRunner's client (not the proxy) so a permanently-failing login can't hammer the target or re-trigger itself. PARTIAL, honestly: this detects a logged-out session PASSIVELY on the live response stream rather than issuing Burp's dedicated active 'validation request' to a known URL, and there is still no in-browser recovery prompt; but the core -- match status/keyword and conditionally run the re-auth macro -- is real. Closes launch blocker #11 (\"no check-session-is-valid\")."},{"a":"sequencer","f":"Rule action: \"Prompt for in-browser session recovery\" (pause and let the user re-login in the browser)","s":"absent","i":"medium","e":"weeks","g":"Absent. The pause-and-resume primitive exists in the proxy intercept path and could be borrowed, but nothing in session handling can trigger it.","w":"Confirmed. Both session TUs read in full — non-blocking, non-interactive, no pause primitive. Note there IS an interactive pause mechanism in the codebase (InterceptController, app.cpp:770) but it is not reachable from the session path.","v":"session_rules.cpp and session_manager.cpp (both re-read in full: now 488 and 288 lines, up from 239/193) contain no wait, no signal-and-block, no user prompt -- including the new SessionMacro/maybeReauth code (session_rules.cpp:453-486), which is itself async (QtConcurrent::run) and non-interactive. The nearest analogue is Src/App/app.cpp:931-932 `Nullock::Proxy::InterceptController intercept; proxy.setInterceptController(&intercept);` -- the request-intercept pause, which no session code references.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Both files grew substantially since the last audit (session_rules.cpp 239->488 lines, session_manager.cpp 193->288 lines) with the SessionMacro/auto-reauth feature (relevant to items #72/159 and #85/200), so re-read both in full rather than trusting the old line counts. The new maybeReauth path is itself fire-and-forget async (QtConcurrent::run, session_rules.cpp:481) with no pause, no signal-and-block, no prompt -- it re-runs a macro unattended or does nothing, never asking a human to intervene. InterceptController wiring drifted app.cpp:770-771 -> 931-932, still unreferenced by any session code. Claim holds; evidence refreshed."},{"a":"sequencer","f":"Rule action: \"Invoke a Burp extension\" (extension-registered session handling action, ISessionHandlingAction)","s":"absent","i":"medium","e":"days","g":"An extension can rewrite every request, but cannot register a named session-handling action that a rule invokes at a chosen point in an ordered action list — because rules have no action list.","w":"Confirmed. The extension surface is a blanket per-request mutation hook, not a registerable named action — verified against the API header.","v":"extensions_api.hpp:306 `Q_INVOKABLE void onResponse(const QJSValue &callback);` and :311 `Q_INVOKABLE void onRequest(const QJSValue &callback);`, consumed via `applyRequestMutation` (declared :147). No registration API for a named, invocable session-handling action; SessionRule (session_rules.hpp:44-86) still has no action-name field to reference one.","o":"","r":"Wave 0 register-accuracy audit: held at absent. onResponse/onRequest drifted 167/172 -> 306/311, applyRequestMutation drifted :87 -> :147 (extensions_api.hpp grew substantially -- other extension-API work landed, unrelated to session handling). Re-grepped for registerAction/sessionAction/ISessionHandling/registerSessionHandling repo-wide: 0 hits. SessionRule's field list (session_rules.hpp:44-86) still has no action-name/action-id field. Claim holds; evidence refreshed."},{"a":"sequencer","f":"Macros: record a macro by selecting requests from Proxy history, with a macro editor and \"Test macro\"","s":"present","i":"blocker","e":"weeks","g":"None -- recording (POST /api/chain/record), a visual macro editor (SESSIONS tab's Login macros section: name/session host/logged-out condition fields, Record from history, save/edit/delete/run), and \"Test macro\" (POST /api/chain/run) are all done, and the last remaining piece -- a full, untruncated response viewer -- is now closed too: StepResult.responsePreview (chain_runner.cpp) is no longer capped at 2 KiB, and the SCANS tab's Request chain section renders a collapsible per-step viewer (name/status/timing/extracted vars, full response body on expand) instead of the prior raw-JSON-only dump.","w":"Closed 2026-08-27 (d929886): chain_runner.cpp:85 changed `sr.responsePreview = res.rawResponse.left(2 * 1024)` to `sr.responsePreview = res.rawResponse` (full, untruncated) and the .hpp comment updated to match. ui-v2/app.jsx's Request chain section (SCANS tab) gained a per-step list -- each row shows name/HTTP status or error/ms/response size/extracted-var names, click to expand a <pre> with the complete response body -- reusing the same chainRes state the section already populated via NL.actions.chainRun. This is the exact gap the 2026-08-26 reconcile (4300b81) left open after closing recording and the visual macro editor, so state moves partial -> present. Verified cross-platform: GitHub Actions run 33036681345 (this cloud session cannot build/run Qt locally) shows the Windows and Linux NullockApp builds both green against this exact diff, plus the macOS build, CLI-syntax, labs-syntax, fuzz-corpus, marketplace-schema and Docker-image jobs -- 8/8 jobs completed=success before this state flip.","v":"Src/Core/Networking/chain_runner.cpp:85 `sr.responsePreview = res.rawResponse;` (was `.left(2 * 1024)`); chain_runner.hpp:52 `QByteArray responsePreview; // full raw response, untruncated`. ui-v2/app.jsx: chainOpenStep state, the Request chain Section's `chainRes.steps.map(...)` block rendering a clickable name/status/ms/size/extracted-vars header per step with an expandable <pre>{st.responsePreview}<\/pre>. control_server.cpp:10132 unchanged -- `{ \"responsePreview\", QString::fromUtf8(sr.responsePreview) }` already carried whatever the struct held, so no backend wire-format change was needed beyond chain_runner.cpp itself.","o":"present","r":"Closed the last open gap on this item: removed the 2 KiB StepResult.responsePreview cap (chain_runner.cpp) and added a collapsible per-step response viewer to the SCANS tab's Request chain section (ui-v2/app.jsx) -- name/status/timing/extracted vars in a clickable header, full untruncated response body on expand. Recording, the visual macro editor, and Test macro were already closed by the 2026-08-26 waves (b36c77d, 4300b81); this closes the one piece those reconciles explicitly left open. state: partial -> present. Verified via GitHub Actions run 33036681345 (8/8 jobs green, including both the Windows and Linux NullockApp builds) since this cloud session cannot build Qt/C++ locally."},{"a":"sequencer","f":"Cookie jar honors cookie domain scope (Domain attribute, host-only vs domain cookies, subdomain matching)","s":"partial","i":"high","e":"days","g":"`Set-Cookie: SESSION=...; Domain=.example.com` from www.example.com is never sent to api.example.com. The workaround is the manual copyTo button (session_manager.cpp:177), which the analyst must remember and which copies EVERY cookie for the host — over-sharing in the other direction, including cookies that were host-only by design.","w":"Confirmed by reading the attribute parser in full — `domain` is genuinely not one of the five handled keys, and I confirmed storage is exact-host.","v":"session_manager_logic.cpp:67-71 verbatim, the complete attribute switch: `if      (key == \"path\")     c.path     = val; else if (key == \"expires\")  c.expires  = val; else if (key == \"httponly\") c.httpOnly = true; else if (key == \"secure\")   c.secure   = true; else if (key == \"samesite\") c.sameSite = val;` — no domain arm; the attribute is parsed and then dropped on the floor. Storage: session_mana","o":"partial","r":"absent -> partial 2026-08-12: the gap's core deficiency ('domain is parsed and then dropped on the floor') is fixed -- parseSetCookie now records the Domain attribute into CapturedCookie.domain (lowercased, a single leading '.' stripped, empty => host-only) and a pure RFC 6265 5.1.3 domainMatches(cookieDomain, reqHost) predicate is implemented with a real label boundary (evil-example.com does NOT match example.com) + IP-literal exact-only handling, unit- + mutation-tested (dropping the '.' boundary fails the label-trick case). NOT yet a full close: injectInto still does an exact-host lookup -- wiring domain-aware, DETERMINISTIC (m_byHost is a QHash) multi-host cookie collection plus the RFC 6265 5.3 Domain-vs-origin-host validation into injection is the remaining architectural step."},{"a":"sequencer","f":"Cookie jar expiry handling (Expires / Max-Age respected; expired cookies dropped, session cookies distinguished)","s":"present","i":"medium","e":"hours","g":"None -- Max-Age + Expires are parsed to an absolute expiry (cookieExpired predicate), ENFORCED at capture (an already-expired Set-Cookie deletes the stored cookie) and at inject (expired cookies are skipped), with session-vs-persistent surfaced to the UI. Historical note: a logout via `Set-Cookie: SESSION=; Expires=Thu, 01 Jan 1970...` happens to work because the name-keyed merge (session_manager.cpp:72-80) overwrites the value with empty — but `Max-Age=0` is not understood as a deletion, and session-vs-persistent cookies are indistinguishable in both the store and the UI.","w":"Confirmed as stub — the field is captured and surfaced but never consulted. I traced the full inject predicate set: exactly two filters, neither temporal.","v":"Captured as an opaque string, session_manager_logic.cpp:68 `else if (key == \"expires\")  c.expires  = val;` — never parsed to a QDateTime. Surfaced at control_server.cpp:4849 `co[\"expires\"] = c.expires;`. The complete inject filter set is session_manager.cpp:131-132: `if (!SessionLogic::injectableOverTransport(c, req.port)) continue; if (!SessionLogic::pathMatches(c.path, req.path)) continue;`. `gr","o":"present","r":"Cookie-jar expiry DONE. Pure foundation (39f6cf5, mutation-proven): Max-Age + Expires -> absolute expiry (RFC 6265 5.3, Max-Age wins), cookieExpired predicate, session-vs-persistent. Enforced (2a7729d): resolve on capture, delete an already-expired Set-Cookie (logout), skip expired cookies on inject, surface persistent/expiresEpoch to the UI. Pure logic unit-tested; QObject inject/capture wiring gauntlet-verified (not unit-testable, cf. #194)."},{"a":"sequencer","f":"Cookie jar and session rules persist in the project file / user settings across restarts","s":"present","i":"high","e":"days","g":"Cookie jars and session rules persist per project. Cookie changes autosave every two seconds and after shutdown workers drain; session-rule edits save when applied. Failed workspace writes remain visible and block project switching. Transient extracted session variables are intentionally cleared when changing projects.","w":"Cookie jars and session rules persist per project. Cookie changes autosave every two seconds and after shutdown workers drain; session-rule edits save when applied. Failed workspace writes remain visible and block project switching. Transient extracted session variables are intentionally cleared when changing projects.","v":"Src/App/app.cpp saveWorkspaces; Src/Core/Storage/project_store.cpp saveSessionWorkspace; scripts/workspace_recovery_regression.py","o":"absent","r":"Cookie jars and session rules persist per project. Cookie changes autosave every two seconds and after shutdown workers drain; session-rule edits save when applied. Failed workspace writes remain visible and block project switching. Transient extracted session variables are intentionally cleared when changing projects."},{"a":"sequencer","f":"Session handling tracer (step-by-step log of which rules fired, which actions ran, and the request state after each)","s":"absent","i":"high","e":"days","g":"When an injection does not happen there are now at least seven distinct silent exits and no way to tell which one fired. Given the Repeater/Intruder/chain bypass and the port-443 Secure heuristic, this is the debugging tool the current design most needs — it would surface four of the defects in this report as observable behaviour rather than mystery.","w":"Confirmed: 0 hits for tracer, and the only introspection is the flattened variable bag. This assessment gets MORE important given what I found: I identified four additional silent-failure paths in this area (scope early-return, verbatim {{var}} injection, Secure-cookie port heuristic, chain-runner bypass), none of which produce any diagnostic.","v":"Signals: session_rules.hpp:166-170 `signals: void rulesChanged(); void variablesChanged(); void macrosChanged(); ... void sessionReauthed(const QString &host, const QString &macro);` -- two more signals than before (macrosChanged, sessionReauthed), still none of them fire-grained per-rule/per-action. Sole introspection: session_rules.cpp:133-141 `variables()`, `// Flattened view for the UI/debug (later hosts win on a name collision).`. Silent, unlogged early exits: applyToResponse (session_rules.cpp:193 rs.isEmpty() return, :197 !enabled continue, :198 !matches continue, :199 empty key/var continue), applyToRequest (:259 rs.isEmpty() return, :263-266 four more continues), ingestVariables (:414 host/vars empty return), and three NEW ones in the SessionMacro re-auth path: runMacro (:442 macro-not-found/no-steps return), maybeReauth (:467 already-in-flight return, :469 cooldown return) -- none of these seven-plus branches produce any diagnostic output.","o":"","r":"Wave 0 register-accuracy audit: held at absent -- and, per the original 'why''s own framing, this gets MORE relevant, not less. Re-enumerated the silent-return sites in the now-nearly-doubled session_rules.cpp (239->488 lines): the SessionMacro/auto-reauth feature (items #72/159, #85/200) added THREE new unlogged early-exit branches (macro not found, already re-authing, cooldown) on top of the original set, and two new signals (macrosChanged, sessionReauthed) that are still coarse rulesChanged-style notifications, not a fired-rule trace. Grepped repo-wide for 'tracer'/'Tracer': 0 hits, confirming no such feature exists anywhere, not just in this subsystem. Claim holds; evidence substantially refreshed (old line citations no longer matched current code shape after the SessionMacro addition, not just shifted)."},{"a":"sequencer","f":"Platform authentication: per-host credentials for HTTP Basic, Digest, NTLMv1/v2 and Negotiate, applied automatically on 401","s":"absent","i":"high","e":"days","g":"Testing an intranet app behind NTLM or Negotiate is impossible — every request 401s. Basic-auth targets require hand-adding an Authorization header separately in each tool, and because session rules do not reach Repeater or Intruder, even a session-rule workaround would not cover them.","w":"Confirmed. I re-ran the greps and checked the two NTLM hits and the 33 \"Negotiate\" hits myself — the NTLM hits are a hash-format label, and none of the Negotiate hits are HTTP auth. Zero hits for WWW-Authenticate anywhere in Src/.","v":"The only NTLM reference is transcode.cpp:363 `case 32:  out << QStringLiteral(\"MD5\") << QStringLiteral(\"NTLM\") << QStringLiteral(\"MD4\"); break;` and transcode.hpp:43 (`32 hex -> MD5 / NTLM`) -- a hash-format identifier, not auth. `grep -rn WWW-Authenticate Src/`: 0 hits. `grep -rn platformAuth|basicAuth|DigestAuth|Proxy-Authorization Src/`: 3 hits, all in proxy_server.cpp/proxy_logic.cpp/.hpp and all about STRIPPING the hop-by-hop `Proxy-Authorization` header before forwarding (MITM proxy-credential hygiene), unrelated to authenticating to the TARGET. No 401-challenge handler exists in the HTTP client path.","o":"","r":"Wave 0 register-accuracy audit: held at absent. NTLM hash-label citation drifted transcode.cpp:299 -> 363, transcode.hpp:37 -> 43 (content unchanged). Re-ran the Proxy-Authorization grep and, unlike the original which reported 0 hits, it now returns 3 -- checked all three by hand: proxy_logic.cpp:150 and proxy_server.cpp:1305 plus a proxy_logic.hpp comment, all about the MITM proxy stripping ITS OWN hop-by-hop Proxy-Authorization header before relaying upstream, which is proxy-credential hygiene, not a per-host Basic/Digest/NTLM/Negotiate challenge-response mechanism for the TARGET application. WWW-Authenticate still 0 hits repo-wide. Claim holds; evidence refreshed including the corrected (non-zero but irrelevant) grep count."},{"a":"sequencer","f":"Client-side TLS certificates: per-host PKCS#12 / keystore for mutual-TLS targets","s":"absent","i":"medium","e":"days","g":"Any target requiring mutual TLS is untestable — there is no per-host keystore, no PKCS#12 import, and no upstream QSslConfiguration to attach one to.","w":"Confirmed. I enumerated every QSslCertificate/setLocalCertificate site in Src/ — the only cert-presentation code is the MITM listener's own leaf, and every other site is inspection of the PEER's cert.","v":"Sole presentation site, proxy_server.cpp:452-460: `QSslCertificate cert(leaf.certPem, QSsl::Pem); QSslKey key(leaf.keyPem, QSsl::Rsa, QSsl::Pem); ... cfg.setLocalCertificate(cert); cfg.setPrivateKey(key);` -- the cert Nullock presents TO the browser (the MITM leaf), unchanged in content from the prior audit. Every other hit is peer-side inspection: tls_inspect.cpp:99 `const QSslCertificate cert = sock.peerCertificate();`, :187 `QSslCertificate::verify(sock.peerCertificateChain(), req.host);` (both unchanged line numbers). `grep -rn pkcs12|PKCS12 Src/`: 0 hits.","o":"","r":"Wave 0 register-accuracy audit: held at absent. The MITM leaf-presentation site drifted proxy_server.cpp:398-406 -> 452-460 (content identical); both tls_inspect.cpp peer-inspection citations (:99, :187) did NOT drift. Re-ran the pkcs12/PKCS12 grep repo-wide: still 0 hits. No per-host client-cert keystore, no QSslConfiguration consumer for a CLIENT identity when Nullock is itself connecting outbound (Repeater/Intruder/chain/crawler/audit HttpClient sends). Claim holds; evidence refreshed."},{"a":"sequencer","f":"Recorded login sequences (browser-recorded login replayed by the scanner) for authenticated crawl/audit","s":"partial","i":"medium","e":"months","g":"HTTP scanners and the crawler now use enabled cookies, tool-scoped session rules and recorded HTTP login macros, including expiry-triggered refresh. Browser interaction recording and JavaScript-driven login execution remain unavailable.","w":"The shared HTTP client applies Scanner-scoped session rules, captures rotated tokens/cookies and refreshes configured expired sessions. Explicit identity comparisons and recorded macro requests retain their own credentials.","v":"Src/Core/Networking/networking.cpp; session_rules.cpp; crawler.cpp; scripts/scanner_sessions_regression.py; Tests/session_rules/session_rules_test.cpp","o":"","r":"HTTP authenticated scan workflows verified, including form CSRF replacement, compressed token extraction, refresh cooldown, request fidelity and project isolation. Browser login execution remains a separate gap."},{"a":"sequencer","f":"Application login credentials (username/password pairs supplied to the scanner, which finds and drives the login form)","s":"absent","i":"medium","e":"weeks","g":"Absent. No credential input to any scanner, and no form-finding logic to drive one with (there is no HTML form parser in the extraction layers either — see the form-field item).","w":"Confirmed. The username/password hits in Src/Core/Networking/*.hpp are all prose or payload text; no configuration struct anywhere accepts credentials for a scan.","v":"Hits are host_header.hpp (password-reset poisoning prose), nosql_injection.hpp (an auth-bypass payload string), sequencer.hpp (a comment listing token kinds) -- confirmed still prose-only, no code reference. No scan-config struct has credential fields anywhere in Src/Core/Networking/ (SessionMacro's ChainRunner::Step, session_rules.hpp:96, carries only raw recorded HTTP bytes -- no username/password fields). The audit entry point (control_server.cpp `/api/audit/run`, in kActivePaths at :3263, handler at :7802) takes a target host, not credentials.","o":"","r":"Wave 0 register-accuracy audit: held at absent. kActivePaths/`/api/audit/run` drifted :2953 -> kActivePaths set starting :3256 (path listed at :3263) / handler at :7802 (both moved with the file's overall growth). Specifically checked the new SessionMacro struct (session_rules.hpp:88-102, added since the last audit) for a credentials field, since it is the newest 'login-adjacent' addition in this area: it carries `name`, `sessionHost`, `steps` (raw recorded ChainRunner::Step requests), `loggedOutStatus`, `loggedOutBodyRegex` -- no username/password fields, and nothing drives a login FORM (it replays already-recorded raw HTTP requests verbatim, it does not find-and-fill a form). Claim holds; evidence refreshed to also rule out the newest candidate location."},{"a":"platform","f":"Collaborator: HTTP interaction capture","s":"present","i":"high","e":"hours","g":"None for HTTP capture itself. (Reachability of the hits is a separate item — see Collaborator client.)","w":"Re-read Src/Core/APIs/Oast/oast_server.cpp in full. Every quoted line is real and at the cited offsets, and the wiring at app.cpp:877-882 exists verbatim. This one holds unchanged — it is a real socket server, not a lookalike: it parses the request line and headers, enforces slowloris deadlines on both header and body reads, extracts the token from BOTH the Host header and the path, and records so","v":"oast_server.cpp:111 `void OastServer::handleClient(QTcpSocket *socket) {`; :182-189 `hit.token = extractToken(hostHdr, path); hit.sourceIp = socket->peerAddress().toString(); ... hit.bodyPreview = QString::fromUtf8(rest.left(4096));`; :199-205 `static const QByteArray kBody = \"nullock-oast: callback received\\n\"; ... resp += \"HTTP/1.1 200 OK\\r\\n\";`. Wired at Src/App/app.cpp:877-878 `Nullock::Core::","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Collaborator: DNS interaction capture","s":"present","i":"medium","e":"hours","g":"DNS interactions are counted and correlated but never stored or listable — there is no way to inspect a DNS callback's source IP, qname or timing after the fact. Plus A-only answers regardless of QTYPE (no AAAA/TXT/CNAME/NS).","w":"DOWNGRADED. The capture path is real and does feed the correlator, but the first pass missed the bigger of the two defects. DnsSink stores NO hits at all — it has only a counter, not a list. So a DNS callback can auto-confirm a finding, but the raw interaction record is unrecoverable: /api/oast/poll reads `m_wiring.oast->hitsSince(...)`, which is the HTTP sink's ring buffer. A DNS-only Log4Shell c","v":"Src/Core/APIs/Oast/dns_sink.hpp:67 `int m_hitCount = 0;` — the ONLY hit state (compare oast_server.hpp:90 `QList<OastHit> m_hits;  // ring; we cap at kMaxHits`). dns_sink.cpp:114-115 `++m_hitCount; emit hitReceived(hit);` — emit-and-forget, nothing retained. dns_sink.cpp:63-64 `resp.append(char(0xC0)).append(char(0x0C)); resp.append(char(0x00)).append(char(0x01)); // TYPE A` with no QTYPE branch a","o":"partial","r":"partial -> present. Both defects fixed. (1) STORAGE+LISTING (the audit's 'bigger defect'): DnsSink gained a mutex-guarded OastHit ring (cap kMaxHits, own monotonic id space, mirrors OastServer) + hitsSince(sinceId), exposed at GET /api/oast/dns/poll?since=<id> -- a DNS-only callback (Log4Shell with LDAP egress firewalled, blind SSRF/XXE) is now listable with its qname, resolver source IP, timing, and record type, with a strictly-after cursor. (2) QTYPE: DnsLogic::ParsedQuery now parses qtype + a pure qtypeName(); the responder answers the type asked -- A for A/ANY, AAAA for AAAA, protocol-correct NODATA (NOERROR ANCOUNT=0) for anything else -- instead of always a mistyped A record; the interaction is logged regardless of qtype (token is in the QNAME). dns_logic_test 58/58 incl. qtype parse (A/AAAA/TXT/high-byte-257) + qtypeName, +2 mutations (parse reads QCLASS not QTYPE; qtypeName(28) mis-map). e2e vs the live UDP sink (14/14): listable w/ qname+sourceIp, cursor strictly-after, A->A, AAAA->AAAA, TXT->NODATA, every qtype logged. ctest 99/99, probe_smoke 156/156. NB the separate Collaborator-TAB item's 'Interactions table' still needs a ui-v2 panel to render these DNS rows (concurrent-agent lane); the backend list they need now exists."},{"a":"platform","f":"Collaborator: automatic scan-check integration and interaction-to-issue correlation","s":"present","i":"high","e":"hours","g":"","w":"Re-read Src/Core/APIs/Oast/oast_correlator.cpp end-to-end (85 lines) and the registration sites. Confirmed with no downgrade, and it is genuinely Burp-equivalent rather than a lookalike: registry is mutex-guarded, deduped via m_confirmed, bounded at 50k, and the kind is derived from the registered probe class so log4shell/xxe/rce callbacks each land as their own enriched finding. The register-befo","v":"oast_correlator.cpp:57 `const QString kind = baseKind + \"-confirmed\";`; :76-78 `baseKind.startsWith(\"log4shell\") || baseKind.startsWith(\"rce\") ? QStringLiteral(\"critical\") : QStringLiteral(\"high\");`; :80-81 `m_scanner->reportFinding(origin.rowId, severity, kind, summary, evidence, origin.host, origin.url);`. Registration-before-fire verified at control_server.cpp:2252-2264 `// Register BEFORE firi","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Collaborator: private server deployment","s":"present","i":"high","e":"days","g":"None -- the app now points at a remote nullock-oast via --oast-remote=URL --oast-remote-key=KEY (mint + poll proxied through the same correlator), completing the deploy-a-sink + use-it-from-the-desktop loop.","w":"Re-ran the grep myself across Src, ui-v2 and browser-ext rather than trusting it. Confirmed: OAST_ADMIN_KEY and X-Oast-Key appear ONLY inside Src/Tools/oast_server_main.cpp. There is no client. I also confirmed the desktop app unconditionally constructs its own in-process sink with no remote branch, so the 'partial' is correct and the gap statement is accurate.","v":"Src/Tools/oast_server_main.cpp:141 `if (QString::fromLatin1(l.left(c)).compare(\"X-Oast-Key\", Qt::CaseInsensitive) == 0)`; :144 `if (adminKey.isEmpty() || key != adminKey) { sendJson(s, 401, ...` ; :149 `if (method == \"GET\" && path == \"/poll\")`; :156 `if (method == \"POST\" && path == \"/mint\")`. Client side absent — Src/App/app.cpp:877 `Nullock::Core::OastServer oast;` is the only construction and ta","o":"present","r":"The deployable standalone sink (nullock-oast: POST /mint, GET /poll, X-Oast-Key) already existed; client mode completes the loop. OastServer::startRemote(url, key) (--oast-remote / --oast-remote-key) points the DESKTOP app at a remote sink: mint proxies to POST /mint, a poll timer pulls GET /poll and re-emits hits through the same correlator. Verified end-to-end (mint on remote -> callback on remote -> hit polled back). Falls back to the local sink if unreachable."},{"a":"platform","f":"Notes (free-text engagement notes stored in the project)","s":"present","i":"medium","e":"hours","g":"None -- a Notes editor now lives in the Scope tab (tabs.jsx ScopeTab): a textarea bound to scope.notes, dirty-tracked so a mid-typing snapshot poll never stomps unsaved edits, saved on blur / Ctrl+Enter / an explicit SAVE button via the pre-existing NL.actions.scopeSetNotes -> POST /api/scope/notes. Still a single project-wide blob -- per-host/per-issue/per-request notes remain out of scope, as originally flagged.","w":"Closed 2026-08-11: the backend setter (project_store.cpp setNotes/saveMetadata) and the client action (real-data.js scopeSetNotes) were already wired to /api/scope/notes; the only gap was a UI consumer. Added one in the Scope tab next to the existing in/out glob columns, reusing the tab where scope.notes already lives in app state.","v":"ui-v2/tabs.jsx ScopeTab -- new notes textarea + SAVE control calling dispatch({type:\"scope-set-notes\"}); ui-v2/app.jsx reducer case \"scope-set-notes\" calls act(\"scopeSetNotes\", value) -> NL.actions.scopeSetNotes (real-data.js:141, POST /api/scope/notes); Src/Core/Storage/project_store.cpp:335-338 setNotes persists via saveMetadata.","o":"present","r":"Scope-tab Notes editor + Update-check banner batch: adds the missing UI consumer for the already-complete scopeSetNotes/setNotes path."},{"a":"platform","f":"Project files: disk-backed project with save/restore of engagement state","s":"partial","i":"medium","e":"days","g":"Traffic + scope + M&R rules survive restart; nothing else. A directory of files, not a portable project file. No save-copy-as, rename, delete or compaction.","w":"Read saveMetadata() in full. The claim is exactly right and I can now enumerate the persisted set definitively: v, name, notes, created, updated, inScope, outOfScope, rules — and nothing else. Streaming replay of history.ndjson on open is real. 'partial' confirmed.","v":"Src/Core/Storage/project_store.cpp:359-403 ProjectStore::saveMetadata() -- the persisted set is far larger than the last audit found: v, name, notes, created, updated, inScope, outOfScope, rules, repeater, interceptRules, interceptAutoContentLength, interceptAutoFixNewlines, sessionMacros, advancedScope, acceptInvalidUpstreamHosts, sessionRules, cookieJar, suppressedKinds, falsePositiveKeys, severityOverrides, deletedKeys -- one project.json write per save. control_server.cpp /api/project/list (:10895), /api/project/open (:10906) and /api/project/create (:10911) are still the complete project-management surface: `grep -n \"renameProject|deleteProject|copyProject|compact\" Src/Core/Storage/project_store.hpp`: 0 hits.","o":"","r":"Wave 0 register-accuracy audit: held at partial, but the evidence needed a real correction, not a line refresh. The prior evidence's central claim -- \"the persisted set: v, name, notes, created, updated, inScope, outOfScope, rules -- and nothing else\" -- is now false: saveMetadata() (project_store.cpp:359-403) has grown to also persist repeater state, intercept rules and settings, session macros, advanced scope, accept-invalid-hosts, session rules, the cookie jar, and finding-triage state (suppressed kinds, false positives, severity overrides, deleted keys) -- ten fields the original evidence said did not exist. This is a substantial expansion of what survives a restart. The gap survives regardless: I checked project_store.hpp for rename/delete/copy/compact and found none (0 hits), and control_server.cpp's project surface is still exactly list/open/create -- no save-copy-as, no rename, no delete, no compaction, and it is still a directory of files (project.json + history.ndjson + findings), not a single portable project file. State holds at partial; evidence corrected to stop understating what persists."},{"a":"platform","f":"Project templates / scan configuration presets applied at project creation","s":"partial","i":"medium","e":"hours","g":"extensionsEnabled is the sole remaining schema-fidelity gap: a template promising to enable an extension does nothing, since extensions currently load globally from the app-data dir and there is no per-project enable set to write into. `rules` is NOT dropped -- create-from-template applies it (see reconciled 60cf588 below); a prior audit pass re-stated the pre-fix 'silently drops both' language after that fix had already shipped, which this pass corrects. GET /api/project/templates and POST /api/project/create-from-template are both ui-v2-reachable via Settings' Projects card (template picker + description hint + 'Create from template' button).","w":"Re-read the live create-from-template handler against the gap/why text above it and found them stale: they still said 'rules and extensionsEnabled ... silently drops both' even though the 2026-08-19 reconciled note directly beneath them (60cf588) already documents rules being applied via ruleFromJson/setRules, and the current source confirms it (control_server.cpp:5511-5517). Corrected the gap/why to match the reconciled history instead of contradicting it -- audit-register fix only, no code change this pass. 'partial' unchanged: extensionsEnabled is still genuinely unenforced.","v":"control_server.cpp:5502-5528: `m_wiring.projectStore->setInScope(inS); m_wiring.projectStore->setOutOfScope(outS); m_wiring.projectStore->setNotes(...);` followed by `QList<Nullock::Proxy::MatchReplaceRule> tplRules; for (const QJsonValue &rv : tplObj.value(\"rules\").toArray()) tplRules.append(ruleFromJson(rv.toObject())); m_wiring.projectStore->setRules(tplRules);` -- rules ARE parsed and applied. Then: `QJsonArray wantExt = tplObj.value(\"extensionsEnabled\").toArray();` is read only to echo back in the response (`extensionsRequested`), never enforced -- comment at :5519-5523 explains why (no per-project extension-enable set exists; semantics of 'ensure on' vs 'only these' are ambiguous). templates/projects/oauth-review.json ships a real non-empty `rules` array (1 rule) confirming the schema is genuinely exercised, not just theoretical. ui-v2 reachability unchanged from the 69ab754/60cf588 reconciles: ui-v2/real-data.js `projectTemplates()`/`projectCreateFromTemplate()`; ui-v2/app.jsx SettingsTab's Projects card.","o":"partial","r":"REGISTER FIX (stays partial, no code change). The gap/why fields had gone stale: they still claimed create-from-template 'silently drops both' rules and extensionsEnabled, but the 60cf588 reconciled note directly below (2026-08-19) already documents rules being applied, and control_server.cpp:5511-5517 confirms it live today (tplRules parsed via ruleFromJson, applied via setRules -- unchanged since 60cf588, no regression). Only extensionsEnabled remains a real gap (echoed as extensionsRequested, never enforced -- no per-project extension-enable set exists in ExtensionsApi/ProjectStore, confirmed by grep). Rewrote gap/why/evidence to match live source instead of contradicting the reconcile history beneath them; state and audited_state stay partial, unchanged. python3 scripts/parity_report.py --check green after the edit."},{"a":"platform","f":"Reporting: HTML issue report","s":"present","i":"high","e":"hours","g":"Report content is complete; delivery is not. No button, no menu, no pasteable URL — requires `curl -X POST -H 'X-Nullock-UI: 1'`. The Qt report pane is an 8-line placeholder.","w":"DOWNGRADED. The generator itself is real and better than the first pass implied — I read all ~170 lines and confirmed the grade badge, severity cards, stacked bar, scope block, per-finding CVSS/CWE/OWASP/compliance/fix table, and universal toHtmlEscaped(). But no user can produce it. I grepped ui-v2 recursively, Src/App/app.qml, and the docs for `/api/report/html|/api/report/build|/api/report/json","v":"Generator real: control_server.cpp:5047 `if (path == \"/api/report/html\") {` with `auto esc = [](const QString &s) -> QString { return s.toHtmlEscaped(); };` (5048) and the finding table at 5176-5200. Unreachable: `grep -an \"report/html\\|report/json\\|report/build\\|/api/report\" ui-v2/ -r` → no output; same grep over Src/App/app.qml → no output. Not allowlisted — control_server.cpp:1656-1685 isReadPa","o":"partial","r":"REPORTING tab adds Download Markdown / Download HTML buttons (fetch POST -> blob download) so the HTML/Markdown report is one click, no curl needed."},{"a":"platform","f":"Reporting/exports beyond Burp: SARIF, CycloneDX SBOM, Postman collection, OpenAPI, HAR, nmap XML, machine-readable master JSON","s":"exceeds","i":"medium","e":"hours","g":"","w":"CONFIRMED, and the first pass actually UNDERSOLD the UI story while getting its line numbers stale. Every endpoint exists (line numbers have drifted ~140 lines since their pass; I re-located each). More importantly, they claimed 'exactly one export button at app.jsx:809' — that is wrong twice over: app.jsx:809 is a `placeholder=\"csrf strip\"` input, and there are THREE working download buttons. All","v":"control_server.cpp:5748 `// GET /api/export/nmap-xml`; :5806 `// GET /api/export/sarif  -> findings as SARIF v2 (CI-friendly)`; :5875 `// GET /api/export/sbom  -> CycloneDX 1.5 SBOM`; :6009 `// GET /api/export/postman`; :4670 `if (path == \"/api/openapi/export\")`; :5225 `if (path == \"/api/report/json\")`. Allowlisted at control_server.cpp:1682 `|| p.startsWith(\"/api/export/\")`. UI buttons: ui-v2/app","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Scan-to-scan issue delta (new vs fixed findings between runs)","s":"present","i":"medium","e":"hours","g":"None -- the ISSUES tab has a Baseline bar (Save baseline / Diff vs current / Clear) showing hasBaseline/savedAt/count status and, after a diff, the new/fixed/unchanged counts plus the new and fixed finding lists.","w":"Closed 2026-08-10: ui-v2/app.jsx IssuesTab wires /api/baseline/save|status|diff|clear (previously API-only, zero ui-v2 callers).","v":"ui-v2/app.jsx IssuesTab Baseline bar + diff panel; control_server.cpp:4116 save, :4172 status, :4184 clear, :4189 diff.","o":"present","r":"Issues/Baseline batch: Baseline bar in the ISSUES tab (save/status/diff/clear) closes the GUI-reachability gap."},{"a":"platform","f":"One-click browser proxy configuration + CA trust path (the onboarding job Burp's browser does)","s":"partial","i":"medium","e":"weeks","g":"Extension must be side-loaded unpacked; CA must still be installed into the OS/browser trust store by hand per-platform, despite the manifest claiming one-click. Not comparable to a browser that just works.","w":"Read manifest.json and background.js myself. The extension is real MV3 and genuinely flips chrome.proxy.settings. The CA endpoints are real too. But note the manifest's own description overpromises — it claims 'one-click installs the CA cert', which MV3 cannot do; there is no OS-trust-store path in the extension. Combined with side-loading in developer mode, 'partial' is correct.","v":"browser-ext/manifest.json: `\"permissions\": [\"proxy\", \"storage\", \"tabs\"]` and `\"description\": \"Routes browser traffic through a local Nullock proxy and one-click installs the CA cert...\"`. browser-ext/background.js:32-45 `await chrome.proxy.settings.set({ value: { mode: \"fixed_servers\", rules: { singleProxy: { scheme: \"http\", host: cfg.proxyHost, port: cfg.proxyPort }, bypassList: cfg.bypassList } }, scope: \"regular\" });`.","o":"","r":"Wave 0 register-accuracy audit: held at partial. manifest.json and background.js are byte-identical to the prior audit (same permissions, same description overpromise, same chrome.proxy.settings.set call at background.js:32-45, was :30-44 -- a 2-line drift from unrelated file changes). The extension still has no OS/browser CA trust-store installer and still requires developer-mode side-loading. No change."},{"a":"platform","f":"DOM Invader (runtime DOM-XSS: canary injection, sink tracing, prototype-pollution scan, postMessage/web-message interception, stack traces)","s":"partial","i":"high","e":"months","g":"No runtime instrumentation: no canary tracing, no prototype-pollution gadget scan, no postMessage interception, no stack traces. Blind to SPA-framework-generated sinks. Produces leads, not confirmations.","w":"Read extensions/dom_taint.js. The source/sink vocabularies and the one-hop-with-two-propagation-passes dataflow are real, not co-occurrence matching, and the file's self-declared limits are verbatim as quoted. This is a legitimately useful lead generator, so it is more than a stub — but it shares no mechanism with DOM Invader (no runtime instrumentation of any kind, confirmed by the absence of any","v":"extensions/dom_taint.js:5-10 `Burp Pro's DOM Invader runs *inside* the browser and instruments the live DOM at runtime. Nullock is a proxy, so we can't hook the page -- but every script the app serves passes through us, and we can analyse it statically.`; :54 `{ re: /\\.\\s*innerHTML\\s*=/g, name: \"innerHTML\", cls: \"html\" },`. File is 256 lines total, source/sink tables and one-hop dataflow unchanged.","o":"","r":"Wave 0 register-accuracy audit: held at partial. dom_taint.js drifted 2 lines from a version-comment addition (\"nullock:version 0.2.0\" at :3) but the self-declared-limits quote, the source/sink regex tables and the one-hop dataflow logic are unchanged. Still no runtime instrumentation, no canary tracing, no prototype-pollution gadget scan, no postMessage interception, no stack traces -- confirmed no new files or functions under extensions/ or Src/ implementing any of those. Claim holds."},{"a":"platform","f":"Global search across all tools' items","s":"partial","i":"high","e":"days","g":"Proxy history only — Repeater, Intruder, issues, sitemap unsearchable. Worse, the 500-row cap scans the OLDEST 500 rows of the in-memory window, so recent traffic is invisible to search on any busy engagement, and the SQLite index holding the full history is never consulted.","w":"State confirmed, but the gap is materially WORSE than the first pass described and I want that on the record. They said the 500-row cap means 'the first 500 rows'. I checked ProxyModel::addResponse: rows are APPENDED at the end and evicted from the FRONT. So index 0 is the OLDEST retained row, and the search loop runs `row < min(n, 500)` from index 0. On any engagement past 500 requests, search co","v":"control_server.cpp:1755 `constexpr int kSearchRowCap     = 500;`; :1803 `const int rowLoopMax = std::min(n, kSearchRowCap);`; :1806 `for (int row = 0; row < rowLoopMax && hits.size() < limit; ++row) {` — ascending from 0. Ordering proof at Src/FrontEnd/GUI/Models/Proxy/proxy_model.cpp:70-73 `const int row = static_cast<int>(m_entries.size()); beginInsertRows({}, row, row); m_entries.append({ m_nex","o":"","r":"Both halves of the audited gap addressed; stays partial only because two of the FIVE sources remain. (1) The 500-row-cap-scans-oldest bug the audit flagged as 'materially worse' was already replaced (before this) by a newest-first scan under a wall-clock budget -- no fixed row cap, recent traffic searched first. (2) This commit fixes the SCOPE half: /api/search was proxy-history-only; the excerpt/limit/regex-safety logic is now a source-tagged addHits(source,id,where,text) shared by every store, and TWO new sources join under the SAME wall-clock budget + ReDoS guards -- Repeater tabs (request+response, honouring where=req|resp) and Issues (each finding's summary/evidence/url/host/kind/severity, on where=both). Every hit now carries a `source` field (proxy|repeater|issue). VERIFIED e2e over the live control API: a shared marker seeded into proxy history + a Repeater tab + a passive finding is returned tagged from all three sources; where=req excludes issues but still finds proxy+repeater; a source-unique marker yields only that source; every hit carries a source tag (7/7). Gauntlet ctest 98/98 + probe 156 (proxy-search regression intact). REMAINDER (-> stays partial): Intruder attack results and the site-map are not yet wired as search sources (the addHits seam makes each a small addition), and the SQLite full-history index is still not consulted for out-of-window rows."},{"a":"platform","f":"Resource pools (named concurrency/throttle pools assignable per task)","s":"partial","i":"medium","e":"days","g":"No named pool object and no cross-tool budget. Cannot say 'this fragile target gets 1 concurrent request across every tool' — three tools running at once still hammer the target independently.","w":"Grepped for the concept under every synonym I could think of (resourcePool, namedPool, poolName, sharedPool, globalThrottle). Exactly one hit in the entire codebase, and it is a comment on a per-tool field. Every other tool takes its own ad-hoc throttle argument. Confirmed partial — the throttling exists, the pool abstraction does not.","v":"`grep -rn \"resourcePool|namedPool|poolName|sharedPool|globalThrottle\" Src ui-v2`: 0 hits. Src/Core/Networking/intruder.hpp:190 `// Request-pool config (Burp-parity \"resource pool\"): how many requests may be` -- still the only occurrence repo-wide, still a comment on a per-tool field. Per-tool knobs: control_server.cpp:1672-1673 `intruder[\"concurrency\"] = m_wiring.intruder->maxConcurrency(); intruder[\"throttleMs\"] = m_wiring.intruder->throttleMs();`; crawler takes its own at :4728 `const int throttle = bodyJson.value(\"throttleMs\").toInt(200);`.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Same single repo-wide hit for the \"resource pool\" concept (intruder.hpp, drifted :155 -> :190), still just a comment on a per-tool field. Confirmed each tool (Intruder, crawler, deep-audit) still carries its own independent concurrency/throttle knob with no shared, named, cross-tool budget object. Claim holds; evidence line numbers refreshed."},{"a":"platform","f":"Burp REST API (service toggle, bind address, multiple named API keys, /v0.1/scan launch + status)","s":"exceeds","i":"low","e":"days","g":"Single shared bearer token rather than multiple revocable named keys; no self-describing OpenAPI/Swagger for its own endpoints (it can generate OpenAPI for targets, not for itself).","w":"Verified the security-critical half by reading app.cpp directly rather than trusting the quote. The token plumbing, the off-loopback refusal, the read/write method split and the CSRF guard are all real and correctly ordered (token check precedes CSRF, so scripted clients with a bearer token bypass the browser-only guard). The endpoint surface is genuinely far larger than Burp's /v0.1. 'exceeds' st","v":"Src/App/app.cpp:1308-1310 `QString apiToken = qEnvironmentVariable(\"NULLOCK_API_TOKEN\"); if (apiToken.isEmpty()) apiToken = flagValue(argc, argv, \"--api-token\"); controlServer.setApiToken(apiToken);`; :1326-1338 off-loopback bind without a token refuses to start (`FATAL: --listen=... binds the control API off loopback, which requires a token ... Refusing to start.`). Ordering verified in control_server.cpp:1108-1115 (bearer-token check) precedes the CSRF guard at :1143-1160 (`if (!tokenValid && !ControlLogic::isRequestAuthorized(...))`) -- a valid token skips the CSRF/Origin check entirely, confirming scripted clients bypass the browser-only guard via the token alone.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Headless operation (run without a display, for containers/CI)","s":"present","i":"high","e":"hours","g":"","w":"Re-read app.cpp around the flag and the app-class selection. Both quotes are verbatim and correct, and I confirmed the consequence they imply: QCoreApplication means no QPA platform plugin and no display server is required, and the QQuickStyle call is guarded behind `if (!headless)`. The headless run loop with worker drain is real. Confirmed present.","v":"Src/App/app.cpp:568 `const bool headless = hasFlag(argc, argv, \"--headless\") || !scanUrl.isEmpty();`; :623-626 `if (!headless) { QQuickStyle::setStyle(QStringLiteral(\"Basic\")); }`; :631-634 `QScopedPointer<QCoreApplication> app(headless ? new QCoreApplication(argc, argv) : static_cast<QCoreApplication *>(new QGuiApplication(argc, argv)));`; :1133-1143 `if (headless) { const int rc = app->exec(); s","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"CI integration with meaningful exit codes (fail the build on findings at/above a threshold)","s":"exceeds","i":"high","e":"hours","g":"","w":"Read runGateScan in full plus all of ci_gate_logic.cpp. The fail-closed preflight is real and correctly reasoned — any complete HTTP response counts as reachable, only a transport failure trips it, and the only escape from exit 3 is an explicit fail-on=none. Threshold parsing defaults unknown/empty to 'high' rather than to 'never fail', which is the safe direction. The shipped Action is real. 'exc","v":"control_server.cpp:9613 `int runGateScan(const QString &url, const QString &failOn, bool ndjson) {`; preflight at :9646-9678 `const auto pr = probe.send(t.host, ...); if (!pr.ok) { ... return ug.exitCode; }`. Src/Core/Networking/ci_gate_logic.cpp:83-87 `// An explicit \"none\"/\"off\" means the operator opted out ... Everyone else fails CLOSED: not scanning is not passing.` and `r.exitCode = neverFail","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Machine-readable live event stream for automation","s":"exceeds","i":"medium","e":"hours","g":"","w":"Read the whole ndjson block. The context-object threading fix is real and the explanatory comment is verbatim; the rowId uses lastId() not rowCount() specifically so ids stay monotonic past the window cap, which means response and finding events remain joinable — that is a subtlety a lookalike would get wrong. Query stripping defaults to ON. Every write is followed by an explicit flush, which matt","v":"Src/App/app.cpp:1040-1048 `without a context object this lambda would be a DirectConnection and run there ... so the one-object-per-line NDJSON contract tears apart under load.`; :1036 `const bool includeQuery = hasFlag(argc, argv, \"--ndjson-include-query\");`; :1069 `e[\"rowId\"] = model.lastId();` guarded by the comment `lastId(), NOT rowCount()`; :1075-1076 `QTextStream(stdout) << QJsonDocument(e)","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Container/Docker distribution for headless + CI","s":"partial","i":"medium","e":"hours","g":"The build-docker CI job (added last wave) is now confirmed GREEN end-to-end: `docker build` succeeds and `docker run ... --help` starts cleanly, closing the 'self-declared unvalidated, nothing ever proves it builds' half of the prior gap for real (last wave had only wired the job in without a Docker daemon to pre-validate it -- its very first real run failed, five times in a row, on real bugs this wave root-caused and fixed one at a time). Still genuinely missing: no published/pushed image (a `docker pull` still isn't possible -- the file only builds locally or in CI, it is not a distribution channel yet) and the base images are pinned to a version tag (`ubuntu:22.04`) rather than a content digest, so a tag repoint could still silently change the build.","w":"Confirmed the build-docker job's first real run (commit 41710a4/e73e96a) had actually failed -- `conclusion: failure` on GitHub Actions, not yet checked at the time it was added. Root-caused and fixed five distinct real bugs, one CI round-trip (~15-20min each, no docker daemon in this cloud session to pre-validate any of them locally) at a time, all specific to a bare `ubuntu:22.04` container lacking things GitHub's hosted runner images ship pre-installed and CI's `jurplel/install-qt-action` (which the Dockerfile's raw `aqt install-qt` call approximates, not calls) papers over: (1) aqtinstall renamed the Linux desktop arch from `gcc_64` to `linux_gcc_64` as of Qt 6.7.0 -- the Dockerfile's pin to 6.7.3 needed the new name; (2) Ubuntu 22.04's apt cmake (3.22.1) is older than CMakeLists.txt's `cmake_minimum_required(3.24)` -- switched to installing cmake via pip; (3) `zlib1g-dev` was missing (Src/BackEnd/Proxy/CMakeLists.txt:83 `find_package(ZLIB REQUIRED)` on Linux, since Qt's Linux build has no ZlibPrivate); (4) `libfontconfig1-dev`/`libfreetype-dev`/`libdbus-1-dev` (+ runtime counterparts) were missing -- libQt6Gui.so/libQt6DBus.so need them at link and load time; (5) FrontEndGUI (Src/FrontEnd/GUI, a `qt_add_qml_module` target -- the one SHARED lib in an otherwise all-STATIC Src/ tree) was never copied into the runtime image at all, so NullockApp couldn't even start -- switched the build stage to `cmake --install --component Runtime` to reuse the project's own existing install(TARGETS FrontEndGUI ...) + INSTALL_RPATH \"$ORIGIN\" rule (root CMakeLists.txt:89-99, added originally for Linux AppImage packaging) instead of re-solving it ad hoc, which also replaced three separate hand-copies of ui-v2/templates/extensions with the same install prefix; (6) the runtime image was also missing most of the GLVND OpenGL dispatch stack (`libopengl0`/`libegl1`/`libgles2`) plus Mesa's actual llvmpipe/swrast software driver (`libgl1-mesa-dri`) -- QT_QPA_PLATFORM=offscreen still needs a working GL context for FrontEndGUI's Qt Quick scene graph, and GitHub's runners have no GPU. Each fix was verified against the specific error the prior push's CI run actually produced, not guessed preemptively (the one exception: the GL-stack fix bundled 3 packages at once given the ~18min-per-round-trip cost, reasoning from the observed GLVND split rather than guessing blind). The sixth push (commit 6f39fea) is the first to come back fully green: both the `docker build` step and the `docker run --rm nullock:ci --help` runtime smoke step show `conclusion: success` on GitHub Actions run 32611161443.","v":"GitHub Actions run 32611161443, job 'build Docker image': `docker build` step conclusion=success (01:46:14-02:01:51, ~15.5min), `runtime smoke (--help, no listeners/token required)` step conclusion=success; Dockerfile (linux_gcc_64 arch, pip-installed cmake, zlib1g-dev/libfontconfig1-dev/libfreetype-dev/libdbus-1-dev in the build stage, `cmake --install build --component Runtime` instead of manual COPY of individual build-tree paths, libopengl0/libegl1/libgles2/libgl1-mesa-dri + libfontconfig1/libfreetype6/libdbus-1-3 in the runtime stage); root CMakeLists.txt:89-99 (the pre-existing install(TARGETS FrontEndGUI ...) + INSTALL_RPATH \"$ORIGIN\" rule this wave's fix reuses rather than re-solving); Src/BackEnd/Proxy/CMakeLists.txt:79-85 (the Qt6::ZlibPrivate-unavailable-on-Linux fallback that needs system zlib); no registry push step anywhere in the repo's workflows (grep for `docker push`/`docker/build-push-action` across `.github/workflows/` is empty) -- no published image exists; Dockerfile:22,79 `FROM ubuntu:22.04` still tag-pinned, not digest-pinned.","o":"partial","r":"Confirmed last wave's build-docker CI job had actually failed on its first real run (never checked before), then root-caused and fixed five distinct real bugs across five CI round-trips (Qt6.7 aqtinstall arch rename, apt cmake too old, missing zlib1g-dev, missing fontconfig/freetype/dbus dev+runtime libs, FrontEndGUI.so never installed into the runtime image, missing GLVND+Mesa-software-driver GL stack) until the sixth push came back fully green -- both docker build and the --help runtime smoke check now pass on GitHub Actions. No published image and no digest-pinned base remain, honestly unaffected -- this closes the CI-validation gap for real, not just 'wired in and hoped', which is what the state stays 'partial' for."},{"a":"platform","f":"Burp Suite DAST / Enterprise Edition (server-side scanning platform: multi-site scheduling, RBAC, SSO, scan agents, Jira/ticketing integration, dashboards)","s":"partial","i":"low","e":"months","g":"Findings-only sync, last-write-wins, no users/roles/SSO, no scheduling, no scan agents, no ticketing, no web dashboard. A seed of an Enterprise story, not one.","w":"Read workspace_server_main.cpp's header. It is a real deployable binary with SQLite/WAL storage and it reuses the same finding identity key as baseline/diff, which is a genuine design win — but its own header names every missing Enterprise pillar. Confirmed partial and the gap statement is accurate.","v":"Src/Tools/workspace_server_main.cpp:13-21 `Auth: a single shared bearer key (X-Workspace-Key header or ?key=). Full OIDC/SSO + per-user roles is the separate design/enterprise-sso.md track; this MVP is \"shared team key\"` and `Sync: per-engagement monotonic seq; push upserts by identity key and bumps seq, pull returns everything with seq > since. Last-write-wins.`; endpoints `POST /api/ws/push, GET /api/ws/pull` (header comment :21).","o":"","r":"Wave 0 register-accuracy audit: held at partial. workspace_server_main.cpp's header is unchanged in substance (drifted 12-17 -> 13-21, same self-declared MVP scope: shared bearer key, last-write-wins sync). Still no users/roles/SSO, no scheduling, no scan agents, no ticketing integration, no web dashboard beyond the sync API itself. Claim holds."},{"a":"platform","f":"Diagnostics / crash reporting for support","s":"present","i":"low","e":"hours","g":"GUI-reachable now: a Diagnostics card in Settings lists crash/non-fatal reports (GET /api/diagnostics) and lets you view one before filing an issue (GET /api/diagnostics/report?name=), and recordNonFatal() is now actually called (extension-load failure, onUnload handler throw) instead of being dead code. Remaining short of a full support pipeline: still local-only, no upload/telemetry (a deliberate privacy choice, not a gap) and no in-app 'File a GitHub issue' deep link with the report pre-attached.","w":"Closed 2026-08-29: added GET /api/diagnostics (+ /report) surfacing CrashReporter::crashDir()'s report listing/content, a Settings > Diagnostics card consuming it, and wired recordNonFatal() into extensions_api.cpp's two real error sites so the mechanism the header doc always described actually produces a report.","v":"control_server.cpp /api/diagnostics + /api/diagnostics/report handlers; ui-v2/app.jsx Diagnostics() card (Settings tab); extensions_api.cpp recordNonFatal() calls at the evaluate()-error and onUnload-error sites.","o":"present","r":"Diagnostics view wave: GET /api/diagnostics[/report] + Settings Diagnostics card + recordNonFatal() wired into its first two real call sites."},{"a":"platform","f":"Update check / new-version notification","s":"present","i":"low","e":"hours","g":"None -- App() now reads snapshot.update and shows a dismissible corner banner (current->latest version, release notes excerpt, a VIEW RELEASE button honoring the Qt.openUrlExternally convention used elsewhere in the app) whenever update.available is true. Dismissal is remembered per latest version (localStorage, best-effort) so it does not reappear until a newer release ships. No in-app download/apply -- the banner links out to the release page, matching the backend, which only checks and reports.","w":"Closed 2026-08-11: backend was already complete (UpdateChecker + root[\"update\"] in every snapshot). Added the one missing piece -- a frontend consumer -- as a small dismissible UpdateBanner component in app.jsx, wired off the existing nl-update snapshot-poll event so no new polling was needed.","v":"ui-v2/real-data.js applySnapshot: NL.update = snap.update || {available:false,...}; ui-v2/app.jsx UpdateBanner component + App() showUpdateBanner/dismissUpdate wiring; control_server.cpp:1552-1563 root[\"update\"] = {available,currentVersion,latestVersion,releaseUrl,releaseNotes,publishedAt}.","o":"present","r":"Scope-tab Notes editor + Update-check banner batch: adds the missing UI consumer for the already-complete UpdateChecker/root[update] path."},{"a":"platform","f":"Engagement tool: Generate CSRF PoC","s":"present","i":"medium","e":"hours","g":"None -- a CSRF POC button in the Proxy history / Site map DetailPane calls /api/csrf/poc and shows the generated HTML in an overlay with COPY and DOWNLOAD, ready to host on an attacker page. No technique selector (server auto-picks form vs fetch() PoC by content-type) -- a minor UI nicety, not a functional gap.","w":"Closed 2026-08-09: added NL.actions.csrfPoc(rowId) (POST /api/csrf/poc {id}) and a ⚔ CSRF POC button in DetailPane's row-action bar (ui-v2/proxy.jsx), reusing the existing CodecOverlay (extended with optional note + downloadName/DOWNLOAD-button props) to preview and save the generated PoC HTML.","v":"ui-v2/proxy.jsx DetailPane CSRF POC button + CodecOverlay note/downloadName props; ui-v2/real-data.js NL.actions.csrfPoc; control_server.cpp:3908 /api/csrf/poc handler (unchanged, already complete); request_export.cpp:50 csrfPoc() generator.","o":"present","r":"CSRF PoC wave: wired /api/csrf/poc into the GUI (Proxy history / Site map DetailPane), closing the last GUI-reachability gap."},{"a":"platform","f":"AI-assisted issue explanation / triage (Burp AI: Explain This, false-positive assessment)","s":"partial","i":"low","e":"hours","g":"A Triage button per finding in the ISSUES tab calls the endpoint and renders the model verdict (or the heuristic fallback text) inline. The verdict is now also cached to localStorage, keyed by the same finding-identity formula the backend already uses for its own per-finding flags (kind+U+001F+host+U+001F+url+U+001F+summary, matching FindingTriageLogic::findingKey) rather than the ephemeral row id, so it survives switching away from the ISSUES tab and back, and a full page reload -- closing the \"never persisted\" blocker. That persistence is honestly browser-local only, not a real per-project backend store: it does not sync across browsers/devices, is lost if site data is cleared, and is not scoped per-project the way Burp's own state would be. One blocker remains, unchanged: it still depends on an unbundled local Ollama instance serving qwen2.5:14b, with a silent heuristic fallback when that is not running.","w":"UPGRADED (partial, was already partial): ui-v2/app.jsx IssuesTab's doTriage() writes each completed verdict (model result or heuristic fallback) to a localStorage cache via saveTriageCacheEntry(), and a new hydration effect rehydrates React state for any currently-listed finding whose identity key is found in that cache on mount -- so a verdict computed before a tab switch (which previously unmounted IssuesTab and discarded its state) or before a page reload is shown again without re-querying the model. Re-clicking Triage on an already-triaged finding now just toggles the panel instead of re-fetching. Closes the persistence third of the prior gap; the Ollama dependency is unchanged, and the new persistence is explicitly client-local, not project-scoped -- both honestly disclosed above, not claimed fixed.","v":"ui-v2/app.jsx: findingIdentityKey()/loadTriageCache()/saveTriageCacheEntry() (localStorage key \"nl-triage-cache\"), IssuesTab's rehydration useEffect keyed on `findings`, and doTriage()'s cache-write + toggle-instead-of-refetch branch. Backend precedent for the identity formula: control_server.cpp:1362 `const QString fkey = FT::findingKey(f.kind, f.host, f.url, f.summary);` and Src/Core/Networking/finding_triage_logic.cpp:10-14 (QChar(0x1f) separator).","o":"partial","r":"Wave 2: persisted AI-triage verdicts to localStorage keyed by finding identity (matching the backend's own findingKey formula), closing the \"never persisted\" blocker; the Ollama dependency and the client-local (not per-project) nature of the new persistence remain honest partials."},{"a":"platform","f":"Collaborator: HTTPS interaction capture","s":"absent","i":"high","e":"days","g":"No TLS listener and no https:// payload form. Targets that only permit https:// egress (common in cloud SSRF and any app validating the scheme) can never call back.","w":"Re-ran the synonym hunt myself across the whole Oast directory for Ssl/ssl/https — zero hits. The listener is a plain QTcpServer and mintToken() emits only http:// in both URL forms, with no scheme parameter or branch. Confirmed absent.","v":"`grep -rni \"ssl|https\" Src/Core/APIs/Oast/*.cpp Src/Core/APIs/Oast/*.hpp`: 0 hits. oast_server.cpp:32 `m_server = new QTcpServer(this);`; :192 `const QString pathUrl = QString(\"http://%1:%2/oast/%3/cb\")...`; :199 `hostUrl = QString(\"http://%1.%2:%3/\").arg(tok, m_baseHost).arg(p);`.","o":"","r":"Wave 0 register-accuracy audit: held at absent. OAST directory unchanged in this respect (one new file since the last pass, oast_origin.hpp, is a data-struct extraction for the persistence feature reconciled separately under item #7/159 -- not a TLS listener). oast_server.cpp is still a plain QTcpServer with no SSL/TLS wrapping and both URL-minting sites emit http:// only (lines drifted 23->32, 76-77->192,199, content identical). Claim holds."},{"a":"platform","f":"Collaborator: SMTP / SMTPS interaction capture","s":"absent","i":"low","e":"days","g":"Email-header-injection / SMTP-relay OOB classes cannot be confirmed.","w":"Re-grepped case-insensitively across all of Src. Every hit is port-scanner service naming or banner classification — nothing that listens. No SMTP file exists in the OAST directory (which contains only dns_logic, dns_sink, oast_correlator, oast_logic, oast_server). Confirmed absent.","v":"`ls Src/Core/APIs/Oast/`: dns_logic.cpp/.hpp, dns_sink.cpp/.hpp, oast_correlator.cpp/.hpp, oast_logic.cpp/.hpp, oast_origin.hpp, oast_server.cpp/.hpp -- no SMTP listener. `grep -rni \"smtp\" Src` hits only port-scanner service classification (Src/Core/Networking/port_logic.cpp, Src/Core/Networking/scan_bridge.cpp) -- nothing that listens.","o":"","r":"Wave 0 register-accuracy audit: held at absent. The OAST directory listing grew by exactly one file since the last audit (oast_origin.hpp, the persistence-feature struct split from item #7/159 -- not SMTP-related). Every \"smtp\" grep hit across Src is still port-scanner banner classification, not a listener. Claim holds."},{"a":"platform","f":"Collaborator: hosted public server (zero-config, works out of the box)","s":"partial","i":"blocker","e":"weeks","g":"The app can now point at a hosted sink (--oast-remote), so OOB fires against real targets once you deploy nullock-oast. Remaining: a bundled zero-config public instance so it works with no setup -- ops, not code (the standalone sink already supports wildcard DNS + TLS).","w":"Confirmed, and this is correctly flagged as the blocker in this area. Both defaults are loopback, and I independently verified there is no hosted-service client (the OAST_ADMIN_KEY/X-Oast-Key grep matches only the standalone server binary). So out of the box every minted callback URL points at 127.0.0.1 and no blind-vuln class can ever fire against a real target without the user first standing up ","v":"Src/App/app.cpp:872-874 `const QString oastHost = flagValue(argc, argv, \"--oast-host\").isEmpty() ? QStringLiteral(\"127.0.0.1\") : flagValue(argc, argv, \"--oast-host\");`; oast_server.cpp:22 `m_baseHost = baseHost.isEmpty() ? QStringLiteral(\"127.0.0.1\") : baseHost;`; dns_sink.cpp:16-19 same loopback default for both baseHost and answerIp. No client: OAST_ADMIN_KEY / X-Oast-Key appear only in Src/Tool","o":"partial","r":"Client mode lands the app-side half: --oast-remote points the desktop app at a HOSTED nullock-oast so OOB fires against real targets. PARTIAL -- there is still no bundled zero-config public instance (the remaining piece is ops: run nullock-oast + wildcard DNS + TLS on a public box, all already supported by the standalone tool); until then the user supplies --oast-remote pointing at their own deployment."},{"a":"platform","f":"Collaborator client (dedicated panel: generate N payloads, copy to clipboard, poll now, view interaction detail)","s":"present","i":"high","e":"days","g":"None for the mint/poll/detail workflow or the blast spray. DNS-only interactions still never surface (DnsSink retains no hit list — see \"Collaborator: DNS interaction capture\"), so a pure-DNS Log4Shell confirmation stays invisible in this panel (the Blast section's Log4Shell checkbox fires the DNS-canary shots, but a hit only auto-confirms as a finding via the correlator — it will never appear as a row in this panel's own Interactions table).","w":"Closed 2026-08-09 (5d9c3c6): added a COLLABORATOR tab wiring /api/oast/mint and /api/oast/poll (mint payload, copy URL, poll now / auto-poll, click-through interaction detail). Extended 2026-08-10 (this wave): a Blast section in the same tab wires the previously-orphaned POST /api/oast/blast — target URL + SSRF/XXE/RCE/Log4Shell toggles, fires the spray, and renders the returned vector list (kind/note/token/callback URL) so the operator can see exactly what was fired. No backend change — the endpoint was already complete and allowlisted, only unreachable from the GUI.","v":"ui-v2/app.jsx CollaboratorTab (mint/poll/hit-table/detail-pane, plus the new Blast section); ui-v2/real-data.js NL.actions.oastMint/oastPoll/oastBlast; control_server.cpp:3593 POST /api/oast/mint returns {token,pathUrl,hostUrl,port,baseHost}; control_server.cpp:1927 GET /api/oast/poll returns {running,port,baseHost,hits:[{id,atMs,token,sourceIp,method,hostHeader,path,bodyBytes,userAgent,bodyPreview}]}; control_server.cpp:3619-3829 POST /api/oast/blast accepts {url,ssrf?,xxe?,rce?,log4shell?,paramNames?} and returns {fired,target,vectors:[{kind,note,token,callbackUrl}]} — every field the Blast section reads or sends matches.","o":"present","r":"Collaborator wave: dedicated COLLABORATOR tab wires /api/oast/mint and /api/oast/poll (mint payload, copy URL, poll now / auto-poll, click-through interaction detail). Extended this wave: a Blast section wires /api/oast/blast (SSRF/XXE/RCE/Log4Shell spray with target + toggles, fired-vector list). DNS-hit listing in the panel itself remains open, tracked separately under \"Collaborator: DNS interaction capture\"."},{"a":"platform","f":"Collaborator: interaction persistence across restarts","s":"partial","i":"medium","e":"hours","g":"The ACTIONABLE half now persists: OastCorrelator saves its token registry (token -> origin) and already-confirmed set to <appdata>/oast-interactions.json (atomic QSaveFile write on every register / new confirmation) and reloads it on startup, so an overnight callback that lands AFTER a restart still correlates to the token minted before it and emits its confirmed finding, and an interaction already reported is never re-reported. STILL in-memory-only: the raw hit LOG shown by /api/oast/poll (oast_server's capped m_hits ring) and DNS hits (never stored even in RAM) -- those remain lost across a restart.","w":"Partial-closed 2026-08-24: added OastLogic::serializeState/deserializeState (pure, versioned, Core-only) + OastCorrelator::setPersistPath (loads on set) / saveLocked (atomic write on each change), wired in app.cpp to an AppDataLocation file. This makes the correlation -- the part that turns a callback into a finding -- survive restarts. The raw poll-log ring + DNS-hit retention are a separate, larger change (QtNetwork sink TUs) and remain open.","v":"oast_logic.cpp:12 `QJsonObject serializeState(...)`; :36 `void deserializeState(...)`; oast_correlator.cpp:12 `void OastCorrelator::setPersistPath(const QString &path) {`, :26 `void OastCorrelator::saveLocked() const {`, called from registerToken (:46) and the onHit new-confirmation branch (:71 `else { m_confirmed.insert(hit.token); saveLocked(); }`); app.cpp:1186 `oastCorrelator.setPersistPath(oastDir + \"/oast-interactions.json\");`.","o":"","r":"Wave 0 register-accuracy audit: held at partial. All cited functions and call sites verified present and wired exactly as described (serializeState/deserializeState in oast_logic.cpp, setPersistPath/saveLocked in oast_correlator.cpp called from both registerToken and the onHit confirmation path, app.cpp wiring to AppDataLocation/oast-interactions.json). The raw poll-log ring and DNS-hit retention remain the larger, un-persisted half of \"interaction persistence\" as the original note said. Claim holds; this is the one platform-area item that already carried fresh, accurate evidence from its 2026-08-24 closing commit -- only the audit-trail (reconciled) block was missing."},{"a":"platform","f":"Logger (records HTTP traffic from ALL Burp tools and extensions, not just the proxy)","s":"partial","i":"high","e":"weeks","g":"Reclassify stub->partial: the prior 'Repeater traffic never lands in history' is now STALE — the /api/.../replay handler appends replayed responses to both history model and ProjectStore (control_server.cpp:2944-2946), and the crawler already logs (app.cpp entryLoaded->addResponse/appendEntry). What is genuinely still missing is (a) any tool-attribution/source column — ProxyModel::Roles has no Sou","w":"Reclassified stub -> partial (2026-08-02): triage + adversarial-verify agreed; keyed by stable roadmap id, area-guarded. See PARITY-BACKLOG.md.","v":"control_server.cpp:3154 `if (parts[1] == \"replay\")` -> :3214 `if (w.history) w.history->addResponse(r, resp);` / :3216 `if (w.projectStore) w.projectStore->appendEntry(r, resp);`. proxy_model.hpp:14-25 Roles {Id,Host,Method,Url,StatusCode,Mime,Params,Tls,Ip,Timestamp} -- still no source/tool role. intruder.cpp:124 `: QAbstractListModel(parent), m_model(historyModel) {}` -- its own separate model, not routed through proxy history.","o":"stub","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Logger: capture filters, view filters, custom columns, per-tool filtering","s":"absent","i":"high","e":"weeks","g":"No 'show me only Scanner traffic' or 'only requests my extension modified'. No custom columns, no script-based filters — and no source column exists to build them on.","w":"Confirmed. I read the filter builder in history_logic.cpp — the supported keys are exactly method/host/path/status/minSize/maxSize/sinceMs and nothing else, and I separately confirmed ProxyModel exposes no source/tool role, so per-tool filtering has no column to filter on even in principle. Confirmed absent.","v":"Src/Core/Storage/history_logic.cpp:43-103 buildFindQuery() builds the WHERE clause from a fixed key set only: method (:67-70), host LIKE (:71-81), path LIKE (:82-85), and addNumeric-driven status/minSize/maxSize/sinceMs (:86-89) -- nothing else. Unrecognized numeric keys are collected into `ignoredFilters` (:59 `if (ignoredFilters) ignoredFilters->append(key);`). No source column: Src/FrontEnd/GUI/Models/Proxy/proxy_model.hpp:14-25 `enum Roles { IdRole = Qt::UserRole + 1, HostRole, MethodRole, UrlRole, StatusCodeRole, MimeRole, ParamsRole, TlsRole, IpRole, TimestampRole };` -- no tool/source role.","o":"","r":"Wave 0 register-accuracy audit: held at absent. buildFindQuery's supported key set is unchanged (method/host/path/status/minSize/maxSize/sinceMs), only line numbers drifted (67-89 -> 43-103, the function itself starts at 43 not 67 -- a fuller citation, not a content change). ProxyModel's Roles enum is unchanged, still no source/tool role to filter on. No custom-column or script-filter mechanism exists anywhere in the history/proxy-model layer. Claim holds."},{"a":"platform","f":"Organizer (collect messages into collections, read-only copies + metadata)","s":"absent","i":"medium","e":"weeks","g":"No way to set aside interesting requests for later. Testers keep a second window or notepad.","w":"Confirmed. I did not just grep 'Organizer' — I hunted the synonyms this codebase might plausibly use: collection, bookmark, starred, pin/pinned, shortlist, savedItems. Every hit across Src and ui-v2 is unrelated (pinned certificates, pinned crawler ports, pinned CVE versions, Postman collections). No collection concept exists.","v":"`grep -rani \"collection\\\\b|bookmark|starred|pinned|shortlist|savedItems\" Src ui-v2` returns only unrelated matches: cert-pinning comments (proxy_server.cpp, proxy_server.hpp), a version-pinned CVE table (service_vulns_logic.cpp), a Postman-collection exporter (control_server.cpp:7187-7212, ui-v2/proxy.jsx:1048, 2289), and marketplace catalog integrity pinning (marketplace_logic.hpp). No collection/bookmark concept exists anywhere.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-ran the full synonym grep; the hit set shifted (a Postman-collection exporter and a service-CVE version-pin table are new-ish additions since the last pass) but every single hit is still an unrelated use of the words \"collection\"/\"pinned\". No way to set aside interesting requests into a saved, read-only collection exists in Src or ui-v2. Claim holds."},{"a":"platform","f":"Annotations: per-item Notes column and colour highlighting on Proxy history / any message table","s":"partial","i":"high","e":"days","g":"Other message tables and global report formats do not yet share this annotation store; Proxy history and Site map workflows are implemented.","w":"Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action.","v":"Src/Core/Storage/project_store.cpp (historyAnnotations, annotateHistory, HAR import/export); Src/BackEnd/Control/control_server.cpp (/api/history/annotations, /api/history/annotation); ui-v2/real-data.js and proxy.jsx; bin/nullock; scripts/annotations_regression.py; Tests/ui/annotations_data_test.cjs and annotations_browser_test.cjs.","o":"partial","r":"Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action."},{"a":"platform","f":"Project files: scan issues persisted in the project and restored on reopen","s":"present","i":"blocker","e":"days","g":"None -- findings persist to <project>/findings.ndjson at discovery time and are streamed back into the findings panel on reopen; the baseline diff no longer reports restored issues as FIXED because the live set is repopulated first.","w":"Closed 2026-08-13: added a pure FindingSerial JSON round-trip (finding_serial.cpp, its own unit test, mutation-proven on the ts + compliance fields); ProjectStore.appendFinding writes findings.ndjson (deduped by the baseline identity key) and streamExistingFindings/restoreFindings stream it back on open; PassiveScanner gained a findingAdded signal (append-on-discovery, crash-safe) + ingestFinding (verbatim restore, no re-enrich/re-persist); app.cpp wires both. Restore preserves ts/enrichment/rowId. Gauntlet 93/93 + 156/156.","v":"`grep -rn \"findings.json|findings.ndjson|saveFindings|loadFindings|persistFindings\" --include=*.cpp --include=*.hpp Src` → no output. `grep -n \"findings\" Src/Core/Storage/project_store.cpp Src/Core/Storage/project_store.hpp` → no output. saveMetadata (project_store.cpp:283-315) serialises only v/name/notes/created/updated/inScope/outOfScope/rules. On open only traffic is replayed: Src/App/app.cpp:","o":"present","r":"Findings persist to <project>/findings.ndjson (append-on-report, deduped by the baseline identity key) and restore into the panel on reopen, preserving each finding's ts, enrichment and history rowId. New pure FindingSerial module (unit-tested + mutation-proven on ts/compliance), PassiveScanner findingAdded signal + ingestFinding restore, ProjectStore appendFinding/streamExistingFindings. Gauntlet ctest 93/93, probe_smoke 156/156."},{"a":"platform","f":"Project files: Repeater tabs, Intruder attack config and Sequencer state saved in the project","s":"partial","i":"high","e":"days","g":"Repeater tabs and Intruder configuration/result rows now restore with each project. Sequencer state is still not project-persisted. Intruder saves on project switch and clean exit, not after every edit; raw response bodies are not in the existing saved-run format.","w":"Repeater persistence already existed. Intruder now saves atomically to intruder.json, restores after startup/project changes without sending requests, resets every setting for fresh projects, and retains the current draft if saving or incoming-file validation fails. The combined feature stays partial until Sequencer state is also persisted.","v":"Src/Core/Storage/project_store.cpp: open/saveIntruderWorkspace; Src/App/app.cpp: setWorkspaceSave, intruderWorkspaceChanged and saveWorkspaceOnExit after worker drain; Src/Core/Networking/intruder.cpp: clearAll/loadRun; scripts/intruder_workspace_regression.py (19 runtime checks); Tests/ui/intruder_workspace_browser_test.cjs (two-client synchronization, project isolation, reload).; Tests/ui/intruder_data_test.cjs (ordered writes, stale polls, rejected old-project edits and failure recovery).","o":"absent","r":"Intruder configuration and result rows persist per project on switch/clean exit and restore idle. Browser drafts survive stale polls; rules/grep settings synchronize and stale project edits are refused. Runtime, browser and CLI checks pass. Sequencer persistence remains outstanding."},{"a":"platform","f":"Project options vs user options (settings split, persisted across restarts)","s":"absent","i":"medium","e":"days","g":"Everything non-project is a CLI flag or env var. No persisted preferences, no per-project vs per-user distinction.","w":"Confirmed. I grepped for QSettings and for the synonyms a Qt codebase might use instead (preferences, userSettings, settings.json) across all .cpp/.hpp in Src — the only matches are a content-discovery wordlist entry and unrelated TLS comments. There is no user-level settings store of any kind.","v":"`grep -rni \"QSettings|preferences|userSettings|settings.json\" --include=*.cpp --include=*.hpp Src` returns only Src/Core/Networking/content_discovery.cpp:73 `\"settings.py\", \"web.config\", \"appsettings.json\", \"wp-config.php.bak\",` (a fuzzing wordlist) and Src/Core/Networking/tls_profile.hpp:10,22 (cipher-preference prose comments). Theme choice resets each launch: Src/FrontEnd/GUI/Themes/themes_manager.cpp:13 `ThemesManager::ThemesManager(QObject *parent) : QObject(parent), m_current(\"cyber\") {`.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Grep results are the same shape as the prior pass (a fuzzing wordlist entry and TLS cipher-preference prose, neither a settings store). ThemesManager still hard-codes its startup theme in the constructor with no persisted user-level store. No QSettings, preferences file, or user-vs-project options split exists anywhere in Src. Claim holds."},{"a":"platform","f":"Configuration import/export as JSON (and Burp's configuration library / named config presets)","s":"present","i":"medium","e":"days","g":"None -- the ui-v2 preset switcher now exists: Settings' Project card gained a \"Config presets\" row (name input + Save, a saved-presets <select> + Load/Delete) wired to all four preset endpoints.","w":"Implemented. GET /api/config/export + POST /api/config/import move a versioned {format:'nullock-config',version,sections} document carrying scope (in/out/notes/advanced), match&replace rules, session-handling rules and intercept rules. Import reuses the EXACT setters behind /api/scope, /api/rules, /api/session-rules and /api/intercept/rules, so a re-imported config and the live editors are one code path; the envelope refuses a newer-major-version document and a non-Nullock document. The preset library (POST /api/config/presets/save|load|delete + GET /api/config/presets) is built ON TOP of that same code: save snapshots live config via the SAME capture used by export, and load applies via the SAME per-section apply used by import (both extracted to shared captureConfigSections()/applyConfigSections() lambdas), so a preset is byte-for-byte an export document. Partial only because the ui-v2 preset switcher is not built yet. Closed 2026-08-28: added the missing ui-v2 preset switcher. SettingsTab (app.jsx) gained presets/presetName/presetSel state, a refreshPresets() poll-on-mount, and savePreset/loadPreset/deletePreset handlers calling the four new real-data.js actions (configPresetsList/Save/Load/Delete). Rendered as a row in the Project card: a name input + SAVE, a <select> populated from GET /api/config/presets + LOAD/DELETE, disabled appropriately when no name is typed or no preset is selected. Load surfaces the applied-section list via alert(), matching the existing Import config pattern.","v":"control_server.cpp `/api/config/export`+`/api/config/import` (now sharing captureConfigSections()/applyConfigSections()) + the preset library `/api/config/presets/save|load|delete` and GET `/api/config/presets` (persisted to AppData/config-presets.json as {name:document}; name-validated via ControlLogic::presetNameValid, listed via ControlLogic::presetNames). Envelope + preset logic pure + mutation-proven in Tests/control_logic/control_logic_test.cpp (buildConfigDocument/validateConfigDocument M1 version-gate + M2 format-gate; presetNameValid M_A char-allowlist + M_B dot-only, presetNames sorted-keys). Live e2e 14/14 (scripts scratchpad preset_verify): add scope marker → save preset → remove marker → load preset restores the marker (apply path proven) → list shows it → delete removes it; invalid names (bad/name, '..', empty) rejected; missing-preset load → ok:false; real project.json + config-presets.json snapshot-restored. ui-v2/app.jsx SettingsTab (presets state + Config presets row in the Project card); ui-v2/real-data.js NL.actions.configPresetsList/Save/Load/Delete. Verified: bundled-babel transform of both touched files; a 13-assertion Node functional test (fake fetch, minimal browser-global shims) confirming each action hits the correct path/method and carries the correct {name} body against control_server.cpp's actual /api/config/presets* contract.","o":"partial","r":"Preset-library gap closed: wired the ui-v2 SWITCHER this item's own prior wave flagged as the sole remaining piece. absent->partial->present."},{"a":"platform","f":"Reporting: XML issue report","s":"present","i":"low","e":"hours","g":"Pipelines built on burp_issues XML (Dradis/Faraday importers, report generators) cannot ingest Nullock output directly. SARIF/JSON are arguably a better modern answer, so this is a compatibility gap rather than a capability gap.","w":"Confirmed. I enumerated every /api/export/ route in control_server.cpp myself: nmap-xml, sarif, sbom, postman. The only XML emitter is the port-scan nmap format; there is no issue-XML schema anywhere. The first pass's line numbers were stale by ~140 lines but the conclusion is right.","v":"`grep -n \"/api/export/\" Src/BackEnd/Control/control_server.cpp` → :5748 `// GET /api/export/nmap-xml  -> port scan results as nmap-compatible XML`, :5806 `// GET /api/export/sarif`, :5875 `// GET /api/export/sbom`, :6009 `// GET /api/export/postman`. No burp_issues-shaped XML exists.","o":"present","r":"Closed 2026-08-11: GET /api/report/xml serializes the report/json finding corpus into a Burp-style XML issue report (<nullockReport>/<issue> with name/host/url/cwe/owasp/detail/remediation). The finding->XML pass is the pure, mutation-tested ControlLogic::findingsJsonToXml -- every attacker-influenced value is xmlAttrEscape'd so a summary carrying <\/issue> cannot break framing."},{"a":"platform","f":"Reporting: report customisation (select which issues to include, severity/confidence filter, detail level, custom title/appendix, request-response inclusion)","s":"partial","i":"high","e":"days","g":"Issue SELECTION now spans ALL FOUR report sinks: GET /api/report/json + /api/report/xml (query params) and POST /api/report/build (Markdown) + /api/report/html (JSON body) all take minSeverity/minConfidence/includeKinds/excludeKinds/includeFixed and emit only the issues that pass, via one shared predicate (ControlLogic::findingPasses). The two builders also accept a custom `title` and an `appendix`. json keeps posture/coverage over the FULL set (+ findingsTotal vs findingsTotalAll + filtered flag) so an API consumer sees engagement truth; the two human reports reflect the INCLUDED set throughout (Burp's report-wizard behaviour) and print a 'showing X of Y (filtered)' note. Still partial for: a detail-level toggle, and full request/response evidence embedding (evidence is still truncated).","w":"Implemented + mutation-proven. One selection rule, one source of truth: ControlLogic::findingPasses(severity,confidence,kind,fixed,criteria) backs both filterFindings (the JSON-shape path) and the QList<Finding> report builders; criteria are parsed by reportFilterFromQuery (GET) / reportFilterFromJson (POST). severity floor via severityRank, confidence floor via confidenceRank (confirmed/firm/tentative AND high/medium/low), kind include/exclude (exclude wins), includeFixed. All live in control_logic (Qt6::Core-linkable, unit-tested) -- deliberately NOT in control_server.cpp's anonymous namespace, which reproducibly ICE'd MSVC 14.38 (C1001).","v":"control_logic.cpp:298 `bool findingPasses(const QString &severity, const QString &confidence, ...)`; :355 `ReportFilterCriteria reportFilterFromQuery(const QUrlQuery &q) {`; :368 `ReportFilterCriteria reportFilterFromJson(const QJsonObject &body) {`. All four report sinks wired to the shared predicate: control_server.cpp GET /api/report/json (:6200), GET /api/report/xml (:6257), POST /api/report/build (:5884), POST /api/report/html (:5995).","o":"","r":"Wave 0 register-accuracy audit: held at partial (real parity for issue selection, still missing detail-level and request/response-inclusion controls per the existing gap text). findingPasses/reportFilterFromQuery/reportFilterFromJson all present and wired to all four report endpoints exactly as the last (already-fresh, 2026-08-2x-vintage) evidence described; this item only needed the audit-trail block, not a re-derivation. Claim holds."},{"a":"platform","f":"Reporting: reachable from the UI (Report menu / right-click > report selected issues)","s":"present","i":"high","e":"hours","g":"None -- the REPORTING tab (ReportingTab in ui-v2/app.jsx, mounted at `tab === \"reporting\"`) is Burp's Report menu equivalent: every engagement report is one click. The Engagement report section now downloads Markdown (POST /api/report/build), styled HTML (POST /api/report/html), JSON (GET /api/report/json), and the Burp-style XML issue report (GET /api/report/xml) plus a View-summary readout; the same tab drives OpenAPI export/import, SBOM download, and workspace push/pull. The POST-only generators are reached via fetch->blob download (downloadBlob), the two allowlisted GET reports via a plain anchor (downloadHref). No curl needed for any format.","w":"Reconciled forward. The original 2026-08-08 note already recorded the REPORTING tab shipping (Markdown/HTML/JSON reachable from one panel), but the top-level gap/why/evidence were never updated off the pre-tab 'you must curl it' state and audited_state was left at stub. Re-derived against live source this wave: the tab exists and is mounted, all four report formats download from buttons, and the XML report -- the last format that was reachable only via curl -- now has its own Download XML button too.","v":"ui-v2/app.jsx: ReportingTab Engagement-report Btns -- Download Markdown (downloadBlob->NL.actions.reportBuild), Download HTML (downloadBlob->NL.actions.reportHtml), Download JSON (downloadHref '/api/report/json'), Download XML (downloadHref '/api/report/xml'); tab mounted at `{tab === \"reporting\" && <ReportingTab />}`. Backend: control_server.cpp report/build :5473, report/html :5561, report/json :5739, report/xml :5787; isReadPath allowlists report/json :1764 and report/xml :1765 so the GET anchor downloads work without the X-Nullock-UI header.","o":"present","r":"Register reconciled to reality (audited_state stub->present) and the last curl-only report format wired: a Download XML button (GET /api/report/xml) added beside the existing Markdown/HTML/JSON downloads, so every engagement report format is now one click from the REPORTING tab. Builds on the 2026-08-08 tab (557e5f8)."},{"a":"platform","f":"Issue lifecycle: mark false positive, set issue status/severity override, delete issue","s":"present","i":"high","e":"days","g":"None — all three named actions (mark false positive, severity override, delete) are reachable end-to-end in ui-v2's Issues tab, on top of the per-project-persisted backend that already covered them.","w":"Backend + API covered the whole triage lifecycle since 536f2b7 (false-positive marking, severity override, soft-delete, all persisted per-project keyed by finding identity, applied at display time) but had no caller anywhere in ui-v2 — confirmed via a fresh grep (zero hits for set-severity/findings/delete/findings/mark/suppress-kind in any ui-v2/*.jsx before this wave). IssuesTab now wires all four endpoints: a per-row FP/un-FP toggle, a del/restore toggle, and a severity-override select, plus a per-kind mute toggle on the kind-filter chips (bonus — suppress-kind was also unwired). Deleted and muted-kind findings are hidden from the default view behind a new 'show hidden' toggle that reveals + lets them be restored; a plain false-positive mark stays visible, dimmed and struck-through, matching Burp only annotating rather than hiding an FP-marked issue.","v":"ui-v2/app.jsx IssuesTab's doMarkFP/doToggleDelete/doSetSeverity/doSuppressKind call NL.actions.findingMark/findingDelete/findingSetSeverity/findingSuppressKind (ui-v2/real-data.js) -> POST /api/findings/{mark,delete,set-severity,suppress-kind}; every field read (f.falsePositive/f.deleted/f.suppressed/f.severity/f.id) matches control_server.cpp:1358-1393's /api/snapshot findings array field-for-field.","o":"present","r":"Wave 2: wired the already-complete backend issue-lifecycle (FP mark, severity override, soft-delete, kind-mute) into ui-v2's Issues tab — the remaining follow-on this item's own prior reconciled note (536f2b7) had explicitly flagged as outstanding. No backend change."},{"a":"platform","f":"Burp's browser (embedded pre-configured Chromium — no proxy config, no CA install)","s":"absent","i":"high","e":"months","g":"Onboarding requires manually configuring a browser proxy and installing the CA into the OS/browser trust store. Burp's single biggest friction-remover.","w":"Confirmed. Grepped for QWebEngine, WebEngine, chromium, puppeteer and playwright across .cpp/.hpp/CMakeLists and got zero hits — importantly including CMakeLists.txt, so no browser component is even linked. The only launch behaviour is opening the user's own default browser at the control UI. Confirmed absent.","v":"`grep -rni \"QWebEngine|WebEngine|puppeteer|playwright|chromium\" --include=*.cpp --include=*.hpp Src CMakeLists.txt`: 0 hits. Src/App/app.cpp:1346 `if (!headless && ctlLoopback) QDesktopServices::openUrl(QUrl(url));` -- the default OS browser at the control UI, nothing embedded.","o":"","r":"Wave 0 register-accuracy audit: held at absent. No embedded-browser dependency of any kind is linked (CMakeLists.txt included in the grep, still 0 hits). The only launch behaviour is opening the user's own default browser (app.cpp, drifted :1021 -> :1346, unchanged content). Claim holds."},{"a":"platform","f":"Dashboard task engine: live task list with per-task progress, pause/resume/cancel, task detail view","s":"absent","i":"high","e":"weeks","g":"Once /api/audit/all or /api/probe/all starts you cannot see progress, pause it, or stop it. Burp's Dashboard is the primary control surface for exactly this.","w":"Confirmed. I grepped for a task registry under several names (tasks array, taskList, jobQueue, progressPct, cancelTask, pauseTask) — nothing exists. I then read the audit sweep entry point directly and confirmed it is exactly as described: a single global atomic that only answers 'already running', with no handle, no counter and no cancel path once QtConcurrent::run is dispatched.","v":"`grep -rani \"\\\"tasks\\\"|taskList|jobQueue|progressPct|cancelTask|pauseTask\" Src ui-v2`: 0 hits. control_server.cpp:7858-7861 `static QAtomicInteger<int> auditAllInFlight(0); if (!auditAllInFlight.testAndSetAcquire(0, 1)) return okJson({{ \"ok\", false }, { \"queued\", 0 }, { \"error\", \"a deep-audit sweep is already running\" }});` then dispatched fire-and-forget via QtConcurrent::run with no handle, counter, or cancel path.","o":"","r":"Wave 0 register-accuracy audit: held at absent. No task-registry vocabulary exists anywhere (0 hits repeated). /api/audit/all is still gated by a single global QAtomicInteger that answers only \"already running\" -- no handle, no per-task progress, no pause/resume/cancel, no detail view (line drifted 6657-6660/6725 -> 7858-7869, logic byte-identical). Claim holds."},{"a":"platform","f":"Dashboard event log (suite-wide errors, warnings, info)","s":"absent","i":"medium","e":"days","g":"Failures are silent to the operator. A failed SQLite index, a dropped filter, a TLS error — none of it surfaces.","w":"Confirmed. Grepped eventLog/appLog/activityLog/toast/notification: the only 'EventLog' is H2EventLog, which I checked is an HTTP/2 frame tracer (noteFrame / noteRequestHeader / noteResponseStatus / noteRstStream), not an application log. The only operator-visible log is the per-extension one. Backend errors go to qWarning(), which per this project's own build model is invisible in the shipped GUI-","v":"Src/BackEnd/Proxy/h2_events.cpp:19 `void H2EventLog::noteFrame(...)`, :52 noteRequestHeader, :69 noteResponseStatus, :79 noteRstStream -- an HTTP/2 protocol frame tracer, not an application log. Only user-facing log: control_server.cpp:1311-1313 `for (const QString &line : m_wiring.extensions->recentLog(40)) extLog.append(line); bootInfo[\"extensionsLog\"] = extLog;`. `grep -rani \"eventLog|appLog|activityLog\\b\" --include=*.cpp --include=*.hpp Src`: 0 hits outside H2EventLog.","o":"","r":"Wave 0 register-accuracy audit: held at absent. H2EventLog's four note* methods are unchanged (line numbers identical: 19/52/69/79), confirmed it is still purely an HTTP/2 frame tracer with no general error/warning/info channel. The only operator-visible log surface is still the per-extension recentLog (control_server.cpp, drifted 1224-1227 -> 1311-1313). Backend qWarning() output is still not surfaced anywhere in the GUI. Claim holds."},{"a":"platform","f":"Scheduled tasks (run a scan/task at a given time or on a repeating schedule)","s":"absent","i":"medium","e":"days","g":"No recurring scans. The workaround is external cron driving --scan, which loses all project context.","w":"Confirmed. Grepped for scheduled/schedule/cron/recurring and for timer-driven task patterns across .cpp/.hpp/.jsx — no timer-driven task registry exists anywhere in product code. Consistent with the absence of a task engine generally.","v":"`grep -rani \"QTimer.*schedul|cron|recurring\" --include=*.cpp --include=*.hpp --include=*.jsx Src ui-v2` now returns false-positive noise from Src/Core/Networking/session_rules.cpp (`macroName` contains the substring \"croN\", matching /cron/i) -- no real hit. Separately grepped `QTimer` usage in app.cpp and control_server.cpp directly: every instance is a kill-timer or event-loop timeout (app.cpp:74,95,139,148,179,183,250,255), not a task scheduler. No timer-driven task registry exists anywhere in product code.","o":"","r":"Wave 0 register-accuracy audit: held at absent. The exact synonym grep now returns spurious hits in session_rules.cpp because the new SessionMacro variable `macroName` (added since the last audit, for the login-macro feature covered by items #71-72/157-159) happens to contain the case-insensitive substring \"cron\" (m-a-c-r-o-N-ame). Verified by hand that none of those lines are scheduling-related -- they are macro-name plumbing around QtConcurrent::run. Read every QTimer use in app.cpp directly as a second check: all are shutdown/kill timers or synchronous-call timeouts, not a recurring-task mechanism. No scheduling surface exists in buildSnapshot or the endpoint dispatcher. Claim holds; flagging the grep false-positive so it isn't mistaken for a real hit in a future pass."},{"a":"platform","f":"Hotkeys (configurable keyboard shortcuts) and the command palette","s":"present","i":"high","e":"days","g":"A command palette (Ctrl/Cmd+K, or the title bar's ⌘K button) lists every tab plus a handful of cross-cutting toggles (intercept, intercept-responses, appearance/tweaks panel, copy CA cert path, and now \"Customize keyboard shortcuts…\" itself), fuzzy-filterable, arrow-key navigable, Enter to run. Ctrl/Cmd+1-9 jump directly to the first nine tabs, and every one of those 10 bindings (palette-open + the 9 tab jumps) is now user-remappable through a HotkeysOverlay rebind UI -- click a binding, press a new combo, a live conflict check warns if another action already owns it, per-row reset-to-default, persisted to localStorage (nl-hotkeys) and read back on load. Still honestly missing: there is no Ctrl+R send-to-repeater / Ctrl+Shift+R / Ctrl+O contextual shortcut set -- the palette and the rebind UI both only reach global navigation + a few app-level toggles, not per-row or per-tab contextual actions like \"send this history row to Repeater\", because the reducer has no generic contextual-dispatch surface to bind against yet.","w":"Added a rebindable-hotkeys layer on top of the existing CommandPalette: pure helpers (defaultHotkeys/comboFromEvent/comboLabel/loadHotkeys/saveHotkeys/matchHotkeyAction, ui-v2/app.jsx:5621-5680) turn a keydown event into a normalized \"mod[+shift][+alt]+key\" combo string and look it up against a persisted binding map instead of the old hardcoded if (k===\"k\") / /^[1-9]$/ checks; a new HotkeysOverlay component (app.jsx:5686-5773) lets the user click a binding, press a new combo, and see+resolve conflicts against every other current binding before it's saved. App()'s global keydown effect now dispatches via matchHotkeyAction(hotkeys, combo) and is suspended while the overlay itself is open (so recording a new combo there can't also fire the old one); the palette gained a \"Customize keyboard shortcuts…\" entry as the discovery path, and its own tab-row hints now render the live bound key via comboLabel() instead of a hardcoded \"Ctrl+N\" string. This closes the one gap #247 was explicitly left partial for last wave (\"bindings are fixed, not user-configurable\") -- upgraded partial -> present. Per-row/contextual hotkeys (Ctrl+R send-to-repeater etc.) remain a real, separate, honestly-undocumented-as-fixed gap: no code here invents a contextual-dispatch surface the reducer doesn't have.","v":"ui-v2/app.jsx:5621-5680 (HOTKEYS_STORAGE_KEY, defaultHotkeys, comboFromEvent, comboLabel, loadHotkeys, saveHotkeys, matchHotkeyAction), :5686-5773 (HotkeysOverlay component), App()'s hotkeys/hotkeysOpen state + the rewritten keydown effect and hotkeyActions/updateHotkey/resetHotkey (app.jsx ~5878-5951), paletteCommands' new \"customize-shortcuts\" entry and comboLabel-driven tab hints, and the {hotkeysOpen && <HotkeysOverlay .../>} render alongside the existing palette render.","o":"present","r":"Rebindable-hotkeys batch: the command palette's 10 global bindings (open-palette + Ctrl/Cmd+1-9 tab jumps) are now user-remappable via a new HotkeysOverlay, persisted to localStorage, with live conflict detection and per-row reset. Closes the configurability half of #247's gap (partial -> present); contextual per-row shortcuts stay the honest remainder, unrelated to this batch. No backend touched."},{"a":"platform","f":"Performance feedback / memory usage display / low-memory warnings and memory settings","s":"absent","i":"low","e":"days","g":"No visibility into memory or throughput and no warning before trouble. Being C++ this matters far less than for Burp's JVM, but the operator is still flying blind on a long engagement — and the row cap silently discards rows from the live model with no indication.","w":"Confirmed. Grepped for the platform-specific APIs a C++ app would actually use (GlobalMemoryStatus, getrusage, /proc/self/status) plus memoryUsage/memUsage — zero hits across all .cpp in Src. The only memory control is the blind row cap, which I verified is a hard-coded default with no feedback of any kind.","v":"`grep -rni \"GlobalMemoryStatus|memoryUsage|getrusage|/proc/self/status\" --include=*.cpp Src`: 0 hits. The one control: Src/App/app.cpp:639 `\"  --max-rows=N          ProxyModel in-memory window cap (default 10000)\\n\"` implemented as Src/FrontEnd/GUI/Models/Proxy/proxy_model.hpp:89 `int m_maxRows = 10'000; // window cap`, enforced silently at proxy_model.cpp:58-78 (`m_maxRows = std::max(100, n);` ... `while (static_cast<int>(m_entries.size()) > m_maxRows) {`).","o":"","r":"Wave 0 register-accuracy audit: held at absent. No platform memory-query API is used anywhere (0 hits, same as prior pass). The row-cap mechanism is unchanged in substance, only line numbers drifted (584 -> 639 for the flag help text; 78-82 -> 58-78 for the eviction loop, content identical). No memory/throughput visibility or low-memory warning exists anywhere. Claim holds."},{"a":"platform","f":"Clickbandit (clickjacking PoC generator) and Burp Infiltrator","s":"partial","i":"low","e":"hours","g":"A CLICKJACK POC button next to CSRF POC in Proxy history / Site map's DetailPane now generates a standalone HTML page (invisible iframe framing the row's URL over a decoy button, HTML-escaped) and offers it for download -- the actual PoC-generation half this item names. Still missing versus Burp's Clickbandit specifically: the interactive in-browser tool where you drag/resize the target's live rendered elements under the decoy overlay and it records your clicks as you place them; this is a static one-shot template instead. Infiltrator remains out of scope (deprecated in current Burp, not worth building, per prior audit).","w":"Closed 2026-08-26: added buildClickjackPoc() (ui-v2/proxy.jsx) reusing the same parseRawRequest()-derived fullUrl the existing COPY AS / CSRF POC machinery already builds, and a CLICKJACK POC button wired to the shared CodecOverlay (title/body/note/downloadName) -- the same pattern CSRF POC already uses, so no backend endpoint was needed (framing a URL client-side requires no server-side replay). Client-only, matching how COPY AS already generates curl/wget/etc without a round trip.","v":"ui-v2/proxy.jsx buildClickjackPoc() (escapes the URL into an <iframe src> under a positioned decoy <button>) and the CLICKJACK POC button in DetailPane calling parseRawRequest(row, req) for fullUrl then setOverlay({title, body, note, downloadName}) -- rendered by the existing CodecOverlay (proxy.jsx:2555). No backend change; Src/Core/Networking/request_export.cpp's csrfPoc() is untouched and unrelated.","o":"partial","r":"Clickjacking PoC generator wave: client-side CLICKJACK POC button (DetailPane, Proxy history / Site map) closes the PoC-generation gap this item names; Clickbandit's interactive drag-placement UX and Infiltrator remain out of scope, so state moves absent -> partial rather than -> present."},{"a":"platform","f":"Desktop application shell (a single native GUI hosting every tool)","s":"stub","i":"medium","e":"months","g":"There is effectively ONE front end (ui-v2 in the user's browser). The Qt GUI tree is scaffolding and its host window only loads from a source checkout. Browser-hosted UI means no native menus, no OS keyboard integration, no multi-window layout.","w":"Confirmed, with numbers I generated myself. `wc -l` over the GUI tree returns 8 for every one of the 23 .qml component files — 184 lines total for the entire advertised Qt front end. Only Src/App/app.qml has content (1211 lines), and I verified it is loaded from a RELATIVE source path, so the QML window only works when the binary is run from a source checkout — it cannot function in an installed o","v":"`wc -l Src/FrontEnd/GUI/*/*.qml Src/FrontEnd/GUI/*/Components/*.qml`: `8` for all 23 files, `184 total` (e.g. Src/FrontEnd/GUI/Workspace/workspace.qml, .../Proxy/proxy.qml, .../RepeaterHub/repeater_hub.qml). `wc -l Src/App/app.qml`: `1211`. Src/App/app.cpp:1485-1486 `// run from project root so this relative path resolves to Nullock/Src/App/app.qml` / `const QUrl url(QStringLiteral(\"./Src/App/app.qml\"));`.","o":"","r":"Wave 0 register-accuracy audit: held at stub. Re-ran the exact wc -l sweep: still 8 lines for all 23 scaffold .qml components (184 total, unchanged), still 1211 lines for the one real app.qml, still loaded from a relative source-checkout path (app.cpp, drifted 1159-1160 -> 1485-1486, content identical -- the binary still cannot locate its own QML window from an installed/packaged location). ui-v2 (the browser-hosted front end) remains the sole functional UI. Claim holds."},{"a":"proxy","f":"Proxy listener > Request handling > Support invisible proxying (non-proxy-aware clients)","s":"partial","i":"high","e":"days","g":"Invisible HTTPS (the actual use case) is impossible -- no TLS-first/SNI accept path. Cleartext invisible mode is undocumented, untoggleable, and, because the listener is hard-bound to 127.0.0.1, only reachable from the same host via a hosts-file redirect onto whatever --proxy-port was chosen.","w":"Re-read proxy_server.cpp run()/rewriteHostPort myself. The claim holds: the accept path unconditionally parses an HTTP request line, and the Host-header fallback makes cleartext invisible proxying work by accident. I confirmed no SNI peek exists (grep 'SNI' across Src returns only the cert_logic.hpp comment). I kept 'partial' rather than dropping to 'stub' because the plaintext path really does wo","v":"Src/BackEnd/Proxy/proxy_server.cpp:287-290 `void run() { ... if (!readRequest(req)) { fail(\"malformed request\"); return; }` -- a TLS ClientHello with no CONNECT fails readRequestFrom's `if (parts.size() < 3) return false;` (proxy_server.cpp:881). Host fallback confirmed in rewriteHostPort, proxy_server.cpp:244-264 (`const QString hostHeader = findHeader(req.headers, \"Host\");` used only when the target isn't already an absolute URL).","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-checked run()/readRequestFrom/rewriteHostPort line by line (drifted ~30 lines from the last audit, logic byte-identical) and re-ran `grep -rn SNI Src`: still only the two unrelated comment hits (cert_logic.hpp, tls_logic.cpp), no SNI-peek implementation anywhere. Invisible HTTPS (TLS-first accept with no CONNECT) is still impossible; cleartext invisible mode still works only by the same Host-header-fallback accident. No change."},{"a":"proxy","f":"Proxy listener > Certificate > Generate CA-signed per-host certificate (per-host leaf minting)","s":"present","i":"medium","e":"hours","g":"Leaf carries a single SAN (DNS:<host> for a normal hostname target, or IP:<addr> for an IPv4/IPv6 literal target via CertLogic::sanEntryForHost -- see item #286 for that IP-SAN work's own state). Burp clones the upstream cert's full subject/SAN set; Nullock does not, so a client pinning on issuer-independent fields (multi-SAN, OU, serial) still breaks -- multi-SAN/wildcard leaves and the live-handshake forged-leaf path are #286's tracked remainder. Whole path is gated on an external openssl binary (item 6).","w":"CertAuthority mints per-host RSA leaves signed by the local CA, with DNS/IP SANs, serverAuth usage, and explicit subject/authority key identifiers for OpenSSL and LibreSSL compatibility.","v":"Src/BackEnd/Proxy/cert_authority.cpp leaf extension configuration; cert_logic.cpp sanEntryForHost; scripts/runtime_regression.py packaged HTTPS transaction with strict certificate verification.","o":"present","r":"Declare leaf key identifiers explicitly so strict TLS clients accept LibreSSL-generated certificates. Runtime regression exercises real proxy HTTPS with strict validation enabled on every Python version."},{"a":"proxy","f":"CA certificate: leaf caching across restarts","s":"present","i":"medium","e":"hours","g":"Persisted leaves are checked against the current CA and private key after restart. Cache eviction, a clear-leaves control, live CA replacement, and automatic CA/key repair remain unavailable.","w":"Disk-cache reuse verifies parsing, common name, the requested DNS/IP subject alternative name, dates, authority key identifier, server-certificate trust against the current CA, and the private key public component. Stale, damaged or mismatched files are regenerated; valid files are reused and private-key permissions are reapplied.","v":"Src/BackEnd/Proxy/cert_authority.cpp cachedLeafMatchesCaAndKey and leafCertFor; scripts/runtime_regression.py strict HTTPS after restart for valid reuse, legacy leaves, mismatched/damaged keys, invalid signatures, wrong/missing subject alternative names and replaced CA.","o":"","r":"Verify the current CA, private key and requested DNS/IP subject alternative name before disk-cache reuse. Strict HTTPS regressions cover wrong and missing SANs; focused checks retain valid DNS, IPv4 and IPv6 leaves."},{"a":"proxy","f":"CA private key hardening on disk","s":"present","i":"low","e":"hours","g":"Restrictions cover CA and persisted leaf keys. They separate OS accounts; they do not isolate other programs running as the owning user. Unsupported filesystems or ACL failures produce warnings rather than preventing startup.","w":"The code applies owner-only POSIX permissions or a Windows ACL for the current user when creating and reusing CA and leaf keys. Call sites report failures. The older claims that leaf keys bypass hardening and failures are silent no longer match the source; a comparison-based exceeds grade is not retained.","v":"Src/BackEnd/Proxy/cert_authority.cpp lockdownPrivateKeyFile; ensureCa creation/reuse; leafCertFor creation/reuse; qWarning at every hardening call site.","o":"exceeds","r":"Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits. Grade changed from exceeds to present."},{"a":"proxy","f":"CA certificate: export in DER (http://burp/cert), export cert+key as PKCS#12, import a CA from PKCS#12, regenerate CA","s":"partial","i":"medium","e":"days","g":"DER export now ships: GET /ca.der (and Burp's /cert alias) serves the CA as application/pkix-cert, converting the PEM via the pure ControlLogic::pemCertToDer (no OpenSSL). Still partial for PKCS#12 export/import of cert+key (share one CA across a team / load Burp's CA) and CA regenerate (recovery from a compromised/expired CA is still delete-ca.pem/ca.key-by-hand-and-restart) -- both need OpenSSL pkcs12 + swapping the live CA/leaf cache.","w":"Re-ran the greps myself: `pkcs12|PKCS12|\\.pfx` returns ZERO hits across all of Src, ui-v2 and browser-ext. The /ca.pem handler is real and is the only export. Confirmed partial (PEM download exists and is UI-linked).","v":"Src/BackEnd/Control/control_server.cpp:1194 `} else if (path == \"/ca.pem\" || path == \"/ca.crt\") {` and :1220-1236 `} else if (path == \"/ca.der\" || path == \"/cert\") { ... hdr += \"Content-Disposition: attachment; filename=\\\"nullock-ca.der\\\"\\r\\n\";`. CertAuthority's whole public surface is still cert_authority.hpp:26-33 (`ensureCa`, `caCertPath`, `caDir`, `hasOpenssl`, `leafCertFor`) -- no import, no regenerate, no PKCS#12 anywhere.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-ran `grep -rn 'pkcs12|PKCS12|\\.pfx' Src ui-v2 browser-ext`: still zero hits repo-wide. /ca.pem and /ca.der (plus the /cert Burp-compat alias) are still the complete export surface; CertAuthority's public API is unchanged (ensureCa/leafCertFor only, no import/regenerate entry point). No change."},{"a":"proxy","f":"MITM CA works out of the box (bundled crypto)","s":"partial","i":"high","e":"weeks","g":"On a stock Windows box (no OpenSSL on PATH) HTTPS interception does nothing -- every host tunnels opaquely. The indicator is a small 'openssl ✗' chip; the intercept/history panes just look empty with no explanation. Burp requires no external tooling.","w":"Confirmed the external-openssl dependency and the hasOpenssl() gate on the CONNECT path. Two corrections to the evidence: (a) it is NOT silent -- bootInfo.hasOpenssl is surfaced in both front ends (ui-v2/tabs.jsx:19 'openssl ✗', ui-v2/app.jsx:488 'OpenSSL: missing'), so the user has a visible indicator, just not on the intercept path; (b) the '30s+ QProcess forks on first contact' figure is wrong ","v":"Src/BackEnd/Proxy/cert_authority.cpp:114-115 `QStringLiteral(\"C:/Program Files/OpenSSL-Win64/bin/openssl.exe\"), ...` -> hasOpenssl() gate at proxy_server.cpp:388 `if (inScope && sslClient && ca && ca->hasOpenssl() && !blocked) {`. Visible indicators: ui-v2/tabs.jsx:242 `{bootInfo.hasOpenssl ? \"openssl \\u2713\" : \"openssl \\u2717\"}`, ui-v2/app.jsx:995 `<Row label=\"OpenSSL\" value={b.hasOpenssl ? \"found\" : \"missing\"} />`.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Same external-openssl dependency, same hasOpenssl() gate on the CONNECT path, both UI indicators (tabs.jsx, app.jsx) still present and unchanged in behavior -- only line numbers drifted (tabs.jsx :19->:242, app.jsx :488->:995, cert_authority.cpp :102-114->:114-115, proxy_server.cpp :334->:388). On a stock box with no openssl on PATH, HTTPS interception is still silently a blind tunnel with only the small chip as an explanation. No change."},{"a":"proxy","f":"TLS pass through list (manual host/IP-range + port entries, 'Apply to out-of-scope items')","s":"partial","i":"medium","e":"hours","g":"No host:port or IP-range entries -- matching is still a plain QSet exact-string contains, so wildcards and CIDR ranges are unsupported -- and there is no 'apply to out-of-scope items' knob. Both are real backend-shaped gaps; add/delete/clear/view are now all reachable end to end.","w":"The 7c28cc9 wave (2026-08-18) closed pre-add (POST /api/mitm/block) and per-host delete (POST /api/mitm/unblock) at the backend/API level, but its own reconciled note already flagged the UI still had zero callers for either -- confirmed still true by a fresh grep at the start of this wave (only clearMitmBlocked() had a caller in ui-v2). Closed the remaining UI half: the Proxy card's MITM bypass row (SettingsTab, ui-v2/app.jsx) now renders each blocked host as a chip with a per-host × remove button (NL.actions.unblockMitmHost), plus a text input + Add button to pre-add a host (NL.actions.markMitmBlocked) -- both new thin wrappers in ui-v2/real-data.js posting to the pre-existing, already-backend-verified endpoints. Stays honestly partial: only the matching-scheme and out-of-scope-knob gaps remain, both backend changes this cloud session cannot build.","v":"ui-v2/app.jsx SettingsTab's MITM bypass row: each entry in mitmBlockedList renders `<span>{h}<button onClick={() => removeBypassHost(h)}>×<\/button><\/span>` calling `NL.actions.unblockMitmHost(h)`; a new host input + `Btn label=\"Add\" onClick={addBypassHost}` calling `NL.actions.markMitmBlocked(h)`. ui-v2/real-data.js: `markMitmBlocked(host) { return post(\"/api/mitm/block\", { host }).then(r => r.json()); }` and `unblockMitmHost(host) { return post(\"/api/mitm/unblock\", { host }).then(r => r.json()); }`, both matching the existing backend contract at control_server.cpp's `/api/mitm/block` and `/api/mitm/unblock` routes (unchanged, verified e2e in the 7c28cc9 wave).","o":"partial","r":"Closed the last UI gap on this item: the Proxy card (SettingsTab, ui-v2/app.jsx) now exposes per-host delete (× chip button -> NL.actions.unblockMitmHost) and pre-add (host input + Add button -> NL.actions.markMitmBlocked) for the TLS pass-through list, wired to the backend endpoints the 7c28cc9 wave already built and e2e-verified but which had no UI caller until now. No backend touched. Stays partial: exact-string-only matching (no host:port/IP-range/wildcard) and no 'apply to out-of-scope items' knob remain, both real backend gaps."},{"a":"proxy","f":"TLS pass through > Automatically add entries on client TLS negotiation failure","s":"present","i":"medium","e":"hours","g":"No on/off switch (Burp's is a checkbox) to disable auto-add entirely -- confirmed still absent (no such Q_INVOKABLE/flag exists). The two other gaps noted in an earlier pass no longer hold: the upstream-handshake trigger (proxy_server.cpp:541-555) now only blocklists on a genuine unreachable/timeout (`tlsErrors.isEmpty()`), NOT on a transient cert-rejection, so a one-off TLS error no longer causes a permanent demotion; and per-host removal now exists end-to-end -- `ProxyServer::clearMitmBlocked(host)` (proxy_server.hpp:195), the `/api/mitm/unblock` endpoint (control_server.cpp:6658-6664), and a per-row \"x\" button wired to `NL.actions.unblockMitmHost(h)` in the Proxy pane (ui-v2/app.jsx:843-850, `removeBypassHost` at :718-721).","w":"Both trigger sites verified verbatim, plus persistence via setBlocklistPath (wired in Src/App/app.cpp:671). The behaviour genuinely exists and survives restarts. Kept 'present' but filled the empty gap: the trigger is broader than Burp's (any upstream handshake failure inside a 3 s window, not just a client-side refusal) and there is no per-entry removal.","v":"Src/BackEnd/Proxy/proxy_server.cpp:470-476 (client path) `if (!waitEncrypted(sslClient, kReadTimeoutMs, m_server)) {\\n            // Client refused our forged cert -- usually cert pinning.\\n            m_server->markMitmBlocked(host);`; upstream twin at proxy_server.cpp:541-555, refined since the prior pass to gate on `if (tlsErrors.isEmpty()) m_server->markMitmBlocked(host);` -- a cert-level rejection (tlsErrors non-empty) is no longer blocklisted, only a genuine handshake timeout/unreachable is; `kHandshakeTimeoutMs = 3'000` at proxy_server.cpp:57. Persisted via `setBlocklistPath` (proxy_server.cpp:1485), wired in Src/App/app.cpp:740 `proxy.setBlocklistPath(certAuthority.caDir() + \"/mitm_blocked.txt\");`.","o":"","r":"Wave 0 register-accuracy audit: re-verified against live source. Found real drift -- two of the three gaps this item recorded have since been closed by other work (the upstream trigger was narrowed to exclude transient cert errors, and per-host unblock was wired end-to-end, backend + UI). Corrected the gap text to describe only what's actually still missing (a global on/off switch) and refreshed evidence line numbers. No state change -- still 'present', not upgraded to 'exceeds', since the remaining gap (no way to fully disable auto-add) is real."},{"a":"proxy","f":"Handling invalid upstream TLS certificates (Burp accepts by default so self-signed / expired lab targets stay testable)","s":"present","i":"high","e":"hours","g":"Backend allow-list/filter/persistence/visibility shipped in d95a390; the operator-facing gap named here since then -- 'no way to act on the diagnostics' -- is now closed: Settings' CA & TLS card has an Accept-invalid host chip-list (add/remove, backed by /api/proxy/accept-invalid-hosts/{add,remove}) plus a read-only table of exactly which certs were waived (host/sha256/ignored-errors/when), sourced from the same bootInfo fields the backend already published. Two named remainders stay open, both smaller and already called out in the backend reconciliation: a per-proxy-history-row 'this leg was unverified' annotation, and certificate-fingerprint pinning/TOFU (v1.1).","w":"Verified live: the backend wiring (project-scoped allow-list, benign-error filter, per-host unblock, persistence, bootInfo visibility) was already real per d95a390's own reconciliation, but grepping ui-v2/*.jsx + real-data.js for acceptInvalidHosts/accept-invalid-hosts/acceptedInvalidCerts returned nothing -- an operator had no way to add a host or see what was waived except curl. Added the missing UI leg only; no backend change.","v":"Src/BackEnd/Control/control_server.cpp:6373-6394 (POST /api/proxy/accept-invalid-hosts/{add,remove}, echoes acceptInvalidUpstreamHosts); control_server.cpp:1264-1275 (bootInfo.acceptInvalidUpstreamHosts + acceptedInvalidCerts with host/sha256/ignoredErrors/acceptedAt); ui-v2/real-data.js NL.actions.acceptInvalidHostAdd/Remove; ui-v2/app.jsx SettingsTab 'CA & TLS' card, Accept-invalid chip list + waived-certs table, mirroring the existing MITM-bypass chip-list pattern in the same card group.","o":"partial","r":"Added the operator-facing UI for the per-host accept-invalid-cert allow-list that d95a390 built backend-only: a chip-list (add/remove) in Settings' CA & TLS card wired to the existing POST /api/proxy/accept-invalid-hosts/{add,remove}, plus a read-only table rendering bootInfo.acceptedInvalidCerts (host, leaf sha256, which errors were waived, when) so an operator can audit exactly what verification was relaxed. No backend change. partial -> present (backend was already sound; the missing piece was purely that no UI could reach it)."},{"a":"proxy","f":"Settings > Network > TLS > Use custom protocols and ciphers","s":"partial","i":"low","e":"weeks","g":"Two hardcoded browser profiles selected by --tls-fingerprint only -- no UI, no free-form protocol/cipher list, and TLS 1.3 suites cannot be pinned at all (Qt 6 has no setCiphersuites). Not shaped at all on the SChannel backend.","w":"Verified apply() line by line. Two of the claims needed sharpening: on a non-OpenSSL backend it does not 'silently degrade' -- it qWarns and returns false (the contract is documented as 'true ONLY when actually shaped'); and a partial cipher resolution deliberately leaves Qt defaults rather than shipping a mangled list. Still partial: two canned profiles, launch-flag only, no user-facing picker.","v":"Src/Core/Networking/tls_profile.cpp:61-69 `const QStringList settable = settableCipherNames(full); const QList<QSslCipher> ciphers = resolveCiphers(settable); if (ciphers.size() != settable.size()) { qWarning() ... return false; }` then `cfg.setCiphers(ciphers); cfg.setProtocol(QSsl::TlsV1_2OrLater);`; SChannel branch at :79-84 `if (!backendIsOpenSsl()) { qWarning() << ... \"cipher ORDER is ignored, so the JA3 fingerprint is NOT shaped.\"; return false; }`. Still launch-flag only: Src/App/app.cpp:717-719 `const QString tlsFingerprint = flagValue(argc, argv, \"--tls-fingerprint\"); if (!tlsFingerprint.isEmpty()) { const auto p = Nullock::Core::TlsProfile::fromName(tlsFingerprint);` -- `grep -rn tlsFingerprint\\|TlsProfile ui-v2`: 0 hits, no UI picker.","o":"","r":"Wave 0 register-accuracy audit: held at partial. tls_profile.cpp is unchanged (same partial-resolution no-op-rather-than-mangle contract, same SChannel qWarning-and-return-false). Confirmed again there is no ui-v2 caller for TlsProfile/tlsFingerprint -- still --tls-fingerprint=chrome|firefox|none at process launch only, two canned profiles, no free-form protocol/cipher picker, no TLS 1.3 suite pinning (Qt 6 has no setCiphersuites()). No change."},{"a":"proxy","f":"Intercept client requests: hold, edit, forward, drop in flight","s":"present","i":"low","e":"hours","g":"Backpressure cap: Src/BackEnd/Proxy/intercept_logic.hpp:48 `kMaxPendingIntercepts = 256` -- past that, requests auto-forward uninterceptable (intercept.cpp:162-167). Burp queues without bound. Also no interception rules at all (Group B #10), so every held message must be resolved by hand.","w":"Verified the full chain: the worker really blocks on a QSemaphore, the operator's forward()/drop() releases it, the resolver returns the original bytes verbatim when unedited, and both front ends drive it (ui-v2 buttons and QML app.qml:864-868). Confirmed present. Filled the empty gap with a real limit I found in the code: a hard 256-message cap silently auto-forwards once the operator falls behin","v":"Src/BackEnd/Proxy/proxy_server.cpp:284-291 `if (auto *ic = m_server->interceptController(); ic && inScope) {\\n            const InterceptResult ir = ic->pend(outBytes, req.host, req.port, /*tls=*/false);\\n            if (ir.dropped) { m_client->disconnectFromHost(); return; }` ; block at Src/BackEnd/Proxy/intercept.cpp:221 `p->done.acquire();` ; resolve at intercept.cpp:44-62 forward()/64-78 drop(","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"proxy","f":"Intercept server responses: hold, edit, forward, drop before the client sees them","s":"present","i":"high","e":"hours","g":"Not hooked on the --h2-termination browser leg. Desktop QML front end has no response toggle at all (grep 'responsesEnabled' in Src/App/app.qml: zero hits) -- ui-v2/control-API only. serializeResponse also strips Transfer-Encoding and re-adds Content-Length (proxy_server.cpp:889-895), so what the operator edits is a re-framed response, not the wire bytes.","w":"Verified resolveResponseForClient and all three call sites (plaintext, h2-upstream bridge, h1 MITM keep-alive), plus the independent toggle. Confirmed the two stated gaps by my own greps: 'responsesEnabled|interceptResponses' has no hit in Src/App/app.qml, and the h2-termination leg's omission is documented in-code. Present stands.","v":"Src/BackEnd/Proxy/proxy_server.cpp:1023-1032 resolveResponseForClient(...) pends through interceptController() when responsesEnabled(); call sites at :365 (plaintext), :743 (h2-upstream bridge, browser leg stays h1), :836 (h1 MITM keep-alive). The h2-terminated browser leg (H2Terminator, browserIsH2 branch ~line 660) still intentionally skips response interception -- now documented in-code with an explicit comment block, matching this item's stated gap verbatim. grep for 'responsesEnabled|interceptResponses' in Src/App/app.qml: still zero hits.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"proxy","f":"Intercept message editor: Pretty / Raw / Hex / Params / Headers views + Inspector side panel","s":"partial","i":"high","e":"days","g":"Views expanded: HEADERS/BODY/PREVIEW(Pretty)/HEX/PARAMS joined the existing EDIT(Raw)/INSPECTOR toggle -- six of Burp's named views now present, one more than Repeater's own sibling item (#342, which never gained a Params view). Still genuinely missing: true binary-safe hex editing (the Hex view stays read-only, same concession the gap already called out: an edited binary body cannot be reassembled without corruption). The Params view itself has a real, honestly-scoped limit: it only edits URL query params, a form-urlencoded body, and the Cookie header -- a JSON/multipart/binary body has no key-value shape to show and is left params-invisible (same as Burp on a non-form body). Desktop QML editor (Src/App/app.qml) is unchanged -- still a bare TextArea, ui-v2-only capability, same asymmetry as every other Intercept/Repeater editor item.","w":"Narrowed 2026-08-22 (params wave): added the sixth view, PARAMS, closing the one gap explicitly named by the prior wave's own gap text. RepeaterParamsView (ui-v2/tabs.jsx) renders three editable key-value tables -- QUERY (from the request-line target's querystring), BODY (only when Content-Type is exactly application/x-www-form-urlencoded; hidden, not shown empty, otherwise -- editing a JSON/multipart body as flat key-value pairs would corrupt it), and COOKIE (from the Cookie header, split on ';') -- each row addable/removable/editable, only offered when current.kind !== 1 (a held REQUEST; Burp's Params view has no response analogue either). Every edit round-trips through the same repeaterSplitRaw/repeaterBuildRaw text machinery repeaterChangeMethod/repeaterChangeBodyEncoding already use, writing back into the one real 'edit' buffer that actually gets forwarded -- not a second, divergent state. Query and body pairs are url-decoded for display / url-encoded on write (matching those two existing functions' own convention for form pairs); Cookie pairs are deliberately NOT url-encoded, since real cookie tokens routinely carry raw base64 '+'/'/' characters that repeaterUrlDecode's '+' -> space rule would silently corrupt on a round-trip. Content-Length is recomputed on any body-params edit, same as every other Repeater/Intercept text-rewrite path. No backend change -- pure client-side text derivation/rewrite of the already-fetched held-message text, same architecture as the five sibling views.","v":"ui-v2/tabs.jsx: repeaterParams(raw) (parses queryParams/bodyParams/cookieParams via repeaterSplitRaw + repeaterParseFormPairs/repeaterParseCookiePairs, bodyParams=null unless Content-Type is form-urlencoded); repeaterRebuildParams(raw, {queryParams,bodyParams,cookieParams}) (rewrites target/body/Cookie header via repeaterBuildRaw, recomputes Content-Length); RepeaterParamsView/RepeaterParamRow (the editable table, add/remove/edit row handlers calling repeaterRebuildParams -> onChange(setEditedText)); InterceptTab's RepeaterEditorToolbar views=[\"edit\",\"params\",\"headers\",\"body\",\"preview\",\"hex\",\"inspector\"] for current.kind!==1, unchanged 6-view list (no params) for kind===1 responses; render branch editorView===\"params\" ? <RepeaterParamsView raw={editedText} onChange={setEditedText}/> alongside the existing edit/inspector/readonly branches.","o":"partial","r":"Intercept Params-view wave: partial -> partial, gap narrowed further (not a state flip -- binary-safe hex editing is still the one genuinely missing piece of the six-view set). Added an editable QUERY/BODY/COOKIE Params grid to the held-request editor, closing the prior wave's own explicitly-named remaining gap. No backend change."},{"a":"proxy","f":"Match and replace rules (8 sections; literal-or-regex; per-rule enable; ordered list)","s":"partial","i":"medium","e":"hours","g":"No 'request param name' / 'request param value' sections, and no literal match type (metacharacters must be hand-escaped). fixContentLength only rewrites an EXISTING header (proxy_server.cpp:1418-1425), so a body-rewriting rule on a chunked response leaves the framing wrong -- documented but unfixed.","w":"Verified the enum, both apply functions, the CRUD+move endpoints and the UI form (which is at ui-v2/app.jsx:722-900, not 533-700 as claimed -- the first pass's line numbers are shifted throughout). All stated gaps confirmed: no param-name/param-value sections, and `applyOne` always compiles the find string as a QRegularExpression, so there is no literal mode. Follow-up (2026-08-21): the /api/rules/move endpoint and its real-data.js wrapper ruleMove(from,to) existed with zero callers anywhere in ui-v2 -- rules could be added/removed/toggled from the GUI but never reordered, even though Burp's match/replace list supports drag-reordering. Added up/down buttons per row in RulesTab wired to the existing endpoint; no backend change. State stays partial: the two previously-identified real gaps (no request-param-name/value sections, chunked-response fixContentLength framing) are unaffected and remain open.","v":"Src/BackEnd/Proxy/proxy_server.hpp:75-82 `enum Section { ReqUrl = 0, ReqHeader = 1, ReqBody = 2, RespHeader = 3, RespBody = 4, RespStatus = 5, };` ; regex-only at proxy_server.cpp:1406-1412 `bool applyOne(QString &s, const MatchReplaceRule &r, const QRegularExpression &compiledFind) { ... s.replace(compiledFind, r.replace);` ; endpoints control_server.cpp:3050-3076; UI ui-v2/app.jsx:817-819 `<sele` (truncated in source) -- Rule reorder is now UI-reachable: ui-v2/app.jsx RulesTab row actions gained up/down buttons (boundary-disabled at first/last row) calling NL.actions.ruleMove(i,i-1)/(i,i+1) -> POST /api/rules/move -> ProjectStore::moveRule (project_store.cpp:581), a real, functional backend endpoint that previously had zero UI callers.","o":"partial","r":"Wired the pre-existing /api/rules/move endpoint (ProjectStore::moveRule) to the RulesTab UI via boundary-disabled up/down buttons per rule row -- previously present in the backend and real-data.js with zero UI callers, so rules could not be reordered from the GUI despite full CRUD support. State stays partial (param-name/value sections and chunked-response Content-Length framing remain the real, unaffected gaps)."},{"a":"proxy","f":"Match and replace: per-rule host scoping","s":"exceeds","i":"low","e":"hours","g":"","w":"Verified the field, the compile step, the per-rule enforcement AND the user-facing input -- the host glob is a first-class field in the rules form, so it is genuinely reachable, not internal-only. Burp has no per-rule host scoping. Exceeds confirmed.","v":"Src/BackEnd/Proxy/proxy_server.hpp:86 `QString     hostGlob;    // empty = all hosts; \"*.example.com\" style` ; compiled at proxy_server.cpp:1375-1385; enforced at proxy_server.cpp:1454 `if (!c.hostAll && !c.host.match(req.host).hasMatch()) continue;` ; whole-ruleset gate at :1447 `if (!isInScope(req.host)) return;` with the exfil rationale at :1438-1446. UI: ui-v2/app.jsx:812-814 `<input style={in","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"proxy","f":"HTTP history table with full column set (#, Host, Method, URL, Params, Edited, Status, Length, MIME, Extension, Title, Notes, TLS, IP, Cookies, Time, Listener port, response timing)","s":"partial","i":"medium","e":"days","g":"Missing Edited, Extension, Title, Notes, Cookies, Listener port. Time is dead (always em-dash) because nothing ever measures the round-trip. No column sorting in either front end; the desktop Proxy QML components are placeholder rectangles.","w":"Verified the column set, the model roles, the hardcoded elapsed, the absent sort handlers and the 8-line QML stubs. Confirmed exactly as claimed; `row[\"elapsed\"] = 0;` is at control_server.cpp:1435 and HttpResponse (proxy_server.hpp:46-63) carries no timing field, so the Time column can only ever render em-dash.","v":"ui-v2/proxy.jsx:421-432 `<th><\/th><th>#<\/th><th>Method<\/th><th>Status<\/th><th>Host<\/th><th>Path<\/th><th>Params<\/th><th>Mime<\/th><th>Size<\/th><th>Time<\/th><th>IP<\/th><th>Captured<\/th>` (no onClick anywhere on them); Src/BackEnd/Control/control_server.cpp:1564 `row[\"elapsed\"] = 0;` rendered by ui-v2/proxy.jsx:9 `function fmtMs(n) { if (!n) return \"\\u2014\"; return n + \" ms\"; }`. Desktop QML stub unchanged: Src/FrontEnd/GUI/Proxy/proxy.qml is still 8 lines, a bare placeholder Rectangle.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Column set, model roles, hardcoded `elapsed = 0`, absent sort handlers, and the 8-line QML stub are all byte-identical to the last audit (only line numbers drifted, control_server.cpp :1435->:1564). Still missing Edited/Extension/Title/Notes/Cookies/Listener port columns, still no sorting in either front end, Time column still permanently em-dash. No change."},{"a":"proxy","f":"HTTP history filter bar (in-scope only / hide items without responses / MIME / status / regex + negative + case-sensitive search / extension show-hide / annotation / listener)","s":"present","i":"high","e":"days","g":"Listener/port filter remains missing. Case sensitivity applies to local column/free-text matching; the server regex body-search path remains case-insensitive. Annotation filtering now uses project-persisted, cross-client notes.","w":"Closed 2026-08-10 (5c0c4b4): FilterBar/HistoryTable gain MIME-class/extension/case-sensitivity/negative-search dimensions. Register-accuracy update 2026-08-21: the annotation dimension named in this feature's own title was still marked missing here after c25af6a (2026-08-20) shipped it -- FilterBar now renders an ANNOTATED chip (ui-v2/proxy.jsx:332) and HistoryTable's filter predicate honors annotatedOnly (:114), closing that dimension client-side. Only listener/port remains a real gap. Updated 2026-09-11: 63ecda0e closes the browser-local annotation limitation with project storage and a revisioned read/patch API.","v":"ui-v2/proxy.jsx: MIME_CATEGORIES/mimeCategory() and pathExtension()/parseExtList()/extFilterMatch()/parseSearchTerm() helpers; HistoryTable's useMemo predicate applies mimeFilter/extList/extHide/caseSensitive/negate/annotatedOnly (:107-148); FilterBar renders the MIME select, EXT input+toggle, Aa case-sensitivity button, and ANNOTATED chip (:332); ProxyTab's `shown` count mirrors the same predicate so the header stays in sync.","o":"","r":"Annotation persistence caveat removed; unrelated filtering gaps remain documented."},{"a":"proxy","f":"HTTP history persistence + search at engagement scale","s":"present","i":"high","e":"days","g":"None left that this cloud session can close. A DB SEARCH overlay on the Proxy tab (ui-v2/proxy.jsx) wires /api/history/find directly: method/host/path (LIKE)/status/min-max size/since-minutes/limit filters, a results table, and an inline full-raw request/response view for the selected result via NL.requestRawById/responseRawById. A 2026-09-02 pass found and closed a narrower gap in the OTHER path to an evicted row: the main DetailPane's row selection (ui-v2/proxy.jsx `selectedRow = rows.find(...)`) had no cold-storage fallback of its own -- requestRawById/responseRawById's eviction-safe fetch only covered the raw request/response bytes, not the row metadata DetailPane gates rendering on, so a row selected before the in-memory window evicted it silently collapsed to \"select a row to inspect\" mid-session. Now closed via NL.historyFullById() wiring the previously-orphaned GET /api/history/full/<id> (control_server.cpp:4607) as that fallback.","w":"Closed this session (2026-08-13, DB Search wave): added DbSearchOverlay + the pure buildHistoryFindFilters helper to ui-v2/proxy.jsx, a DB SEARCH button next to WS REPEATER/H2 FRAME LOG in the HTTP HISTORY pane-head, and NL.actions.historyFind() in ui-v2/real-data.js posting to the existing, previously-orphaned /api/history/find. 2026-09-02 follow-up: the prior note's claim that \"DetailPane already used\" an eviction-safe cold-fetch path was only half true -- that covered raw bytes (requestRawById/responseRawById -> buildHistoryRow()'s SQLite fallback), not the row metadata (host/method/path/status/tls/...) DetailPane's `if (!row) return <placeholder>` gates on. Added NL.historyFullById(rowId) to ui-v2/real-data.js: a memoized sync-XHR accessor (same pattern as requestRawById/responseRawById) that GETs the previously-unwired /api/history/full/<id>, maps its JSON onto the same row shape NL.rows entries carry (id/method/host/port/path/url/status/size/tls/elapsed), and pre-seeds the raw-body cache from the same response. ui-v2/proxy.jsx's `selectedRow` computation now falls back to it when `rows.find` misses.","v":"ui-v2/proxy.jsx DbSearchOverlay + buildHistoryFindFilters, ProxyTab's DB SEARCH button; ui-v2/real-data.js NL.actions.historyFind; Src/BackEnd/Control/control_server.cpp:4072-4083 POST /api/history/find; Src/Core/Storage/history_logic.hpp/.cpp buildFindQuery (filter set); Src/Core/Storage/history_index.cpp:296-337 find() (returned row shape). 2026-09-02: ui-v2/real-data.js NL.historyFullById(); ui-v2/proxy.jsx `selectedRow` fallback (search \"NL.historyFullById\"); Src/BackEnd/Control/control_server.cpp:4601-4639 GET /api/history/full/<id> handler (its own comment names the evicted-row-still-selected case).","o":"present","r":"Follow-up: closed the metadata half of the eviction gap left over from the 2026-08-13 DB Search wave -- DetailPane's own selectedRow lookup (distinct from the DB Search overlay's self-contained flow) had no cold-storage fallback, so a row selected before eviction would silently drop out of view. Wired the previously-orphaned GET /api/history/full/<id> via a new NL.historyFullById() accessor. Verified: bundled-babel transform of ui-v2/proxy.jsx succeeds; Node functional test of the row-shape mapping (path->url mirroring, null-on-missing/error) and the rows.find-then-fallback selection logic (present row never triggers fallback, evicted id does, null selection short-circuits); backend read directly from source (control_server.cpp:4607-4639) to confirm the endpoint's field set and SQLite cold-storage fallback match what the frontend now consumes. No C++ build available in this cloud session -- backend code itself was not touched, only its consumption."},{"a":"proxy","f":"WebSockets history (separate tab, message direction, length, comment, filtering)","s":"partial","i":"medium","e":"days","g":"Captured only on the TLS MITM leg -- runWebSocketRelay is invoked solely from the h1 MITM keep-alive loop's 101 Upgrade branch (proxy_server.cpp), so a plaintext ws:// tunnel is never relayed or logged; Burp captures both. Connections are also grouped client-side by host:port only, since a history row carries no per-tunnel session id -- two concurrent WS tunnels to the same host:port interleave in one bucket in the new tab. Both are backend-shaped gaps outside what this frontend-only wave could close.","w":"Closed the frontend half of this item 2026-08-17: a dedicated WEBSOCKETS tab (ui-v2/app.jsx WebSocketsTab) reads the same NL.rows entries the Proxy tab already shows as pseudo-HTTP WS↑/WS↓ rows (no new backend call), groups them into a CONNECTIONS list keyed by host:port, and renders each message with real columns instead of the cosmetic Status/Mime pair: Direction (parsed from the WS↑/WS↓ method), Type/deflate/continued (parsed out of the synthetic path string \"(<opcode>[ deflate], <n> B[, continued])\" -- the only place proxy_server.cpp's emitMessage carries those flags), Length (the row's existing numeric size field, already accurate -- payload.size()), Time, and a per-message free-text Comment (localStorage-persisted client state, the same client-only pattern as Comparer/Decoder -- there is no backend field for a WS message comment). A DIRECTION (up/down) and TYPE (text/binary/close/ping/pong) filter bar sits above the message table. Selecting a message renders it through proxy.jsx's DetailPane -- the exact component the Proxy tab already renders these same rows through -- so Raw/Headers/Body/Hex/Inspector and every Send-to-Repeater/Intruder/Comparer/Decoder/Sequencer pivot work identically here. State stays partial, not present: the feature name promises parity with Burp's WebSockets history, and Burp captures plaintext ws:// traffic too -- Nullock's relay only ever ran on the TLS-MITM leg, a real capture-scope gap this frontend-only session cannot close (needs a plaintext-WS relay path in proxy_server.cpp, a C++ change this cloud session cannot build/verify).","v":"ui-v2/app.jsx WebSocketsTab (new component) + TABS entry `{id:\"websockets\", label:\"WEBSOCKETS\"}` + tab-render switch; WS_PATH_RE parses Src/BackEnd/Proxy/proxy_server.cpp:1086-1090 `req.path = QString(\"(%1%2, %3 B%4)\").arg(label).arg(deflate).arg(payload.size()).arg(continued)`; row.size already carries `resp->body.size()` per control_server.cpp:1440; DetailPane reused verbatim from ui-v2/proxy.jsx (same component ProxyTab mounts); capture-scope gap confirmed at the sole runWebSocketRelay call site, proxy_server.cpp's h1 MITM 101-Upgrade branch.","o":"","r":"WEBSOCKETS tab (ui-v2/app.jsx) closes the tab/direction/length/comment/filtering half of this item -- reused proxy.jsx's DetailPane for message detail + every Send-to- pivot, no backend touched. Left honestly partial: plaintext ws:// is never captured (TLS-MITM-only relay, a backend gap) and concurrent same-host:port tunnels interleave in one connection bucket (history rows carry no per-tunnel session id)."},{"a":"proxy","f":"WebSocket message injection into a live connection (Burp: WebSocket Repeater)","s":"present","i":"medium","e":"hours","g":"None -- ProxyTab (ui-v2/proxy.jsx) HTTP HISTORY pane-head gains a WS REPEATER button opening an overlay that polls GET /api/ws/sessions every 2s, offers direction (up/down) + opcode (text/binary/close/ping/pong) selectors and a payload editor, queues the frame via POST /api/ws/send, and offers a one-click resend-last. Frame history in the panel itself is still absent (each send is fire-and-forget against the live relay) -- that gap is tracked separately under #269 WebSockets history.","w":"Closed 2026-08-12: added NL.actions.wsSessions()/wsSend() (ui-v2/real-data.js) and a WsRepeaterOverlay component (ui-v2/proxy.jsx) wired to a toolbar button in the Proxy tab. Both response fields read by the overlay (sessions[].id/host/port/framesUp/framesDown and send response ok/queued) match control_server.cpp exactly -- verified by reading the handlers directly (GET /api/ws/sessions control_server.cpp:2009-2024, POST /api/ws/send :5689-5735) rather than trusting the prior audit note alone.","v":"ui-v2/proxy.jsx WsRepeaterOverlay + WS_OPCODES + wsRepeaterOpen toolbar button in ProxyTab; ui-v2/real-data.js NL.actions.wsSessions/wsSend; backend unchanged -- Src/BackEnd/Proxy/ws_repeater.hpp Q_INVOKABLE sendFrame; control_server.cpp:2009-2024 (/api/ws/sessions) and :5689-5735 (/api/ws/send).","o":"present","r":"WS Repeater wave: WebSocket message injection UI closes the GUI-reachability gap for /api/ws/send + /api/ws/sessions."},{"a":"proxy","f":"HTTP/1.1 keep-alive on the proxied connection","s":"partial","i":"medium","e":"hours","g":"Cleartext HTTP tears the connection down after every request regardless of Connection: keep-alive, and any pipelined follow-up bytes are dropped. Slow on HTTP-only targets and it changes the connection behaviour the origin observes -- which matters for smuggling/desync work. No 'use keep-alive if the server supports it' setting either way.","w":"Verified both legs. The MITM keep-alive loop and its close semantics (explicit Connection: close either side, HTTP/1.0 default-close with keep-alive opt-in) are correct. The plaintext leg really is one-request-per-connection with an unconditional disconnect. Partial confirmed.","v":"Plaintext leg, Src/BackEnd/Proxy/proxy_server.cpp:366-369 `if (ir.dropped) { m_client->disconnectFromHost(); return; } m_client->write(ir.bytes); waitWritten(m_client, kReadTimeoutMs, m_server); m_client->disconnectFromHost();` -- end of run(), no loop, one request per connection. MITM leg still loops with Connection: close handling (proxy_server.cpp:752-860 region).","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-read run()'s plaintext leg end-to-end: still an unconditional disconnectFromHost() after exactly one response, no keep-alive loop, no setting to opt in. The MITM leg's loop-and-honor-Connection-close semantics are unchanged. No change (evidence line numbers refreshed from :313-315 to :366-369)."},{"a":"proxy","f":"Miscellaneous proxy options (HTTP/1.0 downgrades, forced Connection: close, strip Proxy-*, normalise Accept-Encoding, strip Sec-WebSocket-Extensions, unpack compressed messages, don't log to history)","s":"partial","i":"low","e":"days","g":"Seven of nine absent: no HTTP/1.0 downgrade either direction, no forced Connection: close, no Accept-Encoding normalisation, no Sec-WebSocket-Extensions strip (so permessage-deflate cannot be turned off), no 'stop logging to history'. (The Proxy-Authorization-leak gap noted in the last audit is fixed: it is now stripped alongside Proxy-Connection, not forwarded upstream.)","w":"Verified both implemented items and re-grepped the rest myself across Src/BackEnd/Proxy: 'Sec-WebSocket-Extensions' and 'Accept-Encoding' still return zero hits in the proxy path. Confirmed 2-of-9. Correction from the last audit: the proxy-hop header strip is no longer Proxy-Connection-only -- serializeRequestForOrigin() now calls HttpLogic::isProxyHopRequestHeader(), which matches BOTH Proxy-Connection and Proxy-Authorization, so the credential-leak gap the last audit flagged no longer exists. This doesn't change the 2-of-9 count (strip-proxy-headers was already counted present) but the old evidence's claim that Proxy-Authorization leaks upstream is now false.","v":"Src/BackEnd/Proxy/proxy_logic.cpp:148-151 `bool isProxyHopRequestHeader(const QString &name) { return name.compare(QLatin1String(\"Proxy-Connection\"), Qt::CaseInsensitive) == 0 || name.compare(QLatin1String(\"Proxy-Authorization\"), Qt::CaseInsensitive) == 0; }`, called from Src/BackEnd/Proxy/proxy_server.cpp:1306 `if (HttpLogic::isProxyHopRequestHeader(h.first)) continue;` inside serializeRequestForOrigin(). Decode-for-inspection (the other present-of-9 item) at proxy_server.cpp:987 `const QByteArray dec = decodeContentEncoding(...)`. `grep -n 'Sec-WebSocket-Extensions\\|Accept-Encoding' Src/BackEnd/Proxy/proxy_server.cpp`: 0 hits.","o":"","r":"Wave 0 register-accuracy audit: held at partial (2-of-9), but with a real evidence correction, not just a line refresh. The last audit's evidence said 'the header strip really is only Proxy-Connection -- Proxy-Authorization is forwarded to the origin verbatim' and the gap text listed that as a leaked-credential gap. That is now false: serializeRequestForOrigin() (proxy_server.cpp:1299-1312) was refactored to call the new HttpLogic::isProxyHopRequestHeader() (proxy_logic.cpp:148-151), which strips both Proxy-Connection and Proxy-Authorization before forwarding to the origin. Re-verified Sec-WebSocket-Extensions/Accept-Encoding normalisation are still entirely absent from the proxy path (0 grep hits), so the 2-of-9 count is unchanged -- gap and why text corrected to drop the now-false leaked-credential claim."},{"a":"proxy","f":"'Don't send items to Proxy history or live tasks, if out of scope'","s":"present","i":"low","e":"hours","g":"None -- the ProxyServer bool, endpoint, and now the ui-v2 checkbox all exist. Scope tab's SCOPE pane-head carries a 'log out-of-scope traffic' checkbox (default OFF = Burp's default 'don't send' behavior) that toggles ProxyServer::m_logOutOfScope via POST /api/proxy/log-out-of-scope. When off, out-of-scope requests and responses are dropped from Proxy history AND live tasks (passive scan); when on, everything is kept. MITM tunnelling of out-of-scope HTTPS is unchanged, matching Burp.","w":"Closed 2026-08-20: the backend half (m_logOutOfScope + POST /api/proxy/log-out-of-scope {value} + bootInfo.logOutOfScope snapshot) shipped in 80f8ec9; this wave adds the missing GUI control -- a Scope-tab checkbox wired through a new log-out-of-scope-toggle reducer case and NL.actions.setLogOutOfScope. logIt = inScope || logOutOfScope() gates both requestReceived and responseReceived (proxy_server.cpp:292/335), and app.cpp fans responseReceived to both the history model and the passive scanner, so the single toggle controls history and live tasks together, exactly Burp's checkbox.","v":"Backend: proxy_server.cpp:292 `const bool logIt = inScope || m_server->logOutOfScope();` gating requestReceived (:293) and responseReceived (:335); control_server.cpp:3190-3198 POST /api/proxy/log-out-of-scope; control_server.cpp:1232 bootInfo[\"logOutOfScope\"]. UI: ui-v2/tabs.jsx ScopeTab SCOPE pane-head 'log out-of-scope traffic' checkbox -> dispatch{type:'log-out-of-scope-toggle'}; ui-v2/app.jsx log-out-of-scope-toggle reducer case + logOutOfScope state slice (initial from NL.bootInfo.logOutOfScope, nl-snapshot merge); ui-v2/real-data.js NL.actions.setLogOutOfScope -> POST /api/proxy/log-out-of-scope {value}.","o":"present","r":"partial -> present. The 80f8ec9 wave left this at partial ONLY because the ui-v2 checkbox was missing (all backend/API/snapshot plumbing was already done and e2e-verified 6/6). This wave adds that checkbox to the Scope tab: a 'log out-of-scope traffic' toggle (default OFF, matching Burp's default) bound to the existing POST /api/proxy/log-out-of-scope endpoint via a new reducer case + NL.actions.setLogOutOfScope, reading its initial/live state from bootInfo.logOutOfScope. No backend change. Verified: bundled-babel transform of app.jsx/tabs.jsx/real-data.js; NUL byte in tabs.jsx still exactly 1 occurrence; a 10-check Node functional test of the reducer toggle + snapshot-merge + init-coercion logic; a 12-check hook-stubbed vm render of ScopeTab across off/on/undefined states confirming the checkbox reflects the prop and its onChange dispatches log-out-of-scope-toggle."},{"a":"proxy","f":"HTTP/2 support to the server (ALPN h2 upstream, h2-to-h1 translation)","s":"present","i":"low","e":"weeks","g":"Only reachable inside a successful MITM tunnel, so it inherits the openssl dependency and the blocklist stickiness. Editing an intercepted request on this leg is honoured, but the response the operator sees is re-framed by serializeResponse rather than being upstream's wire bytes.","w":"Verified the ALPN offer, the negotiation check, the reject-unexpected-ALPN branch, the persistent-session bridge loop, and the header translation (pseudo-header order, hop-by-hop drop, Connection-named-field drop). This is a real, default-on, user-reachable path. Present confirmed.","v":"Src/BackEnd/Proxy/proxy_server.cpp:438-441 `upstreamCfg.setAllowedNextProtocols({\\n            QByteArrayLiteral(\"h2\"),\\n            QByteArrayLiteral(\"http/1.1\"),\\n        });` ; :489-495 negotiation + unexpected-ALPN bailout; bridge at :584-614 `if (upstreamIsH2) { m_server->noteH2Upstream(); H2Client h2; ... const auto h2res = h2.send(upstream, req);` ; translation Src/BackEnd/Proxy/h2_client_l","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"proxy","f":"HTTP/2 multiplexing to the server (concurrent streams on one connection)","s":"stub","i":"medium","e":"weeks","g":"Concurrent multiplexing is dead code from a user's perspective: no proxy path, no control endpoint, no test exercises it with N>1. Requests to an h2 origin are serialised, so h2-specific concurrency behaviour (stream interleaving, single-packet attacks, race conditions) cannot be observed or exercised.","w":"DOWNGRADED HARD -- this is the most expensive wrong 'present' in the set. sendConcurrent() is real and correctly implemented, but I grepped every caller in Src and Tests: the ONLY call in the entire repository passes a single-element list. The proxy never uses it; both proxy paths use send(), one request at a time. On the h1-browser leg the loop is strictly read-request/send/read-response; on the ","v":"Only caller: Src/BackEnd/Proxy/http2_client.cpp:494-495 `H2Client::Result H2Client::sendRequest(QSslSocket *sock, const HttpRequest &req) { const QList<Result> rs = sendConcurrent(sock, { req }); }` -- and sendRequest itself has no caller outside this file (`grep -rn sendRequest\\( Src Tests`: only the .hpp declaration). The proxy uses the sequential persistent-connection API instead: proxy_server.cpp:632 `const auto r = upstreamH2.send(upstream, req);` and :713 `const auto h2res = h2.send(upstream, req);`, both inside per-stream while loops that send one request at a time. `grep -rln sendConcurrent Tests/`: no hits, no test exercises N>1.","o":"","r":"Wave 0 register-accuracy audit: held at stub. Re-confirmed sendConcurrent()'s only caller (H2Client::sendRequest) is itself uncalled outside http2_client.cpp, and both live proxy paths (persistent-connection leg and per-tunnel leg) still use the sequential .send() API one request at a time. No test in Tests/ exercises sendConcurrent with N>1. The correctly-implemented concurrent-stream code remains entirely dead from a user's perspective. No change."},{"a":"proxy","f":"Proxy listener > HTTP > allow the CLIENT to use HTTP/2 (browser-to-proxy h2, on by default in Burp)","s":"partial","i":"medium","e":"weeks","g":"Off by default, so in the shipped configuration every browser is downgraded to HTTP/1.1 on the proxy leg -- hiding h2-specific origin behaviour. When enabled: request edits are silently discarded (only drop works), response interception is disabled on that leg, and upstream fan-out is sequential.","w":"Verified the flag, the gated ALPN offer, the terminator, and all three stated limitations (sequential upstream, drop-only request editing, no response interception) directly in the code and its comments. Partial confirmed.","v":"Src/BackEnd/Proxy/proxy_server.hpp:243-244 `void setH2Termination(bool on) { m_h2Termination = on; } bool h2Termination() const { return m_h2Termination; }`, default at :335 `bool m_h2Termination = false;   // --h2-termination (Phase 3, experimental)`; gate at proxy_server.cpp:465 `if (m_server->h2Termination())` before offering the h2 ALPN protocol; flag parsed at Src/App/app.cpp:744 `proxy.setH2Termination(hasFlag(argc, argv, \"--h2-termination\"));`.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Flag name, default-false, and the ALPN gate are all unchanged (only line numbers drifted). Still off by default, still launch-flag only with no UI toggle. Did not re-verify the three stated in-code limitations (drop-only request editing, no response interception, sequential upstream fan-out on that leg) beyond confirming the surrounding code is untouched since the last audit. No change."},{"a":"proxy","f":"HTTP/2 frame-level visibility (Burp has no frame log at all)","s":"present","i":"low","e":"days","g":"None on GUI reachability -- the Proxy tab's HTTP HISTORY pane-head gains an H2 FRAME LOG button (an overlay showing a per-stream summary table from GET /api/h2/streams and a live-tailing raw frame feed from GET /api/h2/events?since=<cursor>, polled every 2s while open). The remaining honest caveat: this is a passive viewer, not a filter/search tool -- no per-connection filtering, no frame-type filter, capped at the last 500 tailed frames client-side.","w":"Closed the GUI-reachability gap this wave: NL.actions.h2Streams()/h2Events(sinceMs) added to real-data.js, and a new H2FrameLogOverlay component in ui-v2/proxy.jsx renders the stream table (conn/streamId/method/path/status/bytesIn/bytesOut/framesIn/framesOut/closed) plus the frame feed (ts/conn/type/flags/streamId/bytes/errorCode), reusing the WS Repeater overlay's polling-modal pattern. Every field read matches control_server.cpp's actual JSON response for both handlers exactly -- no invented fields.","v":"ui-v2/real-data.js NL.actions.h2Streams/h2Events; ui-v2/proxy.jsx H2FrameLogOverlay + the H2 FRAME LOG button in the HTTP HISTORY pane-head; backend unchanged -- control_server.cpp:1961 GET /api/h2/streams, :1984 GET /api/h2/events?since=<ms>, both already allowlisted in isReadPath (:1669-1670).","o":"present","r":"Wave 2 (frontend-only): added the H2 Frame Log overlay to the Proxy tab, closing #277's GUI-reachability gap (state stays present -- the underlying capability was already present, only the UI affordance was missing). No backend touched."},{"a":"proxy","f":"Burp's built-in browser / one-click proxy + CA configuration for the client","s":"partial","i":"medium","e":"days","g":"No pre-configured browser instance; CA trust is still a manual per-OS step; the extension is Chromium-only and defaults to port 8080 regardless of --proxy-port. The PAC sends all RFC1918 traffic DIRECT, so internal targets silently never reach the proxy.","w":"Verified the PAC handler and the MV3 extension (manifest_version 3, 'proxy' permission, fixed_servers). Partial confirmed. I found an additional defect the first pass missed: the generated PAC returns DIRECT for every RFC1918 range, so an internal-engagement target on 10.x/192.168.x/172.16-31.x bypasses the proxy entirely.","v":"Src/BackEnd/Control/control_server.cpp:1856 `pac += \"        || shExpMatch(host, \\\"10.*\\\")\\n\";` ... :1864 `pac += \"    return \\\"PROXY 127.0.0.1:\\\" + QByteArray::number(pport) + \\\"\\\\\\\";\\\\n\\\";` -- the whole 172.16/12 and 192.168/16 and 10/8 ranges still return DIRECT before the PROXY fallback. Extension: browser-ext/background.js:19 `proxyPort: 8080,` (DEFAULTS), applied verbatim at :36-42 `await chrome.proxy.settings.set({ value: { mode: \"fixed_servers\", rules: { singleProxy: { scheme: \"http\", host: cfg.proxyHost, port: cfg.proxyPort } ...`. background.js:67 does read `j.bootInfo?.port` from a live /api/snapshot ping, but only to display it in the popup status -- it is never fed back into applyProxy()'s port, so a non-default --proxy-port still requires the user to manually edit and save the extension's port field.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-checked the PAC generator: the RFC1918 DIRECT bypass for 10.*/192.168.*/172.16-31.* is unchanged (still means an internal-engagement target on those ranges silently never reaches the proxy). Re-checked background.js in full this pass (not just the applyProxy snippet the last audit quoted): it does now surface the live control-server's port via pingControl()'s j.bootInfo?.port for the popup's status display, but that value is read-only informational -- applyProxy() still sources its port from DEFAULTS/chrome.storage (8080 unless the user manually edits and saves it in the popup), so 'defaults to port 8080 regardless of --proxy-port' still holds in practice. No functional change to the gap; evidence expanded to cover this so a future pass doesn't mistake the informational readout for an auto-sync fix."},{"a":"proxy","f":"Proxy on/off toggle preserving the configured listener port","s":"present","i":"medium","e":"hours","g":"Toggling off/on from either UI silently rebinds to 8080 (or the next free port in the fallback list), which is not necessarily where the browser/PAC/extension is pointed. No UI for choosing the port at all -- launch flag only.","w":"Verified: the toggle endpoint calls the zero-argument start(), whose defaults are LocalHost:8080 -- the operator's --proxy-port is only applied at app.cpp:749-751 and is not remembered anywhere. Confirmed real, and confirmed the fallback port walk. Partial stands.","v":"Src/BackEnd/Control/control_server.cpp:2971-2975 `if (path == \"/api/proxy/toggle\") {\\n        if (m_wiring.proxy) {\\n            if (m_wiring.proxy->isRunning()) m_wiring.proxy->stop();\\n            else                             m_wiring.proxy->start();` against Src/BackEnd/Proxy/proxy_server.hpp:102-103 `Q_INVOKABLE bool start(const QHostAddress &address = QHostAddress::LocalHost,\\n           ","o":"partial","r":"partial -> present. The audit evidence is STALE: /api/proxy/toggle no longer calls the zero-arg start() -- it calls restart() (control_server.cpp:3139-3147), which re-listens on the remembered m_bindAddress + m_bindPort (proxy_server.cpp:1899-1943 stores the actually-bound port on every successful listen; restart() replays it). So a toggle preserves BOTH the off-loopback --proxy-bind and the custom --proxy-port instead of reverting to 127.0.0.1:8080; shipped in a6b57a0 ('toggle-safe'). VERIFIED e2e vs the live app: started on a distinctive custom --proxy-port (34759, outside the 8080/8081/8888/... fallback walk), toggled off (proxy stops), toggled on -> came back on the SAME 34759, never 8080 (5/5). The gap's second clause ('no UI for choosing the port') is a distinct capability tracked by the separate absent item 'Proxy listeners: multiple simultaneous listeners (add/edit/remove, per-listener ...)', not this toggle-behavior item; the port is configured today via --proxy-port. No code change this reconcile -- verification of already-shipped behavior."},{"a":"proxy","f":"Save/export proxy history items (Burp: 'Save items' XML; HAR import is extension-only)","s":"exceeds","i":"low","e":"hours","g":"No Burp-XML 'Save items' format for interop (HAR-only). The prior redact-only-via-API gap is now closed: the Export HAR button in Settings' Project card has an 'include unredacted auth material' checkbox that posts {redact:false}.","w":"Closed the redact-toggle gap this pass: real-data.js's exportHar() took no arguments, so the UI could never reach control_server.cpp's existing bodyJson.value(\"redact\") override -- confirmed by grep showing zero call sites passing an options object before this change. Now exportHar(opts) forwards opts to POST /api/har/export and Settings gained a bound checkbox. HAR round-trip import/export beyond Burp's extension-only HAR support remains exceeds; only the gap text changed to describe the still-real Burp-XML-format absence.","v":"Src/BackEnd/Control/control_server.cpp:6045-6053 /api/har/export honors bodyJson.value(\"redact\") to override the default-on ProjectStore::exportRedact; ui-v2/real-data.js:204 exportHar(opts) now forwards opts (was exportHar() with no params); ui-v2/app.jsx new harUnredacted state + checkbox next to the Export HAR button in SettingsTab's Project card wires it end to end.","o":"exceeds","r":"Wave 2: Export HAR redact toggle -- Settings' Export HAR button gains an 'include unredacted auth material' checkbox (harUnredacted state) that posts {redact:false} through a new exportHar(opts) parameter, closing the previously-named gap that the backend's existing redact override was UI-unreachable. State stays exceeds (native HAR round-trip already beat Burp's extension-only HAR support); only the gap text changed. No backend touched -- control_server.cpp already read bodyJson.value(\"redact\")."},{"a":"proxy","f":"Proxy listener: Bind to address (loopback only / all interfaces / specific local IP)","s":"present","i":"blocker","e":"hours","g":"None -- --proxy-bind=ADDR binds the proxy to loopback, all interfaces, or a specific IP (a non-loopback bind requires the explicit --proxy-bind-insecure acknowledgement, since it exposes a cert-forging MITM to the LAN). Phones, tablets, VMs and second machines can now be proxied.","w":"I re-grepped for every synonym I could think of (proxy-bind, proxy-listen, proxy-host, iface, interface, QHostAddress::Any, AnyIPv4, 0.0.0.0, allInterfaces) across Src, ui-v2, docs and README. The only Any-bind hits are the OAST/workspace standalone tools and the control server's --listen. The proxy is hardcoded to LocalHost at its single call site. Confirmed absent, and the blocker rating is righ","v":"Src/App/app.cpp:749-751 `const bool proxyStarted = (wantedProxyPort > 0)\\n        ? proxy.start(QHostAddress::LocalHost, wantedProxyPort)\\n        : proxy.start();` ; default also loopback (proxy_server.hpp:102). --listen applies only to the control API: Src/App/app.cpp:990-993 `if (listenArg == \"0.0.0.0\" || listenArg.compare(\"any\", Qt::CaseInsensitive) == 0)\\n            ctlAddr = QHostAddress::A","o":"present","r":"--proxy-bind=ADDR (or NULLOCK_PROXY_BIND) binds the proxy to loopback (default), all interfaces (0.0.0.0/::), or a specific IP. Because an off-loopback intercepting proxy is a LAN-exposed cert-forging MITM, a non-loopback bind is refused without the explicit --proxy-bind-insecure ack and prints a warning -- stricter than Burp's checkbox. ProxyServer::restart() remembers the bind so /api/proxy/toggle preserves it (also fixing a toggle that reset --proxy-port). Verified: netstat shows 0.0.0.0:PORT LISTENING with the ack, FATAL exit-1 without. Gauntlet 93/93 + 156/156."},{"a":"proxy","f":"Proxy listeners: multiple simultaneous listeners (add/edit/remove, per-listener config, running checkbox)","s":"absent","i":"medium","e":"days","g":"One listener, one port, one configuration. No per-listener request handling, no listener column in history, no way to run an invisible listener alongside a normal one.","w":"Confirmed by reading the class: one QTcpServer member, constructed once, one listen() call. My own grep for addListener/listenerPort/listeners across Src and ui-v2 found nothing but unrelated JS event listeners and the OAST tool's comment. Absent confirmed.","v":"Src/BackEnd/Proxy/proxy_server.hpp:325 `QTcpServer *m_server;` ; Src/BackEnd/Proxy/proxy_server.cpp:1315 `ProxyServer::ProxyServer(QObject *parent) : QObject(parent), m_server(new SslReadyTcpServer(this)) {` ; single bind loop at proxy_server.cpp:1940-1941 `for (quint16 p : tries) { if (m_server->listen(address, p)) {`.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Still exactly one QTcpServer member, constructed once, one bind loop that stops at the first port that succeeds. Re-ran `grep -rn addListener\\|listenerPort Src ui-v2`: no hits besides unrelated JS/comment noise. Absent confirmed (line numbers refreshed)."},{"a":"proxy","f":"Proxy listener > Request handling > Redirect to host / Redirect to port","s":"absent","i":"medium","e":"hours","g":"Cannot pin traffic at a specific backend host/port -- the standard technique for testing one node behind a load balancer, or pointing a hardcoded thick-client endpoint at a lab box.","w":"Re-grepped redirectHost/redirectTo/forceTls/forceSsl/forceHttps across Src, ui-v2 and browser-ext -- the only hits are the open-redirect SCANNER (Src/Core/Networking/open_redirect.*), which is unrelated vocabulary. The upstream destination is taken verbatim from the request with no override hook. Absent confirmed.","v":"Src/BackEnd/Proxy/proxy_server.cpp:314 `upstream.connectToHost(req.host, req.port);` with req.host/port set only by rewriteHostPort (proxy_server.cpp:244-264); CONNECT side parses the target the same way and passes it straight to runMitmTunnel/runBlindTunnel with no override hook anywhere.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-grepped redirectHost/redirectTo/forceTls/forceSsl/forceHttps across Src, ui-v2 and browser-ext -- the only hits are still the unrelated open-redirect SCANNER vocabulary. The upstream destination is still taken verbatim from the request with no override field, flag, or endpoint. No change."},{"a":"proxy","f":"Proxy listener > Request handling > Force use of TLS","s":"absent","i":"low","e":"hours","g":"HTTP-in / HTTPS-out rewriting is impossible, so you cannot strip TLS for a client that only speaks HTTP while still talking TLS to the origin.","w":"Confirmed: the cleartext path constructs a plain QTcpSocket with no conditional upgrade, and there is no flag/field/endpoint that would switch it. Same greps as the redirect item. Absent confirmed.","v":"Src/BackEnd/Proxy/proxy_server.cpp:313-317 `QTcpSocket upstream; upstream.connectToHost(req.host, req.port); if (!waitConnected(&upstream, kReadTimeoutMs, m_server)) {` -- a QTcpSocket, never a QSslSocket; the only QSslSocket upstream is inside runMitmTunnel (connectToHostEncrypted at :540).","o":"","r":"Wave 0 register-accuracy audit: held at absent. The cleartext path still constructs a plain QTcpSocket unconditionally; still no flag/field/endpoint that would switch it to TLS. Same greps as the redirect item, same zero hits. No change (evidence line numbers refreshed)."},{"a":"proxy","f":"Proxy listener > Certificate > Use a custom certificate (PKCS#12) / self-signed / CA-signed with specific hostname","s":"absent","i":"low","e":"days","g":"Cannot present a supplied certificate to the client -- needed when the target pins a cert you legitimately hold, or when a listener must present a corp-issued cert.","w":"Confirmed with my own grep: `pkcs12|PKCS12|\\.pfx` returns ZERO hits across the entire repository (Src, ui-v2, browser-ext). CertAuthority exposes exactly one minting entry point and the tunnel has exactly two outcomes (forged leaf or blind tunnel). Absent confirmed.","v":"Whole public API unchanged: Src/BackEnd/Proxy/cert_authority.hpp:26-33 `Q_INVOKABLE bool ensureCa(); ... LeafCert leafCertFor(const QString &host);` ; only consumer Src/BackEnd/Proxy/proxy_server.cpp:389-395 `leaf = ca->leafCertFor(host); ... if (leaf.valid()) { runMitmTunnel(...) } else { runBlindTunnel(...) }`.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-ran `grep -rn 'pkcs12|PKCS12|\\.pfx'` across the whole repo: still zero hits. CertAuthority still exposes exactly one minting entry point and the tunnel still has exactly two outcomes (forged leaf or blind tunnel). No supplied-certificate path exists. No change."},{"a":"proxy","f":"Per-host leaf certificates for IP-address and IPv6 targets (IP SANs)","s":"partial","i":"high","e":"hours","g":"IP SAN emission is now correct for BOTH families: sanEntryForHost returns IP:<addr> for an IPv4 literal (already) AND for an IPv6 literal (new strict isIpv6Literal), and isValidHostForCert now accepts a validated IPv6 (its ':' was previously rejected, so IPv6 targets never reached minting and fell through to a blind tunnel). Remaining for full parity: multi-SAN and wildcard-SAN leaves, and the live-handshake path (the forged-leaf CONNECT+MITM over a real socket, plus removing a single auto-added MITM-blocklist entry) -- socket-path work outside headless verification.","w":"isIpv6Literal is a strict, Qt6::Core-only textual validator (full/compressed/embedded-IPv4/'::' forms; rejects zone id, a second '::', empty/oversize/non-hex groups) mutation-proven in cert_logic_test, wired into sanEntryForHost (IP: SAN) and isValidHostForCert (accept), so an IPv6 target now mints a correct IP:<addr> leaf instead of being blind-tunnelled. The IPv4 half was already emitting IP: (this gap's 'DNS:192.168.1.10' claim was stale). Held partial for multi/wildcard SAN + the socket-level MITM handshake.","v":"Src/BackEnd/Proxy/cert_authority.cpp:246-250 `const QString contents = QStringLiteral(\\n            \"subjectAltName = %1\\n\" ...).arg(CertLogic::sanEntryForHost(host));` -- SAN type now dynamic. Src/BackEnd/Proxy/cert_logic.cpp:19-60 `bool isIpv6Literal(...)` (strict textual validator) and :62-66 `isValidHostForCert` accepts it (`if (isIpv6Literal(host)) return true;`); :98-101 `sanEntryForHost` returns `IP:<addr>` for either family.","o":"partial","r":"IPv6 half done, completing the IPv4 work from 81a0ba2. Added a strict, Qt6::Core-only CertLogic::isIpv6Literal (full/compressed/embedded-IPv4/'::' forms; rejects zone id, a second '::', empty/oversize/non-hex groups), wired into isValidHostForCert (accept) and sanEntryForHost (IP: SAN) -- an IPv6 https target now mints a correct iPAddress-SAN leaf instead of falling through to a blind tunnel. VERIFIED: cert_logic_test 68/68 incl. new IPv6/SAN cases + 2 mutations (dropping the IPv6 arm from sanEntryForHost; defeating the group-count check). Gauntlet ctest green per commit message. This run (2026-08-27) corrected the stale doc comments in cert_logic.hpp (isIpv4Literal's doc still described IPv6 as unimplemented; sanEntryForHost's doc didn't mention the IPv6 arm) and backfilled this item's own commit hash -- 983fca1 updated gap/why but left reconciled pointing at 81a0ba2 and audited_state at absent, both now corrected. REMAINDER (-> stays partial): multi-SAN and wildcard-SAN leaves, and the live-handshake path (forged-leaf CONNECT+MITM over a real socket) -- socket-path work outside headless verification."},{"a":"proxy","f":"Settings > Network > TLS > Client TLS certificates (per-host client certs, PKCS#12/JKS, mutual TLS)","s":"absent","i":"high","e":"days","g":"Nullock cannot present a client certificate to the origin. Any mutual-TLS target (banking back-office, gov, internal PKI-gated apps) is completely untestable through the proxy.","w":"Re-grepped clientCert/mutualTls/mTLS/pkcs12/setLocalCertificate across Src myself. The only setLocalCertificate is the server-side forged leaf presented TO the browser; the only mTLS string is a remediation blurb in finding_enricher.cpp. I read the full upstream QSslConfiguration block -- ALPN, verify mode, TLS profile, peerVerifyName, and no local certificate or key. Absent confirmed.","v":"Server-side only: Src/BackEnd/Proxy/proxy_server.cpp:459-460 `cfg.setLocalCertificate(cert); cfg.setPrivateKey(key);` (inside runMitmTunnel, applied to sslClient -- presenting Nullock's forged leaf TO the browser). Upstream config in full at proxy_server.cpp:491-511 -- setAllowedNextProtocols, setPeerVerifyMode, TlsProfile::apply, setPeerVerifyName -- and nothing else; no setLocalCertificate/setPrivateKey call on the upstream QSslConfiguration anywhere.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-grepped clientCert/mutualTls/mTLS/pkcs12/setLocalCertificate across Src: the only setLocalCertificate is still the server-side forged leaf presented to the browser; the only mTLS string is still the unrelated remediation blurb in finding_enricher.cpp. Re-read the full upstream QSslConfiguration block end to end -- still no local certificate/key set for the outbound connection. No change."},{"a":"proxy","f":"Upstream proxy servers (destination-scoped rules, basic/NTLM/digest auth)","s":"absent","i":"high","e":"days","g":"Cannot sit behind a corporate proxy or chain into another tool. On any engagement where egress is proxy-only, Nullock cannot reach anything.","w":"Re-grepped upstreamProxy/parentProxy/proxy chain/chained proxy/setProxy/QNetworkProxy/--upstream/HTTP_PROXY across Src. Zero relevant hits -- QNetworkProxy is never used anywhere, and the only HTTP_PROXY string is the UI's copy-paste helper telling the USER to set their own env var. Both outbound connects are direct. Absent confirmed.","v":"Direct connects only: Src/BackEnd/Proxy/proxy_server.cpp:314 `upstream.connectToHost(req.host, req.port);` and :540 `upstream->connectToHostEncrypted(host, port);`. `grep -rn QNetworkProxy Src`: 0 hits repo-wide. The only HTTP_PROXY string is still ui-v2/app.jsx's copy-paste helper telling the USER to set their own env var, not something Nullock itself reads.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-grepped upstreamProxy/parentProxy/chained proxy/setProxy/QNetworkProxy/--upstream/HTTP_PROXY across Src: same zero relevant hits as the last audit. Both outbound connects (plaintext and MITM-upstream) are still direct QTcpSocket/QSslSocket connects with no proxy-chaining hook. No change."},{"a":"proxy","f":"SOCKS proxy chaining (SOCKS4/5, 'Do DNS lookups over SOCKS proxy')","s":"absent","i":"high","e":"days","g":"No SOCKS at all -- no chaining through an SSH dynamic tunnel, no Tor, no pivot through a compromised host. That is how most internal testing is actually routed.","w":"I ran the grep myself over the whole repo (all extensions, excluding node_modules): `socks` returns ZERO hits. Nothing to upgrade. Absent confirmed.","v":"`grep -rniE 'socks' --include=*.cpp --include=*.hpp --include=*.jsx --include=*.qml --include=*.js --include=*.md .`: no output. Corroborated by the continued absence of QNetworkProxy anywhere in Src (QNetworkProxy::Socks5Proxy would be the Qt route).","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-ran the same repo-wide case-insensitive grep for 'socks': still zero hits. Nothing to upgrade. No change."},{"a":"proxy","f":"Intercept requests based on rules (match type, Matches/Does not match, AND/OR, per-rule enable)","s":"present","i":"blocker","e":"days","g":"None -- an And/Or rule list (match type + Matches/Does-not-match + per-rule enable) decides which requests are held; e.g. 'file extension does not match css,png,js' skips static assets. A RULES panel in the Intercept tab (ui-v2/tabs.jsx InterceptRulesPanel) now edits the list live -- add/edit/reorder/delete/toggle -- reading/writing the newly-added interceptRules snapshot field and POSTing the whole array to /api/intercept/rules, persisted per project.","w":"Confirmed by reading intercept.hpp end to end: the class has two atomics and a queue, no rule structure of any kind, and pend() is gated only by the global toggle plus the caller's inScope check. Endpoint list confirmed as toggle/responses-toggle/forward/drop/forwardAll only. Absent confirmed; blocker rating is right -- this is what makes interception tolerable in daily use.","v":"Src/BackEnd/Proxy/intercept.cpp:189-194 `InterceptResult InterceptController::pend(...) {\\n    // Worker-thread early-out: interception off -> pass the bytes straight\\n    // through ...\\n    if (m_enabled.loadAcquire() == 0) return { false, requestBytes };\\n    return pendImpl(requestBytes, host, port, tls, PendingRequest::Request);` ; entire member list intercept.hpp:136-141 (two QAtomicInt, m_c","o":"present","r":"GUI-reachability follow-up on c88e6bb: the rules engine/API/persistence shipped backend-only (\"Rules-editor UI pending\"). Added interceptRules to buildSnapshot() (control_server.cpp) so the poll loop carries the live rule list like sessionRules/rules already do, and a new InterceptRulesPanel component in ui-v2/tabs.jsx (RULES toggle button in InterceptTab's toolbar) lets an operator add/edit/reorder (up/down)/toggle/delete rules -- op (AND/OR), direction (request/response/both), match type (any/file-extension/method/url-regex/host-glob/content-type/status-code/has-header), negate, and condition -- against the exact InterceptLogic::interceptRulesToJson/FromJson wire contract, POSTing the whole array to /api/intercept/rules (NL.actions.interceptRulesSet) on every mutation, same whole-list-replace pattern as session handling rules. State stays present; this closes the GUI-reachability gap text only."},{"a":"proxy","f":"Intercept responses based on rules (content-type, status code, 'request was intercepted/modified', URL)","s":"partial","i":"high","e":"days","g":"Response rules now decide which responses are held (content-type / status code / URL / host / header, And/Or + negate), editable live from the same Intercept tab RULES panel via the dir=response/both rows. Remaining: the 'only intercept responses to requests I intercepted/modified' cross-reference match, which needs request/response correlation.","w":"Same verification as the request side -- pendResponse is gated only by m_enabledResponses; no rule type exists in intercept.hpp. Absent confirmed. I re-rated user_impact blocker -> high: response interception is opt-in and off by default, so an operator hits this only after deliberately enabling it, unlike the request side which is the primary workflow.","v":"Src/BackEnd/Proxy/intercept.cpp:197-201 `InterceptResult InterceptController::pendResponse(const QByteArray &responseBytes,\\n                                                  const QString &host, int port, bool tls) {\\n    if (m_enabledResponses.loadAcquire() == 0) return { false, responseBytes };\\n    return pendImpl(responseBytes, host, port, tls, PendingRequest::Response);` ; kinds are only Req","o":"partial","r":"Same InterceptRulesPanel wave as the request-side item above -- dir=response and dir=both rows in the same rule list gate response holds via InterceptController::pendResponse's existing interceptRulesHold() call. GUI-reachability gap closed; state stays partial (the request-was-intercepted cross-reference correlation is still unimplemented, unchanged from the prior audit)."},{"a":"proxy","f":"Intercept: 'Do intercept > Response to this request' (per-message opt-in)","s":"present","i":"medium","e":"hours","g":"None for the primary ui-v2 GUI: a per-message FORWARD, HOLD RESPONSE button in the Intercept tab opts just the current held request into response-holding, forwarding it while the RESPONSES toggle can stay off for everything else. The Qt desktop app.qml intercept pane has no equivalent control yet -- a separate, QML-only remainder not addressed here (not buildable/verifiable from this cloud session).","w":"The backend plumbing (forwardInterceptingResponse -> POST /api/intercept/forward-hold-response) was built and e2e-verified in the prior wave (f859d3a) but had zero ui-v2 caller -- the concurrent-agent-lane remainder that wave named explicitly. This wave adds the ui-v2 half: InterceptTab (ui-v2/tabs.jsx) gains a FORWARD, HOLD RESPONSE button next to DROP/FORWARD, shown only for held REQUESTS (current.kind !== 1), dispatching a new intercept-forward-hold-response reducer case (ui-v2/app.jsx) that calls NL.actions.interceptForwardHoldResponse(text) (ui-v2/real-data.js), posting the edited buffer to the existing endpoint and advancing the intercept queue exactly like plain FORWARD.","v":"ui-v2/tabs.jsx InterceptTab: the FORWARD, HOLD RESPONSE button (current.kind !== 1 guard) dispatching {type:\"intercept-forward-hold-response\", text: editedText}; ui-v2/app.jsx reducer case \"intercept-forward-hold-response\" calling act(\"interceptForwardHoldResponse\", ...) and slicing the queue; ui-v2/real-data.js interceptForwardHoldResponse(text) posting to /api/intercept/forward-hold-response (control_server.cpp:3259, body field \"text\" matching the server's bodyJson.value(\"text\") read).","o":"present","r":"GUI-reachability wave: added the per-message FORWARD, HOLD RESPONSE control to ui-v2 InterceptTab, closing the concurrent-agent-lane remainder the f859d3a backend wave named. No backend change -- pure frontend wiring of an already-built, already-verified endpoint. partial -> present for the ui-v2 GUI; the Qt desktop app.qml pane is untouched and still lacks the control (not buildable/verifiable from this cloud session, tracked separately if the desktop UI is ever audited on its own)."},{"a":"proxy","f":"'Automatically update Content-Length header when the request / response is edited' (on by default in Burp)","s":"partial","i":"high","e":"hours","g":"REQUEST side is fully closed (backend recompute + a Burp-default-ON 'Update Content-Length' checkbox in the ui-v2 Intercept tab, both wired to /api/intercept/autocl). RESPONSE side remains absent and is a deliberate, documented deferral: the intercept layer processing response bytes cannot see the paired request method, so it can't tell a legitimate zero-body HEAD/204/304 response apart from a truncated one, and recomputing blindly would corrupt the former -- Burp's own feature covers both directions, so this item stays short of it.","w":"Confirmed: the whole edit resolver is a compare-and-reencode with no header handling, and fixContentLength is called only from applyRequestRules/applyResponseRules, never from the intercept path. Note this is a DELIBERATE, documented choice (the header comment argues an operator must be able to emit a desynced request), not an oversight. I re-rated blocker -> high: the editor is raw text, so the o","v":"Src/BackEnd/Proxy/intercept_logic.cpp:5-18 `QByteArray resolveForwardBytes(const QByteArray &originalBytes, const QString &currentText) {\\n    if (currentText == QString::fromUtf8(originalBytes))\\n        return originalBytes;\\n    ...\\n    return currentText.toUtf8();\\n}` ; rationale at intercept_logic.hpp:33-36 `an EDITED forward whose Content-Length no longer matches the new body\\n// is left as","o":"partial","r":"ui-v2/tabs.jsx's InterceptTab toggle bar gains an UPDATE CONTENT-LENGTH checkbox (next to the existing REQUESTS/RESPONSES power toggles), bound to a new interceptAutoContentLength state slice (app.jsx: initial state, nl-snapshot merge from NL.interceptAutoContentLength, a new intercept-autocl-toggle reducer case) and a new NL.actions.interceptSetAutoContentLength (real-data.js) posting to the already-existing /api/intercept/autocl endpoint (control_server.cpp:3105, added by the 4369973 backend wave but never wired to any GUI control until now). Closes the GUI-reachability half of this item's own remaining ask for the REQUEST side; the response-side gap is unchanged and named honestly above, so state stays partial rather than claimed present. No backend touched."},{"a":"proxy","f":"'Automatically fix missing or superfluous new lines at end of request'","s":"present","i":"low","e":"hours","g":"None -- a hand-edited, bodyless request that dropped or duplicated its terminating blank line is repaired before forwarding, gated behind a Burp-default-ON 'FIX NEW LINES' toggle in the Intercept tab.","w":"Closed: InterceptLogic::fixTrailingNewline (Src/BackEnd/Proxy/intercept_logic.cpp) resolves the header/body boundary the same terminator-agnostic way as recomputeContentLength. Three cases: (1) no blank line anywhere -- the operator deleted the terminator that closes the headers -- append one, matching the message's own terminator style (CRLF/LF); (2) a blank line found with only stray terminator bytes after it and no declared body -- drop the superfluous trailing blank line(s); (3) anything else (a real body, or a body explicitly declared via Content-Length / Transfer-Encoding: chunked) -- left byte-for-byte untouched, so a deliberate desync probe still survives. Wired exactly like the existing 'Update Content-Length' toggle: a new autoFixNewlines Q_PROPERTY on InterceptController (default ON), shouldFixTrailingNewline gates it to edited REQUESTS only (never responses, drops, or a passive unedited forward), applied in pendImpl BEFORE the Content-Length recompute so CL is computed over the corrected framing. Persisted via ProjectStore's interceptAutoFixNewlines (same absent-key-means-ON contract as its CL sibling), surfaced in the boot snapshot, toggled from POST /api/intercept/autonl, and exposed as a 'FIX NEW LINES' checkbox next to 'UPDATE CONTENT-LENGTH' in the ui-v2 Intercept tab.","v":"Src/BackEnd/Proxy/intercept_logic.cpp fixTrailingNewline()/shouldFixTrailingNewline(); Src/BackEnd/Proxy/intercept.{hpp,cpp} autoFixNewlines Q_PROPERTY + pendImpl wiring (before recomputeContentLength); Src/Core/Storage/project_store.{hpp,cpp} interceptAutoFixNewlines persistence; Src/BackEnd/Control/control_server.cpp POST /api/intercept/autonl + boot snapshot field; ui-v2/tabs.jsx InterceptTab 'FIX NEW LINES' checkbox; ui-v2/real-data.js interceptSetAutoFixNewlines; Tests/intercept_logic/intercept_logic_test.cpp -- 13 new assertions (5-case gate + 8 fixTrailingNewline cases: missing blank line CRLF/LF/no-terminator-at-all, already-correct no-op, superfluous-blank-lines trim, real-body/declared-CL/declared-chunked preservation), all passing under a real local g++/Qt6Core build+run (93/93) -- this cloud session installed Qt6Core/Network/Sql headers and compiled+ran the actual test binary rather than relying on CI alone.","o":"present","r":"Intercept 'Fix missing/superfluous new lines' wave: added InterceptLogic::fixTrailingNewline + shouldFixTrailingNewline, wired through InterceptController/ProjectStore/control_server exactly like the existing 'Update Content-Length' toggle, and exposed as a Burp-default-ON checkbox in the ui-v2 Intercept tab. Absent -> present."},{"a":"proxy","f":"Intercept WebSocket messages (hold client-to-server / server-to-client, then edit or drop the frame)","s":"absent","i":"high","e":"days","g":"WebSocket messages are observable and injectable but never holdable. For an app whose protocol is entirely WS (chat, trading, collaborative editing, LLM streaming) you cannot tamper with a live message -- the core reason to proxy it.","w":"Confirmed by reading the relay: both readyRead handlers write the bytes to the peer socket BEFORE the parser is fed, so there is no point at which a frame could be held. InterceptController has only Request/Response kinds. Absent confirmed.","v":"Src/BackEnd/Proxy/proxy_server.cpp:1117-1124 `connect(client, &QTcpSocket::readyRead, this,\\n            [client, upstream, clientParser, ...] {\\n                const QByteArray bytes = client->readAll();\\n                upstream->write(bytes);\\n                for (const WsFrame &f : clientParser->feed(bytes)) {` -- write first, parse second; mirror at :1126-1134. Kinds: intercept.hpp:44 `enum ","o":"","r":"FOUNDATION + vetted design shipped; state stays ABSENT (no operator hold capability yet). A 3-engineer + synthesis design review produced a GO, implementation-ready v1 with a structurally-safe boundary: HOLD only UNCOMPRESSED text/binary MESSAGES (rsv1/2/3=0), pass CONTROL frames (ping/pong/close) + COMPRESSED (rsv1) + rsv2/3 through VERBATIM. That boundary makes permessage-deflate window desync IMPOSSIBLE rather than merely guarded -- an rsv1=0 message never touches the per-direction LZ77 sliding window, so editing/dropping/auto-forwarding it is provably orthogonal to deflate state (editing a context-takeover COMPRESSED message would silently oblige re-deflating EVERY later message, so that is a documented v1.5/v2 remainder behind a per-connection VERIFIED no_context_takeover handshake). Full design: invert the relay from forward-then-observe to PARSE-THEN-GATE, buffer un-forwarded frames in a per-direction FIFO inside the relay's own event loop (no new threads, no blocking), resolve by a process-global holdId via the existing frameQueued-style queued bridge, with disarm-flush + shutdown-flush + a leaky-bucket cap for deadlock/walk-away safety; a SEPARATE WsInterceptController (the HTTP blocking-worker model can't drive the async duplex relay) reusing the intercept toggle-pair + InterceptRule schema; /api/ws/intercept/* + wsIntercepted[] snapshot + project.json persistence; 7-step build order. STEP 1 IS DONE + mutation-proven (this commit): the pure shared serializer wsEncodeFrame(opcode,fin,rsv1,payload,mask) (FIN/RSV1 bits, minimal 7/16/64-bit length form, fresh-CSPRNG client->server masking) + wsHoldEligible predicate, in Src/BackEnd/Proxy/ws_encode.cpp (Qt6::Core-only), with WsRepeater::buildFrame now delegating to it (dedup, byte-equivalent -- injection regression green). ws_encode_test 26/26 + 2 mutations (16-bit length boundary; text/binary eligibility). Gauntlet ctest + probe_smoke green. REMAINDER (why still absent): the relay parse-then-gate inversion (step 2), the per-direction gate state machine (step 3), WsInterceptController + queued bridge (step 4), /api/ws/intercept/* + snapshot + persistence (step 5), the GUI WS tab (step 6), and the real-WS-client e2e (step 7) -- plus compressed-message hold behind the verified no_context_takeover renegotiation."},{"a":"proxy","f":"Intercept: Action menu (send held message to Repeater / Intruder / Comparer / Decoder / Scanner)","s":"present","i":"low","e":"hours","g":"None -- all five pivots named in the original gap are wired: Repeater/Intruder/Comparer (send-to-repeater-raw/send-to-intruder-raw/comparer-add), Decoder (send-to-decoder, a prior wave that never flipped this item), and Scanner (a new SCAN button on a held request parses the raw request line for its target -- Intercept carries no captured `url` field, only host/port/tls/text -- and POSTs the reconstructed url/method/headers/body to the existing /api/audit/run, the same active-test battery the SCANS tab's Assess & audit section drives; findings file into Issues as usual, and an inline result strip reports the finding/tester counts or the error).","w":"This wave added the Scanner pivot: sendToScanner() in InterceptTab reuses proxy.jsx's parseRawRequest() -- extended with a fallback so it can derive the request-line target when no captured row.url is available (previously every caller had one) -- to turn the held request text into {method, fullUrl, headers, body}, then calls NL.actions.auditRun(url, opts) (already used by the SCANS tab's Audit form, unmodified). Also discovered while implementing this that Send to Decoder had already shipped in an earlier wave (df50bbc, 2026-08-12) but this item was never flipped -- the register was stale by two of its five gaps, not just one.","v":"ui-v2/tabs.jsx InterceptTab: sendToScanner()/SCAN button (kind!==1 only) + scanRes result strip; ui-v2/proxy.jsx parseRawRequest() row.url fallback; ui-v2/real-data.js NL.actions.auditRun (unchanged, already wired to POST /api/audit/run); control_server.cpp:6760-6797 /api/audit/run handler (url/method/body/headers/include request shape, {ok,target,totalFindings,testers} response shape) matches every field read/sent.","o":"present","r":"Intercept Scan pivot batch: added Send to Scanner (parses the held request's raw request-line target via a parseRawRequest fallback, POSTs to /api/audit/run), and corrected the register for Send to Decoder (already shipped, never flipped) -- all five action-menu destinations now present."},{"a":"proxy","f":"WebSocket match and replace rules","s":"absent","i":"low","e":"days","g":"No automated rewriting of WebSocket traffic at all.","w":"Confirmed: MatchReplaceRule::Section has no WS member, and I traced every applyRequestRules/applyResponseRules call site -- all are on HTTP paths. The WS relay writes frame bytes through untouched. Absent confirmed.","v":"Sections enumerated at Src/BackEnd/Proxy/proxy_server.hpp:80-87 (ReqUrl/ReqHeader/ReqBody/RespHeader/RespBody/RespStatus) -- no WS member. Relay passthrough at proxy_server.cpp:1233 and :1242 `const QByteArray bytes = client->readAll(); ... upstream->write(bytes);` (and the reverse direction) -- raw frame bytes forwarded untouched. Rule call sites: proxy_server.cpp:311, 343, 624, 656, 701, 735, 785, 813 -- every one on an HTTP request/response path, none inside runWebSocketRelay.","o":"","r":"Wave 0 register-accuracy audit: held at absent. MatchReplaceRule::Section still has no WS variant; traced every applyRequestRules/applyResponseRules call site again (8 call sites, up from the last audit's list due to the H2 tunnel legs, all still HTTP paths) and runWebSocketRelay still just shuttles readAll()/write() bytes in both directions with no rule application. No change."},{"a":"proxy","f":"Response modification options (unhide hidden fields, enable disabled fields, remove length limits, remove JS validation, remove all JS, remove <object>, HTTPS->HTTP links, strip Secure flag)","s":"present","i":"low","e":"days","g":"None. All eight of Burp's one-click removals are reachable per held response, and a standing auto-apply toggle set (persisted to localStorage) now applies the enabled ones automatically to every future held response the instant it is captured -- matching Burp's Options-tab checkboxes, not just a manual per-message action.","w":"Added a RESP_MODS table + applyEnabledRespMods (ui-v2/tabs.jsx) driving a persisted settings row (\"response mods . auto-apply on hold:\") rendered unconditionally in InterceptTab, independent of whether a message is currently held. The held-item reset effect now runs applyEnabledRespMods against the settings captured at hold-time (via a ref, so toggling settings mid-edit of an already-held item does not clobber the user's in-progress edit) before the response text is shown for review, so every future held response gets the enabled transforms baked in without a click. The 8 manual per-message buttons stay for a one-off tweak of the currently-held item. No backend touched. present, not exceeds: this remains a client-side edit-before-forward, not a body-rewrite engine.","v":"ui-v2/tabs.jsx:856-905 (8 resp* helper functions, RESP_MODS table at :887, applyEnabledRespMods at :897, loadRespModSettings/saveRespModSettings persisting to localStorage key nl-intercept-respmods), the unconditional \"response mods . auto-apply on hold:\" checkbox row rendered under the icp-toggle bar, and the current.id-keyed reset effect that runs applyEnabledRespMods(current.text, respModSettingsRef.current) for kind===1 (response) matching control_server.cpp:1461-1476's kind field (0=request,1=response).","o":"present","r":"Intercept response-mods wave: RESP_MODS/applyEnabledRespMods + a persisted auto-apply toggle row closes the standing-setting gap (partial -> present)."},{"a":"proxy","f":"HTTP history annotations: per-item highlight colours and comments, plus filter-by-annotation","s":"present","i":"medium","e":"days","g":"None for this history/Site map workflow. Other message tables and global report formats remain outside this item; see the platform annotation item.","w":"Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action.","v":"Src/Core/Storage/project_store.cpp (historyAnnotations, annotateHistory, HAR import/export); Src/BackEnd/Control/control_server.cpp (/api/history/annotations, /api/history/annotation); ui-v2/real-data.js and proxy.jsx; bin/nullock; scripts/annotations_regression.py; Tests/ui/annotations_data_test.cjs and annotations_browser_test.cjs.","o":"partial","r":"Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action."},{"a":"proxy","f":"Proxying plaintext ws:// WebSocket connections","s":"present","i":"medium","e":"hours","g":"A ws:// handshake over plain HTTP is answered with a re-framed 101 and the socket is then closed. Plaintext WebSocket traffic is not relayed, not logged and not repeatable -- broken, not merely unsupported.","w":"Confirmed by tracing the plaintext leg end to end. The 101 branch exists only inside the MITM keep-alive loop. On the cleartext path a 101 is read (readResponse special-cases it and hands back the post-header bytes as the body), then passed to resolveResponseForClient -> serializeResponse, which strips Transfer-Encoding and appends a Content-Length -- and then the socket is closed. The handshake i","v":"Only 101 handler: Src/BackEnd/Proxy/proxy_server.cpp:719-727 `if (resp.statusCode == 101) {\\n                sslClient->write(serializeUpgradeResponse(resp));` (inside runMitmTunnel). Plaintext path: readResponse's 101 early-return at proxy_server.cpp:833-836, then run() at :310-315 goes through `serializeResponse` (which at :890-895 skips Transfer-Encoding and adds `Content-Length`) and ends with","o":"absent","r":"CLOSED. The plain-HTTP response path now mirrors the MITM path's 101 handling: on a 101 Switching Protocols carrying Upgrade: websocket it writes serializeUpgradeResponse(resp) -- which already appends the buffered post-101 frame tail (so a server-that-sends-first frame is not dropped) -- and hands the socket pair to runWebSocketRelay instead of the normal serializeResponse -> close path. runWebSocketRelay is transport-agnostic (plain QTcpSocket*), and it registers the session with WsRepeater + notes every frame exactly as the wss:// path does, so plaintext ws:// is now RELAYED, LOGGED (WebSocket history) and REPEATABLE -- all three things the audit found broken. A non-websocket 101 still takes the normal response path. VERIFIED e2e with a raw WS echo server + a raw client connecting THROUGH the proxy (real RFC 6455 handshake): the proxy relays the 101, Sec-WebSocket-Accept passes through intact, and a masked text frame round-trips via the echo (3/3). Gauntlet ctest 99/99 + probe 156. This reaches PARITY with the (present) wss:// path through the same relay; note WS-message INTERCEPTION (hold/edit/drop) is a separate roadmap item still in progress for both transports."},{"a":"repeater","f":"Repeater: multiple concurrent request tabs","s":"partial","i":"medium","e":"days","g":"The GUI/control Repeater runs one request at a time on a worker, preserving UI responsiveness and edits made during a send. Busy/Stop states are exposed; Stop prevents subsequent redirects after the current response. Browser mutations are serialized and stale polls cannot overwrite pending edits. Tabs autosave per project. Independent concurrent sends across multiple tabs remain unavailable.","w":"The GUI/control Repeater runs one request at a time on a worker, preserving UI responsiveness and edits made during a send. Busy/Stop states are exposed; Stop prevents subsequent redirects after the current response. Browser mutations are serialized and stale polls cannot overwrite pending edits. Tabs autosave per project. Independent concurrent sends across multiple tabs remain unavailable.","v":"Src/Core/Networking/repeater.cpp sendAsync; ui-v2/real-data.js writeRepeater; scripts/control_responsiveness_regression.py; Tests/ui/repeater_data_test.cjs","o":"","r":"The GUI/control Repeater runs one request at a time on a worker, preserving UI responsiveness and edits made during a send. Busy/Stop states are exposed; Stop prevents subsequent redirects after the current response. Browser mutations are serialized and stale polls cannot overwrite pending edits. Tabs autosave per project. Independent concurrent sends across multiple tabs remain unavailable."},{"a":"repeater","f":"Repeater: tab renaming (double-click) and auto-naming","s":"present","i":"cosmetic","e":"hours","g":"Rename is now inline (double-click the tab, edit in place, Enter/blur to commit, Escape to cancel) instead of a prompt() dialog, and each tab gets a click-to-cycle colour dot from a fixed 6-colour palette. The colour label is client-only cosmetic state (no `color` field exists in the repeater-tab wire contract, which is index-addressed with no stable id) -- it does not persist across a page reload or travel with project save/load, unlike name/notes. Auto-naming from the request line still applies only on addTabFromHistory/loadFromHistory, unchanged by this batch -- a plain addTab still gets 'tab N'.","w":"Closed 2026-08-09 (attack-type wiring, unrelated) then hardened 2026-08-18: RepeaterTab's onDoubleClick now opens an inline <input> (renameIdx/renameVal state, commit on blur/Enter, cancel on Escape) instead of prompt(), and a small colour dot next to each tab name cycles through TAB_COLOR_PALETTE on click (tabColors state, index-keyed).","v":"ui-v2/tabs.jsx TAB_COLOR_PALETTE + RepeaterTab's startRename/commitRename/onRenameKeyDown/cycleTabColor (tab strip render, double-click -> inline <input>; dot span -> cycleTabColor); repeaterTabRename POST still the only backend call, unchanged (control_server.cpp's /api/repeater/tab/rename).","o":"present","r":"Repeater-area polish batch: inline tab rename (was prompt()) + client-only colour labels, closing the two named gaps; auto-naming quirk left untouched, honestly."},{"a":"repeater","f":"Repeater: send a captured message to Repeater from other tools","s":"partial","i":"high","e":"days","g":"History loading preserves full request bytes, including binary bodies and bodies beyond the former preview limit. Browser and CLI use stable history IDs. Dedicated pivots from every tool, including Intruder result rows and Comparer, are not implemented.","w":"The history-ID endpoint reads the actual request from memory or the history index and serializes it without preview truncation. The CLI now calls that endpoint and rejects missing or invalid IDs. Browser history, the shared site-map detail pane and Intercept expose Repeater entry points. File and stdin loading now send base64 to the same reversible byte mapping, preserving NULs, invalid UTF-8 and trailing newlines.","v":"Src/BackEnd/Control/control_server.cpp /api/repeater/tab/addFromHistoryId; Src/Core/Networking/repeater.cpp setRequestBytes/addTabFromHistoryById; ui-v2/app.jsx send-to-repeater and send-to-repeater-raw; bin/nullock cmd_repeater; scripts/repeater_cli_runtime.py; scripts/runtime_regression.py binary history checks. /api/repeater/set requestBase64; CLI file/stdin runtime tests with 76,804-byte bodies.","o":"","r":"CLI file and stdin input preserve raw body bytes. Empty input clears the draft, omitted input preserves it, and invalid base64 is rejected before mutation. Existing missing tool pivots keep the grade partial."},{"a":"repeater","f":"Repeater: Host header and target stay in sync when you edit either","s":"present","i":"high","e":"hours","g":"None for the load-bearing direction. Changing the target now rewrites the request's Host header to match; a deliberate Host desync (host-header-injection testing) is preserved. Editing the raw Host header is intentionally NOT propagated back to the connection target (doing so would break injection testing).","w":"Closed 2026-08-10 (fef9cc4): Repeater::setHost calls NetworkingLogic::rewriteHostHeader so the Host line follows the target unless the user aimed it elsewhere. Mutation-proven pure test lock; full gauntlet green.","v":"Src/Core/Networking/networking_logic.cpp rewriteHostHeader (match-guarded, :port + LF/CRLF preserving); repeater.cpp setHost wires it + emits requestTextChanged; Tests/networking/networking_logic_test.cpp 8 cases, inverted-guard mutant fails exactly the 5 discriminating ones.","o":"partial","r":"Target host change now syncs the request Host header (desync-preserving)."},{"a":"repeater","f":"Repeater: response metadata display (status, byte length, elapsed milliseconds)","s":"present","i":"high","e":"hours","g":"None. STATUS, byte length and elapsed ms all render in the Repeater toolbar (tabs.jsx), sourced from the same snapshot fields the backend has served since 8bb4d7d; the history-nav tooltip carries the same two fields per navigated entry.","w":"Confirmed, and I found the capability already exists one file over — the proxy detail pane renders both size and elapsed — which makes this pure wiring rather than a build-out.","v":"ui-v2/tabs.jsx RepeaterTab toolbar: a `{fmtSize(rep.responseBytes)} · {fmtMs(rep.elapsedMs)}` span next to STATUS, gated on `typeof rep.elapsedMs === \"number\" && rep.elapsedMs > -1` so the pre-send sentinel (-1) renders nothing instead of \"-1 ms\"; the history-nav title string appends the same pair per `histEntries[histPos]`. Backend fields unchanged since 8bb4d7d/control_server.cpp:1551-1552,1566-1567,1576-1577.","o":"partial","r":"UI HALF of #305, closing the remainder left open by 8bb4d7d/1ecbc7b (concurrent backend lane): RepeaterTab's toolbar (ui-v2/tabs.jsx) now renders response byte length + elapsed ms next to STATUS via the existing proxy.jsx fmtSize/fmtMs helpers (shared global scope, proxy.jsx loads before tabs.jsx in Nullock.html), reading rep.elapsedMs/rep.responseBytes straight off the snapshot (NL.repeater = snap.repeater verbatim in real-data.js, no field allowlist to update). Gated on `elapsedMs > -1` so the -1 pre-send sentinel shows nothing rather than a bogus \"-1 ms\"/\"-0.0 KB\" (fmtSize/fmtMs were never designed for negative input). The history-nav arrows' hover tooltip gained the same two fields per entry (histEntries[histPos].elapsedMs/.responseBytes), which the wire contract already carried per-history-entry (control_server.cpp:1576-1577) but the UI never read. Verified: bundled-babel transform of all six ui-v2 script files (real-data.js is plain JS, not JSX, so untransformed) all succeed; tabs.jsx's intentional single NUL byte confirmed still present and exactly 1 occurrence (offset shifted from 58081 to 80301 purely from upstream file growth since that check was last recorded, not from this diff); a Node functional test of the show/hide gate and formatter across 4 cases (before-any-send sentinel, the older snapshot-fallback object with undefined fields, a normal 615ms/1234B send, and a degenerate 0ms/0B send) all matched expectation. No backend touched. python3 scripts/parity_report.py --check green after regenerating the page."},{"a":"repeater","f":"Repeater: \"Copy as curl command\" / copy request to other tooling","s":"exceeds","i":"medium","e":"hours","g":"None. Nine exporters (curl/wget/httpie/powershell/fetch/sqlmap/postman/nuclei/burp-raw), each with sensitive-header redaction, now reachable from BOTH proxy history and the Repeater toolbar -- vs Burp's single 'Copy as curl'.","w":"Closed 2026-08-02: the exporters existed but were reachable only from a proxy-history row. Wired the same shared renderRequestAs into the Repeater toolbar (clipboard, token-redacted). Exceeds Burp on format count and on redaction, which Burp does not do.","v":"ui-v2/tabs.jsx RepeaterTab COPY AS dropdown -> global renderRequestAs(row, rep.request); verified under bundled @babel/standalone 7.29.0 + a functional test confirming URL assembly, POST derivation, and Authorization/Cookie redaction.","o":"partial","r":"COPY AS wired into Repeater with all 9 redacting exporters; functional + real-babel verified."},{"a":"repeater","f":"Repeater: out-of-scope send guard","s":"exceeds","i":"low","e":"hours","g":"The guard protects the browser UI and the CLI (the paths that matter) but not the Qt desktop Send button, which invokes Repeater::send() directly. There is also a narrow TOCTOU: the check reads the ACTIVE tab's host, then the send is posted with Qt::QueuedConnection, so a scripted client can activate a different tab between the two.","w":"The guard is real and refuses the send (Burp Repeater has no scope enforcement at all), so 'exceeds' holds. But I found a bypass the auditor missed: the check lives in the HTTP handler, not in Repeater::send(), and the Qt desktop Send button calls the Q_INVOKABLE directly.","v":"Src/BackEnd/Control/control_server.cpp:3557-3558 `if (path == \"/api/repeater/send\") {\\n        if (m_wiring.repeater && blocksScope(m_wiring.repeater->host()))`. `blocksScope` at control_server.cpp:1263-1265 `return m_wiring.proxy && !host.isEmpty() && !m_wiring.proxy->isInScope(host);` -- out-of-scope wins via ProxyServer::isInScope. Confirmed the bypass still holds: Src/Core/Networking/repeater.cpp:135 `Repeater::send()` has no scope check at all -- only the HTTP control-server path (used by the browser UI and CLI) enforces it; the Qt desktop Send button calling the Q_INVOKABLE directly would skip it.","o":"","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Repeater: headless / scriptable driving of the tool","s":"present","i":"low","e":"hours","g":"The CLI requires Bash, curl and jq, plus base64 for file/stdin loading; a native Windows CLI remains unimplemented. Send waits for a bounded period and reports unfinished requests explicitly. Stop completes after the current response rather than aborting the socket.","w":"History loads use stable IDs, asynchronous sends survive multiple busy polls, and binary file/stdin bodies retain their bytes. Tab summaries read an explicit per-tab response flag; fresh or duplicated tabs no longer claim a response. Duplicating a request clears its response metadata.","v":"bin/nullock cmd_repeater; Src/BackEnd/Control/control_server.cpp snapshot hasResponse and requestBase64; Src/Core/Networking/repeater.cpp duplicateTab; scripts/repeater_cli_test.py and scripts/repeater_cli_runtime.py.","o":"exceeds","r":"Verified the CLI through owned API fixtures and a real app: history IDs, asynchronous sends, Stop, binary file/stdin input and tab response state. Replaced stale defect descriptions and removed an unverified exceeds comparison."},{"a":"repeater","f":"Repeater: WebSocket message repeater tab (reissue and edit a captured WebSocket message)","s":"partial","i":"medium","e":"days","g":"A captured message can now be reissued for the common case: DetailPane's new ↦ WS REPEATER button (ui-v2/proxy.jsx, only on a WS↑/WS↓ history row) opens the existing WsRepeaterOverlay pre-filled with the row's direction and payload, and pre-selects any still-open live session on that same host:port. Still short of the item's full title: it is a global modal reused from #270, not a dedicated 'ws' tab or docked pane, and only TEXT-opcode frames are reissuable -- ProxyModel::responseRawAt (proxy_model.cpp renderBody/looksTextual) renders a binary/close/ping/pong frame's body as a \"[binary N bytes, ...]\" placeholder, not its real bytes, so the button stays disabled (with an explanatory title) on those rows rather than reissuing garbage.","w":"Closed the reissue-link half of this register's own gap text (\"What is missing is the edit-and-reissue link between that list and the (working) injector\") -- confirmed live that no such link existed (grep for onSendWsRepeater/wsInitFromRow/WS_LABEL_TO_OPCODE in ui-v2 predated this change: no hits) before building it. The binary-frame limitation is a real backend gap (the display endpoint elides non-textual bytes), not a shortcut taken here, and is surfaced honestly rather than silently reissuing a placeholder string.","v":"ui-v2/proxy.jsx DetailPane: isWsFrame/isWsTextFrame/wsInitFromRow (row.method \"WS↑\"/\"WS↓\", label parsed from row.path, body split on the raw response's \"\\n\\n\" separator -- proxy_model.cpp responseRawAt joins headers with bare \\n, not \\r\\n); WS_LABEL_TO_OPCODE top-level const; WsRepeaterOverlay now takes an `initial` prop seeding direction/opcode/payload useState and preferring a session matching initial.host/port in its `refresh` session-list callback. Reused endpoints unchanged: POST /api/ws/send, GET /api/ws/sessions (control_server.cpp, already wired by #270).","o":"","r":"Wave 2 Repeater/WS batch -- WS message repeater tab reissue-link closed for text frames (binary/control frames stay honestly out of reach), partial -> partial (gap narrowed, not a state-count move)."},{"a":"repeater","f":"Comparer: word-level comparison","s":"present","i":"low","e":"hours","g":"","w":"Verified verbatim including the tokenizer contract and the UI path.","v":"Src/Core/Networking/compare.cpp:171-176 `diff()` default branch `return lcsDiff(tokenizeWords(a), tokenizeWords(b)); // default: words`; tokenizeWords at :18-43 (each token = a word plus its trailing whitespace, or a leading-whitespace run on its own, so joining all tokens reproduces the input); token-interned LCS core at :107-127 (QHash<QString,int> ids assigns integer ids so DP cells compare in O(1)). modes() :166-169 lists \"words\" first / used as default.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers/paths that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Comparer: byte-level comparison","s":"present","i":"medium","e":"days","g":"Exact byte diff implemented: Compare::diffBytes() diffs two raw byte buffers (one 2-hex-char token per octet through the same LCS core), and /api/compare gains a binary-safe path -- mode \"bytes\" with base64 inputs (aBase64/bBase64) is decoded to raw octets before diffing, so non-UTF-8 / binary content (session tokens, serialized objects, images) survives JSON transport and compares exactly instead of being folded through QString. \"bytes\" is also listed in modes().","w":"Implemented + mutation-proven. Adds tokenizeBytes()/diffBytes() to compare.cpp and a base64 branch to the /api/compare handler; the byte tokens run through the existing budgeted LCS, inheriting its cell cap and truncation semantics. Tests/compare/compare_test.cpp (45 pass) covers identical binary buffers, a single-byte change, side rebuilds, and the key case that 0x80 vs 0x81 (both invalid UTF-8 starts) still differ rather than folding to U+FFFD; M1 (drop the low hex nibble) and M2 (swap the diff sides) each fail only their targeted cases.","v":"Src/Core/Networking/compare.cpp:76-88 `tokenizeBytes(const QByteArray &b)` (one 2-hex-char token per octet through the shared LCS core) and :179-181 `DiffResult diffBytes(const QByteArray &a, const QByteArray &b) { return lcsDiff(tokenizeBytes(a), tokenizeBytes(b)); }`; \"bytes\" listed in modes() :166-169. control_server.cpp:10452-10465 POST /api/compare: when mode == \"bytes\" and the body carries aBase64/bBase64, decodes to raw QByteArray and calls `Nullock::Core::Compare::diffBytes(a, b)` -- binary-safe, bypassing QString entirely. Tests/compare/compare_test.cpp covers identical binary buffers, a single-byte change, side rebuilds, and 0x80 vs 0x81 (both invalid UTF-8 starts) still differing rather than folding to U+FFFD.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers/paths that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Comparer: line-level comparison","s":"exceeds","i":"low","e":"hours","g":"","w":"Verified; Burp's Comparer offers Words and Bytes only, so a line mode is genuinely extra.","v":"Src/Core/Networking/compare.cpp:45-53 `QStringList tokenizeLines(const QString &s) { ... if (s[i] == QLatin1Char('\\n')) { out << s.mid(start, i - start + 1); start = i + 1; } ... }`, selected at :173 `if (m == QLatin1String(\"lines\")) return lcsDiff(tokenizeLines(a), tokenizeLines(b));`, advertised in modes() :166-169, surfaced at ui-v2/app.jsx:3385 `<Btn label=\"lines\" primary={mode === \"lines\"} onClick={() => setMode(\"lines\")} />`.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers/paths that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Comparer: colour-coded diff (added / deleted / unchanged)","s":"present","i":"low","e":"hours","g":"A greedy left-to-right scan (comparerMarkModified()) now pairs an adjacent del+ins (or ins+del) run into a distinct amber 'modified' style instead of showing them as an unrelated delete next to an unrelated insert -- matches Burp's visual treatment for straightforward in-place value changes. It is a positional heuristic, not an LCS-based rename/move detector: a modified run separated from its counterpart by an intervening common/other-op segment is not paired, and a run of multiple consecutive dels followed by multiple consecutive ins only pairs adjacent members one-to-one (extra dels/ins at either end stay plain delete/insert).","w":"Closed 2026-08-18: comparerMarkModified() (ui-v2/app.jsx, pure function) post-processes the backend's merged diff segment array before the existing streamA/streamB split, flagging paired del+ins segments `modified: true`; segStyle() renders those with a distinct amber background/colour instead of the plain red/green del/ins styling.","v":"ui-v2/app.jsx comparerMarkModified() + segStyle(op, modified) + ComparerTab's `const segs = comparerMarkModified(...)`; /api/compare's segment contract ({op,text}) unchanged, no backend touched.","o":"present","r":"Repeater-area polish batch: adjacent del+ins runs in the Comparer diff now render as a distinct 'modified' colour instead of separate delete/insert, closing the named gap."},{"a":"repeater","f":"Comparer: handles large messages","s":"partial","i":"high","e":"days","g":"2000 tokens is ~10-15 KB of words, and only 2000 CHARACTERS in chars mode — most real HTML responses truncate immediately. The cap exists because Compare::diff runs synchronously on the control/GUI thread; the fix is to move it off-thread, not to raise the number.","w":"Verified, including the honest truncation handling. The cap is real and small.","v":"D:/dev/Nullock/Src/Core/Networking/compare.cpp:14 `constexpr int kMaxTokens = 2000;` with the rationale at :11-13 `// The control handler runs on the GUI thread, so bound the LCS table`. Clipping at :74-75 `if (a.size() > kMaxTokens) { a = a.mid(0, kMaxTokens); res.truncated = true; }`. Honesty guard at :122-125 `// A TRUNCATED diff compared only the clipped prefix, so it must NEVER assert identit","o":"","r":"PROGRESS (stays partial). The flat 2000-token/side cap is replaced by an adaptive AREA budget (pure, mutation-proven Compare::budgetedSizes; kMaxCells = 16M = the same ~64 MB / ~100 ms the old 2000x2000 table cost). A side that already fits is kept WHOLE and only an oversized side is clipped, so the common short-vs-long case -- a one-line injected value vs a 30 KB response -- now diffs the long side in FULL instead of clipping it to 2000; two moderately large messages compare at up to ~4000 tokens each (2x the old linear ceiling). The tokeniser's per-side stop rose 2000 -> 20000. The proven O(n*m) LCS + exact backtrack are UNCHANGED (identical output for existing inputs; compare_test green). Verified: compare_test 38/38 incl. new budget cases + 2 mutations (preserve-short-side; both-large sqrt-of-budget); an asymmetric short-vs-3000-token compare is now NOT truncated and diffs all 3000. Gauntlet ctest 98/98 + probe 156. REMAINDER (why still partial, matching the gap's own point): a truly huge SYMMETRIC compare still clips at ~4000/side because the diff runs synchronously on the request thread -- lifting that ceiling needs it moved OFF-thread plus a linear-space LCS (Hirschberg) to raise the memory bound. This narrows the gap for the asymmetric + moderately-large cases without that larger refactor."},{"a":"repeater","f":"Comparer: compare two proxy-history items directly","s":"exceeds","i":"low","e":"days","g":"Still a divergent diff engine (client-side diffLines) from the backend Comparer's C++ engine, with different tokenization — two engines to maintain, a low-value cosmetic gap. The prior audit's other two claims are now stale: the id-as-index bug is gone (proxy.jsx reads NL.requestRawById/responseRawById, not an index), and the unbounded n*m Int32Array table is now capped at DIFF_MAX_LINES=2000 lines per side (mirroring the backend's compare.cpp kMaxTokens), surfaced via a TRUNCATED badge in the overlay header when either side is clipped.","w":"The mark-then-diff flow is real and is a genuine workflow win over Burp's two Send-to-Comparer trips, so exceeds stands. Re-verified against live source: the id-as-index bug the prior audit found was already fixed in an earlier wave (this item's own evidence field still quoted the dead NL.requestRawAt(idA - 1) code); the unbounded-diff hang/OOM risk was real and unfixed until this pass, which added the same line cap the backend Comparer already enforces.","v":"ui-v2/proxy.jsx MARK/DIFF buttons: `<button onClick={() => setDiffMark(row.id)}> ⊟ MARK` / `<button onClick={() => setDiffOpen({ idA: diffMark, idB: row.id })}> ⊟ DIFF vs #...`. Overlay at proxy.jsx:1623 `function DiffOverlay({ idA, idB, onClose, onClearMark })` reads proxy.jsx:1634-1637 `NL.requestRawById(idA)`/`NL.responseRawById(idA)` (not an index). diffLines (proxy.jsx:1588-1615) now clips each side to `DIFF_MAX_LINES = 2000` lines (mirroring Src/Core/Networking/compare.cpp:14 `kMaxTokens = 2000`) and sets `rows.truncated`, rendered as a TRUNCATED badge in the overlay header (proxy.jsx:1712-1718) when either side was clipped.","o":"exceeds","r":"Backlog #315: capped diffLines at DIFF_MAX_LINES=2000 lines/side (was unbounded n*m, could hang/OOM on a large response) + added a TRUNCATED badge; corrected the gap/evidence text's stale id-as-index claim (already fixed in an earlier wave). State stays exceeds — the mark-then-diff workflow win is unchanged — but the gap text is now accurate and the real remaining defect (uncapped diff) is fixed."},{"a":"repeater","f":"Decoder: URL encode / decode","s":"present","i":"low","e":"hours","g":"One variant only. Burp also offers 'URL encode all characters' / key-character-only modes; Qt's default toPercentEncoding leaves the unreserved set alone, so filter-bypass work that needs full encoding has to be done by hand.","w":"Verified verbatim and reachable from the Decoder tab's OPS list.","v":"Src/Core/Networking/transcode.cpp:30-32 `Result urlEncode(const QString &in) { return ok(QString::fromLatin1(in.toUtf8().toPercentEncoding())); }`; :33-35 `urlDecode` via `QByteArray::fromPercentEncoding`. Registered in operations() :279; dispatched :298-299. UI list ui-v2/app.jsx:5752-5754 DecoderTab OPS includes \"url-encode\"/\"url-decode\".","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: HTML encode / decode","s":"present","i":"low","e":"hours","g":"Named-entity table covers only lt/gt/quot/apos/amp; &nbsp;, &copy; and the rest pass through untouched. Burp resolves the full HTML entity set. Note the PROXY pane's html-decode is a different implementation (browser textarea.innerHTML) with the full set — the two disagree (see A23).","w":"Verified. The single-pass decoder is careful and correct; the entity table really is five entries.","v":"Src/Core/Networking/transcode.cpp:51-91 htmlDecode: single left-to-right pass (comment :52-56), numeric &#dd;/&#xhh; at :67-79, named-entity table at :80-88 covering only lt/gt/quot/apos/amp (5 entries -- &nbsp;/&copy;/etc pass through untouched). Registered in operations() :281; dispatched :300-301. UI list ui-v2/app.jsx:5752-5754 DecoderTab OPS.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: Base64 encode / decode","s":"exceeds","i":"low","e":"hours","g":"","w":"Verified. Strict decode + four registered ops including base64url as first-class operations, which Burp does not offer separately.","v":"Src/Core/Networking/transcode.cpp:21-23 `Result base64Decode(const QString &in, bool url) { const auto opt = (url ? QByteArray::Base64UrlEncoding : QByteArray::Base64Encoding) | QByteArray::AbortOnBase64DecodingErrors; ...` -- strict decode plus four registered ops including base64url as a first-class operation (transcode.cpp:295-297), which Burp does not offer separately.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: ASCII hex encode / decode","s":"present","i":"low","e":"hours","g":"None remaining for the decode itself: hexDecode now returns the exact octets via okBytes() and /api/transcode exposes them as outputBase64, so hex-decoding a binary blob is byte-lossless (the U+FFFD-folding is gone). The `output` text field is still a best-effort UTF-8 view by design; a Hex view reads outputBase64.","w":"The QString::fromUtf8 lossy-decode gap is fixed (base64/hex/octal/binary decoders return okBytes(raw); endpoint emits outputBase64). Present as before, now without the binary-loss caveat.","v":"Src/Core/Networking/transcode.cpp:95-97 hexEncode `return ok(QString::fromLatin1(in.toUtf8().toHex()));`; :98-107 hexDecode (strip whitespace, require even length + hex-only via QRegularExpression, then `return ok(QString::fromUtf8(QByteArray::fromHex(s.toLatin1())));` -- the fromUtf8 collapses non-UTF-8 bytes to U+FFFD). Registered in operations() :281; dispatched in apply() :302-303. UI list ui-v2/app.jsx:5755 OPS includes \"hex-encode\"/\"hex-decode\".","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers/paths that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: Hash operations (MD2, MD4, MD5, SHA, SHA-224, SHA-256, SHA-384, SHA-512)","s":"present","i":"low","e":"hours","g":"Comprehensive hash set: MD4, MD5, SHA-1, SHA-224/256/384/512, SHA3-256. MD2 is intentionally omitted -- Qt/OpenSSL do not expose it and it is a broken, deprecated hash.","w":"Closed 2026-08-10 (eb944ee): added md4/sha224/sha384/sha3-256 to transcode; MD2 unavailable in Qt (documented).","v":"transcode.cpp apply() hash dispatch + ops(); Tests/transcode known-vector assertions (md4/sha224/sha384/sha3-256).","o":"partial","r":"Hash set extended (all but MD2, which Qt cannot provide)."},{"a":"repeater","f":"Decoder: \"Smart decode\" heuristic auto-detection","s":"exceeds","i":"low","e":"hours","g":"","w":"Verified end to end: the loop, the no-progress guard, the chain return, the API passing chain through, and the UI rendering it.","v":"Src/Core/Networking/transcode.cpp:323-345 `Result smartDecode(const QString &input, QStringList *chain) { ... for (int iter = 0; iter < 12; ++iter) { ... jwt -> url -> html -> base64 -> hex ... const Result r = apply(op, cur); if (!r.ok || r.output == cur) break; // failed or made no progress; steps << op; ... }`, terminal break on jwt-decode :338, no-progress guard :335, chain returned via out-param and surfaced by the caller. Base64 detector guard :248-265 `looksLikeBase64()` requires >=80% printable decoded bytes so a pure-hex string falls through to hex-decode instead of a false-positive base64 hit. UI: ui-v2/app.jsx:5885 `<Btn label=\"✦ smart decode\" primary onClick={() => run(\"smart\")} ...`.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers/paths that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: stacked block chaining (each transform creates a new block feeding the next, with per-block Decode-as / Encode-as / Hash)","s":"partial","i":"medium","e":"days","g":"Pressing '↑ input' discards the prior stage and clears the recorded smart-decode chain, so you cannot revise stage 2 and watch 3-5 recompute the way Burp's vertical block stack does. Smart decode records its chain but only as a label.","w":"Verified; the state really is one input + one output and the chain button is destructive.","v":"ui-v2/app.jsx DecoderTab (function at :6171); the single chaining affordance `const useOutputAsInput = () => { setInput(output); setOutput(\"\"); setOutputB64(\"\"); setChain([]); setErr(\"\"); };` (:6248) bound to the '↑ input' button (:6326) -- resets rather than stacks (line drift from the prior 1536-1541 citation, content unchanged).","o":"","r":"Wave 0 register-accuracy audit: held at partial. useOutputAsInput (ui-v2/app.jsx:6248) still does `setInput(output); setOutput(\"\"); setOutputB64(\"\"); setChain([]); setErr(\"\");` -- pressing the chain button still discards the prior stage's output/error state and clears the recorded chain rather than pushing a new stacked block, matching the prior finding exactly (line drift only). No code change this pass."},{"a":"repeater","f":"Decoder: \"Send to Decoder\" from other tools / decode a selection in place","s":"present","i":"medium","e":"days","g":"\"Send to Decoder\" now exists from the three places it was missing: Proxy history / Site map's DetailPane (a DECODER menu, request/response, mirroring the existing COMPARER menu), Repeater's request/response message-editor panes (a DEC button beside the existing CMP button), and the Intercept queue's held-message toolbar (a DEC button beside CMP). Each dispatches send-to-decoder, which bumps the app reducer's decoder.seedNonce -- the Decoder tab watches that nonce and overwrites its own local input, then switches to the tab. The remaining honest gap from the original plan is unchanged and separate: the Proxy detail pane's own CodecBar selection-decode tools are still a second, divergent JS codec implementation (proxy.jsx) rather than a call to /api/transcode, so it can still disagree with the canonical Decoder tab on HTML-entity and hex edge cases -- unifying those two codec paths is unrelated follow-up work, not required for the affordance this item names.","w":"Closed 2026-08-12: added a client-only decoder.seedText/seedNonce slot to the app reducer and a send-to-decoder action; DecoderTab (app.jsx) takes a decoder prop and a useEffect keyed on seedNonce overwrites its local input (and clears stale output) on every send, including a repeat send of identical text. Wired three callers: proxy.jsx's DetailPane (new DECODER dropdown beside COMPARER), tabs.jsx's RepeaterTab (new DEC button beside CMP on both request and response panes), and tabs.jsx's InterceptTab (new DEC button beside CMP on the held-message toolbar).","v":"ui-v2/app.jsx: initialState.decoder slot + reducer's \"send-to-decoder\" case (bumps seedNonce); DecoderTab({decoder}) useEffect keyed on decoder.seedNonce. ui-v2/proxy.jsx: DetailPane's DECODER dropdown (request/response) calling the new onSendDecoder prop; ProxyTab wires onSendDecoder={{... dispatch send-to-decoder + onSwitchTab(\"decoder\") ...}}. ui-v2/tabs.jsx: RepeaterTab's sendToDecoder() + two DEC buttons (request/response panes); InterceptTab's sendToDecoder() + DEC button on the held-message toolbar.","o":"present","r":"Wave 2: \"Send to Decoder\" wired from Proxy/Site-map DetailPane, Repeater's request/response panes, and the Intercept held-message toolbar, closing the affordance half of #323 (partial -> present); the codec-divergence caveat is left honestly in gap as unrelated follow-up."},{"a":"repeater","f":"Decoder: hash-algorithm identification from a digest","s":"exceeds","i":"low","e":"hours","g":"","w":"Verified verbatim, wired, and surfaced. Burp has no equivalent.","v":"D:/dev/Nullock/Src/Core/Networking/transcode.cpp:287-308 `QStringList identifyHash(const QString &input)` — `if (s.startsWith(QLatin1String(\"$2a$\")) || ... \"$2b$\" || \"$2y$\") { out << QStringLiteral(\"bcrypt\"); return out; } ... \"$1$\" md5crypt, \"$5$\" sha256crypt, \"$6$\" sha512crypt, \"$argon2\"` then hex-length classification `case 32: out << \"MD5\" << \"NTLM\" << \"MD4\"; case 40: SHA-1/RIPEMD-160; case 56","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: JWT decode with security analysis","s":"exceeds","i":"low","e":"hours","g":"","w":"Verified on both sides. The proxy-side analyser is substantially richer than the auditor even credited (alg-confusion hint, kid injection, nbf/iat/iss/aud, JWE).","v":"Backend D:/dev/Nullock/Src/Core/Networking/transcode.cpp:166-174 `QString out = QStringLiteral(\"=== HEADER ===\\n\") + pretty(hdr) + ... if (alg.compare(QLatin1String(\"none\"), Qt::CaseInsensitive) == 0) out += \"\\n\\n[!] alg=none -- signature not verified; forgeable.\" else if (alg.startsWith(QLatin1String(\"HS\"))) ... out += \"\\n\\n[i] Signature is NOT verified here (no key).\"`. Proxy-side ui-v2/proxy.js","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: additional codecs beyond Burp's set (rot13, unicode escape, GraphQL, gRPC framing, CBOR, SAML)","s":"exceeds","i":"low","e":"days","g":"CBOR is still self-declared partial (no tag handling) -- unchanged by this batch. All four protocol decoders (graphql-parse/grpc-frame/cbor-decode/saml-decode) are now also reachable from the dedicated Decoder tab's op-button row, not just the Proxy/Repeater CodecBar -- both surfaces call the same pure client-side runCodec(), so behaviour is identical either way.","w":"Closed 2026-08-18: DecoderTab's OPS array (ui-v2/app.jsx) gains graphql-parse/grpc-frame/cbor-decode/saml-decode; run() special-cases those four names (CLIENT_ONLY_OPS) to call runCodec() directly (proxy.jsx, synchronous, already used by CodecBar) instead of round-tripping through the backend /api/transcode endpoint those decoders were never wired into.","v":"ui-v2/app.jsx DecoderTab OPS + CLIENT_ONLY_OPS + run(); ui-v2/proxy.jsx runCodec() cases graphql-parse/grpc-frame/cbor-decode/saml-decode (unchanged implementation, only the caller is new).","o":"exceeds","r":"Repeater-area polish batch: the Decoder tab's op-button row now includes the four protocol decoders that previously lived only in the Proxy/Repeater CodecBar, routed to the same pure runCodec() implementation."},{"a":"repeater","f":"Inspector: \"Request attributes\" (method, path, HTTP version/protocol)","s":"present","i":"medium","e":"days","g":"None — surfaced in the app by the new INSPECTOR tab.","w":"Closed 2026-08-02: the /api/inspect backend existed; added the INSPECTOR tab (commit 86f094c) that renders this. Verified via bundled-babel transform + field-contract match to inspector_logic (backend covered by inspector_logic_test).","v":"The INSPECTOR tab renders the request line: method, path, HTTP version, content-type, body size/kind (ui-v2 app.jsx InspectorTab -> /api/inspect).","o":"stub","r":"INSPECTOR tab surfaces the /api/inspect structured view."},{"a":"repeater","f":"Inspector: \"Parameters\" — query string parameters","s":"present","i":"high","e":"days","g":"None -- surfaced read-only in the INSPECTOR tab's Query params section (ui-v2/app.jsx InspectorTab, view.queryParams), the same commit that shipped the sibling Cookies/JWT-decode/Request-attributes projections in the same panel. No add/remove/edit affordance -- same as those three items, and consistent with how this register already grades a read-only Inspector projection as full parity.","w":"Register-accuracy correction: this item's “no UI, nothing calls /api/inspect” verdict went stale the moment the INSPECTOR tab shipped (commit 86f094c, 2026-08-02) -- that same commit closed sibling items #327 (request attributes), #330 (cookies) and #332 (JWT decode) to present, but this one was never reconciled. Re-verified against live source: ui-v2/app.jsx:3045 `view.queryParams && view.queryParams.length ? <Section title={\"Query params \" ...` renders every pair /api/inspect returns via inspector_logic.cpp's parsePairs(query) (:168). Flipped stub -> present for consistency with the established grading of the other three Inspector projections in the same panel; no code change needed.","v":"D:/dev/Nullock/Src/Core/Networking/inspector_logic.cpp:164-168 `const int q = target.indexOf('?'); out[\"path\"] = q < 0 ? target : target.left(q); const QString query = q < 0 ? QString() : target.mid(q + 1); out[\"query\"] = query; out[\"queryParams\"] = parsePairs(query);` over :30-43 `if (eq < 0) arr.append(nv(urlDecode(part, formDecode), QString())); else arr.append(nv(urlDecode(part.left(eq), formD UI: ui-v2/app.jsx:3045 `{view.queryParams && view.queryParams.length ? <Section title={\"Query params (\" + view.queryParams.length + \")\"}><KV rows={view.queryParams} /><\/Section> : null}` inside InspectorTab, called via NL.actions.inspect(raw, kind) -> POST /api/inspect.","o":"stub","r":"Register-accuracy fix: the INSPECTOR tab (86f094c) already renders view.queryParams read-only, matching the same-panel grading precedent for Cookies/JWT/Request-attributes -- this item was simply never flipped when that shipped. No code change, docs/roadmap regenerated."},{"a":"repeater","f":"Inspector: \"Parameters\" — body parameters (form-urlencoded and JSON)","s":"present","i":"high","e":"weeks","g":"All four body content types now populate the params view: form-urlencoded, JSON (recursively flattened into Burp-style dotted/bracketed leaves -- user.name, user.addr.city, tags[0], items[1].id -- incl. a top-level array and {}/[]-placeholders for empty containers), multipart/form-data (each part as name=value; a file part shows [file: <name>, <N> bytes] parsed from the RAW bytes so a binary upload isn't transcode-mangled), and XML (leaf element-path text order.item.sku plus attributes order@id). All parsers are depth-/count-bounded (maxDepth 64, maxParams 2000).","w":"Implemented + mutation-proven. inspector_logic.cpp gained flattenJson (recursive JSON), parseMultipart (raw-byte multipart) and flattenXml (QXmlStreamReader element paths + attributes); the content-type switch dispatches form/multipart/json/xml/other. Tests/inspector_logic/inspector_logic_test.cpp (60 pass) locks nested JSON, top-level array, multipart text+file, and XML path+attr; four mutants (array [i] format, object prefix, multipart file-detection, XML path nesting) each fail only their targeted cases. The prior gap's UI half already shipped (ui-v2 InspectorTab renders view.bodyParams); with all body kinds now parsed, the item is at parity.","v":"inspector_logic.cpp flattenJson()/parseMultipart()/flattenXml(); switch dispatches multipart/form-data + xml alongside form + json. Live POST /api/inspect: nested JSON -> {user.name,user.addr.city,tags[0]}; multipart -> {t:hi, f:[file: a.bin, 3 bytes]}; XML -> {a@id:7, a.b:hi}. Full gauntlet green (ctest 100/100, probe_smoke 156/156).","o":"stub","r":"Closed partial -> present: recursive JSON flattening, raw-byte multipart parsing, and XML element-path/attribute flattening added to inspector_logic.cpp, so all four body content types populate the params view. Mutation-proven (4 mutants), gauntlet green, live-verified via /api/inspect. The reachability (UI) half had already shipped via the INSPECTOR tab; this closes the parsing-depth half."},{"a":"repeater","f":"Inspector: \"Cookies\" — request cookies and response Set-Cookie with attributes","s":"present","i":"medium","e":"days","g":"None — surfaced in the app by the new INSPECTOR tab.","w":"Closed 2026-08-02: the /api/inspect backend existed; added the INSPECTOR tab (commit 86f094c) that renders this. Verified via bundled-babel transform + field-contract match to inspector_logic (backend covered by inspector_logic_test).","v":"The INSPECTOR tab renders request cookies and response Set-Cookie with attributes (name/value/attributes) from /api/inspect.","o":"stub","r":"INSPECTOR tab surfaces the /api/inspect structured view."},{"a":"repeater","f":"Inspector: \"Headers\" panel with add / remove / reorder","s":"present","i":"high","e":"weeks","g":"None -- an editable HEADERS view (its own tab alongside raw/body/preview/hex/inspector, the same sibling-view convention the Params table already established) now lets the user add, remove, and reorder headers with per-row up/down/× buttons in both the Repeater request editor and Intercept's held request/response editors, rewriting the underlying raw text on every change.","w":"Closed 2026-08-23: added a pure repeaterHeaderRows/repeaterHeaderRowsToLines/repeaterRebuildHeaderRows round-trip (ui-v2/tabs.jsx) built on the same repeaterSplitRaw/repeaterBuildRaw machinery repeaterChangeMethod/repeaterChangeBodyEncoding already use -- works for both a request line and a status line, since repeaterSplitRaw only treats the first raw line as three space-separated parts. A new RepeaterHeadersView component (add-row button, per-row name/value inputs, up/down reorder, remove button) is wired into the \"headers\" view tab of the Repeater request editor (rep.request, dispatches repeater-set) and Intercept's held-message editor for both request and response (editedText/setEditedText) -- the two editors in the message-editor toolbar family that were already editable. Repeater's own RESPONSE pane and Proxy history's DetailPane stay on the prior read-only headers text view, matching their own pre-existing \"read-only\" labels/scope (Burp doesn't offer header editing on immutable history entries either). The write path the old why-text found missing (\"no re-serializer anywhere\") now exists and is UI-reachable.","v":"ui-v2/tabs.jsx repeaterHeaderRows/repeaterHeaderRowsToLines/repeaterRebuildHeaderRows (pure); RepeaterHeadersView + RepeaterHeaderRow (new components); reqView===\"headers\" branch in RepeaterTab's request pane (dispatches {type:\"repeater-set\", payload:{request:next}}); editorView===\"headers\" branch in the Intercept held-message editor (setEditedText) for both current.kind 0 (request) and 1 (response), both of which already listed \"headers\" in their views array.","o":"stub","r":"Editable HEADERS view (add/remove/reorder, ui-v2/tabs.jsx RepeaterHeadersView) wired into the Repeater request editor and Intercept's held request+response editors, sharing the repeaterSplitRaw/repeaterBuildRaw round-trip already used by the method/encoding transforms. Repeater's read-only response pane and Proxy history's DetailPane intentionally left on the prior read-only headers text view."},{"a":"repeater","f":"Inspector: JWT decoding of tokens found in headers and cookies","s":"present","i":"medium","e":"days","g":"None — surfaced in the app by the new INSPECTOR tab.","w":"Closed 2026-08-02: the /api/inspect backend existed; added the INSPECTOR tab (commit 86f094c) that renders this. Verified via bundled-babel transform + field-contract match to inspector_logic (backend covered by inspector_logic_test).","v":"The INSPECTOR tab renders decoded JWTs (alg/typ/header/payload) found in headers and cookies, from inspector_logic collectJwts via /api/inspect.","o":"stub","r":"INSPECTOR tab surfaces the /api/inspect structured view."},{"a":"repeater","f":"Repeater: per-tab request history with back/forward (< >) navigation through previously sent requests","s":"present","i":"blocker","e":"days","g":"None -- each tab keeps a capped history of prior sends; ◀ ▶ buttons in the target row (ui-v2/tabs.jsx) step back/forward through it, showing a live n/count position label and a status/timestamp tooltip, and reload the selected entry into the tab via /api/repeater/history/load.","w":"Confirmed. I re-read the struct and re-ran the synonym hunt myself (historyIndex, undoStack, prevRequest, goBack, goForward, requestHistory, versions[) across Src/Core/Networking and ui-v2 — zero hits. Send genuinely overwrites in place.","v":"D:/dev/Nullock/Src/Core/Networking/repeater.hpp:19-27 `struct RepeaterTab { QString name; QString host; int port = 443; bool useTls = true; QString requestText; QString responseText; QString statusLine; };` — no history container. Overwrite at repeater.cpp:138-143 `if (result.ok) { t.responseText = QString::fromUtf8(result.rawResponse); t.statusLine = ...`. Snapshot per-tab object (control_server.","o":"present","r":"Closes the last remaining gap: a ◀ ▶ control in RepeaterTab's target row (ui-v2/tabs.jsx) navigates the active tab's send history via two pure helpers (repeaterHistoryPrevIndex/repeaterHistoryNextIndex, boundary-clamped) and NL.actions.repeaterHistoryLoad -> POST /api/repeater/history/load. histPos null means \"at the live/newest send\" (already what the tab shows, no wire call needed); a numeric index reloads that entry's full request/response via the existing endpoint. No backend touched -- reads only the historyCount/history[].statusLine/.sentAt fields already in the snapshot (control_server.cpp:1508-1514)."},{"a":"repeater","f":"Repeater: tab groups (drag tabs into a named group, reorder tabs)","s":"absent","i":"medium","e":"days","g":"No grouping, no drag-reorder. Past ~10 tabs the flat horizontal strip becomes unusable, and reordering requires close-and-recreate (which loses the tab entirely, since nothing persists).","w":"Confirmed. Fresh grep for tabGroup/groupName/sendGroup/draggable/dragstart across Src/Core/Networking/repeater.* and ui-v2/tabs.jsx: zero hits.","v":"Src/Core/Networking/repeater.hpp:187 `QList<RepeaterTab> m_tabs;` -- the RepeaterTab struct carries no group or order field; ui-v2/tabs.jsx's tab strip renders a flat horizontal scroller with no drag handlers (re-grepped for draggable/dragstart in tabs.jsx -- 0 hits).","o":"","r":"Wave 0 register-accuracy audit: held at absent. Fresh case-insensitive grep for tabGroup/groupName/sendGroup/draggable/dragstart across Src/Core/Networking/repeater.* and ui-v2/tabs.jsx returns zero hits -- no grouping or drag-reorder exists for Repeater tabs. RepeaterTab still has no group/order field. No code change this pass."},{"a":"repeater","f":"Repeater: \"Send group in sequence (separate connections)\"","s":"absent","i":"medium","e":"weeks","g":"Cannot drive a multi-step flow (login -> token -> privileged action) as an ordered sequence from Repeater. Note Src/Core/Networking/chain_runner.* does implement multi-step request chaining, but it is a separate engine with no Repeater entry point.","w":"Confirmed. No group concept exists and the only send path takes no tab list.","v":"Src/Core/Networking/repeater.cpp:135 `void Repeater::send() { if (m_busy) return; auto &t = activeTab_(); ... }` -- active tab only, one request per call. control_server.cpp:3685 `if (path == \"/api/repeater/send\")` reads no body parameters and just invokes send() on the active tab via a queued connection (line drift from the prior 116-153/3087-3097 citation, content unchanged).","o":"","r":"Wave 0 register-accuracy audit: held at absent. Repeater::send() (repeater.cpp:135) is still single-tab only (operates on activeTab_()), and POST /api/repeater/send (control_server.cpp:3685) still reads no body parameters at all -- it just QMetaObject::invokeMethod(...\"send\"...) on whichever tab is currently active. No group/sequence concept exists anywhere in the send path. No code change this pass."},{"a":"repeater","f":"Repeater: \"Send group in sequence (single connection)\" — single-packet attack over HTTP/2, last-byte synchronization over HTTP/1","s":"absent","i":"high","e":"weeks","g":"No single-packet or last-byte-sync send, and no path from Repeater to the race tester at all. The stale comment should also be fixed: Burp ships single-packet group send in Repeater in both Community and Pro.","w":"Confirmed, including the stale Burp claim in the comment. Fresh grep for last.byte / single.packet / lastByte / singlePacket across all of Src/ hits only those three comment lines, unchanged.","v":"Src/Core/Networking/race_tester.hpp:22-24 `// v1 fires via the thread pool (good enough to win most application-layer races); true last-byte / single-packet synchronization is a future raw-socket iteration.` -- verbatim match to the prior citation, no drift.","o":"","r":"Wave 0 register-accuracy audit: held at absent, including the stale-Burp-claim correction from the prior pass. race_tester.hpp's comment ('v1 fires via the thread pool ... true last-byte / single-packet synchronization is a future raw-socket iteration') is byte-for-byte unchanged, and a fresh grep for last.byte/single.packet/lastByte/singlePacket across Src/ still hits only those same comment lines -- no raw-socket last-byte-sync or single-packet send has landed, and there is still no path from Repeater into the race tester at all. No code change this pass."},{"a":"repeater","f":"Repeater: per-tab notes / annotations","s":"present","i":"low","e":"hours","g":"None -- a NOTES button in the tab strip (prompt-based, matching the existing double-click rename affordance) sets free-text per-tab notes; tabs carrying notes show a small pencil (✎) indicator and the tab tooltip includes the note text.","w":"Closed 2026-08-13: RepeaterTab (repeater.hpp:19-29) gains a `notes` QString field; Repeater::setTabNotes(index, notes) (repeater.cpp:219-223) mirrors the existing renameTab pattern and is exposed as POST /api/repeater/tab/notes (control_server.cpp:3183-3187). The snapshot's tabs[] array now includes notes (control_server.cpp:1501). ui-v2/tabs.jsx's RepeaterTab component gets a NOTES button in the tab strip (prompt-based edit of the active tab), a pencil indicator span on any tab carrying notes, and the tab tooltip appends the note text.","v":"Src/Core/Networking/repeater.hpp:19-29 (notes field), :87 (setTabNotes); repeater.cpp:219-223 (setTabNotes impl); control_server.cpp:1501 (snapshot to[\"notes\"]), :3183-3187 (/api/repeater/tab/notes); ui-v2/real-data.js:165 (repeaterTabNotes action); ui-v2/tabs.jsx onNotes handler + NOTES button + indicator span.","o":"present","r":"Repeater per-tab notes batch -- absent -> present. Backend adds a notes field to RepeaterTab plus setTabNotes()/the /api/repeater/tab/notes endpoint; frontend adds a NOTES button, a per-tab pencil indicator, and a tooltip note. This cloud session cannot build the C++ side; will confirm the next GitHub Actions ci run is green before calling this fully closed."},{"a":"repeater","f":"Repeater: \"Follow redirection\" button + redirect-following setting (never / on-site only / in-scope only / always) and \"Process cookies in redirections\"","s":"present","i":"high","e":"days","g":"","w":"Confirmed by my own grep over repeater.cpp, networking.cpp and tabs.jsx for followRedirect/maxRedirect/redirectFollow/Location: — zero hits in all three. The only redirect logic in the tree is the unrelated robots.txt fetcher.","v":"D:/dev/Nullock/Src/Core/Networking/repeater.cpp:133-147 does one `m_client.send(...)` and stores the result with no 3xx branch. HttpClient::send (Src/Core/Networking/networking.cpp:186-330) parses status/Content-Length/Transfer-Encoding but never reads Location. Unrelated: Src/Core/Networking/robots_recon.cpp:9 `constexpr int kMaxRedirectHops = 3;`.","o":"absent","r":"The ui-v2 Repeater tab now exposes both settings inline in the target-row: a FOLLOW select (mirroring RedirectLogic::FollowPolicy 0-3, never/on-site/in-scope/always) and a COOKIES checkbox, both dispatched via the existing repeater-set action to POST /api/repeater/set -- the same backend + API from the a6987bb wave, now reachable from a click rather than only from a raw API call. The backend snapshot (control_server.cpp) was extended to serialize followRedirects/processCookies back to the GUI so the controls reflect live state after a reload. No remaining gap for this item's own ask (button + 4-mode setting + cookie-processing setting)."},{"a":"repeater","f":"Repeater: \"Change request method\" (GET ↔ POST, moving parameters between query string and body)","s":"present","i":"medium","e":"days","g":"None -- a ⇄ METHOD button in the Repeater request pane-head (ui-v2/tabs.jsx) toggles GET <-> POST on the raw request text via the pure repeaterChangeMethod() helper: GET moves its query string into an x-www-form-urlencoded body (setting Content-Type) and POST moves an urlencoded body back into the query string (merging with any existing query params), recomputing Content-Length either way. Dispatched through the same repeater-set path a hand edit uses, so it round-trips through /api/repeater/set like any other edit.","w":"Closed 2026-08-17: added repeaterChangeMethod() (ui-v2/tabs.jsx) -- a pure request-line/body transform with its own small parser/serializer (repeaterSplitRaw/repeaterBuildRaw/repeaterSetHeader family), since proxy.jsx's parseRawRequest is one-way and drops Host/Content-Length, unsuitable for an edit-in-place button. Wired to a new ⇄ METHOD button next to the existing CMP/DEC/SEQ pane-head buttons.","v":"ui-v2/tabs.jsx repeaterChangeMethod() + repeaterSplitRaw/repeaterBuildRaw/repeaterSetHeader/repeaterRemoveHeader helpers; the ⇄ METHOD button in RepeaterTab's REQUEST pane-head dispatches {type:\"repeater-set\", payload:{request: repeaterChangeMethod(rep.request)}}, the identical mutation path the request textarea's own onChange uses (app.jsx:148-150 -> NL.actions.repeaterSet -> POST /api/repeater/set).","o":"","r":"Repeater request-transform batch: pure client-side GET<->POST param-location swap button, no backend change needed (the raw text just flows through the existing repeater-set/repeater/set mutation path)."},{"a":"repeater","f":"Repeater: \"Change body encoding\" (application/x-www-form-urlencoded ↔ multipart/form-data)","s":"present","i":"medium","e":"days","g":"None for hand-built or freshly-generated bodies -- a ⇄ ENCODING button in the Repeater request pane-head converts application/x-www-form-urlencoded <-> multipart/form-data via the pure repeaterChangeBodyEncoding() helper (generates a random boundary, wraps each param as a form-data part, or parses an existing multipart body's boundary/parts back into urlencoded pairs), recomputing Content-Type/Content-Length either way. Captured requests now load their full bodies. This conversion operates on form field names and values; multipart file metadata and opaque binary file parts are not preserved when converting to URL-encoded form data.","w":"Closed 2026-08-17: added repeaterChangeBodyEncoding() (ui-v2/tabs.jsx), reusing the same repeaterSplitRaw/repeaterBuildRaw/repeaterSetHeader parser family as #339's method-swap button. Wired to a new ⇄ ENCODING button next to it. The #303 capture-time multipart-destruction defect is a separate, already-tracked gap this frontend-only change does not touch.","v":"ui-v2/tabs.jsx repeaterChangeBodyEncoding() (boundary-aware multipart part parser + builder) and repeaterUrlDecode(); the ⇄ ENCODING button in RepeaterTab's REQUEST pane-head dispatches {type:\"repeater-set\", payload:{request: repeaterChangeBodyEncoding(rep.request)}}. #303's placeholder-body defect (control_server.cpp send-to-Repeater path) is the named remaining limit, unchanged by this wave.","o":"","r":"Repeater request-transform batch: pure client-side urlencoded<->multipart body re-encode button, no backend change needed."},{"a":"repeater","f":"Repeater: response \"Render\" tab (renders the HTML response)","s":"present","i":"medium","e":"days","g":"No way to see what a reflected payload actually does in a renderer. (A sandboxed srcdoc iframe would be the safe implementation; rendering attacker-controlled HTML in the tool's own origin would be a self-XSS on the control server.)","w":"Confirmed, and I verified the proxy 'preview' tab the auditor flagged: it really is only a JSON pretty-printer, not a renderer.","v":"D:/dev/Nullock/ui-v2/tabs.jsx response pane: `<textarea className=\"txt readonly\" value={rep.response} readOnly />` — no view tabs, no iframe. Proxy preview at ui-v2/proxy.jsx:1102-1108 `if (view === \"preview\") { const t = (body || \"\").trim(); if (t.startsWith(\"{\") || t.startsWith(\"[\")) { try { return JSON.stringify(JSON.parse(t), null, 2); } catch (e) {} } return body || \"(no body)\"; }`. No srcdoc","o":"absent","r":"Response pane gets a Render view: sandboxed srcdoc iframe (sandbox=\"\", no scripts/forms/same-origin) rendering the response body. tabs.jsx RepeaterTab, respView===\"render\"."},{"a":"repeater","f":"Repeater: message editor views — Pretty / Raw / Hex for both request and response","s":"partial","i":"high","e":"hours","g":"The views exist, but the Repeater response is converted from bytes to UTF-8 text before the Hex view receives it. Invalid UTF-8 bytes become replacement characters; the Hex view shows the encoded display text rather than the original response bytes.","w":"The browser offers Raw, Headers, Body, Preview and Hex views for both panes, with a static Render view for responses. A live response containing bytes 00 ff 80 41 becomes text 00 U+FFFD U+FFFD 41, so the full byte-fidelity requirement remains incomplete.","v":"ui-v2/tabs.jsx RepeaterEditorToolbar, reqText and respText; ui-v2/proxy.jsx toHexDump uses TextEncoder; Src/Core/Networking/repeater.cpp send converts rawResponse/decodedBody through QString::fromUtf8.","o":"absent","r":"Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits. Grade changed from present to partial."},{"a":"repeater","f":"Repeater: automatic \"Update Content-Length\" when the body is edited","s":"present","i":"blocker","e":"hours","g":"AUTO-CL recomputes the outgoing body length by default. Turning it off preserves deliberately malformed request framing for manual testing.","w":"Repeater::send encodes the complete request and calls ChainRunner::normalizeContentLength when enabled. The browser exposes the setting. Native helper tests and live binary-request regressions cover length recomputation without truncating or changing the request body.","v":"Src/Core/Networking/repeater.cpp send and NetworkingLogic::encodeRequestText; Src/Core/Networking/chain_runner.cpp normalizeContentLength; ui-v2/tabs.jsx AUTO-CL checkbox; Tests/chain_runner; scripts/runtime_regression.py; scripts/repeater_cli_runtime.py.","o":"present","r":"Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits."},{"a":"repeater","f":"Repeater: HTTP/2 support — per-tab HTTP/1 vs HTTP/2 protocol toggle, raw pseudo-header editing, HTTP/2-specific request smuggling","s":"absent","i":"high","e":"weeks","g":"No h2 in the manual-testing tool despite a working nghttp2 client in the proxy layer. Blocks h2-specific work: pseudo-header injection, h2.CL/h2.TE smuggling, single-packet timing.","w":"Confirmed. Fresh grep for http2/HTTP\\/2/h2 across repeater.cpp and repeater.hpp returned nothing, and the client writes HTTP/1 bytes to a plain socket.","v":"Src/Core/Networking/repeater.hpp -- RepeaterTab has no protocol field (re-checked, unchanged); Src/Core/Networking/networking.cpp's send path still connects a plain socket and writes HTTP/1 request bytes with HTTP/1 status-line parsing. The h2 stack exists but elsewhere: Src/BackEnd/Proxy/h2_client_logic.cpp, http2_client.cpp, h2_server.cpp (nghttp2, proxy-layer only).","o":"","r":"Wave 0 register-accuracy audit: held at absent. Fresh grep for http2/HTTP\\/2/h2 across repeater.cpp and repeater.hpp still returns nothing; RepeaterTab has no protocol field and the client still writes HTTP/1 bytes to a plain QTcpSocket/QSslSocket. The nghttp2-backed h2 stack (h2_client_logic.cpp, http2_client.cpp, h2_server.cpp) exists but remains confined to the proxy layer, with no Repeater entry point. No code change this pass."},{"a":"repeater","f":"Repeater: \"Unpack gzip / deflate\" in the response view","s":"present","i":"high","e":"hours","g":"gzip, x-gzip and deflate are decoded for display. Brotli and zstd remain unsupported. Display retains the original response headers, including compressed Content-Length; the decoded text is not a raw wire export.","w":"HttpClient populates decodedBody through decodeContentEncoding, and Repeater displays it with the original header block. The content_decode native suite tests gzip and both wrapped/raw deflate. The former statement that the change could not be built is stale.","v":"Src/BackEnd/Proxy/content_decode.cpp; Src/Core/Networking/networking.cpp decodeContentEncoding call; Src/Core/Networking/repeater.cpp decodedBody display; Tests/content_decode/content_decode_test.cpp.","o":"present","r":"Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits."},{"a":"repeater","f":"Repeater: cancel an in-flight request; non-blocking send","s":"partial","i":"high","e":"days","g":"Send runs on a worker and the UI remains responsive. Stop marks cancellation and prevents later redirects after the current response finishes; it does not immediately abort a stalled socket. One request can run at a time across all tabs.","w":"sendAsync copies the request into a worker and applies the result without replacing newer edits. Browser/API Stop and the CLI stop command share the cancellation flag. Live API and browser regressions verify responsiveness, busy state, draft preservation and redirect cancellation.","v":"Src/Core/Networking/repeater.cpp sendAsync/cancel; ui-v2/tabs.jsx Repeater Stop; bin/nullock repeater stop; scripts/control_responsiveness_regression.py; Tests/ui/repeater_responsiveness_browser_test.cjs; scripts/repeater_cli_test.py.","o":"","r":"Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits. Grade changed from absent to partial."},{"a":"repeater","f":"Repeater: keyboard shortcut to send (Ctrl+Space / configurable hotkeys)","s":"present","i":"medium","e":"hours","g":"Edit-send-read is the core Repeater loop; forcing a mouse trip on every iteration is a real throughput tax. No configurable hotkey layer exists at all.","w":"Confirmed for Repeater send, but the auditor's supporting claim was overstated and I am correcting it: there ARE other key handlers in the UI (Enter-to-submit in scope, decoder and recon inputs). What does not exist is any hotkey for Repeater send, and no ctrlKey/metaKey handling anywhere.","v":"D:/dev/Nullock/ui-v2/tabs.jsx Repeater send is mouse-only: `<button className=\"btn primary\" onClick={send} disabled={busy}>{busy ? \"SENDING…\" : \"▶ SEND\"}<\/button>`. Other handlers that do exist: ui-v2/app.jsx:1406 `onKeyDown={e => { if (e.key === \"Enter\") run(); }}`, :1844 similar, ui-v2/tabs.jsx:63 and :91 (scope add), ui-v2/proxy.jsx:613 and :772 (Escape-to-close overlays). `grep -an 'ctrlKey|me","o":"absent","r":"Register-accuracy fix: Ctrl+Space-to-send was actually shipped in commit 1074f35 (Comparer wave, 2026-08-08) but parity.json was never flipped for it. tabs.jsx:312 `onKeyDown={e => { if (e.ctrlKey && e.code === \"Space\") { e.preventDefault(); send(); } }}` confirmed live in the current tree."},{"a":"repeater","f":"Repeater: search / highlight within the request and response editors (case-sensitivity, regex, match count)","s":"present","i":"medium","e":"days","g":"Finding a reflected canary in a large response means relying on the browser's own Ctrl+F, which does not reliably search a textarea's scrolled content.","w":"Confirmed. The Repeater panes are plain textareas with no search affordance; the deep-search facility is bound to proxy history rows only.","v":"D:/dev/Nullock/ui-v2/tabs.jsx Repeater panes are two `<textarea>` elements with header rows showing only a LINES count. Existing search is row-scoped: ui-v2/proxy.jsx:1137-1155 uses `NL.actions.search(search, \"both\", 500)` -> real-data.js:141-147 `search(q, where = \"both\", limit = 200) { const url = \"/api/search?q=\" ... }`, which returns matching history rows, not in-pane matches.","o":"absent","r":"In-editor find gains a case-sensitivity toggle (\"Aa\") and a regex mode toggle (\".*\", JS regex syntax, zero-length-match safe, invalid patterns fail closed to 0 matches instead of throwing). Combined with the existing wrap-around next/prev and match counter (cd03a95), this closes the full ask: case-sensitivity, regex, and match count."},{"a":"repeater","f":"Repeater: send from a Repeater tab to Intruder / Comparer / Decoder / Sequencer / Scanner","s":"present","i":"high","e":"days","g":"Closed: RepeaterTab now has a send-to path for all five sibling tools -- → Comparer/→ Decoder/→ Sequencer already existed (#345/#323/#167), and this wave added → Intruder (promotes the draft request into a new attack template via the same send-to-intruder-raw reducer case InterceptTab's own send-to-Intruder button already used) and → Scanner (runs the active-test battery against the draft request via the same parseRawRequest+auditRun pairing InterceptTab's own send-to-Scanner button already established). No remaining Repeater-side gap; Repeater is no longer a dead end.","w":"Reclassified 2026-08-22 (repeater send-to wave). Re-audited live source: the original claim ('exactly two send-to sites, both in the proxy DetailPane') is now stale -- RepeaterTab (ui-v2/tabs.jsx) already had working → CMP / → DEC / → SEQ buttons in its request/response pane headers from prior waves. The only two missing legs, Intruder and Scanner, are added in this wave: sendToIntruder dispatches the existing send-to-intruder-raw action (app.jsx, already used by InterceptTab) with rep.host/port/tls/request; sendToScanner reuses parseRawRequest (proxy.jsx, already used by InterceptTab's own send-to-Scanner) to build the audit URL/method/body/headers and calls NL.actions.auditRun, rendering the same finding-count banner InterceptTab already renders. Both reuse existing, already-verified reducer cases/backend calls -- no new backend surface.","v":"ui-v2/tabs.jsx RepeaterTab: sendToComparer/sendToDecoder/sendSelectionToSequencer (pre-existing) plus this wave's sendToIntruder (dispatch({type:\"send-to-intruder-raw\", host: rep.host, port: rep.port, tls: rep.tls, text: rep.request})) and sendToScanner (parseRawRequest({host:rep.host,port:rep.port,tls:rep.tls}, rep.request) -> NL.actions.auditRun(parsed.fullUrl, {method, body, headers})); request-pane header buttons ↦ CMP / ↦ DEC / ↦ SEQ / ↦ INT / ↦ SCAN plus a scan-result banner (finding count / error, DISMISS); app.jsx \"send-to-intruder-raw\" reducer case (pre-existing, previously reachable only from InterceptTab); ui-v2/real-data.js auditRun() (pre-existing, POST /api/audit/run).","o":"present","r":"Repeater send-to wave: absent -> present. Added → Intruder and → Scanner send-to buttons to RepeaterTab's request pane, completing the five-tool set (Comparer/Decoder/Sequencer already present from prior waves). Pure frontend, reusing existing reducer cases and the existing parseRawRequest+auditRun pairing InterceptTab already established. No backend change."},{"a":"repeater","f":"Repeater: tab state persisted in the project file and restored on reopen","s":"present","i":"blocker","e":"days","g":"Repeater tabs save per project every two seconds when changed, before project switching, and after shutdown workers drain. Failed writes retain the current project and retry. Per-tab request history remains a separate capability.","w":"Repeater tabs save per project every two seconds when changed, before project switching, and after shutdown workers drain. Failed writes retain the current project and retry. Per-tab request history remains a separate capability.","v":"Src/App/app.cpp saveWorkspaces; Src/Core/Storage/project_store.cpp saveSessionWorkspace; scripts/workspace_recovery_regression.py","o":"present","r":"Repeater tabs save per project every two seconds when changed, before project switching, and after shutdown workers drain. Failed writes retain the current project and retry. Per-tab request history remains a separate capability."},{"a":"repeater","f":"Comparer: item list — Paste / Load from file / Remove / Clear, sortable, pick any two","s":"present","i":"medium","e":"days","g":"Item list exists with paste/load-file/remove/clear; only two items are picked (A/B) for a pairwise diff at a time -- matches Burp's own Comparer, which also compares exactly two items per run.","w":"Re-read app.jsx ComparerTab after rewriting it. state.comparer.items is a real list (lifted into the app reducer, not local-only state) with comparer-add/remove/clear reducer cases; the toolbar has a paste popup (label + textarea + Add) and a hidden <input type=file> wired to FileReader.readAsText. Each row shows label, byte length, and A/B picker buttons.","v":"ui-v2/app.jsx ComparerTab: reducer cases comparer-add/comparer-remove/comparer-clear; item-list toolbar (+ paste item / load file / clear all) and per-item A/B/remove row.","o":"absent","r":"Comparer rebuilt around a real item list + send-to-comparer + synced dual-pane diff + text/hex toggle."},{"a":"repeater","f":"Comparer: \"Send to Comparer\" from any Burp message","s":"present","i":"medium","e":"hours","g":"Wired from Proxy history (request or response) and Repeater (request/response panes); not yet from Decoder output or Intruder results.","w":"Re-read proxy.jsx DetailPane and tabs.jsx RepeaterTab after adding the wiring. DetailPane has a \"COMPARER ▾\" dropdown (request/response) that dispatches comparer-add and switches to the Comparer tab; RepeaterTab has a \"CMP\" button on both the request and response pane heads doing the same.","v":"ui-v2/proxy.jsx DetailPane onSendComparer dropdown (request/response) -> dispatch comparer-add + onSwitchTab(\"comparer\"); ui-v2/tabs.jsx RepeaterTab sendToComparer() wired to both pane-head buttons.","o":"absent","r":"Comparer rebuilt around a real item list + send-to-comparer + synced dual-pane diff + text/hex toggle."},{"a":"repeater","f":"Comparer: two synchronized side-by-side result panels with \"Sync views\" scrolling","s":"present","i":"medium","e":"days","g":"","w":"Re-read the new ComparerTab result rendering. The backend's single merged segments[] array (POST /api/compare) is split client-side into streamA (op !== \"ins\") and streamB (op !== \"del\"), rendered into two <div> panes with independent refs; onScroll on either pane mirrors scrollTop/scrollLeft onto the other while a \"sync: on/off\" toggle button is active (default on).","v":"ui-v2/app.jsx ComparerTab: streamA/streamB filters, paneARef/paneBRef, onScrollA/onScrollB, syncScroll state + toggle button.","o":"absent","r":"Comparer rebuilt around a real item list + send-to-comparer + synced dual-pane diff + text/hex toggle."},{"a":"repeater","f":"Comparer: Text / Hex toggle on the results view","s":"present","i":"low","e":"hours","g":"","w":"Re-read the new result rendering. A \"text\"/\"hex\" button pair sets view state; renderSeg() emits either the literal segment text or textToHexPairs(s.text) (UTF-8 byte pairs via TextEncoder) per diff segment, preserving the same insert/delete color coding in both modes.","v":"ui-v2/app.jsx: textToHexPairs() helper + ComparerTab view state (\"text\"|\"hex\") + renderSeg().","o":"absent","r":"Comparer rebuilt around a real item list + send-to-comparer + synced dual-pane diff + text/hex toggle."},{"a":"repeater","f":"Decoder: Octal encode / decode","s":"present","i":"low","e":"hours","g":"None. octal-encode/decode (3-digit octal per byte) added to the transcode engine + Decoder UI.","w":"Closed 2026-08-10 (eb944ee).","v":"transcode.cpp octalEncode/octalDecode + apply()/ops(); Tests/transcode round-trip + reject cases; ui-v2 Decoder op list.","o":"absent","r":"Octal codec added + tested."},{"a":"repeater","f":"Decoder: Binary encode / decode","s":"present","i":"low","e":"hours","g":"None. binary-encode/decode (8 bits per byte) added to the transcode engine + Decoder UI.","w":"Closed 2026-08-10 (eb944ee).","v":"transcode.cpp binaryEncode/binaryDecode + apply()/ops(); Tests/transcode round-trip + reject cases.","o":"absent","r":"Binary codec added + tested."},{"a":"repeater","f":"Decoder: Gzip encode / decode","s":"present","i":"medium","e":"hours","g":"Closed client-side, not via the backend gzip zlib path this item originally scoped -- the browser's own Compression Streams API (CompressionStream/DecompressionStream, 'gzip' format) does the encode/decode entirely in ui-v2, no /api/transcode round-trip, matching the Decoder tab's existing client-only-op pattern (graphql-parse/grpc-frame/cbor-decode/saml-decode). Binary output is shown as base64 text on encode; decode accepts base64 gzip input and falls back to a hex dump if the decompressed bytes aren't valid UTF-8, same convention as the existing base64-decode op. Requires a browser with the Compression Streams API (Chrome 80+, Firefox 113+, Safari 16.4+) -- older browsers get a caught, readable error instead of a silent failure. Does not cover brotli/zstd (no browser stream codec for either), an honest remainder shared with the original gap text.","w":"Confirmed no backend gzip transcode op exists (transcode.cpp's operations() still has none) and did not add one -- instead wired the operation entirely client-side, since gzip/gunzip needs no server round-trip and the Web platform already ships a stream-based codec for it. Verified via a real gzip round-trip functional test (ascii, unicode, empty input, magic-byte check on the compressed output) and negative cases (invalid base64, valid-base64-but-not-gzip, non-UTF8 decompressed payload) run against the actual babel-transformed module in a vm sandbox with Node's native CompressionStream/DecompressionStream.","v":"ui-v2/app.jsx: gzipEncodeText/gzipDecodeText (CompressionStream/DecompressionStream 'gzip', bytesToBase64/base64ToBytes helpers) added just above DecoderTab; DecoderTab's OPS array gains \"gzip-encode\"/\"gzip-decode\"; a new ASYNC_CLIENT_OPS dispatch table in run() (parallel to the existing sync CLIENT_ONLY_OPS/runCodec table, since Compression Streams are async) routes both ops away from NL.actions.transcode.","o":"present","r":"Wave 2: Decoder gzip encode/decode wired purely client-side via the browser Compression Streams API (no backend transcode op needed); absent -> present. Brotli/zstd remain unsupported (no browser stream codec), an honest remainder shared with the original gap."},{"a":"repeater","f":"Decoder: Text / Hex view toggle per block","s":"present","i":"medium","e":"hours","g":"None -- the output hex view now reads the backend's outputBase64 field (raw octets) when present, instead of re-encoding the already-UTF-8-mangled `output` string.","w":"Wave 2 (2026-08-26): wired the remaining ui-v2 half. DecoderTab now tracks the transcode response's outputBase64 in its own state (outputB64), reset alongside output on every run/seed/use-as-input, and derives the output hex view from hexDumpBytes(base64ToBytes(outputB64)) -- the exact decoded bytes -- falling back to the prior toHexDump(output) only when outputBase64 is absent (encode ops / text-only ops carry no outputBytes server-side). hexDumpBytes is a new byte-array-taking function factored out of proxy.jsx's toHexDump(string), which now just UTF-8-encodes its input and delegates -- no behavior change for its other callers (input hex view, proxy/repeater raw-view hex mode, the gzip-decode fallback). Verified functionally: hex-decode of 00ff41 -> outputBase64 \"AP9B\" -> hexDumpBytes(base64ToBytes(...)) reproduces \"00 ff 41\" exactly, where the old toHexDump(output) path produced \"00 ef bf bd 41\" (the UTF-8 encoding of the U+FFFD that had already swallowed the 0xff byte server-side).","v":"ui-v2/proxy.jsx hexDumpBytes(bytes) (new, hoisted out of toHexDump); toHexDump(s) now `return hexDumpBytes(new TextEncoder().encode(s));`. ui-v2/app.jsx DecoderTab: outputB64 state set from r.outputBase64 in run(), cleared in the seedNonce effect and useOutputAsInput; outputHex = React.useMemo reading hexDumpBytes(base64ToBytes(outputB64)) when outputB64 is truthy, else toHexDump(output); output hex-view textarea now renders outputHex. Src/BackEnd/Control/control_server.cpp:10514-10515 already emitted outputBase64 = r.outputBytes.toBase64() when outputBytes is non-empty.","o":"present","r":"Wave 2: DecoderTab's output hex view now consumes /api/transcode's outputBase64 field via a new hexDumpBytes(bytes) helper, closing the frontend-only gap the prior register correction (663a1f2) left open -- no backend change."},{"a":"repeater","f":"Inspector: docked structured side panel in the Repeater / Intruder / Proxy message editors","s":"present","i":"high","e":"weeks","g":"None — docked in all three named editors via a new \"inspector\" view-tab, live off the existing /api/inspect.","w":"Closed 2026-08-09: the /api/inspect backend and its field contract already existed (closed the standalone paste-and-parse INSPECTOR tab in 86f094c); this wave added a reusable RepeaterInspectorPanel and mounted it as a debounced, live-updating view-tab inside the actual message editors instead of a separate tool. Verified via bundled-babel transform of both touched files + a vm-sandboxed render of DetailPane/IntruderTab proving the cross-file forward reference (tabs.jsx panel used from proxy.jsx, which loads earlier) resolves at render time, plus a field-name match against inspector_logic.cpp's JSON keys.","v":"ui-v2/tabs.jsx RepeaterInspectorPanel (debounced NL.actions.inspect call) mounted as the \"inspector\" view in RepeaterEditorToolbar's views list for both request+response panes; ui-v2/proxy.jsx DetailPane reqTab/respTab gain the same \"inspector\" option; ui-v2/tabs.jsx IntruderTab TEMPLATE pane gets an INSPECTOR/EDIT toggle. All three call the same control_server.cpp:9442 /api/inspect used by the pre-existing standalone tab.","o":"stub","r":"Added RepeaterInspectorPanel (tabs.jsx), a debounced /api/inspect view reused as a docked \"inspector\" tab in Repeater's request+response editors, Proxy history's DetailPane request+response panes, and Intruder's TEMPLATE editor -- closes the stub->partial reclassification to present."},{"a":"repeater","f":"Inspector: edit-in-place — modify a decoded value and have the raw message automatically re-encoded","s":"absent","i":"high","e":"weeks","g":"This is what makes Burp's Inspector a tool rather than a viewer: edit a param value and Burp re-encodes it and fixes Content-Length. Nullock has no write direction at all — and no Content-Length fixer to call even if it did (B11).","w":"Confirmed, and this one really is absent rather than stub: unlike the read path there is no code at all. Re-ran the symbol hunt (rebuildRequest/applyInspector/reserialize/applyEdit) across Src/ -- the only reserialize hits belong to the unrelated session-handling-rules feature (session_rules.cpp), not the Inspector.","v":"Src/Core/Networking/inspector_logic.hpp declares only inspectRequest/inspectResponse (both `QJsonObject f(const QByteArray &raw)` -- input bytes, output JSON, no write-back). No Inspector-specific re-serializer symbol exists anywhere in the tree; the only `reserialize` hits are session_rules.cpp:279/373 and session_rules.hpp:153, which reserialize a request for session-rule injection, an unrelated feature.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-ran the symbol hunt (rebuildRequest/applyInspector/reserialize/applyEdit) across Src/ -- the only reserialize hits are session_rules.cpp/.hpp's unrelated session-handling-rules reserialization (rewriting a request for injected cookies/tokens), not an Inspector write path. inspector_logic.hpp still declares only inspectRequest/inspectResponse, both read-only `QJsonObject f(const QByteArray &raw)` functions -- no mutation parameter is accepted anywhere in the inspect endpoint. No code change this pass."},{"a":"repeater","f":"Inspector: automatic multi-step decoding of values (HTML/URL/Base64) with a visible, revisable decode chain per item","s":"partial","i":"medium","e":"days","g":"Two decode paths now exist. (1) ui-v2 runs a client-side gated auto-detector (url/base64/html, up to 6 layers, with a per-step retarget <select>) over each Inspector KV row. (2) The BACKEND now also emits a decodeChain per query/cookie/body param: inspectRequest runs the bounded recursive Transcode::smartDecode over each value and attaches {decoded, decodeChain} when it makes progress -- covering url/base64/html AND hex/jwt -- so the API/report/CLI consumers of /api/inspect see decoded values too, not only the browser. Remaining gap versus Burp: neither path yet decodes an arbitrary highlighted byte RANGE in the raw editor (Burp's chain follows the text selection, not named fields), and gzip layers aren't covered.","w":"Closed 2026-08-26: the backend still decodes each Inspector value exactly once (inspector_logic.cpp unchanged, confirmed by re-reading it), so this is a second, purely client-side pass on top of that single decode -- ui-v2/tabs.jsx's repeaterInspectorKV() and ui-v2/app.jsx's InspectorTab KV() (used by every Status/Request-line/Headers/Cookies/Query/Body-params row in both surfaces) now route each row's value through one new shared component instead of a raw String() cast.","v":"ui-v2/tabs.jsx DecodeChainValue (new) plus its pure helpers decodeChainGateUrl/decodeChainGateBase64/decodeChainGateHtml (auto-detection gates), decodeChainRawUrl/decodeChainRawBase64/decodeChainRawHtml (ungated manual-override decoders), and buildDecodeChain(text, overrides, maxSteps) (chain builder, cycle-guarded via a `seen` Set, capped at 6 steps) -- defined once in tabs.jsx (loaded before app.jsx in ui-v2/Nullock.html) and consumed from both repeaterInspectorKV() (tabs.jsx) and InspectorTab's KV() (app.jsx:3464-3471), the only two Inspector-value KV renderers in the app. No backend touched; inspector_logic.cpp's urlDecode() (still one layer) is unrelated and unread by this change's own decode paths.","o":"partial","r":"Inspector decode-chain wave: a shared, gated auto-detect + per-step revisable decode chain (url/base64/html, up to 6 layers) is wired into every Inspector KV row in both the standalone INSPECTOR tab and Repeater's docked Inspector panel. Stays honestly partial -- it operates on parsed field values, not an arbitrary highlighted text selection in the raw editor, and covers only the three encodings this item names, not Burp's fuller decode-type list."},{"a":"repeater","f":"Inspector: \"Selection\" widget — character count and ASCII decimal/hex values for highlighted text, including non-printing characters","s":"present","i":"low","e":"days","g":"None functionally -- the docked Inspector panel (Repeater request/response panes and Proxy history/Site map DetailPane) now has a live Selection section: character count plus the first selected byte's decimal/hex value, with non-printing bytes labelled (\\n/\\t/\\r/space) instead of rendered invisibly. Honest remainder: Intruder's INSPECTOR/EDIT template-editor toggle does not yet track selection (no textarea selection listener wired there), so its Inspector panel always shows \"nothing selected\" -- a narrower surface than Repeater/Proxy, not a missing capability.","w":"Folded the existing per-pane selection readout (repeaterSelectionStats/repeaterDisplayChar, tabs.jsx) into RepeaterInspectorPanel itself as a permanent \"Selection\" section (rendered before the parsed-view content, so it shows even while parsing/erroring/empty) instead of a strip that vanished whenever the Inspector view-tab was active. Wired the same selection tracking into Proxy history/Site map's DetailPane (proxy.jsx), which previously had zero selection-aware code outside the codec bar's grab-whole-or-selected helper -- DetailPane gained reqSel/respSel state, onSelect/onMouseUp/onKeyUp handlers on both textareas, a bottom RepeaterSelectionReadout strip matching Repeater's UX, and sel passed into both RepeaterInspectorPanel calls.","v":"ui-v2/tabs.jsx RepeaterInspectorPanel (selectionSection, Section title=\"Selection\"); ui-v2/proxy.jsx DetailPane reqSel/respSel state + onReqSelect/onRespSelect + RepeaterInspectorPanel sel={reqSel|respSel} + RepeaterSelectionReadout in the non-inspector branches.","o":"present","r":"Docked the Selection widget inside the Inspector panel itself (Repeater + Proxy/Site-map DetailPane), matching Burp's Selection Info section rather than a separate bottom strip that disappeared when Inspector was the active view. Closes #362 partial -> present; Intruder's template-editor Inspector toggle still lacks selection tracking, called out honestly as a narrower remainder."},{"a":"repeater","f":"Inspector: HTTP/2 pseudo-header display and editing (:method, :path, :authority, :scheme) and HTTP/1↔HTTP/2 protocol toggle","s":"partial","i":"high","e":"weeks","g":"The DISPLAY half now ships: inspectRequest emits a pseudoHeaders array (:method from the request line, :path from the full target, :authority from the Host header, :scheme defaulting to https), reachable via /api/inspect. Still partial for the interactive half: EDITING a pseudo-header, the HTTP/1<->HTTP/2 protocol toggle, and actually EMITTING malformed h2 pseudo-headers on the wire (Repeater has no protocol field and writes HTTP/1 bytes) -- ui-v2 + a Repeater-h2 socket path outside headless verification.","w":"Pure addition to inspector_logic.cpp (out[\"pseudoHeaders\"]) mutation-proven in inspector_logic_test. Re-confirmed the DISPLAY half ships unchanged; held partial for the editing/toggle/emit legs, which remain blocked on both the Repeater HTTP/2 gap (#7, still absent) and the Inspector write-path gap (#9, still absent).","v":"Src/Core/Networking/inspector_logic.cpp:338 `out[\"pseudoHeaders\"] = QJsonArray{ nv(QStringLiteral(\":method\"), ...` through :343 (four pseudo-headers, line drift from the prior 158-162 citation which cited the start-line parse just above this block -- content and conclusion unchanged).","o":"","r":"Wave 0 register-accuracy audit: held at partial. The DISPLAY half is still there and unchanged: inspector_logic.cpp emits a pseudoHeaders array (:method/:path/:authority/:scheme) reachable via /api/inspect. The editing half is still absent -- Repeater has no protocol field (per item #7's re-verification) and the Inspector has no write path at all (per item #9's re-verification), so there is nothing to wire a pseudo-header edit into yet. No code change this pass."},{"a":"repeater","f":"Repeater / Comparer / Decoder / Inspector available in the native Qt desktop app","s":"partial","i":"low","e":"weeks","g":"The Qt Repeater is single-tab (no tab strip, no duplicate/rename) and its Send button bypasses the scope guard entirely (calls repeater.send() directly — see A7). There is still no Comparer/Decoder/Inspector in app.qml (tabs are Proxy/Scope/Repeater/Intercept/Intruder). And app.cpp:1163-1176 treats this window as optional legacy — 'The REAL UI is the browser control panel' — loading it only when the exe is launched from the repo root.","w":"Confirmed. Re-read Src/App/app.qml's tab bar: still five tabs (Proxy/Scope/Repeater/Intercept/Intruder), Comparer/Decoder/Inspector correctly reported absent there. The RepeaterHub/*.qml dead scaffolding finding from the prior pass is unaffected.","v":"Src/App/app.qml:110-114 `TabHeader { label: \"Proxy\"; ... root.currentTab = 0 }` through the Intruder tab at :114 -- five tabs total, no Comparer/Decoder/Inspector entry (line drift from the prior 112/657 citation, content unchanged).","o":"","r":"Wave 0 register-accuracy audit: held at partial. Src/App/app.qml's tab bar (:110-114) is still exactly Proxy/Scope/Repeater/Intercept/Intruder -- Comparer, Decoder and Inspector remain absent from the native desktop shell, unchanged. The working single-tab Repeater implementation in app.qml is unaffected by this pass. No code change this pass."},{"a":"repeater","f":"Extension access to Repeater / Comparer / Decoder / Inspector (Montoya API: sendToRepeater, registerContextMenuItem, custom message-editor tabs)","s":"partial","i":"medium","e":"weeks","g":"Extensions can now push a request into Repeater or Intruder (nullock.sendToRepeater / nullock.sendToIntruder, wired to the live tool objects) -- the most commonly used of the four integration points this item names. Still missing: registering a context-menu action, contributing a codec to the Decoder, and adding a custom message-editor tab -- the marketplace/install flow being built does not change this, since the missing piece is the hook surface, not distribution.","w":"Re-read the full extension API surface (extensions_api.hpp, all Q_INVOKABLE methods) instead of trusting the prior 'only traffic observation and finding reporting' summary. Found sendToRepeater/sendToIntruder are real, callable, and wired to the live tool objects -- confirmed by tracing setSendToRepeater's call site in app.cpp into an actual Repeater::addTabFromHistory-style path. Fresh grep for registerContextMenuItem/messageEditor/registerCodec/registerDecoder across the same file: zero hits, so those three integration points are still absent.","v":"extensions_api.hpp:351 `Q_INVOKABLE void sendToRepeater(const QString &host, int port, bool tls, const QString &requestText);` and :353 sendToIntruder (same signature); extensions_api.cpp:127-143 both implementations call through m_owner->m_sendToRepeater / m_sendToIntruder (optional callbacks) and log `[ext] sendToRepeater host:port`; Src/App/app.cpp:1220 `// nullock.sendToRepeater / sendToIntruder: extensions push a request into the` wires both via setSendToRepeater/setSendToIntruder to the real Repeater/Intruder instances. `grep -n 'registerContextMenuItem|messageEditor|registerCodec|registerDecoder' extensions_api.hpp` = 0 hits -- context-menu registration and custom-editor/codec contribution remain unimplemented.","o":"absent","r":"Wave 0 register-accuracy audit: UPGRADED absent -> partial. The prior audit's 'only hooks are traffic observation and finding reporting' claim is now stale: Q_INVOKABLE sendToRepeater(host,port,tls,requestText) and sendToIntruder(...) exist on the JS bridge (extensions_api.hpp:351,353; implemented extensions_api.cpp:127-143) and are wired live in app.cpp:1220 via setSendToRepeater/setSendToIntruder callbacks into the real Repeater and Intruder objects -- an extension really can push a captured request into either tool today. Still genuinely absent: registerContextMenuItem (no context-menu registration hook anywhere on the bridge) and custom message-editor tabs / Decoder codec contribution (no editor-provider or codec-registration method exists). 1 of the 4 named integration points now real; the other 3 remain absent."},{"a":"target","f":"Site map tree roots keyed by protocol://host:port (http://x.com:80 and https://x.com:443 are separate branches)","s":"partial","i":"medium","e":"days","g":"Closed for the ui-v2 web UI, still absent for the native Qt desktop app. ui-v2/proxy.jsx's SiteMap tree now groups by scheme+host+port (derived client-side from NL.rows, which already carries host/port/tls per request), so an app on :443 and an admin panel on :8443 render as two distinct nodes with correct per-node counts and non-OR'd TLS flags, and clicking a node scopes the history table to that exact origin. The Qt desktop app's own Site Map list (Src/App/app.qml:159-167, bound directly to the siteMap C++ model) is unchanged: SiteMapModel's Entry struct still has no port field and still ORs TLS across every request to a host -- that half needs a backend model change this cloud session can't build.","w":"Re-verified against live source after the ui-v2 fix. site_map_model.hpp/.cpp genuinely still has Entry {host,count,anyTls} with no port/scheme (unchanged from the prior audit) -- app.qml's Site Map list binds this model directly, so the desktop half of the gap is fully unchanged. ui-v2/proxy.jsx no longer reads NL.sitemap (the host-only /api/snapshot block fed by that same model) for its tree at all; it derives origin-keyed entries from rows instead, same technique already proven for leaf derivation (#370, same file).","v":"Src/FrontEnd/GUI/Models/Proxy/site_map_model.hpp:40-44 `struct Entry { QString host; int count = 0; bool anyTls = false; };` -- no port, no scheme, unchanged. Src/App/app.qml:159-167 binds `model: siteMap` directly, unchanged. ui-v2/proxy.jsx's ProxyTab now computes `sitemapEntries` via `React.useMemo` over `rows`, keyed by `(tls?\"https\":\"http\")+\"://\"+r.host+\":\"+port` (r.port/r.tls per row: control_server.cpp:1481/1488/1491), and `SiteMap` renders `e.origin` (default port omitted, mirroring the SSRF-probe origin-builder at control_server.cpp:2275-2278) as the tree label.","o":"partial","r":"ui-v2/proxy.jsx's SiteMap tree roots and leaf lookup now key on scheme+host+port derived client-side from NL.rows, instead of the backend's host-only NL.sitemap block -- closes the merged-node/OR'd-TLS half of the gap absent -> partial for the web UI; the Qt desktop app's own Site Map (bound to the same host-only SiteMapModel) is unchanged and still needs the backend model change, called out honestly. Selecting a tree node now filters the history table by exact origin (host+port+tls), not just a host substring."},{"a":"target","f":"Site map auto-populates from proxied traffic in real time","s":"present","i":"low","e":"hours","g":"","w":"Held. Every link in the chain verified end to end; the only correction is the file path (control_server.cpp lives at Src/BackEnd/Control/, not Src/App/).","v":"Src/FrontEnd/GUI/Models/Proxy/site_map_model.cpp:9-12 `connect(m_source, &QAbstractItemModel::rowsInserted, this, &SiteMapModel::onSourceRowsInserted); connect(m_source, &QAbstractItemModel::modelReset, this, &SiteMapModel::onSourceModelReset);`. Incremental update at :79-100 `onSourceRowsInserted`: existing host -> `m_entries[existing].count++` + `emit dataChanged(changed, changed, { CountRole, TlsRole })`; new host -> `beginInsertRows`/`endInsertRows`. control_server.cpp lives at Src/BackEnd/Control/control_server.cpp (not Src/App/).","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers/paths that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"target","f":"Site map populates from the crawler / automated crawl","s":"present","i":"medium","e":"hours","g":"None — a DISCOVER tab now exposes seed input + START/STOP CRAWL, hitting /api/crawler/start and /api/crawler/stop. Crawled pages stream into Proxy history via the existing entryLoaded wiring, same as before. (Host-granularity of the site-map display is tracked separately as item 366.)","w":"Closed 2026-08-08: the crawler engine + control endpoints were already wired end to end; only the UI trigger was missing. Added NL.actions.crawlerStart/crawlerStop in real-data.js and a start/stop control in the new DISCOVER tab. Verified via bundled-babel transform; field contract (ok/error) matched against control_server.cpp:4002-4015.","v":"DiscoverTab (ui-v2/app.jsx) calls NL.actions.crawlerStart(seed) -> POST /api/crawler/start, and crawlerStop() -> POST /api/crawler/stop; crawled pages land in Proxy history via the pre-existing Crawler::entryLoaded -> ProxyModel wiring (Src/App/app.cpp:941-946).","o":"partial","r":"DISCOVER tab adds a start/stop crawl control."},{"a":"target","f":"Site map contents table columns: Host, Method, URL, Params, Status, Length, MIME type, Title, Comment, TLS, IP, Cookies, Time","s":"partial","i":"medium","e":"days","g":"No Comment or Cookies column. Columns are still hardcoded -- no show/hide, no reorder, no click-to-sort, no copy-column. (A client-side highlight-colour + free-text-comment annotation layer exists -- right-click a row, see parity item #299 -- which covers part of the practical intent of a Comment column, but it is a row overlay, not an actual sortable/reorderable table column, so that part of the gap still stands.)","w":"Narrowed 2026-09-01: Title and Extension, the two parseable/derivable columns named in the feature title, are now real table columns. Comment-as-column, Cookies-as-column, and show/hide/reorder/sort/copy-column remain absent.","v":"ui-v2/proxy.jsx HistoryTable colgroup/thead now render 14 cells (was 12): the leading blank marker, `#, Method, Status, Host, Path, Title, Params, Ext, Mime, Size, Time, IP, Captured`. Title reads a new `row[\"title\"]` field control_server.cpp's buildSnapshot() emits by regex-matching `<title>` out of the DECODED response body (bodyForInspection(), capped to the first 16 KB so a large body isn't fully scanned); Ext reuses the existing client-side `pathExtension()` helper already used by the EXT filter. Comment/Cookies columns and click-to-sort/show-hide/reorder/copy-column are still absent -- no `onClick` on any `<th>`, TLS still a dot inside the Host cell not its own column.","o":"partial","r":"Closed the Title and Extension halves of this gap: control_server.cpp's buildSnapshot() now parses a response's <title> tag (decoded body, 16 KB cap, first match) into a new `title` row field; ui-v2/proxy.jsx's HistoryTable gained Title and Ext columns (Ext via the existing pathExtension() helper). Comment-as-column, Cookies-as-column, and show/hide/reorder/sort/copy-column remain -- state held at partial, gap text narrowed rather than closed. CI confirmed green on 692664f (all 8 ci.yml jobs, including build-windows' full regression-test suite and build-linux/build-macos): https://github.com/Bikebrainz/Nullock/actions/runs/33526543362."},{"a":"target","f":"Site map: view full request/response for the selected item, with the message editor (Pretty/Raw/Hex, Inspector)","s":"present","i":"medium","e":"days","g":"None -- Inspector is docked live in the message editor, the preview tab pretty-prints XML/HTML/JSON, and Site map hosts now expand into per-URL leaf nodes (proxy.jsx SiteMap, deduped by method+path off the HTTP history rows already in state, most-recent-id wins) that jump straight to that message editor -- the last gap (host-only tree, no leaf to click) is closed.","w":"Re-verified against live source. The prior remaining gap was real: SiteMap (proxy.jsx) rendered one row per HOST from NL.sitemap ({host,count,tls} only -- control_server.cpp:1446-1459 has no per-path field), so a specific message could only be reached via the HTTP history table below, not clicked off the map. Closed client-side without a backend change: the HTTP history rows already in ProxyTab state (state.rows) carry host/method/path/status/id, so a per-host twisty now derives unique method+path leaves from those rows (leavesFor(), dedupes by method+path keeping the highest-id/most-recent row), rendered as a new .sm-leaf row list under each expanded host; clicking a leaf dispatches both selectedHost and selectedRowId, opening that exact message in DetailPane the same way clicking its row in HistoryTable would.","v":"ui-v2/proxy.jsx SiteMap() (leavesFor, .sm-twisty expand toggle, .sm-leaf rows) reads r.host/r.method/r.path/r.status/r.id off the rows prop -- the same row shape already read by HistoryTable/FilterBar elsewhere in this file (e.g. r.path at proxy.jsx:80/159/2225, r.status at :2212), so no field is invented. ui-v2/styles.css .sm-twisty/.sm-leaf/.sm-leaf-method/.sm-leaf-path/.sm-leaf-status rules. ProxyTab passes rows/selectedRowId/onSelectLeaf into <SiteMap>, dispatching {selectedHost, selectedRowId} on leaf click.","o":"","r":"Site map leaf-node wave: hosts in the Site Map tree now expand (twisty toggle) into a deduped per-URL leaf list derived client-side from the HTTP history rows already in state -- no backend change, since /api/snapshot sitemap stays host-only. Clicking a leaf selects that exact message the same way a history-table row click does. This was the sole remaining real gap on this item (map has no per-URL leaf nodes); state moves partial -> present. Verified via bundled-babel transform of ui-v2/proxy.jsx, a Node functional test of the leaf-dedupe logic (5 checks: method+path grouping, highest-id-wins on duplicate paths, distinct-method leaves, host filtering, empty-host fallback) plus a vm-sandboxed render smoke test of SiteMap in both collapsed and expanded states proving the new JSX branch does not throw, and confirmation ui-v2/tabs.jsx was untouched."},{"a":"target","f":"Site map filter — by MIME type (HTML/Script/XML/CSS/Other text/Images/Flash/Other binary), by status code family, by file extension (show only / hide), by search term (regex, case-sensitive, negative), by annotation (commented / highlighted)","s":"present","i":"medium","e":"days","g":"Case sensitivity applies to local column/free-text matching; the server regex body-search path remains case-insensitive. Annotation filtering now uses project-persisted, cross-client notes.","w":"Register correction (2026-08-19, 6dcc404): downgraded present -> partial because the annotation criterion this feature's own name enumerates was confirmed absent. Re-verified 2026-08-21: c25af6a (2026-08-20) shipped client-side highlight-colour + comment annotations with an ANNOTATED filter chip shared by FilterBar, and SiteMap (ui-v2/proxy.jsx:361-397) filters its leaf list on the same annotatedOnly/annotations props HistoryTable uses (:397 `return annotatedOnly ? leaves.filter(r => annotations && annotations[r.id]) : leaves;`) and renders the same coloured row edge (:435-437). All five enumerated criteria are now genuinely present at the surface, matching how this file grades #267's identical situation -- present, with the client-side-only caveat carried in the gap text rather than blocking the whole item. Updated 2026-09-11: 63ecda0e closes the browser-local annotation limitation with project storage and a revisioned read/patch API.","v":"ui-v2/proxy.jsx:361 SiteMap signature takes annotations/annotatedOnly; :397 leaf-list filter on annotatedOnly; :435-437 row highlight from annotationColorHex(note.color); :332 FilterBar's ANNOTATED chip feeds the same state into both HistoryTable and SiteMap (ProxyTab :2497,:2520-2521). mimeCategory()/pathExtension()/parseExtList()/extFilterMatch()/parseSearchTerm() remain the same pure helpers shared with HTTP history.","o":"present","r":"Annotation persistence caveat removed; unrelated filtering gaps remain documented."},{"a":"target","f":"Site map item actions: \"Delete host\"/\"Delete branch\", \"Save selected items\" (Burp XML), \"Copy URLs\", \"Copy links\", \"Report issues for selected branch\"","s":"present","i":"medium","e":"days","g":"None -- Delete host / Delete branch, Save selected items (Burp-site-map-shaped XML), Copy URLs, Copy links, and now Report issues for selected branch all exist in the Site map right-click menu, scoped identically (single row / directory branch / whole host).","w":"Closed the final \"Report issues for selected branch\" leg. window.NL.findings -- the same live array the ISSUES tab renders -- is filtered client-side to the ctx-menu's host/branch/single-row scope (by URL pathname prefix, not an exact-string match against the independently-built ctxMenuTargetUrls(), since a finding's url and a re-derived history-row url can format the query string differently) and rendered into a standalone, self-escaped HTML report via the same Blob+<a download> pattern Save selected items already uses. No backend endpoint needed -- findings are already fully loaded on the page. All five item-actions this parity item names are now built, so it moves partial -> present.","v":"ui-v2/proxy.jsx: urlPathname()/findingsForScope() (pure path-prefix scoping, new), buildBranchIssuesHtml() (pure HTML-escaped report builder, new), ProxyTab's reportCtxMenuIssues() handler and a new 📋 REPORT ISSUES entry in the ctxMenu JSX (beside 💾 SAVE SELECTED ITEMS). Verified with a sandboxed functional test: whole-host/branch/single-row scoping (including a sibling-prefix false-positive check, /apix vs /api), an unparseable finding.url is skipped rather than throwing, severity sort order in the rendered table, and an XSS payload in a finding's url/summary/evidence is HTML-escaped (quotes too, since the url lands in an href attribute) rather than reaching the downloaded HTML unescaped.","o":"present","r":"Wave 2 Site-map batch, final leg -- \"Report issues for selected branch\" added to the Site map right-click menu as a client-side HTML export of window.NL.findings scoped to the clicked host/branch/row (path-prefix match), reusing the existing findings data with no backend change. Closes the last open leg of this item: partial -> present."},{"a":"target","f":"Compare site maps (wizard: pick two maps or two sessions, choose which requests to compare, diff both content and issues, colour-coded result table)","s":"partial","i":"medium","e":"weeks","g":"Narrowed, not closed: a COMPARE HOSTS overlay in the Proxy tab's Site map pane now diffs the URL-path surface and the findings of two HOSTS already captured in HTTP history (client-side, no backend endpoint), split into only-A / common / only-B panes for both dimensions the item names. Still genuinely missing: no wizard to pick arbitrary saved site maps or sessions (Nullock has neither concept -- only \"two hosts seen in this engagement's history\" is comparable), no session/role dimension beyond whatever two hosts the user already captured under, and the content diff is URL-path presence only -- it does not diff request/response bytes the way a true site-map content-differ would.","w":"Re-derived against live source after the earlier register note flagged this as the item most overstated by the pre-existing baseline UI: the \"Scan-to-scan issue delta\" feature (this file's own separate \"present\" item) already has a Save/Diff/Clear baseline UI in ui-v2/app.jsx's IssuesTab (doBaselineSave/doBaselineDiff/doBaselineClear, confirmed live -- the old \"no UI caller at all\" claim about /api/baseline/* here was stale), but that is the SAME-host scan-to-scan delta, not a two-map/two-host compare, so it does not touch this item. This wave built the actual two-host comparator instead: CompareHostsOverlay (ui-v2/proxy.jsx) computes hostUrlPaths/diffHostSurfaces over rows already in state (no endpoint needed, matching the Target Analyzer/Site map tree precedent) and diffHostFindings over the existing global NL.findings array, keyed by kind+path+summary (path normalized via stripUrlOrigin so a bare-path vs full-URL finding still matches) -- the same identity-key shape control_server.cpp's own baseline/diff handler uses, just scoped to two hosts instead of two points in time for the same host. Left honestly partial: still no map/session picker, no content-byte diff, no single colour-coded result table (two side-by-side panes instead).","v":"ui-v2/proxy.jsx: hostUrlPaths/diffHostSurfaces/stripUrlOrigin/diffHostFindings (pure helpers) + CompareHostsOverlay (the panel: HOST A / HOST B selects populated from Array.from(new Set(rows.map(r => r.host))), a URL PATHS pane pair and a FINDINGS pane pair, each only-A/common/only-B). ProxyTab's pane-head gains a COMPARE HOSTS button (disabled below two distinct hosts) beside ANALYZE TARGET. Findings read from the existing global NL.findings (ui-v2/real-data.js:36 `NL.findings = snap.findings || []`), same field shape (kind/host/url/summary/severity) IssuesTab already reads. No backend touched.","o":"partial","r":"Compare-hosts wave: stub -> partial. Added a client-side COMPARE HOSTS overlay (ui-v2/proxy.jsx) diffing URL paths and findings between two hosts already in HTTP history. Honest remaining gap: no arbitrary map/session picker, no request/response content diff, findings-only + path-only surface."},{"a":"target","f":"Target > Scope: include-list of URL-matching rules","s":"partial","i":"high","e":"days","g":"The rule is a glob over the HOST STRING only. `https://example.com/app/` as a scope entry matches nothing (the anchored regex would need the literal string to BE the Host header). Path-scoped engagements ('only /shop, not /blog') cannot be expressed, and since scope gates every active tool (item 15), the coarseness propagates everywhere. A separate 'Advanced scope control' feature now provides the missing path/protocol/port dimension as a composed extra layer (its own parity item, partial, UI-wired in the SCOPE tab) -- so the practical path-scoping need this item names IS now addressable in the product, just not through the simple include-list this item is titled after.","w":"Held exactly. Re-read the compiler and the matcher; the quoted code is verbatim correct.","v":"Src/BackEnd/Proxy/proxy_server.cpp:1501-1514 `void ProxyServer::setScope(...) { auto compile = [](const QStringList &globs) { ... QString pattern = QRegularExpression::escape(g); pattern.replace(\"\\\\*\", \".*\"); out.append(QRegularExpression(\"^\" + pattern + \"$\", QRegularExpression::CaseInsensitiveOption)); ...`. globVerdict() (:1527-1538) matches this compiled list against a bare `host` string only -- no path/scheme/port parameter anywhere in this layer. A separate, newer layer now exists alongside it: Src/BackEnd/Proxy/scope_logic.hpp's AdvancedScopeRule/CompiledRule (protocol + host-regex + port-range + file-regex, composed on top of the simple list via ScopeLogic::urlInScope) -- tracked and UI-wired under its own parity item 'Advanced scope control...' (partial, ~10 non-proxy tool gates still host-only). This item's own subject, the SIMPLE include/exclude list, is unchanged: still a bare host glob with no path dimension.","o":"partial","r":"Wave 0 register-accuracy audit: held at partial. Re-read setScope/globVerdict -- the simple include-list this item names is still a bare host-glob with no path dimension, exactly as originally graded (line numbers refreshed, :1312-1338 drifted to :1501-1538). Cross-referenced the sibling 'Advanced scope control' parity item, which since this item was last touched grew a full editor UI and now supplies the path/protocol/port dimension this item's gap complains is missing -- added a pointer so the gap text does not read as if no progress happened anywhere in scope-land. No code change this pass."},{"a":"target","f":"Target > Scope: exclude-list, with exclude taking precedence over include","s":"present","i":"low","e":"hours","g":"Same host-only matching limitation as the include list.","w":"Held. Precedence, persistence and mutators all verified verbatim.","v":"Src/BackEnd/Proxy/proxy_server.cpp:1530-1539 `globVerdict()` -- `globOut = false; for (const auto &rx : outOfScope) if (rx.match(host).hasMatch()) { globOut = true; break; } ...`, consumed by `isInScope`/`isUrlInScope` (proxy_server.cpp:1542-1567) as `return !globOut && globIn;` -- out-of-scope still wins unconditionally. Persisted at Src/Core/Storage/project_store.cpp:368-371 `QJsonArray outS; for (const QString &s : m_meta.outOfScope) outS.append(s); ... o[\"outOfScope\"] = outS;`. Mutators at project_store.cpp addOutOfScope/removeOutOfScope emit scopeChanged (e.g. :519-521).","o":"","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add. Noted for context (no item change): a separate 'advanced scope' layer (protocol/host/port/file regex, ScopeLogic::CompiledRule) has since been added on top of this simple host-glob layer; it is tracked by its own backlog item ('Advanced scope control...', partial) and does not change this item's host-only gap, which is specifically about the simple glob layer this item describes."},{"a":"target","f":"Scope UI actions: Add / Edit / Remove / Paste URL / Load (from file) on both tables","s":"present","i":"medium","e":"hours","g":"None -- the two scope columns (tabs.jsx ScopeColumn) now support Edit (click a glob to load it, Save does remove-then-re-add), Paste-URL (a URL->HOST button converts a pasted URL into its hostname via new URL()), and Load-from-file (a hidden <input type=file> reads newline-delimited globs and adds each).","w":"Closed 2026-08-09: ScopeTab's two columns were previously Add-only (a text input + ADD button + per-row remove). Replaced with a shared ScopeColumn component adding click-to-edit, a URL->HOST conversion helper (urlToScopeGlob), and a file-load path, all dispatching through the existing scope-add-in/out and scope-remove-in/out reducer actions -- no backend change needed since /api/scope/in|out/add|remove already existed.","v":"ui-v2/tabs.jsx ScopeColumn (commit): click-to-edit via editIndex state + commit() remove-then-add; urlToScopeGlob() parses pasted text via `new URL()`; loadFile() reads a hidden file input via FileReader.readAsText and dispatches one scope-add-* per non-empty line.","o":"absent","r":"Wave 2 Target/Scope batch -- Scope UI actions: Add / Edit / Remove / Paste URL / Load (from file) on both tables closed (absent -> present), frontend-only, no backend change."},{"a":"target","f":"Out-of-scope handling: Burp logs everything by default and prompts \"stop sending out-of-scope items to history?\"; the proxy can optionally restrict logging/interception to in-scope items","s":"present","i":"high","e":"hours","g":"None left -- the at-the-moment 'stop sending out-of-scope items to history?' prompt is now built. ProxyTab (ui-v2/proxy.jsx) shows a dismissible banner above HTTP history the first time out-of-scope traffic is actually landing in history (a scope is defined AND logOutOfScope is on AND a visible row falls outside it), offering 'Yes, stop logging out-of-scope' (dispatches the existing log-out-of-scope-toggle action, same one the SCOPE tab checkbox uses) or 'No, keep logging everything'. Either choice dismisses it for the browser session (sessionStorage), matching Burp's one-time nudge rather than re-prompting on every render.","w":"Held. All five gate sites verified verbatim, including the two Match&Replace gates the first pass cited. Partial is the right call: Burp's restricted mode is what Nullock always does, so half the feature is present -- just not optional and not the default Burp ships.","v":"proxy_server.cpp:264-266 `const bool inScope = m_server->isInScope(req.host); if (inScope) emit m_server->requestReceived(req); else m_server->noteFiltered();` and cpp:305 `if (inScope) emit m_server->responseReceived(req, resp);`. CONNECT never MITMs off-scope: cpp:324-334 `// Out-of-scope hosts: never MITM, never log. Just keep their TLS opaque ... if (inScope && sslClient && ca && ca->hasOpenss","o":"present","r":"Closes the last remaining gap on this item (the prompt itself; the per-row marker and per-project persistence of the toggle were already closed in prior waves). Pure frontend: a client-side banner in ProxyTab (ui-v2/proxy.jsx) computed from state already in the reducer (scope, logOutOfScope, history rows) -- no backend change, no C++ build needed to verify. Verified by: babel transform of proxy.jsx succeeding, and a standalone functional test of the extracted hostInScope/loadOosPromptDismissed/saveOosPromptDismissed logic (in-scope/out-of-scope/wildcard host matching, and sessionStorage dismissal round-trip) against a stub window.sessionStorage, all passing."},{"a":"target","f":"Scope persists in the project file and reloads with the project","s":"present","i":"low","e":"hours","g":"No standalone scope import/export separate from the project file.","w":"Held. Verified both the write and the read-back path, which the first pass only half-cited.","v":"Write: Src/Core/Storage/project_store.cpp:368-371 `QJsonArray inS; for (const QString &s : m_meta.inScope) inS.append(s); QJsonArray outS; for (const QString &s : m_meta.outOfScope) outS.append(s); o[\"inScope\"] = inS; o[\"outOfScope\"] = outS;`. Read: project_store.cpp:264-269 `m_meta.inScope.clear(); for (const QJsonValue &v : o.value(\"inScope\").toArray()) m_meta.inScope.append(v.toString()); m_meta.outOfScope.clear(); for (...) m_meta.outOfScope.append(...)`.","o":"","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"target","f":"Scope is live — edits take effect immediately across the running tools without a restart","s":"present","i":"low","e":"hours","g":"","w":"Held. Confirmed both the initial seed and the live reconnect, plus the mutex pairing that makes it safe on the request hot path.","v":"Src/App/app.cpp:768-771 `proxy.setScope(projectStore.metadata().inScope, projectStore.metadata().outOfScope); QObject::connect(&projectStore, &Nullock::Core::ProjectStore::scopeChanged, &proxy, &Nullock::Proxy::ProxyServer::setScope);`. Mutex-guarded on the hot path: proxy_server.cpp:1513 `QMutexLocker lock(&m_scopeMutex);` inside `setScope` (1501-1516), matched by the same lock inside `isInScope` (proxy_server.cpp:1546) and `isUrlInScope` (:1561).","o":"","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"target","f":"Scope drives tool behaviour (proxy logging/interception, live audit, redirect-following in Repeater/Intruder)","s":"exceeds","i":"low","e":"hours","g":"Burp lets you fire Repeater at anything; Nullock refuses. Safer posture, at the cost that the coarse host-only matcher (item 9) is what gates all of it -- an over-broad glob over-permits, a narrow one blocks the whole host.","w":"Held, and it is stronger than the first pass described. Beyond the 11 explicit blocksScope() call sites (re-verified 2026-08-25 -- the prior pass's count of 13 included the function definition and a comment mention) there is a declarative kActivePaths set that auto-gates ~40 active endpoints before their handler even runs, so a newly added probe endpoint is scope-gated by listing it rather than by remembering to call the guard.","v":"control_server.cpp:1241 `bool ControlServer::blocksScope(const QString &host) const` ; 11 explicit call sites (3218, 3506, 3831, 3982, 5135, 7648, 7673, 9998, 10178, 10180, 10312 -- corrected from the prior pass's '13', which counted the definition and a comment mention alongside the real call sites) plus the declarative kActivePaths set (control_server.cpp:3198-3212, ~40 active endpoints) that scope-gates a probe endpoint by listing it rather than by remembering to call the guard. Repeater: control_server.cpp:3506 `if (m_wiring.repeater && blocksScope(m_wiring.repeater->host()))`.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"target","f":"Per-issue definition content: Issue background, Remediation background, Vulnerability classifications (CWE), Typical severity, References","s":"partial","i":"medium","e":"weeks","g":"Backend enrichment (finding_enricher.cpp Mapping struct) carries only a one-line `fix` string alongside cwe/owasp/cvssScore/cvssVector/compliance -- there is no Issue-background prose, no separate Remediation-background prose, no References list, and no typical-severity field distinct from a finding's own instance severity. That remains a genuine backend data-model gap (a C++ struct change this cloud session cannot build/verify).","w":"Re-verified against live source (2026-08-20) and CORRECTED: the prior why-text's two 'UI' claims are both stale/false. (1) 'no ui-v2 surface renders it' is wrong -- ui-v2/app.jsx's IssueDetailBody (1262-1295) is mounted in the ISSUES tab (each finding row has a click-to-toggle ADVISORY/REQUEST/RESPONSE detail pane, toggleDetail/detailOpenId at 1426-1429, rendered 1725-1758) and shows CWE/OWASP/CVSS(+vector)/Confidence/Compliance/Fix straight off the finding object -- exactly the fields FindingEnricher attaches. (2) 'the report endpoint that does has no button' is wrong -- REPORTING tab's 'Download HTML' button (app.jsx:4424) already calls NL.actions.reportHtml() -> POST /api/report/html. Both false negatives removed; state correctly stays partial for the real remaining gap only (no background/remediation prose, no References, no typical-severity field -- all backend data-model additions, not UI wiring).","v":"ui-v2/app.jsx:1262-1295 IssueDetailBody renders CWE/OWASP/CVSS+vector/Confidence/Compliance/Fix from `finding`; :1426-1429 detailOpenId/toggleDetail state; :1658 row onClick=toggleDetail(f); :1725-1758 ADVISORY/REQUEST/RESPONSE tab bar + mounted <IssueDetailBody>; :4424 REPORTING tab 'Download HTML' button -> NL.actions.reportHtml() -> POST /api/report/html. Backend fields match exactly: control_server.cpp:1371-1377 fo[\"cwe\"]/fo[\"owasp\"]/fo[\"cvssScore\"]/fo[\"cvssVector\"]/fo[\"compliance\"]/fo[\"fixSummary\"]/fo[\"confidence\"] in the /api/snapshot findings array. Remaining real gap confirmed absent: Src/Core/Networking/finding_enricher.cpp:9-16 struct Mapping has only {cwe,owasp,cvssScore,cvssVector,compliance,fix} -- no background/remediation/references/typicalSeverity fields anywhere in the 490-line table.","o":"partial","r":"Register-accuracy fix: the 'no ui-v2 surface' and 'report button missing' claims were both stale -- IssueDetailBody (ISSUES tab) and the REPORTING tab's Download HTML button already existed. Gap narrowed to the true remaining backend-only piece (Issue/Remediation background prose, References, typical-severity field) -- no code changed, state stays partial."},{"a":"target","f":"Extension-defined custom issues that appear in the site map alongside built-in issues","s":"partial","i":"low","e":"days","g":"They land in the same flat list, so 'alongside built-in issues in the site map' is unreachable -- there is no site-map issue view. (The dead click on rowId-0 findings the prior audit flagged as an extra defect has since been fixed -- see the Issues detail pane's rowId guard.)","w":"Held, with one extra defect found: extension findings are reported with rowId 0, and the Issues list makes every row click-to-jump, so clicking an extension finding navigates to a nonexistent row #000.","v":"Src/App/app.cpp:834-836 `// Let JS extensions emit findings into the same panel via nullock.reportFinding(). Without this they fall back to the ext log.` / `extensions.setScanner(&scanner);`. Bridge at Src/Core/APIs/ExtensionsAPI/extensions_api.cpp:108-124: `ExtensionsApiBridge::reportFinding(...)` calls `scanner->reportFinding(0, severity, kind, summary, evidence, host, url)` -- rowId 0 for every extension finding, landing in the same flat Issues list as built-in findings (no site-map issue view exists to appear 'alongside' anything in). The dead-click defect the prior pass flagged (clicking a rowId-0 finding tried to jump to a nonexistent row) is FIXED since then: ui-v2/app.jsx:1733 `if (!finding.rowId) { return (<div ...>no associated request — this finding has no underlying HTTP transaction (extension-sourced)<\/div>);}` and app.jsx:2420-2421 disables the 'Open in proxy' button (`disabled={!f.rowId}`) with the title 'No associated request (extension finding)' -- clicking an extension finding today shows a clear message instead of misnavigating.","o":"partial","r":"Wave 0 register-accuracy audit: held at partial, core gap unchanged (no site-map issue view exists for anything to appear 'alongside' in). Found a genuine improvement the register hadn't caught: the dead-click-on-rowId-0 defect this item's own 'why' used to cite as an extra bug is fixed -- app.jsx now guards `!finding.rowId` in both the detail pane and the 'Open in proxy' button, showing an honest 'no associated request (extension-sourced)' message instead of a broken jump. Updated gap/evidence to drop the stale defect claim and refreshed drifted line numbers (app.cpp 726-728 -> 834-836; extensions_api.cpp 61-78 -> 108-124). No code change this pass."},{"a":"target","f":"Engagement tools > Discover content: the content-discovery engine with its own session window, live status, and pause/resume","s":"partial","i":"medium","e":"days","g":"No session object, no live progress, no pause/resume/stop. A 2000-word run blocks the control API for the whole duration with zero feedback.","w":"Held. Confirmed the handler runs discover() to completion inline and returns -- one synchronous POST, no session object. Correcting the line numbers: the handler is at control_server.cpp:8447-8492, not 8306-8352.","v":"Engine: Src/Core/Networking/content_discovery.cpp:96 `const QString base = normBase(req.basePath);` and its Request struct now has concurrency/throttleMs/extensions/mutations fields (pool-based fan-out was added since the prior pass), but that is all still internal to one synchronous call. Handler control_server.cpp:9663-9705 `if (path == \"/api/content/discover\") { ... const auto cres = Nullock::Core::ContentDiscovery::discover(cr); ... }` -- one blocking POST that runs the whole probe pool to completion on the control-server thread and returns; no session object, no progress endpoint, no start/stop/pause/resume pair anywhere in this handler or file (confirmed by re-grepping the file for a second content/discover-prefixed route -- there is none).","o":"partial","r":"Wave 0 register-accuracy audit: held at partial. Re-read the handler (moved 8447-8492 -> 9663-9705 across intervening waves) -- still one synchronous discover() call with no session/progress/pause-resume surface. Noted the engine gained an internal concurrency pool (concurrency/throttleMs) and extension/mutation wordlist variants since the prior pass, but neither changes the blocking, session-less shape this item grades on. No code change this pass."},{"a":"target","f":"Content discovery config: built-in short/long wordlists, custom wordlist file, \"derive words from site map / response bodies\", case-sensitivity handling","s":"partial","i":"medium","e":"days","g":"Custom wordlist paste + load-from-file now exist in the DiscoverTab config panel (feeds the existing per-call wordlist override). Still no short/long built-in choice (only the one 126-word default), no derivation from observed site-map paths or response bodies (Burp's single most productive discovery source), and no case-variation -- all unbuilt on the backend, not just missing UI.","w":"Partially closed by this wave: the 'custom wordlist file' ask is now real (FileReader-backed load button, same pattern as Sequencer's manual-load). The remaining asks (short/long presets, derive-from-observed-traffic, case-sensitivity) need new backend logic this cloud session cannot build/verify, so the item stays partial rather than present.","v":"ui-v2/app.jsx DiscoverTab wordlistText state + loadWordlistFile (FileReader.readAsText, mirrors SequencerTab's loadFile) + a paste textarea, both feeding NL.actions.discoverContent opts.wordlist -> control_server.cpp:9094-9095 cr.wordlist array override of ContentDiscovery::defaultWordlist().","o":"partial","r":"Discovery config wave: wordlist paste + load-from-file added to DiscoverTab, closing the custom-wordlist-file half of this item. Built-in short/long presets, derive-from-sitemap/response-bodies, and case-sensitivity handling remain open backend gaps."},{"a":"target","f":"Content discovery: thread count / concurrency and request throttling controls","s":"present","i":"high","e":"days","g":"None -- concurrency (1-64) and throttle-ms (0-60000) fields in the DiscoverTab config panel POST straight to /api/content/discover's existing concurrency/throttleMs fields.","w":"The backend dials (631088c) had no GUI caller until this wave; DiscoverTab's new Discovery config panel adds both number inputs, closing the GUI-reachability gap.","v":"ui-v2/app.jsx DiscoverTab discConcurrency/discThrottleMs state -> NL.actions.discoverContent(url, max, {concurrency, throttleMs}) -> control_server.cpp:9090-9093 clamp+set on ContentDiscovery::Request.","o":"present","r":"Discovery config wave: concurrency + throttle-ms inputs added to DiscoverTab, the remaining ui-v2 follow-on flagged in the 631088c reconciled note."},{"a":"target","f":"Content discovery: 404 / soft-404 detection so a catch-all server doesn't report the whole wordlist","s":"exceeds","i":"low","e":"hours","g":"","w":"Held -- this one survives adversarial reading intact. All three defences are real, and the corroboration discipline (trust the fingerprint only when two independently-random probes canonicalise identically) is genuinely beyond what Burp documents. Tests/content_discovery exists in the test tree.","v":"Same-depth twin calibration: Src/Core/Networking/content_discovery.cpp:125-141 `const QString t1 = base + \"/\" + randToken(); ... const QString t2 = base + \"/\" + randToken(); ... cal.reliable = (s1 == s2); // corroborated only if they agree` with `cal.jitter = std::max(64, std::abs(l1 - l2) * 2);` (:145). Path-masked fingerprint trusted only on agreement, surfaced as `result.calibrationReliable`/`softNotFoundStatus`/`softNotFoundIs200` (:159-162). Tests/scope_logic and content-discovery coverage remain in the test tree.","o":"","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"target","f":"Engagement tools > Generate CSRF PoC","s":"present","i":"medium","e":"hours","g":"None -- same DetailPane button as #224 (Proxy/Target share one component). Preview is text-only (no in-app render of the auto-submitting form, by design -- rendering it would fire the request).","w":"Closed 2026-08-09: same fix as #224 -- DetailPane is shared between the Proxy history table and the Site map (both areas of ui-v2/proxy.jsx's ProxyTab), so the new CSRF POC button reaches both.","v":"ui-v2/proxy.jsx DetailPane (used by both SiteMap row selection and HTTP history row selection in ProxyTab); control_server.cpp:3908 /api/csrf/poc.","o":"present","r":"CSRF PoC wave: wired /api/csrf/poc into the GUI (Proxy history / Site map DetailPane), closing the last GUI-reachability gap."},{"a":"target","f":"Engagement tools > Search (regex search across a site map branch, request and response)","s":"present","i":"high","e":"hours","g":"None -- the last remaining gap (cannot scope to a site-map branch) is closed: the Site map tree now has real directory nodes (see the sibling \"hierarchical tree\" item), and clicking one scopes both the HTTP history table and Deep Search's /api/search regex-over-bodies results to that branch (client-side post-filter on the already-server-scanned hits, the same pattern already used for the in-scope/params/hide-404 chips).","w":"CLOSED 2026-08-22: proxy.jsx SiteMap folder click now sets selectedOrigin.branch (a path prefix); ProxyTab.originRows filters on it (r.path stripped of its query string === branch, or startsWith branch + \"/\"), and both HistoryTable (fed originRows) and the existing Deep Search toggle (which filters those same rows by deepHits) are scoped for free -- no backend change needed since /api/search already returns global hits and the frontend was already post-filtering them against the visible row set.","v":"control_server.cpp /api/search now iterates ControlLogic::searchRowForIteration(n,i) newest-first with NO fixed row cap; truncated = ControlLogic::searchTruncated(scanned,n); the response carries scanned/total/scannedMinId. proxy.jsx HistoryTable keeps rows with id < deepMinId (unscanned) visible. Locks in Tests/control_logic: newest-first mapping + truncated-iff-incomplete, mutation-proven.","o":"present","r":"Site map branch-scoping wave: added real directory nodes to the Site map tree (buildSiteMapTree in ui-v2/proxy.jsx) and threaded folder selection through as selectedOrigin.branch, scoping originRows (and therefore both HistoryTable and Deep Search) to the selected branch. Closes the sole remaining gap on this item -- flips partial -> present."},{"a":"target","f":"Site map: hierarchical tree (protocol://host:port → directory → file), expandable, one node per discovered resource","s":"present","i":"high","e":"weeks","g":"Client-side only, same architecture as the existing #370 per-host leaf derivation: SiteMapModel (site_map_model.hpp) stays a flat host-only QAbstractListModel with no parent-index tree, so the Qt desktop front end (Src/App/app.qml) does not gain this -- ui-v2-only, the same asymmetry already flagged on sibling ui-v2-only capabilities elsewhere in this file. The tree only reflects paths actually seen in HTTP history (captured traffic, manual \"+ map\" adds, and OpenAPI/robots/sitemap promotions) -- it is not merged live with a running content-discovery session's own tree (tracked separately: \"Content discovery results as a live tree merged into the site map\").","w":"CLOSED 2026-08-22: ui-v2/proxy.jsx SiteMap now builds a real protocol://host:port -> directory -> file tree via buildSiteMapTree(), splitting each leaf's pathname (query stripped for the directory split only, kept on the leaf itself) on \"/\" into nested, independently expandable directory nodes -- exactly the node-per-segment structure the item asks for, one leaf per discovered method+path resource at the bottom. Selecting a directory node scopes the HTTP history table (and Deep Search) to that branch, doubling as the \"Engagement tools > Search\" branch-scoping fix (sibling item, same commit).","v":"Src/FrontEnd/GUI/Models/Proxy/site_map_model.hpp:18 `class FRONTEND_GUI_EXPORT SiteMapModel : public QAbstractListModel {` -- a LIST model; rowCount returns 0 for any valid parent (cpp:17-20 `if (parent.isValid()) return 0;`). Entry is host/count/anyTls (hpp:40-44); path is never read -- site_map_model.cpp:83 reads only HostRole and TlsRole. Browser UI: ui-v2/proxy.jsx:189-198 `{entries.map(e => (","o":"","r":"Site map branch-scoping wave: buildSiteMapTree()/siteMapTreeLeafCount() (pure, unit-tested) group a host's leaves into nested directory nodes by path segment; SiteMap renders them as expandable folder rows (a new .sm-folder style) recursively nested under each host, with a scope banner to show/clear the selected branch. absent -> present."},{"a":"target","f":"Site map also populates from Repeater, Intruder, Scanner and extension-issued requests (everything Burp sends lands in the map)","s":"absent","i":"medium","e":"days","g":"Requests you craft in Repeater or fire from Intruder never appear in history or the map, so the map is not a record of what you sent the target. Content-discovery hits become findings with rowId 0, not rows.","w":"Confirmed by enumerating every caller of addResponse/appendEntry repo-wide rather than trusting the app.cpp grep, then reading Repeater::send to be sure it does not emit through some other route. It does not. Two producers the first pass missed do reach the map (history replay, OpenAPI import) but neither is one of the four tools named here.","v":"Repeater is still a dead end: Src/Core/Networking/repeater.cpp:135 `void Repeater::send() { ... emit responseChanged(); emit busyChanged(); emit tabsChanged(); }` -- UI-state signals only, no entryLoaded/responseReceived. Repo-wide `grep -rn \"addResponse|appendEntry\" Src/` still returns only history-replay (control_server.cpp:3214-3216 `if (w.history) w.history->addResponse(r, resp); ... if (w.projectStore) w.projectStore->appendEntry(r, resp);`) and direct project-store callers (project_store.cpp:1054, control_server.cpp:6679) -- confirmed by grepping Src/Core/Networking/intruder.cpp and every scanner .cpp for the same two symbols: zero hits in either. Content-discovery hits still become rowId-0 findings, not history rows (see the sibling 'live tree' item).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-grepped every addResponse/appendEntry call site repo-wide plus Repeater::send and every scanner source file directly -- Repeater, Intruder and Scanner still never write into history or the site map; only history-replay and direct project-store appends (OpenAPI import, etc.) reach it, matching the prior pass's finding exactly with no line drift. No code change this pass."},{"a":"target","f":"Site map \"Issues\" pane: scanner issues attached to the selected tree node, with a per-branch issue tree and severity/confidence icons overlaid on the map","s":"absent","i":"high","e":"days","g":"You cannot select a URL and see its issues, and cannot see which branch of the app is where the bugs are. Triage is a flat scroll.","w":"Confirmed. Corrected line numbers (IssuesTab is app.jsx:927, not 742) and verified the SiteMap component's prop list to be certain it cannot overlay anything.","v":"ui-v2/app.jsx:1781 `function IssuesTab({ dispatch })` still renders a flat list with only severity/kind filters, plain-text location (`{f.host} · {f.url}`) -- no per-branch tree, no map overlay. ui-v2/proxy.jsx:660 `function SiteMap({ entries, rows, selectedOrigin, selectedRowId, onSelect, onSelectLeaf, totalRows, onRowContextMenu, annotations, annotatedOnly })` -- the prop list carries no findings/issues data of any kind, confirming the map component still cannot overlay a severity/confidence icon or receive a per-node issue count.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-read IssuesTab (line moved 927 -> 1781) and SiteMap's full prop signature (line moved 172 -> 660, gained an `annotations`/`annotatedOnly` pair for the #299 highlight-colour feature but still nothing findings-shaped) -- confirms the map still cannot show per-node issues or overlay severity icons. No code change this pass."},{"a":"target","f":"Site map filter — Filter by request type: \"Show only in-scope items\", \"Show only requested items\", \"Show only parameterized requests\", \"Hide not-found items\"","s":"present","i":"medium","e":"days","g":"None -- proxy.jsx FilterBar/HistoryTable gain IN-SCOPE, PARAMS, and HIDE 404 toggle chips (client-side predicates over r.params/r.status/r.host, the last via a new hostInScope() glob matcher against scope.in). 'Requested only' stays trivially true for every row since Nullock does not yet distinguish requested-vs-inferred URLs (no inference engine exists), so it was not given a separate toggle -- an honest limitation, not a missing control.","w":"Closed 2026-08-09: ProxyFilterModel/proxy.jsx previously exposed only host/status-class/method/search filters. Added three concrete toggle chips wired into both HistoryTable's filtered useMemo and ProxyTab's own `shown` count, all pure frontend over fields already present on every row.","v":"ui-v2/proxy.jsx globToRegex()/hostInScope() (glob match r.host against scope.in); HistoryTable paramsOnly/hideNotFound/inScopeOnly props applied in its filter predicate; FilterBar IN-SCOPE/PARAMS/HIDE 404 chip row.","o":"absent","r":"Wave 2 Target/Scope batch -- Site map filter — Filter by request type: \"Show only in-scope items\", \"Show only requested items\", \"Show only parameterized requests\", \"Hide not-found items\" closed (absent -> present), frontend-only, no backend change."},{"a":"target","f":"Site map / history annotations: per-item Comment and Highlight (six colours), used to drive filters and reporting","s":"present","i":"high","e":"days","g":"None for this history/Site map workflow. Other message tables and global report formats remain outside this item; see the platform annotation item.","w":"Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action.","v":"Src/Core/Storage/project_store.cpp (historyAnnotations, annotateHistory, HAR import/export); Src/BackEnd/Control/control_server.cpp (/api/history/annotations, /api/history/annotation); ui-v2/real-data.js and proxy.jsx; bin/nullock; scripts/annotations_regression.py; Tests/ui/annotations_data_test.cjs and annotations_browser_test.cjs.","o":"partial","r":"Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action."},{"a":"target","f":"Manual application mapping / unrequested items: adding items to the site map by hand, and Burp inferring unrequested nodes from links, robots.txt and sitemap.xml so they show greyed-out in the tree","s":"partial","i":"medium","e":"days","g":"Both named legs now have a real UI path, but neither is automatic the way Burp's is: (1) hand-mapping is a one-URL-at-a-time text box (ui-v2/proxy.jsx), not a right-click 'add to site map' on an arbitrary selection; (2) robots.txt Disallow paths and sitemap.xml <loc> URLs each need an explicit '+ map' click per hit (ui-v2/app.jsx DiscoverTab) rather than being auto-inferred the moment they're discovered. There is still no link-graph inference (Burp also greys out same-page HTML links never actually requested) -- only the two backend-known sources (robots/sitemap) can be promoted, since content_discovery.cpp/robots_recon.cpp are the only C++ that surfaces candidate paths never sent.","w":"Closed the two frontend legs the prior why-text correctly identified as missing, reusing the existing synthetic-import mechanism rather than adding a backend route: a new NL.actions.addUrlToSiteMap(originUrl, path, method) thin wrapper (ui-v2/real-data.js) builds a one-path, one-operation OpenAPI-shaped spec and posts it through the already-proven /api/openapi/import endpoint, so a hand-typed URL or a promoted robots/sitemap hit lands as the exact same status-0 'OpenAPI imported (not yet sent)' unrequested row the spec-paste importer already produces -- confirmed by reading control_server.cpp:6231-6241 (resp.statusCode=0, reasonPhrase='OpenAPI imported (not yet sent)', persisted via appendEntry+entryLoaded) and confirming no other code path in the repo ever persists a status-0 row, so status===0 is an unambiguous unrequested marker for the frontend to grey on.","v":"ui-v2/proxy.jsx SiteMap(): a `.sm-add-row` text input + ADD button calls addUrlToMap() -> NL.actions.addUrlToSiteMap(origin, path, \"GET\"); each leaf row now computes `const unrequested = r.status === 0` and adds an `unrequested` class (opacity 0.55, dashed underline, status text replaced with \"not sent\") -- ui-v2/styles.css .sm-leaf.unrequested. ui-v2/app.jsx DiscoverTab(): each robots-scan \"Disallowed paths\" and \"Sitemap URLs\" table row gains a MapBtn calling addHitToMap(key, origin, path) -> the same wrapper, tracked per-hit in a mappedHits Set so a promoted hit shows \"✓ mapped\" instead of the button again. Src/BackEnd/Control/control_server.cpp:6057-6252 /api/openapi/import (unchanged, reused as-is) and :7814-7876 /api/robots/scan (unchanged, already returned `disallowed`/`sitemapUrls` -- only their existing UI table gained the per-row button).","o":"partial","r":"Manual add-to-map text box + unrequested (status-0) greying in the Site Map tree, plus a per-hit \"+ map\" promotion button on robots.txt Disallow paths and sitemap.xml URLs in the Discover tab -- all three reuse the existing /api/openapi/import synthetic-entry endpoint, no backend change."},{"a":"target","f":"Site map \"Crawl paths\" view (path a crawl took to reach each location)","s":"absent","i":"low","e":"days","g":"No way to see how a resource was reached. Low value outside large automated crawls, and moot until a tree exists.","w":"Confirmed. Read the crawler's queue structure directly -- depth is tracked, the referrer is not persisted.","v":"Src/Core/Networking/crawler.hpp:74-77 `struct PendingUrl { QString url; int depth = 0; };` -- no parent/referrer field. hpp:80 `void extractAndEnqueue(const QString &fromUrl, const QByteArray &body, int depth);` takes fromUrl but only to resolve relative URLs; hpp:106-107 `QSet<QString> m_seenUrls; QQueue<PendingUrl> m_queue;` stores no edges. `grep -rail \"crawl path|crawlPath\" Src ui-v2 extension","o":"absent","r":"Wave 0 register-accuracy audit: held at absent, verbatim. Re-read crawler.hpp:74-107 -- `PendingUrl` is still `{ QString url; int depth = 0; }` with no parent/referrer field, `m_seenUrls`/`m_queue` store no edges, and a fresh `grep -rail \"crawl path|crawlPath\" Src ui-v2 extensions` still returns nothing. Cited line numbers (74-77, 80, 106-107) matched exactly with zero drift. No code change this pass."},{"a":"target","f":"Scope: \"Include subdomains\" checkbox on a prefix rule","s":"present","i":"low","e":"hours","g":"None -- an 'include subdomains when adding' checkbox in the Scope tab's pane-head applies to both scope columns: when checked, adding a host also adds its *.host wildcard via the same scope-add-in/out dispatch. Implemented as a shared toggle above both columns rather than per-input (functionally equivalent: still adds both entries per Add action), and the placeholder text was corrected to show a bare host works too.","w":"Closed 2026-08-09: scope is still a flat glob list server-side (no per-rule subdomain flag), so the fix is the two-entry UI convenience the plan called for -- ScopeColumn's commit() adds both `host` and `*.host` when the checkbox is on and the value isn't already a wildcard.","v":"ui-v2/tabs.jsx ScopeTab include-subdomains checkbox (pane-head) threaded into both ScopeColumn instances via the includeSubdomains prop; ScopeColumn.commit() dispatches a second scope-add-* with '*.'+value when set.","o":"absent","r":"Wave 2 Target/Scope batch -- Scope: \"Include subdomains\" checkbox on a prefix rule closed (absent -> present), frontend-only, no backend change."},{"a":"target","f":"Advanced scope control: per-rule Protocol (HTTP/HTTPS/Any) + Host-or-IP-range (regex) + Port (regex) + File (regex, query ignored), toggled by the \"Use advanced scope control\" checkbox","s":"present","i":"high","e":"days","g":"","w":"Active tools check every concrete outbound request against host, protocol, port and path scope. Raw TCP/TLS probes require an unrestricted endpoint grant. Invalid enabled rules fail closed; invalid editor saves preserve the prior policy.","v":"Src/Core/Networking/outbound_scope.cpp; HttpClient::send; raw port/TLS/WebSocket guards; Tests/scope_logic/scope_logic_test.cpp; Tests/proxy_shutdown/proxy_shutdown_test.cpp; scripts/outbound_scope_regression.py; Tests/ui/scope_browser_test.cjs","o":"present","r":"Full outbound scope boundary, live policy updates, full-URL redirect/crawler checks and visible validation errors."},{"a":"target","f":"\"Add to scope\" / \"Remove from scope\" from the right-click context menu on any site map or Proxy history item","s":"present","i":"medium","e":"hours","g":"None -- right-click (onContextMenu) on any site-map or HTTP history row opens a small menu with Add to scope / Remove from scope, both dispatching the existing scope-add-in/scope-remove-in reducer actions.","w":"Closed 2026-08-09: there was no context-menu infrastructure anywhere in ui-v2. Added a lightweight menu (ProxyTab ctxMenu state + a fixed-position panel closed by an overlay click) wired to both SiteMap and HistoryTable rows via a shared onRowContextMenu callback.","v":"ui-v2/proxy.jsx ProxyTab ctxMenu state + openRowMenu/closeRowMenu; SiteMap and HistoryTable both gain an onRowContextMenu prop invoked from each row's onContextMenu; menu body dispatches scope-add-in / scope-remove-in.","o":"absent","r":"Wave 2 Target/Scope batch -- \"Add to scope\" / \"Remove from scope\" from the right-click context menu on any site map or Proxy history item closed (absent -> present), frontend-only, no backend change."},{"a":"target","f":"Target > Issue definitions: a browsable library of every issue type the scanner can report, independent of whether it has been found","s":"present","i":"low","e":"days","g":"None remaining for the browse capability itself. The library exists as data + an endpoint (GET /api/issue-definitions, 198 issue kinds) AND is now reachable in-app: the ISSUES tab's view toggle gained a third \"Definitions\" mode (ui-v2/app.jsx) that lazily fetches the catalog and renders it as a filterable list (search by kind/CWE/OWASP), independent of whether any of those kinds have actually been found yet -- exactly Burp's Target > Issue definitions library. What's still tracked separately: each entry's prose is the one-line canonical remediation rather than Burp's multi-paragraph background/remediation prose (a backend data-model gap, see the 'Per-issue definition content' item) -- that does not gate this item, which was specifically about the browsable-independent-of-found-status capability.","w":"UPGRADED partial->present: the prior audit's remaining blocker was \"no in-app browse UI yet\" -- that is now false. Added a Definitions view to the existing ISSUES tab's Flat/Grouped toggle (now Flat/Grouped/Definitions): a lazy-loaded fetch of NL.actions.issueDefinitions() -> GET /api/issue-definitions, rendered as a scrollable list (kind, CWE, OWASP, CVSS, compliance tags, confidence, description) with a client-side filter box matching kind/CWE/OWASP substrings. Every field the component reads (kind/cwe/owasp/cvssScore/compliance/confidence/description) matches the endpoint's actual JSON shape exactly -- no new field invented, nothing read that the backend doesn't send.","v":"ui-v2/app.jsx IssuesTab: defs/defsLoading/defsQuery state + loadDefs() + visibleDefs filter; switchView(\"definitions\") lazy-loads via NL.actions.issueDefinitions(); Definitions toggle button next to Flat/Grouped; content branch renders visibleDefs when view===\"definitions\". ui-v2/real-data.js NL.actions.issueDefinitions() -> fetch(\"/api/issue-definitions\").then(r=>r.json()). Backend unchanged: control_server.cpp:6152 /api/issue-definitions already served {ok,count,definitions[]} with exactly the fields read. Verified: bundled-babel transform of app.jsx succeeds; a standalone functional test of the visibleDefs filter logic (kind/CWE/OWASP substring match, case-insensitive, null/empty-safe) passes against sample data shaped like the real endpoint response.","o":"partial","r":"Wave 2 UI wiring: added a Definitions view to the ISSUES tab (ui-v2/app.jsx + real-data.js) that browses the existing GET /api/issue-definitions catalog -- closes the \"no in-app browse UI\" gap the prior audit flagged; the endpoint was already implemented and tested server-side, only the UI was missing."},{"a":"target","f":"Issue detail view with Advisory / Request / Response sub-tabs and per-instance evidence highlighting","s":"present","i":"medium","e":"days","g":"None for the core pane -- clicking a finding in the flat ISSUES list opens an inline detail pane (Advisory / Request / Response tabs) instead of navigating away. Advisory renders the enrichment fields the backend already attaches (cwe/owasp/cvssScore/cvssVector/confidence/compliance/fixSummary); Request/Response pull the same raw history bytes proxy.jsx's DetailPane uses, with every literal occurrence of the finding's evidence string highlighted inline. One honest remainder: extension-sourced findings (rowId 0) have no underlying HTTP transaction to show -- the pane says so rather than fetching row 0, tied to item #390's rowId-0 gap, not a new one.","w":"Closed 2026-08-11: ui-v2/app.jsx IssuesTab's flat-view row click now toggles an inline IssueDetailBody (Advisory/Request/Response tabs) instead of calling jumpToRow() directly; jumpToRow is still reachable via an explicit \"Open in proxy\" button in the pane's header. A new highlightEvidence() pure helper marks every occurrence of the finding's evidence string in the raw request/response text.","v":"ui-v2/app.jsx IssueDetailBody()/highlightEvidence()/toggleDetail() + IssuesTab's detailOpenId/detailTab state; NL.requestRawById/responseRawById (ui-v2/real-data.js) for the raw pair; control_server.cpp:1311-1328 finding JSON contract (cwe/owasp/cvssScore/cvssVector/compliance/fixSummary/confidence/rowId) matched field-for-field.","o":"absent","r":"Issue-detail batch: inline Advisory/Request/Response pane with evidence highlighting replaces the old navigate-away-on-click behavior in the ISSUES tab."},{"a":"target","f":"Content discovery: no UI at all vs Burp's dedicated discovery window","s":"present","i":"high","e":"days","g":"None — a DISCOVER tab now wraps all three engines (wordlist content/directory discovery, robots.txt + sitemap recon, BFS crawler start/stop) with results rendered generically and content-discovery/robots hits also flowing to Issues.","w":"Closed 2026-08-08: all three engines and their control endpoints were already complete server-side; only the client had no wrapper. Added discoverContent/scanRobots/crawlerStart/crawlerStop to ui-v2/real-data.js and a DISCOVER tab that runs each and renders its result. Verified via bundled-babel transform; response fields matched against control_server.cpp's /api/content/discover, /api/robots/scan, /api/crawler/start|stop handlers.","v":"ui-v2/real-data.js: discoverContent (POST /api/content/discover), scanRobots (POST /api/robots/scan), crawlerStart/crawlerStop (POST /api/crawler/start|stop); ui-v2/app.jsx DiscoverTab renders hits/disallowed/sitemapUrls per the control_server.cpp JSON shape.","o":"absent","r":"DISCOVER tab surfaces content-discovery, robots/sitemap recon, and crawler start/stop."},{"a":"target","f":"Content discovery: recursive descent into discovered directories (Burp's discovery recurses into every folder it finds)","s":"absent","i":"high","e":"days","g":"One directory level per invocation. Finding /admin never leads to /admin/users -- the tester must re-POST manually for each hit, which is the core of what Burp's engine automates.","w":"Confirmed by reading the loop. base is computed once and never reassigned; there is no queue, no depth field, and no re-entry into discover().","v":"content_discovery.cpp:96 `const QString base = normBase(req.basePath);` is still the sole assignment -- base is never reassigned into a discovered subdirectory. The probe loop (now :169-176, building a flat `probes` list fanned out across a concurrency pool added since the last pass) still has no queue of discovered directories and no re-entry into discover() -- the concurrency addition parallelizes the SAME flat wordlist, it does not add a second level.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-read the probe-building loop (moved 154-176 -> 169-176 after a concurrency-pool addition) -- still exactly one directory level per invocation, `base` assigned once, no depth field or requeue anywhere. The new concurrency/throttle controls speed up the flat scan, they do not add recursion. No code change this pass."},{"a":"target","f":"Content discovery: file-extension bruteforce (probe each word against a list of extensions) and filename mutation rules","s":"present","i":"medium","e":"hours","g":"None -- filename-mutation rules are built end-to-end: ContentDiscovery::mutateFilenames (content_logic.cpp) expands each candidate to word~, word.bak/.old/.orig/.save/.tmp/.1 and a dir-aware .leaf.swp, wired into discover() via req.mutations, exposed as a `mutations` boolean on POST /api/content/discover (control_server.cpp:9518), and now toggled from a \"filename mutations\" checkbox in ui-v2 DiscoverTab (sibling of the extensions field). The extension-bruteforce half already had its GUI field.","w":"CONFIRMED end-to-end. Backend: content_discovery.hpp Request::mutations (default false); content_discovery.cpp:101 `words = mutateFilenames(words, req.mutations)`; control_server.cpp:9518 `cr.mutations = bodyJson.value(\"mutations\").toBool(false)`. Frontend: ui-v2/app.jsx DiscoverTab now has a `mutations` boolean state + checkbox next to the extensions field, threaded through NL.actions.discoverContent(url, max, {..., mutations}) -> real-data.js POST body `mutations`. Both touched ui-v2 files transform cleanly under the bundled babel.","v":"ui-v2/app.jsx DiscoverTab `mutations` checkbox -> NL.actions.discoverContent opts.mutations; ui-v2/real-data.js discoverContent() posts `mutations`; control_server.cpp:9518 cr.mutations; content_discovery.cpp:101 mutateFilenames(words, req.mutations); content_discovery.hpp:51 bool mutations = false.","o":"present","r":"Wave 2 frontend wiring: added the ui-v2 `mutations` checkbox (DiscoverTab) that was the sole remaining gap on this item, closing it to present."},{"a":"target","f":"Content discovery results as a live tree merged into the site map, with the discovery session's own request count / status","s":"absent","i":"high","e":"days","g":"Discovered paths cannot be sent to Repeater, re-requested, or inspected. You get a status code and a byte count in a flat findings list, and the request that produced them is discarded.","w":"Confirmed. Hits become findings with rowId 0 and a JSON array; no history row is created, so nothing can reach the map. Corrected line numbers (8467-8480, not 8328-8339).","v":"control_server.cpp:9682-9697 `for (const auto &h : cres.hits) { hits.append(QJsonObject{ { \"path\", h.path }, { \"status\", h.status }, { \"size\", h.size }, { \"location\", h.location }, { \"note\", h.note } }); if (m_wiring.scanner) m_wiring.scanner->reportFinding(0, \"info\", \"content-discovered\", ...` -- still rowId 0, i.e. no history row, so nothing a discovered path produces can be sent to Repeater or re-requested. SiteMapModel still exposes no insertion API a discovery session could stream into.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-read the hit-to-finding loop (moved 8467-8480 -> 9682-9697) -- still `reportFinding(0, ...)`, no history row, no site-map tree insertion, matching the prior pass's finding with refreshed line numbers only. No code change this pass."},{"a":"target","f":"Engagement tools > Analyze target (Target Analyzer): counts of static vs dynamic URLs, unique parameter names, and per-URL entry points across a site map branch","s":"partial","i":"low","e":"days","g":"Query-string parameter names only -- request bodies aren't held client-side, so form/JSON body parameter names never appear in the unique-parameter list or an entry point's params column, a real gap vs. Burp's whole-body-aware analyzer. Static/dynamic classification is also a URL-shape heuristic (recognized static extension + no query string), not Burp's own algorithm, so edge cases (e.g. a static-looking path served dynamically with no query) can misclassify.","w":"Closed the frontend half via a client-side ANALYZE TARGET overlay (ui-v2/proxy.jsx TargetAnalyzerOverlay) reached from the HTTP HISTORY pane-head, computed entirely from HTTP history rows already in state -- no backend endpoint needed or added, since r.path already carries the full path+query (control_server.cpp:1515-1516 map both \"url\" and \"path\" to ProxyModel::UrlRole, which is request.path verbatim). Pure helpers classifyUrlKind/queryParamNames/analyzeTargetSurface produce unique-URL, static, and dynamic counts, a unique query-parameter-name list (each tagged with the entry-point count it appears across), and a per-path entry-point table (methods + param names + kind), scoped to whatever the site-map tree currently has selected (a host, a branch, or all hosts) via the existing originRows the SiteMap/HistoryTable pair already computes -- so \"across a site map branch\" is a real, working scope, not just the whole history. Moved absent -> partial rather than present: body-parameter names are a genuine, honestly-named remaining gap (see gap text).","v":"ui-v2/proxy.jsx: classifyUrlKind/queryParamNames/analyzeTargetSurface (pure helpers) + TargetAnalyzerOverlay (new component) + an \"ANALYZE TARGET\" button in ProxyTab's HTTP HISTORY pane-head, wired to originRows (the same site-map-scoped row set HistoryTable/SiteMap already use) and selectedOrigin for the scope label. Field contract: r.path/r.method already present on every row (control_server.cpp:1515-1516 url/path -> ProxyModel::UrlRole -> proxy_model.cpp:22 request.path); no new fields invented, no backend endpoint added.","o":"partial","r":"Target Analyzer wave: client-side ANALYZE TARGET overlay in the Proxy tab closes the URL-count/parameter-name/entry-point legs of this item, scoped to the current site-map selection; body-parameter names stay an honest remaining gap."},{"a":"target","f":"Engagement tools > Simulate manual testing (generates decoy traffic)","s":"absent","i":"cosmetic","e":"days","g":"Missing. Rarely used; exists mainly to make an automated scan look human in target logs.","w":"Confirmed. Grepped for the feature name and for the concept (decoy/noise/synthetic traffic); the single 'decoy' hit is an unrelated comment about stale robots.txt directives.","v":"`grep -rlia \"decoy|simulate manual|manual testing simulat\" .` now matches 15 files (up from 1 at the prior pass, driven mostly by Lab 24's clickjacking PoC which legitimately uses \"decoy\" for its overlay button) -- every hit re-checked by hand is either the Lab 24 clickjacking PoC (labs/24-clickjacking/*, docs/labs/24-clickjacking.html, ui-v2/labs-data.js, scripts/labs_site.py, ui-v2/proxy.jsx's own clickjacking-PoC generator) or an unrelated code comment using \"decoy\" colloquially (js_recon_logic.cpp:144 stale-directive comment; ssrf_scan.hpp:74/ssrf_scan.cpp:201/ssrf_logic.cpp:58 \"decoy param\" in SSRF sink-detection comments; two test-file comments about a decoy secret/value in unrelated regression tests). None is a decoy-TRAFFIC-generation feature -- still nothing shipped that fires synthetic background traffic to disguise an automated scan.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. The literal grep now returns far more hits than the prior pass's \"exactly one file\" (new labs and comments added \"decoy\" in unrelated senses since), so re-checked every match by hand rather than trusting the count -- all are Lab 24's clickjacking PoC or unrelated SSRF/regression-test comments. No decoy-traffic feature exists. No code change this pass."},{"a":"target","f":"Engagement tools > Schedule task (run a scan/crawl at a set time or interval)","s":"absent","i":"low","e":"days","g":"No in-app scheduling and no shipped scheduled job. A user would have to write their own cron around --scan, and there is no crawl/discovery equivalent to schedule anyway.","w":"Confirmed, and I tightened the compensating-control claim. The first pass said the CI direction partly compensates; the shipped workflow is workflow_dispatch (manual) only, with no cron: schedule block, so nothing shipped schedules anything.","v":"`grep -rain \"schedul|cron|recurring\" Src/BackEnd/Control/control_server.cpp` -> no matches. .github/workflows/nullock-scan-example.yml:5-8 `# Manual-dispatch only so it never runs against a target without an explicit opt-in.` / `on:` / `  workflow_dispatch:` -- no `schedule:` key anywhere in the file. The CLI gate it drives is one-shot: Src/App/app.cpp:658-661 `if (!scanUrl.isEmpty()) { ... return","o":"absent","r":"Wave 0 register-accuracy audit: held at absent, verbatim. Re-ran both greps: `schedul|cron|recurring` (case-insensitive, proper alternation) against control_server.cpp still returns zero matches, and `.github/workflows/nullock-scan-example.yml` still declares only `workflow_dispatch:` with no `schedule:` key. No code change this pass."},{"a":"target","f":"Qt desktop Target UI (the project ships a Qt6 front end as well as the browser UI)","s":"partial","i":"low","e":"weeks","g":"Real, but the same flat host list and host-glob scope as ui-v2 -- no tree, no per-node issues, no context menu, no annotations. The misleading part is the repo layout, not the capability: the four blank Components files read as an unfinished Target UI while the finished one lives in app.qml. Also carries the relative-path load bug for installed builds.","w":"UPGRADED, and this is the first pass's largest error. It read the four 8-line placeholder .qml files and concluded the Qt Target UI is blank. Those files are dead scaffolding -- registered in the QML module but never instantiated. The QML the app actually LOADS is Src/App/app.qml, which contains a working Site Map pane bound to the siteMap model and a complete Scope tab with both lists and add/rem","v":"The loaded file: Src/App/app.cpp:1485-1487 `// run from project root so this relative path resolves to Nullock/Src/App/app.qml` / `const QUrl url(QStringLiteral(\"./Src/App/app.qml\"));` / `engine.load(url);`. Working site map, app.qml:159 `HeaderCell { text: \"Site Map (\" + siteMap.rowCount() + \")\"; ... }` with a bound ListView beneath it; the Scope tab (app.qml:111 TabHeader, :428 onward) has real in-scope/out-of-scope lists bound to `projectStore.inScopeList`/`outOfScopeList` with add/remove wired to `projectStore.addInScope`/`removeInScope` -- still the same flat host list and host-glob scope as ui-v2, no tree, no per-node issues, no context menu.","o":"partial","r":"Wave 0 register-accuracy audit: held at partial (the prior pass's UPGRADE from absent-looking to a real, if limited, Qt Target UI stands). Re-verified app.cpp still loads ./Src/App/app.qml by relative path (line moved 1159-1161 -> 1485-1487, same relative-path-for-installed-builds bug) and app.qml's site map + scope tab are functionally unchanged. No code change this pass."},{"a":"platform","f":"AI payload generator (local Ollama mutates a seed payload set into novel-but-shaped variants on demand) -- Burp has no equivalent, an extension is required for any AI payload assist","s":"present","i":"medium","e":"hours","g":"None -- the PAYLOADS tab's AI GENERATE control (count field + button) calls the endpoint and renders the returned payloads (or the seed-list fallback with a clear \"ollama unreachable\" badge) alongside the existing static Payload Forge list.","w":"The backend endpoint (control_server.cpp /api/payloads/generate) existed but had no ui-v2 caller anywhere -- confirmed by grep across ui-v2/*.jsx and real-data.js before this change. Closed by wiring it: NL.actions.aiGeneratePayloads(kind, count) in real-data.js, and an AI generate section in PayloadsTab (app.jsx) that reuses the technique already selected for the static forge, shows the model name on success, and distinguishes the deterministic fallback (ok:false, fallback:true) from a genuine model response.","v":"ui-v2/real-data.js aiGeneratePayloads() -> POST /api/payloads/generate {kind,count}; ui-v2/app.jsx PayloadsTab's aiGenerate()/aiData state + render block reading aiData.payloads/model/fallback, matching control_server.cpp's response shape verbatim ({ok,model,payloads} or {ok:false,fallback:true,model,payloads,error}).","o":"present","r":"Wired the previously-orphaned /api/payloads/generate (AI payload mutation via local Ollama) into the PAYLOADS tab: a count field + AI GENERATE button, rendering the model's variants or the deterministic seed-list fallback with a distinct badge."}]</script>
+<script type="application/json" id="rm-data">[{"a":"intruder","f":"Attack type: Sniper","s":"present","i":"low","e":"hours","g":"None -- a MODE select in the Intruder target row (tabs.jsx) lets the user pick sniper explicitly, and the pane-head label reflects the live selection.","w":"Closed 2026-08-09: added an attack-type <select> (tabs.jsx target-row) bound to intruder.attackType, dispatching intruder-set{attackType} -> POST /api/intruder/set. Sniper is option 0.","v":"ui-v2/tabs.jsx ATTACK_TYPES select in IntruderTab's target-row; control_server.cpp:3209-3215 already parsed attackType (int or name).","o":"present","r":"Intruder wave: MODE selector (sniper/battering-ram/pitchfork/cluster-bomb) closes the GUI-reachability gap for all four attack types."},{"a":"intruder","f":"Attack type: Battering ram","s":"present","i":"low","e":"hours","g":"None -- selectable via the same MODE select as Sniper (option 1).","w":"Closed 2026-08-09: same MODE <select> as item 0; battering-ram is option 1, no backend change needed.","v":"ui-v2/tabs.jsx ATTACK_TYPES select; control_server.cpp:3209-3215 attackType parsing.","o":"present","r":"Intruder wave: MODE selector closes the GUI-reachability gap for all four attack types."},{"a":"intruder","f":"Attack type: Pitchfork","s":"present","i":"medium","e":"days","g":"None -- the MODE select plus a per-position PAYLOAD SETS column editor (shown when pitchfork/cluster-bomb is picked and the template has >1 §marker§) let the user fill payloadSets[i] per position from the GUI.","w":"Closed 2026-08-09: added a per-position multi-column payload-set editor (tabs.jsx IntruderTab, isMultiSet branch) that renders one textarea per §marker§ pair, dispatching intruder-set{payloadSets} -> POST /api/intruder/set. No backend change; setPayloadSets/syncSetsToPositions already existed.","v":"ui-v2/tabs.jsx PAYLOAD SETS pane (isMultiSet && posCount>1); control_server.cpp:3221-3232 payloadSets accepts one array per position; intruder_engine.cpp:86-104 zip-by-index engine.","o":"present","r":"Intruder wave: per-position payload-set editor closes Pitchfork's GUI-reachability gap."},{"a":"intruder","f":"Attack type: Cluster bomb","s":"present","i":"medium","e":"days","g":"None -- same per-position PAYLOAD SETS editor as Pitchfork (item 2); Cluster bomb is MODE option 3.","w":"Closed 2026-08-09: same multi-set editor as item 2; the engine's odometer/cartesian product was already complete, only the GUI to enter one set per position was missing.","v":"ui-v2/tabs.jsx PAYLOAD SETS pane; control_server.cpp:3221-3232 payloadSets; intruder_engine.cpp:105-129 odometer cartesian product.","o":"present","r":"Intruder wave: per-position payload-set editor closes Cluster bomb's GUI-reachability gap."},{"a":"intruder","f":"Payload positions (§marker§) + insertion","s":"present","i":"low","e":"hours","g":"","w":"Re-read findMarkers/applyPayloads; scan-and-splice with null=default confirmed. Template textarea and § counter present in GUI.","v":"intruder_engine.cpp:15-32 findMarkers scans U+00A7 pairs; :134-148 applyPayloads splices, `out += p.isNull() ? m.def : p;`. tabs.jsx:620 `(intruder.template.match(/§/g)?.length||0)/2` shows insertion-point count.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Auto-mark payload positions (Add/Clear/Auto §)","s":"present","i":"medium","e":"days","g":"None -- + § wraps the current template-textarea selection in markers, CLEAR § strips every marker, and AUTO § auto-marks every query-string, form-body and Cookie value via a new pure autoMarkTemplate() helper (idempotent: already-marked values are left alone).","w":"Closed 2026-08-09: added +§/CLEAR §/AUTO § buttons to the TEMPLATE pane header. AUTO § parses the raw request (request-line query string, Cookie header, x-www-form-urlencoded body) and wraps each value; verified with a Node functional test (request-line, Cookie, form-body, idempotency, CRLF and LF templates).","v":"ui-v2/tabs.jsx autoMarkTemplate() (pure, exported for testing) + IntruderTab TEMPLATE pane-head buttons.","o":"partial","r":"Intruder wave: +§/CLEAR §/AUTO § close the auto-mark gap (partial -> present)."},{"a":"intruder","f":"Payload type: Simple list","s":"present","i":"low","e":"hours","g":"","w":"Re-read parseSet and the payloads textarea/presets. Fully GUI-reachable.","v":"intruder.cpp:20-27 parseSet splits the newline block, trims, drops empties. tabs.jsx:699-704 payloads textarea; PAYLOAD_PRESETS tabs.jsx:339-447 curated lists.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Payload type: Numbers (range/step/hex/padded)","s":"present","i":"medium","e":"days","g":"None -- a GENERATOR dialog in the Intruder PAYLOADS pane (numbers/dates/brute tabs, discovered from /api/intruder/generator-types) offers from/to/step/width/hex fields with a live count+sample preview, applying via /api/intruder/set{generator}.","w":"GUI closed: engine+API were already complete (re-read 2026-08-02), the only gap was that ui-v2 never called them. Generator dialog now covers all three types.","v":"intruder_generators.cpp:23-39 numbers(from,to,step,width,hex), stops before qint64 wrap. control_server.cpp:3143-3147 expandGen wires it; /api/intruder/generate previews. GUI: ui-v2/tabs.jsx IntruderTab GENERATOR dialog (buildGenSpec numbers branch); ui-v2/real-data.js intruderGenerate/intruderGeneratorTypes actions.","o":"present","r":"Intruder generator-dialog wave: numbers/dates/brute-forcer payload generation is now reachable from the GUI (was API-only)."},{"a":"intruder","f":"Payload type: Dates","s":"present","i":"low","e":"days","g":"None -- same GENERATOR dialog (dates tab: from/to ISO, stepDays, format), live preview via /api/intruder/generate.","w":"GUI closed alongside Numbers/Brute in the same dialog; no backend change needed.","v":"intruder_generators.cpp:76-87 dates(fromIso,toIso,stepDays,format) via QDate::addDays. control_server.cpp:3151-3154. GUI: ui-v2/tabs.jsx IntruderTab GENERATOR dialog (buildGenSpec dates branch).","o":"present","r":"Intruder generator-dialog wave: numbers/dates/brute-forcer payload generation is now reachable from the GUI (was API-only)."},{"a":"intruder","f":"Payload type: Brute forcer","s":"present","i":"low","e":"days","g":"None -- same GENERATOR dialog (brute tab: charset/minLen/maxLen), live preview shows count + capped flag before apply.","w":"GUI closed alongside Numbers/Dates in the same dialog; no backend change needed.","v":"intruder_generators.cpp:41-74 brute(charset,minLen,maxLen) over `charset.toUcs4()`, `kMaxChars = kMaxCount*64` (~6.4M) cap. control_server.cpp:3148-3150. GUI: ui-v2/tabs.jsx IntruderTab GENERATOR dialog (buildGenSpec brute branch).","o":"present","r":"Intruder generator-dialog wave: numbers/dates/brute-forcer payload generation is now reachable from the GUI (was API-only)."},{"a":"intruder","f":"Processing rule: Add prefix","s":"present","i":"low","e":"hours","g":"None -- the RULES bar (tabs.jsx IntruderTab) is an ordered rule-chain editor (op select populated from GET /api/intruder/rule-ops, +/-/reorder) covering prefix as one op.","w":"Closed 2026-08-09: added a RULES bar with add/remove/reorder rows, an op <select> per row (arg inputs for prefix/suffix/match-replace), dispatching intruder-set{rules} -> POST /api/intruder/set. rules is UI-only client state (not echoed by the snapshot), matching the existing grepMatch/grepExtract pattern.","v":"ui-v2/tabs.jsx RULES bar in IntruderTab; control_server.cpp:3247-3260 rules parsing (op+arg); intruder_rules.cpp:13 prefix op.","o":"present","r":"Intruder wave: RULES bar closes the processing-rule-chain GUI gap for prefix/suffix/encode/hash/case/reverse/match-replace at once."},{"a":"intruder","f":"Processing rule: Add suffix","s":"present","i":"low","e":"hours","g":"None -- same RULES bar as item 10 (suffix is one op in the dropdown).","w":"Closed 2026-08-09: same RULES bar as item 10; suffix is a listed op with a text arg input.","v":"ui-v2/tabs.jsx RULES bar; intruder_rules.cpp:14 suffix op.","o":"present","r":"Intruder wave: RULES bar closes the processing-rule-chain GUI gap for prefix/suffix/encode/hash/case/reverse/match-replace at once."},{"a":"intruder","f":"Processing rule: Match/replace","s":"present","i":"low","e":"hours","g":"None -- regex-replace matches a regex and replaces every occurrence with Burp-style back-references ($0/$1..$9/$$); the literal match-replace op remains for exact-string replaces.","w":"Re-read intruder_rules.cpp:28-39. The op does a LITERAL QString::replace only. Burp's match/replace processing rule is regex-based; the defining capability (regex) is absent, so this is a lookalike, not the Burp rule. Downgraded present->partial.","v":"intruder_rules.cpp:36-37 `QString s=value; s.replace(find, repl); return s;` — QString::replace(QString,QString) is a literal substring replace; there is no QRegularExpression path.","o":"present","r":"Added a `regex-replace` processing-rule op (arg 'pattern\\x1freplacement'): matches a QRegularExpression and replaces every occurrence, with Burp-style back-references $0/$1..$9/$$ expanded manually. The literal match-replace op stays for exact-string replaces. Pure + mutation-proven; fail-safe on invalid regex."},{"a":"intruder","f":"Processing rule: Modify case","s":"present","i":"low","e":"hours","g":"None -- uppercase/lowercase PLUS propername (Titlecase) and propername-keep (upper-first, keep rest) processing-rule ops cover Burp's Modify-case modes.","w":"Closed 2026-08-12: added the propername ops to applyRule (see reconciled).","v":"intruder_rules.cpp:15-16 `if(op==\"uppercase\") return value.toUpper(); if(op==\"lowercase\") return value.toLower();`.","o":"present","r":"Added propername + propername-keep processing-rule ops (upper-first / lower-or-keep-rest, code-point-safe, reusing the casemod generator's proper-case semantics) alongside the existing uppercase/lowercase; pure + mutation-proven. Reachable via the rule chain like every other processing op."},{"a":"intruder","f":"Processing rule: Encode (URL/HTML/Base64/hex)","s":"present","i":"low","e":"hours","g":"None -- same RULES bar; the encode ops (base64/base64url/url/hex/html/unicode-escape/rot13) are listed in the op <select>, sourced live from GET /api/intruder/rule-ops.","w":"Closed 2026-08-09: same RULES bar as item 10; encode ops need no arg input, just the op selection.","v":"ui-v2/tabs.jsx RULES bar + RULE_OPS_FALLBACK; intruder_rules.cpp:42-46 delegates encode ops to Transcode::apply.","o":"present","r":"Intruder wave: RULES bar closes the processing-rule-chain GUI gap for prefix/suffix/encode/hash/case/reverse/match-replace at once."},{"a":"intruder","f":"Processing rule: Hash","s":"present","i":"low","e":"hours","g":"None -- same RULES bar; md5/sha1/sha256/sha512 are listed hash ops in the <select>.","w":"Closed 2026-08-09: same RULES bar as item 10.","v":"ui-v2/tabs.jsx RULES bar; intruder_rules.cpp:67-68 hash ops via Transcode::apply.","o":"present","r":"Intruder wave: RULES bar closes the processing-rule-chain GUI gap for prefix/suffix/encode/hash/case/reverse/match-replace at once."},{"a":"intruder","f":"Grep - Match","s":"present","i":"low","e":"hours","g":"Single boolean 'any hit' column; Burp adds one flag column per configured expression.","w":"Re-read grep + computeGrep + GUI input. Works and is GUI-reachable, but collapses to one boolean column.","v":"intruder_grep.cpp:19-36 grepMatch tries each needle as regex else literal contains(). intruder.cpp:89 computeGrep() runs it over grepScanText(resp) (headers+decoded body). tabs.jsx:2264-2271 GREP·MATCH input; tabs.jsx:2691-2693 single ✓/· column (r.matched ternary), still one boolean flag, not one column per expression.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Grep - Extract","s":"partial","i":"low","e":"days","g":"Backend supports both regex and start/end-delimiter extract, but an attempt stores only ONE extracted value and the UI exposes a single regex Extract column -- Burp allows multiple grep-extract items per attack.","w":"Corrected from 'present' on independent re-derivation (2026-08-02): intruder.cpp:143 returns a single m_extracted QString (one ExtractedRole), so multi-extract parity with Burp is not met.","v":"intruder.cpp:162 `case ExtractedRole:return a->m_extracted;` (single QString); intruder_grep.cpp implements regex+delimiter extract modes (grepExtract); tabs.jsx:2558-2562 sends only {regex} to grepExtract, one Extract column (tabs.jsx:2273).","o":"partial","r":"Wave 0 register-accuracy audit: audited_state was stuck at \"present\" (the pre-correction grade the \"why\" field already says was corrected to partial on 2026-08-02) which rendered backwards on the roadmap page (\"closed since audit: present -> partial\" reads as a regression, not a correction) -- reset it to match the current, re-verified state. No code change; single-value extraction (m_extracted, one Extract column) still holds."},{"a":"intruder","f":"Resource pool: concurrent requests","s":"present","i":"low","e":"hours","g":"","w":"Re-read runWorker + pool_logic; semaphore-bounded concurrency and 1..64 clamp confirmed. GUI CONC field present.","v":"intruder.cpp:550 `m_pool.setMaxThreadCount(concurrency);`; :556 `QSemaphore inFlight(concurrency);`. intruder_pool_logic.cpp:5-8 clampConcurrency 1..kMaxConcurrency. tabs.jsx:2285-2292 CONC input (min=1 max=64, dispatches intruder-set{concurrency}).","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Resource pool: throttle / delay","s":"present","i":"low","e":"hours","g":"Fixed delay only; no randomized/variable delay (Burp offers a delay with random variance).","w":"Re-read dispatch loop + clamp + rps alias + GUI. Fixed inter-dispatch delay confirmed.","v":"intruder.cpp:730 `if (throttleMs > 0) interruptibleSleep(throttleMs, m_stopRequested);` in the main dispatch loop (a second site at :708 covers the recursive-grep pipe branch). intruder_pool_logic.cpp:11-14 clampThrottleMs 0..kMaxThrottleMs; :28-30 rpsToDelayMs. tabs.jsx:2294-2301 THROTTLE·MS input.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Results table: filtering","s":"present","i":"medium","e":"days","g":"None -- the RESULTS pane gained 2xx/3xx/4xx/5xx toggle chips, min/max response-length filters, and a regex (with leading '-' negation) search box over payload+extracted text, composed with the existing hide-404 checkbox via a new pure intruderRowVisible() predicate.","w":"Closed 2026-08-09: replaced the single hardcoded hide-404 checkbox with a full filter bar; all fields were already client-side (intruder.results), so this is a pure ui-v2 predicate change verified with a Node functional test covering every filter dimension plus fail-open on an invalid regex.","v":"ui-v2/tabs.jsx intruderRowVisible() (pure, exported for testing) + IntruderTab RESULTS filter bar.","o":"partial","r":"Intruder wave: results filter bar closes the filtering gap (partial -> present)."},{"a":"intruder","f":"Save/Resume attack","s":"present","i":"medium","e":"days","g":"None — loadRun restores every row's raw combo + completion flag, and resume() re-fires ONLY the never-completed rows over the same worker (completed rows keep their results). Exposed as Q_INVOKABLE resume(), POST /api/intruder/resume, and a ▷ RESUME button next to SAVE/LOAD.","w":"Closed 2026-08-29: added Intruder::resume() + a skipRows filter on runWorker's dispatch loop; the pure resume decision (IntruderPersist::planResume — recursive-grep unresumable, all-complete = nothing to resume, else skip the completed indices) is unit-tested + mutation-proven, and the firing reuses the proven start()/runWorker path over the round-trip-restored combos.","v":"Src/Core/Networking/intruder.cpp: saveRun/loadRun/resume; ui-v2/tabs.jsx: SAVE/LOAD/RESUME; bin/nullock: intruder save/load/reset; Tests/intruder_persist_logic/intruder_persist_logic_test.cpp; scripts/intruder_workspace_regression.py: project restoration remains idle and preserves completed/pending rows.","o":"present","r":"Existing manual SAVE/LOAD/RESUME is retained. Project switch and clean exit now save automatically; restoration remains idle and pending rows still need explicit Resume. CLI adds save/load/reset."},{"a":"intruder","f":"Resend / re-issue a single result row","s":"present","i":"low","e":"hours","g":"","w":"Re-read resend(); re-fires the stored combo through the current template on a separate worker. GUI ↻ button present.","v":"intruder.cpp:749-787 Intruder::resend(row) re-applies m_payloadRules to a->m_combo and runs it through m_resendWorker on a QtConcurrent worker. tabs.jsx:2699-2705 per-row ↻ button calling NL.actions.intruderResend(i).","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Send to Intruder from other tools","s":"present","i":"low","e":"hours","g":"None -- a + § button in the TEMPLATE pane wraps the current textarea selection in §markers§, matching Burp's Add-§ control; manual placement by editing the textarea was already possible.","w":"Closed 2026-08-09: added the +§ button (reads templateRef.current.selectionStart/End) alongside the pre-existing send-to-intruder auto-mark and editable template textarea.","v":"ui-v2/tabs.jsx IntruderTab TEMPLATE pane-head +§ button; app.jsx:77 send-to-intruder auto-mark (pre-existing).","o":"present","r":"Intruder wave: +§ selection-wrap button closes the interactive marking gap."},{"a":"intruder","f":"Full-speed Intruder (no artificial throttle)","s":"exceeds","i":"low","e":"hours","g":"","w":"Re-read fire loop; no time-throttle unless the user sets one, concurrency defaults to 10 and dispatches immediately. Genuinely beats Burp Community's deliberate rate limit.","v":"intruder.cpp:724-730 dispatch loop fires each combo via QtConcurrent::run immediately; throttle only applied `if (throttleMs > 0) interruptibleSleep(...)`. intruder_pool_logic.hpp:18 kDefaultConcurrency=10. No artificial per-request delay unless the user sets one.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Interruptible attack + safe shutdown mid-run","s":"present","i":"low","e":"hours","g":"","w":"Re-read stop(), the sliced sleeps, and the destructor join. All confirmed.","v":"intruder.cpp:419-422 stop() sets m_stopRequested; :724-727 dispatcher checks before and after acquire; :110-118 interruptibleSleep slices the wait; :125-139 ~Intruder sets stop then waitForFinished on worker+resend+pool before qDeleteAll.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Payload type: Runtime file","s":"absent","i":"medium","e":"days","g":"No way to stream payloads line-by-line from a large file; everything must be loaded into the textarea/memory.","w":"Re-grepped intruder sources for QFile/readFile/fromFile/runtime — nothing. types() lists only numbers/brute/dates. Confirmed absent.","v":"intruder_generators.cpp:337-344 types() now returns 13 generator types (numbers/brute/dates/null/frobber/blocks/casemod/charsub/bitflip/username/illegal-unicode/ecb-shuffle/iterator), up from the 3 last cited here -- still none reading from a file. No QFile/file-streaming reference anywhere in intruder*.cpp/hpp.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Payload type: Custom iterator","s":"present","i":"low","e":"days","g":"Implemented as a positional cartesian-product generator: IntruderGenerators::customIterator(positions, separator) emits every combination pos[0][i]+sep+pos[1][j]+... in odometer order (last position varies fastest), reachable via type \"iterator\" on /api/intruder/generate and /api/intruder/set. Matches Burp's core custom-iterator behaviour; the only nicety not carried is a DISTINCT separator per position (one shared between-positions separator instead) -- noted as a possible enhancement, not a gap that blocks the use case.","w":"Implemented + mutation-proven, following the exact pattern the other 12 payload generators use (all marked present): a pure Qt6::Core-linkable IG function + expandGen dispatch + types() entry. Bounded at kMaxCount by capping the working set after EACH position, so a huge product truncates in COUNT while every emitted payload stays a COMPLETE combination (never a length-truncated fragment) and never OOMs.","v":"intruder_generators.cpp:314 customIterator(); types() (:344) lists \"iterator\"; control_server.cpp:3648 expandGen `if (t == \"iterator\")` parses positions (arrays or newline-joined) + separator. Tests/intruder_generators/intruder_generators_test.cpp (107 pass): odometer order + separator, no-separator concat, single-position no-sep, 3-position join, empty/empty-factor -> empty, and 47^3 capped at kMaxCount with every payload complete; M1 (drop separator) + M2 (drop cap) each fail only their targeted case. Live: POST type=iterator positions=[[a,b],[1,2,3]] sep=- -> a-1..b-3 (count 6).","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Payload type: Character substitution","s":"present","i":"low","e":"hours","g":"Cannot emit progressive substrings of a value as payloads.","w":"Grep over intruder sources for substring returns nothing; no generator emits progressive substrings.","v":"intruder_generators.cpp only defines numbers/brute/dates; intruder_rules.cpp operations() (55-70) has no substring.","o":"present","r":"Closed 2026-08-12. NAME CORRECTED: the audit labelled this 'Character substring' with a 'progressive substrings' gap, but Burp Intruder has no 'substring' payload type -- its documented type is 'Character substitution' (leetspeak). Implemented that (the real Burp feature): IntruderGenerators::charSub(items, subs) emits, per item, all 2^k permutations of applying-or-not each substitutable character position (e.g. peter + {e:3,t:7} -> peter/p3ter/pe7er/p37er/pet3r/p3t3r/pe73r/p373r), enumerated leftmost-position-as-LSB to match Burp's order. Verified against the PortSwigger docs. Wired into control_server expandGen (t==charsub, items from array/newline, subs from a {char:char} object) + types(). Unit- + mutation-tested (linearising the 2^k enumeration fails the multi-position cases)."},{"a":"intruder","f":"Payload type: Case modification","s":"present","i":"low","e":"hours","g":"No payload type that expands one word into its case permutations.","w":"Confirmed: case exists only as a processing rule (uppercase/lowercase), not as a payload generator that expands one word into case variants.","v":"intruder_generators.cpp:89-91 types() has no 'case'; intruder_rules.cpp:15-16 has the global uppercase/lowercase rules only.","o":"present","r":"Closed 2026-08-11: added IntruderGenerators::caseMod(items, modes) -- for each item, one payload per enabled case option in canonical order, item-major, no dedup. The FIVE Burp options confirmed from the PortSwigger docs (a vetting-agent 4-mode proposal was wrong): No change / lower / upper / Propername (first cp upper, rest LOWER) / ProperName (first cp upper, rest UNCHANGED). Distinct from the 1:1 intruder_rules uppercase/lowercase transforms -- this is a list-multiplying payload TYPE. First char upper-cased by code point (non-BMP safe). Wired into control_server expandGen (t==casemod, items from array/newline-split, modes from a token array defaulting to all five). Unit- + mutation-tested (collapsing Propername's lower-rest fails the lower-rest cases; the Propername vs ProperName distinction is the docs' 'critical difference')."},{"a":"intruder","f":"Payload type: Recursive grep","s":"partial","i":"high","e":"weeks","g":"No chaining an extracted value into the next request; blocks CSRF-token/nonce walking and stateful sequences.","w":"Re-read the fire loop. computeGrep results are stored on the row and never fed forward into the next request's payload. Confirmed absent.","v":"intruder.cpp:445-507 fireOne computes grep (484-487) and posts it to the row; combos are pre-generated at :376-378 before firing — no path takes a response-N extract into request N+1.","o":"absent","r":"ENGINE done (the hard part the audit called 'weeks'): the extract IS now fed forward. Recursive grep runs as a SERIAL branch in Intruder::runWorker -- each request's payload is the value the grep-EXTRACT spec pulls from the PREVIOUS response, walked from a `seed` for `count` requests, stopping early when a response yields no extract (chain ended). fireOne was refactored to RETURN its extracted value (it already computed it for the result column) and to record the runtime-discovered payload into the row; start() reserves `count` placeholder rows and forces concurrency 1 (the run is inherently serial -- each request depends on the prior response); it reuses the existing IntruderGrep::grepExtract spec as the payload source, so no new extraction code. Config via /api/intruder/set { recursiveGrep, recursiveGrepSeed, recursiveGrepCount }; snapshot exposes intruder.recursiveGrep. VERIFIED e2e against a chaining mock: a 5-request walk carried exactly [seed, TOK0, TOK1, TOK2, TOK3] (each request carried the PRIOR response's extracted token -- the chain proven), result rows recorded the extracted token + the payload used, `count` bounded the run, and a dried-up token stopped the chain early (fired 3 of 10). Gauntlet ctest 98/98 + probe_smoke 156/156. This is the classic anti-CSRF-bruteforce / one-time-nonce / state-machine walk. REMAINDER (-> stays partial): the ui-v2 payload-type selector + seed/count fields (concurrent-agent lane), save/resume (RunConfig) of a recursive attack, and multi-position recursive (only position 0 carries the recursive value today, Sniper-style)."},{"a":"intruder","f":"Payload type: Illegal Unicode","s":"present","i":"low","e":"hours","g":"None -- an overlong-UTF-8 payload generator emits the illegal 2..6-byte encodings of a target character (WAF / path-normalization bypass).","w":"Closed 2026-08-12: added IntruderGenerators::illegalUnicode (overlong UTF-8 of the target code point at each 2..6-byte length, hex/%-prefixed, semantics confirmed vs PortSwigger), advertised in types() + dispatched by control_server expandGen ('illegal-unicode'); pure + mutation-proven.","v":"intruder_generators.cpp illegalUnicode + types(); control_server.cpp expandGen illegal-unicode branch; Tests/intruder_generators (+7 cases incl. the exact '/' overlong ladder, mutation-proven lead prefix + continuation marker).","o":"present","r":"Intruder wave: Illegal Unicode payload type -- overlong UTF-8 encodings (2..6 bytes) of a target char, %C0%AF-style (PortSwigger-verified); pure + mutation-proven, no engine wiring."},{"a":"intruder","f":"Payload type: Character blocks","s":"present","i":"low","e":"hours","g":"No generator producing blocks of a repeated character at increasing sizes (buffer/limit testing).","w":"Grep for char-block returns nothing; no repeated-character block generator.","v":"intruder_generators.cpp:89-91 types() lists only numbers/brute/dates.","o":"present","r":"Closed 2026-08-11: added IntruderGenerators::charBlocks(base,minMult,maxMult,step) -- one payload per multiplier k in [minMult,maxMult] step, each `base` repeated k times (base x k). Semantics verified against the PortSwigger docs: Burp MULTIPLIES/whole-repeats the base, it does NOT truncate to a length (my first guess was truncate -- the docs corrected it). Wired into control_server expandGen (t==blocks) + types()={numbers,brute,dates,null,frobber,blocks}. Bounded in count + total chars, refuses to build an over-cap block (no OOM). Unit- + mutation-tested (replacing repeated(k) with left(k) fails the exact-output cases)."},{"a":"intruder","f":"Payload type: Null payloads","s":"present","i":"medium","e":"hours","g":"Cannot fire the same base request N times (session/CSRF/timing tests) without a real payload list.","w":"Confirmed: the only 'null' concept is the null-combo default for unfilled markers, not a null-payloads type that fires the base request N times.","v":"intruder_engine.cpp:64 `const QString def = QString(); // null => use the marker's own default`; no null-payloads generator in types().","o":"present","r":"Closed 2026-08-11: added IntruderGenerators::nullPayloads(count) -- emits `count` empty payloads so a position is filled with nothing and the base request is re-sent unchanged N times (Burp's Null payloads: rate-limit / race / non-determinism probing). Wired into control_server expandGen (/api/intruder/generate + /set) and advertised by types()={numbers,brute,dates,null}. count<1 -> empty; capped at kMaxCount. Unit- + mutation-tested (emitting a non-empty payload fails the emptiness assertions; the size/count checks pass)."},{"a":"intruder","f":"Payload type: Character frobber","s":"present","i":"low","e":"hours","g":"No type that increments each character of the base value in turn.","w":"Grep 'frobber' over the whole repo returns nothing. Confirmed absent.","v":"No match for 'frobber' in Src/Core/Networking; intruder_generators.cpp types() has none.","o":"present","r":"Closed 2026-08-11: added IntruderGenerators::frob(base) -- one payload per code-point position, each the whole base with that position's code point +1 (Burp Character frobber). Code-point safe (toUcs4; surrogate-range bump -> 0xE000, past 0x10FFFF -> 0) and bounded in count + total chars (O(L^2)). Wired into control_server expandGen (t==frobber -> g[base]) + types()={numbers,brute,dates,null,frobber}. Semantics verified against PortSwigger docs by the vetting workflow's adversarial pass; unit- + mutation-tested (a +2 increment fails the exact-output cases)."},{"a":"intruder","f":"Payload type: Bit flipper","s":"present","i":"medium","e":"days","g":"No bit-flipping type for CBC/padding-oracle and encrypted-token fuzzing.","w":"Grep 'bit.?flip' over the repo returns nothing. Confirmed absent.","v":"No bit-flip generator in intruder_generators.cpp; types() lists numbers/brute/dates only.","o":"present","r":"Closed 2026-08-12: added IntruderGenerators::bitFlip(base) -- per byte of the base (its UTF-8 bytes), one payload per bit position 0..7 with that single bit XOR-flipped, byte order left-to-right, bit order LSB(0x01)->MSB(0x80). Matches Burp's documented output exactly (ab -> `b,cb,eb,ib,qb,Ab,!b,ab-with-0xE1, ac,a`,af,aj,ar,aB,a-quote,a-with-0xE2), verified against the PortSwigger docs; flipped bytes render via Latin-1 as Burp displays them. Wired into control_server expandGen (t==bitflip) + types(). Unit- + mutation-tested (OR-instead-of-XOR fails the exact-output list). Caveat noted in the header: an MSB flip yields a >=0x80 byte that a string payload re-encodes to two UTF-8 bytes on the wire; the 7 lower-bit flips are byte-exact."},{"a":"intruder","f":"Payload type: Username generator","s":"present","i":"low","e":"hours","g":"None -- a name/email -> username permutation generator produces the common schemes (concatenations, dot/underscore/hyphen separated, reversed order, first/last-initial combos).","w":"Closed 2026-08-12: added IntruderGenerators::usernameGen (semantics confirmed vs PortSwigger), advertised in types() and dispatched by control_server expandGen ('username', arg 'name'); pure, deduped, capped, mutation-proven.","v":"intruder_generators.cpp usernameGen + types(); control_server.cpp expandGen username branch; Tests/intruder_generators (+17 cases, mutation-proven initial + email handling).","o":"present","r":"Intruder wave: Username generator payload type -- name/email -> username candidates via common schemes (PortSwigger-verified), lower-cased/deduped/capped; pure + mutation-proven, no engine wiring."},{"a":"intruder","f":"Payload type: ECB block shuffler","s":"present","i":"low","e":"days","g":"None -- a hex ciphertext is split into blockSize-byte blocks and the block-permutation variants are emitted (deduped, capped). The classic ECB token-forgery shuffle.","w":"Closed 2026-08-12: added ecbBlockShuffle (see reconciled).","v":"intruder_generators.cpp ecbBlockShuffle + types(); control_server.cpp expandGen ecb-shuffle branch; Tests/intruder_generators (+9 cases, mutation-proven align guard + dedup).","o":"present","r":"Added IntruderGenerators::ecbBlockShuffle -- hex ciphertext -> blockSize-byte blocks -> the complete deduped block-permutation set (capped), dispatched via expandGen ('ecb-shuffle'); pure + mutation-proven, fail-safe on non-hex/misaligned input. (Burp's optional 'additional encrypted strings' block-pooling is a future refinement.)"},{"a":"intruder","f":"Payload type: Extension-generated (payload provider)","s":"absent","i":"medium","e":"weeks","g":"Extensions cannot supply Intruder payloads or attack types (no payload-provider API wired to Intruder).","w":"Re-read the entire intruder.cpp; start()/runWorker/fireOne never call any extension hook. No IIntruderPayloadGenerator equivalent exists.","v":"intruder.cpp:437 start() and :613 runWorker build combos purely from m_payloadSets + generators; `grep -n extension Src/Core/Networking/intruder.cpp` returns no hits -- no extension hook anywhere on the payload path.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Processing rule: Substring / Reverse substring","s":"present","i":"low","e":"hours","g":"None -- substring (0-indexed start offset + optional length) and reverse-substring (end offset + length counted from the end) are both processing ops, code-point-safe and fail-safe.","w":"Closed 2026-08-12: added substring + reverse-substring ops to applyRule (arg = 'offset' or 'offset,length', semantics verified vs PortSwigger), advertised in operations(); pure + mutation-proven. No engine wiring needed -- rules round-trip as {op,arg} via the control API.","v":"intruder_rules.cpp applyRule substring/reverse-substring branch + operations(); Tests/intruder_rules (+12 cases, mutation-proven start-offset + reverse end-offset).","o":"present","r":"Intruder wave: substring + reverse-substring payload-processing ops (PortSwigger-verified semantics), code-point-safe, fail-safe on out-of-range; pure + mutation-proven, no engine wiring."},{"a":"intruder","f":"Processing rule: Decode","s":"present","i":"low","e":"hours","g":"MISCLASSIFICATION. The decode capability already EXECUTES: applyRule delegates any non-local op to Transcode::apply (intruder_rules.cpp:45-46), and Transcode::apply supports base64-decode/base64url-decode/url-decode/html-decode/hex-decode/jwt-decode (transcode.cpp:243-248). So passing op=\"base64-decode\" as a rule already decodes today. Only the discovery list operations() deliberately omits them (","w":"Reclassified absent -> partial (2026-08-02): independent triage + adversarial-verify agreed; cited files re-confirmed to exist. See PARITY-BACKLOG.md.","v":"intruder_rules.cpp:45-46 fallthrough to Transcode::apply(op,value); transcode.cpp:229-235 ops() and :243-248 apply() implement base64/url/html/hex/jwt decode; intruder_rules.cpp:56-58 comment excludes them from the advertised list only.","o":"present","r":"Closed 2026-08-11: operations() now advertises the decode inverse of each advertised reversible encode -- base64-decode/base64url-decode/url-decode/hex-decode/html-decode -- matching Burp's Decode payload rule. The ops already executed (applyRule -> Transcode::apply) and fail safe (a decode of non-decodable input is a no-op), so this only closes the discoverability gap; /api/intruder/rule-ops (control_server.cpp:3305) serves operations() verbatim so the UI dropdown picks them up. The prior blanket exclusion ('payloads are authored, not received') was re-derived as incomplete -- payload lists routinely arrive pre-encoded. Round-trips unit- + mutation-tested. Non-payload decodes (jwt-decode multi-line JSON; octal/binary-decode, no advertised encoder) stay unadvertised but still run if named."},{"a":"intruder","f":"Processing rule: Add raw payload","s":"present","i":"low","e":"hours","g":"None -- add-raw-payload is a new local op in the processing-rule chain: it appends the ORIGINAL, pre-chain payload value regardless of what earlier rules already did to the running value, so e.g. [sha256] -> [add-raw-payload] yields \"<hash><rawvalue>\" for sign-then-send patterns.","w":"Closed: applyRule/applyRules only ever saw the current running value, with no way to reach back to the pre-chain original once an earlier rule had transformed it. Gave applyRule a third `original` parameter (the 2-arg overload defaults it to `value` itself, preserving every existing call site and test) and had applyRules thread the constant pre-chain value through as `original` on every step, so add-raw-payload works correctly no matter where it sits in the chain or how many times it repeats.","v":"Src/Core/Networking/intruder_rules.hpp:56-57 (applyRule 3-arg + 2-arg overloads), intruder_rules.cpp:28-35 (add-raw-payload op + original threading), :169-172 (applyRules passes the constant original), operations() now advertises add-raw-payload; ui-v2/tabs.jsx RULE_OPS_FALLBACK includes it (the live list already comes from GET /api/intruder/rule-ops -> IntruderRules::operations(), control_server.cpp:3635-3639); Tests/intruder_rules/intruder_rules_test.cpp adds 5 checks (standalone self-append, appends original past an earlier transform, sha256-then-raw sign-then-send pattern, repeated add-raw-payload chain, operations() advertisement).","o":"absent","r":"absent -> present. Burp Payload Processing rule \"Add raw payload\": re-inserts the unmodified original payload at that point in the chain, most commonly used after a hash/encode step to build a sign-then-send value (hash+raw). The engine (intruder_rules.cpp) previously threaded only the running value through each rule with no notion of the untouched pre-chain original, so there was no way to get back to it once an earlier rule (e.g. sha256) had overwritten the running value. Added a third `original` parameter to applyRule (2-arg overload defaults it to value, so every existing call site and the 40+ existing unit tests are untouched) and have applyRules thread the constant pre-chain payload through as `original` on every step of the loop, so add-raw-payload appends the true original no matter where it sits in the chain or how many times it repeats. New op registered in operations() (auto-flows to the GUI dropdown via the existing /api/intruder/rule-ops -> ruleOps live-fetch, ui-v2/tabs.jsx:1642-1648) plus added to the static RULE_OPS_FALLBACK for when that fetch fails. 5 new unit tests in Tests/intruder_rules/intruder_rules_test.cpp lock the standalone self-append semantics, correct original-vs-running-value behavior after an earlier transform, the sha256-then-raw sign-then-send pattern named in the prior gap text, a repeated-in-chain case, and operations() advertisement. Backend C++ change this cloud session cannot build locally -- pushed and will be confirmed against a green GitHub Actions ctest run (ctest -R intruder_rules) before being called fully verified; documented here as the honest state at push time per this file's convention for cloud session C++ waves."},{"a":"intruder","f":"Processing rule: Skip if matches regex","s":"present","i":"low","e":"hours","g":"None -- a `skip-if-matches` processing rule (arg = regex) drops any payload whose transformed-so-far value matches, before the request is fired. The skip-aware applyRules(value, rules, bool* skipped) overload signals the drop; Intruder::start() filters skipped combos out before result rows are built, so the sent-request count and the table reflect only surviving payloads (Burp's behaviour). An empty/invalid pattern never skips.","w":"Closed 2026-08-24: added the skip signal to the rule chain (skip-aware applyRules overload; the 2-arg path is a safe no-op so a payload never vanishes where a caller cannot honour a skip) and the combo filter in Intruder::start(). Advertised in operations() for UI discovery. Mutation-proven.","v":"intruder_rules.cpp:174-195 applyRules(value,rules,bool*): a `skip-if-matches` rule (op registered :219) matching the running value sets *skipped and returns; intruder.cpp:460-475 Intruder::start() drops combos whose processed payload skips, before beginResetModel (:479)/row build. Tests: intruder_rules_test.cpp:208-237 -- a payload matching the regex is skipped, a non-match is kept, the plain 2-arg path never drops, the match is against the TRANSFORMED value, and empty/invalid patterns never skip.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Processing rule: Invoke extension","s":"absent","i":"low","e":"weeks","g":"No extension-backed payload processing.","w":"Confirmed: applyRule op set is fixed; no branch calls into an extension.","v":"intruder_rules.cpp:32-172 applyRule's op dispatch is a fixed if-chain (add-raw-payload/prefix/suffix/uppercase/lowercase/propername/reverse/match-replace/regex-replace/url-encode-chars/substring/reverse-substring) falling back to Transcode::apply for everything else; no extension call anywhere on the rule path.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"intruder","f":"Payload encoding (global 'URL-encode these characters')","s":"present","i":"medium","e":"hours","g":"None -- the global 'URL-encode these characters' safety net is implemented: a configured character set is percent-encoded in every payload.","w":"Closed 2026-08-12: added a code-point-safe `url-encode-chars` payload-processing op (percent-encodes ONLY the listed chars, byte-by-byte over UTF-8) and wired Intruder::setGlobalEncodeChars to append it as the FINAL step of every payload's chain (full run + single-row resend), configured via `encodeChars` on /api/intruder/set. Off by default so existing attacks are unchanged.","v":"intruder_rules.cpp url-encode-chars op + operations(); intruder.cpp setGlobalEncodeChars + effective-chain append at the run and resend sites; control_server.cpp /api/intruder/set encodeChars; Tests/intruder_rules (+11 cases, mutation-proven).","o":"present","r":"Intruder wave: global URL-encode-these-characters safety net via a code-point-safe url-encode-chars op appended to every payload's processing chain; opt-in (empty=off), mutation-proven."},{"a":"intruder","f":"Grep - Payloads (flag reflected payloads)","s":"present","i":"medium","e":"hours","g":"None -- an automatic reflection column flags a row when one of its submitted payloads echoes literally in the response.","w":"Closed 2026-08-12: added IntruderGrep::payloadReflected (LITERAL substring, bounded, never regex -- a payload is data not a pattern) and wired it into computeGrep as a per-row `reflected` flag driven by the row's combo, exposed via a ReflectedRole/Q_PROPERTY, toggled by `grepPayloads` on /api/intruder/set, and persisted across save/resume. Off by default.","v":"intruder_grep.cpp payloadReflected + Tests/intruder_grep (+11, mutation-proven); intruder.cpp computeGrep reflected-out + ReflectedRole + setGrepPayloadReflection + run/resend compute; intruder_persist_logic AttackRow.reflected + RunConfig.grepPayloadReflection JSON round-trip; control_server.cpp grepPayloads.","o":"present","r":"Intruder wave: automatic reflected-payload column via a literal (non-regex) payloadReflected predicate; per-row flag, persisted, opt-in, mutation-proven."},{"a":"intruder","f":"Follow redirections (never/on-site/in-scope/always)","s":"present","i":"medium","e":"days","g":"","w":"Re-read Intruder::resend() after wiring the redirect-follow block into it and diffed it line-by-line against fireOne(); both now build the same RL::requestUrl/resolveRedirect/followAllowed/mergeSetCookies/buildFollowRequest chain off identical captured state. Confirmed present.","v":"intruder.cpp fireOne() (attack-fire path) and resend() (single-row re-fire path, intruder.cpp:640-745) both now call the shared RedirectLogic chain-follow block on a 3xx result -- resend mirrors fireOne exactly (same requestUrl/resolveRedirect/followAllowed/mergeSetCookies/buildFollowRequest sequence, up to kMaxRedirectHops), using the same m_followPolicy/m_followCookies/m_inScope state the /api/intruder/set FOLLOW select and COOKIES checkbox (fcbe737) already drive.","o":"present","r":"Closes the one remaining gap this item named after fcbe737: Intruder::resend() (the single-row re-fire path off a completed attack) now runs the same redirect-follow block as fireOne() (the attack-fire path) -- built from a captured-by-value copy of m_followPolicy/m_followCookies/m_inScope, identical chain-walk logic (isRedirectStatus / resolveRedirect / followAllowed / mergeSetCookies / methodAfterRedirect / redirectPreservesBody / buildFollowRequest), capped at kMaxRedirectHops. A resent row now grades against the same final page a first-pass fired row does. No new pure logic was added -- this reuses RedirectLogic, already unit-tested + mutation-proven by the Repeater wave -- so no new unit tests were required; the change is a direct structural mirror of the already-verified fireOne() block, confirmed line-by-line against it. Backend-only, no frontend change (the FOLLOW/COOKIES controls already apply to every resend since resend reads the same m_followPolicy/m_followCookies instance fireOne does). This cloud session cannot build/run the C++ side itself; will confirm the next GitHub Actions ci run is green before treating this as fully closed CI-wise (same honest-partial pattern this file has used before for backend-only changes)."},{"a":"intruder","f":"Resource pool: retries on network failure","s":"present","i":"low","e":"hours","g":"None -- a RETRIES field (0..5, backend-clamped) in the Intruder target row lets the operator configure a resend count for a NETWORK-level failure only (connect refused/timeout/reset); an HTTP error status is never retried since it's a real result, not a transport failure. Resent on the same pool thread so it never blocks other in-flight requests, and stops early on Stop so a cancelled attack doesn't burn through every retry against a dead target first.","w":"Closed 2026-08-25: added Intruder::setMaxRetries/maxRetries (clamped via a new IntruderPool::clampRetries, 0..kMaxRetries=5) threaded through runWorker/fireOne -- on !result.ok (network failure, not an HTTP status), fireOne re-sends via the same HttpClient up to `retries` more times, checking m_stopRequested between attempts. Wired through /api/intruder/set{retries} and the snapshot's intruder.retries field, a RETRIES number input next to CONC/THROTTLE·MS in the Intruder target row (ui-v2/tabs.jsx), and saveRun/loadRun (IntruderPersist::RunConfig.retries) so a saved attack round-trips it too.","v":"Src/Core/Networking/intruder_pool_logic.{hpp,cpp} kMaxRetries/clampRetries; Src/Core/Networking/intruder.{hpp,cpp} m_maxRetries/setMaxRetries/maxRetries, runWorker's new `retries` parameter, fireOne's retry loop around client.send, saveRun/loadRun; Src/Core/Networking/intruder_persist_logic.{hpp,cpp} RunConfig.retries; Src/BackEnd/Control/control_server.cpp intruder[\"retries\"] snapshot field + set-handler's bodyJson.contains(\"retries\") branch; ui-v2/tabs.jsx RETRIES field in IntruderTab's pool-config row.","o":"present","r":"Intruder resource-pool batch: RETRIES (0..5, network-failure-only resend, HTTP status codes never retried) closes the last 'hours'-effort intruder pool-config gap."},{"a":"intruder","f":"Results table: sortable columns","s":"present","i":"high","e":"days","g":"None -- every results-table header is click-to-sort (numeric-aware for status/size/ms/matched, string-aware for payload/extracted/err), tracked via a new pure intruderSortValue() accessor; the resend button still targets the original row index after sorting/filtering.","w":"Closed 2026-08-09: added sortKey/sortDir state and onClick handlers to every <th>, sorting a derived {p,i,r} row list (i = original index, preserved through filter+sort) rather than intruder.payloads directly. Verified with a Node functional test including a numeric-vs-lexicographic ordering check.","v":"ui-v2/tabs.jsx intruderSortValue() (pure, exported for testing) + IntruderTab RESULTS <thead> onClick handlers.","o":"absent","r":"Intruder wave: sortable results columns close the sortable-columns gap (absent -> present)."},{"a":"scanner","f":"[A1] Crawl: build site map by link-following (spider)","s":"partial","i":"medium","e":"weeks","g":"Static HTML only (crawler.cpp:154 'Doesn't run JS'); no navigation-graph diffing, no volatile-content handling. The GUI-reachability half of this gap is closed: the DISCOVER tab (ui-v2/app.jsx DiscoverTab) has a start/stop crawl control (seed URL + max-pages/max-depth/throttle-ms) wired to /api/crawler/start,stop, with crawled pages feeding straight into Proxy history. Remaining gap is the JS-rendering/diffing engine work itself, not GUI wiring.","w":"Register-accuracy fix: this item's gap text still said \"Also API-only: no crawl button/tab in the shipped UI\", stale since a prior Wave 2 batch (3494297, 2026-08-13) added the DISCOVER tab's crawl-config UI on top of an already-existing crawl start/stop control -- confirmed live by grep of ui-v2/app.jsx (DiscoverTab startCrawl/stopCrawl calling NL.actions.crawlerStart/crawlerStop) and TABS (discover entry, chrome.jsx render switch). State stays partial: the crawler is still static-HTML-only with no JS execution or diffing (crawler.cpp:154), the real remaining gap; only the previously-stale GUI-reachability clause is corrected.","v":"crawler.cpp:84 `m_worker = QtConcurrent::run([this]() { while (... m_visited < m_maxPages && !m_queue.isEmpty()) { ... crawlOne(u); ...}});`  crawler.cpp:163-166 refs += extractSrcset/extractMetaRefresh/extractFormGets","o":"","r":"Register-accuracy fix: corrected stale \"no crawl button/tab in the shipped UI\" gap text -- the DISCOVER tab has shipped a full crawl start/stop + config UI since 3494297 (2026-08-13). State unchanged (partial); only gap/why corrected to reflect the true remaining gap (no JS rendering/diffing)."},{"a":"scanner","f":"[A2] Crawl: automatic form submission / registration during crawl","s":"stub","i":"medium","e":"weeks","g":"No form is submitted with generated data, no auto-fill, no account registration to reach deeper states. Burp submits forms to expand coverage; Nullock only appends GET-form param names to the crawl frontier.","w":"Downgraded partial->stub. Re-read crawler_logic.cpp:90-116: extractFormGets only turns GET-form field NAMES into empty-valued query strings ('?n1=&n2=') to crawl as URLs. Nothing is ever SUBMITTED: no POST, no value generation, no registration. Line 103 explicitly '(a POST form isn't a URL surface)'. So the capability 'automatic form submission' is not implemented; only GET-form param-name surfaci","v":"crawler_logic.cpp:111 `for (const QString &n : names) q += (q.isEmpty() ? \"?\" : \"&\") + n + \"=\";`  line 103 `if (!methodGet.match(attrs).hasMatch()) continue;   // GET forms only`","o":"","r":"Wave 0 register-accuracy audit: held at stub. Re-verified crawler_logic.cpp:90-114 extractFormGets -- GET forms only (methodGet.match guard at :103), field NAMES turned into empty-valued query params (:111 `q += ... + n + \"=\";`), never a POST, never a filled value, no registration flow. Line numbers unchanged, content unchanged. No code change this pass."},{"a":"scanner","f":"[A3] Crawl configuration: max depth, max locations, crawl limits","s":"partial","i":"low","e":"days","g":"No max-unique-locations, per-directory limits, crawl-budget, or coverage-strategy toggles -- Nullock's crawler only exposes three knobs (max pages, max depth, per-request throttle), matching a small slice of Burp's crawl-configuration surface. Still partial for that reason, but the three existing knobs are now settable from the Discover tab's GUI instead of only the raw /api/crawler/start JSON body.","w":"Re-read crawler.cpp:67-69: qBound(1,maxPages,5000), qBound(0,maxDepth,10), qBound(0,throttleMs,60000) -- exactly three knobs, as claimed. GUI-reachability gap closed 2026-08-13: the Discover tab's crawler control row gained max-pages/max-depth/throttle-ms number inputs (defaulting to the backend's own defaults 200/4/200), wired through NL.actions.crawlerStart's existing seed/maxPages/maxDepth signature plus a new throttleMs 4th argument, straight to the already-complete /api/crawler/start {seed,maxPages?,maxDepth?,throttleMs?} contract (control_server.cpp:4092-4101). No backend touched -- the contract already accepted all three fields, only the GUI to set them was missing.","v":"crawler.cpp:67 `m_maxPages = qBound(1, maxPages, 5000); m_maxDepth = qBound(0, maxDepth, 10); m_throttleMs = qBound(0, throttleMs, 60'000);`","o":"","r":"Discover tab's crawler control row (ui-v2/app.jsx DiscoverTab) gains max pages / max depth / throttle (ms) number inputs, disabled while a crawl is running, passed through a new 4th throttleMs argument on NL.actions.crawlerStart (ui-v2/real-data.js) to the existing /api/crawler/start contract. Still partial: Burp's fuller crawl-configuration surface (max-unique-locations, per-directory limits, crawl-budget, coverage-strategy) has no Nullock equivalent at all, backend or frontend -- that remains a real gap, not just a GUI one."},{"a":"scanner","f":"[A4] Passive audit: missing security headers (CSP/HSTS/XFO/XCTO/RP/Permissions-Policy/COOP/COEP/CORP)","s":"present","i":"low","e":"hours","g":"","w":"Passive checks run on proxied responses. XCTO and Referrer-Policy now use shared effective-value parsing: the first nosniff token controls MIME protection, and the last recognized referrer policy survives unknown fallback keywords. Malformed tokens and nonbreaking spaces cannot count as configured protection.","v":"Src/Core/Networking/passive_scanner.cpp; response_header_values.cpp; networking_logic.cpp; Src/BackEnd/Proxy/proxy_logic.cpp; Tests/scanner_regression/scanner_regression_test.cpp; Tests/header_audit/header_audit_test.cpp; Tests/ui/header_values_browser_test.cjs; scripts/probe_smoke.sh.","o":"present","r":"Hardened active and passive security-header parsing for repeated fields, fallback policies and malformed whitespace. Native regressions and pinned Chromium comparisons cover effective values. Existing capability remains present."},{"a":"scanner","f":"[A5] Passive audit: cookie security flags + prefixes","s":"present","i":"low","e":"hours","g":"","w":"Re-read passive_scanner.cpp:249-260 (no-httponly/no-secure gated on wasTls/no-samesite) and 456-488 (__Secure- prefix, __Host- prefix with tokenized Path=/ check, broad-path-no-samesite). Present and live per response.","v":"passive_scanner.cpp:250 cookie-no-httponly; :457 cookie-secure-prefix-violation; :476 cookie-host-prefix-violation; :485 cookie-broad-path-no-samesite (uses tokenized pathRoot, not substring)","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A6] Passive audit: CORS misconfiguration","s":"present","i":"low","e":"hours","g":"","w":"Re-read passive_scanner.cpp:283-292 (wildcard+creds high / wildcard info) and 766-793 (origin-reflection-with-creds high, null-origin medium, ACAM/ACAH wildcard). All present and live.","v":"passive_scanner.cpp:284 cors-wildcard-creds; :771 cors-origin-reflection (high); :777 cors-null-origin; :785 cors-methods-wildcard; :790 cors-headers-wildcard","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A7] Passive audit: information disclosure","s":"present","i":"low","e":"hours","g":"","w":"Re-read passive_scanner.cpp:266-277 (server-version-leak, x-powered-by), 700-711 (internal-ip-leak/internal-hostname-leak), 733 (html-comment-leak), plus grep confirmed source-map-exposed:568, exposed-dev-file:671, phpinfo-output:936, server-timing-leak:843. All present.","v":"passive_scanner.cpp:268 server-version-leak; :700 internal-ip-leak; :733 html-comment-leak; grep: :568 source-map-exposed, :671 exposed-dev-file, :936 phpinfo-output","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A8] Passive audit: secrets / sensitive data in URL and body","s":"present","i":"low","e":"hours","g":"Body/secret battery only runs via the API deep-audit (/api/audit/*), not passively and not from any GUI button; the live passive check is URL-query only.","w":"Re-read passive_scanner.cpp:296-311 (secret-in-url over query keys, LIVE per response). Body secret battery SecretScanner::scan confirmed in runDeepAudit control_server.cpp:769-784 emitting secret-exposed with per-type severity. URL check is live; body check is API-only (audit path).","v":"passive_scanner.cpp:346 `addFinding(rowId, req, resp, \"medium\", \"secret-in-url\", ...)` -- live, per response, query keys only. control_server.cpp:786-802 deep-audit block runs `SecretScanner::scan(ssr)` and emits a `secret-exposed` finding with per-type severity -- API-only (/api/audit/*), not passive and not from any GUI button.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A9] Passive audit: tech/CMS fingerprint with CVE correlation","s":"present","i":"low","e":"hours","g":"Passive fingerprints carry no CVE; CVE correlation runs via /api/assess, which now has a GUI trigger (SCANS tab's Assess target panel) but still depends on the bundled cve_database.cpp table, not a live advisory feed.","w":"Re-read passive_scanner.cpp:1394-1523: ~13 CMS + ~8 frameworks emit info-only 'cms-*'/'fw-*' findings with NO CVE; CVE correlation lives only in assessWebTarget (control_server.cpp:396-470), reachable via /api/assess. That endpoint was API-only through 2026-08-10; the SCANS tab's new Assess & audit section (ui-v2/app.jsx) wires a URL input -> /api/assess -> host/port/tls/tech/findingCount display, closing the GUI-reachability half of the gap. The static-DB-vs-live-feed caveat is unchanged and still holds 'present' rather than 'exceeds'.","v":"control_server.cpp:432 `for (const auto &m : Nullock::Core::CveDatabase::lookup(t.cveKind, t.name + \" \" + t.version)) addF(... \"cve-correlated\" ...)`; passive_scanner.cpp:1394 flagCms(...\"cms-wordpress\"...) emits info, no CVE; ui-v2/app.jsx ScansTab's 'Assess target' Section calls NL.actions.assess(url) -> POST /api/assess.","o":"present","r":"Unified scan/audit runner batch: SCANS tab's Assess & audit section adds a GUI trigger for /api/assess, closing the 'no GUI' half of this gap; the live-feed caveat stands untouched."},{"a":"scanner","f":"[A10] Passive audit: DOM-XSS source/sink detection","s":"partial","i":"medium","e":"months","g":"No live DOM taint tracking (no browser); misses runtime-reached sinks and external JS. Regex over the first 1MB of inline HTML only.","w":"Re-read passive_scanner.cpp:1076-1099: static regex over inline scripts for innerHTML<-location, eval<-location, postMessage '*', eval-of-responseText. Regex-only, no runtime taint. Claim holds.","v":"passive_scanner.cpp:1196 `R\"(\\.innerHTML\\s*=\\s*[^;]*(?:location|document\\.referrer|window\\.name))\"` (block starts :1188, body slice :1189-1190)","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified passive_scanner.cpp -- the DOM-XSS sink block (line drift 1076-1099 -> 1188-1213) is still a static QRegularExpression table (innerHTML<-location, eval/setTimeout<-location, postMessage '*', eval-of-responseText) run over `scanBody.left(1MB)` when `html` is true (:1189), gated by `scanBody.size() < 1MB` (:1189). No live DOM taint tracking, no runtime-reached-sink coverage, no external-JS fetch. Claim holds; evidence line refreshed 1083 -> 1196."},{"a":"scanner","f":"[A11] Active audit: SQL injection (error/boolean/blind time-based)","s":"present","i":"medium","e":"days","g":"Boolean/differential blind SQLi is not implemented (Burp does it). Time-based is opt-in only. Dedicated multi-technique module is API-only; GUI users get single-quote error detection via the probe path only.","w":"Re-read sql_injection.cpp end-to-end. Error-based with balanced-payload corroboration (lines 92-124) and blind time-based per-DBMS SLEEP with SLEEP(0) control (131-175) are real. But BOOLEAN-based (true/false differential) is ABSENT -- no such phase exists in the 185-line file. The claim's 'boolean' sub-claim is false. Also: the dedicated module is only reached via /api/audit/* (no GUI); the GUI '","v":"sql_injection.cpp is still 185 lines; error-based phase around line 123 (`QStringLiteral(\"error-based\")`), blind time-based SLEEP-per-DBMS with a SLEEP(0) control around lines 131-175 (`QStringLiteral(\"time-based\")`). No 'boolean' technique string or differential true/false phase anywhere in the file -- claim unchanged.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A12] Active audit: reflected XSS","s":"partial","i":"low","e":"hours","g":"The reduced HTML tokenizer still misclassifies inert template content and some SVG/MathML contexts; it is not a complete browser parser. XML document execution, stored XSS and DOM XSS remain outside this probe. Document sniffing models Chromium 151; older browsers can differ on combined nosniff values.","w":"The public API and deep audit detect reflected tags using effective Content-Type/nosniff values and HTML context checks. Exact raw-text tag names, iframe fallback content and abrupt comment endings now match pinned Chromium comparisons. Confirmed template and foreign-content mismatches prevent a full-parity claim.","v":"Src/Core/Networking/xss_logic.cpp effectiveMediaType/canExecuteHtml/inExecutingHtmlContext; Tests/xss_reflected/xss_reflected_test.cpp; Tests/ui/xss_context_browser_test.cjs; Tests/ui/xss_media_types_browser_test.cjs; scripts/probe_smoke.sh xss-context, xss-media and xss-nosniff fixtures.","o":"present","r":"Correct 66 browser/analyzer mismatches involving custom tag names, iframe fallback text and abrupt comment closure. Add 95 pinned-browser context comparisons and five public-API fixtures. Downgrade present to partial after separately reproducing template and SVG context gaps; those cases remain follow-up work."},{"a":"scanner","f":"[A13] Active audit: OS command injection (incl. blind/OAST)","s":"present","i":"low","e":"hours","g":"GUI probe cmdi is output-channel only (no blind/time). Dedicated CmdInjection module is API-only.","w":"Re-read control_server.cpp:739-747 (CmdInjection::test -> command-injection critical) and GUI probe cmdi at :2325-2339 ('; id' output-channel, uid= regex). OAST infra exists (Src/Core/APIs/Oast/). Present.","v":"control_server.cpp:756-764 deep-audit block: `CmdInjection::test(cir)` -> critical `command-injection` finding (API-only, /api/audit/*). GUI probe cmdi is output-channel only: control_server.cpp:2564-2578, payload `\";id;#\"`, `QRegularExpression rxUid(\"uid=\\\\d+\\\\(.+\\\\) gid=\\\\d+\")` at :2576-2577 -- no blind/time-based leg in the GUI path. OAST infra exists at Src/Core/APIs/Oast/ (oast_server.cpp, oast_correlator.cpp, dns_sink.cpp).","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A14] Active audit: path traversal / LFI","s":"present","i":"low","e":"hours","g":"","w":"Re-read control_server.cpp:749-757 (PathTraversal::test -> path-traversal critical) and GUI probe traversal at :2304-2317 (etc/passwd marker). Present on both surfaces.","v":"control_server.cpp:753 `const auto res = Nullock::Core::PathTraversal::test(ptr);`; :2309 `if (body.contains(\"root:x:0:0:\") ...)`","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A15] Active audit: XXE injection","s":"present","i":"medium","e":"hours","g":"Reachable via /api/audit/run|all. /api/audit/run now has a GUI trigger (SCANS tab's Audit run panel with per-tester include checkboxes) but XXE is still not part of the TESTS tab's uniform battery or the 'Probe all rows' quick action.","w":"Re-read control_server.cpp:655-668: XxeInjection::test, content-type/body-gated to XML, emits xxe-injection critical. Module file xxe_injection.cpp (91 lines) exists. Was present but fully API-only through 2026-08-10; the SCANS tab's new Audit run panel now POSTs url/method/body/include (xxe among the checkboxes) to /api/audit/run and renders the per-tester hit summary + raw response.","v":"control_server.cpp:663 `const auto res = Nullock::Core::XxeInjection::test(xrr);` gated by :658 `if (ctl.contains(\"xml\") || bt.startsWith(\"<?xml\") ...)`; ui-v2/app.jsx ScansTab's 'Audit run' Section include-checkbox list contains \"xxe\", posting to NL.actions.auditRun -> POST /api/audit/run.","o":"present","r":"Unified scan/audit runner batch: SCANS tab's Audit run panel adds a GUI trigger for /api/audit/run (include-checkbox battery, xxe among them); still absent from TESTS' uniform battery and Probe-all, called out honestly."},{"a":"scanner","f":"[A16] Active audit: server-side template injection","s":"present","i":"medium","e":"hours","g":"API-only (/api/audit/*); not in the GUI probe battery, so a GUI-only user never runs SSTI.","w":"Re-read control_server.cpp:786-801: iterates up to 5 query params, Ssti::test, emits ssti-confirmed critical with engine names. Present but API-only.","v":"control_server.cpp:796 `const auto res = Nullock::Core::Ssti::test(sr);` :797 `if (res.confirmed) { ++hits; engines << res.engines; }`","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A17] Active audit: SSRF (cloud metadata + OAST)","s":"present","i":"low","e":"hours","g":"","w":"Re-read control_server.cpp:704-714 (SsrfScan::test, ssrf-cloud-metadata escalated to critical) and the GUI probe SSRF at :2181-2274 (6 cloud-metadata probes with shaped controls + OAST token minting/correlation). Present and strong on both surfaces.","v":"control_server.cpp:725 `const auto res = Nullock::Core::SsrfScan::test(srr);`; :2426-2486 GUI probe (6 cloud-metadata endpoints with shaped-control suppression) reports critical ssrf-cloud-metadata; :2494-2512 OAST mintToken/registerToken+fire-and-forget.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A18] Active audit: LDAP injection","s":"present","i":"medium","e":"hours","g":"The high-fidelity engine is reachable from the GUI two ways: the per-row live probe fires an ldap-injection-suspect heuristic, and the full LdapInjection::test now also runs via the Findings tab's 'Deep audit all rows' button (POST /api/audit/all, default sweep). No remaining GUI gap.","w":"Re-read control_server.cpp:684-692 (LdapInjection::test -> ldap-injection high). Module ldap_injection.cpp (111 lines) exists. Present but API-only.","v":"control_server.cpp:688 `const auto res = Nullock::Core::LdapInjection::test(lrr);`","o":"present","r":"The Findings tab's new 'Deep audit all rows' button (real-data.js NL.actions.auditAll -> POST /api/audit/all {fromHistory:true}) runs the default deep-audit sweep -- which already includes LdapInjection::test -- against every history row with params/body. Closes the 'API-only' gap."},{"a":"scanner","f":"[A19] Active audit: XPath injection","s":"present","i":"medium","e":"hours","g":"No longer API-only: the Findings tab's 'Deep audit all rows' button runs the default sweep (which includes XpathInjection::test) against every history row with params/body. No per-row probe-battery entry exists, but the high-fidelity tester is now one click away in the GUI.","w":"Re-read control_server.cpp:694-702 (XpathInjection::test -> xpath-injection high). Module xpath_injection.cpp (111 lines) exists. Present but API-only.","v":"control_server.cpp:698 `const auto res = Nullock::Core::XpathInjection::test(xrr);`","o":"present","r":"Closed via the same 'Deep audit all rows' button as LDAP/host-header/cache-poison/deser/nosql/mass-assign/CORS -- one frontend change (auditAll action + button, POST /api/audit/all) surfaces the whole default-sweep cluster."},{"a":"scanner","f":"[A20] Active audit: server-side code / EL / OGNL injection","s":"partial","i":"low","e":"weeks","g":"OGNL/Struts2 is now ACTIVELY probed (no longer CVE-correlation-only): the SSTI tester's two-expression arithmetic proof gained the %{ } delimiter family, which only OGNL/Apache-Struts2 evaluates, so an OGNL-parsed sink is confirmed and fingerprinted as Struts2. Remaining gap: generic non-arithmetic server-side code-eval -- SpEL class access (T(java.lang.Runtime)...), raw eval() APIs, and OGNL member-access chains beyond infix math -- is still not actively probed.","w":"Extended the proven SSTI engine rather than duplicating it: added { \"%{\", \"}\", \"OGNL (Apache Struts2)\" } to ssti_tester.cpp families(). The existing polyglot sends pre%{a*b}sep%{c*d}suf and confirmsArithmetic() requires BOTH products with the literal separator preserved and neither raw expression echoed -- so a Struts2 OGNL sink confirms while pure reflection / a single-expression calculator do not. No other family uses %{ }, so the hit's engine string uniquely fingerprints OGNL.","v":"ssti_tester.cpp families() now includes the %{ } OGNL family; hpp doc updated (\"...also covers OGNL/Apache-Struts2\"). Live-proven in scripts/probe_smoke.sh: a new ssti-ognl mock evaluates ONLY %{N*N} (not Jinja {{ }}), and /api/ssti/test confirms it with engines containing 'OGNL' AND not 'Jinja2' (2 new cases). Mutation-proven: deleting the %{ } family drops that case to confirmed:false/hits:[] while ssti-vuln/safe/calc stay correct. Gauntlet: ctest 100/100, probe_smoke 158/158.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified ssti_tester.cpp -- the `{ \"%{\", \"}\", \"OGNL (Apache Struts2)\" }` family (:32) is present and wired exactly as described, giving an active OGNL/Struts2 confirm via the arithmetic-polyglot proof. Generic non-arithmetic server-side code-eval (SpEL class access, raw eval() APIs, OGNL member-access chains) is still not actively probed -- grep for SpEL/T\\(java\\.lang\\.Runtime confirms no such family exists. Claim holds, no drift."},{"a":"scanner","f":"[A21] Active audit: HTTP request smuggling (CL.TE / TE.CL)","s":"present","i":"medium","e":"hours","g":"The per-row live probe already fires an http-smuggling-clte-suspect heuristic. The full opt-in Smuggling::test battery IS GUI-reachable: the Scans tab's 'Audit run' section has a per-tester include checkbox list with a 'smuggle (opt-in, not in default sweep)' entry that posts include:['smuggle'] to /api/audit/run. Prior gap text calling this API-only via a direct POST to /api/audit/all was stale/incorrect.","w":"Register-accuracy correction, no code change: re-verified against live source rather than trusting the prior gap text. ui-v2/app.jsx's AUDIT_INCLUDES array (Scans tab, 'Audit run' section) includes \"smuggle\", rendered as a checkbox labeled '(opt-in, not in default sweep)', wired through doAuditRun -> NL.actions.auditRun(url, {include}) -> POST /api/audit/run, which calls the identical runDeepAudit(...) helper (and its smuggle-gated branch) that /api/audit/all uses. The prior note said this was reachable 'only via a direct POST to /api/audit/all' -- that was already false by the time it was written and stayed uncorrected across several later waves.","v":"ui-v2/app.jsx:1943 AUDIT_INCLUDES array contains \"smuggle\"; :2382-2387 renders one checkbox per include name in the Audit run Section, with the smuggle checkbox specially labeled; :1945-1952 doAuditRun() builds opts.include from the checked set and calls NL.actions.auditRun; ui-v2/real-data.js:371 auditRun(url,opts) posts to /api/audit/run; Src/BackEnd/Control/control_server.cpp:6953,6991 /api/audit/run reads bodyJson.value(\"include\") and calls runDeepAudit(m_wiring.scanner, t, include, testerReports); control_server.cpp:634-642 runDeepAudit's smuggling branch is gated on include.contains(\"smuggle\").","o":"present","r":"Wave 0 register-accuracy fix: corrected stale gap text claiming the opt-in smuggling battery was reachable only via a direct POST to /api/audit/all. Live source shows it has been GUI-reachable via the Scans tab's Audit run section's smuggle checkbox (POST /api/audit/run, same runDeepAudit include-gated branch) since that section landed -- no code change, state stays present, only the gap/why/evidence text corrected."},{"a":"scanner","f":"[A22] Active audit: Host header injection / poisoning","s":"present","i":"medium","e":"hours","g":"No longer API-only: reachable from the GUI via the Findings tab's 'Deep audit all rows' button (default sweep includes HostHeader::test). The per-row live probe still only fires an X-Forwarded-Host cache-poison variant, not host-header-injection proper, but the high-fidelity tester itself is now GUI-reachable.","w":"Re-read control_server.cpp:609-629: HostHeader::test, splits high host-header-injection (Host->Location) from medium host-header-reflected-location. Present but API-only.","v":"control_server.cpp:614 `const auto res = Nullock::Core::HostHeader::test(hhr);` :620 fromHostLine && where=='Location' -> high","o":"present","r":"Closed via the shared 'Deep audit all rows' button (auditAll action, POST /api/audit/all default sweep)."},{"a":"scanner","f":"[A23] Active audit: web cache poisoning","s":"present","i":"medium","e":"hours","g":"Fully GUI-reachable: the default sweep ('Deep audit all rows') still runs the narrower X-Forwarded-Host variant per row, and the TESTS tab now also has a dedicated Web cache poisoning panel wiring the full CachePoison::test single-target probe directly (/api/cache/poison) with a free-form custom-header editor -- the confirmed/cacheable/unkeyed severity ladder, baseline status, and request count are all rendered.","w":"Re-read control_server.cpp:594-607: CachePoison::test with severity ladder confirmed(critical)/cacheable(high)/unkeyed(low). Present but API-only.","v":"control_server.cpp:599 `const auto res = Nullock::Core::CachePoison::test(cpr);` :601-604 sev/kind ladder","o":"present","r":"Wired the previously-orphaned /api/cache/poison endpoint into a dedicated Web cache poisoning panel on the TESTS tab (custom-header textarea + URL/method + confirmed/cacheable hit table), closing the last GUI-reachability gap UI-NAVIGABILITY.md tracked for this endpoint."},{"a":"scanner","f":"[A24] Active audit: open redirection","s":"present","i":"low","e":"hours","g":"","w":"Re-read control_server.cpp:575-592 (OpenRedirect::test, header-confirmed high / client-side medium) and GUI probe open-redirect at :2156-2179 (external-host canary in Location). Present on both surfaces.","v":"control_server.cpp:592-609 (OpenRedirect::test, header-confirmed high / client-side medium); :2401-2424 GUI probe emits open-redirect on external-canary Location match.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A25] Active audit: CRLF / response header injection","s":"present","i":"low","e":"hours","g":"","w":"Re-read control_server.cpp:759-767 (CrlfInjection::test -> crlf-injection high). GUI probe also has a CRLF marker probe (control_server.cpp:2341+). Present.","v":"control_server.cpp:780 `const auto res = Nullock::Core::CrlfInjection::test(cir);` (deep-audit path, note(\"crlf\", ...) -> \"high\"/\"crlf-injection\"); :2645-2663 GUI probe injects `x%0d%0aX-Nullock-Inject:%20<tag>` and reports high crlf-injection when the header is reflected verbatim in the response.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A26] Active audit: insecure deserialization","s":"present","i":"medium","e":"hours","g":"No longer API-only: DeserProbe::test is reachable from the GUI via 'Deep audit all rows' (default sweep). Still no per-row probe-battery entry.","w":"Re-read control_server.cpp:716-727: DeserProbe::test -> per-format kind critical. Module deser_probe.cpp (248 lines) exists. Present but API-only.","v":"control_server.cpp:720 `const auto res = Nullock::Core::DeserProbe::test(drr);` :726 kindForFormat(...)","o":"present","r":"Closed via the shared 'Deep audit all rows' button (auditAll action, POST /api/audit/all default sweep)."},{"a":"scanner","f":"[A27] Active audit: NoSQL injection","s":"present","i":"medium","e":"hours","g":"The per-row live probe already fires a nosql-injection-suspect heuristic, and the full NoSqlInjection::test operator battery is now also reachable from the GUI via 'Deep audit all rows' (default sweep). No remaining GUI gap.","w":"Re-read control_server.cpp:644-652: NoSqlInjection::test -> nosql-injection high. Present but API-only.","v":"control_server.cpp:648 `const auto res = Nullock::Core::NoSqlInjection::test(nrr);`","o":"present","r":"Closed via the shared 'Deep audit all rows' button (auditAll action, POST /api/audit/all default sweep)."},{"a":"scanner","f":"[A28] Active audit: mass assignment / auto-binding","s":"present","i":"low","e":"hours","g":"Only default field names, only when a body is present, no app-model awareness (inherent to blind mass-assignment testing -- Burp has the same limitation). No longer API-only: reachable from the GUI via 'Deep audit all rows' (default sweep), in addition to the existing per-row mass-assignment-suspect heuristic.","w":"Downgraded exceeds->present. Re-read control_server.cpp:558-568: MassAssign::test over default fields, only when a body is present, emits mass-assignment high. It is a real check beyond Burp core, but it is a basic default-field probe, fires only with a body, and is API-only (no GUI). 'exceeds' overstates a modest, gated, headless check.","v":"control_server.cpp:565 `const auto res = Nullock::Core::MassAssign::test(mr, Nullock::Core::MassAssign::defaultFields());` gated by :558 `&& !t.body.isEmpty()`","o":"present","r":"Closed the GUI-reachability gap via the shared 'Deep audit all rows' button (auditAll action, POST /api/audit/all default sweep)."},{"a":"scanner","f":"[A29] Active audit: CORS active probing (attacker-origin reflection)","s":"present","i":"low","e":"hours","g":"No longer API-only: CorsTester::test (worst-probe severity, real probe-kind labeling) is reachable from the GUI via 'Deep audit all rows' (default sweep). Still no per-row probe-battery entry.","w":"Re-read control_server.cpp:523-541: CorsTester::test picks the worst reflected-origin probe and reports its real kind/severity. Present but the audit path is API-only.","v":"control_server.cpp:527 `const auto res = Nullock::Core::CorsTester::test(cr);` :533 tracks worst severity/kind","o":"present","r":"Closed via the shared 'Deep audit all rows' button (auditAll action, POST /api/audit/all default sweep)."},{"a":"scanner","f":"[A30] Access-control / authz testing via multi-identity replay","s":"present","i":"medium","e":"hours","g":"Identities still supplied as manual header sets (no auto-login); divergence heuristic is status/size only (false-positives on dynamic pages).","w":"GUI-reachability gap closed 2026-08-11: an AUTHZ TEST button on Proxy history / Site map's DetailPane (ui-v2/proxy.jsx) opens a modal identity editor (name + raw \"Header: value\" lines per identity, add/remove), POSTs to the existing /api/authz-test via a new NL.actions.authzTest(rowId, identities), and renders the per-identity status/bodySize table plus a divergent/consistent verdict banner -- the server still files the authz-divergence finding into Issues independently. The remaining caveats (manual identities, naive status/size divergence heuristic) are real and unrelated to this batch, left honestly in the gap text above rather than claimed fixed.","v":"control_server.cpp:4592 POST /api/authz-test {rowId, identities:[{name,headers}]} -> {ok,divergent,results:[{identity,ok,status,bodySize,error}],row}; ui-v2/proxy.jsx AuthzTestOverlay + DetailPane's \"AUTHZ TEST\" button; ui-v2/real-data.js NL.actions.authzTest.","o":"","r":"Authz-test batch: multi-identity replay modal wired into Proxy/Site-map DetailPane, closing the GUI-reachability half of #78 [A30]."},{"a":"scanner","f":"[A31] Hidden parameter discovery (param miner)","s":"present","i":"low","e":"hours","g":"Deep-audit param-mining still uses only the first 60 wordlist entries (runDeepAudit's in-sweep variant, unchanged). The standalone /api/paramminer endpoint now has a GUI button (SCANS tab's Param miner panel, default or pasted wordlist, uncapped up to the backend's 2000-entry limit).","w":"Re-read control_server.cpp:6604-6634 (/api/paramminer, wordlist capped 2000, off-thread) and runDeepAudit:500-510 (folded in, but wordlist there is capped to only the first 60 names via .mid(0,60)) -- that in-audit truncation is unchanged. The standalone endpoint was API-only through 2026-08-10 (grep ui-v2 'parammin' was empty); the SCANS tab's new Param miner panel now POSTs url + optional pasted wordlist to /api/paramminer and renders requestsSent/candidatesTried/foundCount + the found-param list.","v":"control_server.cpp:6627 `wordlist = Nullock::Core::ParamMiner::defaultWordlist();` :6628 capped 2000; runDeepAudit:505 `ParamMiner::defaultWordlist().mid(0, 60)`; ui-v2/app.jsx ScansTab's 'Param miner' Section calls NL.actions.paramMine(url, opts) -> POST /api/paramminer.","o":"present","r":"Unified scan/audit runner batch: SCANS tab's Param miner panel adds a GUI trigger for /api/paramminer; the deep-audit in-sweep 60-entry cap remains an honest separate gap, untouched."},{"a":"scanner","f":"[A32] Scan launch modes (crawl-only/crawl+audit/audit-selected/live-passive)","s":"partial","i":"medium","e":"weeks","g":"No 'crawl then audit' pipeline, no live active scanning of proxy traffic, no named launch-mode selector.","w":"Re-read: passive is always-on live (passive_scanner.hpp:71-73), active is manual per-URL (/api/audit/run:6460) or session-wide (/api/audit/all:6513 fromHistory). Crawler is a separate endpoint. No unified crawl->audit pipe, no named launch-mode selector. Claim holds.","v":"control_server.cpp:7855 `/api/audit/all` pulls history rows; :4722 `/api/crawler/start` is separate; no code path feeds crawler output into runDeepAudit","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified control_server.cpp -- /api/crawler/start (:4722, was :3959) and /api/audit/run (:7802) / /api/audit/all (:7855, was :6513) remain three independent entry points; no code path feeds crawler output into runDeepAudit, no named launch-mode selector exists. Claim holds; evidence line numbers refreshed."},{"a":"scanner","f":"[A33] Issue severity model (High/Medium/Low/Info)","s":"present","i":"low","e":"hours","g":"","w":"Re-read passive_scanner.hpp:26 (severity 'info|low|medium|high|critical') and control_server.cpp severityRank/computePostureGrade. Adds a critical tier above Burp's High. Confirmed.","v":"passive_scanner.hpp:26 `QString severity;     // \"info\" | \"low\" | \"medium\" | \"high\" | \"critical\"`","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A34] Issue confidence model (Certain/Firm/Tentative)","s":"present","i":"low","e":"hours","g":"Confidence is derived from the kind string, not per-evidence; no user override.","w":"Re-read passive_scanner.hpp:39-47 (confidence field) and finding_enricher.cpp:463-487 confidenceForKind maps kinds -> confirmed/firm/tentative. Confirmed.","v":"finding_enricher.cpp:463 confidenceForKind(); passive_scanner.hpp:47 `QString confidence;`","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"scanner","f":"[A35] Retest an individual issue","s":"partial","i":"medium","e":"weeks","g":"Cannot re-run one check for one issue; only whole-baseline diff, not tied to the original insertion point/payload.","w":"Re-read: grep for retest finds no per-issue endpoint. Only /api/baseline/save + /api/baseline/diff (control_server.cpp:4074,4147) re-run and diff the whole finding set. Claim holds.","v":"control_server.cpp:4926 `if (path == \"/api/baseline/diff\")`; no per-finding retest route exists","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified control_server.cpp -- /api/baseline/save (:4853, was :4074) and /api/baseline/diff (:4926, was :4147) remain the only baseline-related routes; grep for `retest` across control_server.cpp and ui-v2/ returns no per-issue retest endpoint or UI action. Claim holds; evidence line numbers refreshed."},{"a":"scanner","f":"[A36] Authenticated scanning: session-handling rules (macros)","s":"partial","i":"high","e":"weeks","g":"HTTP scanners and the crawler now use enabled cookies, tool-scoped session rules and recorded HTTP login macros, including expiry-triggered refresh. Browser interaction recording and JavaScript-driven login execution remain unavailable.","w":"The shared HTTP client applies Scanner-scoped session rules, captures rotated tokens/cookies and refreshes configured expired sessions. Explicit identity comparisons and recorded macro requests retain their own credentials.","v":"Src/Core/Networking/networking.cpp; session_rules.cpp; crawler.cpp; scripts/scanner_sessions_regression.py; Tests/session_rules/session_rules_test.cpp","o":"","r":"HTTP authenticated scan workflows verified, including form CSRF replacement, compressed token extraction, refresh cooldown, request fidelity and project isolation. Browser login execution remains a separate gap."},{"a":"scanner","f":"[A37] Out-of-scope handling during scans","s":"present","i":"low","e":"hours","g":"","w":"Active tools check every concrete outbound request against host, protocol, port and path scope. Raw TCP/TLS probes require an unrestricted endpoint grant. Invalid enabled rules fail closed; invalid editor saves preserve the prior policy.","v":"Src/Core/Networking/outbound_scope.cpp; HttpClient::send; raw port/TLS/WebSocket guards; Tests/scope_logic/scope_logic_test.cpp; Tests/proxy_shutdown/proxy_shutdown_test.cpp; scripts/outbound_scope_regression.py; Tests/ui/scope_browser_test.cjs","o":"present","r":"Full outbound scope boundary, live policy updates, full-URL redirect/crawler checks and visible validation errors."},{"a":"scanner","f":"[A38] Scan speed vs accuracy tradeoff settings","s":"partial","i":"medium","e":"weeks","g":"No thread-count/concurrency control; no fast/normal/thorough presets that change payload depth or retries.","w":"Re-read control_server.cpp:6524-6527 (audit/all throttleMs default 150 bounded 0..60000, limit default 50 bounded 1..200) and the sweep worker at 6584-6592 (single serial QtConcurrent::run loop). Only throttle+cap, serial, no concurrency knob, no accuracy presets. Claim holds.","v":"control_server.cpp:7947 `auditAllInFlight.storeRelease(0); // sweep done` -- single serial loop with QThread::msleep(throttleMs) between targets","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified control_server.cpp /api/audit/all -- throttleMs default 150 bounded 0..60000 and limit default 50 bounded 1..200 (line drift 6524-6527 -> ~7866-7869), sweep dispatched via QtConcurrent::run but the target loop itself is still a single serial iteration with QThread::msleep(throttleMs) between targets (no thread-count knob, no fast/normal/thorough accuracy presets). Claim holds; evidence line numbers refreshed."},{"a":"scanner","f":"[A39] Live scanning of proxy traffic (live active audit tasks)","s":"partial","i":"medium","e":"weeks","g":"No live active task; user must manually kick off /api/audit/all or GUI 'Probe all rows' after browsing.","w":"Re-read: passive is wired live on every response (app.cpp:945-946 crawler->onResponseReceived, scanner ctor). Active auditing is only user-triggered (/api/audit/run, /api/audit/all fromHistory, GUI /api/probe/all). No auto-active-scan of in-scope requests as they pass. Claim holds.","v":"app.cpp:1266 `QObject::connect(&crawler, ...entryLoaded, ...)` / :1271 `&scanner, &...::onResponseReceived)`; no live active-scan task exists","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified app.cpp -- crawler.entryLoaded is still connected straight to scanner.onResponseReceived for passive-only coverage (line drift 945-946 -> 1266-1271); active auditing remains exclusively user-triggered via /api/audit/run, /api/audit/all, or GUI /api/probe/all. No live active-scan task exists. Claim holds; evidence line numbers refreshed."},{"a":"scanner","f":"[A40] Vulnerable/outdated JS library detection","s":"partial","i":"low","e":"weeks","g":"Version-string correlation against a bundled DB, not a retire.js-style known-vulnerable-JS hash catalogue or live feed.","w":"Re-read: js_recon.cpp exists; assessWebTarget correlates detected tech+version to CveDatabase (control_server.cpp:431-435); framework fingerprints passive_scanner.cpp:1483-1517. CVE correlation is version-string based against the curated cve_database.cpp, not a retire.js hash/pattern catalogue. Claim holds.","v":"control_server.cpp:452 `CveDatabase::lookup(t.cveKind, t.name + \" \" + t.version)`; no hash/pattern library-advisory catalogue in Src/","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified control_server.cpp assessWebTarget (line drift 431-435 -> 415-452) still resolves via CveDatabase::lookup(t.cveKind, name+version) -- version-string correlation against the bundled cve_database.cpp, not a retire.js-style hash/pattern catalogue. Claim holds; evidence line numbers refreshed."},{"a":"scanner","f":"[B1] Crawl: JavaScript/SPA crawling via embedded browser","s":"absent","i":"high","e":"months","g":"No browser-driven crawl; client-rendered SPA navigation is invisible.","w":"Re-read crawler.cpp:151-183 (regex link extraction over static HTML) and grep of Src/ for headless|chromium|puppeteer|webengine|CDP returns nothing in the crawl path. Confirmed absent; task #12 headless-browser DAST still pending.","v":"crawler.cpp:154 'Doesn't run JS so heavily-SPA targets won't yield many links'; no browser engine in Src/","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-verified crawler.cpp:153 comment still reads \"Doesn't run JS so heavily-SPA targets won't yield...\" (line drift from :154); grep of Src/ for headless|chromium|puppeteer|webengine|CDP in the crawl path still returns nothing. Confirmed still absent, no drift in substance."},{"a":"scanner","f":"[B2] Active audit: stored cross-site scripting","s":"absent","i":"medium","e":"months","g":"No stored-XSS detection (needs inject-at-A / detect-at-B after re-crawl). Neither the dedicated module nor the GUI probe attempts it.","w":"Re-read xss_reflected.hpp:12 ('DOM-based, and stored XSS are out of scope') and grep 'stored.?xss' across Src/ returns only that exclusion comment. No inject-here/detect-there correlation engine. Confirmed absent.","v":"xss_reflected.hpp:12 '...DOM-based, and stored XSS are out of scope for this reflected check.'; no stored-xss correlation code exists","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-verified xss_reflected.hpp:12 still excludes \"DOM-based, and stored XSS\" from the reflected checker's scope; grep for stored.?xss across Src/ still returns only that exclusion comment. No inject-at-A/detect-at-B correlation engine exists. Confirmed still absent."},{"a":"scanner","f":"[B3] Scan configuration library (saved named configs / presets)","s":"absent","i":"medium","e":"weeks","g":"No saved/named scan configs, no built-in preset library, no import/export. Every run re-specifies include[] + throttle inline.","w":"Re-read control_server.cpp:6480-6483 (audit selection is a freeform include[] set built per-call). Grep of Src/ and ui-v2/ for scanConfig|savedConfig|config.?library|named.?config|scanProfile returns nothing. No persistence of a scan profile. Confirmed absent.","v":"control_server.cpp:6481 `QSet<QString> include;` built inline per request; grep for named/saved config returns empty","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-verified control_server.cpp /api/audit/all still builds its `include` set as a freeform QSet<QString> parsed inline per request (no persisted profile); grep of Src/ and ui-v2/ for scanConfig|savedConfig|config.?library|named.?config|scanProfile still returns nothing. Confirmed still absent."},{"a":"scanner","f":"[B4] Scan queue with per-task detail (progress, pause/resume/cancel)","s":"absent","i":"high","e":"weeks","g":"No scan queue UI/model; cannot inspect, pause, resume, cancel, or see per-target/per-insertion-point progress.","w":"Re-read control_server.cpp:6516-6519 (single global auditAllInFlight atomic flag) and 6584-6593 (one QtConcurrent::run loop, returns only a queued count). No task model, no per-item status, no pause/resume. Grep ScanQueue|scanTask|pauseScan returns only an unrelated kMaxScanTasks constant. Confirmed absent.","v":"control_server.cpp:7858 `static QAtomicInteger<int> auditAllInFlight(0);`; sweep returns only a queued count","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-verified control_server.cpp -- auditAllInFlight is still a single global QAtomicInteger<int> testAndSetAcquire gate (line drift 6516 -> 7858), the sweep still returns only a queued count, no per-task model, no pause/resume/cancel. grep for ScanQueue|scanTask|pauseScan still returns only the unrelated kMaxScanTasks constant. Confirmed still absent; evidence line refreshed."},{"a":"scanner","f":"[B5] Issue suppression / false-positive marking","s":"present","i":"high","e":"weeks","g":"None -- the ISSUES tab (ui-v2/app.jsx IssuesTab) now has per-finding fp/un-fp and del/restore buttons plus a severity-override <select>, and a per-kind mute/muted button on each kind filter chip, all calling the already-built /api/findings/mark, /delete, /set-severity, and /suppress-kind routes and reflecting the returned falsePositive/deleted/suppressed flags back onto each row.","w":"Wave 0 register-accuracy audit: the 2026-08-17 close left this PARTIAL pending the Issues-UI follow-on; that follow-on has since landed (not separately reconciled here before now). ui-v2/app.jsx:1811-1826 defines doMarkFP/doToggleDelete/doSetSeverity/doSuppressKind, and each is wired to a live control: the fp/un-fp and del/restore buttons + severity <select> on every finding row (app.jsx:2342-2377), and a mute/muted button on every kind chip in the filter row (app.jsx:2198-2208). real-data.js:595-598 posts each to its backend route. Verified end to end against control_server.cpp:6891 (/api/findings/mark), :6910 (/suppress-kind), :6922 (/set-severity, /delete) and the snapshot's falsePositive/deleted/suppressed/severity fields (control_server.cpp:1420-1429) that the UI reads back. Upgraded partial -> present.","v":"ui-v2/app.jsx:1811-1826 (doMarkFP/doToggleDelete/doSetSeverity/doSuppressKind), :2198-2208 (per-kind mute button), :2342-2377 (per-finding fp/del buttons + severity select); ui-v2/real-data.js:595-598 (findingMark/findingDelete/findingSetSeverity/findingSuppressKind); control_server.cpp:6891,6910,6922 (routes), :1420-1429 (snapshot flags).","o":"absent","r":"Wave 0 register-accuracy audit: upgraded partial -> present. The 2026-08-17 entry closed the backend (/api/findings/mark, /suppress-kind) and left the Issues-UI buttons as a named follow-on; grepping ui-v2/app.jsx today shows that follow-on is already fully wired (per-finding fp/del buttons, a severity-override select, and a per-kind mute button), calling all four persisted mutation routes and rendering their returned flags -- parity.json simply never caught up to that landing. No code changed in this commit; this is a state correction only."},{"a":"scanner","f":"[B6] Authenticated scanning: recorded login sequences","s":"partial","i":"high","e":"months","g":"Recorded steps are raw HTTP requests replayed via ChainRunner (built from Proxy history row IDs), not a browser interaction recording -- a JS-driven/SPA login that requires executing client-side script to reach the auth endpoint still cannot be captured or replayed. Also, per item #84, the deep-audit testers don't consult SessionRules directly, so a macro's re-auth only refreshes the shared variable bag, not an in-flight audit request.","w":"UPGRADED absent->partial: this grade is genuinely stale. Commit 88cbe99 (2026-08-28), after this file's audit_date (2026-07-30) and reconciled_through (2026-08-25), added SessionMacro (session_rules.hpp:93-101): a named macro combining recorded ChainRunner steps with an optional logged-out-status/body-regex auto-re-auth trigger. SessionRules::runMacro (session_rules.hpp:135) replays the steps synchronously and ingestVariables merges extracted values into the host's variable bag, which the existing session-rule injection pipeline then applies to subsequent requests -- a real login-sequence-replay auth mechanism, not just static header/cookie rules.","v":"session_rules.hpp:93 `struct SessionMacro { QString name; QString sessionHost; QList<ChainRunner::Step> steps; QString loggedOutStatus; QString loggedOutBodyRegex; };`; control_server.cpp:4555 `/api/session-macros` (get/set, persisted via projectStore->setSessionMacros) and :4574 `/api/session-macros/run` (QtConcurrent::run(sr->runMacro)); ui-v2/app.jsx:7370 \"LOGIN MACROS -- named recorded login sequences ... record steps from Proxy history\"; ui-v2/real-data.js:448-450 sessionMacrosGet/Set/Run.","o":"","r":"Wave 0 register-accuracy audit: UPGRADED absent -> partial. SessionMacro (named, recorded-from-proxy-history login sequences with ChainRunner replay and auto re-auth trigger on logged-out detection) landed in 88cbe99, after this file's prior audit_date/reconciled_through window. Fully wired: backend struct+persistence, /api/session-macros (get/set) and /api/session-macros/run endpoints, and a GUI 'Login macros' panel in app.jsx recording steps from Proxy history rows. Remaining gap: HTTP-replay only, no browser-driven capture for JS/SPA logins, and per item #84 the deep-audit path doesn't consult SessionRules mid-request."},{"a":"extender","f":"[A1] HttpHandler — handleHttpRequestToBeSent / handleHttpResponseReceived, fired for every Burp tool with the originating ToolType","s":"partial","i":"high","e":"weeks","g":"No ToolType: a handler cannot tell proxy from repeater from scan probe and cannot opt out per tool. Intruder is silently uncovered — extensions never see or influence an attack. Host/port immutable, so no redirection. Binary bodies unrepresentable (bodyText is a QString; corruption is avoided only by refusing to write back an unchanged body).","w":"CONFIRMED, every cited line re-read and correct (control_server line numbers shifted +1 for the deep-scan sites because of uncommitted marketplace code, 2105->2106 etc.; the replay sites 2875/2895 are exact). I independently re-ran the reach analysis: `grep -rn applyRequestMutation Src/` returns proxy_server.cpp {273,527,603,684} + control_server.cpp {2106,2674,2745,2780,2875} and nothing else; `g","v":"extensions_api.cpp:695-697 `// Read final mutated values back into the C++ struct. Host/port stay // immutable on purpose -- changing them mid-flight would require // reconnecting to a different upstream, which is a bigger design.`; extensions_api.cpp:720 `req.headers = headersFromJs(entry.property(\"headers\"));`","o":"partial","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[A2] ScanCheck registration — custom passive and active scan checks (registerScanCheck / doPassiveScan / doActiveScan, consolidateDuplicateIssues)","s":"partial","i":"high","e":"weeks","g":"An output channel, not a scan check. No registration, no insertion-point-driven invocation, no active checks (structurally impossible without a send API), no per-check enable/disable, no duplicate consolidation (rowId hard-coded 0). Deep-scan probes call applyRequestMutation, which only lets an extension rewrite Nullock's own probes.","w":"CONFIRMED but the claim is generous and I nearly downgraded. reportFinding at extensions_api.cpp:61-78 is verbatim as quoted and app.cpp:728 `extensions.setScanner(&scanner);` is real, and dom_taint.js is a shipped extension that genuinely lands findings in the panel, so a USER does get working extension-authored passive detection — that is more than a stub. But there is no registration API of any","v":"extensions_api.cpp:122-124 `// rowId 0 = extension-originated; the panel still renders it, the URL // makes it actionable.` then `scanner->reportFinding(0, severity, kind, summary, evidence, host, url);`; extensions_api.hpp:342 `Q_INVOKABLE void reportFinding(...)` is the only finding-related bridge method.","o":"partial","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[A3] Extension output and error streams: api.logging().output()/error(), per-extension Output and Errors tabs, redirectable to console or file","s":"partial","i":"medium","e":"days","g":"One global stream for all extensions — attribution only if the author prefixed the line. No stdout/stderr separation, no file or console redirect, no export, no scrollback. Only the newest 40 of 500 buffered lines are exposed by any API and only 30 are rendered; a chatty extension loses lines silently.","w":"CONFIRMED, and WORSE than the auditor stated in one respect I verified myself. kMaxLogLines=500 and the ring buffer are verbatim. But the 500-line buffer is not reachable: the ONLY API surface is bootInfo, which calls recentLog(40) (control_server.cpp:1226), and there is no /api/extensions/log endpoint — `grep -n '/api/extensions' control_server.cpp` returns exactly install-builtins:5272 and reloa","v":"extensions_api.cpp:27 `constexpr int kMaxLogLines = 500;`; extensions_api.cpp:485-486 `if (m_logLines.size() > kMaxLogLines) m_logLines.remove(0, m_logLines.size() - kMaxLogLines);`; control_server.cpp:1311 `for (const QString &line : m_wiring.extensions->recentLog(40))`; ui-v2/app.jsx:1393 `: extLog.slice(-30).map((line, i) => (`","o":"partial","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[A4] Extension auto-reload during development (Auto-reload checkbox; Ctrl/Cmd-click to reload a single extension)","s":"partial","i":"medium","e":"hours","g":"The auto-reload checkbox now exists and works end-to-end (toggling it in Settings' Extensions card flips the same opt-in QFileSystemWatcher the backend shipped in 5dba22c). Still missing: the Ctrl/Cmd-click-to-reload-a-single-extension gesture named in the title -- Reload (and now auto-reload) both rebuild the whole QJSEngine and re-run every script; there is no per-extension reload path, backend or frontend.","w":"Wave 2 (2026-08-23): wired the auto-reload CHECKBOX -- the ui-v2 half the prior wave (5dba22c) explicitly left as the honest remainder. Added NL.actions.setExtAutoReload (ui-v2/real-data.js, POSTs the already-existing /api/extensions/auto-reload {value}) and a checkbox in Settings' Extensions card action row (ui-v2/app.jsx), initialised from the already-published bootInfo.extAutoReload and updated optimistically with a revert-on-failure guard, matching the toggleExtensionEnabled pattern already used two rows below it. No backend change -- the endpoint and snapshot field existed and were unread, same shape as the accept-invalid-cert and CVE-overlay waves before it. Stays partial, not present: single-extension reload (the Ctrl/Cmd-click gesture) is unbuilt at any layer.","v":"ui-v2/real-data.js setExtAutoReload(value) posts /api/extensions/auto-reload {value}; ui-v2/app.jsx SettingsTab: extAutoReload state seeded from b.extAutoReload (bootInfo, control_server.cpp:1293 bootInfo[\"extAutoReload\"] = m_wiring.extensions->autoReload()), toggleExtAutoReload() calls the action and reconciles against the server's echoed autoReload; checkbox rendered in the Extensions card's action row next to the existing Install bundled / Reload buttons. control_server.cpp:6417-6421 POST handler unchanged (pre-existing). Single-extension reload: grep 'reload.*name\\|per-extension.*reload' across ExtensionsApi/ui-v2 = no match; /api/extensions/reload and setAutoReload's own reload() both call the same whole-engine rebuildEngine().","o":"partial","r":"Wave 2: wired the [A4] auto-reload checkbox into Settings' Extensions card (ui-v2/app.jsx + ui-v2/real-data.js), closing the ui-v2-reachability half the prior backend wave (5dba22c) left open. No backend change. Stays partial -- the Ctrl/Cmd-click single-extension reload gesture remains unbuilt, honestly named in the updated gap text."},{"a":"extender","f":"[A5] BApp Store: extension detail page (full description, author, version, source-code link, 'Report a bug')","s":"present","i":"low","e":"days","g":"No changelog and no screenshots (the catalog has no per-entry changelog field or images to show); everything else is closed. The Marketplace card's per-item DETAILS button opens an in-app panel with author/version/summary/categories/permissions/full sha256, a link to the published docs/marketplace/e/<id>.html detail page (rendered source), a raw-source download link, and a prefilled GitHub issue link for bug reports.","w":"Closed 2026-08-10: the prior gap was specifically the missing IN-APP detail surface (the web catalog detail pages already existed). Added a DETAILS toggle per Marketplace row (ui-v2/app.jsx Marketplace) that renders a panel from the already-fetched catalog entry -- no new fetch -- plus three links (full description & source, raw source, report a bug) built from the entry's `id`.","v":"docs/marketplace/index.html:88-91 `<p class=\"summary\">${ext.summary || \"\"}<\/p> ... <span>by ${ext.author || \"unknown\"}<\/span>` assigned via `div.innerHTML = ...` (line 81); marketplace_logic.hpp:61-63 `-- \"summary\" and \"author\" in particular are free text from a remote file and must be escaped by whoever renders them.`; EXTENSIONS.md:141-143 `the manifest's hooks is descriptive metadata for the ca","o":"present","r":"Extender/BApp-store batch: in-app extension detail panel closes #99."},{"a":"extender","f":"[A6] BApp Store: submission and review process (PortSwigger reviews source before publication)","s":"partial","i":"low","e":"days","g":"PR review is still the whole human review model and no third party has used it. No signing, no automated source review. But integrity IS pinned end to end now (manifest sha256 + CI drift check + install-time verification), which the first pass reported as absent.","w":"State CONFIRMED but the auditor's gap statement is now FACTUALLY WRONG and I corrected it. They wrote 'no signing, no hash pinning in the manifest'. The uncommitted working tree adds exactly that: every catalog entry now carries a sha256, CI fails the build on a missing/malformed digest AND on drift between the manifest hash and the committed .js. That is stronger than 'trust the PR'. Still partia","v":"extensions/marketplace.json:+ `\"sha256\": \"8c02c0578289944a6dc858726e7a1357804bff3872a80480fa606b496b554d1a\"` on each entry; .github/workflows/ci.yml `- name: every extension pins a well-formed sha256` / `(.sha256 | test(\"^[0-9a-f]{64}$\"))` and `- name: manifest hashes match the committed extensions` / `run: bash scripts/marketplace_sync.sh --check`; docs/marketplace/index.html:62 `Submit a PR to B","o":"partial","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[A7] Security model around third-party code (Burp: in-process, full JVM privileges, no sandbox, no permission model)","s":"exceeds","i":"low","e":"days","g":"Extensions still share one QJSEngine, so a loaded observe-only script can pollute globals/prototypes another relies on while both are active. reload() now DESTROYS and rebuilds the QJSEngine (rebuildEngine, extensions_api.cpp:93-107 / reload :121-146), so those effects no longer persist past an uninstall or reload. Remaining real gap (tracked separately as task #115): no per-extension execution-time bound -- grep for setInterrupted/isInterrupted/watchdog/deadline in ExtensionsAPI/ is empty, so a runaway handler freezes the main event loop, including the removal endpoint. That hardening (a watchdog thread calling QJSEngine::setInterrupted) is a separate ~1-day build, not required to keep the 'exceeds' verdict.","w":"Re-confirmed 2026-08-11 against live source: default-deny modify-requests/modify-responses grants parsed from the script (ExtensionPerms::isAllowed, enforced at onRequest registration and in doMutateResponse per-handler, extensions_api.cpp:36-59,489-491) -- a real permission model Burp lacks entirely. rebuildEngine confirmed to fully replace the QJSEngine on reload, not just clear a namespace. setInterrupted/watchdog/deadline confirmed still absent (0 grep hits in Src/Core/APIs/Extensions/).","v":"extensions_api.cpp:93-107 rebuildEngine fresh QJSEngine per reload; :36-59 grant-gated registration; :489-491 mayMutate discard; grep setInterrupted/watchdog/deadline ExtensionsAPI/ = empty (no time bound)","o":"exceeds","r":"Wave 0 register-accuracy audit: gap/evidence text was stale (referred to an earlier reload() that only cleared a namespace) -- refreshed to describe the current rebuildEngine behavior and the still-open execution-time-bound gap (task #115), re-verified against live source. State unchanged (exceeds)."},{"a":"extender","f":"[A8] Per-extension declared capability visibility (Burp shows only what the extension registered)","s":"present","i":"medium","e":"hours","g":"None -- the Extensions card in Settings now renders a per-script row with a modifies-traffic / observe-only badge sourced from bootInfo.extensionGrants (the DOWNLOADED script's own declared capabilities, not the marketplace catalog's claim).","w":"Closed 2026-08-10: bootInfo.extensionGrants was already published (control_server.cpp:1240-1244) but nothing in ui-v2 read it. Added a per-script row under the Extensions card (ui-v2/app.jsx SettingsTab) that looks up extensionGrants[filename] and flags modify-requests/modify-responses as 'modifies traffic', anything else as 'observe-only', with the full declared-capability list in a title tooltip. No backend change -- the field already existed and was unread.","v":"extensions_api.cpp:145-147 `appendLog(g.isEmpty() ? QString(\"[ext] loaded %1 (observe-only)\").arg(fi.fileName()) : QString(\"[ext] loaded %1 (granted: %2)\").arg(fi.fileName(), g.join(\", \")));`; control_server.cpp:1237-1241 `const auto &sg = m_wiring.extensions->scriptGrants(); ... bootInfo[\"extensionGrants\"] = grants;`; ui-v2/app.jsx:456-476 renders only `<Row label=\"Folder\">`, `<Row label=\"Loaded\"; ui-v2/app.jsx SettingsTab Extensions card now maps scripts to b.extensionGrants[s] per row (2026-08-10).","o":"present","r":"Extender/BApp-store batch: per-extension capability badges close #102."},{"a":"extender","f":"[B1] Montoya API (burp.api.montoya) — typed, versioned extension API; BurpExtension.initialize(MontoyaApi)","s":"absent","i":"medium","e":"months","g":"No object model, no typed events, no versioning. Extensions receive ad-hoc JS objects built in doMutateRequest/doMutateResponse. A different design rather than a smaller one.","w":"CONFIRMED. I re-ran the greps myself across Src/ ui-v2/ extensions/: montoya=0, IBurpExtender=0, registerExtension/ExtensionPoint=0. I read extensions_api.hpp end to end — the bridge really is exactly four Q_INVOKABLEs, no more.","v":"extensions_api.hpp:297-345 -- the complete bridge, `class ExtensionsApiBridge : public QObject`: `Q_INVOKABLE void log(const QString &message);`, `Q_INVOKABLE void onResponse(const QJSValue &callback);`, `Q_INVOKABLE void onRequest(const QJSValue &callback);`, `Q_INVOKABLE void reportFinding(...)`.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B2] Legacy Extender API (IBurpExtenderCallbacks) retained for backward compatibility","s":"absent","i":"low","e":"months","g":"No compatibility layer. Moot unless Nullock ever hosts a JVM.","w":"CONFIRMED by my own grep: IBurpExtenderCallbacks / registerExtenderCallbacks = 0 hits across Src/, ui-v2/, extensions/. Nothing to upgrade — there is no JVM to host it.","v":"extensions_api.hpp:297-345 defines ExtensionsApiBridge as the sole JS-facing class; no other extension entry point exists in the tree.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B3] Java extension support (load a .jar as an extension)","s":"absent","i":"high","e":"months","g":"No JVM host, so the entire BApp ecosystem is unreachable. Largest single difference in this area.","w":"CONFIRMED. loadAll globs only *.js and I re-read the line; no .jar/JVM/jni references. This is the structural fork in the road for the whole area.","v":"extensions_api.cpp:400 `const QFileInfoList files = QDir(dir).entryInfoList({ \"*.js\" }, QDir::Files, QDir::Name);` -- the only extension discovery path in the codebase.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B4] Python extension support via Jython","s":"absent","i":"high","e":"months","g":"No Python extensions; throwaway Python BApps must be rewritten as ES5-ish JS with no stdlib.","w":"CONFIRMED by my own grep (jython=0) and by the loader glob, which I re-read.","v":"extensions_api.cpp:400 `entryInfoList({ \"*.js\" }, QDir::Files, QDir::Name);` -- the only extension discovery path in the codebase.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B5] Ruby extension support via JRuby","s":"absent","i":"low","e":"months","g":"Absent. Low real-world demand.","w":"CONFIRMED (jruby=0 in my grep; same loader restriction).","v":"extensions_api.cpp:400 `entryInfoList({ \"*.js\" }, QDir::Files, QDir::Name);` -- the only extension discovery path in the codebase.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B6] Extension environment settings: library JAR folder / module import path","s":"absent","i":"medium","e":"weeks","g":"Extensions cannot share code or use libraries; primitives get inlined by hand in every script.","w":"CONFIRMED. `grep -rn installExtensions Src/` = 0 in my own run, so the engine gets no console, no require, no import — the sandbox has no module system to configure.","v":"extensions_api.cpp:253,322 -- the ONLY global installed is the bridge: `m_bridge = new ExtensionsApiBridge(this);` ... `m_engine->globalObject().setProperty(\"nullock\", nullockObj);`","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B7] ProxyRequestHandler / ProxyResponseHandler — DROP a message, force intercept, or follow intercept rules","s":"absent","i":"high","e":"days","g":"An extension cannot block a request, force interception, or annotate/highlight a history row. Rules out blockers, auto-taggers and per-request interception logic.","w":"Re-verified against live source. doMutateRequest (moved 358-379 -> 672-721 across intervening waves) still only reads back method/path/headers/bodyText -- no sentinel, no action enum, no drop path, matching the prior finding exactly. Noted for completeness: proxy.jsx has since grown a #299 per-row highlight+comment layer, but that is a *user*-driven manual UI feature, not an extension hook -- it does not touch the extension-facing gap this item grades on, which is unchanged.","v":"extensions_api.cpp:672-721 doMutateRequest -- the full read-back: `const QString m = entry.property(\"method\").toString();` ... `req.headers = headersFromJs(entry.property(\"headers\")); req.body = entry.property(\"bodyText\").toString().toUtf8();` -- no action/verdict field is ever consulted (line drift from the prior pass's 358-379 citation, content unchanged).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-read doMutateRequest's readback (line drift 358-379 -> 672-721) -- confirms no action/drop field is ever consulted, matching the prior finding exactly. No code change this pass."},{"a":"extender","f":"[B8] Intruder payload generator provider (registerPayloadGeneratorProvider)","s":"absent","i":"medium","e":"days","g":"Extensions cannot feed Intruder, and cannot influence an Intruder request by any other path either.","w":"CONFIRMED again, re-checking the whole bridge surface rather than trusting the old '164-185, four methods' citation, which has drifted -- the surface has grown substantially since (log/onResponse/onRequest/onUnload/registerUnloadingHandler/history/reportFinding/sendToRepeater/sendToIntruder on the main bridge, plus entirely new utils/collaborator/storage bridges for codecs, OOB mint-and-poll, and a KV store) -- none of it payload-generation-shaped. intruder.cpp has also grown 608->956 lines; a fresh grep still returns zero extension references anywhere in it.","v":"extensions_api.hpp:296-436 -- the complete current JS-facing surface (ExtensionsApiBridge plus the utils/collaborator/storage bridges) has no payload-generator registration of any kind; `grep -rni 'extension' Src/Core/Networking/intruder.cpp` (956 lines, up from 608) still returns nothing.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-read the whole extensions_api.hpp bridge surface (grown to 296-436, replacing the stale 164-185/four-method citation) and re-grepped intruder.cpp (now 956 lines, was 608) -- no payload-generator seam either place. No code change this pass."},{"a":"extender","f":"[B9] Intruder payload processor (registerPayloadProcessor) — transform each payload before placement","s":"absent","i":"high","e":"days","g":"The classic escape hatch for custom encodings/signing inside an attack. Without it a bespoke-signed API cannot be fuzzed.","w":"CONFIRMED. Re-read the current bridge surface (extensions_api.hpp:296-436, replacing the stale 164-185 citation) -- no processor registration exists. control_server.cpp's rule-ops handler (moved 3262 -> 3992) still exposes only the built-in transform set, unchanged in shape.","v":"extensions_api.hpp:296-436 -- no processor registration; control_server.cpp:3992 `if (path == \"/api/intruder/rule-ops\")` exposes only the built-in rule set (line drift from 3262).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-read the bridge surface and the rule-ops handler (line drift 3262 -> 3992) -- still no processor-registration seam. No code change this pass."},{"a":"extender","f":"[B10] Session handling action (registerSessionHandlingAction) — extension-provided action invocable from a session rule","s":"absent","i":"high","e":"days","g":"No extension-driven auth/login macro. Custom SSO or signature schemes must be always-on onRequest handlers instead of scoped session rules.","w":"CONFIRMED. Fresh `grep -rnia 'extension|macro|ExtensionsApi' Src/Core/Networking/session_rules*.cpp` still returns only hits for the unrelated session-macro login-flow feature (a stored request-replay macro, not an extension seam) -- zero for actual extension/ExtensionsApi wiring. extensions/aws_sigv4.js:30-36's hard-coded-creds CONFIG block is unchanged, still the only workaround an SSO/custom-signature scheme has.","v":"`grep -rnia 'extension|macro|ExtensionsApi' Src/Core/Networking/session_rules*.cpp` = 0 hits; extensions/aws_sigv4.js:30-36 `var CONFIG = { accessKey: \"\", secretKey: \"\", ...` — the workaround is an always-on onRequest handler with hard-coded creds","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-grepped session_rules*.cpp for extension/macro/ExtensionsApi -- confirms the 'macro' hits are all the unrelated session-handling-rules feature, none an extension seam. No code change this pass."},{"a":"extender","f":"[B11] Custom suite tab (userInterface().registerSuiteTab)","s":"absent","i":"high","e":"weeks","g":"Extensions are headless. Autorize / Turbo Intruder / JWT Editor / Logger++ shapes have no equivalent.","w":"CONFIRMED, and the gap has actually WIDENED in file count even though the conclusion holds: alongside the still-8-line extensions_hub.qml (blank white Rectangle) and the still-0-byte extensions_hub_model.cpp/.hpp, two MORE blank-Rectangle placeholder files have landed since -- Src/FrontEnd/GUI/ExtensionsHub/Components/extensions_console.qml and .../extensions.qml, each an identical 8-line `import QtQuick; Rectangle { ... color: \"#ffffff\" }` stub. Neither is referenced by app.qml or CMakeLists.txt -- confirmed by grep, zero hits for all three file names in both. Three orphaned placeholder shells now exist where the prior audit found one; none is wired to anything, so the mount-point gap is unchanged.","v":"Src/FrontEnd/GUI/ExtensionsHub/extensions_hub.qml (8 lines, unchanged: `Rectangle { id: extensionsHub; width: 400; height: 300; color: \"#ffffff\" }`) plus two newer siblings -- Components/extensions_console.qml and Components/extensions.qml, both identical 8-line blank-Rectangle stubs -- none referenced by grepping app.qml or CMakeLists.txt for any of the three names (0 hits); extensions_hub_model.cpp/.hpp remain 0 bytes.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Found two new but equally-orphaned blank-Rectangle QML stubs (Components/extensions_console.qml, Components/extensions.qml) alongside the original extensions_hub.qml -- none wired into app.qml or CMakeLists.txt, so the no-mount-point conclusion is unchanged, just now evidenced by three stub files instead of one. No code change this pass."},{"a":"extender","f":"[B12] Context menu items (ContextMenuItemsProvider), scoped by InvocationType","s":"absent","i":"medium","e":"days","g":"'Send to <my extension>', the most common BApp integration point, has no equivalent.","w":"CONFIRMED. Fresh repo-wide case-insensitive grep for contextMenu/ContextMenuItemsProvider/InvocationType across Src/ and ui-v2/ (vendor excluded) still returns zero hits.","v":"extensions_api.hpp:296-436 -- no UI registration method on the bridge (line drift from the stale 164-185 citation).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Fresh grep for contextMenu/ContextMenuItemsProvider/InvocationType -- still 0 hits. No code change this pass."},{"a":"extender","f":"[B13] Message editor tabs (registerHttpRequestEditorProvider / HttpResponseEditorProvider)","s":"absent","i":"medium","e":"weeks","g":"The built-in Inspector/Decoder is not extensible.","w":"CONFIRMED. Re-read the whole Settings Extensions card, which has grown substantially since the prior citation (line drift 456-477 -> 1319-1391): it now adds per-extension enable/disable checkboxes, a modifies-traffic/observe-only capability badge per script, an Auto-reload (dev) toggle, and an 'Install bundled' button -- none of it a pluggable editor-tab surface. A fresh grep for registerHttpRequestEditorProvider/HttpResponseEditorProvider still returns 0 hits -- the built-in Inspector/Decoder remains closed to extensions.","v":"ui-v2/app.jsx:1319-1391 -- the complete current extension UI: per-extension Loaded checkbox + modifies-traffic/observe-only capability badge, an Auto-reload (dev) toggle, an Install bundled button, `<Row label=\"Folder\" value={b.extensionsDir} copyable />`, and a 30-line log tail. Still a management list only -- no editor-tab mount point (line drift from the prior 456-477 citation).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. The Settings Extensions card has grown (enable checkboxes, capability badges, auto-reload toggle, Install bundled button, line drift 456-477 -> 1319-1391) but is still a management list, not a pluggable editor-tab surface. No code change this pass."},{"a":"extender","f":"[B14] Scanner insertion point provider (registerScannerInsertionPointProvider)","s":"absent","i":"medium","e":"days","g":"Custom serialization formats cannot be taught to the scanner.","w":"CONFIRMED. Fresh case-insensitive grep for insertion|injectionPoint|insertPoint across Src/ still returns only the same two non-seam hits as before, with line drift: the Intruder §payload§ marker label at Src/App/app.qml:984 (unchanged) and a prose comment in control_server.cpp, now at :7800 (was :6599).","v":"`grep -rnia 'insertion|injectionPoint|insertPoint' Src/` -> Src/App/app.qml:984 (unchanged UI label) and control_server.cpp:7800 (prose comment, drifted from 6599) -- neither is a provider seam.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Fresh grep for insertion/injectionPoint/insertPoint -- same two non-seam hits, line drift 6599 -> 7800 on the comment. No code change this pass."},{"a":"extender","f":"[B15] Extension can issue its own HTTP requests through the tool's stack (api.http().sendRequest)","s":"absent","i":"high","e":"weeks","g":"An extension is purely reactive: it cannot confirm a finding, enumerate, or re-issue a request. This is why no scan-check, macro or crawler BApp equivalent can exist.","w":"CONFIRMED, core gap unchanged -- the bridge still has no I/O-performing method. The surrounding surface has grown since the prior pass in ways worth noting so the register doesn't read as if nothing changed: ExtensionsApiBridge gained sendToRepeater/sendToIntruder (fire-and-forget pushes into those tools' UI, no response returned to the script) and a new ExtensionsCollaboratorBridge exposes generate()/interactions() (mint an OOB token, later poll for out-of-band HTTP/DNS hits). Both are genuinely useful but neither lets an extension issue a request through the tool's stack and read the reply synchronously -- re-read every one of the now much larger set of Q_INVOKABLE methods to confirm none is a disguised sendRequest. None is.","v":"extensions_api.hpp:296-436 -- the complete current bridge surface (9 ExtensionsApiBridge methods + 11 across the utils/collaborator/storage bridges); none performs synchronous request I/O. sendToRepeater/sendToIntruder (:351-354) push only, no return value; collaborator generate()/interactions() (:398,404) is async OOB polling, not request/response I/O.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent for the core ask (no synchronous send-and-read-response method), while noting two new adjacent-but-not-closing additions since the prior pass: sendToRepeater/sendToIntruder (push-only, no response) and the new collaborator bridge's generate()/interactions() (async OOB polling). Neither is I/O an extension can use to confirm a finding synchronously. No code change this pass."},{"a":"extender","f":"[B16] Extension access to Burp Collaborator (api.collaborator().createClient(), poll interactions)","s":"partial","i":"medium","e":"days","g":"No OOB payload generation or interaction polling from an extension.","w":"CONFIRMED after checking the local synonym the brief warned about — 'Collaborator' is 'OAST' here, and oast_logic.cpp does exist — but the bridge exposes none of it. There is no oast/collaborator reference anywhere under Src/Core/APIs, and the four-method bridge has no payload-generation or polling entry point.","v":"extensions_api.hpp:164-185 (complete bridge, no OAST method); the OAST subsystem lives at Src/Core/Networking/oast_logic.cpp and is wired to the scanner in app.cpp:890 `oastCorrelator.setScanner(&scanner);` — never to extensions","o":"absent","r":"absent -> partial. Both named absences closed: nullock.collaborator (Burp's api.collaborator()) now gives extensions OOB payload generation AND interaction polling. generate() mints an OAST token via OastServer::mintToken() and returns { token, hostUrl, pathUrl, port, baseHost }, recording the token; interactions() reads OastServer::hitsSince(0) (HTTP) + DnsSink::hitsSince(0) (DNS), filters to the tokens THIS collaborator minted, and returns each as { id, token, type:'http'|'dns', sourceIp, atMs, host, method, path }. Wired via ExtensionsApi::setOast(&oast,&dnsSink) in app.cpp (OAST + DNS sinks are in the same APIs lib -- no cross-lib callback interface); the collaborator bridge is CppOwned so its minted-token set survives an engine reload (a callback landing after a reload still surfaces). VERIFIED e2e (5/5): a test extension generates a token (interactions empty), a real DNS callback is fired to that token, and after reload interactions() surfaces a dns hit scoped to its token. ctest 100/100, probe 156/156. REMAINDER (why still partial): SMTP interactions (Nullock has no SMTP sink) and the full raw callback body / Burp's per-client object nesting; the core mint+poll for HTTP+DNS is done."},{"a":"extender","f":"[B17] Extension access to sitemap and proxy history (api.siteMap(), api.proxy().history()); adding issues to the sitemap","s":"partial","i":"medium","e":"days","g":"Reclassify absent->partial: the 'add issues' half IS present — reportFinding(severity,kind,summary,evidence,url) routes into the same findings/scanner sink with CWE/OWASP/CVSS enrichment (extensions_api.cpp:61-78), which is the addToSiteMap-issue equivalent. The READ half (api.siteMap()/api.proxy().history()) is still absent — extensions only see the single live entry built per request/response, n","w":"Reclassified absent -> partial (2026-08-02): triage + adversarial-verify agreed; keyed by stable roadmap id, area-guarded. See PARITY-BACKLOG.md.","v":"extensions_api.cpp:61-78 reportFinding->scanner sink (issue-add works); onResponseReceived (196-240) builds one live entry only; no history/siteMap read method on the bridge","o":"absent","r":"PROGRESS (stays partial). Closes the proxy-history READ half: new bridge invokable nullock.history(max) returns the most recent proxy exchanges (method/host/port/path/url/tls/status/responseSize/atMs), Burp's api.proxy().history() equivalent. ExtensionsApi keeps a bounded ring (kMaxHistory) recorded at the TOP of onResponseReceived -- before the no-handlers early-return -- so history is complete even for a script that registered no onResponse handler; ungated (same traffic onResponse already observes); owner-thread only (record + read on the engine thread, no mutex); not cleared on engine rebuild (history is proxy traffic, outlives a reload). e2e vs the live app (4/4): a test extension driven by real proxy traffic (curl -x) reads a history growing 1->2->3 with correct GET/200/url per entry, history(1) clamps to one. ctest 99/99, probe 156/156. With the 'add issues' half already present (reportFinding), the two remaining pieces are api.siteMap() (a distinct tree API -- though an extension can now DERIVE a sitemap from history()) and history body/header access (current entries carry metadata + size, not full bytes)."},{"a":"extender","f":"[B18] Extension can start/configure scans (startAudit / startCrawl) and read scan issues","s":"absent","i":"low","e":"days","g":"Absent.","w":"CONFIRMED. setScanner (now :121, drifted from 80-81) remains a C++-side wiring point only; the JS-facing surface (now :296-436, replacing the stale 164-185 citation) still has no startAudit/startCrawl/read-issues method. reportFinding is still write-only into the sink.","v":"extensions_api.hpp:121 `void setScanner(IFindingSink *scanner) { m_scanner = scanner; }` (line drift from 80-81) -- a C++-side wiring point, not JS-reachable; the JS surface is extensions_api.hpp:296-436.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Line drift only (setScanner 80-81 -> 121); still no scan-control or issue-read method on the JS surface. No code change this pass."},{"a":"extender","f":"[B19] Extension can send items to other tools (sendToRepeater / Intruder / Organizer / Comparer)","s":"partial","i":"medium","e":"days","g":"Extension-driven cross-tool workflow is not possible.","w":"CONFIRMED by my own greps (sendToRepeater=0, sendToIntruder=0) and by reading the bridge.","v":"extensions_api.hpp:164-185 — no cross-tool method","o":"absent","r":"absent -> partial. Cross-tool workflow from an extension is now possible for the two primary attack tools: nullock.sendToRepeater(host,port,tls,request) opens a fresh Repeater tab and populates its target + request; nullock.sendToIntruder(...) loads Intruder's base request. Since APIs deliberately does NOT link Networking, the handlers are std::function callbacks (ExtensionsApi::SendFn) wired from app.cpp with lambdas that drive repeater.addTab/setHost/... and intruder.setHost/setRequestTemplate; ungated (uses the extension's own request data + only stages a tool the user then drives). VERIFIED e2e (7/7): a test extension's sends land -- Repeater snapshot shows target.example:8443 tls + the request text, Intruder snapshot shows intr.example:9443 + the request template. ctest 100/100, probe 156/156. REMAINDER (why still partial): sendToComparer / sendToOrganizer / sendToDecoder from an extension (the '/ Organizer / Comparer' half of the title) not wired yet."},{"a":"extender","f":"[B20] Extension utilities: api.utilities() — Base64/URL/hex/gzip codecs, ByteArray, crypto helpers","s":"partial","i":"medium","e":"days","g":"Every extension re-implements primitives by hand in ES5. No base64, gzip, hashing or byte-level type.","w":"CONFIRMED. The engine setup is two lines and installs exactly one global; with installExtensions never called there is not even a console. I verified the downstream consequence in the shipped extension.","v":"extensions_api.cpp:87-88 `QJSValue nullockObj = m_engine.newQObject(m_bridge); m_engine.globalObject().setProperty(\"nullock\", nullockObj);` — the only global; extensions/aws_sigv4.js inlines SHA-256/HMAC because of it","o":"absent","r":"absent -> partial. Added nullock.utils (Burp's api.utilities() grouping): base64Encode/Decode, urlEncode/Decode, hexEncode/Decode, htmlEncode/Decode, sha256/sha1/md5 -- so an extension no longer hand-rolls base64/hex/hashing in ES5 (the aws_sigv4.js inline-SHA256 the evidence cites). Pure Qt6::Core module extensions_utils_logic.{hpp,cpp} (QByteArray/QUrl/QCryptographicHash) wrapped 1:1 by a grouped ExtensionsUtilsBridge QObject published as nullock.utils, CppOwned so it survives an engine reload() and is re-wrapped each rebuild; ungated (pure text transforms). extensions_utils_logic_test 23/23 (known base64/hex/html vectors + the sha256/sha1/md5 'abc' digests) + 2 mutations (htmlEncode < mis-map; sha256->Sha1 swap); e2e vs the live QJSEngine 12/12 (a test extension's nullock.utils.* results match the pure module). ctest 100/100, probe 156/156. REMAINDER (why still partial): gzip/compression helpers (need a zlib deflate path; extensions already get decompressed response bodies via onResponse) and a byte-array type + the broader Burp utils families (number/random/string) -- JS has no native byte type, so a ByteArray helper is a separate design."},{"a":"extender","f":"[B21] Extension unloading handler (registerUnloadingHandler) — clean teardown","s":"present","i":"high","e":"hours","g":"STALE PRIOR EVIDENCE — reclassify absent->partial. The gap's core claim ('the QJSEngine is never recreated, so an uninstalled script's globals persist in shared scope until restart') is NO LONGER TRUE: reload() now calls rebuildEngine(), which destroys the engine and constructs a fresh one, re-publishing `nullock` (extensions_api.cpp:93-107, 121-146). So the clean-slate half is DONE. What remains ","w":"Reclassified absent -> partial (2026-08-02): independent triage + adversarial-verify agreed; cited files re-confirmed to exist. See PARITY-BACKLOG.md.","v":"extensions_api.cpp:93-107 rebuildEngine() destroys+recreates the engine; reload() 121-146 calls it — the 'globals persist' concern is resolved; no onUnload/registerUnloadingHandler invokable exists (hpp:191-212)","o":"absent","r":"partial -> present. The clean-slate half (rebuildEngine on reload) was already done; this adds the missing teardown-callback half the gap called out. New bridge invokables nullock.onUnload(fn) + the Burp-name alias nullock.registerUnloadingHandler(fn) register an ungated teardown callback (a cleanup hook touches only the script's own state, never the wire -- so it registers like onResponse observation). runUnloadHandlers() fires each once on the owner thread while the engine is still alive, at the START of reload() (before rebuildEngine destroys the engine) and from the destructor (app exit); handlers are isolated (one throwing can't skip the rest) and rebuildEngine() now clears m_onUnloadHandlers too, so none leaks across a reload (QJSValue-lifetime). VERIFIED e2e vs the live app: onUnload does NOT fire on mere load, DOES fire on the next reload (teardown), the alias behaves identically, and the user's real extensions were left untouched. ctest 99/99, probe_smoke 156/156."},{"a":"extender","f":"[B22] Extension settings persistence: persistence().extensionData() / preferences()","s":"partial","i":"high","e":"days","g":"Config is still a hand-edited literal in the .js. The manifest's declared secret handling remains decorative even after the marketplace rewrite. Configuring AWS creds means editing source and reloading.","w":"CONFIRMED and REINFORCED. The obvious upgrade candidate was the new marketplace code, so I checked it specifically: `grep -n config Src/Core/Networking/marketplace_logic.cpp` = 0 hits, and the CatalogEntry struct has no config member. The manifest's config schema — including `\"secret\": true` on the AWS keys — is still read by nothing at all.","v":"marketplace_logic.hpp:64-77 `struct CatalogEntry { QString id; QString name; QString summary; QString version; QString author; QStringList categories; QString url; QString sha256; QStringList hooks; QStringList declaredPermissions; };` — no config field; extensions/aws_sigv4.js:30-36 `var CONFIG = { accessKey: \"\", secretKey: \"\", ...`","o":"absent","r":"absent -> partial. The persistence().extensionData() / preferences() API now exists: nullock.storage.set/get/has/keys/remove/clear, a JSON key/value store (strings, numbers, nested objects/arrays) an extension uses to keep settings/state. Persisted to <appData>/nullock-ext-storage.json -- deliberately a SIBLING of the extensions dir, NOT inside it, so a set() never trips the new auto-reload watcher. Grouped ExtensionsStorageBridge published as nullock.storage, CppOwned so it survives an engine reload(). VERIFIED e2e (8/8): set/get round-trips a string/number/nested-object, has()/keys() correct, the value is written to the sibling file, and after a full app RESTART the extension reads it back on boot. ctest 100/100, probe 156/156. So an extension can now stop hardcoding config (e.g. aws_sigv4's CONFIG literal) and persist it via nullock.storage. REMAINDER (why still partial): (1) the store is GLOBAL, not per-extension isolated (Nullock's shared engine has no per-extension identity at call time; extensions namespace keys) -- Burp's extensionData() is per-extension; (2) no user-facing config INPUT path yet -- Nullock extensions have no per-extension settings UI, so a user still can't enter e.g. AWS creds through the GUI (they'd call the API or the extension self-configures); the manifest's decorative 'secret:true' config schema is a separate injection mechanism, still unwired."},{"a":"extender","f":"[B23] Extensions > Installed tab: per-extension 'Loaded' checkbox to enable/disable without removing","s":"present","i":"high","e":"hours","g":"None -- the Extensions Installed card (ui-v2/app.jsx SettingsTab) now renders bootInfo.extensionAll (every .js present, loaded or disabled) as a checkbox-per-row list instead of only the loaded-scripts list; each checkbox is bound to the extension's persisted enabled state and calls NL.actions.setExtensionEnabled(name, enabled) -> POST /api/extensions/set-enabled, matching the backend contract the de0efca wave already shipped and e2e-verified.","w":"Closed the last gap on this item 2026-08-21: the backend half (de0efca, 2026-08-20) already persisted a per-extension enable/disable state and exposed it via bootInfo.extensionAll + POST /api/extensions/set-enabled, but ui-v2 still read only bootInfo.extensionScripts (loaded-only, no enabled flag, no toggle) -- a disabled extension vanished from the Installed list entirely and there was no way to flip it back on from the GUI. The Installed card now sources its row list from extensionAll ({name, enabled} for every script on disk) and renders a checkbox per row (checked = e.enabled) that calls the new ui-v2/real-data.js NL.actions.setExtensionEnabled(name, next) thin wrapper on toggle, with optimistic local state (React.useState synced from bootInfo via a JSON.stringify-keyed effect, same pattern as the existing mitmBlockedList) and a revert-on-failure fallback. A disabled row shows a plain 'disabled' badge instead of the modifies-traffic/observe-only trust badge, since a disabled script is never (re-)parsed and so carries no live grants to show. Extensions title count switched from extensionScripts.length (loaded-only) to extAllList.length (every installed extension) so a disabled extension still counts toward the header total.","v":"ui-v2/app.jsx SettingsTab: extAllList React.useState seeded from b.extensionAll, toggleExtensionEnabled(name, next) calling NL.actions.setExtensionEnabled; Extensions card row: <input type='checkbox' checked={!!e.enabled} onChange={() => toggleExtensionEnabled(s, !e.enabled)} />. ui-v2/real-data.js: setExtensionEnabled(name, enabled) { return post('/api/extensions/set-enabled', { name, enabled: !!enabled }).then(r => r.json()); }. Backend contract unchanged (already shipped/verified in the de0efca wave): control_server.cpp:1284-1293 bootInfo.extensionAll = [{name, enabled}] via m_wiring.extensions->allScripts()/isExtensionEnabled(); control_server.cpp:6404-6413 POST /api/extensions/set-enabled {name, enabled} -> extensions->setExtensionEnabled(...).","o":"present","r":"partial -> present. The only remaining gap this item named -- the ui-v2 Loaded checkbox in the Installed tab -- is now built, wired to the already-verified backend endpoint. No backend touched. The separate per-project extensionsEnabled template field remains a no-op, but that is a distinct feature (per-project extension state on project switch), not this global enable/disable checkbox."},{"a":"extender","f":"[B24] Extensions > Installed tab: Remove (uninstall) button","s":"present","i":"medium","e":"hours","g":"API only, no UI control, and only for ids that pass safeScriptFileName. Removal leaves the uninstalled script's global-scope side effects live in the shared engine until restart.","w":"UPGRADED — the first pass's evidence ('only two extension endpoints exist') is now out of date. The working tree adds POST /api/marketplace/uninstall backed by a real implementation with path confinement, a canonical-path containment check against symlink escape, and an automatic reload afterwards. It is API-reachable today. Not 'present' because no button exists anywhere: `grep -rna marketplace u","v":"control_server.cpp:5425-5438 `if (path == \"/api/marketplace/uninstall\") { ... const bool ok = Nullock::Core::Marketplace::uninstall(id, m_wiring.extensions->extensionsDir(), &err); if (ok) m_wiring.extensions->reload();`; marketplace.cpp:202-209 `const QString canonicalDir = QFileInfo(extensionsDir).canonicalFilePath(); ... if (canonicalDir.isEmpty() || canonicalFile.isEmpty() || QFileInfo(canonic","o":"partial","r":"Remove button in the marketplace panel, and reload() now REBUILDS the QJSEngine, so an uninstalled script's globals and prototype patches no longer survive. The audit's stated gap -- removal leaving side effects live until restart -- is closed and regression-tested."},{"a":"extender","f":"[B25] Extensions > Installed tab: Up/Down buttons to control invocation order","s":"absent","i":"medium","e":"hours","g":"With multiple mutating extensions the composition order is fixed by filename (alphabetical, deterministic since a QDir::Name sort was added to loadAll()) but still not user-adjustable -- two extensions rewriting the same header still fight, just predictably rather than at random.","w":"CONFIRMED the ask (no reorder control exists) but CORRECTED a stale claim in the prior audit's own 'why': loadAll() -- the call that actually determines handler registration/invocation order -- now sorts with QDir::Name (extensions_api.cpp:400, added since the prior pass), so invocation order is deterministic alphabetical-by-filename, not the arbitrary filesystem order the prior audit's 'fight non-deterministically' language implied. (A second, unsorted entryInfoList call at :298 is refreshWatch()'s file-watch registration, order-irrelevant there.) The user-facing gap is unchanged either way: there is still no Up/Down control, so two extensions touching the same header still fight -- just predictably now, in filename order, rather than at random.","v":"extensions_api.cpp:400 `QDir(dir).entryInfoList({ \"*.js\" }, QDir::Files, QDir::Name)` in loadAll() -- deterministic alphabetical load/registration order (new since the prior audit's 'no sort flag' finding); extensions_api.cpp:683 `for (QJSValue &handler : m_onRequestHandlers)` -- handlers still fire in that registration order with no reorder API or persisted override.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent, but corrected a stale claim -- loadAll() now sorts extension load order with QDir::Name (extensions_api.cpp:400), so invocation order is deterministic alphabetical, not arbitrary as the prior 'why' text implied. Gap text updated to say composition order is fixed-but-predictable rather than fixed-and-random; still no user-facing reorder control. No code change this pass."},{"a":"extender","f":"[B26] Extensions > Installed tab: Add… dialog (choose extension type, file, output/error destination)","s":"stub","i":"high","e":"days","g":"No file picker, no arbitrary local-file install, no type selection, no output/error destination. Only curated-catalog ids can be installed, and only over the API.","w":"Re-verified, held at stub. control_server.cpp's marketplace/install handler (moved 5376-5422 -> 6427ff) is unchanged in shape -- id is still the only input. marketplace.cpp:113-117's safeScriptFileName-derived-from-catalog-id evidence checked line-for-line and stands exactly as cited, no drift. Still no file picker, no arbitrary local-file install, no type selection, no output/error destination -- only curated-catalog ids, only over the API.","v":"control_server.cpp:6427 `if (path == \"/api/marketplace/install\") { ... const QString id = bodyJson.value(\"id\").toString();` (line drift from 5376-5422) -- the only input is a catalog id; marketplace.cpp:113-117 `const QString fileName = safeScriptFileName(entry.id); if (fileName.isEmpty()) { r.error = ...` -- the filename is derived from the catalog, never supplied by the user (unchanged, no drift).","o":"stub","r":"Wave 0 register-accuracy audit: held at stub. Line drift on the install handler (5376-5422 -> 6427ff); marketplace.cpp:113-117 citation unchanged and re-verified exact. No code change this pass."},{"a":"extender","f":"[B27] Extension settings: folder location, reload-on-startup behaviour, auto-update installed extensions","s":"stub","i":"medium","e":"hours","g":"No dedicated extension settings page. Cannot relocate the folder, cannot disable loading at startup, no auto-update setting. An 'Auto-reload (dev)' toggle now exists inline in the Extensions card, but it controls live file-watch reload during development, not reload-on-startup or auto-update -- it doesn't address what this item asks for.","w":"CONFIRMED at stub, with one real addition noted so the register isn't stale: an 'Auto-reload (dev)' checkbox now sits in the Extensions card (ui-v2/app.jsx ~1327), wiring a genuine settings toggle -- but it controls live file-watch reload during development, not the 'reload-on-startup' or 'auto-update installed extensions' behaviours this item specifically asks about, so it doesn't close the gap. extensionsDir() (moved 94-97 -> 352) is still a hard-coded QStandardPaths expression with no setter; loadAll() (moved :89 -> two call sites, :276 constructor and :390 setExtensionEnabled) still runs unconditionally with no startup-disable option; the path is still displayed read-only in ui-v2/app.jsx (Folder row, now :1340, was :460).","v":"extensions_api.cpp:352 `QString ExtensionsApi::extensionsDir() const { return QStandardPaths::writableLocation(QStandardPaths::AppDataLocation) + \"/extensions\"; }` (line drift from 94-97); extensions_api.cpp:276 and :390 `loadAll();` (constructor and setExtensionEnabled, drift from :89) run unconditionally with no startup-disable option; ui-v2/app.jsx:1340 `<Row label=\"Folder\" value={b.extensionsDir} copyable />` (drift from :460) still read-only; the new `Auto-reload (dev)` checkbox sits alongside it (~:1327) but is a dev-mode file-watch toggle, not a startup/auto-update setting.","o":"stub","r":"Wave 0 register-accuracy audit: held at stub. Noted a real but non-closing addition -- an Auto-reload (dev) toggle now exists in the Extensions card, but it's a file-watch setting, not the reload-on-startup/auto-update this item asks about. Line drift refreshed throughout. No code change this pass."},{"a":"extender","f":"[B28] BApp Store: browse installable extensions inside the tool, one-click install","s":"present","i":"high","e":"days","g":"None outstanding for this item's scope (browse + one-click install). BApp Store: search box/category filtering (item [B29]), ratings/last-updated sort (item [B30]), version-compatibility gating (item [B31]), and Pro-only gating (item [B32]) are tracked as separate, distinct roadmap items -- not part of this row's bar.","w":"Re-confirmed 2026-08-11 against live source, and updated for the 2026-08-10 Extender/BApp-store wave (c28f16a): the in-app Marketplace (ui-v2/app.jsx:223-385) is mounted in SettingsTab (app.jsx:639), fetches the merged catalog (NL.actions.marketplaceCatalog -> control_server.cpp:5354), renders per-extension cards with name/version/summary/categories/sha256, and now also a per-item DETAILS panel (author/full sha256/permissions/docs link/raw-source download/prefilled bug-report link). The two-step consent gate is fully wired: first install call sends confirmMutating:false, the server refuses traffic-mutating extensions with needsConfirmation:true (control_server.cpp:5455), and the UI shows the consent panel (app.jsx:315-340) built from permissions read out of the DOWNLOADED+verified bytes. Catalog now holds 14 entries (extensions/marketplace.json), not the 3 present at the original audit. With sha256 pinning + bytes-derived consent this arguably exceeds Burp's BApp store, but is graded 'present' (not 'exceeds') pending the search/ratings/version-gating items above.","v":"ui-v2/app.jsx:223-385 Marketplace component + :639 mount; control_server.cpp:5354 /catalog, :5418 /install (needsConfirmation :5455), :5467 /uninstall; extensions/marketplace.json = 14 ids; c28f16a search input + category chips + per-item DETAILS panel","o":"present","r":"Wave 0 register-accuracy audit: gap/evidence text was stale (still described the pre-c28f16a 3-entry catalog with no search/detail panel). Refreshed to match the live 14-entry catalog, search/category filter, and per-item DETAILS panel; re-verified against source. State unchanged (present)."},{"a":"extender","f":"[B29] BApp Store: search box and category filtering","s":"present","i":"low","e":"hours","g":"None -- the in-app Marketplace (ui-v2/app.jsx) now has the same filter/category-chip model as the published catalog site: a free-text search over name/summary/author/categories, and clickable category chips derived from the live catalog, both applied client-side before the item list renders.","w":"Closed 2026-08-10: ported the filter/chip logic from docs/marketplace/index.html's categories()/filtered() into the Marketplace React component as a useMemo-derived categories list and visibleItems array, with a search <input> and clickable chip row above the item list. No backend change -- all fields were already in the fetched catalog response.","v":"ui-v2/app.jsx:342 state.items.map with no predicate + no <input> in the component; docs/marketplace/index.html:46 search input, :91-113 categories()/filtered(), :183-190 sort handlers","o":"partial","r":"Extender/BApp-store batch: in-app search + category chips close #131."},{"a":"extender","f":"[B30] BApp Store: ratings/popularity, 'Last updated' column and sorting","s":"partial","i":"low","e":"weeks","g":"Two halves. LAST-UPDATED + SORTING now exist on the website store: catalog entries carry a per-entry 'updated' field (extensions/marketplace.json, e.g. dom_taint '2026-06-09') and docs/marketplace/index.html sorts by it (:107-111, sort-updated button). RATINGS/POPULARITY/installs remain absent everywhere with no backend to collect them — CatalogEntry (marketplace_logic.hpp:64-77) has no rating/ins","w":"Reclassified absent -> partial (2026-08-02): independent triage + adversarial-verify agreed; cited files re-confirmed to exist. See PARITY-BACKLOG.md.","v":"marketplace_logic.hpp:64-81 CatalogEntry has no rating/installs/updated member (id/name/summary/version/author/categories/url/sha256/hooks/declaredPermissions/minVersion only); marketplace_logic.cpp:75 only parses the catalog-level `updated` (Catalog::updated) via str(root,\"updated\",32), never a per-entry one; extensions/marketplace.json:24 dom_taint's own per-entry \"updated\":\"2026-06-09\" is present in the source JSON but dropped by the parser; docs/marketplace/index.html:57 sort-updated button, :114 `b.updated` compare.","o":"absent","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"extender","f":"[B31] BApp Store: version-compatibility gating ('requires a later version')","s":"present","i":"medium","e":"hours","g":"RESOLVED: a catalog entry may declare minVersion; parseCatalog reads it, isVersionCompatible + merge(catalog,...,currentVersion) flag an entry needing a newer build as {compatible:false, incompatReason}, surfaced in the /api/marketplace/catalog JSON (including the raw minVersion) with NULLOCK_VERSION baked into the Control target. The in-app Marketplace (ui-v2/app.jsx) now reads compatible/incompatReason/minVersion: an incompatible entry gets a red 'incompatible' badge (title = the reason) and its Install/Update button is disabled with the same reason as its tooltip; the detail panel shows the 'Requires Nullock >= X' line, styled as an error when gated. Original gap (nothing prevented installing an extension written against a different API generation) is closed end to end.","w":"CONFIRMED both halves live. Backend (007b2b9): grep 'minVersion|compatib|incompatReason' across marketplace_logic.{hpp,cpp} + control_server.cpp now hits the full gate (isVersionCompatible, merge(...,currentVersion), the three new /api/marketplace/catalog fields). Frontend (this wave): prior to this change, grep of ui-v2/*.jsx for 'compatible|incompatReason' returned zero hits -- the wire fields existed but nothing read them, so an incompatible entry rendered identically to a normal one and Install would fail only after the click. Now Marketplace() in ui-v2/app.jsx reads x.compatible on every catalog row (badge + disabled Install/Update) and detail.compatible/minVersion in the detail panel.","v":"Src/Core/Networking/marketplace_logic.cpp:102 e.minVersion parsed; :305-311 isVersionCompatible (semver compare, empty either side = compatible); :336-338 merge() sets m.compatible=false + incompatReason = 'requires Nullock >= ' + e.minVersion. Src/BackEnd/Control/control_server.cpp:5964-5968 /api/marketplace/catalog emits minVersion/compatible/incompatReason per entry. ui-v2/app.jsx: Install/Update Btn now passes disabled={x.compatible === false} + a title (the two Btn blocks right after stateBadge/badge('modifies traffic')); an 'incompatible' badge renders next to stateBadge when x.compatible === false; the detail panel adds a 'Requires Nullock >= {minVersion}' line (error-colored when compatible === false).","o":"present","r":"Marketplace UI wave: greys/disables Install and Update on a version-incompatible catalog entry (red 'incompatible' badge + disabled-button tooltip + a 'Requires Nullock >= X' line in the detail panel), closing the frontend half of [B31] left open by 007b2b9's backend gate."},{"a":"extender","f":"[B32] BApp Store: 'Pro' gating — Pro-only BApps flagged and blocked in Community","s":"absent","i":"cosmetic","e":"hours","g":"Not applicable. Arguably an advantage: the Pro-only BApps a Community user cannot run have no analogue here.","w":"CONFIRMED, held not-applicable/absent. CatalogEntry (Src/Core/Networking/marketplace_logic.hpp, now :64-81, gained a minVersion semver-gate field since the prior pass but still no tier/licence field) and a fresh grep of Src/Core/APIs/ExtensionsAPI plus the marketplace TUs for licence/tier/pro confirm no gating concept exists anywhere near extension or marketplace code. Correctly filed as not-applicable bookkeeping rather than a defect -- Nullock is single-tier.","v":"marketplace_logic.hpp:64-81 CatalogEntry (gained a `minVersion` semver-gate field since the prior pass, still no tier/licence field); no licence check appears in Src/Core/APIs/ExtensionsAPI or the marketplace TUs (fresh grep).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent/not-applicable. CatalogEntry grew a minVersion field (unrelated to licensing) since the prior pass; still no tier/licence concept anywhere. No code change this pass."},{"a":"extender","f":"[B33] BApp Store: update notification for installed extensions (available-updates indicator, Reinstall to update)","s":"present","i":"medium","e":"days","g":"None user-facing. All 14 shipped extensions now carry a `// nullock:version` header matching their catalog entry, so the existing merge/badge/Update-button chain (previously dead code -- every install merged as plain Installed) is live: a future catalog version bump renders the update badge, and clicking Update calls the same verified marketplaceInstall() reinstall path used for a fresh install. The one remaining nuance: the separate one-shot install-builtins onboarding action still copies extensions/*.js unconditionally with no version check -- harmless (it always writes the current bundled bytes) but not itself version-aware.","w":"Closed the sole blocking defect this item's own prior wave identified: parseInstalledVersion()/UpdateLogic::compareSemver()/the ui-v2 update badge and Update button were all already correct, but `grep -n 'nullock:version' extensions/*.js` returned zero matches, so every installed extension merged as plain Installed and the whole path was dead. Added a `// nullock:version X.Y.Z` header comment to each of the 14 shipped extensions/*.js, matching that file's own catalog-declared version exactly (dom_taint 0.2.0, the other 13 at 0.1.0), then ran scripts/marketplace_sync.sh (regenerates the sha256 the header edit changed) and scripts/marketplace_site.py (regenerates the 14 published detail pages) so the manifest and site stay generated-not-hand-edited, per that script's own stated purpose. No C++ touched -- data-file-only change to already-tested machinery, so no build risk.","v":"extensions/*.js headers, e.g. aws_sigv4.js:4 `// nullock:version 0.1.0`, dom_taint.js:3 `// nullock:version 0.2.0`; marketplace_logic.cpp:298-303 parseInstalledVersion regex matches the added lines; marketplace_logic.cpp:328-332 merge() now reaches the UpdateAvailable branch once a catalog bump makes compareSemver negative; ui-v2/app.jsx:575-593 badge + Update button -> doInstall(id) -> NL.actions.marketplaceInstall (already wired, previously unreachable in practice); `bash scripts/marketplace_sync.sh --check` and `python3 scripts/marketplace_site.py --check` both green after regeneration.","o":"partial","r":"[B33] partial -> present: all 14 shipped extensions now emit the // nullock:version directive, lighting up the already-built update-available badge + reinstall-to-update flow end to end."},{"a":"extender","f":"[B34] Extension resource control — a runaway extension is killable via Unload","s":"absent","i":"high","e":"days","g":"No execution timeout, no interrupt, no per-extension kill, no unload. A runaway script freezes the main event loop — every proxied request, the UI, and the very endpoints you would use to reload or uninstall it.","w":"CONFIRMED. app.cpp still constructs both ExtensionsApi (now line 752, was 683) and ControlServer (now line 1299, was 974) on the main thread with no moveToThread anywhere in the file (fresh grep, 0 hits). extensions_api.cpp's BlockingQueuedConnection calls (now :642 and :662, was :300-302) are unchanged -- a runaway onRequest/onResponse handler still blocks the calling proxy thread AND, because the JS engine itself lives on the main/GUI thread, the whole app with it. No execution timeout, interrupt, per-extension kill, or Unload-while-running exists.","v":"Src/App/app.cpp:752 `Nullock::Core::ExtensionsApi extensions;` (drift from 683) and app.cpp:1299 `Nullock::Control::ControlServer controlServer(wiring);` (drift from 974) -- both on the main thread, no moveToThread in the file (fresh grep, 0 hits); extensions_api.cpp:642,662 `QMetaObject::invokeMethod(this, \"doMutateRequest\"/\"doMutateResponse\", Qt::BlockingQueuedConnection, ...)` (drift from 300-302).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Line drift on all three citations (683->752, 974->1299, 300-302->642/662); confirmed zero moveToThread calls in app.cpp. No code change this pass."},{"a":"extender","f":"[B35] AI extensions (api.ai() prompts, per-extension AI credit accounting, 'Use AI' toggle)","s":"absent","i":"low","e":"weeks","g":"Absent. Newest Burp axis; nothing comparable exists.","w":"CONFIRMED. Re-checked the now much larger bridge surface (extensions_api.hpp:296-436, replacing the stale 164-185 pointer that covered only 4 methods) end to end, plus a fresh case-insensitive grep for ai(/aiPrompt/api.ai across Src/Core/APIs/ExtensionsAPI -- zero hits either way. No AI surface of any kind exists for extensions, even though the backend gained its own AI surface elsewhere (payload-mutation via local Ollama, /api/payloads/generate, wired into the PAYLOADS tab per UI-NAVIGABILITY.md) -- that capability is tool-driven, not extension-invocable.","v":"extensions_api.hpp:296-436 -- complete JS-facing surface (drift from the stale 164-185 citation), no ai()/prompt method; fresh `grep -rnia 'ai\\(|aiPrompt|api\\.ai' Src/Core/APIs/ExtensionsAPI` -> 0 hits.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-checked the grown bridge surface and confirmed zero ai()/prompt hits; noted the backend's own unrelated AI feature (/api/payloads/generate) isn't extension-invocable either. No code change this pass."},{"a":"extender","f":"[B36] Bambdas: HTTP history filter written as a code snippet","s":"absent","i":"medium","e":"weeks","g":"No user-written filter expressions. Filtering is limited to the predicates the UI exposes.","w":"CONFIRMED. Fresh case-insensitive grep for bambda across Src/, ui-v2/ and extensions/ -- 0 hits, unchanged. ui-v2/proxy.jsx's history filters are still fixed controls; line positions drifted with the file's growth (host filter/search/deepSearch toggle now sit inside a much larger FilterBar after the #299 annotation and other additions) but remain fixed-field UI predicates only, no expression language.","v":"`grep -rnia bambda Src/ ui-v2/ extensions/` -> 0, unchanged; ui-v2/proxy.jsx's FilterBar (now :484-...) exposes only fixed controls -- host filter, free-text search, deepSearch toggle -- line positions drifted with the file's growth (the #299 annotation layer and other additions), unchanged in kind.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Fresh bambda grep still 0; FilterBar line positions refreshed (drifted with file growth), still fixed-field predicates only. No code change this pass."},{"a":"extender","f":"[B37] Bambdas: custom columns in the HTTP history","s":"absent","i":"medium","e":"weeks","g":"No user-computed column.","w":"CONFIRMED. customColumn/addColumn still 0 hits repo-wide. The history table gained a 12th column since the prior citation (was a fixed 11-column table, colSpan={11}; now 12, colSpan={12}, header Host/Method/Status/.../IP/Captured at proxy.jsx:404-432) plus the #299 per-row highlight applied as an inline boxShadow rather than a column -- still zero user-computed columns of any kind.","v":"`grep -rnia 'customColumn|addColumn' Src/ ui-v2/` -> 0 hits, unchanged; ui-v2/proxy.jsx's HistoryTable header (now :404-432) grew a 12th column since the prior citation (was `<td colSpan={11}`, now `<td colSpan={12}`) plus a #299 per-row highlight applied as an inline boxShadow tint (:439) rather than a column -- still zero user-computed columns of any kind.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. customColumn/addColumn grep still 0; history table grew from 11 to 12 fixed columns (colSpan drift 11->12), still no user-computed column mechanism. No code change this pass."},{"a":"extender","f":"[B38] Bambdas: highlight and annotate — colorize matching rows and auto-comment them","s":"partial","i":"high","e":"days","g":"The 'auto' half is still absent -- there is no bambda-style expression engine, so no rule can auto-colorize or auto-comment rows that match a pattern. But the manual half of this ask now exists: a per-row highlight-colour + free-text comment layer (#299) lets a user flag and annotate history rows by hand, client-side, persisted to localStorage. Neither an extension nor a user-written rule can drive it -- every flag is a manual right-click action, one row at a time -- so bulk/scripted triage across a large history still has no equivalent.","w":"UPGRADED one notch from the prior 'no row highlighting or commenting at all, neither user-scripted nor extension-driven' finding, which is now stale. I re-ran the same highlight grep the prior audit used and it still returns nothing bambda-shaped (Src/App/app.qml:306 highlightFollowsCurrentItem and a payload-preview CSS comment, both irrelevant) -- but ui-v2/proxy.jsx has since grown a real per-row annotation feature (#299): ANNOTATION_COLORS + setRowColor/setRowComment/clearRowAnnotation (:3179-3199), a right-click context-menu Highlight swatch row and an Add/Edit Comment prompt (:3482-3520), an ANNOTATED filter chip (:593), and a per-row inline boxShadow tint in the history table (:439) driven by the stored colour. I confirmed by hand that it is purely manual -- there is no matcher/rule/expression input anywhere in the feature, only a per-row click -- so it satisfies the 'colorize and comment' outcome one row at a time but not the 'auto' / rule-matching half the Bambda ask is actually about. Grading this partial rather than leaving it absent reflects that real user-facing outcome without overclaiming the scripted half, which is genuinely still missing.","v":"ui-v2/proxy.jsx:66 (feature marker comment), :3179-3199 (ANNOTATION_COLORS + setRowColor/setRowComment/clearRowAnnotation, localStorage-persisted), :3482-3520 (right-click Highlight swatches + Add/Edit Comment prompt), :593 (ANNOTATED filter chip), :439 (per-row inline boxShadow tint driven by the stored colour) -- all manual, per-row, no expression/matcher input anywhere in the feature (confirmed by reading the full block); `grep -rnia bambda Src/ ui-v2/ extensions/` still 0 hits, so the rule-driven/auto half remains completely absent.","o":"partial","r":"Wave 0 register-accuracy audit: UPGRADED absent -> partial. Found the #299 per-row highlight-colour + comment layer (ui-v2/proxy.jsx, added since this item was last audited) genuinely delivers the manual half of this ask (colorize + comment a row); confirmed by reading the full feature that it is strictly manual/per-row with no matcher or rule input, so the scripted/auto half this item is really about (Bambda-style rule-driven highlighting) remains absent. Gap/evidence/why rewritten to reflect the split honestly rather than either overclaiming or leaving a stale absent grade. No code change this pass -- this is a register correction only."},{"a":"extender","f":"[B39] Bambdas in other tables — Organizer, Logger, Intruder results, WebSockets history, Sitemap","s":"absent","i":"low","e":"weeks","g":"Absent, downstream of having no expression concept.","w":"CONFIRMED, downstream of B36/B38. Fresh grep bambda=0 repo-wide. Note the one exception is now B38 (highlight/annotate on Proxy history), which moved to partial via a manual, non-bambda feature -- but that manual pattern doesn't extend to Organizer/Logger/Intruder-results/WebSockets/Sitemap tables (none of them carry an equivalent per-row annotation layer), so this item's 'downstream of no expression engine, applies nowhere' framing still holds for every table it names.","v":"`grep -rnia bambda Src/ ui-v2/ extensions/` → 0 hits","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Cross-referenced B38's upgrade to partial (a manual, non-bambda annotation layer, Proxy history only) -- confirmed it does not extend to any of the tables this item names. No code change this pass."},{"a":"extender","f":"[B40] Bambda editor: in-place code editor with templates, autocomplete, inline errors; save/load; library repo","s":"absent","i":"low","e":"weeks","g":"Absent.","w":"CONFIRMED. bambda=0 fresh grep. ui-v2/vendor still carries only babel.min.js, react.development.js and react-dom.development.js (checked the directory listing directly) -- no monaco/codemirror or any embeddable code-editor component exists to build a Bambda editor on.","v":"`grep -rnia bambda Src/ ui-v2/` → 0 hits; no monaco/codemirror/snippet module in ui-v2 outside vendor's React+Babel bundle","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-checked ui-v2/vendor's contents directly (babel + react/react-dom only) and re-grepped for monaco/codemirror (0 hits). No code change this pass."},{"a":"extender","f":"[B41] Native GUI surface for extension management (Burp's Extensions tab in the desktop app)","s":"stub","i":"medium","e":"weeks","g":"The named, CMake-listed 'Extensions Hub' renders a blank white rectangle backed by two empty source files. All real extension UI is one card inside SettingsTab in the browser front end — and it still shows no grants, no per-extension enable, no remove, and no marketplace.","w":"CONFIRMED, and re-verified byte-for-byte again as the audit style demands for this item specifically: extensions_hub.qml is still exactly the 8-line blank Rectangle, extensions_hub_model.cpp/.hpp are still 0 bytes each -- and two MORE identical 8-line blank-Rectangle stubs have appeared since (Components/extensions_console.qml, Components/extensions.qml), neither referenced anywhere (0 hits grepping app.qml and CMakeLists.txt for all three names). All real extension UI is still the one ui-v2/app.jsx Settings card (grown since: :1319-1391, was :456-477 -- now with per-extension enable checkboxes and capability badges alongside the folder/loaded/log-tail/reload it had before) -- still no grants UI beyond a read-only per-script badge, no remove button, and the marketplace lives in its own separate Card, not this one.","v":"Src/FrontEnd/GUI/ExtensionsHub/extensions_hub.qml complete contents, unchanged: `import QtQuick` / `Rectangle { id: extensionsHub; width: 400; height: 300; color: \"#ffffff\" }`; two newer identical stubs, Components/extensions_console.qml and Components/extensions.qml, also unreferenced; `ls -la` -> extensions_hub_model.cpp/.hpp both still 0 bytes; ui-v2/app.jsx:1319-1391 (drift from 456-477) is the entire real UI -- now with per-extension Loaded checkboxes and modifies-traffic/observe-only badges alongside the Folder row, 30-line log tail, and Reload button it already had.","o":"stub","r":"Wave 0 register-accuracy audit: held at stub. Same widened-stub finding as B11 (two new orphaned blank-Rectangle QML files); ui-v2/app.jsx real-UI citation refreshed (456-477 -> 1319-1391) to reflect its since-grown per-extension checkboxes/badges. No code change this pass."},{"a":"sequencer","f":"Live capture option: \"Ignore token length differences\" (tolerate variable-length tokens)","s":"present","i":"low","e":"hours","g":"The core analysis (Shannon, char-class, hamming, LCS, sequential) already runs over the full variable-length list -- only the positional and bit-level cross-sample tests require a fixed modal width and silently drop off-width tokens (sequencer_logic.cpp:262 gate `if (modeW<8 || modeC<kDeepMinN || modeC*2<tokens.size()) return r;`), surfacing a bare `applicable:false` at :546 that is indistinguisha","w":"Reclassified stub -> partial (2026-08-02): triage + adversarial-verify agreed; keyed by stable roadmap id, area-guarded. See PARITY-BACKLOG.md.","v":"sequencer_logic.cpp:257-268 (modal-width selection + drop gate), :262 (silent early return -> applicable=false), :544-556 (caller emits only applicable + fields, no dropped count / reason); core tests at :433-539 already consume the raw variable-length list.","o":"present","r":"Closed 2026-08-12: positionalEntropy now ALWAYS reports modalWidth/atModalWidth/offWidth and, when it can't run, a skipReason (length-variance / too-few-tokens / too-few-at-width / tokens-too-short) -- so the previously-indistinguishable bare applicable:false is now diagnosable, and when the cross-sample test DOES run the count of excluded off-width tokens is surfaced instead of silently dropped. The core analysis already tolerated variable lengths (Shannon/char-class/hamming/LCS/sequential run over the raw list); this closes the remaining signal gap. Gating/applicable outcome unchanged. Unit- + mutation-tested (zeroing offWidth fails the counted cases)."},{"a":"sequencer","f":"Manual load: paste newline-delimited tokens or load from file, then \"Analyze now\"","s":"present","i":"high","e":"days","g":"None for the manual-load workflow itself: SequencerTab's textarea accepts newline-delimited pasted tokens, a LOAD FILE button reads a local .txt/.csv/.log via FileReader, a PASTE FROM CLIPBOARD button uses navigator.clipboard.readText() where available (feature-detected, fails closed with a message otherwise), and ANALYZE NOW POSTs the parsed token array to /api/sequencer/analyze. No stdin '-' equivalent in a browser context (not applicable to a GUI) and no bash-only path required anymore.","w":"Closed 2026-08-10: SequencerTab (ui-v2/app.jsx) manual-load box, wired to the pre-existing analyze endpoint.","v":"ui-v2/app.jsx SequencerTab: textarea + tokens useMemo (newline-split/trim/filter), loadFile() FileReader.readAsText, pasteFromClipboard() navigator.clipboard.readText, analyze() -> NL.actions.sequencerAnalyze(tokens) -> POST /api/sequencer/analyze","o":"present","r":"Sequencer batch: manual-load paste/file/clipboard + Analyze now, closes the pure-GUI dimension of this gap."},{"a":"sequencer","f":"Manual load sample summary (token count, shortest / longest token length) shown before analysis","s":"present","i":"low","e":"hours","g":"None: a client-side sequencerSampleSummary(tokens) helper computes token count, shortest length, longest length, and mean length from the pasted/loaded corpus and renders it live under the manual-load box BEFORE the ANALYZE NOW call -- addressing the prior gap that a summary only existed after analysis and only carried mean length (min/max were computed server-side and discarded).","w":"Closed 2026-08-10: pure client-side summary, computed and shown pre-analysis, restoring shortest/longest.","v":"ui-v2/app.jsx sequencerSampleSummary(tokens) pure helper + SequencerTab's summary useMemo/render block, shown above the ANALYZE NOW button","o":"present","r":"Sequencer batch: pre-analysis client-side sample summary (n / shortest / longest / mean), closes the reachability gap."},{"a":"sequencer","f":"Analysis Summary: overall result (entropy estimate in bits) with a stated confidence level and \"amount of data analyzed\"","s":"partial","i":"medium","e":"weeks","g":"The confidence level and the \"amount of data analyzed\" statement are now DONE: result.summary carries verdict + score + a confidence (low/medium/high driven by sample adequacy) + significanceLevel + effectiveBitsPerToken + tokensAnalyzed/avgTokenLength/decodedBits/meetsRecommendedSample/meetsFipsSample + a prose dataAnalyzed line tying n and the decoded-bit count to the estimate. Still partial for the two remaining pieces: no per-significance-level entropy CURVE (a table of the estimate/verdict across 0.1%/1%/5%), and the score deductions are still hand-tuned with no per-flag attribution in the output (three independent flags can drive a 128-bit CSPRNG token to \"predictable\" without saying which cost what).","w":"Confidence + data-analyzed implemented in analyzeTokens (result.summary) and mutation-proven: the confidence tiers are locked by Tests/sequencer/sequencer_test.cpp (10/20 tokens -> low, 150x8-hex -> medium, 200x32-hex -> high; M1 defeating the medium tier and M2 dropping the too-few gate each fail only their targeted case). Confidence is tied to SAMPLE ADEQUACY (SampleSizeGuidance), the honest limiter, not to the verdict. Held at partial only for the entropy-curve + per-flag-attribution items above.","v":"sequencer_logic.cpp:1287-1310 analyzeTokens summary block: `summary[\"confidence\"]=...; summary[\"significanceLevel\"]=alpha; summary[\"effectiveBitsPerToken\"]=effectiveBits; summary[\"tokensAnalyzed\"]=tokens.size(); summary[\"decodedBits\"]=double(bit.bits); summary[\"dataAnalyzed\"]=...` (tiers: tooFew||!estimable -> low, !fipsBitsMet -> medium, else high). Schema in sequencer.hpp:126-148. Verified: Tests/sequencer/sequencer_test.cpp confidence-tier cases at :785-804 (10/20 tokens -> low, 150x8-hex -> medium, 200x32-hex -> high).","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-verified sequencer_logic.cpp's analyzeTokens summary block (function drifted to :966, summary assembly now at 1287-1310) -- confidence/significanceLevel/effectiveBitsPerToken/tokensAnalyzed/avgTokenLength/decodedBits/meetsRecommendedSample/meetsFipsSample/dataAnalyzed are all present and tier-gated exactly as described (tooFew||!estimable->low, !fipsBitsMet->medium, else high). Confirmed against Tests/sequencer/sequencer_test.cpp:785-804 (10/20 tok->low, 150x8-hex->medium, 200x32-hex->high) -- tiers unchanged. No per-significance-level entropy curve and no per-flag score attribution exist anywhere in the file (grepped for 'curve'/'attribution'/'perFlag': 0 hits). Claim holds; evidence line numbers refreshed."},{"a":"sequencer","f":"Effective entropy (bits assigned per character position from that position's observed character-set size, summed across positions)","s":"present","i":"medium","e":"days","g":"None -- a per-position effective-entropy estimate now sits alongside the global one. positionalEffectiveBits() sums log2(observed alphabet size) across the modal-width cohort's columns, so a token that is hex in columns 0-7 (4 bits each) and drawn from a reduced alphabet in 8-31 is credited its TRUE region-by-region keyspace, not the blended global average. Reported as shannon.perPositionEffectiveBits.","w":"Closed 2026-08-24: added the pure positionalEffectiveBits(tokens) in sequencer_logic.cpp (per-column distinct-char count -> log2 -> sum), emitted as shannon.perPositionEffectiveBits in analyzeTokens' JSON. It is a lower bound that tightens with samples (conservative for a keyspace figure). Mutation-proven: dropping the log2 or using a global alphabet instead of per-column both fail the structured-corpus assertions.","v":"sequencer_logic.cpp positionalEffectiveBits(): modal-width cohort, per-column `QSet<QChar>` distinct count, `bits += std::log2(seen.size())` (1-symbol column adds 0); emitted at the shannon block `shannon[\"perPositionEffectiveBits\"] = positionalEffectiveBits(tokens);`. Tests: sequencer_test.cpp -- a hex-prefix + reduced-alphabet-suffix corpus scores ~56 bits (true keyspace) and BELOW the global rate*length estimate, while a uniform 32-hex corpus scores ~128 and agrees with the global estimate.","o":"present","r":"Wave 2: backfilled audited_state + reconciled -- the feat commit (a878a0e) flipped state/gap/why/evidence but never added the audited-page's reconciled block, so this closed item was invisible in the roadmap page's \"reconciled since audit\" list. No code change."},{"a":"sequencer","f":"Character-level test: Character count analysis (per-position chi-square on the distribution of characters, with a p-value per position)","s":"present","i":"medium","e":"days","g":"None -- positionalCharChiSquare() now runs a real per-column chi-square of the observed character distribution against a uniform distribution over that column's observed alphabet (dof = distinct-1), converts each column's statistic to a p-value via the exported chiSquareSurvival() (regularized upper incomplete gamma), and flags columns at a Bonferroni-corrected threshold (0.01/columns). Unlike the entropy-vs-sibling reference, this catches a generator biased UNIFORMLY across every column (each column fails against uniform on its own). Reported as positional.charChiSquare {columns, failures, minPValue, biased}.","w":"Closed 2026-08-24: added positionalCharChiSquare (modal-width cohort, per-column histogram -> chi-square-vs-uniform -> chiSquareSurvival p-value -> Bonferroni pass/fail) alongside the existing per-column entropy. chiSquareSurvival is exported and unit-tested against standard chi-square critical values (dof 1/3/10/15) on BOTH the series and continued-fraction branches. Mutation-proven: breaking either survival branch fails the critical-value table; removing the Bonferroni flags a clean corpus.","v":"sequencer_logic.cpp positionalCharChiSquare() + chiSquareSurvival(); emitted at `posObj[\"charChiSquare\"]`. Tests: sequencer_test.cpp -- chiSquareSurvival matches the chi-square table to <0.003; a corpus with one column biased ~75% toward 'a' FLAGS charChiSquare while a clean 32-hex corpus does not.","o":"present","r":"Wave 2: backfilled audited_state + reconciled -- the feat commit (9ba914e) flipped state/gap/why/evidence but never added the audited-page's reconciled block, so this closed item was invisible in the roadmap page's \"reconciled since audit\" list. No code change."},{"a":"sequencer","f":"Bit-level test: FIPS monobit test, evaluated at every bit position independently","s":"present","i":"medium","e":"days","g":"None -- bitLevelTests now runs a per-bit-position monobit over the modal decoded-byte-width cohort (iterating `per`, not the flattened `cat`): for each bit position it counts 1s across tokens and applies the erfc monobit p-value, with a Bonferroni-corrected threshold (0.01/positions) so the family-wise false-positive rate stays ~1% across all positions. A single stuck/biased bit that the aggregate monobit dilutes 1:(width*8) now fails independently and sets bitLevel.anyFail. Reported as bitLevel.perBitMonobit {positions, failures, minPValue, failed}.","w":"Closed 2026-08-24: kept the aggregate monobit and ADDED the per-position pass over the modal-width cohort. Bonferroni was essential -- a naive 0.01 over 256 positions false-positives ~2.5 times on random data (caught by a clean-corpus regression assertion + an existing strong-random test before commit). Mutation-proven: removing the Bonferroni correction reintroduces the clean-corpus false positive; disabling the threshold misses the stuck bit.","v":"sequencer_logic.cpp bitLevelTests() per-bit-position block: modal decoded-byte-width cohort, `const double alpha = 0.01 / double(positions)`, per-position `onesP` count -> `erfc(sObs/sqrt2)` -> `if (p < alpha) ++r.perBitFails`; wired into anyFail and emitted as bitLevel.perBitMonobit. Tests: sequencer_test.cpp -- a corpus with one always-1 nibble bit FLAGS perBitMonobit while the aggregate monobit passes (the dilution it catches); a clean 32-hex corpus does NOT flag.","o":"present","r":"Wave 2: backfilled audited_state + reconciled -- the feat commit (1de965a) flipped state/gap/why/evidence but never added the audited-page's reconciled block, so this closed item was invisible in the roadmap page's \"reconciled since audit\" list. No code change."},{"a":"sequencer","f":"Bit-level test: Correlation test (correlation between distinct bit positions, with significance adjusted for interdependence)","s":"present","i":"medium","e":"days","g":"None -- bitLevelTests now correlates EVERY PAIR of bit positions across the modal-width cohort (not just byte lag-1): for each pair it builds the 2x2 contingency table and computes chi-square (1 dof) = n*phi^2 -> p via chiSquareSurvival, flagging pairs at a Bonferroni-corrected threshold (0.01/pairs) -- the significance adjustment for testing every interdependent pair. A bit-3-vs-bit-47 truncated-LCG relationship (invisible to byte lag-1) is caught, and no junction pairs are involved (it iterates per-token bit columns, not the flattened stream). Reported as bitLevel.bitCorrelation {pairs, failures, minPValue, failed}, folded into anyFail.","w":"Closed 2026-08-24: added the all-pairs bit-position correlation (phi/chi-square per pair, Bonferroni over all pairs, capped at 1024 positions to bound O(positions^2*n)). The byte lag-1 serial correlation is kept as-is. Mutation-proven: disabling the flag misses a copied-bit pair; using a naive 0.01 (no Bonferroni) false-positives on a clean corpus across the ~8k pairs.","v":"sequencer_logic.cpp bitLevelTests() inter-bit-position correlation block: per-position bit columns over the cohort, 2x2 chi = num*num*N/den (num=both*N-a1*b1), p=chiSquareSurvival(chi,1), `if (p < 0.01/pairs) ++bitCorrFails`. Tests: sequencer_test.cpp -- forcing bit position 40 to equal bit 5 in every token FLAGS bitCorrelation; an independent-bit corpus does not.","o":"present","r":"Wave 2: backfilled audited_state + reconciled -- the feat commit (8502f0d) flipped state/gap/why/evidence but never added the audited-page's reconciled block, so this closed item was invisible in the roadmap page's \"reconciled since audit\" list. No code change."},{"a":"sequencer","f":"Token bit-conversion across encodings (map the token's character set to a bit sequence for the bit-level tests)","s":"present","i":"medium","e":"days","g":"CORRECTED: (a) an ODD-length hex corpus fails `(t.size() % 2) != 0`, falls through, and is silently decoded as BASE64 — the report then claims `\"scheme\":\"base64\"` for a hex corpus; (b) base32/base36/alphanumeric are silently relabelled base64 too; (c) the genuine total loss is any corpus containing a character outside `[A-Za-z0-9+/_-]` — which includes JWTs (`.`), and any decimal-with-separator or URL-encoded token: those report `applicable:false` and get ZERO bit-level analysis. Any single non-conforming token in the corpus kills the whole test via `break`.","w":"I re-read decodeCorpusBytes at :304-333 and the first pass's characterisation of the failure trigger is WRONG in a way that matters in both directions. `b64Re` is `^[A-Za-z0-9+/_-]+={0,2}$`, which MATCHES base32, base36 and alphanumeric session IDs — so those corpora are NOT lost, they are decoded (as base64) and DO get bit-tested. Conversely there are two silent-wrong paths the first pass missed.","v":"sequencer_logic.cpp:306-332: `static const QRegularExpression hexRe(\"^[0-9a-fA-F]+$\"); static const QRegularExpression b64Re(\"^[A-Za-z0-9+/_-]+={0,2}$\"); bool allHex = !tokens.isEmpty(); for (const QString &t : tokens) { if (t.isEmpty() || (t.size() % 2) != 0 || !hexRe.match(t).hasMatch()) { allHex = false; break; } } ... bool allB64 = !tokens.isEmpty(); for (const QString &t : tokens) { if (t.siz","o":"present","r":"Closed 2026-08-11: decodeCorpusBytes rewritten to pick the scheme by charset MAJORITY. Both silent-wrong paths fixed: (a) an odd-length hex corpus is now HEX (odd tokens left-padded to preserve the half-byte) instead of falling through and being decoded+labelled base64; (c) a single non-conforming token (a truncated sample, a JWT's '.') is now SKIPPED (with the count surfaced as bitLevel.skipped) instead of setting the whole corpus applicable:false and zeroing all bit-level analysis. A >=50% majority is required so a genuinely mixed corpus still reports not-applicable. Mutation-proven twice (revert-skip-to-fatal fails the (c) cases; count-even-hex-only fails the (a) case). Residual (documented, cosmetic): base32/base36/alphanumeric is decoded correctly but labelled base64 -- Qt has no base32 decoder, and Burp likewise doesn't distinguish it, so this stays at parity."},{"a":"sequencer","f":"Sequential / counter token detection (Burp infers this indirectly from low entropy; no dedicated test)","s":"exceeds","i":"medium","e":"hours","g":"Detects bare decimal/hex counters only. A prefixed counter (`sess_1001`), a suffixed one, a zero-padded-with-separator one, or a base64-wrapped one is reported `looksSequential:false, looksMonotonic:false`. Such corpora still tend to score \"predictable\" via the keyspace deduction, but the analyst is told the wrong reason — and a LONG prefixed counter (40-char prefix + 8-digit counter) clears `varLen`-based deductions too. Not an exceed over Burp: Burp's indirect low-entropy inference is encoding-agnostic and would still flag it.","w":"DOWNGRADED exceeds -> partial. The quoted code is verbatim correct, but the first pass never looked at what feeds it. `looksSequential` and `looksMonotonic` both go through `decodeNumeric` -> `parseToken`, which requires the ENTIRE token to match `^[0-9]+$` or `^(0[xX])?[0-9a-fA-F]+$`. `sess_1001`, `user-42`, `AAAAZg==` — the counter shapes that actually appear in the wild — all fail and are invis","v":"sequencer_logic.cpp:41-53 `static const QRegularExpression decRe(\"^[0-9]+$\"); static const QRegularExpression hexRe(\"^(0[xX])?[0-9a-fA-F]+$\"); ... if (decRe.match(t).hasMatch()) { out = t.toLongLong(&ok, 10); return ok; } if (hexRe.match(t).hasMatch()) { ... } return false;` — no affix stripping. Call sites pass the RAW list: :533 `const bool seq = looksSequential(tokens, delta);` and :534 `const ","o":"exceeds","r":"UPGRADED partial -> exceeds. The partial verdict was correct and its concrete reason (looksSequential/looksMonotonic route through parseToken, which rejects the whole token, so wrapped counters sess_1001/user-42 were false-negatives Burp's low-entropy inference still caught) is now FIXED: stripCommonNumericWrapper strips a shared non-numeric prefix/suffix (up to its last / from its first non-digit -- constant wrapper only, never a varying digit) before the counter tests. Prefixed/suffixed/zero-padded decimal & hex counters are now detected with their TRUE step; a bare stepped counter (100,200,300, all-digit suffix) keeps delta 100 (regression-locked); wrapped noise does not become a false counter (all mutation-proven). sequential.delta value is now locked too, not just the boolean. With the dedicated looksSequential/looksMonotonic/delta verdict -- which Burp has NO equivalent for -- now covering wrapped counters, Nullock exceeds Burp. Residual: base64-wrapped counters stay keyspace/entropy-flagged (predictable) not sequential-labelled, matching Burp's indirect approach."},{"a":"sequencer","f":"Structural / keyspace grading against a modern standard (Burp reports entropy bits but does not grade against NIST SP 800-63B)","s":"present","i":"low","e":"hours","g":"The grading is genuine but unlabelled: `effectiveBitsPerToken` is emitted, the 60/124 thresholds are not, the standard is not, and the score blends the keyspace verdict with six unrelated deductions so the user cannot recover \"this token is below the 128-bit target\" from the output. Add an explicit `keyspaceGrade` field and this becomes a true exceed.","w":"DOWNGRADED exceeds -> present. The code is verbatim as quoted and the capability is real and genuinely absent from Burp — but \"exceeds\" overstates it. There is no stated grade against a named standard anywhere in the OUTPUT: SP 800-63B appears only in a source comment at :583-585. The user receives an unlabelled 0-100 score in which the keyspace deduction is indistinguishable from the six other de","v":"sequencer_logic.cpp:1010 `shannon[\"effectiveBitsPerToken\"] = effectiveBits;`; score deductions at :1227-1237 (`if (effectiveBits < 60) score -= 55; else if (effectiveBits < 124) score -= 15;` ... `if (combinedBits < 2.0) score -= 25;` ... `if (lcs.size() > varLen / 2 && varLen > 8) score -= 30;`); the 128-bit target and NIST SP 800-63B are named only in a code comment at :1216-1218, not emitted in the JSON output -- no `keyspaceGrade` field exists.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"sequencer","f":"Session handling rules: named, ordered, individually enable/disable-able rules in a rules editor","s":"present","i":"high","e":"weeks","g":"GUI editor now ships: the SESSIONS tab (ui-v2/app.jsx SessionsTab) gains a Session handling rules section -- add/edit/delete a named rule with host+path glob, extract-from (header/cookie/JSON path/regex) + extract key + variable name, inject-into (header/cookie/body/URL query) + inject key + template, and a per-rule enable/disable checkbox, plus a live captured-variables readout with a Clear button. The bin/nullock session-rules CLI editor from the prior audit still exists too. Honest remainder: no persistence across restarts (tracked separately, see \"Cookie jar and session rules persist...\" -- state absent) and no manual drag-to-reorder control (rules apply in array/insertion order, matching how the engine evaluates them and the sibling Match & Replace RULES tab's own precedent of no reorder UI despite a ruleMove backend action existing unused).","w":"Closed 2026-08-12: /api/session-rules/set (whole-list replace) and /api/session-rules/clear-vars were fully wired in the backend and published on every snapshot poll (root[\"sessionRules\"]={rules,variables}, control_server.cpp:1587-1611) but had zero frontend callers -- confirmed by grep across ui-v2/*.jsx and real-data.js before this change. The new editor reads/writes that exact contract with no backend change.","v":"ui-v2/app.jsx SessionsTab Session-handling-rules section (sessionRuleUpsert/sessionRuleRemoveAt/sessionRuleToggle pure helpers + the editor form/list/variables readout); ui-v2/real-data.js sessionRulesSet/sessionRulesClearVars actions and NL.sessionRules snapshot field; field names (name/enabled/hostGlob/pathGlob/extractFrom/extractKey/variable/injectInto/injectKey/injectTemplate; variables as a flat string map) matched verbatim against control_server.cpp:1587-1611 (snapshot) and :3869-3895 (/api/session-rules/set, /clear-vars).","o":"present","r":"Sessions tab gains a Session handling rules editor (name/enable/host+path glob/extract/inject fields) wired to the previously-orphaned /api/session-rules/set + /clear-vars; closes the GUI-reachability gap."},{"a":"sequencer","f":"Rule scope — URL scope (all URLs / suite scope / custom include-exclude URL list)","s":"partial","i":"medium","e":"days","g":"A custom include/exclude URL list now exists per rule: SessionRule gains includeUrls/excludeUrls (JSON round-tripped via /api/session-rules), and matches() consults the pure SessionRulesLogic::urlScopeMatches (globs against host+path, query stripped; empty include => all; exclude beats include), so \"everything except /logout\" is expressible as include=[*], exclude=[*/logout*]. Still partial for the \"use suite scope\" checkbox and protocol/port matching (ui-v2 + scope wiring). Separately, the reverse problem remains: an UNCONFIGURABLE suite-scope gate is imposed upstream at proxy_server.cpp:1447 (`if (!isInScope(req.host)) return;`) BEFORE the session hooks, so an out-of-scope host gets no session handling regardless of a rule.","w":"Confirmed verbatim, both the globs and the anchoring. Held at partial. I add one finding: an implicit suite-scope gate DOES exist, but it is applied to the wrong thing and cannot be turned off (see item 22 of Group B and item 14 here).","v":"session_rules.hpp:49-50 `QString hostGlob = \"*\"; QString pathGlob = \"*\";`; session_rules.cpp:171-173 `return resolve(r.hostGlob).match(host).hasMatch() && resolve(r.pathGlob).match(stripQuery(path)).hasMatch() && SessionRulesLogic::urlScopeMatches(host, path, r.includeUrls, r.excludeUrls);`; session_rules_logic.cpp:17-24 globToRx loop (unchanged). Suite-scope gate now at proxy_server.cpp:1688 `if (!isUrlInScope(req.tls, req.host, req.port, req.path)) return;` (renamed from isInScope(host), now also protocol/port-aware, but still applied before the session hooks with no per-rule override).","o":"","r":"Wave 0 register-accuracy audit: held at partial. hostGlob/pathGlob struct fields drifted 45-46 -> 49-50 (unchanged content); matches() return drifted 65-66 -> 171-173, now a three-clause return with the previously-landed urlScopeMatches include/exclude check appended -- content matches the gap's own already-updated description verbatim. globToRx (session_rules_logic.cpp:12-25, loop body 17-23) is byte-identical, no drift in the cited lines. The upstream suite-scope gate moved from proxy_server.cpp:1447 `isInScope(req.host)` to :1688 `isUrlInScope(req.tls, req.host, req.port, req.path)` -- a real signature change (the scope engine grew protocol/port/advanced-rule matching via ProxyServer::isUrlInScope + setAdvancedScope), but the substance for THIS item is unchanged: it is still an unconditional early return applied before SessionManager::injectInto and SessionRules::applyToRequest, with no per-rule opt-out. Still no 'use suite scope' checkbox or protocol/port field on SessionRule itself. Claim holds; evidence refreshed."},{"a":"sequencer","f":"Rule action: \"Use cookies from the session handling cookie jar\"","s":"partial","i":"high","e":"days","g":"A global per-host boolean living in a different subsystem, not an orderable rule action: cannot be path-scoped, cannot be sequenced against other actions, cannot be restricted to named cookies. Two silent suppressors: (1) the host must be in scope — proxy_server.cpp:1447 returns before injection; (2) Repeater and Intruder never call applyRequestRules at all (grep for \"session\" in repeater.cpp and intruder.cpp: zero hits).","w":"Every cited line verified verbatim (the autoInject endpoint is at control_server.cpp:9489, not 9348 — minor drift, substance correct). Held at partial, and I am ADDING a second silent-failure gate the first pass missed: the scope early-return in applyRequestRules suppresses cookie injection entirely for out-of-scope hosts, before the injectInto call is ever reached.","v":"session_manager.cpp:110-119 `void SessionManager::injectInto(...) { if (req.host.isEmpty()) return; ... auto it = m_byHost.constFind(lowercaseHost(req.host)); if (it == m_byHost.constEnd()) return; if (!it->autoInject) return; use = it->cookies; }`. Toggle: session_manager.cpp:165-176 `setAutoInject`, endpoint control_server.cpp:10775 `if (path == \"/api/sessions/autoInject\") {`, UI ui-v2/app.jsx:7062-7064 the auto-inject checkbox in the Sessions panel. `grep SessionManager Src/Core/Networking/repeater.cpp Src/Core/Networking/intruder.cpp`: 0 hits -- the cookie jar still never reaches either tool.","o":"","r":"Wave 0 register-accuracy audit: held at partial (the cookie-jar-specific claim). injectInto/setAutoInject/endpoint/UI line numbers refreshed (93-103->110-119, 146-157->165-176, control_server.cpp 9489->10775, app.jsx ~190->7062). Silent suppressor (1), the scope early-return, moved 1447->1688 (see item #70/156) and still applies before injectInto. Silent suppressor (2) needed correcting, not just re-lining: the ORIGINAL 'grep session in repeater.cpp/intruder.cpp: zero hits' claim is now FALSE -- both files import session_rules.hpp and call m_sessionRules->applyToRequestBytes(..., ToolRepeater/ToolIntruder) (repeater.cpp:160-161, intruder.cpp:656-657 and :880-881), wired live via repeater.setSessionRules()/intruder.setSessionRules() in app.cpp:1108/1111. That is the SEPARATE SessionRules {{var}}-injection pipeline (item #72/159's mechanism, now scoped by a new per-rule `tools` bitmask), not this item's SessionManager cookie jar -- Repeater and Intruder still hold no SessionManager pointer at all (grep for SessionManager in both .hpp/.cpp: 0 hits), so 'use cookies from the session handling cookie jar' specifically remains Proxy-only. State holds at partial, but the supporting evidence for suppressor (2) needed retargeting to avoid citing a now-false grep result."},{"a":"sequencer","f":"Rule action: \"Set a specific cookie or parameter value\" (static or derived value)","s":"present","i":"medium","e":"hours","g":"A purely static rule (\"always set X-Debug: 1 on this host\") can never fire — line 143 bails until an unrelated extract rule has populated the host's bag. And once it can fire, a rule whose own variable was never captured injects the literal string `{{token}}` into the header, cookie, form body or query string instead of being skipped — a fail-open that corrupts the request and is invisible without a tracer.","w":"The static-rule-never-fires claim is CONFIRMED verbatim at :143. Held at partial — but I found a strictly worse companion bug the first pass missed: once ANY variable exists for the host, an unresolved `{{var}}` is injected VERBATIM rather than skipped, so the feature does not merely no-op, it puts literal template text on the wire.","v":"session_rules.cpp:141-143 verbatim: `vars = m_varsByHost.value(req.host); } if (rs.isEmpty() || vars.isEmpty()) return;`. The verbatim-injection path: :150-154 `const QString templ = r.injectTemplate.isEmpty() ? QString(\"{{%1}}\").arg(r.variable.isEmpty() ? r.injectKey : r.variable) : r.injectTemplate; const QString value = substitute(templ, vars); if (value.isEmpty()) continue;` combined with sess","o":"present","r":"Both silent-failure paths fixed. (1) Dropped the `|| vars.isEmpty()` bail in applyToRequest so a purely static rule (no {{var}}) injects regardless of the per-host bag. (2) Added the pure SessionRulesLogic::hasUnresolvedPlaceholder and skip any rule whose substituted value still holds an un-resolved {{name}} -- no more literal `{{token}}` on the wire. Unit-tested (10 cases) + 2 mutations; e2e vs a raw-socket mock captured the wire bytes proving `X-Static-Test: fixedvalue123` injects on an empty bag while a missing-var rule emits neither the header nor {{token}} garbage. ctest 99/99, probe_smoke 156/156."},{"a":"sequencer","f":"Macro item configuration: per-item custom parameter handling — derive a parameter value from a prior response (cookie / form field / custom rule), and update the final request's parameters from the macro response","s":"partial","i":"high","e":"days","g":"The extraction vocabulary is good and there IS no form-field extractor (only header/cookie/JSONPath/regex/status — no HTML form parser). Values thread forward between chain steps only; there is no \"final request\" whose parameters get updated, because the chain is attached to nothing — `ChainRunner::run` has exactly one caller (control_server.cpp:8994) and the chain's own HttpClient (chain_runner.cpp:52 `HttpClient client;`) means its responses never reach the cookie jar or the session-rules bag either.","w":"Struct verified verbatim (chain_runner.hpp:26-31). Endpoint line numbers in the first pass had drifted (~8831/8853 -> actually 8974/8994) but the substance holds. Held at partial: a user CAN accomplish \"derive a value from response 1 and apply it to request 2\" by making request 2 a chain step, which is a real if awkward version of this capability.","v":"chain_runner.hpp:27-32 verbatim: `struct Extract { QString var; enum From { Header, Cookie, Json, Regex, Status } from = Header; QString key; };`. extractOne implemented at chain_runner.cpp:20-47 covering all five. Substitution + CL repair at chain_runner.hpp:88-90; sanitization at :87 `QString sanitizeExtractedValue(const QString &v);`. Wiring: control_server.cpp:10210 `/api/chain/run` builds `steps` then :10254 `Nullock::Core::ChainRunner::run(steps, continueOnError)`. Second caller: session_rules.cpp:446 `SessionRules::runMacro` -> `Nullock::Core::ChainRunner::run(macro.steps, false)`, whose result is merged via `ingestVariables(macro.sessionHost, result.vars)` (:448) into the SessionRules variable bag that applyToRequest/applyToRequestBytes injects into Proxy, Repeater and Intruder traffic.","o":"","r":"Wave 0 register-accuracy audit: held at partial, WITH a correction to the 'why' field's central claim. Extract struct / extractOne / substitution helpers verified verbatim modulo a small line shift (26-31->27-32, extractOne 21-46->20-47). But 'ChainRunner::run has exactly one caller (control_server.cpp:8994)' is now factually wrong: SessionMacro (session_rules.hpp:93-101, landed in commit 88cbe99 -- see scanner-area item #94's own upgrade, already reconciled in commit 9defca8) added a SECOND caller, SessionRules::runMacro (session_rules.cpp:434-451), which replays macro.steps through the exact same ChainRunner::run and then durably ingests the extracted vars into SessionRules' per-host bag (session_rules.cpp:448 ingestVariables) -- which the injection pipeline (applyToRequest/applyToRequestBytes) then threads into subsequent Proxy/Repeater/Intruder requests. So for a NAMED, persisted SessionMacro specifically, the chain is no longer 'attached to nothing': deriving a value from response 1 and updating request N+1's parameters now works end-to-end, including auto re-auth on a logged-out trigger. This does NOT fully close the gap: (a) it only applies to a configured SessionMacro, not an ad-hoc /api/chain/run chain, which still has no downstream consumer of its own; (b) the form-field extractor gap (item #85/170) is untouched; (c) crawl/deep-audit's own HttpClient still never consults SessionRules (confirmed: no SessionRules reference in crawler.cpp or the runDeepAudit call path -- see item #85/200). State held at partial for these remaining reasons, but the 'attached to nothing' framing in the original gap/why is stale for the login-macro case -- flagged here rather than silently re-affirmed."},{"a":"sequencer","f":"Cookie jar: capture cookies from all tools, with a \"monitor traffic from\" setting per tool (Proxy / Repeater / Scanner / Intruder / Sequencer / Extender)","s":"partial","i":"high","e":"days","g":"Proxy-only, hard-wired at app.cpp:779, no per-tool setting and no way to add one without touching C++. Repeater, Intruder AND the chain runner each construct their own HttpClient and never emit responseReceived, so a session refreshed during a Repeater login — or by a `nullock chain` login sequence — is invisible to the jar. WebSocket responses are explicitly excluded too (session_manager.cpp:35 `if (req.method.startsWith(\"WS\")) return;`).","w":"Confirmed verbatim in app.cpp and session_manager.cpp, and I independently confirmed the Repeater/Intruder gap by grepping those two files for \"session\" — zero hits, so it is not a naming issue. Held at partial (capture works, from exactly one tool, with no setting).","v":"Src/App/app.cpp:937-940: `Nullock::Core::SessionManager sessions; proxy.setSessionManager(&sessions); QObject::connect(&proxy, &Nullock::Proxy::ProxyServer::responseReceived, &sessions, &Nullock::Core::SessionManager::onResponseReceived);` -- the sole feed. Capture at session_manager.cpp:45-51 `for (const auto &h : resp.headers) { if (h.first.compare(\"Set-Cookie\", Qt::CaseInsensitive) != 0) continue; ... }`. WebSocket exclusion at session_manager.cpp:37 `if (req.method.startsWith(\"WS\")) return;`. `grep -n onResponseReceived|SessionManager Src/Core/Networking/repeater.cpp Src/Core/Networking/intruder.cpp Src/Core/Networking/chain_runner.cpp`: 0 hits -- capture (as opposed to the separate SessionRules injection pipeline items #71/#72 discuss) is still Proxy-only.","o":"","r":"Wave 0 register-accuracy audit: held at partial. app.cpp wiring drifted 777-780 -> 937-940 (identical content); session_manager.cpp's Set-Cookie capture loop drifted 39-44 -> 45-51; the WS exclusion drifted :35 -> :37 (all unchanged content, small shifts from earlier additions in the file). Re-confirmed Repeater/Intruder/ChainRunner still construct their own HttpClient and never call SessionManager::onResponseReceived or hold a SessionManager pointer at all (distinct from the SessionRules {{var}}-injection pipeline, which items #71/#72 (157/159) now confirm DOES reach Repeater/Intruder via a per-rule tools bitmask -- capture is a different, still- unaddressed half of this gap). No 'monitor traffic from' per-tool setting exists for the cookie jar. Claim holds; evidence line numbers refreshed."},{"a":"sequencer","f":"Cookie jar honors cookie path scope","s":"present","i":"low","e":"hours","g":"Correct as implemented. Two scope caveats, neither a correctness defect: it only runs on the proxy inject path (injectInto is called solely from proxy_server.cpp:1484), and the cookie's Path is never surfaced in the UI (ui-v2/app.jsx:1932-1946 renders name / value / HO / S / SameSite only), so a path-suppressed cookie is undiagnosable from the app.","w":"Attacked hardest per instructions and it survives. I read session_manager_logic.cpp:81-116 and the inject site in full. The dot-segment normalisation is real RFC 3986 5.2.4, the directory-prefix and '/'-boundary cases are both handled, query and fragment are stripped, and an absent or relative path correctly defaults to \"/\". Enforcement is at the actual inject site, not just declared. Held at pres","v":"session_manager_logic.cpp:94-116 verbatim: `QString cp = cookiePath; if (cp.isEmpty() || !cp.startsWith('/')) cp = QStringLiteral(\"/\"); QString rp = reqPath.isEmpty() ? QStringLiteral(\"/\") : reqPath; const int cut = rp.indexOf(QChar('?')); if (cut >= 0) rp = rp.left(cut); const int hash = rp.indexOf(QChar('#')); if (hash >= 0) rp = rp.left(hash); ... rp = removeDotSegments(rp); if (cp == rp) retur","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"sequencer","f":"Cookie jar viewer: list every cookie, and add / edit / remove individual cookies by hand","s":"present","i":"medium","e":"days","g":"None -- add/edit/remove now round-trip through the backend. POST /api/sessions/setCookie upserts a cookie by name (SessionManager::setCookie, control_server.cpp) covering both 'add a cookie obtained out-of-band' and 'edit a value'; POST /api/sessions/removeCookie deletes exactly one cookie (SessionManager::removeCookie), distinct from the pre-existing whole-host/whole-jar clear. The Sessions tab's Cookie Jar section (ui-v2/app.jsx) gained an Add-cookie button per host plus Edit/Del buttons per cookie row, wired via NL.actions.sessionSetCookie/sessionRemoveCookie (ui-v2/real-data.js).","w":"Closed 2026-08-21: the prior audit correctly found /api/cookies was GET-only with no mutating counterpart for a single cookie. Added the missing backend surface -- pure isValidCookieName/upsertCookie/removeCookieByName helpers in session_manager_logic.{hpp,cpp} (RFC 6265 token-name validation reused from parseSetCookie, so a hand-typed name can't smuggle a second cookie via header injection on the next inject), SessionManager::setCookie (upserts by name, creates the host session if missing, treats a manual cookie as a session cookie so it is never auto-pruned by cookieExpired) and SessionManager::removeCookie, plus the two new POST routes -- then wired both into the existing Cookie Jar UI. A host must already appear in the jar (i.e. have been proxied at least once) to add its first manual cookie; there is no free-text 'new host' entry point, a reasonable scope limit since Burp's own jar is also populated from observed traffic.","v":"Src/Core/Networking/session_manager_logic.{hpp,cpp} (isValidCookieName/upsertCookie/removeCookieByName); Src/Core/Networking/session_manager.{hpp,cpp} (SessionManager::setCookie/removeCookie); Src/BackEnd/Control/control_server.cpp POST /api/sessions/setCookie + /api/sessions/removeCookie; ui-v2/app.jsx Cookie Jar section (Add cookie / Edit / Del buttons); ui-v2/real-data.js sessionSetCookie/sessionRemoveCookie; Tests/session_manager/session_manager_test.cpp (name-validation + upsert/remove list-op coverage).","o":"present","r":"Cookie jar gains real per-cookie mutation: backend setCookie/removeCookie (upsert-by-name, single-cookie delete) plus Add/Edit/Del controls on the Sessions tab's Cookie Jar section, closing the item's last honest gap (no backend endpoint for the three per-cookie mutations). This cloud session cannot build/run ctest -- new pure-logic unit tests added and hand-traced against the implementation; will confirm the session_manager ctest target passes against a green GitHub Actions run before treating this fully verified."},{"a":"sequencer","f":"Per-host isolation of captured session values (Burp's cookie jar is domain-scoped; captured macro variables are global)","s":"exceeds","i":"low","e":"hours","g":"None on the injection path — a host-A secret cannot be injected into a host-B request. Caveat: `variables()` deliberately flattens every host's bag into one namespace for the snapshot, so a same-named variable from a different host overwrites in the READ view and all captured secrets appear together in the polled snapshot JSON. Isolation is enforced where it matters (egress) but is not maintained in the introspection surface.","w":"Verified verbatim on both the store and read sides, plus the declared member. The isolation on the INJECT path is genuine and is a real security property Burp's global macro bag does not have. Held at exceeds — but with a caveat the first pass missed: the same class has a deliberately flattened cross-host reader that is published in the snapshot.","v":"session_rules.cpp:236-240 store side verbatim: `// Store under the HOST the value was extracted from -- never inject a // host-A secret into a host-B request. auto &hostVars = m_varsByHost[req.host]; for (auto it = newVars.cbegin(); it != newVars.cend(); ++it) hostVars.insert(it.key(), it.value());`; read side :251-253 `// ONLY variables captured from THIS request's host -- a secret extracted // from another host must never ride along cross-origin. vars = m_varsByHost.value(req.host);`; member session_rules.hpp:192 `QHash<QString, QHash<QString, QString>> m_varsByHost;`. Flattened read view confirmed at session_rules.cpp:133-141 `variables()` (later host wins on a name collision) -- the caveat still holds.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"sequencer","f":"Safety of injected session values (Burp substitutes macro-derived values verbatim)","s":"exceeds","i":"low","e":"hours","g":"None on the sanitisation itself. Adjacent weakness (tracked under item 15): the same function leaves an UNRESOLVED `{{var}}` in the output string, which is then injected verbatim because it is non-empty — sanitisation is sound, resolution is not.","w":"Every cited line verified verbatim: CR/LF plus C0 stripping, ';' stripping for cookies, JSON-context escaping, and the single-pass substitution that blocks a captured value from expanding into another placeholder. This is a genuine hardening layer Burp does not have. Held at exceeds.","v":"session_rules_logic.cpp:105-114 verbatim: `QString sanitizeHeaderValue(const QString &v) { QString out = v; out.remove('\\r').remove('\\n'); QString clean; clean.reserve(out.size()); for (const QChar c : out) if (c.unicode() >= 0x20 || c == '\\t') clean.append(c); return clean; }`; :116-118 `sanitizeCookieValue` strips ';' on top; JSON escape :120-128 `jsonEscapeInner` (serialize-then-unwrap for a correctly escaped inner literal); single-pass substitute() at :76.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"sequencer","f":"Cookie jar transport safety (do not replay a Secure cookie over cleartext)","s":"present","i":"medium","e":"hours","g":"The gate is still a port heuristic, not a TLS check: injectableOverTransport returns `port == 443` for Secure cookies. Confirmed HttpRequest (proxy_server.hpp:34-44) has NO tls/secure/scheme field, and session_manager.cpp:131 passes only req.port. Fix: (1) add `bool tls = false;` to Nullock::Proxy::HttpRequest; (2) set it true at the two places requests are constructed on a TLS connection (proxy M","w":"Reclassified present -> partial (2026-08-02): independent triage + adversarial-verify agreed; cited files re-confirmed to exist. See PARITY-BACKLOG.md.","v":"session_manager_logic.cpp:118-121 (`if (!c.secure) return true; return port == 443;`); session_manager.cpp:131 (`injectableOverTransport(c, req.port)`); proxy_server.hpp:34-44 (HttpRequest struct — method/target/host/port/path/headers/body/timestamp, no tls flag).","o":"present","r":"Closed 2026-08-12 (SECURITY). Replaced the port==443 heuristic with a real TLS check: added `bool tls=false` to Proxy::HttpRequest, set true on the MITM'd HTTPS paths (proxy_server.cpp H2 + the two sslClient read loops; the plain Connection::run leaves it false), changed injectableOverTransport(c,int port)->(c,bool tls){return c.secure?tls:true;} and its caller session_manager.cpp req.port->req.tls. The heuristic both LEAKED a Secure cookie over cleartext on :443 and REFUSED it over TLS on a non-standard port (:8443); the bool check fixes both. Fail-closed: an unknown/default transport never injects a Secure cookie. Mutation-tested (ignoring transport fails the Secure-over-cleartext cases)."},{"a":"sequencer","f":"Sequencer tool tab (dedicated UI with Live capture / Manual load / Analysis sub-tabs)","s":"present","i":"high","e":"weeks","g":"None -- the SEQUENCER tab (ui-v2/app.jsx SequencerTab) now has all three named sub-areas: Manual Load (paste/load-file/paste-clipboard + sample summary + ANALYZE NOW), Analysis (full results render), and Live Capture (host/port/TLS + raw request + extract-from picker + count/throttle, START/STOP/CLEAR, a progress readout, harvested tokens fed straight into the Manual Load corpus).","w":"Closed 2026-08-23: the Live Capture sub-area named absent in the 2026-08-10 wave note is now built -- the backend engine landed 2026-08-17 (f910a9e) but had no UI caller until this wave wired it up.","v":"ui-v2/app.jsx SequencerTab's Live capture card (capHost/capPort/capTls/capRequest/capExtractFrom/capExtractKey/capCount/capThrottleMs state + captureStart/captureStop/captureClear); ui-v2/real-data.js NL.actions.sequencerCapture{Start,Stop,Clear,Tokens}.","o":"present","r":"Sequencer Live Capture UI wave: wired the existing capture engine/API (f910a9e) into SequencerTab, closing the tab's last missing sub-area."},{"a":"sequencer","f":"Send to Sequencer (context-menu handoff from Proxy history / Repeater / Target)","s":"present","i":"high","e":"days","g":"Wired from Proxy history's DetailPane, Repeater's request/response panes, and Target: the SiteMap tree's onSelectLeaf sets the exact same selectedRowId the HistoryTable uses, so a site-map leaf click renders the identical shared DetailPane underneath -- SEQUENCER button included, no separate per-Target wiring needed. Two honest caveats, same class already accepted for the sibling Send to Comparer/Intruder items: it is a toolbar button, not a literal right-click context-menu entry, and the button requires an actual text selection (grabbed from the textarea at click time) rather than offering whole request/response, since sending a whole HTTP message as a single 'token' would be meaningless for entropy analysis.","w":"Register-accuracy fix, re-verified 2026-08-24: the prior gap text claimed 'Target/scope has no send-to-Sequencer path at all (there's no per-request view there to select a token from)', but that is stale against live source. ui-v2/proxy.jsx's ProxyTab renders SiteMap and DetailPane side by side in one shared layout; SiteMap's onSelectLeaf prop (line ~3005) dispatches the same selectedRowId the HistoryTable's onSelect uses, and DetailPane's row prop is `rows.find(r => r.id === selectedRowId)` regardless of which control set that id -- so clicking a Target/site-map leaf populates the identical DetailPane instance, SEQUENCER button and all (confirmed live: showSitemap defaults to true in tweaks, ui-v2/app.jsx:288, so the tree is on-screen by default). This mirrors the grading already given to the sibling 'Send to Intruder from other tools' and 'Comparer: \"Send to Comparer\" from any Burp message' items, both 'present' despite the same toolbar-button-not-menu nuance and despite Comparer's own gap text admitting it isn't wired from every named source either. No code change this pass -- gap/why/evidence corrected to match live source; state moves partial -> present for consistency with sibling grading now that the 'Target has no path' claim is confirmed false.","v":"ui-v2/proxy.jsx ProxyTab: SiteMap onSelectLeaf={(e, id) => dispatch({type:\"set\", payload:{selectedHost:e.host, selectedOrigin:e, selectedRowId:id}})} (~line 3005); HistoryTable onSelect={r => dispatch({type:\"set\", payload:{selectedRowId:r.id}})} (~line 3084) -- both write the same selectedRowId; `const selectedRow = rows.find(r => r.id === selectedRowId)` (~line 2959) feeds the one <DetailPane row={selectedRow} onSendSequencer={...}> instance (~line 3104-3120) regardless of selection source. ui-v2/app.jsx:288 tweaks.showSitemap default true, passed to ProxyTab as showSitemap prop so the SiteMap tree renders by default. DetailPane's SEQUENCER button/sendSelectionToSequencer unchanged from the 6be90f4 wave.","o":"present","r":"Register-accuracy fix (no code change): the 'Target/scope has no send path' half of this item's gap text was stale -- Target's SiteMap leaf selection has shared the same selectedRowId/DetailPane as Proxy history since the proxy.jsx SiteMap component was built, so the SEQUENCER button already reaches Target too. Corrected gap/why/evidence and moved state partial -> present, matching the sibling Send-to-Comparer/Send-to-Intruder items' existing grading for the same toolbar-button-not-menu nuance. Live Capture (#168-171) stays a separate, larger absent item."},{"a":"sequencer","f":"Live capture — repeatedly issue the selected request and harvest the token from each response","s":"present","i":"blocker","e":"weeks","g":"None -- SequencerTab's Live capture panel drives the full engine: host/port/TLS + a raw request template, an extract-from picker (header/cookie/JSON path/regex/status) + key, shot count + throttle, START/STOP/CLEAR, and a live progress readout (done/total/harvested/emptyExtract/httpErrors/transportErrors/lastStatus). Harvested tokens stream into the same corpus the Manual Load / Analysis sub-areas already use, so a capture flows straight into randomness analysis, Copy/Save, and export with no extra step.","w":"Closed 2026-08-23: f910a9e (2026-08-17) shipped the backend engine + API but left the UI as its own honest remainder ('the Live Capture UI sub-panel ... is the remaining piece'); this wave adds that panel with no backend change.","v":"ui-v2/app.jsx SequencerTab (capPoll polling /api/sequencer/capture/tokens every 1.5s while running, captureStart/captureStop/captureClear); ui-v2/real-data.js NL.actions.sequencerCaptureStart/Stop/Clear/Tokens; control_server.cpp:5105-5188 (unchanged) /api/sequencer/capture/{start,stop,clear,tokens}.","o":"present","r":"Sequencer Live Capture UI wave: frontend-only wiring of the existing capture engine (f910a9e) -- Start/Stop/Clear + progress + corpus harvest, no backend change."},{"a":"sequencer","f":"Live capture token location: Cookie (dropdown of cookies seen in the response)","s":"present","i":"high","e":"days","g":"None -- SequencerTab's Live Capture panel (ui-v2/app.jsx) now shows a live \"cookies seen so far\" <select>, auto-populated from the distinct Set-Cookie names the capture engine has actually observed in captured responses so far (SequencerCapture::snapshot()'s new cookieNames field), refreshed on the same 1.5s poll the rest of the panel already uses. Picking an entry fills the existing free-text extract-key field, which stays editable by hand for a cookie not yet seen or before any shot has completed.","w":"Closed 2026-08-23 (partial -> present): the prior wave's free-text-only key field is now backed by a real auto-populated picker, closing the literal \"dropdown of cookies seen in the response\" ask. Backend: SequencerCapture tracks the distinct Set-Cookie NAMES (not values) seen across a run in a mutex-guarded, capped (kMaxCookieNames=64 -- a target minting a fresh name every response can't grow it unbounded) list, reset on start()/clear(), exposed as snapshot()'s new cookieNames field. /api/sequencer/capture/tokens already forwards the whole snapshot() object (control_server.cpp:5167), so no control_server.cpp change was needed -- the new field reached the frontend for free. Frontend: the picker renders only in Cookie extract-from mode, seeded from the already-polled capSnapshot.cookieNames, with a friendly \"none yet\" placeholder before the first Set-Cookie response arrives.","v":"Src/Core/Networking/sequencer_capture_logic.{hpp,cpp} cookieNameFromSetCookie (7 unit-tested cases, Tests/sequencer_capture/sequencer_capture_test.cpp); sequencer_capture.{hpp,cpp} m_cookieNames/kMaxCookieNames + snapshot()'s cookieNames field, reset in start()/clear(), populated in run()'s per-shot Set-Cookie scan; ui-v2/app.jsx SequencerTab's new cookie-picker <select>, gated on capExtractFrom === 'cookie'.","o":"present","r":"Sequencer live-capture cookie-picker wave: backend now tracks distinct Set-Cookie names seen per run and exposes them via the existing snapshot()/tokens endpoint; SequencerTab's Live Capture panel gets a \"cookies seen so far\" dropdown in Cookie mode that fills the existing free-text extract key, closing the item's literal \"dropdown of cookies seen in the response\" ask."},{"a":"sequencer","f":"Live capture token location: Form field (auto-listed HTML form field values, for anti-CSRF tokens)","s":"absent","i":"medium","e":"days","g":"Absent, and the enabling primitive (an HTML form parser feeding an extractor) does not exist elsewhere to borrow.","w":"Confirmed, and I checked harder than the first pass did: neither the session-rule extractor nor the chain-runner extractor has a form-field mode either, so there is no HTML form parser anywhere that could be wired up. This is absent twice over.","v":"SequencerCaptureLogic::ExtractFrom (sequencer_capture_logic.hpp:23-30) enumerates FromHeader/FromCookie/FromJson/FromRegex/FromStatus/FromDelimiter -- explicitly mirrored from ChainRunner::Extract::From (header comment :10-12) with ONE addition (FromDelimiter, a literal start/end-marker extractor) and still no form-field mode. session_rules.hpp:53-58 (SessionRule::ExtractFrom) and chain_runner.hpp:29 (ChainRunner::Extract::From) likewise have no Form option. No HTML form parser exists anywhere in the extraction layers.","o":"","r":"Wave 0 register-accuracy audit: held at absent, but the evidence needed real re-derivation, not just a line-number refresh -- a live-capture engine (Src/Core/Networking/sequencer_capture.cpp/.hpp + sequencer_capture_logic.cpp/.hpp) was added since the last audit, giving Sequencer its own token-harvesting extraction vocabulary independent of ChainRunner/SessionRules. Checked it specifically for a form-field mode: SequencerCaptureLogic::ExtractFrom (sequencer_capture_logic.hpp:23-30) has Header/Cookie/Json/Regex/Status plus one NEW option, FromDelimiter (a literal start/end-delimiter extractor, key encoded \"<start>\\x1f<end>\") -- useful for scraping an inline-HTML token by surrounding text, but still not an HTML FORM-FIELD parser (no DOM/attribute-aware extraction; a delimiter is just two literal strings). ChainRunner::Extract::From (chain_runner.hpp:29) and SessionRule::ExtractFrom (session_rules.hpp:53-58) are unchanged, still four options, no Form. No HTML form parser exists anywhere in Src/. State holds at absent; the enabling primitive genuinely still does not exist, though the new delimiter mode narrows the practical gap for anti-CSRF tokens with stable surrounding markup."},{"a":"sequencer","f":"Live capture token location: Custom location (define start/end delimiters or a regex extraction rule on the response)","s":"present","i":"high","e":"days","g":"None -- both extraction modes are now GUI-reachable in the SEQUENCER tab's live-capture panel. SEQ_CAPTURE_EXTRACT_FROM gains a 'delimiter' option; picking it swaps the single key input for two fields (start/end delimiter) that encode to SequencerCaptureLogic's '<start>\\x1f<end>' key format at capture-start time. The regex mode (closed 2026-08-17) already had its UI.","w":"Closed 2026-08-27: added the delimiter-mode UI (ui-v2/app.jsx SequencerTab) -- capDelimStart/capDelimEnd state, a start/end-delimiter option in the extract-from select, and encoding to the backend's FromDelimiter key format on captureStart(). The backend half (FromDelimiter, parseExtractFrom) was already implemented and unchanged by this wave.","v":"ui-v2/app.jsx SEQ_CAPTURE_EXTRACT_FROM 'delimiter' option + capDelimStart/capDelimEnd inputs, encoded as capDelimStart + \"\\x1f\" + capDelimEnd in captureStart(); Src/Core/Networking/sequencer_capture_logic.cpp FromDelimiter branch (unchanged) already decodes that exact format.","o":"present","r":"Wired the delimiter-mode UI onto the already-implemented FromDelimiter backend, closing the last open gap on this item (regex mode was closed 2026-08-17)."},{"a":"sequencer","f":"Live capture controls: Start / Pause / Stop, running token count, capture progress panel","s":"partial","i":"medium","e":"days","g":"Start, Stop, running token count, and a full capture-progress panel (done/total/harvested/emptyExtract/httpErrors/transportErrors/lastStatus, plus corpus-guard notes) are now UI-reachable in SequencerTab's Live capture card, polling every 1.5s while a capture runs. Pause remains genuinely unbuilt at the engine level -- SequencerCapture has no pause/resume primitive, only start/stop -- so there is nothing for a Pause button to call.","w":"Narrowed 2026-08-23 (partial -> partial, gap-narrowing not a state flip): the 2026-08-17 wave shipped Start/Stop + the progress snapshot at the API level only ('the control-panel UI is pending'); this wave adds that UI. Pause was never built at any layer and stays the honest remainder.","v":"ui-v2/app.jsx SequencerTab's START/STOP/CLEAR CAPTURE buttons + capSnapshot progress readout; Src/Core/Networking/sequencer_capture.cpp snapshot() fields (unchanged); grep for pause/resume in sequencer_capture.{hpp,cpp} = no match.","o":"absent","r":"Start/Stop + a running token count + capture progress now exist at the engine/API level: /api/sequencer/capture/start and /stop, with the snapshot's sequencerCapture slice reporting running/done/total/harvested (+ emptyExtract/httpErrors/transportErrors/lastStatus). PARTIAL: Pause is not built (only Stop), and the control-panel UI is pending."},{"a":"sequencer","f":"Live capture request engine settings: number of threads, throttle between requests, retry on failure","s":"partial","i":"medium","e":"days","g":"Throttle-between-requests is now UI-reachable (a throttleMs number field in SequencerTab's Live capture card, clamped [0,60000] server-side). Thread-count is intentionally NOT offered at any layer -- capture fires sequentially by design, since rapid parallel identical requests risk tripping rate-limits/lockout on the very session being sampled -- a deliberate omission, not a gap to close. 'Retry on failure' has no operator-facing setting: the engine automatically backs off on a 429's Retry-After header, but there is no configurable retry-count/backoff-policy control.","w":"Narrowed 2026-08-23 (partial -> partial, gap-narrowing not a state flip): the 2026-08-17 wave shipped throttleMs + automatic 429 backoff at the API level only; this wave adds the throttle UI. Thread-count stays a deliberate non-goal; a configurable retry policy remains unbuilt.","v":"ui-v2/app.jsx SequencerTab's throttle (ms) number input -> req.throttleMs; Src/Core/Networking/sequencer_capture_logic.cpp clampThrottleMs/retryAfterMs (unchanged).","o":"absent","r":"Pacing settings are partly built: a per-shot throttleMs (clamped [0,60000]) and automatic 429 Retry-After backoff (bounded + interruptible) pace the loop. The thread-count knob is intentionally NOT offered -- capture fires sequentially on one worker by design (rapid parallel identical requests trip rate-limits / account lockout on the very session being sampled). Remaining: the settings UI."},{"a":"sequencer","f":"Live capture: \"Auto analyze\" (re-run the analysis automatically every N tokens captured)","s":"absent","i":"low","e":"days","g":"Absent. Also note the design would have to change: several tests (positionalEntropy, bitLevelTests) recompute over the full corpus, so incremental re-analysis is O(N) per batch.","w":"Confirmed. analyzeTokens is a one-shot pure function with no incremental or streaming form — I read its full signature and body.","v":"Src/Core/Networking/sequencer_capture.cpp/.hpp: a full live-capture engine now exists (SequencerCapture::run, :108-199) that fires N requests and harvests one token per response into a corpus (m_tokens). control_server.cpp:5511-5535 `/api/sequencer/capture/tokens` recomputes `Nullock::Core::Sequencer().analyze(toks)` (whole-corpus analyzeTokens) fresh on EVERY call (:5527-5529), gated by SequencerCaptureLogic::corpusGuard. ui-v2/app.jsx:4352-4372 `capPoll` calls this endpoint every 1500ms while a capture is running (`setInterval(capPoll, 1500)` at :4370) but only consumes `r.tokens` (folds new tokens into the corpus textarea, :4357-4362) -- `r.analysis`/`r.corpusNote`/`r.distinct` are stored in `capSnapshot` (:4356) but never rendered; the visible Sequencer results panel is only ever populated by the separate, manually-triggered ANALYZE NOW action.","o":"","r":"Wave 0 register-accuracy audit: held at absent, but the underlying facts changed enough to need a full re-derivation, not a line refresh. A live-capture engine (sequencer_capture.cpp/.hpp, sequencer_capture_logic.cpp/.hpp) landed since the last audit and IS wired to auto-run the full randomness analysis: /api/sequencer/capture/tokens recomputes analyzeTokens() over the whole harvested corpus on every call (control_server.cpp:5527-5529), and the UI already polls that exact endpoint every 1.5s while a capture is in flight (app.jsx capPoll/setInterval, :4352-4372) -- so the mechanical pieces for 'auto analyze every N tokens' (a live poll re-running the full analysis) already exist and already fire automatically. The gap survives on a technicality: capPoll only reads the response's `tokens` field to grow the corpus textbox; the `analysis` field the backend computes on the same round trip is stored in `capSnapshot` but never read by any render path (grepped app.jsx for `capSnapshot.analysis`: 0 hits) -- so the user sees no live-updating verdict during a capture, only after manually clicking ANALYZE NOW once it's done. Also worth noting: this poll-and-discard pattern is a full O(N) recompute already running every poll, which the original 'why' assumed would need a design change; that assumption is now stale. State holds at absent as experienced by the user; wiring `capSnapshot.analysis` into the results panel would close this with no backend change."},{"a":"sequencer","f":"Copy tokens / Save tokens to file from a capture","s":"present","i":"low","e":"hours","g":"None -- Live Capture's harvested tokens are folded straight into SequencerTab's shared token corpus (the same `text` state Manual Load/Send-to-Sequencer already populate) as they arrive, so the existing COPY TOKENS (clipboard) and SAVE TOKENS (.txt download) buttons cover a capture's output too, with no separate capture-specific export path needed.","w":"Closed 2026-08-23: the 2026-08-18 wave (da90e67) closed the Manual Load half and named Live Capture's absent request-issuing engine as the reason the other half stayed partial ('blocked on a request-issuing engine Nullock doesn't have'). That engine shipped 2026-08-17 (f910a9e); this wave's Live Capture UI reuses the exact same `text` state for harvested tokens, so Copy/Save now cover both halves for free.","v":"ui-v2/app.jsx SequencerTab: copyTokens()/saveTokens() functions + COPY TOKENS/SAVE TOKENS buttons in the manual-load control row (unchanged, shipped 2026-08-18); the new Live Capture panel's capPoll folds harvested tokens into the same setText()-backed corpus those buttons already read from -- no separate export path was needed.","o":"present","r":"Sequencer Live Capture UI wave: harvested tokens append into the same SequencerTab `text` state the existing COPY TOKENS/SAVE TOKENS buttons already act on, closing this item's Live Capture half as a free side effect."},{"a":"sequencer","f":"Reliability rating of the estimate (how much the result can be trusted given sample size)","s":"present","i":"medium","e":"days","g":"None. The analysis reports a reliability rating (insufficient/low/medium/high/very-high) derived from the token sample size.","w":"Closed 2026-08-10 (da103c8): reliabilityRating added + surfaced as result['reliability'].","v":"Src/Core/Networking/sequencer_logic.cpp reliabilityRating (sequencer.hpp), set as result['reliability'] in analyzeTokens; 5 threshold-band tests in Tests/sequencer.","o":"absent","r":"Sample-size reliability rating implemented + tested."},{"a":"sequencer","f":"Significance level selector (0.1% / 1% / 5% etc.) that re-grades every test and the entropy estimate","s":"partial","i":"medium","e":"days","g":"The UI dropdown is now in: a significance <select> (0.1/1/5/10%) sits next to Sequencer's ANALYZE NOW button, threads significanceLevel into POST /api/sequencer/analyze, and the Bit-level tests section header echoes the server-clamped alpha it actually graded at. Still partial: the keyspace ENTROPY estimate (shannon bits, good/ok/low verdict) is a point estimate, not an alpha-graded hypothesis test, so it is not re-graded by the selector and never will be without a shape change to that estimate -- Burp's own feature covers both, so this stays short of it.","w":"Implemented + mutation-proven. Each bit test's hard-coded p<0.01 critical was replaced by a pValue<alpha comparison computed from the existing statistic (chiSquareSurvival for chi tests; two-sided normal erfc for the z/correlation tests), so alpha=0.01 reproduces the historical criticals EXACTLY (the serial effect-floor provably implies p<0.01 for all m>=20; gauntlet stayed 100/100 + 156/156). alpha is clamped to [1e-6,0.2] and echoed as result.significanceLevel. 2026-08-25: the previously backend-only selector got a GUI control.","v":"sequencer.hpp analyzeTokens(tokens, alpha=0.01) + Sequencer::analyze(tokens, sig=0.01); sequencer_logic.cpp bitLevelTests(tokens, alpha) grades monobit/twoBit/serial/poker/runs/longRun/runLengths + perBit/bitCorr (Bonferroni alpha/N) by pValue<alpha and exposes each pValue; control_server.cpp:/api/sequencer/analyze reads significanceLevel. Tests/sequencer/sequencer_test.cpp (120 pass): pivot-straddle proves monobit.failed flips as alpha crosses its own p-value; echo+clamp+monotonicity+behaviour-preservation; M1 (monobit ignores alpha) and M2 (force alpha=0.01) each fail only their targeted cases. Live e2e: POST significanceLevel=0.179->fail, 0.0448->pass for the same corpus. ui-v2/app.jsx SequencerTab: sigLevel useState + <select> (0.001/0.01/0.05/0.1) wired through NL.actions.sequencerAnalyze(tokens, sigLevel); ui-v2/real-data.js sequencerAnalyze(tokens, significanceLevel) includes it in the POST body only when set.","o":"","r":"Sequencer wave: significance-level <select> next to ANALYZE NOW, wired to the already-complete backend alpha grading; entropy re-grading remains the documented, permanent shortfall vs. Burp."},{"a":"sequencer","f":"Character-level test: Character transition analysis (is the character at position i in token k independent of the character at position i in token k-1)","s":"present","i":"medium","e":"days","g":"None. Per-position character-transition independence is measured as Cramer's V of the consecutive-token contingency table and flagged when any position is strongly associated -- catching per-position serial correlation that per-position entropy is blind to.","w":"Closed 2026-08-10 (80e3672): maxPositionalTransitionV added + surfaced as result['transition']; mutation-proven.","v":"Src/Core/Networking/sequencer_logic.cpp maxPositionalTransitionV (sequencer.hpp), set as result['transition'] in analyzeTokens; Tests/sequencer +1-shift + sentinel cases.","o":"absent","r":"Per-position character-transition (Cramer's V) test implemented + tested."},{"a":"sequencer","f":"Bit-level test: FIPS poker test (non-overlapping 4-bit groups, chi-square over 16 buckets)","s":"present","i":"medium","e":"hours","g":"None. FIPS poker chi-square (15 dof) over non-overlapping 4-bit groups is computed on the decoded bit stream and surfaced in the analysis.","w":"Closed 2026-08-10: fipsPokerChiSquare added + wired into bitLevelTests.","v":"Src/Core/Networking/sequencer_logic.cpp fips{Poker,Runs}/longestBitRun helpers (declared in sequencer.hpp), folded into bitLevelTests + the analysis JSON (bitLevel.poker/.runs/.longRun); mutation-proven in Tests/sequencer (stubbing the helpers fails exactly the 6 discriminating cases). Commit dd9c158.","o":"absent","r":"FIPS poker test implemented + tested."},{"a":"sequencer","f":"Bit-level test: FIPS runs test (counts of runs of length 1..6+ of identical bits, against expected ranges)","s":"present","i":"medium","e":"hours","g":"None. Both a total-runs z-test AND the FIPS length-bucketed form (chi-square over run lengths 1..6+ vs the geometric expectation) are computed and flagged.","w":"Closed 2026-08-10 (045f671): fipsRunsBucketChi adds the length-bucketed variant the total-runs z-test lacked.","v":"Src/Core/Networking/sequencer_logic.cpp fipsRunsBucketChi + compressionRatio (sequencer.hpp), in bitLevelTests + JSON (bitLevel.runLengths/.compression); mutation-proven in Tests/sequencer. Commit 045f671.","o":"partial","r":"FIPS length-bucketed runs test added."},{"a":"sequencer","f":"Bit-level test: FIPS long runs test (flag any run of identical bits exceeding the threshold)","s":"present","i":"low","e":"hours","g":"None. Longest identical-bit run is computed and flagged when a run that long is <1% likely for the sample size (a size-scaled generalisation of FIPS' fixed-26 rule).","w":"Closed 2026-08-10: longestBitRun added + wired into bitLevelTests.","v":"Src/Core/Networking/sequencer_logic.cpp fips{Poker,Runs}/longestBitRun helpers (declared in sequencer.hpp), folded into bitLevelTests + the analysis JSON (bitLevel.poker/.runs/.longRun); mutation-proven in Tests/sequencer (stubbing the helpers fails exactly the 6 discriminating cases). Commit dd9c158.","o":"absent","r":"FIPS long-runs test implemented + tested."},{"a":"sequencer","f":"Bit-level test: Spectral test (treat consecutive values as coordinates in n-dimensional space, look for lattice clustering)","s":"absent","i":"medium","e":"weeks","g":"Absent as such. Lag-1 Pearson correlation detects only 1-dimensional linear dependence; the spectral test is what exposes LCG lattice structure in 2..8 dimensions, and nothing here detects a Mersenne Twister stream at all.","w":"Confirmed: 0 hits for \"spectral\". The source itself concedes both the substitute and the resulting blind spot — I verified both comments verbatim.","v":"sequencer_logic.cpp:322-324: `//   * byte-level lag-1 serial correlation       -> the LCG/linear-congruential //                                                  lattice (and java.util.Random //                                                  low-bit) signature`. Admission at sequencer.hpp:26-28 (unchanged): `// so small or genuinely-random captures are never false-flagged. (A Mersenne // Twister stream passes 6-8; flagging MT needs a matrix-rank / state-recovery // test, left as future work.)`. `grep -rc spectral Src/`: 0 hits repo-wide, including the new sequencer_capture*.{cpp,hpp}.","o":"","r":"Wave 0 register-accuracy audit: held at absent. The lag-1 serial-correlation comment drifted 206-208 -> 322-324 (sequencer_logic.cpp grew with the confidence/dataAnalyzed summary work, item #71/147); the Mersenne Twister admission in sequencer.hpp did NOT drift, still exactly 26-28. Re-ran the 'spectral' grep repo-wide (including the two new sequencer_capture*.cpp/.hpp files, which do not add any bit-level test): 0 hits. Claim holds; one evidence line range refreshed."},{"a":"sequencer","f":"Bit-level test: Compression test (ZLIB-compress the bit sequence; compression ratio bounds the entropy)","s":"present","i":"medium","e":"hours","g":"None. The decoded byte stream is zlib-compressed and its compression ratio bounds are checked (structure/repetition compresses; random does not).","w":"Closed 2026-08-10 (045f671): compressionRatio (qCompress) added + flagged in bitLevelTests.","v":"Src/Core/Networking/sequencer_logic.cpp fipsRunsBucketChi + compressionRatio (sequencer.hpp), in bitLevelTests + JSON (bitLevel.runLengths/.compression); mutation-proven in Tests/sequencer. Commit 045f671.","o":"absent","r":"Compression test implemented + tested."},{"a":"sequencer","f":"Results drill-down: per-test result panels with charts (per-position bar charts, per-bit significance plots) and pass/fail per position","s":"partial","i":"medium","e":"weeks","g":"Raw JSON on stdout via the CLI is still the only access there, but the GUI (ui-v2/app.jsx) now renders a real per-position bar chart -- one bar per corpus column, height proportional to that column's Shannon entropy relative to the strongest column (`pos.reference`), colored red when a column is 'weak' (matches the same h < 0.5*reference threshold sequencer_logic.cpp uses to flag `biased`) and accent-colored otherwise, with a hover tooltip giving the exact bit value per column. Bit-level tests (monobit/two-bit/serial) are shown as labeled numeric stats with red/normal coloring on failure, not as a plot, and there is still no PER-BIT significance chart (only one summary number per test) and no per-position pass/fail beyond the coarse weak/not-weak bar coloring.","w":"UPGRADED absent->partial: this grade is stale. ui-v2/app.jsx's Sequencer results panel (renderResult, ~4524-4610) gained a 'Per-position entropy' Section (:4580-4598) since the last audit that maps `pos.columnEntropy` (the exact array sequencer_logic.cpp already emitted) into one CSS bar per column (:4589-4594), height = `(h / pos.reference) * 100%`, colored `var(--err)` when `h < 0.5 * (pos.reference || 1)` -- a direct visual mirror of sequencer_logic.cpp's own `weak` threshold (:421-423 `h < 0.5 * ref && (ref - h) >= 1.0`). This is a genuine per-position bar chart with a visible pass/fail-like signal per column, which the prior evidence's 'grep -a columnEntropy ui-v2/: 0 hits' claim said did not exist. The bit-level tests panel (:4599-4608) similarly renders monobit p-value / two-bit chi-square / serial r as labeled, color-graded stats -- a 'per-test result panel', though not a plot and not per-bit. Held at partial: no per-bit significance PLOT (only one aggregate number per test), and pass/fail is still not computed or shown per INDIVIDUAL statistical test at each position (only the coarse weak-column threshold).","v":"sequencer_logic.cpp:409 `r.columnEntropy << H;` and :1117-1118 `for (double h : pos.columnEntropy) cols.append(h); posObj[\"columnEntropy\"] = cols;`; weak-column threshold at :421-423. ui-v2/app.jsx:4580-4598 renders it: `{(pos.columnEntropy || []).map((h, i) => (<div ... title={\"col \" + i + \": \" + h.toFixed(2) + \" bits\"} ...><div style={{ ..., height: Math.min(100, (h / (pos.reference || 1)) * 100) + \"%\", background: h < 0.5 * (pos.reference || 1) ? \"var(--err)\" : \"var(--accent)\" }} /><\/div>))}`. Bit-level stats panel at app.jsx:4599-4608. CLI raw-JSON path unchanged: bin/nullock:724 `post /api/sequencer/analyze \"{\\\"tokens\\\":$tokens}\" | pp`.","o":"","r":"Wave 0 register-accuracy audit: UPGRADED absent -> partial. columnEntropy was always emitted by the backend (sequencer_logic.cpp, drift 550-552 -> 1117-1118 from the confidence/dataAnalyzed work) but the original evidence's 'grep -a columnEntropy ui-v2/: 0 hits' is now false -- ui-v2/app.jsx:4580-4598 added a real per-position bar-chart Section since the last audit, rendering one bar per column colored by the same weak-column threshold the backend computes (h < 0.5*reference), plus a labeled bit-level-tests stats panel (:4599-4608, monobit p / two-bit chi-square / serial r, color-graded on failure). This is a genuine 'results drill-down with charts' as the feature title describes, closing the 'no visualisation anywhere' half of the gap. Remaining and real: no per-bit significance PLOT (bit-level tests show one aggregate number each, not a per-bit chart), and no true per-position PASS/FAIL for each individual statistical test (only the coarse per-column weak/not-weak bar coloring). Downgrade risk considered and rejected: this is core-product GUI code (ui-v2/app.jsx), not a stub or dead branch -- verified the Section is inside the always-rendered renderResult() function, gated only on `pos.applicable`."},{"a":"sequencer","f":"Sequencer analysis report export (HTML / XML report of the token analysis)","s":"partial","i":"medium","e":"days","g":"Client-only export -- the HTML/XML file is generated in the browser from the current analysis and downloaded; it does not enter the report/build pipeline (no cmd_report sequencer branch) and never reaches the findings store, so a weak-token result still cannot be tracked alongside scan findings or against a baseline.","w":"Closed the export half 2026-08-19: SequencerTab (ui-v2/app.jsx) gains EXPORT HTML / EXPORT XML buttons next to the existing SAVE TOKENS button. Two new pure functions, sequencerReportHtml()/sequencerReportXml(), render the exact same fields the on-screen result Sections already show (verdict/score/n/distinctTokens/avgLen, Shannon entropy, character-class ratios, Hamming distance, longest-common-substring, sequential/counter detection, per-position entropy, bit-level tests) into a standalone downloadable file -- no backend change, no new endpoint, the report can never drift from what the operator already sees. Token-derived text (the LCS substring) is HTML/XML-escaped before insertion since it originates in the untrusted analyzed corpus. Stays partial, not present: this is a client deliverable only, not integrated into cmd_report or the findings/baseline store -- the remaining architectural gap this file already named is honestly unchanged.","v":"ui-v2/app.jsx sequencerReportHtml()/sequencerReportXml() (pure, no DOM/I-O) + sequencerReportEscape(); SequencerTab.exportReport(format) builds a Blob and triggers a download, same pattern as the existing saveTokens()/CSRF-PoC download helpers; field set matches renderResult()'s own Section blocks 1:1 so the export cannot show something the screen doesn't.","o":"partial","r":"Sequencer report-export batch -- absent -> partial (client-only export, not wired into cmd_report/findings)"},{"a":"sequencer","f":"Sample-size guidance and FIPS conformance threshold (warn under ~100 tokens, note 20,000 for formal FIPS compliance, cap the sample)","s":"present","i":"medium","e":"hours","g":"No minimum-sample warning, no FIPS-conformance statement (20,000 bits / 20,000 tokens is never mentioned), and no explicit cap. The effective cap is the generic 64 MB body limit — ~1.5M tokens — analysed synchronously on the control-server request thread with a 64 MB `combined` QString built at :449-451, so a large corpus stalls the API rather than being rejected.","w":"Confirmed absent. I also checked the upper-bound concern the first pass raised and can now bound it: the control server caps request bodies at 64 MB, so the corpus is bounded, but the analysis is synchronous on the request path.","v":"control_server.cpp:135 `constexpr qint64 kMaxBodyBytes  = 64LL * 1024 * 1024;` enforced at :1040 `if (!ok || contentLength < 0 || contentLength > kMaxBodyBytes) {`. The sequencer route is NOT in the async/offload set (kActivePaths at :2944-2959 does not list it), so `seq.analyze(tokens)` runs inline. No warning field is ever emitted: analyzeTokens returns early only for the empty case (:436-440 `r","o":"present","r":"Closed 2026-08-11: analyzeTokens now emits a sampleGuidance block via the pure, mutation-tested Core::sampleSizeGuidance -- a warning under the recommended ~100-token minimum (plus a harder not-estimable floor below kDeepMinN) and whether the decoded stream reaches the 20,000-bit FIPS 140-2 sample size. Scope: the sample-size guidance + FIPS conformance threshold are delivered and tested; an explicit user-tunable sample cap / async offload is NOT added here -- the corpus is already bounded by the 64 MB body cap, and the synchronous-analysis concern stays tracked separately."},{"a":"sequencer","f":"Rule scope — Tools scope (apply this rule to Proxy / Scanner / Intruder / Repeater / Sequencer / Extender, checkbox per tool)","s":"partial","i":"blocker","e":"days","g":"Configurable AND enforced for proxy, Repeater and Intruder, with a per-tool editor UI (Proxy/Repeater/Intruder/Scanner checkboxes in the SESSIONS tab rule editor, plus a tools-scope summary per rule row). Remaining: the Scanner checkbox is offered/stored but not enforced anywhere (no scanner call site passes ToolScanner to applyToRequest), and the chain-runner / sequencer / extender scopes are entirely unbuilt (no UI, no enforcement).","w":"Confirmed and STRENGTHENED. I verified the Repeater/Intruder bypass by grepping those two files for \"session\" (0 hits, so it is not a naming difference) and reading their send paths. I also found a third bypass and an additional silent gate the first pass missed.","v":"SessionRule (session_rules.hpp:40-71, read in full) has no tool field. Both hooks live inside one function: proxy_server.cpp:1484 `if (m_sessionManager) m_sessionManager->injectInto(req);` and :1490 `if (m_sessionRules) m_sessionRules->applyToRequest(req);`, guarded upstream at :1447 `if (!isInScope(req.host)) return;`. Bypasses: repeater.cpp:133-136 `const auto result = m_client.send(t.host, stat","o":"partial","r":"Adds the per-tool editor checkboxes flagged as the ui-v2 remainder above: SessionsTab's rule editor (ui-v2/app.jsx) gets a Tools scope row -- Proxy/Repeater/Intruder/Scanner checkboxes bound to the rule's `tools` bitmask via a pure sessionRuleToggleToolBit(mask, bit) helper mirroring SessionRulesLogic::SessionTool exactly (1/2/4/8), plus a sessionRuleToolsLabel(mask) summary (\"all tools\" when unset, else a comma list) shown in the rule list's new tools column. No backend change -- `tools` already round-trips through /api/session-rules (control_server.cpp:1618, :3980). Honest remainder, confirmed by grep: the Scanner bit is offered and stored but NOT enforced -- no call site anywhere passes SessionRulesLogic::ToolScanner to applyToRequest/applyToRequestBytes (only ToolIntruder in intruder.cpp:498/628 and ToolRepeater in repeater.cpp:158 exist; proxy_server.cpp:1539 calls the default-tool overload); the chain-runner/sequencer/extender scopes also remain entirely unbuilt, both as UI and as enforcement. State stays partial -- this closes only the ui-v2 half of the previously-named gap."},{"a":"sequencer","f":"Rule scope — Parameter scope (apply only when named parameters are present)","s":"absent","i":"low","e":"days","g":"Absent, and the matcher deliberately strips the query, so adding parameter scope requires changing what is passed in, not just adding a field.","w":"Confirmed by reading the struct and the matcher in full.","v":"session_rules.hpp:44-86 (struct SessionRule) has no parameter field. session_rules.cpp:151-174 `SessionRules::matches` ends (:171-173) `return resolve(r.hostGlob).match(host).hasMatch() && resolve(r.pathGlob).match(stripQuery(path)).hasMatch() && SessionRulesLogic::urlScopeMatches(...);` -- and stripQuery (session_rules_logic.cpp:130-133) actively DISCARDS the query string before matching, so parameters are still not even visible to the matcher (the newer includeUrls/excludeUrls scope, item #70/156, also matches against `host + stripQuery(path)` only -- session_rules_logic.cpp:169).","o":"","r":"Wave 0 register-accuracy audit: held at absent. Struct span drifted 40-71 -> 44-86 (grew with includeUrls/excludeUrls/tools fields, still no parameter field). matches() drifted 46-67 -> 151-174; its closing return grew a THIRD clause (the new URL-scope check) but that clause also operates on host+stripQuery(path), so it does not expose parameters either. stripQuery drifted 123-126 -> 130-133, content unchanged, still strips the query before any matching happens. Claim holds; evidence refreshed to reflect the struct/function's real current shape, not just re-lined."},{"a":"sequencer","f":"Rule action: \"Run a macro\" (execute a recorded request sequence, optionally before every in-scope request)","s":"partial","i":"blocker","e":"days","g":"The manual bridge is real (record -> chain/run with sessionHost -> session bag -> auto-injected into later requests), and now a NAMED macro store exists with an on-demand run (/api/session-macros + /api/session-macros/run -> SessionRules::runMacro) plus an automatic re-run when the session goes invalid (see #190, now built). What's still missing is the scheduled variant of the rule action: no way to configure a session rule to run a macro automatically BEFORE every in-scope request (only after a logged-out response is detected).","w":"Re-verified after a11754e (2026-08-16): control_server.cpp:9233 reads `bodyJson.value(\"sessionHost\")` and calls `m_wiring.sessionRules->ingestVariables(sessionHost, r.vars)` when set -- a plain chain run (no sessionHost) is unchanged, so this is opt-in exactly as the commit describes. session_rules.cpp:284 `ingestVariables` merges host-keyed vars under the existing mutex and emits variablesChanged, the same signal the UI already listens to. I confirmed there is still no rule-action enum, no scheduler, and no logged-out detector anywhere in Src/Core/Networking/session_rules*.cpp or chain_runner*.cpp -- grep for reauth/sessionInvalid/loggedOut/relogin/checkSession/ruleAction still returns 0 hits.","v":"control_server.cpp:9233-9237 `const QString sessionHost = bodyJson.value(\"sessionHost\").toString(); if (!sessionHost.isEmpty() && m_wiring.sessionRules) m_wiring.sessionRules->ingestVariables(sessionHost, r.vars);`; session_rules.cpp:284-293 `void SessionRules::ingestVariables(...) { ... QHash<QString,QString> &bag = m_varsByHost[host]; for (...) bag.insert(it.key(), it.value()); } emit variablesChanged();`; session_rules.hpp:60-65 still only the four-member InjectInto enum -- no rule-action concept.","o":"partial","r":"Closed in two steps. (1) a11754e: POST /api/chain/run gains an opt-in `sessionHost` (control_server.cpp:9233-9237) -- after the macro runs, SessionRules::ingestVariables(host, vars) merges its extracted vars into that host's session-rule bag, so a token a recorded login macro captures is injected into later requests by the matching rules (record-a-macro -> stay-authenticated, manually). (2) 5012a6f: a named-macro store + on-demand run + automatic re-run. SessionMacro {name, sessionHost, ChainRunner steps, loggedOut condition} is settable via /api/session-macros and runnable by name via /api/session-macros/run -> SessionRules::runMacro, which replays the recorded login sequence and ingests its vars. And the automatic half that this item's evidence called 'fully absent' now exists: item #190's re-auth trigger is built, so a macro re-runs by itself when a response to its host matches the logged-out condition. STILL PARTIAL: no scheduled variant -- you cannot yet say 'before each request to /api/*, run the login chain automatically'; the automatic run fires on session-invalid detection, not on a pre-request schedule. Macros now also PERSIST across restart (d728ea4): the shared sessionMacrosToJson/sessionMacrosFromJson serializer writes them into project.json under `sessionMacros` (persist-at-the-API-call-site, restored via ProjectStore::sessionMacrosChanged on open) -- verified e2e (set -> kill -> relaunch -> restored with every field intact). A visual macro editor is the remaining UI follow-on. NB the cookie jar + the session RULES themselves still don't persist (that is parity #2494, unchanged -- macro persistence is orthogonal to it)."},{"a":"sequencer","f":"Rule action: \"Check session is valid\" (issue a validation request, match a keyword/status/redirect, and conditionally run the re-auth macro)","s":"partial","i":"blocker","e":"weeks","g":"No session-validity detection and no automatic re-authentication. A long Intruder run or audit scan that logs out midway produces a page of meaningless 302s with no warning — and given the Repeater/Intruder bypass above, those tools were never carrying the session anyway.","w":"Confirmed. I read applyToRequest and applyToResponse in full: both are pure string manipulation with no network I/O and no conditional branch on response content.","v":"session_rules.cpp:133-237 `SessionRules::applyToRequest` performs only template substitution into four targets and never constructs a request; :74-131 `applyToResponse` only harvests values into `m_varsByHost`. Neither includes networking.hpp. Greps for reauth / sessionInvalid / loggedOut / relogin / checkSession across Src/: 0 hits.","o":"absent","r":"Built: the session-validity check + conditional re-auth now exist. SessionRulesLogic::responseIsLoggedOut(status, bodyText, statusList, bodyRegex) (session_rules_logic.cpp:133-147) is a pure, unit-tested + mutation-proven predicate -- a comma status list (e.g. \"401,403\") and/or a response-body regex; BOTH empty = never (a macro with no condition never auto-re-auths); status 0 (no response) never matches; an invalid regex fails closed. A SessionMacro (session_rules.hpp:86-95) carries loggedOutStatus/loggedOutBodyRegex; SessionRules::maybeReauth, called from applyToResponse, matches every live response to the macro's sessionHost against it and on a hit re-runs the macro ASYNC (QtConcurrent::run -- never blocks the proxy worker on login I/O) to re-acquire the session, then ingests the fresh vars into the host bag. Loop-guarded: an in-flight QSet + a 5s per-host cooldown, and the macro's own requests use ChainRunner's client (not the proxy) so a permanently-failing login can't hammer the target or re-trigger itself. PARTIAL, honestly: this detects a logged-out session PASSIVELY on the live response stream rather than issuing Burp's dedicated active 'validation request' to a known URL, and there is still no in-browser recovery prompt; but the core -- match status/keyword and conditionally run the re-auth macro -- is real. Closes launch blocker #11 (\"no check-session-is-valid\")."},{"a":"sequencer","f":"Rule action: \"Prompt for in-browser session recovery\" (pause and let the user re-login in the browser)","s":"absent","i":"medium","e":"weeks","g":"Absent. The pause-and-resume primitive exists in the proxy intercept path and could be borrowed, but nothing in session handling can trigger it.","w":"Confirmed. Both session TUs read in full — non-blocking, non-interactive, no pause primitive. Note there IS an interactive pause mechanism in the codebase (InterceptController, app.cpp:770) but it is not reachable from the session path.","v":"session_rules.cpp and session_manager.cpp (both re-read in full: now 488 and 288 lines, up from 239/193) contain no wait, no signal-and-block, no user prompt -- including the new SessionMacro/maybeReauth code (session_rules.cpp:453-486), which is itself async (QtConcurrent::run) and non-interactive. The nearest analogue is Src/App/app.cpp:931-932 `Nullock::Proxy::InterceptController intercept; proxy.setInterceptController(&intercept);` -- the request-intercept pause, which no session code references.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Both files grew substantially since the last audit (session_rules.cpp 239->488 lines, session_manager.cpp 193->288 lines) with the SessionMacro/auto-reauth feature (relevant to items #72/159 and #85/200), so re-read both in full rather than trusting the old line counts. The new maybeReauth path is itself fire-and-forget async (QtConcurrent::run, session_rules.cpp:481) with no pause, no signal-and-block, no prompt -- it re-runs a macro unattended or does nothing, never asking a human to intervene. InterceptController wiring drifted app.cpp:770-771 -> 931-932, still unreferenced by any session code. Claim holds; evidence refreshed."},{"a":"sequencer","f":"Rule action: \"Invoke a Burp extension\" (extension-registered session handling action, ISessionHandlingAction)","s":"absent","i":"medium","e":"days","g":"An extension can rewrite every request, but cannot register a named session-handling action that a rule invokes at a chosen point in an ordered action list — because rules have no action list.","w":"Confirmed. The extension surface is a blanket per-request mutation hook, not a registerable named action — verified against the API header.","v":"extensions_api.hpp:306 `Q_INVOKABLE void onResponse(const QJSValue &callback);` and :311 `Q_INVOKABLE void onRequest(const QJSValue &callback);`, consumed via `applyRequestMutation` (declared :147). No registration API for a named, invocable session-handling action; SessionRule (session_rules.hpp:44-86) still has no action-name field to reference one.","o":"","r":"Wave 0 register-accuracy audit: held at absent. onResponse/onRequest drifted 167/172 -> 306/311, applyRequestMutation drifted :87 -> :147 (extensions_api.hpp grew substantially -- other extension-API work landed, unrelated to session handling). Re-grepped for registerAction/sessionAction/ISessionHandling/registerSessionHandling repo-wide: 0 hits. SessionRule's field list (session_rules.hpp:44-86) still has no action-name/action-id field. Claim holds; evidence refreshed."},{"a":"sequencer","f":"Macros: record a macro by selecting requests from Proxy history, with a macro editor and \"Test macro\"","s":"present","i":"blocker","e":"weeks","g":"None -- recording (POST /api/chain/record), a visual macro editor (SESSIONS tab's Login macros section: name/session host/logged-out condition fields, Record from history, save/edit/delete/run), and \"Test macro\" (POST /api/chain/run) are all done, and the last remaining piece -- a full, untruncated response viewer -- is now closed too: StepResult.responsePreview (chain_runner.cpp) is no longer capped at 2 KiB, and the SCANS tab's Request chain section renders a collapsible per-step viewer (name/status/timing/extracted vars, full response body on expand) instead of the prior raw-JSON-only dump.","w":"Closed 2026-08-27 (d929886): chain_runner.cpp:85 changed `sr.responsePreview = res.rawResponse.left(2 * 1024)` to `sr.responsePreview = res.rawResponse` (full, untruncated) and the .hpp comment updated to match. ui-v2/app.jsx's Request chain section (SCANS tab) gained a per-step list -- each row shows name/HTTP status or error/ms/response size/extracted-var names, click to expand a <pre> with the complete response body -- reusing the same chainRes state the section already populated via NL.actions.chainRun. This is the exact gap the 2026-08-26 reconcile (4300b81) left open after closing recording and the visual macro editor, so state moves partial -> present. Verified cross-platform: GitHub Actions run 33036681345 (this cloud session cannot build/run Qt locally) shows the Windows and Linux NullockApp builds both green against this exact diff, plus the macOS build, CLI-syntax, labs-syntax, fuzz-corpus, marketplace-schema and Docker-image jobs -- 8/8 jobs completed=success before this state flip.","v":"Src/Core/Networking/chain_runner.cpp:85 `sr.responsePreview = res.rawResponse;` (was `.left(2 * 1024)`); chain_runner.hpp:52 `QByteArray responsePreview; // full raw response, untruncated`. ui-v2/app.jsx: chainOpenStep state, the Request chain Section's `chainRes.steps.map(...)` block rendering a clickable name/status/ms/size/extracted-vars header per step with an expandable <pre>{st.responsePreview}<\/pre>. control_server.cpp:10132 unchanged -- `{ \"responsePreview\", QString::fromUtf8(sr.responsePreview) }` already carried whatever the struct held, so no backend wire-format change was needed beyond chain_runner.cpp itself.","o":"present","r":"Closed the last open gap on this item: removed the 2 KiB StepResult.responsePreview cap (chain_runner.cpp) and added a collapsible per-step response viewer to the SCANS tab's Request chain section (ui-v2/app.jsx) -- name/status/timing/extracted vars in a clickable header, full untruncated response body on expand. Recording, the visual macro editor, and Test macro were already closed by the 2026-08-26 waves (b36c77d, 4300b81); this closes the one piece those reconciles explicitly left open. state: partial -> present. Verified via GitHub Actions run 33036681345 (8/8 jobs green, including both the Windows and Linux NullockApp builds) since this cloud session cannot build Qt/C++ locally."},{"a":"sequencer","f":"Cookie jar honors cookie domain scope (Domain attribute, host-only vs domain cookies, subdomain matching)","s":"partial","i":"high","e":"days","g":"`Set-Cookie: SESSION=...; Domain=.example.com` from www.example.com is never sent to api.example.com. The workaround is the manual copyTo button (session_manager.cpp:177), which the analyst must remember and which copies EVERY cookie for the host — over-sharing in the other direction, including cookies that were host-only by design.","w":"Confirmed by reading the attribute parser in full — `domain` is genuinely not one of the five handled keys, and I confirmed storage is exact-host.","v":"session_manager_logic.cpp:67-71 verbatim, the complete attribute switch: `if      (key == \"path\")     c.path     = val; else if (key == \"expires\")  c.expires  = val; else if (key == \"httponly\") c.httpOnly = true; else if (key == \"secure\")   c.secure   = true; else if (key == \"samesite\") c.sameSite = val;` — no domain arm; the attribute is parsed and then dropped on the floor. Storage: session_mana","o":"partial","r":"absent -> partial 2026-08-12: the gap's core deficiency ('domain is parsed and then dropped on the floor') is fixed -- parseSetCookie now records the Domain attribute into CapturedCookie.domain (lowercased, a single leading '.' stripped, empty => host-only) and a pure RFC 6265 5.1.3 domainMatches(cookieDomain, reqHost) predicate is implemented with a real label boundary (evil-example.com does NOT match example.com) + IP-literal exact-only handling, unit- + mutation-tested (dropping the '.' boundary fails the label-trick case). NOT yet a full close: injectInto still does an exact-host lookup -- wiring domain-aware, DETERMINISTIC (m_byHost is a QHash) multi-host cookie collection plus the RFC 6265 5.3 Domain-vs-origin-host validation into injection is the remaining architectural step."},{"a":"sequencer","f":"Cookie jar expiry handling (Expires / Max-Age respected; expired cookies dropped, session cookies distinguished)","s":"present","i":"medium","e":"hours","g":"None -- Max-Age + Expires are parsed to an absolute expiry (cookieExpired predicate), ENFORCED at capture (an already-expired Set-Cookie deletes the stored cookie) and at inject (expired cookies are skipped), with session-vs-persistent surfaced to the UI. Historical note: a logout via `Set-Cookie: SESSION=; Expires=Thu, 01 Jan 1970...` happens to work because the name-keyed merge (session_manager.cpp:72-80) overwrites the value with empty — but `Max-Age=0` is not understood as a deletion, and session-vs-persistent cookies are indistinguishable in both the store and the UI.","w":"Confirmed as stub — the field is captured and surfaced but never consulted. I traced the full inject predicate set: exactly two filters, neither temporal.","v":"Captured as an opaque string, session_manager_logic.cpp:68 `else if (key == \"expires\")  c.expires  = val;` — never parsed to a QDateTime. Surfaced at control_server.cpp:4849 `co[\"expires\"] = c.expires;`. The complete inject filter set is session_manager.cpp:131-132: `if (!SessionLogic::injectableOverTransport(c, req.port)) continue; if (!SessionLogic::pathMatches(c.path, req.path)) continue;`. `gr","o":"present","r":"Cookie-jar expiry DONE. Pure foundation (39f6cf5, mutation-proven): Max-Age + Expires -> absolute expiry (RFC 6265 5.3, Max-Age wins), cookieExpired predicate, session-vs-persistent. Enforced (2a7729d): resolve on capture, delete an already-expired Set-Cookie (logout), skip expired cookies on inject, surface persistent/expiresEpoch to the UI. Pure logic unit-tested; QObject inject/capture wiring gauntlet-verified (not unit-testable, cf. #194)."},{"a":"sequencer","f":"Cookie jar and session rules persist in the project file / user settings across restarts","s":"present","i":"high","e":"days","g":"Cookie jars and session rules persist per project. Cookie changes autosave every two seconds and after shutdown workers drain; session-rule edits save when applied. Failed workspace writes remain visible and block project switching. Transient extracted session variables are intentionally cleared when changing projects.","w":"Cookie jars and session rules persist per project. Cookie changes autosave every two seconds and after shutdown workers drain; session-rule edits save when applied. Failed workspace writes remain visible and block project switching. Transient extracted session variables are intentionally cleared when changing projects.","v":"Src/App/app.cpp saveWorkspaces; Src/Core/Storage/project_store.cpp saveSessionWorkspace; scripts/workspace_recovery_regression.py","o":"absent","r":"Cookie jars and session rules persist per project. Cookie changes autosave every two seconds and after shutdown workers drain; session-rule edits save when applied. Failed workspace writes remain visible and block project switching. Transient extracted session variables are intentionally cleared when changing projects."},{"a":"sequencer","f":"Session handling tracer (step-by-step log of which rules fired, which actions ran, and the request state after each)","s":"absent","i":"high","e":"days","g":"When an injection does not happen there are now at least seven distinct silent exits and no way to tell which one fired. Given the Repeater/Intruder/chain bypass and the port-443 Secure heuristic, this is the debugging tool the current design most needs — it would surface four of the defects in this report as observable behaviour rather than mystery.","w":"Confirmed: 0 hits for tracer, and the only introspection is the flattened variable bag. This assessment gets MORE important given what I found: I identified four additional silent-failure paths in this area (scope early-return, verbatim {{var}} injection, Secure-cookie port heuristic, chain-runner bypass), none of which produce any diagnostic.","v":"Signals: session_rules.hpp:166-170 `signals: void rulesChanged(); void variablesChanged(); void macrosChanged(); ... void sessionReauthed(const QString &host, const QString &macro);` -- two more signals than before (macrosChanged, sessionReauthed), still none of them fire-grained per-rule/per-action. Sole introspection: session_rules.cpp:133-141 `variables()`, `// Flattened view for the UI/debug (later hosts win on a name collision).`. Silent, unlogged early exits: applyToResponse (session_rules.cpp:193 rs.isEmpty() return, :197 !enabled continue, :198 !matches continue, :199 empty key/var continue), applyToRequest (:259 rs.isEmpty() return, :263-266 four more continues), ingestVariables (:414 host/vars empty return), and three NEW ones in the SessionMacro re-auth path: runMacro (:442 macro-not-found/no-steps return), maybeReauth (:467 already-in-flight return, :469 cooldown return) -- none of these seven-plus branches produce any diagnostic output.","o":"","r":"Wave 0 register-accuracy audit: held at absent -- and, per the original 'why''s own framing, this gets MORE relevant, not less. Re-enumerated the silent-return sites in the now-nearly-doubled session_rules.cpp (239->488 lines): the SessionMacro/auto-reauth feature (items #72/159, #85/200) added THREE new unlogged early-exit branches (macro not found, already re-authing, cooldown) on top of the original set, and two new signals (macrosChanged, sessionReauthed) that are still coarse rulesChanged-style notifications, not a fired-rule trace. Grepped repo-wide for 'tracer'/'Tracer': 0 hits, confirming no such feature exists anywhere, not just in this subsystem. Claim holds; evidence substantially refreshed (old line citations no longer matched current code shape after the SessionMacro addition, not just shifted)."},{"a":"sequencer","f":"Platform authentication: per-host credentials for HTTP Basic, Digest, NTLMv1/v2 and Negotiate, applied automatically on 401","s":"absent","i":"high","e":"days","g":"Testing an intranet app behind NTLM or Negotiate is impossible — every request 401s. Basic-auth targets require hand-adding an Authorization header separately in each tool, and because session rules do not reach Repeater or Intruder, even a session-rule workaround would not cover them.","w":"Confirmed. I re-ran the greps and checked the two NTLM hits and the 33 \"Negotiate\" hits myself — the NTLM hits are a hash-format label, and none of the Negotiate hits are HTTP auth. Zero hits for WWW-Authenticate anywhere in Src/.","v":"The only NTLM reference is transcode.cpp:363 `case 32:  out << QStringLiteral(\"MD5\") << QStringLiteral(\"NTLM\") << QStringLiteral(\"MD4\"); break;` and transcode.hpp:43 (`32 hex -> MD5 / NTLM`) -- a hash-format identifier, not auth. `grep -rn WWW-Authenticate Src/`: 0 hits. `grep -rn platformAuth|basicAuth|DigestAuth|Proxy-Authorization Src/`: 3 hits, all in proxy_server.cpp/proxy_logic.cpp/.hpp and all about STRIPPING the hop-by-hop `Proxy-Authorization` header before forwarding (MITM proxy-credential hygiene), unrelated to authenticating to the TARGET. No 401-challenge handler exists in the HTTP client path.","o":"","r":"Wave 0 register-accuracy audit: held at absent. NTLM hash-label citation drifted transcode.cpp:299 -> 363, transcode.hpp:37 -> 43 (content unchanged). Re-ran the Proxy-Authorization grep and, unlike the original which reported 0 hits, it now returns 3 -- checked all three by hand: proxy_logic.cpp:150 and proxy_server.cpp:1305 plus a proxy_logic.hpp comment, all about the MITM proxy stripping ITS OWN hop-by-hop Proxy-Authorization header before relaying upstream, which is proxy-credential hygiene, not a per-host Basic/Digest/NTLM/Negotiate challenge-response mechanism for the TARGET application. WWW-Authenticate still 0 hits repo-wide. Claim holds; evidence refreshed including the corrected (non-zero but irrelevant) grep count."},{"a":"sequencer","f":"Client-side TLS certificates: per-host PKCS#12 / keystore for mutual-TLS targets","s":"absent","i":"medium","e":"days","g":"Any target requiring mutual TLS is untestable — there is no per-host keystore, no PKCS#12 import, and no upstream QSslConfiguration to attach one to.","w":"Confirmed. I enumerated every QSslCertificate/setLocalCertificate site in Src/ — the only cert-presentation code is the MITM listener's own leaf, and every other site is inspection of the PEER's cert.","v":"Sole presentation site, proxy_server.cpp:452-460: `QSslCertificate cert(leaf.certPem, QSsl::Pem); QSslKey key(leaf.keyPem, QSsl::Rsa, QSsl::Pem); ... cfg.setLocalCertificate(cert); cfg.setPrivateKey(key);` -- the cert Nullock presents TO the browser (the MITM leaf), unchanged in content from the prior audit. Every other hit is peer-side inspection: tls_inspect.cpp:99 `const QSslCertificate cert = sock.peerCertificate();`, :187 `QSslCertificate::verify(sock.peerCertificateChain(), req.host);` (both unchanged line numbers). `grep -rn pkcs12|PKCS12 Src/`: 0 hits.","o":"","r":"Wave 0 register-accuracy audit: held at absent. The MITM leaf-presentation site drifted proxy_server.cpp:398-406 -> 452-460 (content identical); both tls_inspect.cpp peer-inspection citations (:99, :187) did NOT drift. Re-ran the pkcs12/PKCS12 grep repo-wide: still 0 hits. No per-host client-cert keystore, no QSslConfiguration consumer for a CLIENT identity when Nullock is itself connecting outbound (Repeater/Intruder/chain/crawler/audit HttpClient sends). Claim holds; evidence refreshed."},{"a":"sequencer","f":"Recorded login sequences (browser-recorded login replayed by the scanner) for authenticated crawl/audit","s":"partial","i":"medium","e":"months","g":"HTTP scanners and the crawler now use enabled cookies, tool-scoped session rules and recorded HTTP login macros, including expiry-triggered refresh. Browser interaction recording and JavaScript-driven login execution remain unavailable.","w":"The shared HTTP client applies Scanner-scoped session rules, captures rotated tokens/cookies and refreshes configured expired sessions. Explicit identity comparisons and recorded macro requests retain their own credentials.","v":"Src/Core/Networking/networking.cpp; session_rules.cpp; crawler.cpp; scripts/scanner_sessions_regression.py; Tests/session_rules/session_rules_test.cpp","o":"","r":"HTTP authenticated scan workflows verified, including form CSRF replacement, compressed token extraction, refresh cooldown, request fidelity and project isolation. Browser login execution remains a separate gap."},{"a":"sequencer","f":"Application login credentials (username/password pairs supplied to the scanner, which finds and drives the login form)","s":"absent","i":"medium","e":"weeks","g":"Absent. No credential input to any scanner, and no form-finding logic to drive one with (there is no HTML form parser in the extraction layers either — see the form-field item).","w":"Confirmed. The username/password hits in Src/Core/Networking/*.hpp are all prose or payload text; no configuration struct anywhere accepts credentials for a scan.","v":"Hits are host_header.hpp (password-reset poisoning prose), nosql_injection.hpp (an auth-bypass payload string), sequencer.hpp (a comment listing token kinds) -- confirmed still prose-only, no code reference. No scan-config struct has credential fields anywhere in Src/Core/Networking/ (SessionMacro's ChainRunner::Step, session_rules.hpp:96, carries only raw recorded HTTP bytes -- no username/password fields). The audit entry point (control_server.cpp `/api/audit/run`, in kActivePaths at :3263, handler at :7802) takes a target host, not credentials.","o":"","r":"Wave 0 register-accuracy audit: held at absent. kActivePaths/`/api/audit/run` drifted :2953 -> kActivePaths set starting :3256 (path listed at :3263) / handler at :7802 (both moved with the file's overall growth). Specifically checked the new SessionMacro struct (session_rules.hpp:88-102, added since the last audit) for a credentials field, since it is the newest 'login-adjacent' addition in this area: it carries `name`, `sessionHost`, `steps` (raw recorded ChainRunner::Step requests), `loggedOutStatus`, `loggedOutBodyRegex` -- no username/password fields, and nothing drives a login FORM (it replays already-recorded raw HTTP requests verbatim, it does not find-and-fill a form). Claim holds; evidence refreshed to also rule out the newest candidate location."},{"a":"platform","f":"Collaborator: HTTP interaction capture","s":"present","i":"high","e":"hours","g":"None for HTTP capture itself. (Reachability of the hits is a separate item — see Collaborator client.)","w":"Re-read Src/Core/APIs/Oast/oast_server.cpp in full. Every quoted line is real and at the cited offsets, and the wiring at app.cpp:877-882 exists verbatim. This one holds unchanged — it is a real socket server, not a lookalike: it parses the request line and headers, enforces slowloris deadlines on both header and body reads, extracts the token from BOTH the Host header and the path, and records so","v":"oast_server.cpp:111 `void OastServer::handleClient(QTcpSocket *socket) {`; :182-189 `hit.token = extractToken(hostHdr, path); hit.sourceIp = socket->peerAddress().toString(); ... hit.bodyPreview = QString::fromUtf8(rest.left(4096));`; :199-205 `static const QByteArray kBody = \"nullock-oast: callback received\\n\"; ... resp += \"HTTP/1.1 200 OK\\r\\n\";`. Wired at Src/App/app.cpp:877-878 `Nullock::Core::","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Collaborator: DNS interaction capture","s":"present","i":"medium","e":"hours","g":"DNS interactions are counted and correlated but never stored or listable — there is no way to inspect a DNS callback's source IP, qname or timing after the fact. Plus A-only answers regardless of QTYPE (no AAAA/TXT/CNAME/NS).","w":"DOWNGRADED. The capture path is real and does feed the correlator, but the first pass missed the bigger of the two defects. DnsSink stores NO hits at all — it has only a counter, not a list. So a DNS callback can auto-confirm a finding, but the raw interaction record is unrecoverable: /api/oast/poll reads `m_wiring.oast->hitsSince(...)`, which is the HTTP sink's ring buffer. A DNS-only Log4Shell c","v":"Src/Core/APIs/Oast/dns_sink.hpp:67 `int m_hitCount = 0;` — the ONLY hit state (compare oast_server.hpp:90 `QList<OastHit> m_hits;  // ring; we cap at kMaxHits`). dns_sink.cpp:114-115 `++m_hitCount; emit hitReceived(hit);` — emit-and-forget, nothing retained. dns_sink.cpp:63-64 `resp.append(char(0xC0)).append(char(0x0C)); resp.append(char(0x00)).append(char(0x01)); // TYPE A` with no QTYPE branch a","o":"partial","r":"partial -> present. Both defects fixed. (1) STORAGE+LISTING (the audit's 'bigger defect'): DnsSink gained a mutex-guarded OastHit ring (cap kMaxHits, own monotonic id space, mirrors OastServer) + hitsSince(sinceId), exposed at GET /api/oast/dns/poll?since=<id> -- a DNS-only callback (Log4Shell with LDAP egress firewalled, blind SSRF/XXE) is now listable with its qname, resolver source IP, timing, and record type, with a strictly-after cursor. (2) QTYPE: DnsLogic::ParsedQuery now parses qtype + a pure qtypeName(); the responder answers the type asked -- A for A/ANY, AAAA for AAAA, protocol-correct NODATA (NOERROR ANCOUNT=0) for anything else -- instead of always a mistyped A record; the interaction is logged regardless of qtype (token is in the QNAME). dns_logic_test 58/58 incl. qtype parse (A/AAAA/TXT/high-byte-257) + qtypeName, +2 mutations (parse reads QCLASS not QTYPE; qtypeName(28) mis-map). e2e vs the live UDP sink (14/14): listable w/ qname+sourceIp, cursor strictly-after, A->A, AAAA->AAAA, TXT->NODATA, every qtype logged. ctest 99/99, probe_smoke 156/156. NB the separate Collaborator-TAB item's 'Interactions table' still needs a ui-v2 panel to render these DNS rows (concurrent-agent lane); the backend list they need now exists."},{"a":"platform","f":"Collaborator: automatic scan-check integration and interaction-to-issue correlation","s":"present","i":"high","e":"hours","g":"","w":"Re-read Src/Core/APIs/Oast/oast_correlator.cpp end-to-end (85 lines) and the registration sites. Confirmed with no downgrade, and it is genuinely Burp-equivalent rather than a lookalike: registry is mutex-guarded, deduped via m_confirmed, bounded at 50k, and the kind is derived from the registered probe class so log4shell/xxe/rce callbacks each land as their own enriched finding. The register-befo","v":"oast_correlator.cpp:57 `const QString kind = baseKind + \"-confirmed\";`; :76-78 `baseKind.startsWith(\"log4shell\") || baseKind.startsWith(\"rce\") ? QStringLiteral(\"critical\") : QStringLiteral(\"high\");`; :80-81 `m_scanner->reportFinding(origin.rowId, severity, kind, summary, evidence, origin.host, origin.url);`. Registration-before-fire verified at control_server.cpp:2252-2264 `// Register BEFORE firi","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Collaborator: private server deployment","s":"present","i":"high","e":"days","g":"None -- the app now points at a remote nullock-oast via --oast-remote=URL --oast-remote-key=KEY (mint + poll proxied through the same correlator), completing the deploy-a-sink + use-it-from-the-desktop loop.","w":"Re-ran the grep myself across Src, ui-v2 and browser-ext rather than trusting it. Confirmed: OAST_ADMIN_KEY and X-Oast-Key appear ONLY inside Src/Tools/oast_server_main.cpp. There is no client. I also confirmed the desktop app unconditionally constructs its own in-process sink with no remote branch, so the 'partial' is correct and the gap statement is accurate.","v":"Src/Tools/oast_server_main.cpp:141 `if (QString::fromLatin1(l.left(c)).compare(\"X-Oast-Key\", Qt::CaseInsensitive) == 0)`; :144 `if (adminKey.isEmpty() || key != adminKey) { sendJson(s, 401, ...` ; :149 `if (method == \"GET\" && path == \"/poll\")`; :156 `if (method == \"POST\" && path == \"/mint\")`. Client side absent — Src/App/app.cpp:877 `Nullock::Core::OastServer oast;` is the only construction and ta","o":"present","r":"The deployable standalone sink (nullock-oast: POST /mint, GET /poll, X-Oast-Key) already existed; client mode completes the loop. OastServer::startRemote(url, key) (--oast-remote / --oast-remote-key) points the DESKTOP app at a remote sink: mint proxies to POST /mint, a poll timer pulls GET /poll and re-emits hits through the same correlator. Verified end-to-end (mint on remote -> callback on remote -> hit polled back). Falls back to the local sink if unreachable."},{"a":"platform","f":"Notes (free-text engagement notes stored in the project)","s":"present","i":"medium","e":"hours","g":"None -- a Notes editor now lives in the Scope tab (tabs.jsx ScopeTab): a textarea bound to scope.notes, dirty-tracked so a mid-typing snapshot poll never stomps unsaved edits, saved on blur / Ctrl+Enter / an explicit SAVE button via the pre-existing NL.actions.scopeSetNotes -> POST /api/scope/notes. Still a single project-wide blob -- per-host/per-issue/per-request notes remain out of scope, as originally flagged.","w":"Closed 2026-08-11: the backend setter (project_store.cpp setNotes/saveMetadata) and the client action (real-data.js scopeSetNotes) were already wired to /api/scope/notes; the only gap was a UI consumer. Added one in the Scope tab next to the existing in/out glob columns, reusing the tab where scope.notes already lives in app state.","v":"ui-v2/tabs.jsx ScopeTab -- new notes textarea + SAVE control calling dispatch({type:\"scope-set-notes\"}); ui-v2/app.jsx reducer case \"scope-set-notes\" calls act(\"scopeSetNotes\", value) -> NL.actions.scopeSetNotes (real-data.js:141, POST /api/scope/notes); Src/Core/Storage/project_store.cpp:335-338 setNotes persists via saveMetadata.","o":"present","r":"Scope-tab Notes editor + Update-check banner batch: adds the missing UI consumer for the already-complete scopeSetNotes/setNotes path."},{"a":"platform","f":"Project files: disk-backed project with save/restore of engagement state","s":"partial","i":"medium","e":"days","g":"Traffic + scope + M&R rules survive restart; nothing else. A directory of files, not a portable project file. No save-copy-as, rename, delete or compaction.","w":"Read saveMetadata() in full. The claim is exactly right and I can now enumerate the persisted set definitively: v, name, notes, created, updated, inScope, outOfScope, rules — and nothing else. Streaming replay of history.ndjson on open is real. 'partial' confirmed.","v":"Src/Core/Storage/project_store.cpp:359-403 ProjectStore::saveMetadata() -- the persisted set is far larger than the last audit found: v, name, notes, created, updated, inScope, outOfScope, rules, repeater, interceptRules, interceptAutoContentLength, interceptAutoFixNewlines, sessionMacros, advancedScope, acceptInvalidUpstreamHosts, sessionRules, cookieJar, suppressedKinds, falsePositiveKeys, severityOverrides, deletedKeys -- one project.json write per save. control_server.cpp /api/project/list (:10895), /api/project/open (:10906) and /api/project/create (:10911) are still the complete project-management surface: `grep -n \"renameProject|deleteProject|copyProject|compact\" Src/Core/Storage/project_store.hpp`: 0 hits.","o":"","r":"Wave 0 register-accuracy audit: held at partial, but the evidence needed a real correction, not a line refresh. The prior evidence's central claim -- \"the persisted set: v, name, notes, created, updated, inScope, outOfScope, rules -- and nothing else\" -- is now false: saveMetadata() (project_store.cpp:359-403) has grown to also persist repeater state, intercept rules and settings, session macros, advanced scope, accept-invalid-hosts, session rules, the cookie jar, and finding-triage state (suppressed kinds, false positives, severity overrides, deleted keys) -- ten fields the original evidence said did not exist. This is a substantial expansion of what survives a restart. The gap survives regardless: I checked project_store.hpp for rename/delete/copy/compact and found none (0 hits), and control_server.cpp's project surface is still exactly list/open/create -- no save-copy-as, no rename, no delete, no compaction, and it is still a directory of files (project.json + history.ndjson + findings), not a single portable project file. State holds at partial; evidence corrected to stop understating what persists."},{"a":"platform","f":"Project templates / scan configuration presets applied at project creation","s":"partial","i":"medium","e":"hours","g":"extensionsEnabled is the sole remaining schema-fidelity gap: a template promising to enable an extension does nothing, since extensions currently load globally from the app-data dir and there is no per-project enable set to write into. `rules` is NOT dropped -- create-from-template applies it (see reconciled 60cf588 below); a prior audit pass re-stated the pre-fix 'silently drops both' language after that fix had already shipped, which this pass corrects. GET /api/project/templates and POST /api/project/create-from-template are both ui-v2-reachable via Settings' Projects card (template picker + description hint + 'Create from template' button).","w":"Re-read the live create-from-template handler against the gap/why text above it and found them stale: they still said 'rules and extensionsEnabled ... silently drops both' even though the 2026-08-19 reconciled note directly beneath them (60cf588) already documents rules being applied via ruleFromJson/setRules, and the current source confirms it (control_server.cpp:5511-5517). Corrected the gap/why to match the reconciled history instead of contradicting it -- audit-register fix only, no code change this pass. 'partial' unchanged: extensionsEnabled is still genuinely unenforced.","v":"control_server.cpp:5502-5528: `m_wiring.projectStore->setInScope(inS); m_wiring.projectStore->setOutOfScope(outS); m_wiring.projectStore->setNotes(...);` followed by `QList<Nullock::Proxy::MatchReplaceRule> tplRules; for (const QJsonValue &rv : tplObj.value(\"rules\").toArray()) tplRules.append(ruleFromJson(rv.toObject())); m_wiring.projectStore->setRules(tplRules);` -- rules ARE parsed and applied. Then: `QJsonArray wantExt = tplObj.value(\"extensionsEnabled\").toArray();` is read only to echo back in the response (`extensionsRequested`), never enforced -- comment at :5519-5523 explains why (no per-project extension-enable set exists; semantics of 'ensure on' vs 'only these' are ambiguous). templates/projects/oauth-review.json ships a real non-empty `rules` array (1 rule) confirming the schema is genuinely exercised, not just theoretical. ui-v2 reachability unchanged from the 69ab754/60cf588 reconciles: ui-v2/real-data.js `projectTemplates()`/`projectCreateFromTemplate()`; ui-v2/app.jsx SettingsTab's Projects card.","o":"partial","r":"REGISTER FIX (stays partial, no code change). The gap/why fields had gone stale: they still claimed create-from-template 'silently drops both' rules and extensionsEnabled, but the 60cf588 reconciled note directly below (2026-08-19) already documents rules being applied, and control_server.cpp:5511-5517 confirms it live today (tplRules parsed via ruleFromJson, applied via setRules -- unchanged since 60cf588, no regression). Only extensionsEnabled remains a real gap (echoed as extensionsRequested, never enforced -- no per-project extension-enable set exists in ExtensionsApi/ProjectStore, confirmed by grep). Rewrote gap/why/evidence to match live source instead of contradicting the reconcile history beneath them; state and audited_state stay partial, unchanged. python3 scripts/parity_report.py --check green after the edit."},{"a":"platform","f":"Reporting: HTML issue report","s":"present","i":"high","e":"hours","g":"Report content is complete; delivery is not. No button, no menu, no pasteable URL — requires `curl -X POST -H 'X-Nullock-UI: 1'`. The Qt report pane is an 8-line placeholder.","w":"DOWNGRADED. The generator itself is real and better than the first pass implied — I read all ~170 lines and confirmed the grade badge, severity cards, stacked bar, scope block, per-finding CVSS/CWE/OWASP/compliance/fix table, and universal toHtmlEscaped(). But no user can produce it. I grepped ui-v2 recursively, Src/App/app.qml, and the docs for `/api/report/html|/api/report/build|/api/report/json","v":"Generator real: control_server.cpp:5047 `if (path == \"/api/report/html\") {` with `auto esc = [](const QString &s) -> QString { return s.toHtmlEscaped(); };` (5048) and the finding table at 5176-5200. Unreachable: `grep -an \"report/html\\|report/json\\|report/build\\|/api/report\" ui-v2/ -r` → no output; same grep over Src/App/app.qml → no output. Not allowlisted — control_server.cpp:1656-1685 isReadPa","o":"partial","r":"REPORTING tab adds Download Markdown / Download HTML buttons (fetch POST -> blob download) so the HTML/Markdown report is one click, no curl needed."},{"a":"platform","f":"Reporting/exports beyond Burp: SARIF, CycloneDX SBOM, Postman collection, OpenAPI, HAR, nmap XML, machine-readable master JSON","s":"exceeds","i":"medium","e":"hours","g":"","w":"CONFIRMED, and the first pass actually UNDERSOLD the UI story while getting its line numbers stale. Every endpoint exists (line numbers have drifted ~140 lines since their pass; I re-located each). More importantly, they claimed 'exactly one export button at app.jsx:809' — that is wrong twice over: app.jsx:809 is a `placeholder=\"csrf strip\"` input, and there are THREE working download buttons. All","v":"control_server.cpp:5748 `// GET /api/export/nmap-xml`; :5806 `// GET /api/export/sarif  -> findings as SARIF v2 (CI-friendly)`; :5875 `// GET /api/export/sbom  -> CycloneDX 1.5 SBOM`; :6009 `// GET /api/export/postman`; :4670 `if (path == \"/api/openapi/export\")`; :5225 `if (path == \"/api/report/json\")`. Allowlisted at control_server.cpp:1682 `|| p.startsWith(\"/api/export/\")`. UI buttons: ui-v2/app","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Scan-to-scan issue delta (new vs fixed findings between runs)","s":"present","i":"medium","e":"hours","g":"None -- the ISSUES tab has a Baseline bar (Save baseline / Diff vs current / Clear) showing hasBaseline/savedAt/count status and, after a diff, the new/fixed/unchanged counts plus the new and fixed finding lists.","w":"Closed 2026-08-10: ui-v2/app.jsx IssuesTab wires /api/baseline/save|status|diff|clear (previously API-only, zero ui-v2 callers).","v":"ui-v2/app.jsx IssuesTab Baseline bar + diff panel; control_server.cpp:4116 save, :4172 status, :4184 clear, :4189 diff.","o":"present","r":"Issues/Baseline batch: Baseline bar in the ISSUES tab (save/status/diff/clear) closes the GUI-reachability gap."},{"a":"platform","f":"One-click browser proxy configuration + CA trust path (the onboarding job Burp's browser does)","s":"partial","i":"medium","e":"weeks","g":"Extension must be side-loaded unpacked; CA must still be installed into the OS/browser trust store by hand per-platform, despite the manifest claiming one-click. Not comparable to a browser that just works.","w":"Read manifest.json and background.js myself. The extension is real MV3 and genuinely flips chrome.proxy.settings. The CA endpoints are real too. But note the manifest's own description overpromises — it claims 'one-click installs the CA cert', which MV3 cannot do; there is no OS-trust-store path in the extension. Combined with side-loading in developer mode, 'partial' is correct.","v":"browser-ext/manifest.json: `\"permissions\": [\"proxy\", \"storage\", \"tabs\"]` and `\"description\": \"Routes browser traffic through a local Nullock proxy and one-click installs the CA cert...\"`. browser-ext/background.js:32-45 `await chrome.proxy.settings.set({ value: { mode: \"fixed_servers\", rules: { singleProxy: { scheme: \"http\", host: cfg.proxyHost, port: cfg.proxyPort }, bypassList: cfg.bypassList } }, scope: \"regular\" });`.","o":"","r":"Wave 0 register-accuracy audit: held at partial. manifest.json and background.js are byte-identical to the prior audit (same permissions, same description overpromise, same chrome.proxy.settings.set call at background.js:32-45, was :30-44 -- a 2-line drift from unrelated file changes). The extension still has no OS/browser CA trust-store installer and still requires developer-mode side-loading. No change."},{"a":"platform","f":"DOM Invader (runtime DOM-XSS: canary injection, sink tracing, prototype-pollution scan, postMessage/web-message interception, stack traces)","s":"partial","i":"high","e":"months","g":"No runtime instrumentation: no canary tracing, no prototype-pollution gadget scan, no postMessage interception, no stack traces. Blind to SPA-framework-generated sinks. Produces leads, not confirmations.","w":"Read extensions/dom_taint.js. The source/sink vocabularies and the one-hop-with-two-propagation-passes dataflow are real, not co-occurrence matching, and the file's self-declared limits are verbatim as quoted. This is a legitimately useful lead generator, so it is more than a stub — but it shares no mechanism with DOM Invader (no runtime instrumentation of any kind, confirmed by the absence of any","v":"extensions/dom_taint.js:5-10 `Burp Pro's DOM Invader runs *inside* the browser and instruments the live DOM at runtime. Nullock is a proxy, so we can't hook the page -- but every script the app serves passes through us, and we can analyse it statically.`; :54 `{ re: /\\.\\s*innerHTML\\s*=/g, name: \"innerHTML\", cls: \"html\" },`. File is 256 lines total, source/sink tables and one-hop dataflow unchanged.","o":"","r":"Wave 0 register-accuracy audit: held at partial. dom_taint.js drifted 2 lines from a version-comment addition (\"nullock:version 0.2.0\" at :3) but the self-declared-limits quote, the source/sink regex tables and the one-hop dataflow logic are unchanged. Still no runtime instrumentation, no canary tracing, no prototype-pollution gadget scan, no postMessage interception, no stack traces -- confirmed no new files or functions under extensions/ or Src/ implementing any of those. Claim holds."},{"a":"platform","f":"Global search across all tools' items","s":"partial","i":"high","e":"days","g":"Proxy history only — Repeater, Intruder, issues, sitemap unsearchable. Worse, the 500-row cap scans the OLDEST 500 rows of the in-memory window, so recent traffic is invisible to search on any busy engagement, and the SQLite index holding the full history is never consulted.","w":"State confirmed, but the gap is materially WORSE than the first pass described and I want that on the record. They said the 500-row cap means 'the first 500 rows'. I checked ProxyModel::addResponse: rows are APPENDED at the end and evicted from the FRONT. So index 0 is the OLDEST retained row, and the search loop runs `row < min(n, 500)` from index 0. On any engagement past 500 requests, search co","v":"control_server.cpp:1755 `constexpr int kSearchRowCap     = 500;`; :1803 `const int rowLoopMax = std::min(n, kSearchRowCap);`; :1806 `for (int row = 0; row < rowLoopMax && hits.size() < limit; ++row) {` — ascending from 0. Ordering proof at Src/FrontEnd/GUI/Models/Proxy/proxy_model.cpp:70-73 `const int row = static_cast<int>(m_entries.size()); beginInsertRows({}, row, row); m_entries.append({ m_nex","o":"","r":"Both halves of the audited gap addressed; stays partial only because two of the FIVE sources remain. (1) The 500-row-cap-scans-oldest bug the audit flagged as 'materially worse' was already replaced (before this) by a newest-first scan under a wall-clock budget -- no fixed row cap, recent traffic searched first. (2) This commit fixes the SCOPE half: /api/search was proxy-history-only; the excerpt/limit/regex-safety logic is now a source-tagged addHits(source,id,where,text) shared by every store, and TWO new sources join under the SAME wall-clock budget + ReDoS guards -- Repeater tabs (request+response, honouring where=req|resp) and Issues (each finding's summary/evidence/url/host/kind/severity, on where=both). Every hit now carries a `source` field (proxy|repeater|issue). VERIFIED e2e over the live control API: a shared marker seeded into proxy history + a Repeater tab + a passive finding is returned tagged from all three sources; where=req excludes issues but still finds proxy+repeater; a source-unique marker yields only that source; every hit carries a source tag (7/7). Gauntlet ctest 98/98 + probe 156 (proxy-search regression intact). REMAINDER (-> stays partial): Intruder attack results and the site-map are not yet wired as search sources (the addHits seam makes each a small addition), and the SQLite full-history index is still not consulted for out-of-window rows."},{"a":"platform","f":"Resource pools (named concurrency/throttle pools assignable per task)","s":"partial","i":"medium","e":"days","g":"No named pool object and no cross-tool budget. Cannot say 'this fragile target gets 1 concurrent request across every tool' — three tools running at once still hammer the target independently.","w":"Grepped for the concept under every synonym I could think of (resourcePool, namedPool, poolName, sharedPool, globalThrottle). Exactly one hit in the entire codebase, and it is a comment on a per-tool field. Every other tool takes its own ad-hoc throttle argument. Confirmed partial — the throttling exists, the pool abstraction does not.","v":"`grep -rn \"resourcePool|namedPool|poolName|sharedPool|globalThrottle\" Src ui-v2`: 0 hits. Src/Core/Networking/intruder.hpp:190 `// Request-pool config (Burp-parity \"resource pool\"): how many requests may be` -- still the only occurrence repo-wide, still a comment on a per-tool field. Per-tool knobs: control_server.cpp:1672-1673 `intruder[\"concurrency\"] = m_wiring.intruder->maxConcurrency(); intruder[\"throttleMs\"] = m_wiring.intruder->throttleMs();`; crawler takes its own at :4728 `const int throttle = bodyJson.value(\"throttleMs\").toInt(200);`.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Same single repo-wide hit for the \"resource pool\" concept (intruder.hpp, drifted :155 -> :190), still just a comment on a per-tool field. Confirmed each tool (Intruder, crawler, deep-audit) still carries its own independent concurrency/throttle knob with no shared, named, cross-tool budget object. Claim holds; evidence line numbers refreshed."},{"a":"platform","f":"Burp REST API (service toggle, bind address, multiple named API keys, /v0.1/scan launch + status)","s":"exceeds","i":"low","e":"days","g":"Single shared bearer token rather than multiple revocable named keys; no self-describing OpenAPI/Swagger for its own endpoints (it can generate OpenAPI for targets, not for itself).","w":"Verified the security-critical half by reading app.cpp directly rather than trusting the quote. The token plumbing, the off-loopback refusal, the read/write method split and the CSRF guard are all real and correctly ordered (token check precedes CSRF, so scripted clients with a bearer token bypass the browser-only guard). The endpoint surface is genuinely far larger than Burp's /v0.1. 'exceeds' st","v":"Src/App/app.cpp:1308-1310 `QString apiToken = qEnvironmentVariable(\"NULLOCK_API_TOKEN\"); if (apiToken.isEmpty()) apiToken = flagValue(argc, argv, \"--api-token\"); controlServer.setApiToken(apiToken);`; :1326-1338 off-loopback bind without a token refuses to start (`FATAL: --listen=... binds the control API off loopback, which requires a token ... Refusing to start.`). Ordering verified in control_server.cpp:1108-1115 (bearer-token check) precedes the CSRF guard at :1143-1160 (`if (!tokenValid && !ControlLogic::isRequestAuthorized(...))`) -- a valid token skips the CSRF/Origin check entirely, confirming scripted clients bypass the browser-only guard via the token alone.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Headless operation (run without a display, for containers/CI)","s":"present","i":"high","e":"hours","g":"","w":"Re-read app.cpp around the flag and the app-class selection. Both quotes are verbatim and correct, and I confirmed the consequence they imply: QCoreApplication means no QPA platform plugin and no display server is required, and the QQuickStyle call is guarded behind `if (!headless)`. The headless run loop with worker drain is real. Confirmed present.","v":"Src/App/app.cpp:568 `const bool headless = hasFlag(argc, argv, \"--headless\") || !scanUrl.isEmpty();`; :623-626 `if (!headless) { QQuickStyle::setStyle(QStringLiteral(\"Basic\")); }`; :631-634 `QScopedPointer<QCoreApplication> app(headless ? new QCoreApplication(argc, argv) : static_cast<QCoreApplication *>(new QGuiApplication(argc, argv)));`; :1133-1143 `if (headless) { const int rc = app->exec(); s","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"CI integration with meaningful exit codes (fail the build on findings at/above a threshold)","s":"exceeds","i":"high","e":"hours","g":"","w":"Read runGateScan in full plus all of ci_gate_logic.cpp. The fail-closed preflight is real and correctly reasoned — any complete HTTP response counts as reachable, only a transport failure trips it, and the only escape from exit 3 is an explicit fail-on=none. Threshold parsing defaults unknown/empty to 'high' rather than to 'never fail', which is the safe direction. The shipped Action is real. 'exc","v":"control_server.cpp:9613 `int runGateScan(const QString &url, const QString &failOn, bool ndjson) {`; preflight at :9646-9678 `const auto pr = probe.send(t.host, ...); if (!pr.ok) { ... return ug.exitCode; }`. Src/Core/Networking/ci_gate_logic.cpp:83-87 `// An explicit \"none\"/\"off\" means the operator opted out ... Everyone else fails CLOSED: not scanning is not passing.` and `r.exitCode = neverFail","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Machine-readable live event stream for automation","s":"exceeds","i":"medium","e":"hours","g":"","w":"Read the whole ndjson block. The context-object threading fix is real and the explanatory comment is verbatim; the rowId uses lastId() not rowCount() specifically so ids stay monotonic past the window cap, which means response and finding events remain joinable — that is a subtlety a lookalike would get wrong. Query stripping defaults to ON. Every write is followed by an explicit flush, which matt","v":"Src/App/app.cpp:1040-1048 `without a context object this lambda would be a DirectConnection and run there ... so the one-object-per-line NDJSON contract tears apart under load.`; :1036 `const bool includeQuery = hasFlag(argc, argv, \"--ndjson-include-query\");`; :1069 `e[\"rowId\"] = model.lastId();` guarded by the comment `lastId(), NOT rowCount()`; :1075-1076 `QTextStream(stdout) << QJsonDocument(e)","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Container/Docker distribution for headless + CI","s":"partial","i":"medium","e":"hours","g":"The build-docker CI job (added last wave) is now confirmed GREEN end-to-end: `docker build` succeeds and `docker run ... --help` starts cleanly, closing the 'self-declared unvalidated, nothing ever proves it builds' half of the prior gap for real (last wave had only wired the job in without a Docker daemon to pre-validate it -- its very first real run failed, five times in a row, on real bugs this wave root-caused and fixed one at a time). Still genuinely missing: no published/pushed image (a `docker pull` still isn't possible -- the file only builds locally or in CI, it is not a distribution channel yet) and the base images are pinned to a version tag (`ubuntu:22.04`) rather than a content digest, so a tag repoint could still silently change the build.","w":"Confirmed the build-docker job's first real run (commit 41710a4/e73e96a) had actually failed -- `conclusion: failure` on GitHub Actions, not yet checked at the time it was added. Root-caused and fixed five distinct real bugs, one CI round-trip (~15-20min each, no docker daemon in this cloud session to pre-validate any of them locally) at a time, all specific to a bare `ubuntu:22.04` container lacking things GitHub's hosted runner images ship pre-installed and CI's `jurplel/install-qt-action` (which the Dockerfile's raw `aqt install-qt` call approximates, not calls) papers over: (1) aqtinstall renamed the Linux desktop arch from `gcc_64` to `linux_gcc_64` as of Qt 6.7.0 -- the Dockerfile's pin to 6.7.3 needed the new name; (2) Ubuntu 22.04's apt cmake (3.22.1) is older than CMakeLists.txt's `cmake_minimum_required(3.24)` -- switched to installing cmake via pip; (3) `zlib1g-dev` was missing (Src/BackEnd/Proxy/CMakeLists.txt:83 `find_package(ZLIB REQUIRED)` on Linux, since Qt's Linux build has no ZlibPrivate); (4) `libfontconfig1-dev`/`libfreetype-dev`/`libdbus-1-dev` (+ runtime counterparts) were missing -- libQt6Gui.so/libQt6DBus.so need them at link and load time; (5) FrontEndGUI (Src/FrontEnd/GUI, a `qt_add_qml_module` target -- the one SHARED lib in an otherwise all-STATIC Src/ tree) was never copied into the runtime image at all, so NullockApp couldn't even start -- switched the build stage to `cmake --install --component Runtime` to reuse the project's own existing install(TARGETS FrontEndGUI ...) + INSTALL_RPATH \"$ORIGIN\" rule (root CMakeLists.txt:89-99, added originally for Linux AppImage packaging) instead of re-solving it ad hoc, which also replaced three separate hand-copies of ui-v2/templates/extensions with the same install prefix; (6) the runtime image was also missing most of the GLVND OpenGL dispatch stack (`libopengl0`/`libegl1`/`libgles2`) plus Mesa's actual llvmpipe/swrast software driver (`libgl1-mesa-dri`) -- QT_QPA_PLATFORM=offscreen still needs a working GL context for FrontEndGUI's Qt Quick scene graph, and GitHub's runners have no GPU. Each fix was verified against the specific error the prior push's CI run actually produced, not guessed preemptively (the one exception: the GL-stack fix bundled 3 packages at once given the ~18min-per-round-trip cost, reasoning from the observed GLVND split rather than guessing blind). The sixth push (commit 6f39fea) is the first to come back fully green: both the `docker build` step and the `docker run --rm nullock:ci --help` runtime smoke step show `conclusion: success` on GitHub Actions run 32611161443.","v":"GitHub Actions run 32611161443, job 'build Docker image': `docker build` step conclusion=success (01:46:14-02:01:51, ~15.5min), `runtime smoke (--help, no listeners/token required)` step conclusion=success; Dockerfile (linux_gcc_64 arch, pip-installed cmake, zlib1g-dev/libfontconfig1-dev/libfreetype-dev/libdbus-1-dev in the build stage, `cmake --install build --component Runtime` instead of manual COPY of individual build-tree paths, libopengl0/libegl1/libgles2/libgl1-mesa-dri + libfontconfig1/libfreetype6/libdbus-1-3 in the runtime stage); root CMakeLists.txt:89-99 (the pre-existing install(TARGETS FrontEndGUI ...) + INSTALL_RPATH \"$ORIGIN\" rule this wave's fix reuses rather than re-solving); Src/BackEnd/Proxy/CMakeLists.txt:79-85 (the Qt6::ZlibPrivate-unavailable-on-Linux fallback that needs system zlib); no registry push step anywhere in the repo's workflows (grep for `docker push`/`docker/build-push-action` across `.github/workflows/` is empty) -- no published image exists; Dockerfile:22,79 `FROM ubuntu:22.04` still tag-pinned, not digest-pinned.","o":"partial","r":"Confirmed last wave's build-docker CI job had actually failed on its first real run (never checked before), then root-caused and fixed five distinct real bugs across five CI round-trips (Qt6.7 aqtinstall arch rename, apt cmake too old, missing zlib1g-dev, missing fontconfig/freetype/dbus dev+runtime libs, FrontEndGUI.so never installed into the runtime image, missing GLVND+Mesa-software-driver GL stack) until the sixth push came back fully green -- both docker build and the --help runtime smoke check now pass on GitHub Actions. No published image and no digest-pinned base remain, honestly unaffected -- this closes the CI-validation gap for real, not just 'wired in and hoped', which is what the state stays 'partial' for."},{"a":"platform","f":"Burp Suite DAST / Enterprise Edition (server-side scanning platform: multi-site scheduling, RBAC, SSO, scan agents, Jira/ticketing integration, dashboards)","s":"partial","i":"low","e":"months","g":"Findings-only sync, last-write-wins, no users/roles/SSO, no scheduling, no scan agents, no ticketing, no web dashboard. A seed of an Enterprise story, not one.","w":"Read workspace_server_main.cpp's header. It is a real deployable binary with SQLite/WAL storage and it reuses the same finding identity key as baseline/diff, which is a genuine design win — but its own header names every missing Enterprise pillar. Confirmed partial and the gap statement is accurate.","v":"Src/Tools/workspace_server_main.cpp:13-21 `Auth: a single shared bearer key (X-Workspace-Key header or ?key=). Full OIDC/SSO + per-user roles is the separate design/enterprise-sso.md track; this MVP is \"shared team key\"` and `Sync: per-engagement monotonic seq; push upserts by identity key and bumps seq, pull returns everything with seq > since. Last-write-wins.`; endpoints `POST /api/ws/push, GET /api/ws/pull` (header comment :21).","o":"","r":"Wave 0 register-accuracy audit: held at partial. workspace_server_main.cpp's header is unchanged in substance (drifted 12-17 -> 13-21, same self-declared MVP scope: shared bearer key, last-write-wins sync). Still no users/roles/SSO, no scheduling, no scan agents, no ticketing integration, no web dashboard beyond the sync API itself. Claim holds."},{"a":"platform","f":"Diagnostics / crash reporting for support","s":"present","i":"low","e":"hours","g":"GUI-reachable now: a Diagnostics card in Settings lists crash/non-fatal reports (GET /api/diagnostics) and lets you view one before filing an issue (GET /api/diagnostics/report?name=), and recordNonFatal() is now actually called (extension-load failure, onUnload handler throw) instead of being dead code. Remaining short of a full support pipeline: still local-only, no upload/telemetry (a deliberate privacy choice, not a gap) and no in-app 'File a GitHub issue' deep link with the report pre-attached.","w":"Closed 2026-08-29: added GET /api/diagnostics (+ /report) surfacing CrashReporter::crashDir()'s report listing/content, a Settings > Diagnostics card consuming it, and wired recordNonFatal() into extensions_api.cpp's two real error sites so the mechanism the header doc always described actually produces a report.","v":"control_server.cpp /api/diagnostics + /api/diagnostics/report handlers; ui-v2/app.jsx Diagnostics() card (Settings tab); extensions_api.cpp recordNonFatal() calls at the evaluate()-error and onUnload-error sites.","o":"present","r":"Diagnostics view wave: GET /api/diagnostics[/report] + Settings Diagnostics card + recordNonFatal() wired into its first two real call sites."},{"a":"platform","f":"Update check / new-version notification","s":"present","i":"low","e":"hours","g":"None -- App() now reads snapshot.update and shows a dismissible corner banner (current->latest version, release notes excerpt, a VIEW RELEASE button honoring the Qt.openUrlExternally convention used elsewhere in the app) whenever update.available is true. Dismissal is remembered per latest version (localStorage, best-effort) so it does not reappear until a newer release ships. No in-app download/apply -- the banner links out to the release page, matching the backend, which only checks and reports.","w":"Closed 2026-08-11: backend was already complete (UpdateChecker + root[\"update\"] in every snapshot). Added the one missing piece -- a frontend consumer -- as a small dismissible UpdateBanner component in app.jsx, wired off the existing nl-update snapshot-poll event so no new polling was needed.","v":"ui-v2/real-data.js applySnapshot: NL.update = snap.update || {available:false,...}; ui-v2/app.jsx UpdateBanner component + App() showUpdateBanner/dismissUpdate wiring; control_server.cpp:1552-1563 root[\"update\"] = {available,currentVersion,latestVersion,releaseUrl,releaseNotes,publishedAt}.","o":"present","r":"Scope-tab Notes editor + Update-check banner batch: adds the missing UI consumer for the already-complete UpdateChecker/root[update] path."},{"a":"platform","f":"Engagement tool: Generate CSRF PoC","s":"present","i":"medium","e":"hours","g":"None -- a CSRF POC button in the Proxy history / Site map DetailPane calls /api/csrf/poc and shows the generated HTML in an overlay with COPY and DOWNLOAD, ready to host on an attacker page. No technique selector (server auto-picks form vs fetch() PoC by content-type) -- a minor UI nicety, not a functional gap.","w":"Closed 2026-08-09: added NL.actions.csrfPoc(rowId) (POST /api/csrf/poc {id}) and a ⚔ CSRF POC button in DetailPane's row-action bar (ui-v2/proxy.jsx), reusing the existing CodecOverlay (extended with optional note + downloadName/DOWNLOAD-button props) to preview and save the generated PoC HTML.","v":"ui-v2/proxy.jsx DetailPane CSRF POC button + CodecOverlay note/downloadName props; ui-v2/real-data.js NL.actions.csrfPoc; control_server.cpp:3908 /api/csrf/poc handler (unchanged, already complete); request_export.cpp:50 csrfPoc() generator.","o":"present","r":"CSRF PoC wave: wired /api/csrf/poc into the GUI (Proxy history / Site map DetailPane), closing the last GUI-reachability gap."},{"a":"platform","f":"AI-assisted issue explanation / triage (Burp AI: Explain This, false-positive assessment)","s":"partial","i":"low","e":"hours","g":"A Triage button per finding in the ISSUES tab calls the endpoint and renders the model verdict (or the heuristic fallback text) inline. The verdict is now also cached to localStorage, keyed by the same finding-identity formula the backend already uses for its own per-finding flags (kind+U+001F+host+U+001F+url+U+001F+summary, matching FindingTriageLogic::findingKey) rather than the ephemeral row id, so it survives switching away from the ISSUES tab and back, and a full page reload -- closing the \"never persisted\" blocker. That persistence is honestly browser-local only, not a real per-project backend store: it does not sync across browsers/devices, is lost if site data is cleared, and is not scoped per-project the way Burp's own state would be. One blocker remains, unchanged: it still depends on an unbundled local Ollama instance serving qwen2.5:14b, with a silent heuristic fallback when that is not running.","w":"UPGRADED (partial, was already partial): ui-v2/app.jsx IssuesTab's doTriage() writes each completed verdict (model result or heuristic fallback) to a localStorage cache via saveTriageCacheEntry(), and a new hydration effect rehydrates React state for any currently-listed finding whose identity key is found in that cache on mount -- so a verdict computed before a tab switch (which previously unmounted IssuesTab and discarded its state) or before a page reload is shown again without re-querying the model. Re-clicking Triage on an already-triaged finding now just toggles the panel instead of re-fetching. Closes the persistence third of the prior gap; the Ollama dependency is unchanged, and the new persistence is explicitly client-local, not project-scoped -- both honestly disclosed above, not claimed fixed.","v":"ui-v2/app.jsx: findingIdentityKey()/loadTriageCache()/saveTriageCacheEntry() (localStorage key \"nl-triage-cache\"), IssuesTab's rehydration useEffect keyed on `findings`, and doTriage()'s cache-write + toggle-instead-of-refetch branch. Backend precedent for the identity formula: control_server.cpp:1362 `const QString fkey = FT::findingKey(f.kind, f.host, f.url, f.summary);` and Src/Core/Networking/finding_triage_logic.cpp:10-14 (QChar(0x1f) separator).","o":"partial","r":"Wave 2: persisted AI-triage verdicts to localStorage keyed by finding identity (matching the backend's own findingKey formula), closing the \"never persisted\" blocker; the Ollama dependency and the client-local (not per-project) nature of the new persistence remain honest partials."},{"a":"platform","f":"Collaborator: HTTPS interaction capture","s":"absent","i":"high","e":"days","g":"No TLS listener and no https:// payload form. Targets that only permit https:// egress (common in cloud SSRF and any app validating the scheme) can never call back.","w":"Re-ran the synonym hunt myself across the whole Oast directory for Ssl/ssl/https — zero hits. The listener is a plain QTcpServer and mintToken() emits only http:// in both URL forms, with no scheme parameter or branch. Confirmed absent.","v":"`grep -rni \"ssl|https\" Src/Core/APIs/Oast/*.cpp Src/Core/APIs/Oast/*.hpp`: 0 hits. oast_server.cpp:32 `m_server = new QTcpServer(this);`; :192 `const QString pathUrl = QString(\"http://%1:%2/oast/%3/cb\")...`; :199 `hostUrl = QString(\"http://%1.%2:%3/\").arg(tok, m_baseHost).arg(p);`.","o":"","r":"Wave 0 register-accuracy audit: held at absent. OAST directory unchanged in this respect (one new file since the last pass, oast_origin.hpp, is a data-struct extraction for the persistence feature reconciled separately under item #7/159 -- not a TLS listener). oast_server.cpp is still a plain QTcpServer with no SSL/TLS wrapping and both URL-minting sites emit http:// only (lines drifted 23->32, 76-77->192,199, content identical). Claim holds."},{"a":"platform","f":"Collaborator: SMTP / SMTPS interaction capture","s":"absent","i":"low","e":"days","g":"Email-header-injection / SMTP-relay OOB classes cannot be confirmed.","w":"Re-grepped case-insensitively across all of Src. Every hit is port-scanner service naming or banner classification — nothing that listens. No SMTP file exists in the OAST directory (which contains only dns_logic, dns_sink, oast_correlator, oast_logic, oast_server). Confirmed absent.","v":"`ls Src/Core/APIs/Oast/`: dns_logic.cpp/.hpp, dns_sink.cpp/.hpp, oast_correlator.cpp/.hpp, oast_logic.cpp/.hpp, oast_origin.hpp, oast_server.cpp/.hpp -- no SMTP listener. `grep -rni \"smtp\" Src` hits only port-scanner service classification (Src/Core/Networking/port_logic.cpp, Src/Core/Networking/scan_bridge.cpp) -- nothing that listens.","o":"","r":"Wave 0 register-accuracy audit: held at absent. The OAST directory listing grew by exactly one file since the last audit (oast_origin.hpp, the persistence-feature struct split from item #7/159 -- not SMTP-related). Every \"smtp\" grep hit across Src is still port-scanner banner classification, not a listener. Claim holds."},{"a":"platform","f":"Collaborator: hosted public server (zero-config, works out of the box)","s":"partial","i":"blocker","e":"weeks","g":"The app can now point at a hosted sink (--oast-remote), so OOB fires against real targets once you deploy nullock-oast. Remaining: a bundled zero-config public instance so it works with no setup -- ops, not code (the standalone sink already supports wildcard DNS + TLS).","w":"Confirmed, and this is correctly flagged as the blocker in this area. Both defaults are loopback, and I independently verified there is no hosted-service client (the OAST_ADMIN_KEY/X-Oast-Key grep matches only the standalone server binary). So out of the box every minted callback URL points at 127.0.0.1 and no blind-vuln class can ever fire against a real target without the user first standing up ","v":"Src/App/app.cpp:872-874 `const QString oastHost = flagValue(argc, argv, \"--oast-host\").isEmpty() ? QStringLiteral(\"127.0.0.1\") : flagValue(argc, argv, \"--oast-host\");`; oast_server.cpp:22 `m_baseHost = baseHost.isEmpty() ? QStringLiteral(\"127.0.0.1\") : baseHost;`; dns_sink.cpp:16-19 same loopback default for both baseHost and answerIp. No client: OAST_ADMIN_KEY / X-Oast-Key appear only in Src/Tool","o":"partial","r":"Client mode lands the app-side half: --oast-remote points the desktop app at a HOSTED nullock-oast so OOB fires against real targets. PARTIAL -- there is still no bundled zero-config public instance (the remaining piece is ops: run nullock-oast + wildcard DNS + TLS on a public box, all already supported by the standalone tool); until then the user supplies --oast-remote pointing at their own deployment."},{"a":"platform","f":"Collaborator client (dedicated panel: generate N payloads, copy to clipboard, poll now, view interaction detail)","s":"present","i":"high","e":"days","g":"None for the mint/poll/detail workflow or the blast spray. DNS-only interactions still never surface (DnsSink retains no hit list — see \"Collaborator: DNS interaction capture\"), so a pure-DNS Log4Shell confirmation stays invisible in this panel (the Blast section's Log4Shell checkbox fires the DNS-canary shots, but a hit only auto-confirms as a finding via the correlator — it will never appear as a row in this panel's own Interactions table).","w":"Closed 2026-08-09 (5d9c3c6): added a COLLABORATOR tab wiring /api/oast/mint and /api/oast/poll (mint payload, copy URL, poll now / auto-poll, click-through interaction detail). Extended 2026-08-10 (this wave): a Blast section in the same tab wires the previously-orphaned POST /api/oast/blast — target URL + SSRF/XXE/RCE/Log4Shell toggles, fires the spray, and renders the returned vector list (kind/note/token/callback URL) so the operator can see exactly what was fired. No backend change — the endpoint was already complete and allowlisted, only unreachable from the GUI.","v":"ui-v2/app.jsx CollaboratorTab (mint/poll/hit-table/detail-pane, plus the new Blast section); ui-v2/real-data.js NL.actions.oastMint/oastPoll/oastBlast; control_server.cpp:3593 POST /api/oast/mint returns {token,pathUrl,hostUrl,port,baseHost}; control_server.cpp:1927 GET /api/oast/poll returns {running,port,baseHost,hits:[{id,atMs,token,sourceIp,method,hostHeader,path,bodyBytes,userAgent,bodyPreview}]}; control_server.cpp:3619-3829 POST /api/oast/blast accepts {url,ssrf?,xxe?,rce?,log4shell?,paramNames?} and returns {fired,target,vectors:[{kind,note,token,callbackUrl}]} — every field the Blast section reads or sends matches.","o":"present","r":"Collaborator wave: dedicated COLLABORATOR tab wires /api/oast/mint and /api/oast/poll (mint payload, copy URL, poll now / auto-poll, click-through interaction detail). Extended this wave: a Blast section wires /api/oast/blast (SSRF/XXE/RCE/Log4Shell spray with target + toggles, fired-vector list). DNS-hit listing in the panel itself remains open, tracked separately under \"Collaborator: DNS interaction capture\"."},{"a":"platform","f":"Collaborator: interaction persistence across restarts","s":"partial","i":"medium","e":"hours","g":"The ACTIONABLE half now persists: OastCorrelator saves its token registry (token -> origin) and already-confirmed set to <appdata>/oast-interactions.json (atomic QSaveFile write on every register / new confirmation) and reloads it on startup, so an overnight callback that lands AFTER a restart still correlates to the token minted before it and emits its confirmed finding, and an interaction already reported is never re-reported. STILL in-memory-only: the raw hit LOG shown by /api/oast/poll (oast_server's capped m_hits ring) and DNS hits (never stored even in RAM) -- those remain lost across a restart.","w":"Partial-closed 2026-08-24: added OastLogic::serializeState/deserializeState (pure, versioned, Core-only) + OastCorrelator::setPersistPath (loads on set) / saveLocked (atomic write on each change), wired in app.cpp to an AppDataLocation file. This makes the correlation -- the part that turns a callback into a finding -- survive restarts. The raw poll-log ring + DNS-hit retention are a separate, larger change (QtNetwork sink TUs) and remain open.","v":"oast_logic.cpp:12 `QJsonObject serializeState(...)`; :36 `void deserializeState(...)`; oast_correlator.cpp:12 `void OastCorrelator::setPersistPath(const QString &path) {`, :26 `void OastCorrelator::saveLocked() const {`, called from registerToken (:46) and the onHit new-confirmation branch (:71 `else { m_confirmed.insert(hit.token); saveLocked(); }`); app.cpp:1186 `oastCorrelator.setPersistPath(oastDir + \"/oast-interactions.json\");`.","o":"","r":"Wave 0 register-accuracy audit: held at partial. All cited functions and call sites verified present and wired exactly as described (serializeState/deserializeState in oast_logic.cpp, setPersistPath/saveLocked in oast_correlator.cpp called from both registerToken and the onHit confirmation path, app.cpp wiring to AppDataLocation/oast-interactions.json). The raw poll-log ring and DNS-hit retention remain the larger, un-persisted half of \"interaction persistence\" as the original note said. Claim holds; this is the one platform-area item that already carried fresh, accurate evidence from its 2026-08-24 closing commit -- only the audit-trail (reconciled) block was missing."},{"a":"platform","f":"Logger (records HTTP traffic from ALL Burp tools and extensions, not just the proxy)","s":"partial","i":"high","e":"weeks","g":"Reclassify stub->partial: the prior 'Repeater traffic never lands in history' is now STALE — the /api/.../replay handler appends replayed responses to both history model and ProjectStore (control_server.cpp:2944-2946), and the crawler already logs (app.cpp entryLoaded->addResponse/appendEntry). What is genuinely still missing is (a) any tool-attribution/source column — ProxyModel::Roles has no Sou","w":"Reclassified stub -> partial (2026-08-02): triage + adversarial-verify agreed; keyed by stable roadmap id, area-guarded. See PARITY-BACKLOG.md.","v":"control_server.cpp:3154 `if (parts[1] == \"replay\")` -> :3214 `if (w.history) w.history->addResponse(r, resp);` / :3216 `if (w.projectStore) w.projectStore->appendEntry(r, resp);`. proxy_model.hpp:14-25 Roles {Id,Host,Method,Url,StatusCode,Mime,Params,Tls,Ip,Timestamp} -- still no source/tool role. intruder.cpp:124 `: QAbstractListModel(parent), m_model(historyModel) {}` -- its own separate model, not routed through proxy history.","o":"stub","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"platform","f":"Logger: capture filters, view filters, custom columns, per-tool filtering","s":"absent","i":"high","e":"weeks","g":"No 'show me only Scanner traffic' or 'only requests my extension modified'. No custom columns, no script-based filters — and no source column exists to build them on.","w":"Confirmed. I read the filter builder in history_logic.cpp — the supported keys are exactly method/host/path/status/minSize/maxSize/sinceMs and nothing else, and I separately confirmed ProxyModel exposes no source/tool role, so per-tool filtering has no column to filter on even in principle. Confirmed absent.","v":"Src/Core/Storage/history_logic.cpp:43-103 buildFindQuery() builds the WHERE clause from a fixed key set only: method (:67-70), host LIKE (:71-81), path LIKE (:82-85), and addNumeric-driven status/minSize/maxSize/sinceMs (:86-89) -- nothing else. Unrecognized numeric keys are collected into `ignoredFilters` (:59 `if (ignoredFilters) ignoredFilters->append(key);`). No source column: Src/FrontEnd/GUI/Models/Proxy/proxy_model.hpp:14-25 `enum Roles { IdRole = Qt::UserRole + 1, HostRole, MethodRole, UrlRole, StatusCodeRole, MimeRole, ParamsRole, TlsRole, IpRole, TimestampRole };` -- no tool/source role.","o":"","r":"Wave 0 register-accuracy audit: held at absent. buildFindQuery's supported key set is unchanged (method/host/path/status/minSize/maxSize/sinceMs), only line numbers drifted (67-89 -> 43-103, the function itself starts at 43 not 67 -- a fuller citation, not a content change). ProxyModel's Roles enum is unchanged, still no source/tool role to filter on. No custom-column or script-filter mechanism exists anywhere in the history/proxy-model layer. Claim holds."},{"a":"platform","f":"Organizer (collect messages into collections, read-only copies + metadata)","s":"absent","i":"medium","e":"weeks","g":"No way to set aside interesting requests for later. Testers keep a second window or notepad.","w":"Confirmed. I did not just grep 'Organizer' — I hunted the synonyms this codebase might plausibly use: collection, bookmark, starred, pin/pinned, shortlist, savedItems. Every hit across Src and ui-v2 is unrelated (pinned certificates, pinned crawler ports, pinned CVE versions, Postman collections). No collection concept exists.","v":"`grep -rani \"collection\\\\b|bookmark|starred|pinned|shortlist|savedItems\" Src ui-v2` returns only unrelated matches: cert-pinning comments (proxy_server.cpp, proxy_server.hpp), a version-pinned CVE table (service_vulns_logic.cpp), a Postman-collection exporter (control_server.cpp:7187-7212, ui-v2/proxy.jsx:1048, 2289), and marketplace catalog integrity pinning (marketplace_logic.hpp). No collection/bookmark concept exists anywhere.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-ran the full synonym grep; the hit set shifted (a Postman-collection exporter and a service-CVE version-pin table are new-ish additions since the last pass) but every single hit is still an unrelated use of the words \"collection\"/\"pinned\". No way to set aside interesting requests into a saved, read-only collection exists in Src or ui-v2. Claim holds."},{"a":"platform","f":"Annotations: per-item Notes column and colour highlighting on Proxy history / any message table","s":"partial","i":"high","e":"days","g":"Other message tables and global report formats do not yet share this annotation store; Proxy history and Site map workflows are implemented.","w":"Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action.","v":"Src/Core/Storage/project_store.cpp (historyAnnotations, annotateHistory, HAR import/export); Src/BackEnd/Control/control_server.cpp (/api/history/annotations, /api/history/annotation); ui-v2/real-data.js and proxy.jsx; bin/nullock; scripts/annotations_regression.py; Tests/ui/annotations_data_test.cjs and annotations_browser_test.cjs.","o":"partial","r":"Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action."},{"a":"platform","f":"Project files: scan issues persisted in the project and restored on reopen","s":"present","i":"blocker","e":"days","g":"None -- findings persist to <project>/findings.ndjson at discovery time and are streamed back into the findings panel on reopen; the baseline diff no longer reports restored issues as FIXED because the live set is repopulated first.","w":"Closed 2026-08-13: added a pure FindingSerial JSON round-trip (finding_serial.cpp, its own unit test, mutation-proven on the ts + compliance fields); ProjectStore.appendFinding writes findings.ndjson (deduped by the baseline identity key) and streamExistingFindings/restoreFindings stream it back on open; PassiveScanner gained a findingAdded signal (append-on-discovery, crash-safe) + ingestFinding (verbatim restore, no re-enrich/re-persist); app.cpp wires both. Restore preserves ts/enrichment/rowId. Gauntlet 93/93 + 156/156.","v":"`grep -rn \"findings.json|findings.ndjson|saveFindings|loadFindings|persistFindings\" --include=*.cpp --include=*.hpp Src` → no output. `grep -n \"findings\" Src/Core/Storage/project_store.cpp Src/Core/Storage/project_store.hpp` → no output. saveMetadata (project_store.cpp:283-315) serialises only v/name/notes/created/updated/inScope/outOfScope/rules. On open only traffic is replayed: Src/App/app.cpp:","o":"present","r":"Findings persist to <project>/findings.ndjson (append-on-report, deduped by the baseline identity key) and restore into the panel on reopen, preserving each finding's ts, enrichment and history rowId. New pure FindingSerial module (unit-tested + mutation-proven on ts/compliance), PassiveScanner findingAdded signal + ingestFinding restore, ProjectStore appendFinding/streamExistingFindings. Gauntlet ctest 93/93, probe_smoke 156/156."},{"a":"platform","f":"Project files: Repeater tabs, Intruder attack config and Sequencer state saved in the project","s":"partial","i":"high","e":"days","g":"Repeater tabs and Intruder configuration/result rows now restore with each project. Sequencer state is still not project-persisted. Intruder saves on project switch and clean exit, not after every edit; raw response bodies are not in the existing saved-run format.","w":"Repeater persistence already existed. Intruder now saves atomically to intruder.json, restores after startup/project changes without sending requests, resets every setting for fresh projects, and retains the current draft if saving or incoming-file validation fails. The combined feature stays partial until Sequencer state is also persisted.","v":"Src/Core/Storage/project_store.cpp: open/saveIntruderWorkspace; Src/App/app.cpp: setWorkspaceSave, intruderWorkspaceChanged and saveWorkspaceOnExit after worker drain; Src/Core/Networking/intruder.cpp: clearAll/loadRun; scripts/intruder_workspace_regression.py (19 runtime checks); Tests/ui/intruder_workspace_browser_test.cjs (two-client synchronization, project isolation, reload).; Tests/ui/intruder_data_test.cjs (ordered writes, stale polls, rejected old-project edits and failure recovery).","o":"absent","r":"Intruder configuration and result rows persist per project on switch/clean exit and restore idle. Browser drafts survive stale polls; rules/grep settings synchronize and stale project edits are refused. Runtime, browser and CLI checks pass. Sequencer persistence remains outstanding."},{"a":"platform","f":"Project options vs user options (settings split, persisted across restarts)","s":"absent","i":"medium","e":"days","g":"Everything non-project is a CLI flag or env var. No persisted preferences, no per-project vs per-user distinction.","w":"Confirmed. I grepped for QSettings and for the synonyms a Qt codebase might use instead (preferences, userSettings, settings.json) across all .cpp/.hpp in Src — the only matches are a content-discovery wordlist entry and unrelated TLS comments. There is no user-level settings store of any kind.","v":"`grep -rni \"QSettings|preferences|userSettings|settings.json\" --include=*.cpp --include=*.hpp Src` returns only Src/Core/Networking/content_discovery.cpp:73 `\"settings.py\", \"web.config\", \"appsettings.json\", \"wp-config.php.bak\",` (a fuzzing wordlist) and Src/Core/Networking/tls_profile.hpp:10,22 (cipher-preference prose comments). Theme choice resets each launch: Src/FrontEnd/GUI/Themes/themes_manager.cpp:13 `ThemesManager::ThemesManager(QObject *parent) : QObject(parent), m_current(\"cyber\") {`.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Grep results are the same shape as the prior pass (a fuzzing wordlist entry and TLS cipher-preference prose, neither a settings store). ThemesManager still hard-codes its startup theme in the constructor with no persisted user-level store. No QSettings, preferences file, or user-vs-project options split exists anywhere in Src. Claim holds."},{"a":"platform","f":"Configuration import/export as JSON (and Burp's configuration library / named config presets)","s":"present","i":"medium","e":"days","g":"None -- the ui-v2 preset switcher now exists: Settings' Project card gained a \"Config presets\" row (name input + Save, a saved-presets <select> + Load/Delete) wired to all four preset endpoints.","w":"Implemented. GET /api/config/export + POST /api/config/import move a versioned {format:'nullock-config',version,sections} document carrying scope (in/out/notes/advanced), match&replace rules, session-handling rules and intercept rules. Import reuses the EXACT setters behind /api/scope, /api/rules, /api/session-rules and /api/intercept/rules, so a re-imported config and the live editors are one code path; the envelope refuses a newer-major-version document and a non-Nullock document. The preset library (POST /api/config/presets/save|load|delete + GET /api/config/presets) is built ON TOP of that same code: save snapshots live config via the SAME capture used by export, and load applies via the SAME per-section apply used by import (both extracted to shared captureConfigSections()/applyConfigSections() lambdas), so a preset is byte-for-byte an export document. Partial only because the ui-v2 preset switcher is not built yet. Closed 2026-08-28: added the missing ui-v2 preset switcher. SettingsTab (app.jsx) gained presets/presetName/presetSel state, a refreshPresets() poll-on-mount, and savePreset/loadPreset/deletePreset handlers calling the four new real-data.js actions (configPresetsList/Save/Load/Delete). Rendered as a row in the Project card: a name input + SAVE, a <select> populated from GET /api/config/presets + LOAD/DELETE, disabled appropriately when no name is typed or no preset is selected. Load surfaces the applied-section list via alert(), matching the existing Import config pattern.","v":"control_server.cpp `/api/config/export`+`/api/config/import` (now sharing captureConfigSections()/applyConfigSections()) + the preset library `/api/config/presets/save|load|delete` and GET `/api/config/presets` (persisted to AppData/config-presets.json as {name:document}; name-validated via ControlLogic::presetNameValid, listed via ControlLogic::presetNames). Envelope + preset logic pure + mutation-proven in Tests/control_logic/control_logic_test.cpp (buildConfigDocument/validateConfigDocument M1 version-gate + M2 format-gate; presetNameValid M_A char-allowlist + M_B dot-only, presetNames sorted-keys). Live e2e 14/14 (scripts scratchpad preset_verify): add scope marker → save preset → remove marker → load preset restores the marker (apply path proven) → list shows it → delete removes it; invalid names (bad/name, '..', empty) rejected; missing-preset load → ok:false; real project.json + config-presets.json snapshot-restored. ui-v2/app.jsx SettingsTab (presets state + Config presets row in the Project card); ui-v2/real-data.js NL.actions.configPresetsList/Save/Load/Delete. Verified: bundled-babel transform of both touched files; a 13-assertion Node functional test (fake fetch, minimal browser-global shims) confirming each action hits the correct path/method and carries the correct {name} body against control_server.cpp's actual /api/config/presets* contract.","o":"partial","r":"Preset-library gap closed: wired the ui-v2 SWITCHER this item's own prior wave flagged as the sole remaining piece. absent->partial->present."},{"a":"platform","f":"Reporting: XML issue report","s":"present","i":"low","e":"hours","g":"Pipelines built on burp_issues XML (Dradis/Faraday importers, report generators) cannot ingest Nullock output directly. SARIF/JSON are arguably a better modern answer, so this is a compatibility gap rather than a capability gap.","w":"Confirmed. I enumerated every /api/export/ route in control_server.cpp myself: nmap-xml, sarif, sbom, postman. The only XML emitter is the port-scan nmap format; there is no issue-XML schema anywhere. The first pass's line numbers were stale by ~140 lines but the conclusion is right.","v":"`grep -n \"/api/export/\" Src/BackEnd/Control/control_server.cpp` → :5748 `// GET /api/export/nmap-xml  -> port scan results as nmap-compatible XML`, :5806 `// GET /api/export/sarif`, :5875 `// GET /api/export/sbom`, :6009 `// GET /api/export/postman`. No burp_issues-shaped XML exists.","o":"present","r":"Closed 2026-08-11: GET /api/report/xml serializes the report/json finding corpus into a Burp-style XML issue report (<nullockReport>/<issue> with name/host/url/cwe/owasp/detail/remediation). The finding->XML pass is the pure, mutation-tested ControlLogic::findingsJsonToXml -- every attacker-influenced value is xmlAttrEscape'd so a summary carrying <\/issue> cannot break framing."},{"a":"platform","f":"Reporting: report customisation (select which issues to include, severity/confidence filter, detail level, custom title/appendix, request-response inclusion)","s":"partial","i":"high","e":"days","g":"Issue SELECTION now spans ALL FOUR report sinks: GET /api/report/json + /api/report/xml (query params) and POST /api/report/build (Markdown) + /api/report/html (JSON body) all take minSeverity/minConfidence/includeKinds/excludeKinds/includeFixed and emit only the issues that pass, via one shared predicate (ControlLogic::findingPasses). The two builders also accept a custom `title` and an `appendix`. json keeps posture/coverage over the FULL set (+ findingsTotal vs findingsTotalAll + filtered flag) so an API consumer sees engagement truth; the two human reports reflect the INCLUDED set throughout (Burp's report-wizard behaviour) and print a 'showing X of Y (filtered)' note. Still partial for: a detail-level toggle, and full request/response evidence embedding (evidence is still truncated).","w":"Implemented + mutation-proven. One selection rule, one source of truth: ControlLogic::findingPasses(severity,confidence,kind,fixed,criteria) backs both filterFindings (the JSON-shape path) and the QList<Finding> report builders; criteria are parsed by reportFilterFromQuery (GET) / reportFilterFromJson (POST). severity floor via severityRank, confidence floor via confidenceRank (confirmed/firm/tentative AND high/medium/low), kind include/exclude (exclude wins), includeFixed. All live in control_logic (Qt6::Core-linkable, unit-tested) -- deliberately NOT in control_server.cpp's anonymous namespace, which reproducibly ICE'd MSVC 14.38 (C1001).","v":"control_logic.cpp:298 `bool findingPasses(const QString &severity, const QString &confidence, ...)`; :355 `ReportFilterCriteria reportFilterFromQuery(const QUrlQuery &q) {`; :368 `ReportFilterCriteria reportFilterFromJson(const QJsonObject &body) {`. All four report sinks wired to the shared predicate: control_server.cpp GET /api/report/json (:6200), GET /api/report/xml (:6257), POST /api/report/build (:5884), POST /api/report/html (:5995).","o":"","r":"Wave 0 register-accuracy audit: held at partial (real parity for issue selection, still missing detail-level and request/response-inclusion controls per the existing gap text). findingPasses/reportFilterFromQuery/reportFilterFromJson all present and wired to all four report endpoints exactly as the last (already-fresh, 2026-08-2x-vintage) evidence described; this item only needed the audit-trail block, not a re-derivation. Claim holds."},{"a":"platform","f":"Reporting: reachable from the UI (Report menu / right-click > report selected issues)","s":"present","i":"high","e":"hours","g":"None -- the REPORTING tab (ReportingTab in ui-v2/app.jsx, mounted at `tab === \"reporting\"`) is Burp's Report menu equivalent: every engagement report is one click. The Engagement report section now downloads Markdown (POST /api/report/build), styled HTML (POST /api/report/html), JSON (GET /api/report/json), and the Burp-style XML issue report (GET /api/report/xml) plus a View-summary readout; the same tab drives OpenAPI export/import, SBOM download, and workspace push/pull. The POST-only generators are reached via fetch->blob download (downloadBlob), the two allowlisted GET reports via a plain anchor (downloadHref). No curl needed for any format.","w":"Reconciled forward. The original 2026-08-08 note already recorded the REPORTING tab shipping (Markdown/HTML/JSON reachable from one panel), but the top-level gap/why/evidence were never updated off the pre-tab 'you must curl it' state and audited_state was left at stub. Re-derived against live source this wave: the tab exists and is mounted, all four report formats download from buttons, and the XML report -- the last format that was reachable only via curl -- now has its own Download XML button too.","v":"ui-v2/app.jsx: ReportingTab Engagement-report Btns -- Download Markdown (downloadBlob->NL.actions.reportBuild), Download HTML (downloadBlob->NL.actions.reportHtml), Download JSON (downloadHref '/api/report/json'), Download XML (downloadHref '/api/report/xml'); tab mounted at `{tab === \"reporting\" && <ReportingTab />}`. Backend: control_server.cpp report/build :5473, report/html :5561, report/json :5739, report/xml :5787; isReadPath allowlists report/json :1764 and report/xml :1765 so the GET anchor downloads work without the X-Nullock-UI header.","o":"present","r":"Register reconciled to reality (audited_state stub->present) and the last curl-only report format wired: a Download XML button (GET /api/report/xml) added beside the existing Markdown/HTML/JSON downloads, so every engagement report format is now one click from the REPORTING tab. Builds on the 2026-08-08 tab (557e5f8)."},{"a":"platform","f":"Issue lifecycle: mark false positive, set issue status/severity override, delete issue","s":"present","i":"high","e":"days","g":"None — all three named actions (mark false positive, severity override, delete) are reachable end-to-end in ui-v2's Issues tab, on top of the per-project-persisted backend that already covered them.","w":"Backend + API covered the whole triage lifecycle since 536f2b7 (false-positive marking, severity override, soft-delete, all persisted per-project keyed by finding identity, applied at display time) but had no caller anywhere in ui-v2 — confirmed via a fresh grep (zero hits for set-severity/findings/delete/findings/mark/suppress-kind in any ui-v2/*.jsx before this wave). IssuesTab now wires all four endpoints: a per-row FP/un-FP toggle, a del/restore toggle, and a severity-override select, plus a per-kind mute toggle on the kind-filter chips (bonus — suppress-kind was also unwired). Deleted and muted-kind findings are hidden from the default view behind a new 'show hidden' toggle that reveals + lets them be restored; a plain false-positive mark stays visible, dimmed and struck-through, matching Burp only annotating rather than hiding an FP-marked issue.","v":"ui-v2/app.jsx IssuesTab's doMarkFP/doToggleDelete/doSetSeverity/doSuppressKind call NL.actions.findingMark/findingDelete/findingSetSeverity/findingSuppressKind (ui-v2/real-data.js) -> POST /api/findings/{mark,delete,set-severity,suppress-kind}; every field read (f.falsePositive/f.deleted/f.suppressed/f.severity/f.id) matches control_server.cpp:1358-1393's /api/snapshot findings array field-for-field.","o":"present","r":"Wave 2: wired the already-complete backend issue-lifecycle (FP mark, severity override, soft-delete, kind-mute) into ui-v2's Issues tab — the remaining follow-on this item's own prior reconciled note (536f2b7) had explicitly flagged as outstanding. No backend change."},{"a":"platform","f":"Burp's browser (embedded pre-configured Chromium — no proxy config, no CA install)","s":"absent","i":"high","e":"months","g":"Onboarding requires manually configuring a browser proxy and installing the CA into the OS/browser trust store. Burp's single biggest friction-remover.","w":"Confirmed. Grepped for QWebEngine, WebEngine, chromium, puppeteer and playwright across .cpp/.hpp/CMakeLists and got zero hits — importantly including CMakeLists.txt, so no browser component is even linked. The only launch behaviour is opening the user's own default browser at the control UI. Confirmed absent.","v":"`grep -rni \"QWebEngine|WebEngine|puppeteer|playwright|chromium\" --include=*.cpp --include=*.hpp Src CMakeLists.txt`: 0 hits. Src/App/app.cpp:1346 `if (!headless && ctlLoopback) QDesktopServices::openUrl(QUrl(url));` -- the default OS browser at the control UI, nothing embedded.","o":"","r":"Wave 0 register-accuracy audit: held at absent. No embedded-browser dependency of any kind is linked (CMakeLists.txt included in the grep, still 0 hits). The only launch behaviour is opening the user's own default browser (app.cpp, drifted :1021 -> :1346, unchanged content). Claim holds."},{"a":"platform","f":"Dashboard task engine: live task list with per-task progress, pause/resume/cancel, task detail view","s":"absent","i":"high","e":"weeks","g":"Once /api/audit/all or /api/probe/all starts you cannot see progress, pause it, or stop it. Burp's Dashboard is the primary control surface for exactly this.","w":"Confirmed. I grepped for a task registry under several names (tasks array, taskList, jobQueue, progressPct, cancelTask, pauseTask) — nothing exists. I then read the audit sweep entry point directly and confirmed it is exactly as described: a single global atomic that only answers 'already running', with no handle, no counter and no cancel path once QtConcurrent::run is dispatched.","v":"`grep -rani \"\\\"tasks\\\"|taskList|jobQueue|progressPct|cancelTask|pauseTask\" Src ui-v2`: 0 hits. control_server.cpp:7858-7861 `static QAtomicInteger<int> auditAllInFlight(0); if (!auditAllInFlight.testAndSetAcquire(0, 1)) return okJson({{ \"ok\", false }, { \"queued\", 0 }, { \"error\", \"a deep-audit sweep is already running\" }});` then dispatched fire-and-forget via QtConcurrent::run with no handle, counter, or cancel path.","o":"","r":"Wave 0 register-accuracy audit: held at absent. No task-registry vocabulary exists anywhere (0 hits repeated). /api/audit/all is still gated by a single global QAtomicInteger that answers only \"already running\" -- no handle, no per-task progress, no pause/resume/cancel, no detail view (line drifted 6657-6660/6725 -> 7858-7869, logic byte-identical). Claim holds."},{"a":"platform","f":"Dashboard event log (suite-wide errors, warnings, info)","s":"absent","i":"medium","e":"days","g":"Failures are silent to the operator. A failed SQLite index, a dropped filter, a TLS error — none of it surfaces.","w":"Confirmed. Grepped eventLog/appLog/activityLog/toast/notification: the only 'EventLog' is H2EventLog, which I checked is an HTTP/2 frame tracer (noteFrame / noteRequestHeader / noteResponseStatus / noteRstStream), not an application log. The only operator-visible log is the per-extension one. Backend errors go to qWarning(), which per this project's own build model is invisible in the shipped GUI-","v":"Src/BackEnd/Proxy/h2_events.cpp:19 `void H2EventLog::noteFrame(...)`, :52 noteRequestHeader, :69 noteResponseStatus, :79 noteRstStream -- an HTTP/2 protocol frame tracer, not an application log. Only user-facing log: control_server.cpp:1311-1313 `for (const QString &line : m_wiring.extensions->recentLog(40)) extLog.append(line); bootInfo[\"extensionsLog\"] = extLog;`. `grep -rani \"eventLog|appLog|activityLog\\b\" --include=*.cpp --include=*.hpp Src`: 0 hits outside H2EventLog.","o":"","r":"Wave 0 register-accuracy audit: held at absent. H2EventLog's four note* methods are unchanged (line numbers identical: 19/52/69/79), confirmed it is still purely an HTTP/2 frame tracer with no general error/warning/info channel. The only operator-visible log surface is still the per-extension recentLog (control_server.cpp, drifted 1224-1227 -> 1311-1313). Backend qWarning() output is still not surfaced anywhere in the GUI. Claim holds."},{"a":"platform","f":"Scheduled tasks (run a scan/task at a given time or on a repeating schedule)","s":"absent","i":"medium","e":"days","g":"No recurring scans. The workaround is external cron driving --scan, which loses all project context.","w":"Confirmed. Grepped for scheduled/schedule/cron/recurring and for timer-driven task patterns across .cpp/.hpp/.jsx — no timer-driven task registry exists anywhere in product code. Consistent with the absence of a task engine generally.","v":"`grep -rani \"QTimer.*schedul|cron|recurring\" --include=*.cpp --include=*.hpp --include=*.jsx Src ui-v2` now returns false-positive noise from Src/Core/Networking/session_rules.cpp (`macroName` contains the substring \"croN\", matching /cron/i) -- no real hit. Separately grepped `QTimer` usage in app.cpp and control_server.cpp directly: every instance is a kill-timer or event-loop timeout (app.cpp:74,95,139,148,179,183,250,255), not a task scheduler. No timer-driven task registry exists anywhere in product code.","o":"","r":"Wave 0 register-accuracy audit: held at absent. The exact synonym grep now returns spurious hits in session_rules.cpp because the new SessionMacro variable `macroName` (added since the last audit, for the login-macro feature covered by items #71-72/157-159) happens to contain the case-insensitive substring \"cron\" (m-a-c-r-o-N-ame). Verified by hand that none of those lines are scheduling-related -- they are macro-name plumbing around QtConcurrent::run. Read every QTimer use in app.cpp directly as a second check: all are shutdown/kill timers or synchronous-call timeouts, not a recurring-task mechanism. No scheduling surface exists in buildSnapshot or the endpoint dispatcher. Claim holds; flagging the grep false-positive so it isn't mistaken for a real hit in a future pass."},{"a":"platform","f":"Hotkeys (configurable keyboard shortcuts) and the command palette","s":"present","i":"high","e":"days","g":"A command palette (Ctrl/Cmd+K, or the title bar's ⌘K button) lists every tab plus a handful of cross-cutting toggles (intercept, intercept-responses, appearance/tweaks panel, copy CA cert path, and now \"Customize keyboard shortcuts…\" itself), fuzzy-filterable, arrow-key navigable, Enter to run. Ctrl/Cmd+1-9 jump directly to the first nine tabs, and every one of those 10 bindings (palette-open + the 9 tab jumps) is now user-remappable through a HotkeysOverlay rebind UI -- click a binding, press a new combo, a live conflict check warns if another action already owns it, per-row reset-to-default, persisted to localStorage (nl-hotkeys) and read back on load. Still honestly missing: there is no Ctrl+R send-to-repeater / Ctrl+Shift+R / Ctrl+O contextual shortcut set -- the palette and the rebind UI both only reach global navigation + a few app-level toggles, not per-row or per-tab contextual actions like \"send this history row to Repeater\", because the reducer has no generic contextual-dispatch surface to bind against yet.","w":"Added a rebindable-hotkeys layer on top of the existing CommandPalette: pure helpers (defaultHotkeys/comboFromEvent/comboLabel/loadHotkeys/saveHotkeys/matchHotkeyAction, ui-v2/app.jsx:5621-5680) turn a keydown event into a normalized \"mod[+shift][+alt]+key\" combo string and look it up against a persisted binding map instead of the old hardcoded if (k===\"k\") / /^[1-9]$/ checks; a new HotkeysOverlay component (app.jsx:5686-5773) lets the user click a binding, press a new combo, and see+resolve conflicts against every other current binding before it's saved. App()'s global keydown effect now dispatches via matchHotkeyAction(hotkeys, combo) and is suspended while the overlay itself is open (so recording a new combo there can't also fire the old one); the palette gained a \"Customize keyboard shortcuts…\" entry as the discovery path, and its own tab-row hints now render the live bound key via comboLabel() instead of a hardcoded \"Ctrl+N\" string. This closes the one gap #247 was explicitly left partial for last wave (\"bindings are fixed, not user-configurable\") -- upgraded partial -> present. Per-row/contextual hotkeys (Ctrl+R send-to-repeater etc.) remain a real, separate, honestly-undocumented-as-fixed gap: no code here invents a contextual-dispatch surface the reducer doesn't have.","v":"ui-v2/app.jsx:5621-5680 (HOTKEYS_STORAGE_KEY, defaultHotkeys, comboFromEvent, comboLabel, loadHotkeys, saveHotkeys, matchHotkeyAction), :5686-5773 (HotkeysOverlay component), App()'s hotkeys/hotkeysOpen state + the rewritten keydown effect and hotkeyActions/updateHotkey/resetHotkey (app.jsx ~5878-5951), paletteCommands' new \"customize-shortcuts\" entry and comboLabel-driven tab hints, and the {hotkeysOpen && <HotkeysOverlay .../>} render alongside the existing palette render.","o":"present","r":"Rebindable-hotkeys batch: the command palette's 10 global bindings (open-palette + Ctrl/Cmd+1-9 tab jumps) are now user-remappable via a new HotkeysOverlay, persisted to localStorage, with live conflict detection and per-row reset. Closes the configurability half of #247's gap (partial -> present); contextual per-row shortcuts stay the honest remainder, unrelated to this batch. No backend touched."},{"a":"platform","f":"Performance feedback / memory usage display / low-memory warnings and memory settings","s":"absent","i":"low","e":"days","g":"No visibility into memory or throughput and no warning before trouble. Being C++ this matters far less than for Burp's JVM, but the operator is still flying blind on a long engagement — and the row cap silently discards rows from the live model with no indication.","w":"Confirmed. Grepped for the platform-specific APIs a C++ app would actually use (GlobalMemoryStatus, getrusage, /proc/self/status) plus memoryUsage/memUsage — zero hits across all .cpp in Src. The only memory control is the blind row cap, which I verified is a hard-coded default with no feedback of any kind.","v":"`grep -rni \"GlobalMemoryStatus|memoryUsage|getrusage|/proc/self/status\" --include=*.cpp Src`: 0 hits. The one control: Src/App/app.cpp:639 `\"  --max-rows=N          ProxyModel in-memory window cap (default 10000)\\n\"` implemented as Src/FrontEnd/GUI/Models/Proxy/proxy_model.hpp:89 `int m_maxRows = 10'000; // window cap`, enforced silently at proxy_model.cpp:58-78 (`m_maxRows = std::max(100, n);` ... `while (static_cast<int>(m_entries.size()) > m_maxRows) {`).","o":"","r":"Wave 0 register-accuracy audit: held at absent. No platform memory-query API is used anywhere (0 hits, same as prior pass). The row-cap mechanism is unchanged in substance, only line numbers drifted (584 -> 639 for the flag help text; 78-82 -> 58-78 for the eviction loop, content identical). No memory/throughput visibility or low-memory warning exists anywhere. Claim holds."},{"a":"platform","f":"Clickbandit (clickjacking PoC generator) and Burp Infiltrator","s":"partial","i":"low","e":"hours","g":"A CLICKJACK POC button next to CSRF POC in Proxy history / Site map's DetailPane now generates a standalone HTML page (invisible iframe framing the row's URL over a decoy button, HTML-escaped) and offers it for download -- the actual PoC-generation half this item names. Still missing versus Burp's Clickbandit specifically: the interactive in-browser tool where you drag/resize the target's live rendered elements under the decoy overlay and it records your clicks as you place them; this is a static one-shot template instead. Infiltrator remains out of scope (deprecated in current Burp, not worth building, per prior audit).","w":"Closed 2026-08-26: added buildClickjackPoc() (ui-v2/proxy.jsx) reusing the same parseRawRequest()-derived fullUrl the existing COPY AS / CSRF POC machinery already builds, and a CLICKJACK POC button wired to the shared CodecOverlay (title/body/note/downloadName) -- the same pattern CSRF POC already uses, so no backend endpoint was needed (framing a URL client-side requires no server-side replay). Client-only, matching how COPY AS already generates curl/wget/etc without a round trip.","v":"ui-v2/proxy.jsx buildClickjackPoc() (escapes the URL into an <iframe src> under a positioned decoy <button>) and the CLICKJACK POC button in DetailPane calling parseRawRequest(row, req) for fullUrl then setOverlay({title, body, note, downloadName}) -- rendered by the existing CodecOverlay (proxy.jsx:2555). No backend change; Src/Core/Networking/request_export.cpp's csrfPoc() is untouched and unrelated.","o":"partial","r":"Clickjacking PoC generator wave: client-side CLICKJACK POC button (DetailPane, Proxy history / Site map) closes the PoC-generation gap this item names; Clickbandit's interactive drag-placement UX and Infiltrator remain out of scope, so state moves absent -> partial rather than -> present."},{"a":"platform","f":"Desktop application shell (a single native GUI hosting every tool)","s":"stub","i":"medium","e":"months","g":"There is effectively ONE front end (ui-v2 in the user's browser). The Qt GUI tree is scaffolding and its host window only loads from a source checkout. Browser-hosted UI means no native menus, no OS keyboard integration, no multi-window layout.","w":"Confirmed, with numbers I generated myself. `wc -l` over the GUI tree returns 8 for every one of the 23 .qml component files — 184 lines total for the entire advertised Qt front end. Only Src/App/app.qml has content (1211 lines), and I verified it is loaded from a RELATIVE source path, so the QML window only works when the binary is run from a source checkout — it cannot function in an installed o","v":"`wc -l Src/FrontEnd/GUI/*/*.qml Src/FrontEnd/GUI/*/Components/*.qml`: `8` for all 23 files, `184 total` (e.g. Src/FrontEnd/GUI/Workspace/workspace.qml, .../Proxy/proxy.qml, .../RepeaterHub/repeater_hub.qml). `wc -l Src/App/app.qml`: `1211`. Src/App/app.cpp:1485-1486 `// run from project root so this relative path resolves to Nullock/Src/App/app.qml` / `const QUrl url(QStringLiteral(\"./Src/App/app.qml\"));`.","o":"","r":"Wave 0 register-accuracy audit: held at stub. Re-ran the exact wc -l sweep: still 8 lines for all 23 scaffold .qml components (184 total, unchanged), still 1211 lines for the one real app.qml, still loaded from a relative source-checkout path (app.cpp, drifted 1159-1160 -> 1485-1486, content identical -- the binary still cannot locate its own QML window from an installed/packaged location). ui-v2 (the browser-hosted front end) remains the sole functional UI. Claim holds."},{"a":"proxy","f":"Proxy listener > Request handling > Support invisible proxying (non-proxy-aware clients)","s":"partial","i":"high","e":"days","g":"Invisible HTTPS (the actual use case) is impossible -- no TLS-first/SNI accept path. Cleartext invisible mode is undocumented, untoggleable, and, because the listener is hard-bound to 127.0.0.1, only reachable from the same host via a hosts-file redirect onto whatever --proxy-port was chosen.","w":"Re-read proxy_server.cpp run()/rewriteHostPort myself. The claim holds: the accept path unconditionally parses an HTTP request line, and the Host-header fallback makes cleartext invisible proxying work by accident. I confirmed no SNI peek exists (grep 'SNI' across Src returns only the cert_logic.hpp comment). I kept 'partial' rather than dropping to 'stub' because the plaintext path really does wo","v":"Src/BackEnd/Proxy/proxy_server.cpp:287-290 `void run() { ... if (!readRequest(req)) { fail(\"malformed request\"); return; }` -- a TLS ClientHello with no CONNECT fails readRequestFrom's `if (parts.size() < 3) return false;` (proxy_server.cpp:881). Host fallback confirmed in rewriteHostPort, proxy_server.cpp:244-264 (`const QString hostHeader = findHeader(req.headers, \"Host\");` used only when the target isn't already an absolute URL).","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-checked run()/readRequestFrom/rewriteHostPort line by line (drifted ~30 lines from the last audit, logic byte-identical) and re-ran `grep -rn SNI Src`: still only the two unrelated comment hits (cert_logic.hpp, tls_logic.cpp), no SNI-peek implementation anywhere. Invisible HTTPS (TLS-first accept with no CONNECT) is still impossible; cleartext invisible mode still works only by the same Host-header-fallback accident. No change."},{"a":"proxy","f":"Proxy listener > Certificate > Generate CA-signed per-host certificate (per-host leaf minting)","s":"present","i":"medium","e":"hours","g":"Leaf carries a single SAN (DNS:<host> for a normal hostname target, or IP:<addr> for an IPv4/IPv6 literal target via CertLogic::sanEntryForHost -- see item #286 for that IP-SAN work's own state). Burp clones the upstream cert's full subject/SAN set; Nullock does not, so a client pinning on issuer-independent fields (multi-SAN, OU, serial) still breaks -- multi-SAN/wildcard leaves and the live-handshake forged-leaf path are #286's tracked remainder. Whole path is gated on an external openssl binary (item 6).","w":"CertAuthority mints per-host RSA leaves signed by the local CA, with DNS/IP SANs, serverAuth usage, and explicit subject/authority key identifiers for OpenSSL and LibreSSL compatibility.","v":"Src/BackEnd/Proxy/cert_authority.cpp leaf extension configuration; cert_logic.cpp sanEntryForHost; scripts/runtime_regression.py packaged HTTPS transaction with strict certificate verification.","o":"present","r":"Declare leaf key identifiers explicitly so strict TLS clients accept LibreSSL-generated certificates. Runtime regression exercises real proxy HTTPS with strict validation enabled on every Python version."},{"a":"proxy","f":"CA certificate: leaf caching across restarts","s":"present","i":"medium","e":"hours","g":"Persisted leaves are checked against the current CA and private key after restart. Cache eviction, a clear-leaves control, live CA replacement, and automatic CA/key repair remain unavailable.","w":"Disk-cache reuse verifies parsing, common name, the requested DNS/IP subject alternative name, dates, authority key identifier, server-certificate trust against the current CA, and the private key public component. Stale, damaged or mismatched files are regenerated; valid files are reused and private-key permissions are reapplied.","v":"Src/BackEnd/Proxy/cert_authority.cpp cachedLeafMatchesCaAndKey and leafCertFor; scripts/runtime_regression.py strict HTTPS after restart for valid reuse, legacy leaves, mismatched/damaged keys, invalid signatures, wrong/missing subject alternative names and replaced CA.","o":"","r":"Verify the current CA, private key and requested DNS/IP subject alternative name before disk-cache reuse. Strict HTTPS regressions cover wrong and missing SANs; focused checks retain valid DNS, IPv4 and IPv6 leaves."},{"a":"proxy","f":"CA private key hardening on disk","s":"present","i":"low","e":"hours","g":"Restrictions cover CA and persisted leaf keys. They separate OS accounts; they do not isolate other programs running as the owning user. Unsupported filesystems or ACL failures produce warnings rather than preventing startup.","w":"The code applies owner-only POSIX permissions or a Windows ACL for the current user when creating and reusing CA and leaf keys. Call sites report failures. The older claims that leaf keys bypass hardening and failures are silent no longer match the source; a comparison-based exceeds grade is not retained.","v":"Src/BackEnd/Proxy/cert_authority.cpp lockdownPrivateKeyFile; ensureCa creation/reuse; leafCertFor creation/reuse; qWarning at every hardening call site.","o":"exceeds","r":"Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits. Grade changed from exceeds to present."},{"a":"proxy","f":"CA certificate: export in DER (http://burp/cert), export cert+key as PKCS#12, import a CA from PKCS#12, regenerate CA","s":"partial","i":"medium","e":"days","g":"DER export now ships: GET /ca.der (and Burp's /cert alias) serves the CA as application/pkix-cert, converting the PEM via the pure ControlLogic::pemCertToDer (no OpenSSL). Still partial for PKCS#12 export/import of cert+key (share one CA across a team / load Burp's CA) and CA regenerate (recovery from a compromised/expired CA is still delete-ca.pem/ca.key-by-hand-and-restart) -- both need OpenSSL pkcs12 + swapping the live CA/leaf cache.","w":"Re-ran the greps myself: `pkcs12|PKCS12|\\.pfx` returns ZERO hits across all of Src, ui-v2 and browser-ext. The /ca.pem handler is real and is the only export. Confirmed partial (PEM download exists and is UI-linked).","v":"Src/BackEnd/Control/control_server.cpp:1194 `} else if (path == \"/ca.pem\" || path == \"/ca.crt\") {` and :1220-1236 `} else if (path == \"/ca.der\" || path == \"/cert\") { ... hdr += \"Content-Disposition: attachment; filename=\\\"nullock-ca.der\\\"\\r\\n\";`. CertAuthority's whole public surface is still cert_authority.hpp:26-33 (`ensureCa`, `caCertPath`, `caDir`, `hasOpenssl`, `leafCertFor`) -- no import, no regenerate, no PKCS#12 anywhere.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-ran `grep -rn 'pkcs12|PKCS12|\\.pfx' Src ui-v2 browser-ext`: still zero hits repo-wide. /ca.pem and /ca.der (plus the /cert Burp-compat alias) are still the complete export surface; CertAuthority's public API is unchanged (ensureCa/leafCertFor only, no import/regenerate entry point). No change."},{"a":"proxy","f":"MITM CA works out of the box (bundled crypto)","s":"partial","i":"high","e":"weeks","g":"On a stock Windows box (no OpenSSL on PATH) HTTPS interception does nothing -- every host tunnels opaquely. The indicator is a small 'openssl ✗' chip; the intercept/history panes just look empty with no explanation. Burp requires no external tooling.","w":"Confirmed the external-openssl dependency and the hasOpenssl() gate on the CONNECT path. Two corrections to the evidence: (a) it is NOT silent -- bootInfo.hasOpenssl is surfaced in both front ends (ui-v2/tabs.jsx:19 'openssl ✗', ui-v2/app.jsx:488 'OpenSSL: missing'), so the user has a visible indicator, just not on the intercept path; (b) the '30s+ QProcess forks on first contact' figure is wrong ","v":"Src/BackEnd/Proxy/cert_authority.cpp:114-115 `QStringLiteral(\"C:/Program Files/OpenSSL-Win64/bin/openssl.exe\"), ...` -> hasOpenssl() gate at proxy_server.cpp:388 `if (inScope && sslClient && ca && ca->hasOpenssl() && !blocked) {`. Visible indicators: ui-v2/tabs.jsx:242 `{bootInfo.hasOpenssl ? \"openssl \\u2713\" : \"openssl \\u2717\"}`, ui-v2/app.jsx:995 `<Row label=\"OpenSSL\" value={b.hasOpenssl ? \"found\" : \"missing\"} />`.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Same external-openssl dependency, same hasOpenssl() gate on the CONNECT path, both UI indicators (tabs.jsx, app.jsx) still present and unchanged in behavior -- only line numbers drifted (tabs.jsx :19->:242, app.jsx :488->:995, cert_authority.cpp :102-114->:114-115, proxy_server.cpp :334->:388). On a stock box with no openssl on PATH, HTTPS interception is still silently a blind tunnel with only the small chip as an explanation. No change."},{"a":"proxy","f":"TLS pass through list (manual host/IP-range + port entries, 'Apply to out-of-scope items')","s":"partial","i":"medium","e":"hours","g":"No host:port or IP-range entries -- matching is still a plain QSet exact-string contains, so wildcards and CIDR ranges are unsupported -- and there is no 'apply to out-of-scope items' knob. Both are real backend-shaped gaps; add/delete/clear/view are now all reachable end to end.","w":"The 7c28cc9 wave (2026-08-18) closed pre-add (POST /api/mitm/block) and per-host delete (POST /api/mitm/unblock) at the backend/API level, but its own reconciled note already flagged the UI still had zero callers for either -- confirmed still true by a fresh grep at the start of this wave (only clearMitmBlocked() had a caller in ui-v2). Closed the remaining UI half: the Proxy card's MITM bypass row (SettingsTab, ui-v2/app.jsx) now renders each blocked host as a chip with a per-host × remove button (NL.actions.unblockMitmHost), plus a text input + Add button to pre-add a host (NL.actions.markMitmBlocked) -- both new thin wrappers in ui-v2/real-data.js posting to the pre-existing, already-backend-verified endpoints. Stays honestly partial: only the matching-scheme and out-of-scope-knob gaps remain, both backend changes this cloud session cannot build.","v":"ui-v2/app.jsx SettingsTab's MITM bypass row: each entry in mitmBlockedList renders `<span>{h}<button onClick={() => removeBypassHost(h)}>×<\/button><\/span>` calling `NL.actions.unblockMitmHost(h)`; a new host input + `Btn label=\"Add\" onClick={addBypassHost}` calling `NL.actions.markMitmBlocked(h)`. ui-v2/real-data.js: `markMitmBlocked(host) { return post(\"/api/mitm/block\", { host }).then(r => r.json()); }` and `unblockMitmHost(host) { return post(\"/api/mitm/unblock\", { host }).then(r => r.json()); }`, both matching the existing backend contract at control_server.cpp's `/api/mitm/block` and `/api/mitm/unblock` routes (unchanged, verified e2e in the 7c28cc9 wave).","o":"partial","r":"Closed the last UI gap on this item: the Proxy card (SettingsTab, ui-v2/app.jsx) now exposes per-host delete (× chip button -> NL.actions.unblockMitmHost) and pre-add (host input + Add button -> NL.actions.markMitmBlocked) for the TLS pass-through list, wired to the backend endpoints the 7c28cc9 wave already built and e2e-verified but which had no UI caller until now. No backend touched. Stays partial: exact-string-only matching (no host:port/IP-range/wildcard) and no 'apply to out-of-scope items' knob remain, both real backend gaps."},{"a":"proxy","f":"TLS pass through > Automatically add entries on client TLS negotiation failure","s":"present","i":"medium","e":"hours","g":"No on/off switch (Burp's is a checkbox) to disable auto-add entirely -- confirmed still absent (no such Q_INVOKABLE/flag exists). The two other gaps noted in an earlier pass no longer hold: the upstream-handshake trigger (proxy_server.cpp:541-555) now only blocklists on a genuine unreachable/timeout (`tlsErrors.isEmpty()`), NOT on a transient cert-rejection, so a one-off TLS error no longer causes a permanent demotion; and per-host removal now exists end-to-end -- `ProxyServer::clearMitmBlocked(host)` (proxy_server.hpp:195), the `/api/mitm/unblock` endpoint (control_server.cpp:6658-6664), and a per-row \"x\" button wired to `NL.actions.unblockMitmHost(h)` in the Proxy pane (ui-v2/app.jsx:843-850, `removeBypassHost` at :718-721).","w":"Both trigger sites verified verbatim, plus persistence via setBlocklistPath (wired in Src/App/app.cpp:671). The behaviour genuinely exists and survives restarts. Kept 'present' but filled the empty gap: the trigger is broader than Burp's (any upstream handshake failure inside a 3 s window, not just a client-side refusal) and there is no per-entry removal.","v":"Src/BackEnd/Proxy/proxy_server.cpp:470-476 (client path) `if (!waitEncrypted(sslClient, kReadTimeoutMs, m_server)) {\\n            // Client refused our forged cert -- usually cert pinning.\\n            m_server->markMitmBlocked(host);`; upstream twin at proxy_server.cpp:541-555, refined since the prior pass to gate on `if (tlsErrors.isEmpty()) m_server->markMitmBlocked(host);` -- a cert-level rejection (tlsErrors non-empty) is no longer blocklisted, only a genuine handshake timeout/unreachable is; `kHandshakeTimeoutMs = 3'000` at proxy_server.cpp:57. Persisted via `setBlocklistPath` (proxy_server.cpp:1485), wired in Src/App/app.cpp:740 `proxy.setBlocklistPath(certAuthority.caDir() + \"/mitm_blocked.txt\");`.","o":"","r":"Wave 0 register-accuracy audit: re-verified against live source. Found real drift -- two of the three gaps this item recorded have since been closed by other work (the upstream trigger was narrowed to exclude transient cert errors, and per-host unblock was wired end-to-end, backend + UI). Corrected the gap text to describe only what's actually still missing (a global on/off switch) and refreshed evidence line numbers. No state change -- still 'present', not upgraded to 'exceeds', since the remaining gap (no way to fully disable auto-add) is real."},{"a":"proxy","f":"Handling invalid upstream TLS certificates (Burp accepts by default so self-signed / expired lab targets stay testable)","s":"present","i":"high","e":"hours","g":"Backend allow-list/filter/persistence/visibility shipped in d95a390; the operator-facing gap named here since then -- 'no way to act on the diagnostics' -- is now closed: Settings' CA & TLS card has an Accept-invalid host chip-list (add/remove, backed by /api/proxy/accept-invalid-hosts/{add,remove}) plus a read-only table of exactly which certs were waived (host/sha256/ignored-errors/when), sourced from the same bootInfo fields the backend already published. Two named remainders stay open, both smaller and already called out in the backend reconciliation: a per-proxy-history-row 'this leg was unverified' annotation, and certificate-fingerprint pinning/TOFU (v1.1).","w":"Verified live: the backend wiring (project-scoped allow-list, benign-error filter, per-host unblock, persistence, bootInfo visibility) was already real per d95a390's own reconciliation, but grepping ui-v2/*.jsx + real-data.js for acceptInvalidHosts/accept-invalid-hosts/acceptedInvalidCerts returned nothing -- an operator had no way to add a host or see what was waived except curl. Added the missing UI leg only; no backend change.","v":"Src/BackEnd/Control/control_server.cpp:6373-6394 (POST /api/proxy/accept-invalid-hosts/{add,remove}, echoes acceptInvalidUpstreamHosts); control_server.cpp:1264-1275 (bootInfo.acceptInvalidUpstreamHosts + acceptedInvalidCerts with host/sha256/ignoredErrors/acceptedAt); ui-v2/real-data.js NL.actions.acceptInvalidHostAdd/Remove; ui-v2/app.jsx SettingsTab 'CA & TLS' card, Accept-invalid chip list + waived-certs table, mirroring the existing MITM-bypass chip-list pattern in the same card group.","o":"partial","r":"Added the operator-facing UI for the per-host accept-invalid-cert allow-list that d95a390 built backend-only: a chip-list (add/remove) in Settings' CA & TLS card wired to the existing POST /api/proxy/accept-invalid-hosts/{add,remove}, plus a read-only table rendering bootInfo.acceptedInvalidCerts (host, leaf sha256, which errors were waived, when) so an operator can audit exactly what verification was relaxed. No backend change. partial -> present (backend was already sound; the missing piece was purely that no UI could reach it)."},{"a":"proxy","f":"Settings > Network > TLS > Use custom protocols and ciphers","s":"partial","i":"low","e":"weeks","g":"Two hardcoded browser profiles selected by --tls-fingerprint only -- no UI, no free-form protocol/cipher list, and TLS 1.3 suites cannot be pinned at all (Qt 6 has no setCiphersuites). Not shaped at all on the SChannel backend.","w":"Verified apply() line by line. Two of the claims needed sharpening: on a non-OpenSSL backend it does not 'silently degrade' -- it qWarns and returns false (the contract is documented as 'true ONLY when actually shaped'); and a partial cipher resolution deliberately leaves Qt defaults rather than shipping a mangled list. Still partial: two canned profiles, launch-flag only, no user-facing picker.","v":"Src/Core/Networking/tls_profile.cpp:61-69 `const QStringList settable = settableCipherNames(full); const QList<QSslCipher> ciphers = resolveCiphers(settable); if (ciphers.size() != settable.size()) { qWarning() ... return false; }` then `cfg.setCiphers(ciphers); cfg.setProtocol(QSsl::TlsV1_2OrLater);`; SChannel branch at :79-84 `if (!backendIsOpenSsl()) { qWarning() << ... \"cipher ORDER is ignored, so the JA3 fingerprint is NOT shaped.\"; return false; }`. Still launch-flag only: Src/App/app.cpp:717-719 `const QString tlsFingerprint = flagValue(argc, argv, \"--tls-fingerprint\"); if (!tlsFingerprint.isEmpty()) { const auto p = Nullock::Core::TlsProfile::fromName(tlsFingerprint);` -- `grep -rn tlsFingerprint\\|TlsProfile ui-v2`: 0 hits, no UI picker.","o":"","r":"Wave 0 register-accuracy audit: held at partial. tls_profile.cpp is unchanged (same partial-resolution no-op-rather-than-mangle contract, same SChannel qWarning-and-return-false). Confirmed again there is no ui-v2 caller for TlsProfile/tlsFingerprint -- still --tls-fingerprint=chrome|firefox|none at process launch only, two canned profiles, no free-form protocol/cipher picker, no TLS 1.3 suite pinning (Qt 6 has no setCiphersuites()). No change."},{"a":"proxy","f":"Intercept client requests: hold, edit, forward, drop in flight","s":"present","i":"low","e":"hours","g":"Backpressure cap: Src/BackEnd/Proxy/intercept_logic.hpp:48 `kMaxPendingIntercepts = 256` -- past that, requests auto-forward uninterceptable (intercept.cpp:162-167). Burp queues without bound. Also no interception rules at all (Group B #10), so every held message must be resolved by hand.","w":"Verified the full chain: the worker really blocks on a QSemaphore, the operator's forward()/drop() releases it, the resolver returns the original bytes verbatim when unedited, and both front ends drive it (ui-v2 buttons and QML app.qml:864-868). Confirmed present. Filled the empty gap with a real limit I found in the code: a hard 256-message cap silently auto-forwards once the operator falls behin","v":"Src/BackEnd/Proxy/proxy_server.cpp:284-291 `if (auto *ic = m_server->interceptController(); ic && inScope) {\\n            const InterceptResult ir = ic->pend(outBytes, req.host, req.port, /*tls=*/false);\\n            if (ir.dropped) { m_client->disconnectFromHost(); return; }` ; block at Src/BackEnd/Proxy/intercept.cpp:221 `p->done.acquire();` ; resolve at intercept.cpp:44-62 forward()/64-78 drop(","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"proxy","f":"Intercept server responses: hold, edit, forward, drop before the client sees them","s":"present","i":"high","e":"hours","g":"Not hooked on the --h2-termination browser leg. Desktop QML front end has no response toggle at all (grep 'responsesEnabled' in Src/App/app.qml: zero hits) -- ui-v2/control-API only. serializeResponse also strips Transfer-Encoding and re-adds Content-Length (proxy_server.cpp:889-895), so what the operator edits is a re-framed response, not the wire bytes.","w":"Verified resolveResponseForClient and all three call sites (plaintext, h2-upstream bridge, h1 MITM keep-alive), plus the independent toggle. Confirmed the two stated gaps by my own greps: 'responsesEnabled|interceptResponses' has no hit in Src/App/app.qml, and the h2-termination leg's omission is documented in-code. Present stands.","v":"Src/BackEnd/Proxy/proxy_server.cpp:1023-1032 resolveResponseForClient(...) pends through interceptController() when responsesEnabled(); call sites at :365 (plaintext), :743 (h2-upstream bridge, browser leg stays h1), :836 (h1 MITM keep-alive). The h2-terminated browser leg (H2Terminator, browserIsH2 branch ~line 660) still intentionally skips response interception -- now documented in-code with an explicit comment block, matching this item's stated gap verbatim. grep for 'responsesEnabled|interceptResponses' in Src/App/app.qml: still zero hits.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"proxy","f":"Intercept message editor: Pretty / Raw / Hex / Params / Headers views + Inspector side panel","s":"partial","i":"high","e":"days","g":"Views expanded: HEADERS/BODY/PREVIEW(Pretty)/HEX/PARAMS joined the existing EDIT(Raw)/INSPECTOR toggle -- six of Burp's named views now present, one more than Repeater's own sibling item (#342, which never gained a Params view). Still genuinely missing: true binary-safe hex editing (the Hex view stays read-only, same concession the gap already called out: an edited binary body cannot be reassembled without corruption). The Params view itself has a real, honestly-scoped limit: it only edits URL query params, a form-urlencoded body, and the Cookie header -- a JSON/multipart/binary body has no key-value shape to show and is left params-invisible (same as Burp on a non-form body). Desktop QML editor (Src/App/app.qml) is unchanged -- still a bare TextArea, ui-v2-only capability, same asymmetry as every other Intercept/Repeater editor item.","w":"Narrowed 2026-08-22 (params wave): added the sixth view, PARAMS, closing the one gap explicitly named by the prior wave's own gap text. RepeaterParamsView (ui-v2/tabs.jsx) renders three editable key-value tables -- QUERY (from the request-line target's querystring), BODY (only when Content-Type is exactly application/x-www-form-urlencoded; hidden, not shown empty, otherwise -- editing a JSON/multipart body as flat key-value pairs would corrupt it), and COOKIE (from the Cookie header, split on ';') -- each row addable/removable/editable, only offered when current.kind !== 1 (a held REQUEST; Burp's Params view has no response analogue either). Every edit round-trips through the same repeaterSplitRaw/repeaterBuildRaw text machinery repeaterChangeMethod/repeaterChangeBodyEncoding already use, writing back into the one real 'edit' buffer that actually gets forwarded -- not a second, divergent state. Query and body pairs are url-decoded for display / url-encoded on write (matching those two existing functions' own convention for form pairs); Cookie pairs are deliberately NOT url-encoded, since real cookie tokens routinely carry raw base64 '+'/'/' characters that repeaterUrlDecode's '+' -> space rule would silently corrupt on a round-trip. Content-Length is recomputed on any body-params edit, same as every other Repeater/Intercept text-rewrite path. No backend change -- pure client-side text derivation/rewrite of the already-fetched held-message text, same architecture as the five sibling views.","v":"ui-v2/tabs.jsx: repeaterParams(raw) (parses queryParams/bodyParams/cookieParams via repeaterSplitRaw + repeaterParseFormPairs/repeaterParseCookiePairs, bodyParams=null unless Content-Type is form-urlencoded); repeaterRebuildParams(raw, {queryParams,bodyParams,cookieParams}) (rewrites target/body/Cookie header via repeaterBuildRaw, recomputes Content-Length); RepeaterParamsView/RepeaterParamRow (the editable table, add/remove/edit row handlers calling repeaterRebuildParams -> onChange(setEditedText)); InterceptTab's RepeaterEditorToolbar views=[\"edit\",\"params\",\"headers\",\"body\",\"preview\",\"hex\",\"inspector\"] for current.kind!==1, unchanged 6-view list (no params) for kind===1 responses; render branch editorView===\"params\" ? <RepeaterParamsView raw={editedText} onChange={setEditedText}/> alongside the existing edit/inspector/readonly branches.","o":"partial","r":"Intercept Params-view wave: partial -> partial, gap narrowed further (not a state flip -- binary-safe hex editing is still the one genuinely missing piece of the six-view set). Added an editable QUERY/BODY/COOKIE Params grid to the held-request editor, closing the prior wave's own explicitly-named remaining gap. No backend change."},{"a":"proxy","f":"Match and replace rules (8 sections; literal-or-regex; per-rule enable; ordered list)","s":"partial","i":"medium","e":"hours","g":"No 'request param name' / 'request param value' sections, and no literal match type (metacharacters must be hand-escaped). fixContentLength only rewrites an EXISTING header (proxy_server.cpp:1418-1425), so a body-rewriting rule on a chunked response leaves the framing wrong -- documented but unfixed.","w":"Verified the enum, both apply functions, the CRUD+move endpoints and the UI form (which is at ui-v2/app.jsx:722-900, not 533-700 as claimed -- the first pass's line numbers are shifted throughout). All stated gaps confirmed: no param-name/param-value sections, and `applyOne` always compiles the find string as a QRegularExpression, so there is no literal mode. Follow-up (2026-08-21): the /api/rules/move endpoint and its real-data.js wrapper ruleMove(from,to) existed with zero callers anywhere in ui-v2 -- rules could be added/removed/toggled from the GUI but never reordered, even though Burp's match/replace list supports drag-reordering. Added up/down buttons per row in RulesTab wired to the existing endpoint; no backend change. State stays partial: the two previously-identified real gaps (no request-param-name/value sections, chunked-response fixContentLength framing) are unaffected and remain open.","v":"Src/BackEnd/Proxy/proxy_server.hpp:75-82 `enum Section { ReqUrl = 0, ReqHeader = 1, ReqBody = 2, RespHeader = 3, RespBody = 4, RespStatus = 5, };` ; regex-only at proxy_server.cpp:1406-1412 `bool applyOne(QString &s, const MatchReplaceRule &r, const QRegularExpression &compiledFind) { ... s.replace(compiledFind, r.replace);` ; endpoints control_server.cpp:3050-3076; UI ui-v2/app.jsx:817-819 `<sele` (truncated in source) -- Rule reorder is now UI-reachable: ui-v2/app.jsx RulesTab row actions gained up/down buttons (boundary-disabled at first/last row) calling NL.actions.ruleMove(i,i-1)/(i,i+1) -> POST /api/rules/move -> ProjectStore::moveRule (project_store.cpp:581), a real, functional backend endpoint that previously had zero UI callers.","o":"partial","r":"Wired the pre-existing /api/rules/move endpoint (ProjectStore::moveRule) to the RulesTab UI via boundary-disabled up/down buttons per rule row -- previously present in the backend and real-data.js with zero UI callers, so rules could not be reordered from the GUI despite full CRUD support. State stays partial (param-name/value sections and chunked-response Content-Length framing remain the real, unaffected gaps)."},{"a":"proxy","f":"Match and replace: per-rule host scoping","s":"exceeds","i":"low","e":"hours","g":"","w":"Verified the field, the compile step, the per-rule enforcement AND the user-facing input -- the host glob is a first-class field in the rules form, so it is genuinely reachable, not internal-only. Burp has no per-rule host scoping. Exceeds confirmed.","v":"Src/BackEnd/Proxy/proxy_server.hpp:86 `QString     hostGlob;    // empty = all hosts; \"*.example.com\" style` ; compiled at proxy_server.cpp:1375-1385; enforced at proxy_server.cpp:1454 `if (!c.hostAll && !c.host.match(req.host).hasMatch()) continue;` ; whole-ruleset gate at :1447 `if (!isInScope(req.host)) return;` with the exfil rationale at :1438-1446. UI: ui-v2/app.jsx:812-814 `<input style={in","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"proxy","f":"HTTP history table with full column set (#, Host, Method, URL, Params, Edited, Status, Length, MIME, Extension, Title, Notes, TLS, IP, Cookies, Time, Listener port, response timing)","s":"partial","i":"medium","e":"days","g":"Missing Edited, Extension, Title, Notes, Cookies, Listener port. Time is dead (always em-dash) because nothing ever measures the round-trip. No column sorting in either front end; the desktop Proxy QML components are placeholder rectangles.","w":"Verified the column set, the model roles, the hardcoded elapsed, the absent sort handlers and the 8-line QML stubs. Confirmed exactly as claimed; `row[\"elapsed\"] = 0;` is at control_server.cpp:1435 and HttpResponse (proxy_server.hpp:46-63) carries no timing field, so the Time column can only ever render em-dash.","v":"ui-v2/proxy.jsx:421-432 `<th><\/th><th>#<\/th><th>Method<\/th><th>Status<\/th><th>Host<\/th><th>Path<\/th><th>Params<\/th><th>Mime<\/th><th>Size<\/th><th>Time<\/th><th>IP<\/th><th>Captured<\/th>` (no onClick anywhere on them); Src/BackEnd/Control/control_server.cpp:1564 `row[\"elapsed\"] = 0;` rendered by ui-v2/proxy.jsx:9 `function fmtMs(n) { if (!n) return \"\\u2014\"; return n + \" ms\"; }`. Desktop QML stub unchanged: Src/FrontEnd/GUI/Proxy/proxy.qml is still 8 lines, a bare placeholder Rectangle.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Column set, model roles, hardcoded `elapsed = 0`, absent sort handlers, and the 8-line QML stub are all byte-identical to the last audit (only line numbers drifted, control_server.cpp :1435->:1564). Still missing Edited/Extension/Title/Notes/Cookies/Listener port columns, still no sorting in either front end, Time column still permanently em-dash. No change."},{"a":"proxy","f":"HTTP history filter bar (in-scope only / hide items without responses / MIME / status / regex + negative + case-sensitive search / extension show-hide / annotation / listener)","s":"present","i":"high","e":"days","g":"Listener/port filter remains missing. Case sensitivity applies to local column/free-text matching; the server regex body-search path remains case-insensitive. Annotation filtering now uses project-persisted, cross-client notes.","w":"Closed 2026-08-10 (5c0c4b4): FilterBar/HistoryTable gain MIME-class/extension/case-sensitivity/negative-search dimensions. Register-accuracy update 2026-08-21: the annotation dimension named in this feature's own title was still marked missing here after c25af6a (2026-08-20) shipped it -- FilterBar now renders an ANNOTATED chip (ui-v2/proxy.jsx:332) and HistoryTable's filter predicate honors annotatedOnly (:114), closing that dimension client-side. Only listener/port remains a real gap. Updated 2026-09-11: 63ecda0e closes the browser-local annotation limitation with project storage and a revisioned read/patch API.","v":"ui-v2/proxy.jsx: MIME_CATEGORIES/mimeCategory() and pathExtension()/parseExtList()/extFilterMatch()/parseSearchTerm() helpers; HistoryTable's useMemo predicate applies mimeFilter/extList/extHide/caseSensitive/negate/annotatedOnly (:107-148); FilterBar renders the MIME select, EXT input+toggle, Aa case-sensitivity button, and ANNOTATED chip (:332); ProxyTab's `shown` count mirrors the same predicate so the header stays in sync.","o":"","r":"Annotation persistence caveat removed; unrelated filtering gaps remain documented."},{"a":"proxy","f":"HTTP history persistence + search at engagement scale","s":"present","i":"high","e":"days","g":"None left that this cloud session can close. A DB SEARCH overlay on the Proxy tab (ui-v2/proxy.jsx) wires /api/history/find directly: method/host/path (LIKE)/status/min-max size/since-minutes/limit filters, a results table, and an inline full-raw request/response view for the selected result via NL.requestRawById/responseRawById. A 2026-09-02 pass found and closed a narrower gap in the OTHER path to an evicted row: the main DetailPane's row selection (ui-v2/proxy.jsx `selectedRow = rows.find(...)`) had no cold-storage fallback of its own -- requestRawById/responseRawById's eviction-safe fetch only covered the raw request/response bytes, not the row metadata DetailPane gates rendering on, so a row selected before the in-memory window evicted it silently collapsed to \"select a row to inspect\" mid-session. Now closed via NL.historyFullById() wiring the previously-orphaned GET /api/history/full/<id> (control_server.cpp:4607) as that fallback.","w":"Closed this session (2026-08-13, DB Search wave): added DbSearchOverlay + the pure buildHistoryFindFilters helper to ui-v2/proxy.jsx, a DB SEARCH button next to WS REPEATER/H2 FRAME LOG in the HTTP HISTORY pane-head, and NL.actions.historyFind() in ui-v2/real-data.js posting to the existing, previously-orphaned /api/history/find. 2026-09-02 follow-up: the prior note's claim that \"DetailPane already used\" an eviction-safe cold-fetch path was only half true -- that covered raw bytes (requestRawById/responseRawById -> buildHistoryRow()'s SQLite fallback), not the row metadata (host/method/path/status/tls/...) DetailPane's `if (!row) return <placeholder>` gates on. Added NL.historyFullById(rowId) to ui-v2/real-data.js: a memoized sync-XHR accessor (same pattern as requestRawById/responseRawById) that GETs the previously-unwired /api/history/full/<id>, maps its JSON onto the same row shape NL.rows entries carry (id/method/host/port/path/url/status/size/tls/elapsed), and pre-seeds the raw-body cache from the same response. ui-v2/proxy.jsx's `selectedRow` computation now falls back to it when `rows.find` misses.","v":"ui-v2/proxy.jsx DbSearchOverlay + buildHistoryFindFilters, ProxyTab's DB SEARCH button; ui-v2/real-data.js NL.actions.historyFind; Src/BackEnd/Control/control_server.cpp:4072-4083 POST /api/history/find; Src/Core/Storage/history_logic.hpp/.cpp buildFindQuery (filter set); Src/Core/Storage/history_index.cpp:296-337 find() (returned row shape). 2026-09-02: ui-v2/real-data.js NL.historyFullById(); ui-v2/proxy.jsx `selectedRow` fallback (search \"NL.historyFullById\"); Src/BackEnd/Control/control_server.cpp:4601-4639 GET /api/history/full/<id> handler (its own comment names the evicted-row-still-selected case).","o":"present","r":"Follow-up: closed the metadata half of the eviction gap left over from the 2026-08-13 DB Search wave -- DetailPane's own selectedRow lookup (distinct from the DB Search overlay's self-contained flow) had no cold-storage fallback, so a row selected before eviction would silently drop out of view. Wired the previously-orphaned GET /api/history/full/<id> via a new NL.historyFullById() accessor. Verified: bundled-babel transform of ui-v2/proxy.jsx succeeds; Node functional test of the row-shape mapping (path->url mirroring, null-on-missing/error) and the rows.find-then-fallback selection logic (present row never triggers fallback, evicted id does, null selection short-circuits); backend read directly from source (control_server.cpp:4607-4639) to confirm the endpoint's field set and SQLite cold-storage fallback match what the frontend now consumes. No C++ build available in this cloud session -- backend code itself was not touched, only its consumption."},{"a":"proxy","f":"WebSockets history (separate tab, message direction, length, comment, filtering)","s":"partial","i":"medium","e":"days","g":"Captured only on the TLS MITM leg -- runWebSocketRelay is invoked solely from the h1 MITM keep-alive loop's 101 Upgrade branch (proxy_server.cpp), so a plaintext ws:// tunnel is never relayed or logged; Burp captures both. Connections are also grouped client-side by host:port only, since a history row carries no per-tunnel session id -- two concurrent WS tunnels to the same host:port interleave in one bucket in the new tab. Both are backend-shaped gaps outside what this frontend-only wave could close.","w":"Closed the frontend half of this item 2026-08-17: a dedicated WEBSOCKETS tab (ui-v2/app.jsx WebSocketsTab) reads the same NL.rows entries the Proxy tab already shows as pseudo-HTTP WS↑/WS↓ rows (no new backend call), groups them into a CONNECTIONS list keyed by host:port, and renders each message with real columns instead of the cosmetic Status/Mime pair: Direction (parsed from the WS↑/WS↓ method), Type/deflate/continued (parsed out of the synthetic path string \"(<opcode>[ deflate], <n> B[, continued])\" -- the only place proxy_server.cpp's emitMessage carries those flags), Length (the row's existing numeric size field, already accurate -- payload.size()), Time, and a per-message free-text Comment (localStorage-persisted client state, the same client-only pattern as Comparer/Decoder -- there is no backend field for a WS message comment). A DIRECTION (up/down) and TYPE (text/binary/close/ping/pong) filter bar sits above the message table. Selecting a message renders it through proxy.jsx's DetailPane -- the exact component the Proxy tab already renders these same rows through -- so Raw/Headers/Body/Hex/Inspector and every Send-to-Repeater/Intruder/Comparer/Decoder/Sequencer pivot work identically here. State stays partial, not present: the feature name promises parity with Burp's WebSockets history, and Burp captures plaintext ws:// traffic too -- Nullock's relay only ever ran on the TLS-MITM leg, a real capture-scope gap this frontend-only session cannot close (needs a plaintext-WS relay path in proxy_server.cpp, a C++ change this cloud session cannot build/verify).","v":"ui-v2/app.jsx WebSocketsTab (new component) + TABS entry `{id:\"websockets\", label:\"WEBSOCKETS\"}` + tab-render switch; WS_PATH_RE parses Src/BackEnd/Proxy/proxy_server.cpp:1086-1090 `req.path = QString(\"(%1%2, %3 B%4)\").arg(label).arg(deflate).arg(payload.size()).arg(continued)`; row.size already carries `resp->body.size()` per control_server.cpp:1440; DetailPane reused verbatim from ui-v2/proxy.jsx (same component ProxyTab mounts); capture-scope gap confirmed at the sole runWebSocketRelay call site, proxy_server.cpp's h1 MITM 101-Upgrade branch.","o":"","r":"WEBSOCKETS tab (ui-v2/app.jsx) closes the tab/direction/length/comment/filtering half of this item -- reused proxy.jsx's DetailPane for message detail + every Send-to- pivot, no backend touched. Left honestly partial: plaintext ws:// is never captured (TLS-MITM-only relay, a backend gap) and concurrent same-host:port tunnels interleave in one connection bucket (history rows carry no per-tunnel session id)."},{"a":"proxy","f":"WebSocket message injection into a live connection (Burp: WebSocket Repeater)","s":"present","i":"medium","e":"hours","g":"None -- ProxyTab (ui-v2/proxy.jsx) HTTP HISTORY pane-head gains a WS REPEATER button opening an overlay that polls GET /api/ws/sessions every 2s, offers direction (up/down) + opcode (text/binary/close/ping/pong) selectors and a payload editor, queues the frame via POST /api/ws/send, and offers a one-click resend-last. Frame history in the panel itself is still absent (each send is fire-and-forget against the live relay) -- that gap is tracked separately under #269 WebSockets history.","w":"Closed 2026-08-12: added NL.actions.wsSessions()/wsSend() (ui-v2/real-data.js) and a WsRepeaterOverlay component (ui-v2/proxy.jsx) wired to a toolbar button in the Proxy tab. Both response fields read by the overlay (sessions[].id/host/port/framesUp/framesDown and send response ok/queued) match control_server.cpp exactly -- verified by reading the handlers directly (GET /api/ws/sessions control_server.cpp:2009-2024, POST /api/ws/send :5689-5735) rather than trusting the prior audit note alone.","v":"ui-v2/proxy.jsx WsRepeaterOverlay + WS_OPCODES + wsRepeaterOpen toolbar button in ProxyTab; ui-v2/real-data.js NL.actions.wsSessions/wsSend; backend unchanged -- Src/BackEnd/Proxy/ws_repeater.hpp Q_INVOKABLE sendFrame; control_server.cpp:2009-2024 (/api/ws/sessions) and :5689-5735 (/api/ws/send).","o":"present","r":"WS Repeater wave: WebSocket message injection UI closes the GUI-reachability gap for /api/ws/send + /api/ws/sessions."},{"a":"proxy","f":"HTTP/1.1 keep-alive on the proxied connection","s":"partial","i":"medium","e":"hours","g":"Cleartext HTTP tears the connection down after every request regardless of Connection: keep-alive, and any pipelined follow-up bytes are dropped. Slow on HTTP-only targets and it changes the connection behaviour the origin observes -- which matters for smuggling/desync work. No 'use keep-alive if the server supports it' setting either way.","w":"Verified both legs. The MITM keep-alive loop and its close semantics (explicit Connection: close either side, HTTP/1.0 default-close with keep-alive opt-in) are correct. The plaintext leg really is one-request-per-connection with an unconditional disconnect. Partial confirmed.","v":"Plaintext leg, Src/BackEnd/Proxy/proxy_server.cpp:366-369 `if (ir.dropped) { m_client->disconnectFromHost(); return; } m_client->write(ir.bytes); waitWritten(m_client, kReadTimeoutMs, m_server); m_client->disconnectFromHost();` -- end of run(), no loop, one request per connection. MITM leg still loops with Connection: close handling (proxy_server.cpp:752-860 region).","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-read run()'s plaintext leg end-to-end: still an unconditional disconnectFromHost() after exactly one response, no keep-alive loop, no setting to opt in. The MITM leg's loop-and-honor-Connection-close semantics are unchanged. No change (evidence line numbers refreshed from :313-315 to :366-369)."},{"a":"proxy","f":"Miscellaneous proxy options (HTTP/1.0 downgrades, forced Connection: close, strip Proxy-*, normalise Accept-Encoding, strip Sec-WebSocket-Extensions, unpack compressed messages, don't log to history)","s":"partial","i":"low","e":"days","g":"Seven of nine absent: no HTTP/1.0 downgrade either direction, no forced Connection: close, no Accept-Encoding normalisation, no Sec-WebSocket-Extensions strip (so permessage-deflate cannot be turned off), no 'stop logging to history'. (The Proxy-Authorization-leak gap noted in the last audit is fixed: it is now stripped alongside Proxy-Connection, not forwarded upstream.)","w":"Verified both implemented items and re-grepped the rest myself across Src/BackEnd/Proxy: 'Sec-WebSocket-Extensions' and 'Accept-Encoding' still return zero hits in the proxy path. Confirmed 2-of-9. Correction from the last audit: the proxy-hop header strip is no longer Proxy-Connection-only -- serializeRequestForOrigin() now calls HttpLogic::isProxyHopRequestHeader(), which matches BOTH Proxy-Connection and Proxy-Authorization, so the credential-leak gap the last audit flagged no longer exists. This doesn't change the 2-of-9 count (strip-proxy-headers was already counted present) but the old evidence's claim that Proxy-Authorization leaks upstream is now false.","v":"Src/BackEnd/Proxy/proxy_logic.cpp:148-151 `bool isProxyHopRequestHeader(const QString &name) { return name.compare(QLatin1String(\"Proxy-Connection\"), Qt::CaseInsensitive) == 0 || name.compare(QLatin1String(\"Proxy-Authorization\"), Qt::CaseInsensitive) == 0; }`, called from Src/BackEnd/Proxy/proxy_server.cpp:1306 `if (HttpLogic::isProxyHopRequestHeader(h.first)) continue;` inside serializeRequestForOrigin(). Decode-for-inspection (the other present-of-9 item) at proxy_server.cpp:987 `const QByteArray dec = decodeContentEncoding(...)`. `grep -n 'Sec-WebSocket-Extensions\\|Accept-Encoding' Src/BackEnd/Proxy/proxy_server.cpp`: 0 hits.","o":"","r":"Wave 0 register-accuracy audit: held at partial (2-of-9), but with a real evidence correction, not just a line refresh. The last audit's evidence said 'the header strip really is only Proxy-Connection -- Proxy-Authorization is forwarded to the origin verbatim' and the gap text listed that as a leaked-credential gap. That is now false: serializeRequestForOrigin() (proxy_server.cpp:1299-1312) was refactored to call the new HttpLogic::isProxyHopRequestHeader() (proxy_logic.cpp:148-151), which strips both Proxy-Connection and Proxy-Authorization before forwarding to the origin. Re-verified Sec-WebSocket-Extensions/Accept-Encoding normalisation are still entirely absent from the proxy path (0 grep hits), so the 2-of-9 count is unchanged -- gap and why text corrected to drop the now-false leaked-credential claim."},{"a":"proxy","f":"'Don't send items to Proxy history or live tasks, if out of scope'","s":"present","i":"low","e":"hours","g":"None -- the ProxyServer bool, endpoint, and now the ui-v2 checkbox all exist. Scope tab's SCOPE pane-head carries a 'log out-of-scope traffic' checkbox (default OFF = Burp's default 'don't send' behavior) that toggles ProxyServer::m_logOutOfScope via POST /api/proxy/log-out-of-scope. When off, out-of-scope requests and responses are dropped from Proxy history AND live tasks (passive scan); when on, everything is kept. MITM tunnelling of out-of-scope HTTPS is unchanged, matching Burp.","w":"Closed 2026-08-20: the backend half (m_logOutOfScope + POST /api/proxy/log-out-of-scope {value} + bootInfo.logOutOfScope snapshot) shipped in 80f8ec9; this wave adds the missing GUI control -- a Scope-tab checkbox wired through a new log-out-of-scope-toggle reducer case and NL.actions.setLogOutOfScope. logIt = inScope || logOutOfScope() gates both requestReceived and responseReceived (proxy_server.cpp:292/335), and app.cpp fans responseReceived to both the history model and the passive scanner, so the single toggle controls history and live tasks together, exactly Burp's checkbox.","v":"Backend: proxy_server.cpp:292 `const bool logIt = inScope || m_server->logOutOfScope();` gating requestReceived (:293) and responseReceived (:335); control_server.cpp:3190-3198 POST /api/proxy/log-out-of-scope; control_server.cpp:1232 bootInfo[\"logOutOfScope\"]. UI: ui-v2/tabs.jsx ScopeTab SCOPE pane-head 'log out-of-scope traffic' checkbox -> dispatch{type:'log-out-of-scope-toggle'}; ui-v2/app.jsx log-out-of-scope-toggle reducer case + logOutOfScope state slice (initial from NL.bootInfo.logOutOfScope, nl-snapshot merge); ui-v2/real-data.js NL.actions.setLogOutOfScope -> POST /api/proxy/log-out-of-scope {value}.","o":"present","r":"partial -> present. The 80f8ec9 wave left this at partial ONLY because the ui-v2 checkbox was missing (all backend/API/snapshot plumbing was already done and e2e-verified 6/6). This wave adds that checkbox to the Scope tab: a 'log out-of-scope traffic' toggle (default OFF, matching Burp's default) bound to the existing POST /api/proxy/log-out-of-scope endpoint via a new reducer case + NL.actions.setLogOutOfScope, reading its initial/live state from bootInfo.logOutOfScope. No backend change. Verified: bundled-babel transform of app.jsx/tabs.jsx/real-data.js; NUL byte in tabs.jsx still exactly 1 occurrence; a 10-check Node functional test of the reducer toggle + snapshot-merge + init-coercion logic; a 12-check hook-stubbed vm render of ScopeTab across off/on/undefined states confirming the checkbox reflects the prop and its onChange dispatches log-out-of-scope-toggle."},{"a":"proxy","f":"HTTP/2 support to the server (ALPN h2 upstream, h2-to-h1 translation)","s":"present","i":"low","e":"weeks","g":"Only reachable inside a successful MITM tunnel, so it inherits the openssl dependency and the blocklist stickiness. Editing an intercepted request on this leg is honoured, but the response the operator sees is re-framed by serializeResponse rather than being upstream's wire bytes.","w":"Verified the ALPN offer, the negotiation check, the reject-unexpected-ALPN branch, the persistent-session bridge loop, and the header translation (pseudo-header order, hop-by-hop drop, Connection-named-field drop). This is a real, default-on, user-reachable path. Present confirmed.","v":"Src/BackEnd/Proxy/proxy_server.cpp:438-441 `upstreamCfg.setAllowedNextProtocols({\\n            QByteArrayLiteral(\"h2\"),\\n            QByteArrayLiteral(\"http/1.1\"),\\n        });` ; :489-495 negotiation + unexpected-ALPN bailout; bridge at :584-614 `if (upstreamIsH2) { m_server->noteH2Upstream(); H2Client h2; ... const auto h2res = h2.send(upstream, req);` ; translation Src/BackEnd/Proxy/h2_client_l","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"proxy","f":"HTTP/2 multiplexing to the server (concurrent streams on one connection)","s":"stub","i":"medium","e":"weeks","g":"Concurrent multiplexing is dead code from a user's perspective: no proxy path, no control endpoint, no test exercises it with N>1. Requests to an h2 origin are serialised, so h2-specific concurrency behaviour (stream interleaving, single-packet attacks, race conditions) cannot be observed or exercised.","w":"DOWNGRADED HARD -- this is the most expensive wrong 'present' in the set. sendConcurrent() is real and correctly implemented, but I grepped every caller in Src and Tests: the ONLY call in the entire repository passes a single-element list. The proxy never uses it; both proxy paths use send(), one request at a time. On the h1-browser leg the loop is strictly read-request/send/read-response; on the ","v":"Only caller: Src/BackEnd/Proxy/http2_client.cpp:494-495 `H2Client::Result H2Client::sendRequest(QSslSocket *sock, const HttpRequest &req) { const QList<Result> rs = sendConcurrent(sock, { req }); }` -- and sendRequest itself has no caller outside this file (`grep -rn sendRequest\\( Src Tests`: only the .hpp declaration). The proxy uses the sequential persistent-connection API instead: proxy_server.cpp:632 `const auto r = upstreamH2.send(upstream, req);` and :713 `const auto h2res = h2.send(upstream, req);`, both inside per-stream while loops that send one request at a time. `grep -rln sendConcurrent Tests/`: no hits, no test exercises N>1.","o":"","r":"Wave 0 register-accuracy audit: held at stub. Re-confirmed sendConcurrent()'s only caller (H2Client::sendRequest) is itself uncalled outside http2_client.cpp, and both live proxy paths (persistent-connection leg and per-tunnel leg) still use the sequential .send() API one request at a time. No test in Tests/ exercises sendConcurrent with N>1. The correctly-implemented concurrent-stream code remains entirely dead from a user's perspective. No change."},{"a":"proxy","f":"Proxy listener > HTTP > allow the CLIENT to use HTTP/2 (browser-to-proxy h2, on by default in Burp)","s":"partial","i":"medium","e":"weeks","g":"Off by default, so in the shipped configuration every browser is downgraded to HTTP/1.1 on the proxy leg -- hiding h2-specific origin behaviour. When enabled: request edits are silently discarded (only drop works), response interception is disabled on that leg, and upstream fan-out is sequential.","w":"Verified the flag, the gated ALPN offer, the terminator, and all three stated limitations (sequential upstream, drop-only request editing, no response interception) directly in the code and its comments. Partial confirmed.","v":"Src/BackEnd/Proxy/proxy_server.hpp:243-244 `void setH2Termination(bool on) { m_h2Termination = on; } bool h2Termination() const { return m_h2Termination; }`, default at :335 `bool m_h2Termination = false;   // --h2-termination (Phase 3, experimental)`; gate at proxy_server.cpp:465 `if (m_server->h2Termination())` before offering the h2 ALPN protocol; flag parsed at Src/App/app.cpp:744 `proxy.setH2Termination(hasFlag(argc, argv, \"--h2-termination\"));`.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Flag name, default-false, and the ALPN gate are all unchanged (only line numbers drifted). Still off by default, still launch-flag only with no UI toggle. Did not re-verify the three stated in-code limitations (drop-only request editing, no response interception, sequential upstream fan-out on that leg) beyond confirming the surrounding code is untouched since the last audit. No change."},{"a":"proxy","f":"HTTP/2 frame-level visibility (Burp has no frame log at all)","s":"present","i":"low","e":"days","g":"None on GUI reachability -- the Proxy tab's HTTP HISTORY pane-head gains an H2 FRAME LOG button (an overlay showing a per-stream summary table from GET /api/h2/streams and a live-tailing raw frame feed from GET /api/h2/events?since=<cursor>, polled every 2s while open). The remaining honest caveat: this is a passive viewer, not a filter/search tool -- no per-connection filtering, no frame-type filter, capped at the last 500 tailed frames client-side.","w":"Closed the GUI-reachability gap this wave: NL.actions.h2Streams()/h2Events(sinceMs) added to real-data.js, and a new H2FrameLogOverlay component in ui-v2/proxy.jsx renders the stream table (conn/streamId/method/path/status/bytesIn/bytesOut/framesIn/framesOut/closed) plus the frame feed (ts/conn/type/flags/streamId/bytes/errorCode), reusing the WS Repeater overlay's polling-modal pattern. Every field read matches control_server.cpp's actual JSON response for both handlers exactly -- no invented fields.","v":"ui-v2/real-data.js NL.actions.h2Streams/h2Events; ui-v2/proxy.jsx H2FrameLogOverlay + the H2 FRAME LOG button in the HTTP HISTORY pane-head; backend unchanged -- control_server.cpp:1961 GET /api/h2/streams, :1984 GET /api/h2/events?since=<ms>, both already allowlisted in isReadPath (:1669-1670).","o":"present","r":"Wave 2 (frontend-only): added the H2 Frame Log overlay to the Proxy tab, closing #277's GUI-reachability gap (state stays present -- the underlying capability was already present, only the UI affordance was missing). No backend touched."},{"a":"proxy","f":"Burp's built-in browser / one-click proxy + CA configuration for the client","s":"partial","i":"medium","e":"days","g":"No pre-configured browser instance; CA trust is still a manual per-OS step; the extension is Chromium-only and defaults to port 8080 regardless of --proxy-port. The PAC sends all RFC1918 traffic DIRECT, so internal targets silently never reach the proxy.","w":"Verified the PAC handler and the MV3 extension (manifest_version 3, 'proxy' permission, fixed_servers). Partial confirmed. I found an additional defect the first pass missed: the generated PAC returns DIRECT for every RFC1918 range, so an internal-engagement target on 10.x/192.168.x/172.16-31.x bypasses the proxy entirely.","v":"Src/BackEnd/Control/control_server.cpp:1856 `pac += \"        || shExpMatch(host, \\\"10.*\\\")\\n\";` ... :1864 `pac += \"    return \\\"PROXY 127.0.0.1:\\\" + QByteArray::number(pport) + \\\"\\\\\\\";\\\\n\\\";` -- the whole 172.16/12 and 192.168/16 and 10/8 ranges still return DIRECT before the PROXY fallback. Extension: browser-ext/background.js:19 `proxyPort: 8080,` (DEFAULTS), applied verbatim at :36-42 `await chrome.proxy.settings.set({ value: { mode: \"fixed_servers\", rules: { singleProxy: { scheme: \"http\", host: cfg.proxyHost, port: cfg.proxyPort } ...`. background.js:67 does read `j.bootInfo?.port` from a live /api/snapshot ping, but only to display it in the popup status -- it is never fed back into applyProxy()'s port, so a non-default --proxy-port still requires the user to manually edit and save the extension's port field.","o":"","r":"Wave 0 register-accuracy audit: held at partial. Re-checked the PAC generator: the RFC1918 DIRECT bypass for 10.*/192.168.*/172.16-31.* is unchanged (still means an internal-engagement target on those ranges silently never reaches the proxy). Re-checked background.js in full this pass (not just the applyProxy snippet the last audit quoted): it does now surface the live control-server's port via pingControl()'s j.bootInfo?.port for the popup's status display, but that value is read-only informational -- applyProxy() still sources its port from DEFAULTS/chrome.storage (8080 unless the user manually edits and saves it in the popup), so 'defaults to port 8080 regardless of --proxy-port' still holds in practice. No functional change to the gap; evidence expanded to cover this so a future pass doesn't mistake the informational readout for an auto-sync fix."},{"a":"proxy","f":"Proxy on/off toggle preserving the configured listener port","s":"present","i":"medium","e":"hours","g":"Toggling off/on from either UI silently rebinds to 8080 (or the next free port in the fallback list), which is not necessarily where the browser/PAC/extension is pointed. No UI for choosing the port at all -- launch flag only.","w":"Verified: the toggle endpoint calls the zero-argument start(), whose defaults are LocalHost:8080 -- the operator's --proxy-port is only applied at app.cpp:749-751 and is not remembered anywhere. Confirmed real, and confirmed the fallback port walk. Partial stands.","v":"Src/BackEnd/Control/control_server.cpp:2971-2975 `if (path == \"/api/proxy/toggle\") {\\n        if (m_wiring.proxy) {\\n            if (m_wiring.proxy->isRunning()) m_wiring.proxy->stop();\\n            else                             m_wiring.proxy->start();` against Src/BackEnd/Proxy/proxy_server.hpp:102-103 `Q_INVOKABLE bool start(const QHostAddress &address = QHostAddress::LocalHost,\\n           ","o":"partial","r":"partial -> present. The audit evidence is STALE: /api/proxy/toggle no longer calls the zero-arg start() -- it calls restart() (control_server.cpp:3139-3147), which re-listens on the remembered m_bindAddress + m_bindPort (proxy_server.cpp:1899-1943 stores the actually-bound port on every successful listen; restart() replays it). So a toggle preserves BOTH the off-loopback --proxy-bind and the custom --proxy-port instead of reverting to 127.0.0.1:8080; shipped in a6b57a0 ('toggle-safe'). VERIFIED e2e vs the live app: started on a distinctive custom --proxy-port (34759, outside the 8080/8081/8888/... fallback walk), toggled off (proxy stops), toggled on -> came back on the SAME 34759, never 8080 (5/5). The gap's second clause ('no UI for choosing the port') is a distinct capability tracked by the separate absent item 'Proxy listeners: multiple simultaneous listeners (add/edit/remove, per-listener ...)', not this toggle-behavior item; the port is configured today via --proxy-port. No code change this reconcile -- verification of already-shipped behavior."},{"a":"proxy","f":"Save/export proxy history items (Burp: 'Save items' XML; HAR import is extension-only)","s":"exceeds","i":"low","e":"hours","g":"No Burp-XML 'Save items' format for interop (HAR-only). The prior redact-only-via-API gap is now closed: the Export HAR button in Settings' Project card has an 'include unredacted auth material' checkbox that posts {redact:false}.","w":"Closed the redact-toggle gap this pass: real-data.js's exportHar() took no arguments, so the UI could never reach control_server.cpp's existing bodyJson.value(\"redact\") override -- confirmed by grep showing zero call sites passing an options object before this change. Now exportHar(opts) forwards opts to POST /api/har/export and Settings gained a bound checkbox. HAR round-trip import/export beyond Burp's extension-only HAR support remains exceeds; only the gap text changed to describe the still-real Burp-XML-format absence.","v":"Src/BackEnd/Control/control_server.cpp:6045-6053 /api/har/export honors bodyJson.value(\"redact\") to override the default-on ProjectStore::exportRedact; ui-v2/real-data.js:204 exportHar(opts) now forwards opts (was exportHar() with no params); ui-v2/app.jsx new harUnredacted state + checkbox next to the Export HAR button in SettingsTab's Project card wires it end to end.","o":"exceeds","r":"Wave 2: Export HAR redact toggle -- Settings' Export HAR button gains an 'include unredacted auth material' checkbox (harUnredacted state) that posts {redact:false} through a new exportHar(opts) parameter, closing the previously-named gap that the backend's existing redact override was UI-unreachable. State stays exceeds (native HAR round-trip already beat Burp's extension-only HAR support); only the gap text changed. No backend touched -- control_server.cpp already read bodyJson.value(\"redact\")."},{"a":"proxy","f":"Proxy listener: Bind to address (loopback only / all interfaces / specific local IP)","s":"present","i":"blocker","e":"hours","g":"None -- --proxy-bind=ADDR binds the proxy to loopback, all interfaces, or a specific IP (a non-loopback bind requires the explicit --proxy-bind-insecure acknowledgement, since it exposes a cert-forging MITM to the LAN). Phones, tablets, VMs and second machines can now be proxied.","w":"I re-grepped for every synonym I could think of (proxy-bind, proxy-listen, proxy-host, iface, interface, QHostAddress::Any, AnyIPv4, 0.0.0.0, allInterfaces) across Src, ui-v2, docs and README. The only Any-bind hits are the OAST/workspace standalone tools and the control server's --listen. The proxy is hardcoded to LocalHost at its single call site. Confirmed absent, and the blocker rating is righ","v":"Src/App/app.cpp:749-751 `const bool proxyStarted = (wantedProxyPort > 0)\\n        ? proxy.start(QHostAddress::LocalHost, wantedProxyPort)\\n        : proxy.start();` ; default also loopback (proxy_server.hpp:102). --listen applies only to the control API: Src/App/app.cpp:990-993 `if (listenArg == \"0.0.0.0\" || listenArg.compare(\"any\", Qt::CaseInsensitive) == 0)\\n            ctlAddr = QHostAddress::A","o":"present","r":"--proxy-bind=ADDR (or NULLOCK_PROXY_BIND) binds the proxy to loopback (default), all interfaces (0.0.0.0/::), or a specific IP. Because an off-loopback intercepting proxy is a LAN-exposed cert-forging MITM, a non-loopback bind is refused without the explicit --proxy-bind-insecure ack and prints a warning -- stricter than Burp's checkbox. ProxyServer::restart() remembers the bind so /api/proxy/toggle preserves it (also fixing a toggle that reset --proxy-port). Verified: netstat shows 0.0.0.0:PORT LISTENING with the ack, FATAL exit-1 without. Gauntlet 93/93 + 156/156."},{"a":"proxy","f":"Proxy listeners: multiple simultaneous listeners (add/edit/remove, per-listener config, running checkbox)","s":"absent","i":"medium","e":"days","g":"One listener, one port, one configuration. No per-listener request handling, no listener column in history, no way to run an invisible listener alongside a normal one.","w":"Confirmed by reading the class: one QTcpServer member, constructed once, one listen() call. My own grep for addListener/listenerPort/listeners across Src and ui-v2 found nothing but unrelated JS event listeners and the OAST tool's comment. Absent confirmed.","v":"Src/BackEnd/Proxy/proxy_server.hpp:325 `QTcpServer *m_server;` ; Src/BackEnd/Proxy/proxy_server.cpp:1315 `ProxyServer::ProxyServer(QObject *parent) : QObject(parent), m_server(new SslReadyTcpServer(this)) {` ; single bind loop at proxy_server.cpp:1940-1941 `for (quint16 p : tries) { if (m_server->listen(address, p)) {`.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Still exactly one QTcpServer member, constructed once, one bind loop that stops at the first port that succeeds. Re-ran `grep -rn addListener\\|listenerPort Src ui-v2`: no hits besides unrelated JS/comment noise. Absent confirmed (line numbers refreshed)."},{"a":"proxy","f":"Proxy listener > Request handling > Redirect to host / Redirect to port","s":"absent","i":"medium","e":"hours","g":"Cannot pin traffic at a specific backend host/port -- the standard technique for testing one node behind a load balancer, or pointing a hardcoded thick-client endpoint at a lab box.","w":"Re-grepped redirectHost/redirectTo/forceTls/forceSsl/forceHttps across Src, ui-v2 and browser-ext -- the only hits are the open-redirect SCANNER (Src/Core/Networking/open_redirect.*), which is unrelated vocabulary. The upstream destination is taken verbatim from the request with no override hook. Absent confirmed.","v":"Src/BackEnd/Proxy/proxy_server.cpp:314 `upstream.connectToHost(req.host, req.port);` with req.host/port set only by rewriteHostPort (proxy_server.cpp:244-264); CONNECT side parses the target the same way and passes it straight to runMitmTunnel/runBlindTunnel with no override hook anywhere.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-grepped redirectHost/redirectTo/forceTls/forceSsl/forceHttps across Src, ui-v2 and browser-ext -- the only hits are still the unrelated open-redirect SCANNER vocabulary. The upstream destination is still taken verbatim from the request with no override field, flag, or endpoint. No change."},{"a":"proxy","f":"Proxy listener > Request handling > Force use of TLS","s":"absent","i":"low","e":"hours","g":"HTTP-in / HTTPS-out rewriting is impossible, so you cannot strip TLS for a client that only speaks HTTP while still talking TLS to the origin.","w":"Confirmed: the cleartext path constructs a plain QTcpSocket with no conditional upgrade, and there is no flag/field/endpoint that would switch it. Same greps as the redirect item. Absent confirmed.","v":"Src/BackEnd/Proxy/proxy_server.cpp:313-317 `QTcpSocket upstream; upstream.connectToHost(req.host, req.port); if (!waitConnected(&upstream, kReadTimeoutMs, m_server)) {` -- a QTcpSocket, never a QSslSocket; the only QSslSocket upstream is inside runMitmTunnel (connectToHostEncrypted at :540).","o":"","r":"Wave 0 register-accuracy audit: held at absent. The cleartext path still constructs a plain QTcpSocket unconditionally; still no flag/field/endpoint that would switch it to TLS. Same greps as the redirect item, same zero hits. No change (evidence line numbers refreshed)."},{"a":"proxy","f":"Proxy listener > Certificate > Use a custom certificate (PKCS#12) / self-signed / CA-signed with specific hostname","s":"absent","i":"low","e":"days","g":"Cannot present a supplied certificate to the client -- needed when the target pins a cert you legitimately hold, or when a listener must present a corp-issued cert.","w":"Confirmed with my own grep: `pkcs12|PKCS12|\\.pfx` returns ZERO hits across the entire repository (Src, ui-v2, browser-ext). CertAuthority exposes exactly one minting entry point and the tunnel has exactly two outcomes (forged leaf or blind tunnel). Absent confirmed.","v":"Whole public API unchanged: Src/BackEnd/Proxy/cert_authority.hpp:26-33 `Q_INVOKABLE bool ensureCa(); ... LeafCert leafCertFor(const QString &host);` ; only consumer Src/BackEnd/Proxy/proxy_server.cpp:389-395 `leaf = ca->leafCertFor(host); ... if (leaf.valid()) { runMitmTunnel(...) } else { runBlindTunnel(...) }`.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-ran `grep -rn 'pkcs12|PKCS12|\\.pfx'` across the whole repo: still zero hits. CertAuthority still exposes exactly one minting entry point and the tunnel still has exactly two outcomes (forged leaf or blind tunnel). No supplied-certificate path exists. No change."},{"a":"proxy","f":"Per-host leaf certificates for IP-address and IPv6 targets (IP SANs)","s":"partial","i":"high","e":"hours","g":"IP SAN emission is now correct for BOTH families: sanEntryForHost returns IP:<addr> for an IPv4 literal (already) AND for an IPv6 literal (new strict isIpv6Literal), and isValidHostForCert now accepts a validated IPv6 (its ':' was previously rejected, so IPv6 targets never reached minting and fell through to a blind tunnel). Remaining for full parity: multi-SAN and wildcard-SAN leaves, and the live-handshake path (the forged-leaf CONNECT+MITM over a real socket, plus removing a single auto-added MITM-blocklist entry) -- socket-path work outside headless verification.","w":"isIpv6Literal is a strict, Qt6::Core-only textual validator (full/compressed/embedded-IPv4/'::' forms; rejects zone id, a second '::', empty/oversize/non-hex groups) mutation-proven in cert_logic_test, wired into sanEntryForHost (IP: SAN) and isValidHostForCert (accept), so an IPv6 target now mints a correct IP:<addr> leaf instead of being blind-tunnelled. The IPv4 half was already emitting IP: (this gap's 'DNS:192.168.1.10' claim was stale). Held partial for multi/wildcard SAN + the socket-level MITM handshake.","v":"Src/BackEnd/Proxy/cert_authority.cpp:246-250 `const QString contents = QStringLiteral(\\n            \"subjectAltName = %1\\n\" ...).arg(CertLogic::sanEntryForHost(host));` -- SAN type now dynamic. Src/BackEnd/Proxy/cert_logic.cpp:19-60 `bool isIpv6Literal(...)` (strict textual validator) and :62-66 `isValidHostForCert` accepts it (`if (isIpv6Literal(host)) return true;`); :98-101 `sanEntryForHost` returns `IP:<addr>` for either family.","o":"partial","r":"IPv6 half done, completing the IPv4 work from 81a0ba2. Added a strict, Qt6::Core-only CertLogic::isIpv6Literal (full/compressed/embedded-IPv4/'::' forms; rejects zone id, a second '::', empty/oversize/non-hex groups), wired into isValidHostForCert (accept) and sanEntryForHost (IP: SAN) -- an IPv6 https target now mints a correct iPAddress-SAN leaf instead of falling through to a blind tunnel. VERIFIED: cert_logic_test 68/68 incl. new IPv6/SAN cases + 2 mutations (dropping the IPv6 arm from sanEntryForHost; defeating the group-count check). Gauntlet ctest green per commit message. This run (2026-08-27) corrected the stale doc comments in cert_logic.hpp (isIpv4Literal's doc still described IPv6 as unimplemented; sanEntryForHost's doc didn't mention the IPv6 arm) and backfilled this item's own commit hash -- 983fca1 updated gap/why but left reconciled pointing at 81a0ba2 and audited_state at absent, both now corrected. REMAINDER (-> stays partial): multi-SAN and wildcard-SAN leaves, and the live-handshake path (forged-leaf CONNECT+MITM over a real socket) -- socket-path work outside headless verification."},{"a":"proxy","f":"Settings > Network > TLS > Client TLS certificates (per-host client certs, PKCS#12/JKS, mutual TLS)","s":"absent","i":"high","e":"days","g":"Nullock cannot present a client certificate to the origin. Any mutual-TLS target (banking back-office, gov, internal PKI-gated apps) is completely untestable through the proxy.","w":"Re-grepped clientCert/mutualTls/mTLS/pkcs12/setLocalCertificate across Src myself. The only setLocalCertificate is the server-side forged leaf presented TO the browser; the only mTLS string is a remediation blurb in finding_enricher.cpp. I read the full upstream QSslConfiguration block -- ALPN, verify mode, TLS profile, peerVerifyName, and no local certificate or key. Absent confirmed.","v":"Server-side only: Src/BackEnd/Proxy/proxy_server.cpp:459-460 `cfg.setLocalCertificate(cert); cfg.setPrivateKey(key);` (inside runMitmTunnel, applied to sslClient -- presenting Nullock's forged leaf TO the browser). Upstream config in full at proxy_server.cpp:491-511 -- setAllowedNextProtocols, setPeerVerifyMode, TlsProfile::apply, setPeerVerifyName -- and nothing else; no setLocalCertificate/setPrivateKey call on the upstream QSslConfiguration anywhere.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-grepped clientCert/mutualTls/mTLS/pkcs12/setLocalCertificate across Src: the only setLocalCertificate is still the server-side forged leaf presented to the browser; the only mTLS string is still the unrelated remediation blurb in finding_enricher.cpp. Re-read the full upstream QSslConfiguration block end to end -- still no local certificate/key set for the outbound connection. No change."},{"a":"proxy","f":"Upstream proxy servers (destination-scoped rules, basic/NTLM/digest auth)","s":"absent","i":"high","e":"days","g":"Cannot sit behind a corporate proxy or chain into another tool. On any engagement where egress is proxy-only, Nullock cannot reach anything.","w":"Re-grepped upstreamProxy/parentProxy/proxy chain/chained proxy/setProxy/QNetworkProxy/--upstream/HTTP_PROXY across Src. Zero relevant hits -- QNetworkProxy is never used anywhere, and the only HTTP_PROXY string is the UI's copy-paste helper telling the USER to set their own env var. Both outbound connects are direct. Absent confirmed.","v":"Direct connects only: Src/BackEnd/Proxy/proxy_server.cpp:314 `upstream.connectToHost(req.host, req.port);` and :540 `upstream->connectToHostEncrypted(host, port);`. `grep -rn QNetworkProxy Src`: 0 hits repo-wide. The only HTTP_PROXY string is still ui-v2/app.jsx's copy-paste helper telling the USER to set their own env var, not something Nullock itself reads.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-grepped upstreamProxy/parentProxy/chained proxy/setProxy/QNetworkProxy/--upstream/HTTP_PROXY across Src: same zero relevant hits as the last audit. Both outbound connects (plaintext and MITM-upstream) are still direct QTcpSocket/QSslSocket connects with no proxy-chaining hook. No change."},{"a":"proxy","f":"SOCKS proxy chaining (SOCKS4/5, 'Do DNS lookups over SOCKS proxy')","s":"absent","i":"high","e":"days","g":"No SOCKS at all -- no chaining through an SSH dynamic tunnel, no Tor, no pivot through a compromised host. That is how most internal testing is actually routed.","w":"I ran the grep myself over the whole repo (all extensions, excluding node_modules): `socks` returns ZERO hits. Nothing to upgrade. Absent confirmed.","v":"`grep -rniE 'socks' --include=*.cpp --include=*.hpp --include=*.jsx --include=*.qml --include=*.js --include=*.md .`: no output. Corroborated by the continued absence of QNetworkProxy anywhere in Src (QNetworkProxy::Socks5Proxy would be the Qt route).","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-ran the same repo-wide case-insensitive grep for 'socks': still zero hits. Nothing to upgrade. No change."},{"a":"proxy","f":"Intercept requests based on rules (match type, Matches/Does not match, AND/OR, per-rule enable)","s":"present","i":"blocker","e":"days","g":"None -- an And/Or rule list (match type + Matches/Does-not-match + per-rule enable) decides which requests are held; e.g. 'file extension does not match css,png,js' skips static assets. A RULES panel in the Intercept tab (ui-v2/tabs.jsx InterceptRulesPanel) now edits the list live -- add/edit/reorder/delete/toggle -- reading/writing the newly-added interceptRules snapshot field and POSTing the whole array to /api/intercept/rules, persisted per project.","w":"Confirmed by reading intercept.hpp end to end: the class has two atomics and a queue, no rule structure of any kind, and pend() is gated only by the global toggle plus the caller's inScope check. Endpoint list confirmed as toggle/responses-toggle/forward/drop/forwardAll only. Absent confirmed; blocker rating is right -- this is what makes interception tolerable in daily use.","v":"Src/BackEnd/Proxy/intercept.cpp:189-194 `InterceptResult InterceptController::pend(...) {\\n    // Worker-thread early-out: interception off -> pass the bytes straight\\n    // through ...\\n    if (m_enabled.loadAcquire() == 0) return { false, requestBytes };\\n    return pendImpl(requestBytes, host, port, tls, PendingRequest::Request);` ; entire member list intercept.hpp:136-141 (two QAtomicInt, m_c","o":"present","r":"GUI-reachability follow-up on c88e6bb: the rules engine/API/persistence shipped backend-only (\"Rules-editor UI pending\"). Added interceptRules to buildSnapshot() (control_server.cpp) so the poll loop carries the live rule list like sessionRules/rules already do, and a new InterceptRulesPanel component in ui-v2/tabs.jsx (RULES toggle button in InterceptTab's toolbar) lets an operator add/edit/reorder (up/down)/toggle/delete rules -- op (AND/OR), direction (request/response/both), match type (any/file-extension/method/url-regex/host-glob/content-type/status-code/has-header), negate, and condition -- against the exact InterceptLogic::interceptRulesToJson/FromJson wire contract, POSTing the whole array to /api/intercept/rules (NL.actions.interceptRulesSet) on every mutation, same whole-list-replace pattern as session handling rules. State stays present; this closes the GUI-reachability gap text only."},{"a":"proxy","f":"Intercept responses based on rules (content-type, status code, 'request was intercepted/modified', URL)","s":"partial","i":"high","e":"days","g":"Response rules now decide which responses are held (content-type / status code / URL / host / header, And/Or + negate), editable live from the same Intercept tab RULES panel via the dir=response/both rows. Remaining: the 'only intercept responses to requests I intercepted/modified' cross-reference match, which needs request/response correlation.","w":"Same verification as the request side -- pendResponse is gated only by m_enabledResponses; no rule type exists in intercept.hpp. Absent confirmed. I re-rated user_impact blocker -> high: response interception is opt-in and off by default, so an operator hits this only after deliberately enabling it, unlike the request side which is the primary workflow.","v":"Src/BackEnd/Proxy/intercept.cpp:197-201 `InterceptResult InterceptController::pendResponse(const QByteArray &responseBytes,\\n                                                  const QString &host, int port, bool tls) {\\n    if (m_enabledResponses.loadAcquire() == 0) return { false, responseBytes };\\n    return pendImpl(responseBytes, host, port, tls, PendingRequest::Response);` ; kinds are only Req","o":"partial","r":"Same InterceptRulesPanel wave as the request-side item above -- dir=response and dir=both rows in the same rule list gate response holds via InterceptController::pendResponse's existing interceptRulesHold() call. GUI-reachability gap closed; state stays partial (the request-was-intercepted cross-reference correlation is still unimplemented, unchanged from the prior audit)."},{"a":"proxy","f":"Intercept: 'Do intercept > Response to this request' (per-message opt-in)","s":"present","i":"medium","e":"hours","g":"None for the primary ui-v2 GUI: a per-message FORWARD, HOLD RESPONSE button in the Intercept tab opts just the current held request into response-holding, forwarding it while the RESPONSES toggle can stay off for everything else. The Qt desktop app.qml intercept pane has no equivalent control yet -- a separate, QML-only remainder not addressed here (not buildable/verifiable from this cloud session).","w":"The backend plumbing (forwardInterceptingResponse -> POST /api/intercept/forward-hold-response) was built and e2e-verified in the prior wave (f859d3a) but had zero ui-v2 caller -- the concurrent-agent-lane remainder that wave named explicitly. This wave adds the ui-v2 half: InterceptTab (ui-v2/tabs.jsx) gains a FORWARD, HOLD RESPONSE button next to DROP/FORWARD, shown only for held REQUESTS (current.kind !== 1), dispatching a new intercept-forward-hold-response reducer case (ui-v2/app.jsx) that calls NL.actions.interceptForwardHoldResponse(text) (ui-v2/real-data.js), posting the edited buffer to the existing endpoint and advancing the intercept queue exactly like plain FORWARD.","v":"ui-v2/tabs.jsx InterceptTab: the FORWARD, HOLD RESPONSE button (current.kind !== 1 guard) dispatching {type:\"intercept-forward-hold-response\", text: editedText}; ui-v2/app.jsx reducer case \"intercept-forward-hold-response\" calling act(\"interceptForwardHoldResponse\", ...) and slicing the queue; ui-v2/real-data.js interceptForwardHoldResponse(text) posting to /api/intercept/forward-hold-response (control_server.cpp:3259, body field \"text\" matching the server's bodyJson.value(\"text\") read).","o":"present","r":"GUI-reachability wave: added the per-message FORWARD, HOLD RESPONSE control to ui-v2 InterceptTab, closing the concurrent-agent-lane remainder the f859d3a backend wave named. No backend change -- pure frontend wiring of an already-built, already-verified endpoint. partial -> present for the ui-v2 GUI; the Qt desktop app.qml pane is untouched and still lacks the control (not buildable/verifiable from this cloud session, tracked separately if the desktop UI is ever audited on its own)."},{"a":"proxy","f":"'Automatically update Content-Length header when the request / response is edited' (on by default in Burp)","s":"partial","i":"high","e":"hours","g":"REQUEST side is fully closed (backend recompute + a Burp-default-ON 'Update Content-Length' checkbox in the ui-v2 Intercept tab, both wired to /api/intercept/autocl). RESPONSE side remains absent and is a deliberate, documented deferral: the intercept layer processing response bytes cannot see the paired request method, so it can't tell a legitimate zero-body HEAD/204/304 response apart from a truncated one, and recomputing blindly would corrupt the former -- Burp's own feature covers both directions, so this item stays short of it.","w":"Confirmed: the whole edit resolver is a compare-and-reencode with no header handling, and fixContentLength is called only from applyRequestRules/applyResponseRules, never from the intercept path. Note this is a DELIBERATE, documented choice (the header comment argues an operator must be able to emit a desynced request), not an oversight. I re-rated blocker -> high: the editor is raw text, so the o","v":"Src/BackEnd/Proxy/intercept_logic.cpp:5-18 `QByteArray resolveForwardBytes(const QByteArray &originalBytes, const QString &currentText) {\\n    if (currentText == QString::fromUtf8(originalBytes))\\n        return originalBytes;\\n    ...\\n    return currentText.toUtf8();\\n}` ; rationale at intercept_logic.hpp:33-36 `an EDITED forward whose Content-Length no longer matches the new body\\n// is left as","o":"partial","r":"ui-v2/tabs.jsx's InterceptTab toggle bar gains an UPDATE CONTENT-LENGTH checkbox (next to the existing REQUESTS/RESPONSES power toggles), bound to a new interceptAutoContentLength state slice (app.jsx: initial state, nl-snapshot merge from NL.interceptAutoContentLength, a new intercept-autocl-toggle reducer case) and a new NL.actions.interceptSetAutoContentLength (real-data.js) posting to the already-existing /api/intercept/autocl endpoint (control_server.cpp:3105, added by the 4369973 backend wave but never wired to any GUI control until now). Closes the GUI-reachability half of this item's own remaining ask for the REQUEST side; the response-side gap is unchanged and named honestly above, so state stays partial rather than claimed present. No backend touched."},{"a":"proxy","f":"'Automatically fix missing or superfluous new lines at end of request'","s":"present","i":"low","e":"hours","g":"None -- a hand-edited, bodyless request that dropped or duplicated its terminating blank line is repaired before forwarding, gated behind a Burp-default-ON 'FIX NEW LINES' toggle in the Intercept tab.","w":"Closed: InterceptLogic::fixTrailingNewline (Src/BackEnd/Proxy/intercept_logic.cpp) resolves the header/body boundary the same terminator-agnostic way as recomputeContentLength. Three cases: (1) no blank line anywhere -- the operator deleted the terminator that closes the headers -- append one, matching the message's own terminator style (CRLF/LF); (2) a blank line found with only stray terminator bytes after it and no declared body -- drop the superfluous trailing blank line(s); (3) anything else (a real body, or a body explicitly declared via Content-Length / Transfer-Encoding: chunked) -- left byte-for-byte untouched, so a deliberate desync probe still survives. Wired exactly like the existing 'Update Content-Length' toggle: a new autoFixNewlines Q_PROPERTY on InterceptController (default ON), shouldFixTrailingNewline gates it to edited REQUESTS only (never responses, drops, or a passive unedited forward), applied in pendImpl BEFORE the Content-Length recompute so CL is computed over the corrected framing. Persisted via ProjectStore's interceptAutoFixNewlines (same absent-key-means-ON contract as its CL sibling), surfaced in the boot snapshot, toggled from POST /api/intercept/autonl, and exposed as a 'FIX NEW LINES' checkbox next to 'UPDATE CONTENT-LENGTH' in the ui-v2 Intercept tab.","v":"Src/BackEnd/Proxy/intercept_logic.cpp fixTrailingNewline()/shouldFixTrailingNewline(); Src/BackEnd/Proxy/intercept.{hpp,cpp} autoFixNewlines Q_PROPERTY + pendImpl wiring (before recomputeContentLength); Src/Core/Storage/project_store.{hpp,cpp} interceptAutoFixNewlines persistence; Src/BackEnd/Control/control_server.cpp POST /api/intercept/autonl + boot snapshot field; ui-v2/tabs.jsx InterceptTab 'FIX NEW LINES' checkbox; ui-v2/real-data.js interceptSetAutoFixNewlines; Tests/intercept_logic/intercept_logic_test.cpp -- 13 new assertions (5-case gate + 8 fixTrailingNewline cases: missing blank line CRLF/LF/no-terminator-at-all, already-correct no-op, superfluous-blank-lines trim, real-body/declared-CL/declared-chunked preservation), all passing under a real local g++/Qt6Core build+run (93/93) -- this cloud session installed Qt6Core/Network/Sql headers and compiled+ran the actual test binary rather than relying on CI alone.","o":"present","r":"Intercept 'Fix missing/superfluous new lines' wave: added InterceptLogic::fixTrailingNewline + shouldFixTrailingNewline, wired through InterceptController/ProjectStore/control_server exactly like the existing 'Update Content-Length' toggle, and exposed as a Burp-default-ON checkbox in the ui-v2 Intercept tab. Absent -> present."},{"a":"proxy","f":"Intercept WebSocket messages (hold client-to-server / server-to-client, then edit or drop the frame)","s":"absent","i":"high","e":"days","g":"WebSocket messages are observable and injectable but never holdable. For an app whose protocol is entirely WS (chat, trading, collaborative editing, LLM streaming) you cannot tamper with a live message -- the core reason to proxy it.","w":"Confirmed by reading the relay: both readyRead handlers write the bytes to the peer socket BEFORE the parser is fed, so there is no point at which a frame could be held. InterceptController has only Request/Response kinds. Absent confirmed.","v":"Src/BackEnd/Proxy/proxy_server.cpp:1117-1124 `connect(client, &QTcpSocket::readyRead, this,\\n            [client, upstream, clientParser, ...] {\\n                const QByteArray bytes = client->readAll();\\n                upstream->write(bytes);\\n                for (const WsFrame &f : clientParser->feed(bytes)) {` -- write first, parse second; mirror at :1126-1134. Kinds: intercept.hpp:44 `enum ","o":"","r":"FOUNDATION + vetted design shipped; state stays ABSENT (no operator hold capability yet). A 3-engineer + synthesis design review produced a GO, implementation-ready v1 with a structurally-safe boundary: HOLD only UNCOMPRESSED text/binary MESSAGES (rsv1/2/3=0), pass CONTROL frames (ping/pong/close) + COMPRESSED (rsv1) + rsv2/3 through VERBATIM. That boundary makes permessage-deflate window desync IMPOSSIBLE rather than merely guarded -- an rsv1=0 message never touches the per-direction LZ77 sliding window, so editing/dropping/auto-forwarding it is provably orthogonal to deflate state (editing a context-takeover COMPRESSED message would silently oblige re-deflating EVERY later message, so that is a documented v1.5/v2 remainder behind a per-connection VERIFIED no_context_takeover handshake). Full design: invert the relay from forward-then-observe to PARSE-THEN-GATE, buffer un-forwarded frames in a per-direction FIFO inside the relay's own event loop (no new threads, no blocking), resolve by a process-global holdId via the existing frameQueued-style queued bridge, with disarm-flush + shutdown-flush + a leaky-bucket cap for deadlock/walk-away safety; a SEPARATE WsInterceptController (the HTTP blocking-worker model can't drive the async duplex relay) reusing the intercept toggle-pair + InterceptRule schema; /api/ws/intercept/* + wsIntercepted[] snapshot + project.json persistence; 7-step build order. STEP 1 IS DONE + mutation-proven (this commit): the pure shared serializer wsEncodeFrame(opcode,fin,rsv1,payload,mask) (FIN/RSV1 bits, minimal 7/16/64-bit length form, fresh-CSPRNG client->server masking) + wsHoldEligible predicate, in Src/BackEnd/Proxy/ws_encode.cpp (Qt6::Core-only), with WsRepeater::buildFrame now delegating to it (dedup, byte-equivalent -- injection regression green). ws_encode_test 26/26 + 2 mutations (16-bit length boundary; text/binary eligibility). Gauntlet ctest + probe_smoke green. REMAINDER (why still absent): the relay parse-then-gate inversion (step 2), the per-direction gate state machine (step 3), WsInterceptController + queued bridge (step 4), /api/ws/intercept/* + snapshot + persistence (step 5), the GUI WS tab (step 6), and the real-WS-client e2e (step 7) -- plus compressed-message hold behind the verified no_context_takeover renegotiation."},{"a":"proxy","f":"Intercept: Action menu (send held message to Repeater / Intruder / Comparer / Decoder / Scanner)","s":"present","i":"low","e":"hours","g":"None -- all five pivots named in the original gap are wired: Repeater/Intruder/Comparer (send-to-repeater-raw/send-to-intruder-raw/comparer-add), Decoder (send-to-decoder, a prior wave that never flipped this item), and Scanner (a new SCAN button on a held request parses the raw request line for its target -- Intercept carries no captured `url` field, only host/port/tls/text -- and POSTs the reconstructed url/method/headers/body to the existing /api/audit/run, the same active-test battery the SCANS tab's Assess & audit section drives; findings file into Issues as usual, and an inline result strip reports the finding/tester counts or the error).","w":"This wave added the Scanner pivot: sendToScanner() in InterceptTab reuses proxy.jsx's parseRawRequest() -- extended with a fallback so it can derive the request-line target when no captured row.url is available (previously every caller had one) -- to turn the held request text into {method, fullUrl, headers, body}, then calls NL.actions.auditRun(url, opts) (already used by the SCANS tab's Audit form, unmodified). Also discovered while implementing this that Send to Decoder had already shipped in an earlier wave (df50bbc, 2026-08-12) but this item was never flipped -- the register was stale by two of its five gaps, not just one.","v":"ui-v2/tabs.jsx InterceptTab: sendToScanner()/SCAN button (kind!==1 only) + scanRes result strip; ui-v2/proxy.jsx parseRawRequest() row.url fallback; ui-v2/real-data.js NL.actions.auditRun (unchanged, already wired to POST /api/audit/run); control_server.cpp:6760-6797 /api/audit/run handler (url/method/body/headers/include request shape, {ok,target,totalFindings,testers} response shape) matches every field read/sent.","o":"present","r":"Intercept Scan pivot batch: added Send to Scanner (parses the held request's raw request-line target via a parseRawRequest fallback, POSTs to /api/audit/run), and corrected the register for Send to Decoder (already shipped, never flipped) -- all five action-menu destinations now present."},{"a":"proxy","f":"WebSocket match and replace rules","s":"absent","i":"low","e":"days","g":"No automated rewriting of WebSocket traffic at all.","w":"Confirmed: MatchReplaceRule::Section has no WS member, and I traced every applyRequestRules/applyResponseRules call site -- all are on HTTP paths. The WS relay writes frame bytes through untouched. Absent confirmed.","v":"Sections enumerated at Src/BackEnd/Proxy/proxy_server.hpp:80-87 (ReqUrl/ReqHeader/ReqBody/RespHeader/RespBody/RespStatus) -- no WS member. Relay passthrough at proxy_server.cpp:1233 and :1242 `const QByteArray bytes = client->readAll(); ... upstream->write(bytes);` (and the reverse direction) -- raw frame bytes forwarded untouched. Rule call sites: proxy_server.cpp:311, 343, 624, 656, 701, 735, 785, 813 -- every one on an HTTP request/response path, none inside runWebSocketRelay.","o":"","r":"Wave 0 register-accuracy audit: held at absent. MatchReplaceRule::Section still has no WS variant; traced every applyRequestRules/applyResponseRules call site again (8 call sites, up from the last audit's list due to the H2 tunnel legs, all still HTTP paths) and runWebSocketRelay still just shuttles readAll()/write() bytes in both directions with no rule application. No change."},{"a":"proxy","f":"Response modification options (unhide hidden fields, enable disabled fields, remove length limits, remove JS validation, remove all JS, remove <object>, HTTPS->HTTP links, strip Secure flag)","s":"present","i":"low","e":"days","g":"None. All eight of Burp's one-click removals are reachable per held response, and a standing auto-apply toggle set (persisted to localStorage) now applies the enabled ones automatically to every future held response the instant it is captured -- matching Burp's Options-tab checkboxes, not just a manual per-message action.","w":"Added a RESP_MODS table + applyEnabledRespMods (ui-v2/tabs.jsx) driving a persisted settings row (\"response mods . auto-apply on hold:\") rendered unconditionally in InterceptTab, independent of whether a message is currently held. The held-item reset effect now runs applyEnabledRespMods against the settings captured at hold-time (via a ref, so toggling settings mid-edit of an already-held item does not clobber the user's in-progress edit) before the response text is shown for review, so every future held response gets the enabled transforms baked in without a click. The 8 manual per-message buttons stay for a one-off tweak of the currently-held item. No backend touched. present, not exceeds: this remains a client-side edit-before-forward, not a body-rewrite engine.","v":"ui-v2/tabs.jsx:856-905 (8 resp* helper functions, RESP_MODS table at :887, applyEnabledRespMods at :897, loadRespModSettings/saveRespModSettings persisting to localStorage key nl-intercept-respmods), the unconditional \"response mods . auto-apply on hold:\" checkbox row rendered under the icp-toggle bar, and the current.id-keyed reset effect that runs applyEnabledRespMods(current.text, respModSettingsRef.current) for kind===1 (response) matching control_server.cpp:1461-1476's kind field (0=request,1=response).","o":"present","r":"Intercept response-mods wave: RESP_MODS/applyEnabledRespMods + a persisted auto-apply toggle row closes the standing-setting gap (partial -> present)."},{"a":"proxy","f":"HTTP history annotations: per-item highlight colours and comments, plus filter-by-annotation","s":"present","i":"medium","e":"days","g":"None for this history/Site map workflow. Other message tables and global report formats remain outside this item; see the platform annotation item.","w":"Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action.","v":"Src/Core/Storage/project_store.cpp (historyAnnotations, annotateHistory, HAR import/export); Src/BackEnd/Control/control_server.cpp (/api/history/annotations, /api/history/annotation); ui-v2/real-data.js and proxy.jsx; bin/nullock; scripts/annotations_regression.py; Tests/ui/annotations_data_test.cjs and annotations_browser_test.cjs.","o":"partial","r":"Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action."},{"a":"proxy","f":"Proxying plaintext ws:// WebSocket connections","s":"present","i":"medium","e":"hours","g":"A ws:// handshake over plain HTTP is answered with a re-framed 101 and the socket is then closed. Plaintext WebSocket traffic is not relayed, not logged and not repeatable -- broken, not merely unsupported.","w":"Confirmed by tracing the plaintext leg end to end. The 101 branch exists only inside the MITM keep-alive loop. On the cleartext path a 101 is read (readResponse special-cases it and hands back the post-header bytes as the body), then passed to resolveResponseForClient -> serializeResponse, which strips Transfer-Encoding and appends a Content-Length -- and then the socket is closed. The handshake i","v":"Only 101 handler: Src/BackEnd/Proxy/proxy_server.cpp:719-727 `if (resp.statusCode == 101) {\\n                sslClient->write(serializeUpgradeResponse(resp));` (inside runMitmTunnel). Plaintext path: readResponse's 101 early-return at proxy_server.cpp:833-836, then run() at :310-315 goes through `serializeResponse` (which at :890-895 skips Transfer-Encoding and adds `Content-Length`) and ends with","o":"absent","r":"CLOSED. The plain-HTTP response path now mirrors the MITM path's 101 handling: on a 101 Switching Protocols carrying Upgrade: websocket it writes serializeUpgradeResponse(resp) -- which already appends the buffered post-101 frame tail (so a server-that-sends-first frame is not dropped) -- and hands the socket pair to runWebSocketRelay instead of the normal serializeResponse -> close path. runWebSocketRelay is transport-agnostic (plain QTcpSocket*), and it registers the session with WsRepeater + notes every frame exactly as the wss:// path does, so plaintext ws:// is now RELAYED, LOGGED (WebSocket history) and REPEATABLE -- all three things the audit found broken. A non-websocket 101 still takes the normal response path. VERIFIED e2e with a raw WS echo server + a raw client connecting THROUGH the proxy (real RFC 6455 handshake): the proxy relays the 101, Sec-WebSocket-Accept passes through intact, and a masked text frame round-trips via the echo (3/3). Gauntlet ctest 99/99 + probe 156. This reaches PARITY with the (present) wss:// path through the same relay; note WS-message INTERCEPTION (hold/edit/drop) is a separate roadmap item still in progress for both transports."},{"a":"repeater","f":"Repeater: multiple concurrent request tabs","s":"partial","i":"medium","e":"days","g":"The GUI/control Repeater runs one request at a time on a worker, preserving UI responsiveness and edits made during a send. Busy/Stop states are exposed; Stop prevents subsequent redirects after the current response. Browser mutations are serialized and stale polls cannot overwrite pending edits. Tabs autosave per project. Independent concurrent sends across multiple tabs remain unavailable.","w":"The GUI/control Repeater runs one request at a time on a worker, preserving UI responsiveness and edits made during a send. Busy/Stop states are exposed; Stop prevents subsequent redirects after the current response. Browser mutations are serialized and stale polls cannot overwrite pending edits. Tabs autosave per project. Independent concurrent sends across multiple tabs remain unavailable.","v":"Src/Core/Networking/repeater.cpp sendAsync; ui-v2/real-data.js writeRepeater; scripts/control_responsiveness_regression.py; Tests/ui/repeater_data_test.cjs","o":"","r":"The GUI/control Repeater runs one request at a time on a worker, preserving UI responsiveness and edits made during a send. Busy/Stop states are exposed; Stop prevents subsequent redirects after the current response. Browser mutations are serialized and stale polls cannot overwrite pending edits. Tabs autosave per project. Independent concurrent sends across multiple tabs remain unavailable."},{"a":"repeater","f":"Repeater: tab renaming (double-click) and auto-naming","s":"present","i":"cosmetic","e":"hours","g":"Rename is now inline (double-click the tab, edit in place, Enter/blur to commit, Escape to cancel) instead of a prompt() dialog, and each tab gets a click-to-cycle colour dot from a fixed 6-colour palette. The colour label is client-only cosmetic state (no `color` field exists in the repeater-tab wire contract, which is index-addressed with no stable id) -- it does not persist across a page reload or travel with project save/load, unlike name/notes. Auto-naming from the request line still applies only on addTabFromHistory/loadFromHistory, unchanged by this batch -- a plain addTab still gets 'tab N'.","w":"Closed 2026-08-09 (attack-type wiring, unrelated) then hardened 2026-08-18: RepeaterTab's onDoubleClick now opens an inline <input> (renameIdx/renameVal state, commit on blur/Enter, cancel on Escape) instead of prompt(), and a small colour dot next to each tab name cycles through TAB_COLOR_PALETTE on click (tabColors state, index-keyed).","v":"ui-v2/tabs.jsx TAB_COLOR_PALETTE + RepeaterTab's startRename/commitRename/onRenameKeyDown/cycleTabColor (tab strip render, double-click -> inline <input>; dot span -> cycleTabColor); repeaterTabRename POST still the only backend call, unchanged (control_server.cpp's /api/repeater/tab/rename).","o":"present","r":"Repeater-area polish batch: inline tab rename (was prompt()) + client-only colour labels, closing the two named gaps; auto-naming quirk left untouched, honestly."},{"a":"repeater","f":"Repeater: send a captured message to Repeater from other tools","s":"partial","i":"high","e":"days","g":"History loading preserves full request bytes, including binary bodies and bodies beyond the former preview limit. Browser and CLI use stable history IDs. Dedicated pivots from every tool, including Intruder result rows and Comparer, are not implemented.","w":"The history-ID endpoint reads the actual request from memory or the history index and serializes it without preview truncation. The CLI now calls that endpoint and rejects missing or invalid IDs. Browser history, the shared site-map detail pane and Intercept expose Repeater entry points. File and stdin loading now send base64 to the same reversible byte mapping, preserving NULs, invalid UTF-8 and trailing newlines.","v":"Src/BackEnd/Control/control_server.cpp /api/repeater/tab/addFromHistoryId; Src/Core/Networking/repeater.cpp setRequestBytes/addTabFromHistoryById; ui-v2/app.jsx send-to-repeater and send-to-repeater-raw; bin/nullock cmd_repeater; scripts/repeater_cli_runtime.py; scripts/runtime_regression.py binary history checks. /api/repeater/set requestBase64; CLI file/stdin runtime tests with 76,804-byte bodies.","o":"","r":"CLI file and stdin input preserve raw body bytes. Empty input clears the draft, omitted input preserves it, and invalid base64 is rejected before mutation. Existing missing tool pivots keep the grade partial."},{"a":"repeater","f":"Repeater: Host header and target stay in sync when you edit either","s":"present","i":"high","e":"hours","g":"None for the load-bearing direction. Changing the target now rewrites the request's Host header to match; a deliberate Host desync (host-header-injection testing) is preserved. Editing the raw Host header is intentionally NOT propagated back to the connection target (doing so would break injection testing).","w":"Closed 2026-08-10 (fef9cc4): Repeater::setHost calls NetworkingLogic::rewriteHostHeader so the Host line follows the target unless the user aimed it elsewhere. Mutation-proven pure test lock; full gauntlet green.","v":"Src/Core/Networking/networking_logic.cpp rewriteHostHeader (match-guarded, :port + LF/CRLF preserving); repeater.cpp setHost wires it + emits requestTextChanged; Tests/networking/networking_logic_test.cpp 8 cases, inverted-guard mutant fails exactly the 5 discriminating ones.","o":"partial","r":"Target host change now syncs the request Host header (desync-preserving)."},{"a":"repeater","f":"Repeater: response metadata display (status, byte length, elapsed milliseconds)","s":"present","i":"high","e":"hours","g":"None. STATUS, byte length and elapsed ms all render in the Repeater toolbar (tabs.jsx), sourced from the same snapshot fields the backend has served since 8bb4d7d; the history-nav tooltip carries the same two fields per navigated entry.","w":"Confirmed, and I found the capability already exists one file over — the proxy detail pane renders both size and elapsed — which makes this pure wiring rather than a build-out.","v":"ui-v2/tabs.jsx RepeaterTab toolbar: a `{fmtSize(rep.responseBytes)} · {fmtMs(rep.elapsedMs)}` span next to STATUS, gated on `typeof rep.elapsedMs === \"number\" && rep.elapsedMs > -1` so the pre-send sentinel (-1) renders nothing instead of \"-1 ms\"; the history-nav title string appends the same pair per `histEntries[histPos]`. Backend fields unchanged since 8bb4d7d/control_server.cpp:1551-1552,1566-1567,1576-1577.","o":"partial","r":"UI HALF of #305, closing the remainder left open by 8bb4d7d/1ecbc7b (concurrent backend lane): RepeaterTab's toolbar (ui-v2/tabs.jsx) now renders response byte length + elapsed ms next to STATUS via the existing proxy.jsx fmtSize/fmtMs helpers (shared global scope, proxy.jsx loads before tabs.jsx in Nullock.html), reading rep.elapsedMs/rep.responseBytes straight off the snapshot (NL.repeater = snap.repeater verbatim in real-data.js, no field allowlist to update). Gated on `elapsedMs > -1` so the -1 pre-send sentinel shows nothing rather than a bogus \"-1 ms\"/\"-0.0 KB\" (fmtSize/fmtMs were never designed for negative input). The history-nav arrows' hover tooltip gained the same two fields per entry (histEntries[histPos].elapsedMs/.responseBytes), which the wire contract already carried per-history-entry (control_server.cpp:1576-1577) but the UI never read. Verified: bundled-babel transform of all six ui-v2 script files (real-data.js is plain JS, not JSX, so untransformed) all succeed; tabs.jsx's intentional single NUL byte confirmed still present and exactly 1 occurrence (offset shifted from 58081 to 80301 purely from upstream file growth since that check was last recorded, not from this diff); a Node functional test of the show/hide gate and formatter across 4 cases (before-any-send sentinel, the older snapshot-fallback object with undefined fields, a normal 615ms/1234B send, and a degenerate 0ms/0B send) all matched expectation. No backend touched. python3 scripts/parity_report.py --check green after regenerating the page."},{"a":"repeater","f":"Repeater: \"Copy as curl command\" / copy request to other tooling","s":"exceeds","i":"medium","e":"hours","g":"None. Nine exporters (curl/wget/httpie/powershell/fetch/sqlmap/postman/nuclei/burp-raw), each with sensitive-header redaction, now reachable from BOTH proxy history and the Repeater toolbar -- vs Burp's single 'Copy as curl'.","w":"Closed 2026-08-02: the exporters existed but were reachable only from a proxy-history row. Wired the same shared renderRequestAs into the Repeater toolbar (clipboard, token-redacted). Exceeds Burp on format count and on redaction, which Burp does not do.","v":"ui-v2/tabs.jsx RepeaterTab COPY AS dropdown -> global renderRequestAs(row, rep.request); verified under bundled @babel/standalone 7.29.0 + a functional test confirming URL assembly, POST derivation, and Authorization/Cookie redaction.","o":"partial","r":"COPY AS wired into Repeater with all 9 redacting exporters; functional + real-babel verified."},{"a":"repeater","f":"Repeater: out-of-scope send guard","s":"present","i":"low","e":"hours","g":"Shared outbound scope checks protect the actual destination, port, protocol and path before each HttpClient connection, including redirects. The former API-only bypass and queued-tab-switch descriptions are obsolete. Native QML sends still block the UI; that separate responsiveness gap is tracked under cancellation.","w":"HttpClient::send checks OutboundScope before connecting, so direct Repeater::send calls also use the registered project policy. The API performs its early host check and synchronously copies the active request into sendAsync before scheduling the worker. Live regressions verify path, port, scheme, redirects and dynamic scope edits.","v":"Src/Core/Networking/networking.cpp HttpClient::send; Src/Core/Networking/outbound_scope.cpp; Src/App/app.cpp OutboundScope::Registration; Src/BackEnd/Control/control_server.cpp /api/repeater/send; Src/Core/Networking/repeater.cpp sendAsync; scripts/outbound_scope_regression.py (41 checks).","o":"exceeds","r":"Rechecked the existing shared scope implementation and reran 41 live scope checks. Removed obsolete API-only and queued-tab-switch claims; use present rather than an unverified comparison-based exceeds grade."},{"a":"repeater","f":"Repeater: headless / scriptable driving of the tool","s":"present","i":"low","e":"hours","g":"The CLI requires Bash, curl and jq, plus base64 for file/stdin loading; a native Windows CLI remains unimplemented. Send waits for a bounded period and reports unfinished requests explicitly. Stop completes after the current response rather than aborting the socket.","w":"History loads use stable IDs, asynchronous sends survive multiple busy polls, and binary file/stdin bodies retain their bytes. Tab summaries read an explicit per-tab response flag; fresh or duplicated tabs no longer claim a response. Duplicating a request clears its response metadata.","v":"bin/nullock cmd_repeater; Src/BackEnd/Control/control_server.cpp snapshot hasResponse and requestBase64; Src/Core/Networking/repeater.cpp duplicateTab; scripts/repeater_cli_test.py and scripts/repeater_cli_runtime.py.","o":"exceeds","r":"Verified the CLI through owned API fixtures and a real app: history IDs, asynchronous sends, Stop, binary file/stdin input and tab response state. Replaced stale defect descriptions and removed an unverified exceeds comparison."},{"a":"repeater","f":"Repeater: WebSocket message repeater tab (reissue and edit a captured WebSocket message)","s":"partial","i":"medium","e":"days","g":"A captured message can now be reissued for the common case: DetailPane's new ↦ WS REPEATER button (ui-v2/proxy.jsx, only on a WS↑/WS↓ history row) opens the existing WsRepeaterOverlay pre-filled with the row's direction and payload, and pre-selects any still-open live session on that same host:port. Still short of the item's full title: it is a global modal reused from #270, not a dedicated 'ws' tab or docked pane, and only TEXT-opcode frames are reissuable -- ProxyModel::responseRawAt (proxy_model.cpp renderBody/looksTextual) renders a binary/close/ping/pong frame's body as a \"[binary N bytes, ...]\" placeholder, not its real bytes, so the button stays disabled (with an explanatory title) on those rows rather than reissuing garbage.","w":"Closed the reissue-link half of this register's own gap text (\"What is missing is the edit-and-reissue link between that list and the (working) injector\") -- confirmed live that no such link existed (grep for onSendWsRepeater/wsInitFromRow/WS_LABEL_TO_OPCODE in ui-v2 predated this change: no hits) before building it. The binary-frame limitation is a real backend gap (the display endpoint elides non-textual bytes), not a shortcut taken here, and is surfaced honestly rather than silently reissuing a placeholder string.","v":"ui-v2/proxy.jsx DetailPane: isWsFrame/isWsTextFrame/wsInitFromRow (row.method \"WS↑\"/\"WS↓\", label parsed from row.path, body split on the raw response's \"\\n\\n\" separator -- proxy_model.cpp responseRawAt joins headers with bare \\n, not \\r\\n); WS_LABEL_TO_OPCODE top-level const; WsRepeaterOverlay now takes an `initial` prop seeding direction/opcode/payload useState and preferring a session matching initial.host/port in its `refresh` session-list callback. Reused endpoints unchanged: POST /api/ws/send, GET /api/ws/sessions (control_server.cpp, already wired by #270).","o":"","r":"Wave 2 Repeater/WS batch -- WS message repeater tab reissue-link closed for text frames (binary/control frames stay honestly out of reach), partial -> partial (gap narrowed, not a state-count move)."},{"a":"repeater","f":"Comparer: word-level comparison","s":"present","i":"low","e":"hours","g":"","w":"Verified verbatim including the tokenizer contract and the UI path.","v":"Src/Core/Networking/compare.cpp:171-176 `diff()` default branch `return lcsDiff(tokenizeWords(a), tokenizeWords(b)); // default: words`; tokenizeWords at :18-43 (each token = a word plus its trailing whitespace, or a leading-whitespace run on its own, so joining all tokens reproduces the input); token-interned LCS core at :107-127 (QHash<QString,int> ids assigns integer ids so DP cells compare in O(1)). modes() :166-169 lists \"words\" first / used as default.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers/paths that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Comparer: byte-level comparison","s":"present","i":"medium","e":"days","g":"Exact byte diff implemented: Compare::diffBytes() diffs two raw byte buffers (one 2-hex-char token per octet through the same LCS core), and /api/compare gains a binary-safe path -- mode \"bytes\" with base64 inputs (aBase64/bBase64) is decoded to raw octets before diffing, so non-UTF-8 / binary content (session tokens, serialized objects, images) survives JSON transport and compares exactly instead of being folded through QString. \"bytes\" is also listed in modes().","w":"Implemented + mutation-proven. Adds tokenizeBytes()/diffBytes() to compare.cpp and a base64 branch to the /api/compare handler; the byte tokens run through the existing budgeted LCS, inheriting its cell cap and truncation semantics. Tests/compare/compare_test.cpp (45 pass) covers identical binary buffers, a single-byte change, side rebuilds, and the key case that 0x80 vs 0x81 (both invalid UTF-8 starts) still differ rather than folding to U+FFFD; M1 (drop the low hex nibble) and M2 (swap the diff sides) each fail only their targeted cases.","v":"Src/Core/Networking/compare.cpp:76-88 `tokenizeBytes(const QByteArray &b)` (one 2-hex-char token per octet through the shared LCS core) and :179-181 `DiffResult diffBytes(const QByteArray &a, const QByteArray &b) { return lcsDiff(tokenizeBytes(a), tokenizeBytes(b)); }`; \"bytes\" listed in modes() :166-169. control_server.cpp:10452-10465 POST /api/compare: when mode == \"bytes\" and the body carries aBase64/bBase64, decodes to raw QByteArray and calls `Nullock::Core::Compare::diffBytes(a, b)` -- binary-safe, bypassing QString entirely. Tests/compare/compare_test.cpp covers identical binary buffers, a single-byte change, side rebuilds, and 0x80 vs 0x81 (both invalid UTF-8 starts) still differing rather than folding to U+FFFD.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers/paths that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Comparer: line-level comparison","s":"exceeds","i":"low","e":"hours","g":"","w":"Verified; Burp's Comparer offers Words and Bytes only, so a line mode is genuinely extra.","v":"Src/Core/Networking/compare.cpp:45-53 `QStringList tokenizeLines(const QString &s) { ... if (s[i] == QLatin1Char('\\n')) { out << s.mid(start, i - start + 1); start = i + 1; } ... }`, selected at :173 `if (m == QLatin1String(\"lines\")) return lcsDiff(tokenizeLines(a), tokenizeLines(b));`, advertised in modes() :166-169, surfaced at ui-v2/app.jsx:3385 `<Btn label=\"lines\" primary={mode === \"lines\"} onClick={() => setMode(\"lines\")} />`.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers/paths that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Comparer: colour-coded diff (added / deleted / unchanged)","s":"present","i":"low","e":"hours","g":"A greedy left-to-right scan (comparerMarkModified()) now pairs an adjacent del+ins (or ins+del) run into a distinct amber 'modified' style instead of showing them as an unrelated delete next to an unrelated insert -- matches Burp's visual treatment for straightforward in-place value changes. It is a positional heuristic, not an LCS-based rename/move detector: a modified run separated from its counterpart by an intervening common/other-op segment is not paired, and a run of multiple consecutive dels followed by multiple consecutive ins only pairs adjacent members one-to-one (extra dels/ins at either end stay plain delete/insert).","w":"Closed 2026-08-18: comparerMarkModified() (ui-v2/app.jsx, pure function) post-processes the backend's merged diff segment array before the existing streamA/streamB split, flagging paired del+ins segments `modified: true`; segStyle() renders those with a distinct amber background/colour instead of the plain red/green del/ins styling.","v":"ui-v2/app.jsx comparerMarkModified() + segStyle(op, modified) + ComparerTab's `const segs = comparerMarkModified(...)`; /api/compare's segment contract ({op,text}) unchanged, no backend touched.","o":"present","r":"Repeater-area polish batch: adjacent del+ins runs in the Comparer diff now render as a distinct 'modified' colour instead of separate delete/insert, closing the named gap."},{"a":"repeater","f":"Comparer: handles large messages","s":"partial","i":"high","e":"days","g":"2000 tokens is ~10-15 KB of words, and only 2000 CHARACTERS in chars mode — most real HTML responses truncate immediately. The cap exists because Compare::diff runs synchronously on the control/GUI thread; the fix is to move it off-thread, not to raise the number.","w":"Verified, including the honest truncation handling. The cap is real and small.","v":"D:/dev/Nullock/Src/Core/Networking/compare.cpp:14 `constexpr int kMaxTokens = 2000;` with the rationale at :11-13 `// The control handler runs on the GUI thread, so bound the LCS table`. Clipping at :74-75 `if (a.size() > kMaxTokens) { a = a.mid(0, kMaxTokens); res.truncated = true; }`. Honesty guard at :122-125 `// A TRUNCATED diff compared only the clipped prefix, so it must NEVER assert identit","o":"","r":"PROGRESS (stays partial). The flat 2000-token/side cap is replaced by an adaptive AREA budget (pure, mutation-proven Compare::budgetedSizes; kMaxCells = 16M = the same ~64 MB / ~100 ms the old 2000x2000 table cost). A side that already fits is kept WHOLE and only an oversized side is clipped, so the common short-vs-long case -- a one-line injected value vs a 30 KB response -- now diffs the long side in FULL instead of clipping it to 2000; two moderately large messages compare at up to ~4000 tokens each (2x the old linear ceiling). The tokeniser's per-side stop rose 2000 -> 20000. The proven O(n*m) LCS + exact backtrack are UNCHANGED (identical output for existing inputs; compare_test green). Verified: compare_test 38/38 incl. new budget cases + 2 mutations (preserve-short-side; both-large sqrt-of-budget); an asymmetric short-vs-3000-token compare is now NOT truncated and diffs all 3000. Gauntlet ctest 98/98 + probe 156. REMAINDER (why still partial, matching the gap's own point): a truly huge SYMMETRIC compare still clips at ~4000/side because the diff runs synchronously on the request thread -- lifting that ceiling needs it moved OFF-thread plus a linear-space LCS (Hirschberg) to raise the memory bound. This narrows the gap for the asymmetric + moderately-large cases without that larger refactor."},{"a":"repeater","f":"Comparer: compare two proxy-history items directly","s":"exceeds","i":"low","e":"days","g":"Still a divergent diff engine (client-side diffLines) from the backend Comparer's C++ engine, with different tokenization — two engines to maintain, a low-value cosmetic gap. The prior audit's other two claims are now stale: the id-as-index bug is gone (proxy.jsx reads NL.requestRawById/responseRawById, not an index), and the unbounded n*m Int32Array table is now capped at DIFF_MAX_LINES=2000 lines per side (mirroring the backend's compare.cpp kMaxTokens), surfaced via a TRUNCATED badge in the overlay header when either side is clipped.","w":"The mark-then-diff flow is real and is a genuine workflow win over Burp's two Send-to-Comparer trips, so exceeds stands. Re-verified against live source: the id-as-index bug the prior audit found was already fixed in an earlier wave (this item's own evidence field still quoted the dead NL.requestRawAt(idA - 1) code); the unbounded-diff hang/OOM risk was real and unfixed until this pass, which added the same line cap the backend Comparer already enforces.","v":"ui-v2/proxy.jsx MARK/DIFF buttons: `<button onClick={() => setDiffMark(row.id)}> ⊟ MARK` / `<button onClick={() => setDiffOpen({ idA: diffMark, idB: row.id })}> ⊟ DIFF vs #...`. Overlay at proxy.jsx:1623 `function DiffOverlay({ idA, idB, onClose, onClearMark })` reads proxy.jsx:1634-1637 `NL.requestRawById(idA)`/`NL.responseRawById(idA)` (not an index). diffLines (proxy.jsx:1588-1615) now clips each side to `DIFF_MAX_LINES = 2000` lines (mirroring Src/Core/Networking/compare.cpp:14 `kMaxTokens = 2000`) and sets `rows.truncated`, rendered as a TRUNCATED badge in the overlay header (proxy.jsx:1712-1718) when either side was clipped.","o":"exceeds","r":"Backlog #315: capped diffLines at DIFF_MAX_LINES=2000 lines/side (was unbounded n*m, could hang/OOM on a large response) + added a TRUNCATED badge; corrected the gap/evidence text's stale id-as-index claim (already fixed in an earlier wave). State stays exceeds — the mark-then-diff workflow win is unchanged — but the gap text is now accurate and the real remaining defect (uncapped diff) is fixed."},{"a":"repeater","f":"Decoder: URL encode / decode","s":"present","i":"low","e":"hours","g":"One variant only. Burp also offers 'URL encode all characters' / key-character-only modes; Qt's default toPercentEncoding leaves the unreserved set alone, so filter-bypass work that needs full encoding has to be done by hand.","w":"Verified verbatim and reachable from the Decoder tab's OPS list.","v":"Src/Core/Networking/transcode.cpp:30-32 `Result urlEncode(const QString &in) { return ok(QString::fromLatin1(in.toUtf8().toPercentEncoding())); }`; :33-35 `urlDecode` via `QByteArray::fromPercentEncoding`. Registered in operations() :279; dispatched :298-299. UI list ui-v2/app.jsx:5752-5754 DecoderTab OPS includes \"url-encode\"/\"url-decode\".","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: HTML encode / decode","s":"present","i":"low","e":"hours","g":"Named-entity table covers only lt/gt/quot/apos/amp; &nbsp;, &copy; and the rest pass through untouched. Burp resolves the full HTML entity set. Note the PROXY pane's html-decode is a different implementation (browser textarea.innerHTML) with the full set — the two disagree (see A23).","w":"Verified. The single-pass decoder is careful and correct; the entity table really is five entries.","v":"Src/Core/Networking/transcode.cpp:51-91 htmlDecode: single left-to-right pass (comment :52-56), numeric &#dd;/&#xhh; at :67-79, named-entity table at :80-88 covering only lt/gt/quot/apos/amp (5 entries -- &nbsp;/&copy;/etc pass through untouched). Registered in operations() :281; dispatched :300-301. UI list ui-v2/app.jsx:5752-5754 DecoderTab OPS.","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: Base64 encode / decode","s":"exceeds","i":"low","e":"hours","g":"","w":"Verified. Strict decode + four registered ops including base64url as first-class operations, which Burp does not offer separately.","v":"Src/Core/Networking/transcode.cpp:21-23 `Result base64Decode(const QString &in, bool url) { const auto opt = (url ? QByteArray::Base64UrlEncoding : QByteArray::Base64Encoding) | QByteArray::AbortOnBase64DecodingErrors; ...` -- strict decode plus four registered ops including base64url as a first-class operation (transcode.cpp:295-297), which Burp does not offer separately.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: ASCII hex encode / decode","s":"present","i":"low","e":"hours","g":"None remaining for the decode itself: hexDecode now returns the exact octets via okBytes() and /api/transcode exposes them as outputBase64, so hex-decoding a binary blob is byte-lossless (the U+FFFD-folding is gone). The `output` text field is still a best-effort UTF-8 view by design; a Hex view reads outputBase64.","w":"The QString::fromUtf8 lossy-decode gap is fixed (base64/hex/octal/binary decoders return okBytes(raw); endpoint emits outputBase64). Present as before, now without the binary-loss caveat.","v":"Src/Core/Networking/transcode.cpp:95-97 hexEncode `return ok(QString::fromLatin1(in.toUtf8().toHex()));`; :98-107 hexDecode (strip whitespace, require even length + hex-only via QRegularExpression, then `return ok(QString::fromUtf8(QByteArray::fromHex(s.toLatin1())));` -- the fromUtf8 collapses non-UTF-8 bytes to U+FFFD). Registered in operations() :281; dispatched in apply() :302-303. UI list ui-v2/app.jsx:5755 OPS includes \"hex-encode\"/\"hex-decode\".","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers/paths that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: Hash operations (MD2, MD4, MD5, SHA, SHA-224, SHA-256, SHA-384, SHA-512)","s":"present","i":"low","e":"hours","g":"Comprehensive hash set: MD4, MD5, SHA-1, SHA-224/256/384/512, SHA3-256. MD2 is intentionally omitted -- Qt/OpenSSL do not expose it and it is a broken, deprecated hash.","w":"Closed 2026-08-10 (eb944ee): added md4/sha224/sha384/sha3-256 to transcode; MD2 unavailable in Qt (documented).","v":"transcode.cpp apply() hash dispatch + ops(); Tests/transcode known-vector assertions (md4/sha224/sha384/sha3-256).","o":"partial","r":"Hash set extended (all but MD2, which Qt cannot provide)."},{"a":"repeater","f":"Decoder: \"Smart decode\" heuristic auto-detection","s":"exceeds","i":"low","e":"hours","g":"","w":"Verified end to end: the loop, the no-progress guard, the chain return, the API passing chain through, and the UI rendering it.","v":"Src/Core/Networking/transcode.cpp:323-345 `Result smartDecode(const QString &input, QStringList *chain) { ... for (int iter = 0; iter < 12; ++iter) { ... jwt -> url -> html -> base64 -> hex ... const Result r = apply(op, cur); if (!r.ok || r.output == cur) break; // failed or made no progress; steps << op; ... }`, terminal break on jwt-decode :338, no-progress guard :335, chain returned via out-param and surfaced by the caller. Base64 detector guard :248-265 `looksLikeBase64()` requires >=80% printable decoded bytes so a pure-hex string falls through to hex-decode instead of a false-positive base64 hit. UI: ui-v2/app.jsx:5885 `<Btn label=\"✦ smart decode\" primary onClick={() => run(\"smart\")} ...`.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers/paths that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: stacked block chaining (each transform creates a new block feeding the next, with per-block Decode-as / Encode-as / Hash)","s":"partial","i":"medium","e":"days","g":"Pressing '↑ input' discards the prior stage and clears the recorded smart-decode chain, so you cannot revise stage 2 and watch 3-5 recompute the way Burp's vertical block stack does. Smart decode records its chain but only as a label.","w":"Verified; the state really is one input + one output and the chain button is destructive.","v":"ui-v2/app.jsx DecoderTab (function at :6171); the single chaining affordance `const useOutputAsInput = () => { setInput(output); setOutput(\"\"); setOutputB64(\"\"); setChain([]); setErr(\"\"); };` (:6248) bound to the '↑ input' button (:6326) -- resets rather than stacks (line drift from the prior 1536-1541 citation, content unchanged).","o":"","r":"Wave 0 register-accuracy audit: held at partial. useOutputAsInput (ui-v2/app.jsx:6248) still does `setInput(output); setOutput(\"\"); setOutputB64(\"\"); setChain([]); setErr(\"\");` -- pressing the chain button still discards the prior stage's output/error state and clears the recorded chain rather than pushing a new stacked block, matching the prior finding exactly (line drift only). No code change this pass."},{"a":"repeater","f":"Decoder: \"Send to Decoder\" from other tools / decode a selection in place","s":"present","i":"medium","e":"days","g":"\"Send to Decoder\" now exists from the three places it was missing: Proxy history / Site map's DetailPane (a DECODER menu, request/response, mirroring the existing COMPARER menu), Repeater's request/response message-editor panes (a DEC button beside the existing CMP button), and the Intercept queue's held-message toolbar (a DEC button beside CMP). Each dispatches send-to-decoder, which bumps the app reducer's decoder.seedNonce -- the Decoder tab watches that nonce and overwrites its own local input, then switches to the tab. The remaining honest gap from the original plan is unchanged and separate: the Proxy detail pane's own CodecBar selection-decode tools are still a second, divergent JS codec implementation (proxy.jsx) rather than a call to /api/transcode, so it can still disagree with the canonical Decoder tab on HTML-entity and hex edge cases -- unifying those two codec paths is unrelated follow-up work, not required for the affordance this item names.","w":"Closed 2026-08-12: added a client-only decoder.seedText/seedNonce slot to the app reducer and a send-to-decoder action; DecoderTab (app.jsx) takes a decoder prop and a useEffect keyed on seedNonce overwrites its local input (and clears stale output) on every send, including a repeat send of identical text. Wired three callers: proxy.jsx's DetailPane (new DECODER dropdown beside COMPARER), tabs.jsx's RepeaterTab (new DEC button beside CMP on both request and response panes), and tabs.jsx's InterceptTab (new DEC button beside CMP on the held-message toolbar).","v":"ui-v2/app.jsx: initialState.decoder slot + reducer's \"send-to-decoder\" case (bumps seedNonce); DecoderTab({decoder}) useEffect keyed on decoder.seedNonce. ui-v2/proxy.jsx: DetailPane's DECODER dropdown (request/response) calling the new onSendDecoder prop; ProxyTab wires onSendDecoder={{... dispatch send-to-decoder + onSwitchTab(\"decoder\") ...}}. ui-v2/tabs.jsx: RepeaterTab's sendToDecoder() + two DEC buttons (request/response panes); InterceptTab's sendToDecoder() + DEC button on the held-message toolbar.","o":"present","r":"Wave 2: \"Send to Decoder\" wired from Proxy/Site-map DetailPane, Repeater's request/response panes, and the Intercept held-message toolbar, closing the affordance half of #323 (partial -> present); the codec-divergence caveat is left honestly in gap as unrelated follow-up."},{"a":"repeater","f":"Decoder: hash-algorithm identification from a digest","s":"exceeds","i":"low","e":"hours","g":"","w":"Verified verbatim, wired, and surfaced. Burp has no equivalent.","v":"D:/dev/Nullock/Src/Core/Networking/transcode.cpp:287-308 `QStringList identifyHash(const QString &input)` — `if (s.startsWith(QLatin1String(\"$2a$\")) || ... \"$2b$\" || \"$2y$\") { out << QStringLiteral(\"bcrypt\"); return out; } ... \"$1$\" md5crypt, \"$5$\" sha256crypt, \"$6$\" sha512crypt, \"$argon2\"` then hex-length classification `case 32: out << \"MD5\" << \"NTLM\" << \"MD4\"; case 40: SHA-1/RIPEMD-160; case 56","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: JWT decode with security analysis","s":"exceeds","i":"low","e":"hours","g":"","w":"Verified on both sides. The proxy-side analyser is substantially richer than the auditor even credited (alg-confusion hint, kid injection, nbf/iat/iss/aud, JWE).","v":"Backend D:/dev/Nullock/Src/Core/Networking/transcode.cpp:166-174 `QString out = QStringLiteral(\"=== HEADER ===\\n\") + pretty(hdr) + ... if (alg.compare(QLatin1String(\"none\"), Qt::CaseInsensitive) == 0) out += \"\\n\\n[!] alg=none -- signature not verified; forgeable.\" else if (alg.startsWith(QLatin1String(\"HS\"))) ... out += \"\\n\\n[i] Signature is NOT verified here (no key).\"`. Proxy-side ui-v2/proxy.js","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"repeater","f":"Decoder: additional codecs beyond Burp's set (rot13, unicode escape, GraphQL, gRPC framing, CBOR, SAML)","s":"exceeds","i":"low","e":"days","g":"CBOR is still self-declared partial (no tag handling) -- unchanged by this batch. All four protocol decoders (graphql-parse/grpc-frame/cbor-decode/saml-decode) are now also reachable from the dedicated Decoder tab's op-button row, not just the Proxy/Repeater CodecBar -- both surfaces call the same pure client-side runCodec(), so behaviour is identical either way.","w":"Closed 2026-08-18: DecoderTab's OPS array (ui-v2/app.jsx) gains graphql-parse/grpc-frame/cbor-decode/saml-decode; run() special-cases those four names (CLIENT_ONLY_OPS) to call runCodec() directly (proxy.jsx, synchronous, already used by CodecBar) instead of round-tripping through the backend /api/transcode endpoint those decoders were never wired into.","v":"ui-v2/app.jsx DecoderTab OPS + CLIENT_ONLY_OPS + run(); ui-v2/proxy.jsx runCodec() cases graphql-parse/grpc-frame/cbor-decode/saml-decode (unchanged implementation, only the caller is new).","o":"exceeds","r":"Repeater-area polish batch: the Decoder tab's op-button row now includes the four protocol decoders that previously lived only in the Proxy/Repeater CodecBar, routed to the same pure runCodec() implementation."},{"a":"repeater","f":"Inspector: \"Request attributes\" (method, path, HTTP version/protocol)","s":"present","i":"medium","e":"days","g":"None — surfaced in the app by the new INSPECTOR tab.","w":"Closed 2026-08-02: the /api/inspect backend existed; added the INSPECTOR tab (commit 86f094c) that renders this. Verified via bundled-babel transform + field-contract match to inspector_logic (backend covered by inspector_logic_test).","v":"The INSPECTOR tab renders the request line: method, path, HTTP version, content-type, body size/kind (ui-v2 app.jsx InspectorTab -> /api/inspect).","o":"stub","r":"INSPECTOR tab surfaces the /api/inspect structured view."},{"a":"repeater","f":"Inspector: \"Parameters\" — query string parameters","s":"present","i":"high","e":"days","g":"None -- surfaced read-only in the INSPECTOR tab's Query params section (ui-v2/app.jsx InspectorTab, view.queryParams), the same commit that shipped the sibling Cookies/JWT-decode/Request-attributes projections in the same panel. No add/remove/edit affordance -- same as those three items, and consistent with how this register already grades a read-only Inspector projection as full parity.","w":"Register-accuracy correction: this item's “no UI, nothing calls /api/inspect” verdict went stale the moment the INSPECTOR tab shipped (commit 86f094c, 2026-08-02) -- that same commit closed sibling items #327 (request attributes), #330 (cookies) and #332 (JWT decode) to present, but this one was never reconciled. Re-verified against live source: ui-v2/app.jsx:3045 `view.queryParams && view.queryParams.length ? <Section title={\"Query params \" ...` renders every pair /api/inspect returns via inspector_logic.cpp's parsePairs(query) (:168). Flipped stub -> present for consistency with the established grading of the other three Inspector projections in the same panel; no code change needed.","v":"D:/dev/Nullock/Src/Core/Networking/inspector_logic.cpp:164-168 `const int q = target.indexOf('?'); out[\"path\"] = q < 0 ? target : target.left(q); const QString query = q < 0 ? QString() : target.mid(q + 1); out[\"query\"] = query; out[\"queryParams\"] = parsePairs(query);` over :30-43 `if (eq < 0) arr.append(nv(urlDecode(part, formDecode), QString())); else arr.append(nv(urlDecode(part.left(eq), formD UI: ui-v2/app.jsx:3045 `{view.queryParams && view.queryParams.length ? <Section title={\"Query params (\" + view.queryParams.length + \")\"}><KV rows={view.queryParams} /><\/Section> : null}` inside InspectorTab, called via NL.actions.inspect(raw, kind) -> POST /api/inspect.","o":"stub","r":"Register-accuracy fix: the INSPECTOR tab (86f094c) already renders view.queryParams read-only, matching the same-panel grading precedent for Cookies/JWT/Request-attributes -- this item was simply never flipped when that shipped. No code change, docs/roadmap regenerated."},{"a":"repeater","f":"Inspector: \"Parameters\" — body parameters (form-urlencoded and JSON)","s":"present","i":"high","e":"weeks","g":"All four body content types now populate the params view: form-urlencoded, JSON (recursively flattened into Burp-style dotted/bracketed leaves -- user.name, user.addr.city, tags[0], items[1].id -- incl. a top-level array and {}/[]-placeholders for empty containers), multipart/form-data (each part as name=value; a file part shows [file: <name>, <N> bytes] parsed from the RAW bytes so a binary upload isn't transcode-mangled), and XML (leaf element-path text order.item.sku plus attributes order@id). All parsers are depth-/count-bounded (maxDepth 64, maxParams 2000).","w":"Implemented + mutation-proven. inspector_logic.cpp gained flattenJson (recursive JSON), parseMultipart (raw-byte multipart) and flattenXml (QXmlStreamReader element paths + attributes); the content-type switch dispatches form/multipart/json/xml/other. Tests/inspector_logic/inspector_logic_test.cpp (60 pass) locks nested JSON, top-level array, multipart text+file, and XML path+attr; four mutants (array [i] format, object prefix, multipart file-detection, XML path nesting) each fail only their targeted cases. The prior gap's UI half already shipped (ui-v2 InspectorTab renders view.bodyParams); with all body kinds now parsed, the item is at parity.","v":"inspector_logic.cpp flattenJson()/parseMultipart()/flattenXml(); switch dispatches multipart/form-data + xml alongside form + json. Live POST /api/inspect: nested JSON -> {user.name,user.addr.city,tags[0]}; multipart -> {t:hi, f:[file: a.bin, 3 bytes]}; XML -> {a@id:7, a.b:hi}. Full gauntlet green (ctest 100/100, probe_smoke 156/156).","o":"stub","r":"Closed partial -> present: recursive JSON flattening, raw-byte multipart parsing, and XML element-path/attribute flattening added to inspector_logic.cpp, so all four body content types populate the params view. Mutation-proven (4 mutants), gauntlet green, live-verified via /api/inspect. The reachability (UI) half had already shipped via the INSPECTOR tab; this closes the parsing-depth half."},{"a":"repeater","f":"Inspector: \"Cookies\" — request cookies and response Set-Cookie with attributes","s":"present","i":"medium","e":"days","g":"None — surfaced in the app by the new INSPECTOR tab.","w":"Closed 2026-08-02: the /api/inspect backend existed; added the INSPECTOR tab (commit 86f094c) that renders this. Verified via bundled-babel transform + field-contract match to inspector_logic (backend covered by inspector_logic_test).","v":"The INSPECTOR tab renders request cookies and response Set-Cookie with attributes (name/value/attributes) from /api/inspect.","o":"stub","r":"INSPECTOR tab surfaces the /api/inspect structured view."},{"a":"repeater","f":"Inspector: \"Headers\" panel with add / remove / reorder","s":"present","i":"high","e":"weeks","g":"None -- an editable HEADERS view (its own tab alongside raw/body/preview/hex/inspector, the same sibling-view convention the Params table already established) now lets the user add, remove, and reorder headers with per-row up/down/× buttons in both the Repeater request editor and Intercept's held request/response editors, rewriting the underlying raw text on every change.","w":"Closed 2026-08-23: added a pure repeaterHeaderRows/repeaterHeaderRowsToLines/repeaterRebuildHeaderRows round-trip (ui-v2/tabs.jsx) built on the same repeaterSplitRaw/repeaterBuildRaw machinery repeaterChangeMethod/repeaterChangeBodyEncoding already use -- works for both a request line and a status line, since repeaterSplitRaw only treats the first raw line as three space-separated parts. A new RepeaterHeadersView component (add-row button, per-row name/value inputs, up/down reorder, remove button) is wired into the \"headers\" view tab of the Repeater request editor (rep.request, dispatches repeater-set) and Intercept's held-message editor for both request and response (editedText/setEditedText) -- the two editors in the message-editor toolbar family that were already editable. Repeater's own RESPONSE pane and Proxy history's DetailPane stay on the prior read-only headers text view, matching their own pre-existing \"read-only\" labels/scope (Burp doesn't offer header editing on immutable history entries either). The write path the old why-text found missing (\"no re-serializer anywhere\") now exists and is UI-reachable.","v":"ui-v2/tabs.jsx repeaterHeaderRows/repeaterHeaderRowsToLines/repeaterRebuildHeaderRows (pure); RepeaterHeadersView + RepeaterHeaderRow (new components); reqView===\"headers\" branch in RepeaterTab's request pane (dispatches {type:\"repeater-set\", payload:{request:next}}); editorView===\"headers\" branch in the Intercept held-message editor (setEditedText) for both current.kind 0 (request) and 1 (response), both of which already listed \"headers\" in their views array.","o":"stub","r":"Editable HEADERS view (add/remove/reorder, ui-v2/tabs.jsx RepeaterHeadersView) wired into the Repeater request editor and Intercept's held request+response editors, sharing the repeaterSplitRaw/repeaterBuildRaw round-trip already used by the method/encoding transforms. Repeater's read-only response pane and Proxy history's DetailPane intentionally left on the prior read-only headers text view."},{"a":"repeater","f":"Inspector: JWT decoding of tokens found in headers and cookies","s":"present","i":"medium","e":"days","g":"None — surfaced in the app by the new INSPECTOR tab.","w":"Closed 2026-08-02: the /api/inspect backend existed; added the INSPECTOR tab (commit 86f094c) that renders this. Verified via bundled-babel transform + field-contract match to inspector_logic (backend covered by inspector_logic_test).","v":"The INSPECTOR tab renders decoded JWTs (alg/typ/header/payload) found in headers and cookies, from inspector_logic collectJwts via /api/inspect.","o":"stub","r":"INSPECTOR tab surfaces the /api/inspect structured view."},{"a":"repeater","f":"Repeater: per-tab request history with back/forward (< >) navigation through previously sent requests","s":"present","i":"blocker","e":"days","g":"None -- each tab keeps a capped history of prior sends; ◀ ▶ buttons in the target row (ui-v2/tabs.jsx) step back/forward through it, showing a live n/count position label and a status/timestamp tooltip, and reload the selected entry into the tab via /api/repeater/history/load.","w":"Confirmed. I re-read the struct and re-ran the synonym hunt myself (historyIndex, undoStack, prevRequest, goBack, goForward, requestHistory, versions[) across Src/Core/Networking and ui-v2 — zero hits. Send genuinely overwrites in place.","v":"D:/dev/Nullock/Src/Core/Networking/repeater.hpp:19-27 `struct RepeaterTab { QString name; QString host; int port = 443; bool useTls = true; QString requestText; QString responseText; QString statusLine; };` — no history container. Overwrite at repeater.cpp:138-143 `if (result.ok) { t.responseText = QString::fromUtf8(result.rawResponse); t.statusLine = ...`. Snapshot per-tab object (control_server.","o":"present","r":"Closes the last remaining gap: a ◀ ▶ control in RepeaterTab's target row (ui-v2/tabs.jsx) navigates the active tab's send history via two pure helpers (repeaterHistoryPrevIndex/repeaterHistoryNextIndex, boundary-clamped) and NL.actions.repeaterHistoryLoad -> POST /api/repeater/history/load. histPos null means \"at the live/newest send\" (already what the tab shows, no wire call needed); a numeric index reloads that entry's full request/response via the existing endpoint. No backend touched -- reads only the historyCount/history[].statusLine/.sentAt fields already in the snapshot (control_server.cpp:1508-1514)."},{"a":"repeater","f":"Repeater: tab groups (drag tabs into a named group, reorder tabs)","s":"absent","i":"medium","e":"days","g":"No grouping, no drag-reorder. Past ~10 tabs the flat horizontal strip becomes unusable, and reordering requires close-and-recreate (which loses the tab entirely, since nothing persists).","w":"Confirmed. Fresh grep for tabGroup/groupName/sendGroup/draggable/dragstart across Src/Core/Networking/repeater.* and ui-v2/tabs.jsx: zero hits.","v":"Src/Core/Networking/repeater.hpp:187 `QList<RepeaterTab> m_tabs;` -- the RepeaterTab struct carries no group or order field; ui-v2/tabs.jsx's tab strip renders a flat horizontal scroller with no drag handlers (re-grepped for draggable/dragstart in tabs.jsx -- 0 hits).","o":"","r":"Wave 0 register-accuracy audit: held at absent. Fresh case-insensitive grep for tabGroup/groupName/sendGroup/draggable/dragstart across Src/Core/Networking/repeater.* and ui-v2/tabs.jsx returns zero hits -- no grouping or drag-reorder exists for Repeater tabs. RepeaterTab still has no group/order field. No code change this pass."},{"a":"repeater","f":"Repeater: \"Send group in sequence (separate connections)\"","s":"absent","i":"medium","e":"weeks","g":"Cannot drive a multi-step flow (login -> token -> privileged action) as an ordered sequence from Repeater. Note Src/Core/Networking/chain_runner.* does implement multi-step request chaining, but it is a separate engine with no Repeater entry point.","w":"Confirmed. No group concept exists and the only send path takes no tab list.","v":"Src/Core/Networking/repeater.cpp:135 `void Repeater::send() { if (m_busy) return; auto &t = activeTab_(); ... }` -- active tab only, one request per call. control_server.cpp:3685 `if (path == \"/api/repeater/send\")` reads no body parameters and just invokes send() on the active tab via a queued connection (line drift from the prior 116-153/3087-3097 citation, content unchanged).","o":"","r":"Wave 0 register-accuracy audit: held at absent. Repeater::send() (repeater.cpp:135) is still single-tab only (operates on activeTab_()), and POST /api/repeater/send (control_server.cpp:3685) still reads no body parameters at all -- it just QMetaObject::invokeMethod(...\"send\"...) on whichever tab is currently active. No group/sequence concept exists anywhere in the send path. No code change this pass."},{"a":"repeater","f":"Repeater: \"Send group in sequence (single connection)\" — single-packet attack over HTTP/2, last-byte synchronization over HTTP/1","s":"absent","i":"high","e":"weeks","g":"No single-packet or last-byte-sync send, and no path from Repeater to the race tester at all. The stale comment should also be fixed: Burp ships single-packet group send in Repeater in both Community and Pro.","w":"Confirmed, including the stale Burp claim in the comment. Fresh grep for last.byte / single.packet / lastByte / singlePacket across all of Src/ hits only those three comment lines, unchanged.","v":"Src/Core/Networking/race_tester.hpp:22-24 `// v1 fires via the thread pool (good enough to win most application-layer races); true last-byte / single-packet synchronization is a future raw-socket iteration.` -- verbatim match to the prior citation, no drift.","o":"","r":"Wave 0 register-accuracy audit: held at absent, including the stale-Burp-claim correction from the prior pass. race_tester.hpp's comment ('v1 fires via the thread pool ... true last-byte / single-packet synchronization is a future raw-socket iteration') is byte-for-byte unchanged, and a fresh grep for last.byte/single.packet/lastByte/singlePacket across Src/ still hits only those same comment lines -- no raw-socket last-byte-sync or single-packet send has landed, and there is still no path from Repeater into the race tester at all. No code change this pass."},{"a":"repeater","f":"Repeater: per-tab notes / annotations","s":"present","i":"low","e":"hours","g":"None -- a NOTES button in the tab strip (prompt-based, matching the existing double-click rename affordance) sets free-text per-tab notes; tabs carrying notes show a small pencil (✎) indicator and the tab tooltip includes the note text.","w":"Closed 2026-08-13: RepeaterTab (repeater.hpp:19-29) gains a `notes` QString field; Repeater::setTabNotes(index, notes) (repeater.cpp:219-223) mirrors the existing renameTab pattern and is exposed as POST /api/repeater/tab/notes (control_server.cpp:3183-3187). The snapshot's tabs[] array now includes notes (control_server.cpp:1501). ui-v2/tabs.jsx's RepeaterTab component gets a NOTES button in the tab strip (prompt-based edit of the active tab), a pencil indicator span on any tab carrying notes, and the tab tooltip appends the note text.","v":"Src/Core/Networking/repeater.hpp:19-29 (notes field), :87 (setTabNotes); repeater.cpp:219-223 (setTabNotes impl); control_server.cpp:1501 (snapshot to[\"notes\"]), :3183-3187 (/api/repeater/tab/notes); ui-v2/real-data.js:165 (repeaterTabNotes action); ui-v2/tabs.jsx onNotes handler + NOTES button + indicator span.","o":"present","r":"Repeater per-tab notes batch -- absent -> present. Backend adds a notes field to RepeaterTab plus setTabNotes()/the /api/repeater/tab/notes endpoint; frontend adds a NOTES button, a per-tab pencil indicator, and a tooltip note. This cloud session cannot build the C++ side; will confirm the next GitHub Actions ci run is green before calling this fully closed."},{"a":"repeater","f":"Repeater: \"Follow redirection\" button + redirect-following setting (never / on-site only / in-scope only / always) and \"Process cookies in redirections\"","s":"present","i":"high","e":"days","g":"","w":"Confirmed by my own grep over repeater.cpp, networking.cpp and tabs.jsx for followRedirect/maxRedirect/redirectFollow/Location: — zero hits in all three. The only redirect logic in the tree is the unrelated robots.txt fetcher.","v":"D:/dev/Nullock/Src/Core/Networking/repeater.cpp:133-147 does one `m_client.send(...)` and stores the result with no 3xx branch. HttpClient::send (Src/Core/Networking/networking.cpp:186-330) parses status/Content-Length/Transfer-Encoding but never reads Location. Unrelated: Src/Core/Networking/robots_recon.cpp:9 `constexpr int kMaxRedirectHops = 3;`.","o":"absent","r":"The ui-v2 Repeater tab now exposes both settings inline in the target-row: a FOLLOW select (mirroring RedirectLogic::FollowPolicy 0-3, never/on-site/in-scope/always) and a COOKIES checkbox, both dispatched via the existing repeater-set action to POST /api/repeater/set -- the same backend + API from the a6987bb wave, now reachable from a click rather than only from a raw API call. The backend snapshot (control_server.cpp) was extended to serialize followRedirects/processCookies back to the GUI so the controls reflect live state after a reload. No remaining gap for this item's own ask (button + 4-mode setting + cookie-processing setting)."},{"a":"repeater","f":"Repeater: \"Change request method\" (GET ↔ POST, moving parameters between query string and body)","s":"present","i":"medium","e":"days","g":"None -- a ⇄ METHOD button in the Repeater request pane-head (ui-v2/tabs.jsx) toggles GET <-> POST on the raw request text via the pure repeaterChangeMethod() helper: GET moves its query string into an x-www-form-urlencoded body (setting Content-Type) and POST moves an urlencoded body back into the query string (merging with any existing query params), recomputing Content-Length either way. Dispatched through the same repeater-set path a hand edit uses, so it round-trips through /api/repeater/set like any other edit.","w":"Closed 2026-08-17: added repeaterChangeMethod() (ui-v2/tabs.jsx) -- a pure request-line/body transform with its own small parser/serializer (repeaterSplitRaw/repeaterBuildRaw/repeaterSetHeader family), since proxy.jsx's parseRawRequest is one-way and drops Host/Content-Length, unsuitable for an edit-in-place button. Wired to a new ⇄ METHOD button next to the existing CMP/DEC/SEQ pane-head buttons.","v":"ui-v2/tabs.jsx repeaterChangeMethod() + repeaterSplitRaw/repeaterBuildRaw/repeaterSetHeader/repeaterRemoveHeader helpers; the ⇄ METHOD button in RepeaterTab's REQUEST pane-head dispatches {type:\"repeater-set\", payload:{request: repeaterChangeMethod(rep.request)}}, the identical mutation path the request textarea's own onChange uses (app.jsx:148-150 -> NL.actions.repeaterSet -> POST /api/repeater/set).","o":"","r":"Repeater request-transform batch: pure client-side GET<->POST param-location swap button, no backend change needed (the raw text just flows through the existing repeater-set/repeater/set mutation path)."},{"a":"repeater","f":"Repeater: \"Change body encoding\" (application/x-www-form-urlencoded ↔ multipart/form-data)","s":"present","i":"medium","e":"days","g":"None for hand-built or freshly-generated bodies -- a ⇄ ENCODING button in the Repeater request pane-head converts application/x-www-form-urlencoded <-> multipart/form-data via the pure repeaterChangeBodyEncoding() helper (generates a random boundary, wraps each param as a form-data part, or parses an existing multipart body's boundary/parts back into urlencoded pairs), recomputing Content-Type/Content-Length either way. Captured requests now load their full bodies. This conversion operates on form field names and values; multipart file metadata and opaque binary file parts are not preserved when converting to URL-encoded form data.","w":"Closed 2026-08-17: added repeaterChangeBodyEncoding() (ui-v2/tabs.jsx), reusing the same repeaterSplitRaw/repeaterBuildRaw/repeaterSetHeader parser family as #339's method-swap button. Wired to a new ⇄ ENCODING button next to it. The #303 capture-time multipart-destruction defect is a separate, already-tracked gap this frontend-only change does not touch.","v":"ui-v2/tabs.jsx repeaterChangeBodyEncoding() (boundary-aware multipart part parser + builder) and repeaterUrlDecode(); the ⇄ ENCODING button in RepeaterTab's REQUEST pane-head dispatches {type:\"repeater-set\", payload:{request: repeaterChangeBodyEncoding(rep.request)}}. #303's placeholder-body defect (control_server.cpp send-to-Repeater path) is the named remaining limit, unchanged by this wave.","o":"","r":"Repeater request-transform batch: pure client-side urlencoded<->multipart body re-encode button, no backend change needed."},{"a":"repeater","f":"Repeater: response \"Render\" tab (renders the HTML response)","s":"present","i":"medium","e":"days","g":"No way to see what a reflected payload actually does in a renderer. (A sandboxed srcdoc iframe would be the safe implementation; rendering attacker-controlled HTML in the tool's own origin would be a self-XSS on the control server.)","w":"Confirmed, and I verified the proxy 'preview' tab the auditor flagged: it really is only a JSON pretty-printer, not a renderer.","v":"D:/dev/Nullock/ui-v2/tabs.jsx response pane: `<textarea className=\"txt readonly\" value={rep.response} readOnly />` — no view tabs, no iframe. Proxy preview at ui-v2/proxy.jsx:1102-1108 `if (view === \"preview\") { const t = (body || \"\").trim(); if (t.startsWith(\"{\") || t.startsWith(\"[\")) { try { return JSON.stringify(JSON.parse(t), null, 2); } catch (e) {} } return body || \"(no body)\"; }`. No srcdoc","o":"absent","r":"Response pane gets a Render view: sandboxed srcdoc iframe (sandbox=\"\", no scripts/forms/same-origin) rendering the response body. tabs.jsx RepeaterTab, respView===\"render\"."},{"a":"repeater","f":"Repeater: message editor views — Pretty / Raw / Hex for both request and response","s":"partial","i":"high","e":"hours","g":"The views exist, but the Repeater response is converted from bytes to UTF-8 text before the Hex view receives it. Invalid UTF-8 bytes become replacement characters; the Hex view shows the encoded display text rather than the original response bytes.","w":"The browser offers Raw, Headers, Body, Preview and Hex views for both panes, with a static Render view for responses. A live response containing bytes 00 ff 80 41 becomes text 00 U+FFFD U+FFFD 41, so the full byte-fidelity requirement remains incomplete.","v":"ui-v2/tabs.jsx RepeaterEditorToolbar, reqText and respText; ui-v2/proxy.jsx toHexDump uses TextEncoder; Src/Core/Networking/repeater.cpp send converts rawResponse/decodedBody through QString::fromUtf8.","o":"absent","r":"Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits. Grade changed from present to partial."},{"a":"repeater","f":"Repeater: automatic \"Update Content-Length\" when the body is edited","s":"present","i":"blocker","e":"hours","g":"AUTO-CL recomputes the outgoing body length by default. Turning it off preserves deliberately malformed request framing for manual testing.","w":"Repeater::send encodes the complete request and calls ChainRunner::normalizeContentLength when enabled. The browser exposes the setting. Native helper tests and live binary-request regressions cover length recomputation without truncating or changing the request body.","v":"Src/Core/Networking/repeater.cpp send and NetworkingLogic::encodeRequestText; Src/Core/Networking/chain_runner.cpp normalizeContentLength; ui-v2/tabs.jsx AUTO-CL checkbox; Tests/chain_runner; scripts/runtime_regression.py; scripts/repeater_cli_runtime.py.","o":"present","r":"Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits."},{"a":"repeater","f":"Repeater: HTTP/2 support — per-tab HTTP/1 vs HTTP/2 protocol toggle, raw pseudo-header editing, HTTP/2-specific request smuggling","s":"absent","i":"high","e":"weeks","g":"No h2 in the manual-testing tool despite a working nghttp2 client in the proxy layer. Blocks h2-specific work: pseudo-header injection, h2.CL/h2.TE smuggling, single-packet timing.","w":"Confirmed. Fresh grep for http2/HTTP\\/2/h2 across repeater.cpp and repeater.hpp returned nothing, and the client writes HTTP/1 bytes to a plain socket.","v":"Src/Core/Networking/repeater.hpp -- RepeaterTab has no protocol field (re-checked, unchanged); Src/Core/Networking/networking.cpp's send path still connects a plain socket and writes HTTP/1 request bytes with HTTP/1 status-line parsing. The h2 stack exists but elsewhere: Src/BackEnd/Proxy/h2_client_logic.cpp, http2_client.cpp, h2_server.cpp (nghttp2, proxy-layer only).","o":"","r":"Wave 0 register-accuracy audit: held at absent. Fresh grep for http2/HTTP\\/2/h2 across repeater.cpp and repeater.hpp still returns nothing; RepeaterTab has no protocol field and the client still writes HTTP/1 bytes to a plain QTcpSocket/QSslSocket. The nghttp2-backed h2 stack (h2_client_logic.cpp, http2_client.cpp, h2_server.cpp) exists but remains confined to the proxy layer, with no Repeater entry point. No code change this pass."},{"a":"repeater","f":"Repeater: \"Unpack gzip / deflate\" in the response view","s":"present","i":"high","e":"hours","g":"gzip, x-gzip and deflate are decoded for display. Brotli and zstd remain unsupported. Display retains the original response headers, including compressed Content-Length; the decoded text is not a raw wire export.","w":"HttpClient populates decodedBody through decodeContentEncoding, and Repeater displays it with the original header block. The content_decode native suite tests gzip and both wrapped/raw deflate. The former statement that the change could not be built is stale.","v":"Src/BackEnd/Proxy/content_decode.cpp; Src/Core/Networking/networking.cpp decodeContentEncoding call; Src/Core/Networking/repeater.cpp decodedBody display; Tests/content_decode/content_decode_test.cpp.","o":"present","r":"Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits."},{"a":"repeater","f":"Repeater: cancel an in-flight request; non-blocking send","s":"partial","i":"high","e":"days","g":"Browser/API/CLI sends run on a worker and remain responsive. Native QML still calls synchronous send directly. Stop marks cancellation and prevents later redirects after the current response; it does not immediately abort a stalled socket. One asynchronous request can run at a time across all tabs.","w":"sendAsync copies the request into a worker and applies the result without replacing newer edits. Browser/API Stop and CLI stop share the cancellation flag. Live API/browser regressions cover those paths; Src/App/app.qml uses repeater.send() and has no Stop affordance.","v":"Src/Core/Networking/repeater.cpp sendAsync/cancel; ui-v2/tabs.jsx Repeater Stop; bin/nullock repeater stop; scripts/control_responsiveness_regression.py; Tests/ui/repeater_responsiveness_browser_test.cjs; scripts/repeater_cli_test.py. Src/App/app.qml native Repeater Send handler.","o":"","r":"Reconciled browser/API/CLI asynchronous sends and Stop, while recording the native QML synchronous-send path separately. Immediate socket cancellation and concurrent sends remain incomplete; grade stays partial."},{"a":"repeater","f":"Repeater: keyboard shortcut to send (Ctrl+Space / configurable hotkeys)","s":"present","i":"medium","e":"hours","g":"Edit-send-read is the core Repeater loop; forcing a mouse trip on every iteration is a real throughput tax. No configurable hotkey layer exists at all.","w":"Confirmed for Repeater send, but the auditor's supporting claim was overstated and I am correcting it: there ARE other key handlers in the UI (Enter-to-submit in scope, decoder and recon inputs). What does not exist is any hotkey for Repeater send, and no ctrlKey/metaKey handling anywhere.","v":"D:/dev/Nullock/ui-v2/tabs.jsx Repeater send is mouse-only: `<button className=\"btn primary\" onClick={send} disabled={busy}>{busy ? \"SENDING…\" : \"▶ SEND\"}<\/button>`. Other handlers that do exist: ui-v2/app.jsx:1406 `onKeyDown={e => { if (e.key === \"Enter\") run(); }}`, :1844 similar, ui-v2/tabs.jsx:63 and :91 (scope add), ui-v2/proxy.jsx:613 and :772 (Escape-to-close overlays). `grep -an 'ctrlKey|me","o":"absent","r":"Register-accuracy fix: Ctrl+Space-to-send was actually shipped in commit 1074f35 (Comparer wave, 2026-08-08) but parity.json was never flipped for it. tabs.jsx:312 `onKeyDown={e => { if (e.ctrlKey && e.code === \"Space\") { e.preventDefault(); send(); } }}` confirmed live in the current tree."},{"a":"repeater","f":"Repeater: search / highlight within the request and response editors (case-sensitivity, regex, match count)","s":"present","i":"medium","e":"days","g":"Finding a reflected canary in a large response means relying on the browser's own Ctrl+F, which does not reliably search a textarea's scrolled content.","w":"Confirmed. The Repeater panes are plain textareas with no search affordance; the deep-search facility is bound to proxy history rows only.","v":"D:/dev/Nullock/ui-v2/tabs.jsx Repeater panes are two `<textarea>` elements with header rows showing only a LINES count. Existing search is row-scoped: ui-v2/proxy.jsx:1137-1155 uses `NL.actions.search(search, \"both\", 500)` -> real-data.js:141-147 `search(q, where = \"both\", limit = 200) { const url = \"/api/search?q=\" ... }`, which returns matching history rows, not in-pane matches.","o":"absent","r":"In-editor find gains a case-sensitivity toggle (\"Aa\") and a regex mode toggle (\".*\", JS regex syntax, zero-length-match safe, invalid patterns fail closed to 0 matches instead of throwing). Combined with the existing wrap-around next/prev and match counter (cd03a95), this closes the full ask: case-sensitivity, regex, and match count."},{"a":"repeater","f":"Repeater: send from a Repeater tab to Intruder / Comparer / Decoder / Sequencer / Scanner","s":"present","i":"high","e":"days","g":"Closed: RepeaterTab now has a send-to path for all five sibling tools -- → Comparer/→ Decoder/→ Sequencer already existed (#345/#323/#167), and this wave added → Intruder (promotes the draft request into a new attack template via the same send-to-intruder-raw reducer case InterceptTab's own send-to-Intruder button already used) and → Scanner (runs the active-test battery against the draft request via the same parseRawRequest+auditRun pairing InterceptTab's own send-to-Scanner button already established). No remaining Repeater-side gap; Repeater is no longer a dead end.","w":"Reclassified 2026-08-22 (repeater send-to wave). Re-audited live source: the original claim ('exactly two send-to sites, both in the proxy DetailPane') is now stale -- RepeaterTab (ui-v2/tabs.jsx) already had working → CMP / → DEC / → SEQ buttons in its request/response pane headers from prior waves. The only two missing legs, Intruder and Scanner, are added in this wave: sendToIntruder dispatches the existing send-to-intruder-raw action (app.jsx, already used by InterceptTab) with rep.host/port/tls/request; sendToScanner reuses parseRawRequest (proxy.jsx, already used by InterceptTab's own send-to-Scanner) to build the audit URL/method/body/headers and calls NL.actions.auditRun, rendering the same finding-count banner InterceptTab already renders. Both reuse existing, already-verified reducer cases/backend calls -- no new backend surface.","v":"ui-v2/tabs.jsx RepeaterTab: sendToComparer/sendToDecoder/sendSelectionToSequencer (pre-existing) plus this wave's sendToIntruder (dispatch({type:\"send-to-intruder-raw\", host: rep.host, port: rep.port, tls: rep.tls, text: rep.request})) and sendToScanner (parseRawRequest({host:rep.host,port:rep.port,tls:rep.tls}, rep.request) -> NL.actions.auditRun(parsed.fullUrl, {method, body, headers})); request-pane header buttons ↦ CMP / ↦ DEC / ↦ SEQ / ↦ INT / ↦ SCAN plus a scan-result banner (finding count / error, DISMISS); app.jsx \"send-to-intruder-raw\" reducer case (pre-existing, previously reachable only from InterceptTab); ui-v2/real-data.js auditRun() (pre-existing, POST /api/audit/run).","o":"present","r":"Repeater send-to wave: absent -> present. Added → Intruder and → Scanner send-to buttons to RepeaterTab's request pane, completing the five-tool set (Comparer/Decoder/Sequencer already present from prior waves). Pure frontend, reusing existing reducer cases and the existing parseRawRequest+auditRun pairing InterceptTab already established. No backend change."},{"a":"repeater","f":"Repeater: tab state persisted in the project file and restored on reopen","s":"present","i":"blocker","e":"days","g":"Repeater tabs save per project every two seconds when changed, before project switching, and after shutdown workers drain. Failed writes retain the current project and retry. Per-tab request history remains a separate capability.","w":"Repeater tabs save per project every two seconds when changed, before project switching, and after shutdown workers drain. Failed writes retain the current project and retry. Per-tab request history remains a separate capability.","v":"Src/App/app.cpp saveWorkspaces; Src/Core/Storage/project_store.cpp saveSessionWorkspace; scripts/workspace_recovery_regression.py","o":"present","r":"Repeater tabs save per project every two seconds when changed, before project switching, and after shutdown workers drain. Failed writes retain the current project and retry. Per-tab request history remains a separate capability."},{"a":"repeater","f":"Comparer: item list — Paste / Load from file / Remove / Clear, sortable, pick any two","s":"present","i":"medium","e":"days","g":"Item list exists with paste/load-file/remove/clear; only two items are picked (A/B) for a pairwise diff at a time -- matches Burp's own Comparer, which also compares exactly two items per run.","w":"Re-read app.jsx ComparerTab after rewriting it. state.comparer.items is a real list (lifted into the app reducer, not local-only state) with comparer-add/remove/clear reducer cases; the toolbar has a paste popup (label + textarea + Add) and a hidden <input type=file> wired to FileReader.readAsText. Each row shows label, byte length, and A/B picker buttons.","v":"ui-v2/app.jsx ComparerTab: reducer cases comparer-add/comparer-remove/comparer-clear; item-list toolbar (+ paste item / load file / clear all) and per-item A/B/remove row.","o":"absent","r":"Comparer rebuilt around a real item list + send-to-comparer + synced dual-pane diff + text/hex toggle."},{"a":"repeater","f":"Comparer: \"Send to Comparer\" from any Burp message","s":"present","i":"medium","e":"hours","g":"Wired from Proxy history (request or response) and Repeater (request/response panes); not yet from Decoder output or Intruder results.","w":"Re-read proxy.jsx DetailPane and tabs.jsx RepeaterTab after adding the wiring. DetailPane has a \"COMPARER ▾\" dropdown (request/response) that dispatches comparer-add and switches to the Comparer tab; RepeaterTab has a \"CMP\" button on both the request and response pane heads doing the same.","v":"ui-v2/proxy.jsx DetailPane onSendComparer dropdown (request/response) -> dispatch comparer-add + onSwitchTab(\"comparer\"); ui-v2/tabs.jsx RepeaterTab sendToComparer() wired to both pane-head buttons.","o":"absent","r":"Comparer rebuilt around a real item list + send-to-comparer + synced dual-pane diff + text/hex toggle."},{"a":"repeater","f":"Comparer: two synchronized side-by-side result panels with \"Sync views\" scrolling","s":"present","i":"medium","e":"days","g":"","w":"Re-read the new ComparerTab result rendering. The backend's single merged segments[] array (POST /api/compare) is split client-side into streamA (op !== \"ins\") and streamB (op !== \"del\"), rendered into two <div> panes with independent refs; onScroll on either pane mirrors scrollTop/scrollLeft onto the other while a \"sync: on/off\" toggle button is active (default on).","v":"ui-v2/app.jsx ComparerTab: streamA/streamB filters, paneARef/paneBRef, onScrollA/onScrollB, syncScroll state + toggle button.","o":"absent","r":"Comparer rebuilt around a real item list + send-to-comparer + synced dual-pane diff + text/hex toggle."},{"a":"repeater","f":"Comparer: Text / Hex toggle on the results view","s":"present","i":"low","e":"hours","g":"","w":"Re-read the new result rendering. A \"text\"/\"hex\" button pair sets view state; renderSeg() emits either the literal segment text or textToHexPairs(s.text) (UTF-8 byte pairs via TextEncoder) per diff segment, preserving the same insert/delete color coding in both modes.","v":"ui-v2/app.jsx: textToHexPairs() helper + ComparerTab view state (\"text\"|\"hex\") + renderSeg().","o":"absent","r":"Comparer rebuilt around a real item list + send-to-comparer + synced dual-pane diff + text/hex toggle."},{"a":"repeater","f":"Decoder: Octal encode / decode","s":"present","i":"low","e":"hours","g":"None. octal-encode/decode (3-digit octal per byte) added to the transcode engine + Decoder UI.","w":"Closed 2026-08-10 (eb944ee).","v":"transcode.cpp octalEncode/octalDecode + apply()/ops(); Tests/transcode round-trip + reject cases; ui-v2 Decoder op list.","o":"absent","r":"Octal codec added + tested."},{"a":"repeater","f":"Decoder: Binary encode / decode","s":"present","i":"low","e":"hours","g":"None. binary-encode/decode (8 bits per byte) added to the transcode engine + Decoder UI.","w":"Closed 2026-08-10 (eb944ee).","v":"transcode.cpp binaryEncode/binaryDecode + apply()/ops(); Tests/transcode round-trip + reject cases.","o":"absent","r":"Binary codec added + tested."},{"a":"repeater","f":"Decoder: Gzip encode / decode","s":"present","i":"medium","e":"hours","g":"Closed client-side, not via the backend gzip zlib path this item originally scoped -- the browser's own Compression Streams API (CompressionStream/DecompressionStream, 'gzip' format) does the encode/decode entirely in ui-v2, no /api/transcode round-trip, matching the Decoder tab's existing client-only-op pattern (graphql-parse/grpc-frame/cbor-decode/saml-decode). Binary output is shown as base64 text on encode; decode accepts base64 gzip input and falls back to a hex dump if the decompressed bytes aren't valid UTF-8, same convention as the existing base64-decode op. Requires a browser with the Compression Streams API (Chrome 80+, Firefox 113+, Safari 16.4+) -- older browsers get a caught, readable error instead of a silent failure. Does not cover brotli/zstd (no browser stream codec for either), an honest remainder shared with the original gap text.","w":"Confirmed no backend gzip transcode op exists (transcode.cpp's operations() still has none) and did not add one -- instead wired the operation entirely client-side, since gzip/gunzip needs no server round-trip and the Web platform already ships a stream-based codec for it. Verified via a real gzip round-trip functional test (ascii, unicode, empty input, magic-byte check on the compressed output) and negative cases (invalid base64, valid-base64-but-not-gzip, non-UTF8 decompressed payload) run against the actual babel-transformed module in a vm sandbox with Node's native CompressionStream/DecompressionStream.","v":"ui-v2/app.jsx: gzipEncodeText/gzipDecodeText (CompressionStream/DecompressionStream 'gzip', bytesToBase64/base64ToBytes helpers) added just above DecoderTab; DecoderTab's OPS array gains \"gzip-encode\"/\"gzip-decode\"; a new ASYNC_CLIENT_OPS dispatch table in run() (parallel to the existing sync CLIENT_ONLY_OPS/runCodec table, since Compression Streams are async) routes both ops away from NL.actions.transcode.","o":"present","r":"Wave 2: Decoder gzip encode/decode wired purely client-side via the browser Compression Streams API (no backend transcode op needed); absent -> present. Brotli/zstd remain unsupported (no browser stream codec), an honest remainder shared with the original gap."},{"a":"repeater","f":"Decoder: Text / Hex view toggle per block","s":"present","i":"medium","e":"hours","g":"None -- the output hex view now reads the backend's outputBase64 field (raw octets) when present, instead of re-encoding the already-UTF-8-mangled `output` string.","w":"Wave 2 (2026-08-26): wired the remaining ui-v2 half. DecoderTab now tracks the transcode response's outputBase64 in its own state (outputB64), reset alongside output on every run/seed/use-as-input, and derives the output hex view from hexDumpBytes(base64ToBytes(outputB64)) -- the exact decoded bytes -- falling back to the prior toHexDump(output) only when outputBase64 is absent (encode ops / text-only ops carry no outputBytes server-side). hexDumpBytes is a new byte-array-taking function factored out of proxy.jsx's toHexDump(string), which now just UTF-8-encodes its input and delegates -- no behavior change for its other callers (input hex view, proxy/repeater raw-view hex mode, the gzip-decode fallback). Verified functionally: hex-decode of 00ff41 -> outputBase64 \"AP9B\" -> hexDumpBytes(base64ToBytes(...)) reproduces \"00 ff 41\" exactly, where the old toHexDump(output) path produced \"00 ef bf bd 41\" (the UTF-8 encoding of the U+FFFD that had already swallowed the 0xff byte server-side).","v":"ui-v2/proxy.jsx hexDumpBytes(bytes) (new, hoisted out of toHexDump); toHexDump(s) now `return hexDumpBytes(new TextEncoder().encode(s));`. ui-v2/app.jsx DecoderTab: outputB64 state set from r.outputBase64 in run(), cleared in the seedNonce effect and useOutputAsInput; outputHex = React.useMemo reading hexDumpBytes(base64ToBytes(outputB64)) when outputB64 is truthy, else toHexDump(output); output hex-view textarea now renders outputHex. Src/BackEnd/Control/control_server.cpp:10514-10515 already emitted outputBase64 = r.outputBytes.toBase64() when outputBytes is non-empty.","o":"present","r":"Wave 2: DecoderTab's output hex view now consumes /api/transcode's outputBase64 field via a new hexDumpBytes(bytes) helper, closing the frontend-only gap the prior register correction (663a1f2) left open -- no backend change."},{"a":"repeater","f":"Inspector: docked structured side panel in the Repeater / Intruder / Proxy message editors","s":"present","i":"high","e":"weeks","g":"None — docked in all three named editors via a new \"inspector\" view-tab, live off the existing /api/inspect.","w":"Closed 2026-08-09: the /api/inspect backend and its field contract already existed (closed the standalone paste-and-parse INSPECTOR tab in 86f094c); this wave added a reusable RepeaterInspectorPanel and mounted it as a debounced, live-updating view-tab inside the actual message editors instead of a separate tool. Verified via bundled-babel transform of both touched files + a vm-sandboxed render of DetailPane/IntruderTab proving the cross-file forward reference (tabs.jsx panel used from proxy.jsx, which loads earlier) resolves at render time, plus a field-name match against inspector_logic.cpp's JSON keys.","v":"ui-v2/tabs.jsx RepeaterInspectorPanel (debounced NL.actions.inspect call) mounted as the \"inspector\" view in RepeaterEditorToolbar's views list for both request+response panes; ui-v2/proxy.jsx DetailPane reqTab/respTab gain the same \"inspector\" option; ui-v2/tabs.jsx IntruderTab TEMPLATE pane gets an INSPECTOR/EDIT toggle. All three call the same control_server.cpp:9442 /api/inspect used by the pre-existing standalone tab.","o":"stub","r":"Added RepeaterInspectorPanel (tabs.jsx), a debounced /api/inspect view reused as a docked \"inspector\" tab in Repeater's request+response editors, Proxy history's DetailPane request+response panes, and Intruder's TEMPLATE editor -- closes the stub->partial reclassification to present."},{"a":"repeater","f":"Inspector: edit-in-place — modify a decoded value and have the raw message automatically re-encoded","s":"absent","i":"high","e":"weeks","g":"This is what makes Burp's Inspector a tool rather than a viewer: edit a param value and Burp re-encodes it and fixes Content-Length. Nullock has no write direction at all — and no Content-Length fixer to call even if it did (B11).","w":"Confirmed, and this one really is absent rather than stub: unlike the read path there is no code at all. Re-ran the symbol hunt (rebuildRequest/applyInspector/reserialize/applyEdit) across Src/ -- the only reserialize hits belong to the unrelated session-handling-rules feature (session_rules.cpp), not the Inspector.","v":"Src/Core/Networking/inspector_logic.hpp declares only inspectRequest/inspectResponse (both `QJsonObject f(const QByteArray &raw)` -- input bytes, output JSON, no write-back). No Inspector-specific re-serializer symbol exists anywhere in the tree; the only `reserialize` hits are session_rules.cpp:279/373 and session_rules.hpp:153, which reserialize a request for session-rule injection, an unrelated feature.","o":"","r":"Wave 0 register-accuracy audit: held at absent. Re-ran the symbol hunt (rebuildRequest/applyInspector/reserialize/applyEdit) across Src/ -- the only reserialize hits are session_rules.cpp/.hpp's unrelated session-handling-rules reserialization (rewriting a request for injected cookies/tokens), not an Inspector write path. inspector_logic.hpp still declares only inspectRequest/inspectResponse, both read-only `QJsonObject f(const QByteArray &raw)` functions -- no mutation parameter is accepted anywhere in the inspect endpoint. No code change this pass."},{"a":"repeater","f":"Inspector: automatic multi-step decoding of values (HTML/URL/Base64) with a visible, revisable decode chain per item","s":"partial","i":"medium","e":"days","g":"Two decode paths now exist. (1) ui-v2 runs a client-side gated auto-detector (url/base64/html, up to 6 layers, with a per-step retarget <select>) over each Inspector KV row. (2) The BACKEND now also emits a decodeChain per query/cookie/body param: inspectRequest runs the bounded recursive Transcode::smartDecode over each value and attaches {decoded, decodeChain} when it makes progress -- covering url/base64/html AND hex/jwt -- so the API/report/CLI consumers of /api/inspect see decoded values too, not only the browser. Remaining gap versus Burp: neither path yet decodes an arbitrary highlighted byte RANGE in the raw editor (Burp's chain follows the text selection, not named fields), and gzip layers aren't covered.","w":"Closed 2026-08-26: the backend still decodes each Inspector value exactly once (inspector_logic.cpp unchanged, confirmed by re-reading it), so this is a second, purely client-side pass on top of that single decode -- ui-v2/tabs.jsx's repeaterInspectorKV() and ui-v2/app.jsx's InspectorTab KV() (used by every Status/Request-line/Headers/Cookies/Query/Body-params row in both surfaces) now route each row's value through one new shared component instead of a raw String() cast.","v":"ui-v2/tabs.jsx DecodeChainValue (new) plus its pure helpers decodeChainGateUrl/decodeChainGateBase64/decodeChainGateHtml (auto-detection gates), decodeChainRawUrl/decodeChainRawBase64/decodeChainRawHtml (ungated manual-override decoders), and buildDecodeChain(text, overrides, maxSteps) (chain builder, cycle-guarded via a `seen` Set, capped at 6 steps) -- defined once in tabs.jsx (loaded before app.jsx in ui-v2/Nullock.html) and consumed from both repeaterInspectorKV() (tabs.jsx) and InspectorTab's KV() (app.jsx:3464-3471), the only two Inspector-value KV renderers in the app. No backend touched; inspector_logic.cpp's urlDecode() (still one layer) is unrelated and unread by this change's own decode paths.","o":"partial","r":"Inspector decode-chain wave: a shared, gated auto-detect + per-step revisable decode chain (url/base64/html, up to 6 layers) is wired into every Inspector KV row in both the standalone INSPECTOR tab and Repeater's docked Inspector panel. Stays honestly partial -- it operates on parsed field values, not an arbitrary highlighted text selection in the raw editor, and covers only the three encodings this item names, not Burp's fuller decode-type list."},{"a":"repeater","f":"Inspector: \"Selection\" widget — character count and ASCII decimal/hex values for highlighted text, including non-printing characters","s":"present","i":"low","e":"days","g":"None functionally -- the docked Inspector panel (Repeater request/response panes and Proxy history/Site map DetailPane) now has a live Selection section: character count plus the first selected byte's decimal/hex value, with non-printing bytes labelled (\\n/\\t/\\r/space) instead of rendered invisibly. Honest remainder: Intruder's INSPECTOR/EDIT template-editor toggle does not yet track selection (no textarea selection listener wired there), so its Inspector panel always shows \"nothing selected\" -- a narrower surface than Repeater/Proxy, not a missing capability.","w":"Folded the existing per-pane selection readout (repeaterSelectionStats/repeaterDisplayChar, tabs.jsx) into RepeaterInspectorPanel itself as a permanent \"Selection\" section (rendered before the parsed-view content, so it shows even while parsing/erroring/empty) instead of a strip that vanished whenever the Inspector view-tab was active. Wired the same selection tracking into Proxy history/Site map's DetailPane (proxy.jsx), which previously had zero selection-aware code outside the codec bar's grab-whole-or-selected helper -- DetailPane gained reqSel/respSel state, onSelect/onMouseUp/onKeyUp handlers on both textareas, a bottom RepeaterSelectionReadout strip matching Repeater's UX, and sel passed into both RepeaterInspectorPanel calls.","v":"ui-v2/tabs.jsx RepeaterInspectorPanel (selectionSection, Section title=\"Selection\"); ui-v2/proxy.jsx DetailPane reqSel/respSel state + onReqSelect/onRespSelect + RepeaterInspectorPanel sel={reqSel|respSel} + RepeaterSelectionReadout in the non-inspector branches.","o":"present","r":"Docked the Selection widget inside the Inspector panel itself (Repeater + Proxy/Site-map DetailPane), matching Burp's Selection Info section rather than a separate bottom strip that disappeared when Inspector was the active view. Closes #362 partial -> present; Intruder's template-editor Inspector toggle still lacks selection tracking, called out honestly as a narrower remainder."},{"a":"repeater","f":"Inspector: HTTP/2 pseudo-header display and editing (:method, :path, :authority, :scheme) and HTTP/1↔HTTP/2 protocol toggle","s":"partial","i":"high","e":"weeks","g":"The DISPLAY half now ships: inspectRequest emits a pseudoHeaders array (:method from the request line, :path from the full target, :authority from the Host header, :scheme defaulting to https), reachable via /api/inspect. Still partial for the interactive half: EDITING a pseudo-header, the HTTP/1<->HTTP/2 protocol toggle, and actually EMITTING malformed h2 pseudo-headers on the wire (Repeater has no protocol field and writes HTTP/1 bytes) -- ui-v2 + a Repeater-h2 socket path outside headless verification.","w":"Pure addition to inspector_logic.cpp (out[\"pseudoHeaders\"]) mutation-proven in inspector_logic_test. Re-confirmed the DISPLAY half ships unchanged; held partial for the editing/toggle/emit legs, which remain blocked on both the Repeater HTTP/2 gap (#7, still absent) and the Inspector write-path gap (#9, still absent).","v":"Src/Core/Networking/inspector_logic.cpp:338 `out[\"pseudoHeaders\"] = QJsonArray{ nv(QStringLiteral(\":method\"), ...` through :343 (four pseudo-headers, line drift from the prior 158-162 citation which cited the start-line parse just above this block -- content and conclusion unchanged).","o":"","r":"Wave 0 register-accuracy audit: held at partial. The DISPLAY half is still there and unchanged: inspector_logic.cpp emits a pseudoHeaders array (:method/:path/:authority/:scheme) reachable via /api/inspect. The editing half is still absent -- Repeater has no protocol field (per item #7's re-verification) and the Inspector has no write path at all (per item #9's re-verification), so there is nothing to wire a pseudo-header edit into yet. No code change this pass."},{"a":"repeater","f":"Repeater / Comparer / Decoder / Inspector available in the native Qt desktop app","s":"partial","i":"low","e":"weeks","g":"The Qt Repeater is single-tab (no tab strip, no duplicate/rename) and its Send button bypasses the scope guard entirely (calls repeater.send() directly — see A7). There is still no Comparer/Decoder/Inspector in app.qml (tabs are Proxy/Scope/Repeater/Intercept/Intruder). And app.cpp:1163-1176 treats this window as optional legacy — 'The REAL UI is the browser control panel' — loading it only when the exe is launched from the repo root.","w":"Confirmed. Re-read Src/App/app.qml's tab bar: still five tabs (Proxy/Scope/Repeater/Intercept/Intruder), Comparer/Decoder/Inspector correctly reported absent there. The RepeaterHub/*.qml dead scaffolding finding from the prior pass is unaffected.","v":"Src/App/app.qml:110-114 `TabHeader { label: \"Proxy\"; ... root.currentTab = 0 }` through the Intruder tab at :114 -- five tabs total, no Comparer/Decoder/Inspector entry (line drift from the prior 112/657 citation, content unchanged).","o":"","r":"Wave 0 register-accuracy audit: held at partial. Src/App/app.qml's tab bar (:110-114) is still exactly Proxy/Scope/Repeater/Intercept/Intruder -- Comparer, Decoder and Inspector remain absent from the native desktop shell, unchanged. The working single-tab Repeater implementation in app.qml is unaffected by this pass. No code change this pass."},{"a":"repeater","f":"Extension access to Repeater / Comparer / Decoder / Inspector (Montoya API: sendToRepeater, registerContextMenuItem, custom message-editor tabs)","s":"partial","i":"medium","e":"weeks","g":"Extensions can now push a request into Repeater or Intruder (nullock.sendToRepeater / nullock.sendToIntruder, wired to the live tool objects) -- the most commonly used of the four integration points this item names. Still missing: registering a context-menu action, contributing a codec to the Decoder, and adding a custom message-editor tab -- the marketplace/install flow being built does not change this, since the missing piece is the hook surface, not distribution.","w":"Re-read the full extension API surface (extensions_api.hpp, all Q_INVOKABLE methods) instead of trusting the prior 'only traffic observation and finding reporting' summary. Found sendToRepeater/sendToIntruder are real, callable, and wired to the live tool objects -- confirmed by tracing setSendToRepeater's call site in app.cpp into an actual Repeater::addTabFromHistory-style path. Fresh grep for registerContextMenuItem/messageEditor/registerCodec/registerDecoder across the same file: zero hits, so those three integration points are still absent.","v":"extensions_api.hpp:351 `Q_INVOKABLE void sendToRepeater(const QString &host, int port, bool tls, const QString &requestText);` and :353 sendToIntruder (same signature); extensions_api.cpp:127-143 both implementations call through m_owner->m_sendToRepeater / m_sendToIntruder (optional callbacks) and log `[ext] sendToRepeater host:port`; Src/App/app.cpp:1220 `// nullock.sendToRepeater / sendToIntruder: extensions push a request into the` wires both via setSendToRepeater/setSendToIntruder to the real Repeater/Intruder instances. `grep -n 'registerContextMenuItem|messageEditor|registerCodec|registerDecoder' extensions_api.hpp` = 0 hits -- context-menu registration and custom-editor/codec contribution remain unimplemented.","o":"absent","r":"Wave 0 register-accuracy audit: UPGRADED absent -> partial. The prior audit's 'only hooks are traffic observation and finding reporting' claim is now stale: Q_INVOKABLE sendToRepeater(host,port,tls,requestText) and sendToIntruder(...) exist on the JS bridge (extensions_api.hpp:351,353; implemented extensions_api.cpp:127-143) and are wired live in app.cpp:1220 via setSendToRepeater/setSendToIntruder callbacks into the real Repeater and Intruder objects -- an extension really can push a captured request into either tool today. Still genuinely absent: registerContextMenuItem (no context-menu registration hook anywhere on the bridge) and custom message-editor tabs / Decoder codec contribution (no editor-provider or codec-registration method exists). 1 of the 4 named integration points now real; the other 3 remain absent."},{"a":"target","f":"Site map tree roots keyed by protocol://host:port (http://x.com:80 and https://x.com:443 are separate branches)","s":"partial","i":"medium","e":"days","g":"Closed for the ui-v2 web UI, still absent for the native Qt desktop app. ui-v2/proxy.jsx's SiteMap tree now groups by scheme+host+port (derived client-side from NL.rows, which already carries host/port/tls per request), so an app on :443 and an admin panel on :8443 render as two distinct nodes with correct per-node counts and non-OR'd TLS flags, and clicking a node scopes the history table to that exact origin. The Qt desktop app's own Site Map list (Src/App/app.qml:159-167, bound directly to the siteMap C++ model) is unchanged: SiteMapModel's Entry struct still has no port field and still ORs TLS across every request to a host -- that half needs a backend model change this cloud session can't build.","w":"Re-verified against live source after the ui-v2 fix. site_map_model.hpp/.cpp genuinely still has Entry {host,count,anyTls} with no port/scheme (unchanged from the prior audit) -- app.qml's Site Map list binds this model directly, so the desktop half of the gap is fully unchanged. ui-v2/proxy.jsx no longer reads NL.sitemap (the host-only /api/snapshot block fed by that same model) for its tree at all; it derives origin-keyed entries from rows instead, same technique already proven for leaf derivation (#370, same file).","v":"Src/FrontEnd/GUI/Models/Proxy/site_map_model.hpp:40-44 `struct Entry { QString host; int count = 0; bool anyTls = false; };` -- no port, no scheme, unchanged. Src/App/app.qml:159-167 binds `model: siteMap` directly, unchanged. ui-v2/proxy.jsx's ProxyTab now computes `sitemapEntries` via `React.useMemo` over `rows`, keyed by `(tls?\"https\":\"http\")+\"://\"+r.host+\":\"+port` (r.port/r.tls per row: control_server.cpp:1481/1488/1491), and `SiteMap` renders `e.origin` (default port omitted, mirroring the SSRF-probe origin-builder at control_server.cpp:2275-2278) as the tree label.","o":"partial","r":"ui-v2/proxy.jsx's SiteMap tree roots and leaf lookup now key on scheme+host+port derived client-side from NL.rows, instead of the backend's host-only NL.sitemap block -- closes the merged-node/OR'd-TLS half of the gap absent -> partial for the web UI; the Qt desktop app's own Site Map (bound to the same host-only SiteMapModel) is unchanged and still needs the backend model change, called out honestly. Selecting a tree node now filters the history table by exact origin (host+port+tls), not just a host substring."},{"a":"target","f":"Site map auto-populates from proxied traffic in real time","s":"present","i":"low","e":"hours","g":"","w":"Held. Every link in the chain verified end to end; the only correction is the file path (control_server.cpp lives at Src/BackEnd/Control/, not Src/App/).","v":"Src/FrontEnd/GUI/Models/Proxy/site_map_model.cpp:9-12 `connect(m_source, &QAbstractItemModel::rowsInserted, this, &SiteMapModel::onSourceRowsInserted); connect(m_source, &QAbstractItemModel::modelReset, this, &SiteMapModel::onSourceModelReset);`. Incremental update at :79-100 `onSourceRowsInserted`: existing host -> `m_entries[existing].count++` + `emit dataChanged(changed, changed, { CountRole, TlsRole })`; new host -> `beginInsertRows`/`endInsertRows`. control_server.cpp lives at Src/BackEnd/Control/control_server.cpp (not Src/App/).","o":"present","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers/paths that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"target","f":"Site map populates from the crawler / automated crawl","s":"present","i":"medium","e":"hours","g":"None — a DISCOVER tab now exposes seed input + START/STOP CRAWL, hitting /api/crawler/start and /api/crawler/stop. Crawled pages stream into Proxy history via the existing entryLoaded wiring, same as before. (Host-granularity of the site-map display is tracked separately as item 366.)","w":"Closed 2026-08-08: the crawler engine + control endpoints were already wired end to end; only the UI trigger was missing. Added NL.actions.crawlerStart/crawlerStop in real-data.js and a start/stop control in the new DISCOVER tab. Verified via bundled-babel transform; field contract (ok/error) matched against control_server.cpp:4002-4015.","v":"DiscoverTab (ui-v2/app.jsx) calls NL.actions.crawlerStart(seed) -> POST /api/crawler/start, and crawlerStop() -> POST /api/crawler/stop; crawled pages land in Proxy history via the pre-existing Crawler::entryLoaded -> ProxyModel wiring (Src/App/app.cpp:941-946).","o":"partial","r":"DISCOVER tab adds a start/stop crawl control."},{"a":"target","f":"Site map contents table columns: Host, Method, URL, Params, Status, Length, MIME type, Title, Comment, TLS, IP, Cookies, Time","s":"partial","i":"medium","e":"days","g":"No Comment or Cookies column. Columns are still hardcoded -- no show/hide, no reorder, no click-to-sort, no copy-column. (A client-side highlight-colour + free-text-comment annotation layer exists -- right-click a row, see parity item #299 -- which covers part of the practical intent of a Comment column, but it is a row overlay, not an actual sortable/reorderable table column, so that part of the gap still stands.)","w":"Narrowed 2026-09-01: Title and Extension, the two parseable/derivable columns named in the feature title, are now real table columns. Comment-as-column, Cookies-as-column, and show/hide/reorder/sort/copy-column remain absent.","v":"ui-v2/proxy.jsx HistoryTable colgroup/thead now render 14 cells (was 12): the leading blank marker, `#, Method, Status, Host, Path, Title, Params, Ext, Mime, Size, Time, IP, Captured`. Title reads a new `row[\"title\"]` field control_server.cpp's buildSnapshot() emits by regex-matching `<title>` out of the DECODED response body (bodyForInspection(), capped to the first 16 KB so a large body isn't fully scanned); Ext reuses the existing client-side `pathExtension()` helper already used by the EXT filter. Comment/Cookies columns and click-to-sort/show-hide/reorder/copy-column are still absent -- no `onClick` on any `<th>`, TLS still a dot inside the Host cell not its own column.","o":"partial","r":"Closed the Title and Extension halves of this gap: control_server.cpp's buildSnapshot() now parses a response's <title> tag (decoded body, 16 KB cap, first match) into a new `title` row field; ui-v2/proxy.jsx's HistoryTable gained Title and Ext columns (Ext via the existing pathExtension() helper). Comment-as-column, Cookies-as-column, and show/hide/reorder/sort/copy-column remain -- state held at partial, gap text narrowed rather than closed. CI confirmed green on 692664f (all 8 ci.yml jobs, including build-windows' full regression-test suite and build-linux/build-macos): https://github.com/Bikebrainz/Nullock/actions/runs/33526543362."},{"a":"target","f":"Site map: view full request/response for the selected item, with the message editor (Pretty/Raw/Hex, Inspector)","s":"present","i":"medium","e":"days","g":"None -- Inspector is docked live in the message editor, the preview tab pretty-prints XML/HTML/JSON, and Site map hosts now expand into per-URL leaf nodes (proxy.jsx SiteMap, deduped by method+path off the HTTP history rows already in state, most-recent-id wins) that jump straight to that message editor -- the last gap (host-only tree, no leaf to click) is closed.","w":"Re-verified against live source. The prior remaining gap was real: SiteMap (proxy.jsx) rendered one row per HOST from NL.sitemap ({host,count,tls} only -- control_server.cpp:1446-1459 has no per-path field), so a specific message could only be reached via the HTTP history table below, not clicked off the map. Closed client-side without a backend change: the HTTP history rows already in ProxyTab state (state.rows) carry host/method/path/status/id, so a per-host twisty now derives unique method+path leaves from those rows (leavesFor(), dedupes by method+path keeping the highest-id/most-recent row), rendered as a new .sm-leaf row list under each expanded host; clicking a leaf dispatches both selectedHost and selectedRowId, opening that exact message in DetailPane the same way clicking its row in HistoryTable would.","v":"ui-v2/proxy.jsx SiteMap() (leavesFor, .sm-twisty expand toggle, .sm-leaf rows) reads r.host/r.method/r.path/r.status/r.id off the rows prop -- the same row shape already read by HistoryTable/FilterBar elsewhere in this file (e.g. r.path at proxy.jsx:80/159/2225, r.status at :2212), so no field is invented. ui-v2/styles.css .sm-twisty/.sm-leaf/.sm-leaf-method/.sm-leaf-path/.sm-leaf-status rules. ProxyTab passes rows/selectedRowId/onSelectLeaf into <SiteMap>, dispatching {selectedHost, selectedRowId} on leaf click.","o":"","r":"Site map leaf-node wave: hosts in the Site Map tree now expand (twisty toggle) into a deduped per-URL leaf list derived client-side from the HTTP history rows already in state -- no backend change, since /api/snapshot sitemap stays host-only. Clicking a leaf selects that exact message the same way a history-table row click does. This was the sole remaining real gap on this item (map has no per-URL leaf nodes); state moves partial -> present. Verified via bundled-babel transform of ui-v2/proxy.jsx, a Node functional test of the leaf-dedupe logic (5 checks: method+path grouping, highest-id-wins on duplicate paths, distinct-method leaves, host filtering, empty-host fallback) plus a vm-sandboxed render smoke test of SiteMap in both collapsed and expanded states proving the new JSX branch does not throw, and confirmation ui-v2/tabs.jsx was untouched."},{"a":"target","f":"Site map filter — by MIME type (HTML/Script/XML/CSS/Other text/Images/Flash/Other binary), by status code family, by file extension (show only / hide), by search term (regex, case-sensitive, negative), by annotation (commented / highlighted)","s":"present","i":"medium","e":"days","g":"Case sensitivity applies to local column/free-text matching; the server regex body-search path remains case-insensitive. Annotation filtering now uses project-persisted, cross-client notes.","w":"Register correction (2026-08-19, 6dcc404): downgraded present -> partial because the annotation criterion this feature's own name enumerates was confirmed absent. Re-verified 2026-08-21: c25af6a (2026-08-20) shipped client-side highlight-colour + comment annotations with an ANNOTATED filter chip shared by FilterBar, and SiteMap (ui-v2/proxy.jsx:361-397) filters its leaf list on the same annotatedOnly/annotations props HistoryTable uses (:397 `return annotatedOnly ? leaves.filter(r => annotations && annotations[r.id]) : leaves;`) and renders the same coloured row edge (:435-437). All five enumerated criteria are now genuinely present at the surface, matching how this file grades #267's identical situation -- present, with the client-side-only caveat carried in the gap text rather than blocking the whole item. Updated 2026-09-11: 63ecda0e closes the browser-local annotation limitation with project storage and a revisioned read/patch API.","v":"ui-v2/proxy.jsx:361 SiteMap signature takes annotations/annotatedOnly; :397 leaf-list filter on annotatedOnly; :435-437 row highlight from annotationColorHex(note.color); :332 FilterBar's ANNOTATED chip feeds the same state into both HistoryTable and SiteMap (ProxyTab :2497,:2520-2521). mimeCategory()/pathExtension()/parseExtList()/extFilterMatch()/parseSearchTerm() remain the same pure helpers shared with HTTP history.","o":"present","r":"Annotation persistence caveat removed; unrelated filtering gaps remain documented."},{"a":"target","f":"Site map item actions: \"Delete host\"/\"Delete branch\", \"Save selected items\" (Burp XML), \"Copy URLs\", \"Copy links\", \"Report issues for selected branch\"","s":"present","i":"medium","e":"days","g":"None -- Delete host / Delete branch, Save selected items (Burp-site-map-shaped XML), Copy URLs, Copy links, and now Report issues for selected branch all exist in the Site map right-click menu, scoped identically (single row / directory branch / whole host).","w":"Closed the final \"Report issues for selected branch\" leg. window.NL.findings -- the same live array the ISSUES tab renders -- is filtered client-side to the ctx-menu's host/branch/single-row scope (by URL pathname prefix, not an exact-string match against the independently-built ctxMenuTargetUrls(), since a finding's url and a re-derived history-row url can format the query string differently) and rendered into a standalone, self-escaped HTML report via the same Blob+<a download> pattern Save selected items already uses. No backend endpoint needed -- findings are already fully loaded on the page. All five item-actions this parity item names are now built, so it moves partial -> present.","v":"ui-v2/proxy.jsx: urlPathname()/findingsForScope() (pure path-prefix scoping, new), buildBranchIssuesHtml() (pure HTML-escaped report builder, new), ProxyTab's reportCtxMenuIssues() handler and a new 📋 REPORT ISSUES entry in the ctxMenu JSX (beside 💾 SAVE SELECTED ITEMS). Verified with a sandboxed functional test: whole-host/branch/single-row scoping (including a sibling-prefix false-positive check, /apix vs /api), an unparseable finding.url is skipped rather than throwing, severity sort order in the rendered table, and an XSS payload in a finding's url/summary/evidence is HTML-escaped (quotes too, since the url lands in an href attribute) rather than reaching the downloaded HTML unescaped.","o":"present","r":"Wave 2 Site-map batch, final leg -- \"Report issues for selected branch\" added to the Site map right-click menu as a client-side HTML export of window.NL.findings scoped to the clicked host/branch/row (path-prefix match), reusing the existing findings data with no backend change. Closes the last open leg of this item: partial -> present."},{"a":"target","f":"Compare site maps (wizard: pick two maps or two sessions, choose which requests to compare, diff both content and issues, colour-coded result table)","s":"partial","i":"medium","e":"weeks","g":"Narrowed, not closed: a COMPARE HOSTS overlay in the Proxy tab's Site map pane now diffs the URL-path surface and the findings of two HOSTS already captured in HTTP history (client-side, no backend endpoint), split into only-A / common / only-B panes for both dimensions the item names. Still genuinely missing: no wizard to pick arbitrary saved site maps or sessions (Nullock has neither concept -- only \"two hosts seen in this engagement's history\" is comparable), no session/role dimension beyond whatever two hosts the user already captured under, and the content diff is URL-path presence only -- it does not diff request/response bytes the way a true site-map content-differ would.","w":"Re-derived against live source after the earlier register note flagged this as the item most overstated by the pre-existing baseline UI: the \"Scan-to-scan issue delta\" feature (this file's own separate \"present\" item) already has a Save/Diff/Clear baseline UI in ui-v2/app.jsx's IssuesTab (doBaselineSave/doBaselineDiff/doBaselineClear, confirmed live -- the old \"no UI caller at all\" claim about /api/baseline/* here was stale), but that is the SAME-host scan-to-scan delta, not a two-map/two-host compare, so it does not touch this item. This wave built the actual two-host comparator instead: CompareHostsOverlay (ui-v2/proxy.jsx) computes hostUrlPaths/diffHostSurfaces over rows already in state (no endpoint needed, matching the Target Analyzer/Site map tree precedent) and diffHostFindings over the existing global NL.findings array, keyed by kind+path+summary (path normalized via stripUrlOrigin so a bare-path vs full-URL finding still matches) -- the same identity-key shape control_server.cpp's own baseline/diff handler uses, just scoped to two hosts instead of two points in time for the same host. Left honestly partial: still no map/session picker, no content-byte diff, no single colour-coded result table (two side-by-side panes instead).","v":"ui-v2/proxy.jsx: hostUrlPaths/diffHostSurfaces/stripUrlOrigin/diffHostFindings (pure helpers) + CompareHostsOverlay (the panel: HOST A / HOST B selects populated from Array.from(new Set(rows.map(r => r.host))), a URL PATHS pane pair and a FINDINGS pane pair, each only-A/common/only-B). ProxyTab's pane-head gains a COMPARE HOSTS button (disabled below two distinct hosts) beside ANALYZE TARGET. Findings read from the existing global NL.findings (ui-v2/real-data.js:36 `NL.findings = snap.findings || []`), same field shape (kind/host/url/summary/severity) IssuesTab already reads. No backend touched.","o":"partial","r":"Compare-hosts wave: stub -> partial. Added a client-side COMPARE HOSTS overlay (ui-v2/proxy.jsx) diffing URL paths and findings between two hosts already in HTTP history. Honest remaining gap: no arbitrary map/session picker, no request/response content diff, findings-only + path-only surface."},{"a":"target","f":"Target > Scope: include-list of URL-matching rules","s":"partial","i":"high","e":"days","g":"The rule is a glob over the HOST STRING only. `https://example.com/app/` as a scope entry matches nothing (the anchored regex would need the literal string to BE the Host header). Path-scoped engagements ('only /shop, not /blog') cannot be expressed, and since scope gates every active tool (item 15), the coarseness propagates everywhere. A separate 'Advanced scope control' feature now provides the missing path/protocol/port dimension as a composed extra layer (its own parity item, partial, UI-wired in the SCOPE tab) -- so the practical path-scoping need this item names IS now addressable in the product, just not through the simple include-list this item is titled after.","w":"Held exactly. Re-read the compiler and the matcher; the quoted code is verbatim correct.","v":"Src/BackEnd/Proxy/proxy_server.cpp:1501-1514 `void ProxyServer::setScope(...) { auto compile = [](const QStringList &globs) { ... QString pattern = QRegularExpression::escape(g); pattern.replace(\"\\\\*\", \".*\"); out.append(QRegularExpression(\"^\" + pattern + \"$\", QRegularExpression::CaseInsensitiveOption)); ...`. globVerdict() (:1527-1538) matches this compiled list against a bare `host` string only -- no path/scheme/port parameter anywhere in this layer. A separate, newer layer now exists alongside it: Src/BackEnd/Proxy/scope_logic.hpp's AdvancedScopeRule/CompiledRule (protocol + host-regex + port-range + file-regex, composed on top of the simple list via ScopeLogic::urlInScope) -- tracked and UI-wired under its own parity item 'Advanced scope control...' (partial, ~10 non-proxy tool gates still host-only). This item's own subject, the SIMPLE include/exclude list, is unchanged: still a bare host glob with no path dimension.","o":"partial","r":"Wave 0 register-accuracy audit: held at partial. Re-read setScope/globVerdict -- the simple include-list this item names is still a bare host-glob with no path dimension, exactly as originally graded (line numbers refreshed, :1312-1338 drifted to :1501-1538). Cross-referenced the sibling 'Advanced scope control' parity item, which since this item was last touched grew a full editor UI and now supplies the path/protocol/port dimension this item's gap complains is missing -- added a pointer so the gap text does not read as if no progress happened anywhere in scope-land. No code change this pass."},{"a":"target","f":"Target > Scope: exclude-list, with exclude taking precedence over include","s":"present","i":"low","e":"hours","g":"Same host-only matching limitation as the include list.","w":"Held. Precedence, persistence and mutators all verified verbatim.","v":"Src/BackEnd/Proxy/proxy_server.cpp:1530-1539 `globVerdict()` -- `globOut = false; for (const auto &rx : outOfScope) if (rx.match(host).hasMatch()) { globOut = true; break; } ...`, consumed by `isInScope`/`isUrlInScope` (proxy_server.cpp:1542-1567) as `return !globOut && globIn;` -- out-of-scope still wins unconditionally. Persisted at Src/Core/Storage/project_store.cpp:368-371 `QJsonArray outS; for (const QString &s : m_meta.outOfScope) outS.append(s); ... o[\"outOfScope\"] = outS;`. Mutators at project_store.cpp addOutOfScope/removeOutOfScope emit scopeChanged (e.g. :519-521).","o":"","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add. Noted for context (no item change): a separate 'advanced scope' layer (protocol/host/port/file regex, ScopeLogic::CompiledRule) has since been added on top of this simple host-glob layer; it is tracked by its own backlog item ('Advanced scope control...', partial) and does not change this item's host-only gap, which is specifically about the simple glob layer this item describes."},{"a":"target","f":"Scope UI actions: Add / Edit / Remove / Paste URL / Load (from file) on both tables","s":"present","i":"medium","e":"hours","g":"None -- the two scope columns (tabs.jsx ScopeColumn) now support Edit (click a glob to load it, Save does remove-then-re-add), Paste-URL (a URL->HOST button converts a pasted URL into its hostname via new URL()), and Load-from-file (a hidden <input type=file> reads newline-delimited globs and adds each).","w":"Closed 2026-08-09: ScopeTab's two columns were previously Add-only (a text input + ADD button + per-row remove). Replaced with a shared ScopeColumn component adding click-to-edit, a URL->HOST conversion helper (urlToScopeGlob), and a file-load path, all dispatching through the existing scope-add-in/out and scope-remove-in/out reducer actions -- no backend change needed since /api/scope/in|out/add|remove already existed.","v":"ui-v2/tabs.jsx ScopeColumn (commit): click-to-edit via editIndex state + commit() remove-then-add; urlToScopeGlob() parses pasted text via `new URL()`; loadFile() reads a hidden file input via FileReader.readAsText and dispatches one scope-add-* per non-empty line.","o":"absent","r":"Wave 2 Target/Scope batch -- Scope UI actions: Add / Edit / Remove / Paste URL / Load (from file) on both tables closed (absent -> present), frontend-only, no backend change."},{"a":"target","f":"Out-of-scope handling: Burp logs everything by default and prompts \"stop sending out-of-scope items to history?\"; the proxy can optionally restrict logging/interception to in-scope items","s":"present","i":"high","e":"hours","g":"None left -- the at-the-moment 'stop sending out-of-scope items to history?' prompt is now built. ProxyTab (ui-v2/proxy.jsx) shows a dismissible banner above HTTP history the first time out-of-scope traffic is actually landing in history (a scope is defined AND logOutOfScope is on AND a visible row falls outside it), offering 'Yes, stop logging out-of-scope' (dispatches the existing log-out-of-scope-toggle action, same one the SCOPE tab checkbox uses) or 'No, keep logging everything'. Either choice dismisses it for the browser session (sessionStorage), matching Burp's one-time nudge rather than re-prompting on every render.","w":"Held. All five gate sites verified verbatim, including the two Match&Replace gates the first pass cited. Partial is the right call: Burp's restricted mode is what Nullock always does, so half the feature is present -- just not optional and not the default Burp ships.","v":"proxy_server.cpp:264-266 `const bool inScope = m_server->isInScope(req.host); if (inScope) emit m_server->requestReceived(req); else m_server->noteFiltered();` and cpp:305 `if (inScope) emit m_server->responseReceived(req, resp);`. CONNECT never MITMs off-scope: cpp:324-334 `// Out-of-scope hosts: never MITM, never log. Just keep their TLS opaque ... if (inScope && sslClient && ca && ca->hasOpenss","o":"present","r":"Closes the last remaining gap on this item (the prompt itself; the per-row marker and per-project persistence of the toggle were already closed in prior waves). Pure frontend: a client-side banner in ProxyTab (ui-v2/proxy.jsx) computed from state already in the reducer (scope, logOutOfScope, history rows) -- no backend change, no C++ build needed to verify. Verified by: babel transform of proxy.jsx succeeding, and a standalone functional test of the extracted hostInScope/loadOosPromptDismissed/saveOosPromptDismissed logic (in-scope/out-of-scope/wildcard host matching, and sessionStorage dismissal round-trip) against a stub window.sessionStorage, all passing."},{"a":"target","f":"Scope persists in the project file and reloads with the project","s":"present","i":"low","e":"hours","g":"No standalone scope import/export separate from the project file.","w":"Held. Verified both the write and the read-back path, which the first pass only half-cited.","v":"Write: Src/Core/Storage/project_store.cpp:368-371 `QJsonArray inS; for (const QString &s : m_meta.inScope) inS.append(s); QJsonArray outS; for (const QString &s : m_meta.outOfScope) outS.append(s); o[\"inScope\"] = inS; o[\"outOfScope\"] = outS;`. Read: project_store.cpp:264-269 `m_meta.inScope.clear(); for (const QJsonValue &v : o.value(\"inScope\").toArray()) m_meta.inScope.append(v.toString()); m_meta.outOfScope.clear(); for (...) m_meta.outOfScope.append(...)`.","o":"","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"target","f":"Scope is live — edits take effect immediately across the running tools without a restart","s":"present","i":"low","e":"hours","g":"","w":"Held. Confirmed both the initial seed and the live reconnect, plus the mutex pairing that makes it safe on the request hot path.","v":"Src/App/app.cpp:768-771 `proxy.setScope(projectStore.metadata().inScope, projectStore.metadata().outOfScope); QObject::connect(&projectStore, &Nullock::Core::ProjectStore::scopeChanged, &proxy, &Nullock::Proxy::ProxyServer::setScope);`. Mutex-guarded on the hot path: proxy_server.cpp:1513 `QMutexLocker lock(&m_scopeMutex);` inside `setScope` (1501-1516), matched by the same lock inside `isInScope` (proxy_server.cpp:1546) and `isUrlInScope` (:1561).","o":"","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"target","f":"Scope drives tool behaviour (proxy logging/interception, live audit, redirect-following in Repeater/Intruder)","s":"exceeds","i":"low","e":"hours","g":"Burp lets you fire Repeater at anything; Nullock refuses. Safer posture, at the cost that the coarse host-only matcher (item 9) is what gates all of it -- an over-broad glob over-permits, a narrow one blocks the whole host.","w":"Held, and it is stronger than the first pass described. Beyond the 11 explicit blocksScope() call sites (re-verified 2026-08-25 -- the prior pass's count of 13 included the function definition and a comment mention) there is a declarative kActivePaths set that auto-gates ~40 active endpoints before their handler even runs, so a newly added probe endpoint is scope-gated by listing it rather than by remembering to call the guard.","v":"control_server.cpp:1241 `bool ControlServer::blocksScope(const QString &host) const` ; 11 explicit call sites (3218, 3506, 3831, 3982, 5135, 7648, 7673, 9998, 10178, 10180, 10312 -- corrected from the prior pass's '13', which counted the definition and a comment mention alongside the real call sites) plus the declarative kActivePaths set (control_server.cpp:3198-3212, ~40 active endpoints) that scope-gates a probe endpoint by listing it rather than by remembering to call the guard. Repeater: control_server.cpp:3506 `if (m_wiring.repeater && blocksScope(m_wiring.repeater->host()))`.","o":"exceeds","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"target","f":"Per-issue definition content: Issue background, Remediation background, Vulnerability classifications (CWE), Typical severity, References","s":"partial","i":"medium","e":"weeks","g":"Backend enrichment (finding_enricher.cpp Mapping struct) carries only a one-line `fix` string alongside cwe/owasp/cvssScore/cvssVector/compliance -- there is no Issue-background prose, no separate Remediation-background prose, no References list, and no typical-severity field distinct from a finding's own instance severity. That remains a genuine backend data-model gap (a C++ struct change this cloud session cannot build/verify).","w":"Re-verified against live source (2026-08-20) and CORRECTED: the prior why-text's two 'UI' claims are both stale/false. (1) 'no ui-v2 surface renders it' is wrong -- ui-v2/app.jsx's IssueDetailBody (1262-1295) is mounted in the ISSUES tab (each finding row has a click-to-toggle ADVISORY/REQUEST/RESPONSE detail pane, toggleDetail/detailOpenId at 1426-1429, rendered 1725-1758) and shows CWE/OWASP/CVSS(+vector)/Confidence/Compliance/Fix straight off the finding object -- exactly the fields FindingEnricher attaches. (2) 'the report endpoint that does has no button' is wrong -- REPORTING tab's 'Download HTML' button (app.jsx:4424) already calls NL.actions.reportHtml() -> POST /api/report/html. Both false negatives removed; state correctly stays partial for the real remaining gap only (no background/remediation prose, no References, no typical-severity field -- all backend data-model additions, not UI wiring).","v":"ui-v2/app.jsx:1262-1295 IssueDetailBody renders CWE/OWASP/CVSS+vector/Confidence/Compliance/Fix from `finding`; :1426-1429 detailOpenId/toggleDetail state; :1658 row onClick=toggleDetail(f); :1725-1758 ADVISORY/REQUEST/RESPONSE tab bar + mounted <IssueDetailBody>; :4424 REPORTING tab 'Download HTML' button -> NL.actions.reportHtml() -> POST /api/report/html. Backend fields match exactly: control_server.cpp:1371-1377 fo[\"cwe\"]/fo[\"owasp\"]/fo[\"cvssScore\"]/fo[\"cvssVector\"]/fo[\"compliance\"]/fo[\"fixSummary\"]/fo[\"confidence\"] in the /api/snapshot findings array. Remaining real gap confirmed absent: Src/Core/Networking/finding_enricher.cpp:9-16 struct Mapping has only {cwe,owasp,cvssScore,cvssVector,compliance,fix} -- no background/remediation/references/typicalSeverity fields anywhere in the 490-line table.","o":"partial","r":"Register-accuracy fix: the 'no ui-v2 surface' and 'report button missing' claims were both stale -- IssueDetailBody (ISSUES tab) and the REPORTING tab's Download HTML button already existed. Gap narrowed to the true remaining backend-only piece (Issue/Remediation background prose, References, typical-severity field) -- no code changed, state stays partial."},{"a":"target","f":"Extension-defined custom issues that appear in the site map alongside built-in issues","s":"partial","i":"low","e":"days","g":"They land in the same flat list, so 'alongside built-in issues in the site map' is unreachable -- there is no site-map issue view. (The dead click on rowId-0 findings the prior audit flagged as an extra defect has since been fixed -- see the Issues detail pane's rowId guard.)","w":"Held, with one extra defect found: extension findings are reported with rowId 0, and the Issues list makes every row click-to-jump, so clicking an extension finding navigates to a nonexistent row #000.","v":"Src/App/app.cpp:834-836 `// Let JS extensions emit findings into the same panel via nullock.reportFinding(). Without this they fall back to the ext log.` / `extensions.setScanner(&scanner);`. Bridge at Src/Core/APIs/ExtensionsAPI/extensions_api.cpp:108-124: `ExtensionsApiBridge::reportFinding(...)` calls `scanner->reportFinding(0, severity, kind, summary, evidence, host, url)` -- rowId 0 for every extension finding, landing in the same flat Issues list as built-in findings (no site-map issue view exists to appear 'alongside' anything in). The dead-click defect the prior pass flagged (clicking a rowId-0 finding tried to jump to a nonexistent row) is FIXED since then: ui-v2/app.jsx:1733 `if (!finding.rowId) { return (<div ...>no associated request — this finding has no underlying HTTP transaction (extension-sourced)<\/div>);}` and app.jsx:2420-2421 disables the 'Open in proxy' button (`disabled={!f.rowId}`) with the title 'No associated request (extension finding)' -- clicking an extension finding today shows a clear message instead of misnavigating.","o":"partial","r":"Wave 0 register-accuracy audit: held at partial, core gap unchanged (no site-map issue view exists for anything to appear 'alongside' in). Found a genuine improvement the register hadn't caught: the dead-click-on-rowId-0 defect this item's own 'why' used to cite as an extra bug is fixed -- app.jsx now guards `!finding.rowId` in both the detail pane and the 'Open in proxy' button, showing an honest 'no associated request (extension-sourced)' message instead of a broken jump. Updated gap/evidence to drop the stale defect claim and refreshed drifted line numbers (app.cpp 726-728 -> 834-836; extensions_api.cpp 61-78 -> 108-124). No code change this pass."},{"a":"target","f":"Engagement tools > Discover content: the content-discovery engine with its own session window, live status, and pause/resume","s":"partial","i":"medium","e":"days","g":"No session object, no live progress, no pause/resume/stop. A 2000-word run blocks the control API for the whole duration with zero feedback.","w":"Held. Confirmed the handler runs discover() to completion inline and returns -- one synchronous POST, no session object. Correcting the line numbers: the handler is at control_server.cpp:8447-8492, not 8306-8352.","v":"Engine: Src/Core/Networking/content_discovery.cpp:96 `const QString base = normBase(req.basePath);` and its Request struct now has concurrency/throttleMs/extensions/mutations fields (pool-based fan-out was added since the prior pass), but that is all still internal to one synchronous call. Handler control_server.cpp:9663-9705 `if (path == \"/api/content/discover\") { ... const auto cres = Nullock::Core::ContentDiscovery::discover(cr); ... }` -- one blocking POST that runs the whole probe pool to completion on the control-server thread and returns; no session object, no progress endpoint, no start/stop/pause/resume pair anywhere in this handler or file (confirmed by re-grepping the file for a second content/discover-prefixed route -- there is none).","o":"partial","r":"Wave 0 register-accuracy audit: held at partial. Re-read the handler (moved 8447-8492 -> 9663-9705 across intervening waves) -- still one synchronous discover() call with no session/progress/pause-resume surface. Noted the engine gained an internal concurrency pool (concurrency/throttleMs) and extension/mutation wordlist variants since the prior pass, but neither changes the blocking, session-less shape this item grades on. No code change this pass."},{"a":"target","f":"Content discovery config: built-in short/long wordlists, custom wordlist file, \"derive words from site map / response bodies\", case-sensitivity handling","s":"partial","i":"medium","e":"days","g":"Custom wordlist paste + load-from-file now exist in the DiscoverTab config panel (feeds the existing per-call wordlist override). Still no short/long built-in choice (only the one 126-word default), no derivation from observed site-map paths or response bodies (Burp's single most productive discovery source), and no case-variation -- all unbuilt on the backend, not just missing UI.","w":"Partially closed by this wave: the 'custom wordlist file' ask is now real (FileReader-backed load button, same pattern as Sequencer's manual-load). The remaining asks (short/long presets, derive-from-observed-traffic, case-sensitivity) need new backend logic this cloud session cannot build/verify, so the item stays partial rather than present.","v":"ui-v2/app.jsx DiscoverTab wordlistText state + loadWordlistFile (FileReader.readAsText, mirrors SequencerTab's loadFile) + a paste textarea, both feeding NL.actions.discoverContent opts.wordlist -> control_server.cpp:9094-9095 cr.wordlist array override of ContentDiscovery::defaultWordlist().","o":"partial","r":"Discovery config wave: wordlist paste + load-from-file added to DiscoverTab, closing the custom-wordlist-file half of this item. Built-in short/long presets, derive-from-sitemap/response-bodies, and case-sensitivity handling remain open backend gaps."},{"a":"target","f":"Content discovery: thread count / concurrency and request throttling controls","s":"present","i":"high","e":"days","g":"None -- concurrency (1-64) and throttle-ms (0-60000) fields in the DiscoverTab config panel POST straight to /api/content/discover's existing concurrency/throttleMs fields.","w":"The backend dials (631088c) had no GUI caller until this wave; DiscoverTab's new Discovery config panel adds both number inputs, closing the GUI-reachability gap.","v":"ui-v2/app.jsx DiscoverTab discConcurrency/discThrottleMs state -> NL.actions.discoverContent(url, max, {concurrency, throttleMs}) -> control_server.cpp:9090-9093 clamp+set on ContentDiscovery::Request.","o":"present","r":"Discovery config wave: concurrency + throttle-ms inputs added to DiscoverTab, the remaining ui-v2 follow-on flagged in the 631088c reconciled note."},{"a":"target","f":"Content discovery: 404 / soft-404 detection so a catch-all server doesn't report the whole wordlist","s":"exceeds","i":"low","e":"hours","g":"","w":"Held -- this one survives adversarial reading intact. All three defences are real, and the corroboration discipline (trust the fingerprint only when two independently-random probes canonicalise identically) is genuinely beyond what Burp documents. Tests/content_discovery exists in the test tree.","v":"Same-depth twin calibration: Src/Core/Networking/content_discovery.cpp:125-141 `const QString t1 = base + \"/\" + randToken(); ... const QString t2 = base + \"/\" + randToken(); ... cal.reliable = (s1 == s2); // corroborated only if they agree` with `cal.jitter = std::max(64, std::abs(l1 - l2) * 2);` (:145). Path-masked fingerprint trusted only on agreement, surfaced as `result.calibrationReliable`/`softNotFoundStatus`/`softNotFoundIs200` (:159-162). Tests/scope_logic and content-discovery coverage remain in the test tree.","o":"","r":"Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."},{"a":"target","f":"Engagement tools > Generate CSRF PoC","s":"present","i":"medium","e":"hours","g":"None -- same DetailPane button as #224 (Proxy/Target share one component). Preview is text-only (no in-app render of the auto-submitting form, by design -- rendering it would fire the request).","w":"Closed 2026-08-09: same fix as #224 -- DetailPane is shared between the Proxy history table and the Site map (both areas of ui-v2/proxy.jsx's ProxyTab), so the new CSRF POC button reaches both.","v":"ui-v2/proxy.jsx DetailPane (used by both SiteMap row selection and HTTP history row selection in ProxyTab); control_server.cpp:3908 /api/csrf/poc.","o":"present","r":"CSRF PoC wave: wired /api/csrf/poc into the GUI (Proxy history / Site map DetailPane), closing the last GUI-reachability gap."},{"a":"target","f":"Engagement tools > Search (regex search across a site map branch, request and response)","s":"present","i":"high","e":"hours","g":"None -- the last remaining gap (cannot scope to a site-map branch) is closed: the Site map tree now has real directory nodes (see the sibling \"hierarchical tree\" item), and clicking one scopes both the HTTP history table and Deep Search's /api/search regex-over-bodies results to that branch (client-side post-filter on the already-server-scanned hits, the same pattern already used for the in-scope/params/hide-404 chips).","w":"CLOSED 2026-08-22: proxy.jsx SiteMap folder click now sets selectedOrigin.branch (a path prefix); ProxyTab.originRows filters on it (r.path stripped of its query string === branch, or startsWith branch + \"/\"), and both HistoryTable (fed originRows) and the existing Deep Search toggle (which filters those same rows by deepHits) are scoped for free -- no backend change needed since /api/search already returns global hits and the frontend was already post-filtering them against the visible row set.","v":"control_server.cpp /api/search now iterates ControlLogic::searchRowForIteration(n,i) newest-first with NO fixed row cap; truncated = ControlLogic::searchTruncated(scanned,n); the response carries scanned/total/scannedMinId. proxy.jsx HistoryTable keeps rows with id < deepMinId (unscanned) visible. Locks in Tests/control_logic: newest-first mapping + truncated-iff-incomplete, mutation-proven.","o":"present","r":"Site map branch-scoping wave: added real directory nodes to the Site map tree (buildSiteMapTree in ui-v2/proxy.jsx) and threaded folder selection through as selectedOrigin.branch, scoping originRows (and therefore both HistoryTable and Deep Search) to the selected branch. Closes the sole remaining gap on this item -- flips partial -> present."},{"a":"target","f":"Site map: hierarchical tree (protocol://host:port → directory → file), expandable, one node per discovered resource","s":"present","i":"high","e":"weeks","g":"Client-side only, same architecture as the existing #370 per-host leaf derivation: SiteMapModel (site_map_model.hpp) stays a flat host-only QAbstractListModel with no parent-index tree, so the Qt desktop front end (Src/App/app.qml) does not gain this -- ui-v2-only, the same asymmetry already flagged on sibling ui-v2-only capabilities elsewhere in this file. The tree only reflects paths actually seen in HTTP history (captured traffic, manual \"+ map\" adds, and OpenAPI/robots/sitemap promotions) -- it is not merged live with a running content-discovery session's own tree (tracked separately: \"Content discovery results as a live tree merged into the site map\").","w":"CLOSED 2026-08-22: ui-v2/proxy.jsx SiteMap now builds a real protocol://host:port -> directory -> file tree via buildSiteMapTree(), splitting each leaf's pathname (query stripped for the directory split only, kept on the leaf itself) on \"/\" into nested, independently expandable directory nodes -- exactly the node-per-segment structure the item asks for, one leaf per discovered method+path resource at the bottom. Selecting a directory node scopes the HTTP history table (and Deep Search) to that branch, doubling as the \"Engagement tools > Search\" branch-scoping fix (sibling item, same commit).","v":"Src/FrontEnd/GUI/Models/Proxy/site_map_model.hpp:18 `class FRONTEND_GUI_EXPORT SiteMapModel : public QAbstractListModel {` -- a LIST model; rowCount returns 0 for any valid parent (cpp:17-20 `if (parent.isValid()) return 0;`). Entry is host/count/anyTls (hpp:40-44); path is never read -- site_map_model.cpp:83 reads only HostRole and TlsRole. Browser UI: ui-v2/proxy.jsx:189-198 `{entries.map(e => (","o":"","r":"Site map branch-scoping wave: buildSiteMapTree()/siteMapTreeLeafCount() (pure, unit-tested) group a host's leaves into nested directory nodes by path segment; SiteMap renders them as expandable folder rows (a new .sm-folder style) recursively nested under each host, with a scope banner to show/clear the selected branch. absent -> present."},{"a":"target","f":"Site map also populates from Repeater, Intruder, Scanner and extension-issued requests (everything Burp sends lands in the map)","s":"absent","i":"medium","e":"days","g":"Requests you craft in Repeater or fire from Intruder never appear in history or the map, so the map is not a record of what you sent the target. Content-discovery hits become findings with rowId 0, not rows.","w":"Confirmed by enumerating every caller of addResponse/appendEntry repo-wide rather than trusting the app.cpp grep, then reading Repeater::send to be sure it does not emit through some other route. It does not. Two producers the first pass missed do reach the map (history replay, OpenAPI import) but neither is one of the four tools named here.","v":"Repeater is still a dead end: Src/Core/Networking/repeater.cpp:135 `void Repeater::send() { ... emit responseChanged(); emit busyChanged(); emit tabsChanged(); }` -- UI-state signals only, no entryLoaded/responseReceived. Repo-wide `grep -rn \"addResponse|appendEntry\" Src/` still returns only history-replay (control_server.cpp:3214-3216 `if (w.history) w.history->addResponse(r, resp); ... if (w.projectStore) w.projectStore->appendEntry(r, resp);`) and direct project-store callers (project_store.cpp:1054, control_server.cpp:6679) -- confirmed by grepping Src/Core/Networking/intruder.cpp and every scanner .cpp for the same two symbols: zero hits in either. Content-discovery hits still become rowId-0 findings, not history rows (see the sibling 'live tree' item).","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-grepped every addResponse/appendEntry call site repo-wide plus Repeater::send and every scanner source file directly -- Repeater, Intruder and Scanner still never write into history or the site map; only history-replay and direct project-store appends (OpenAPI import, etc.) reach it, matching the prior pass's finding exactly with no line drift. No code change this pass."},{"a":"target","f":"Site map \"Issues\" pane: scanner issues attached to the selected tree node, with a per-branch issue tree and severity/confidence icons overlaid on the map","s":"absent","i":"high","e":"days","g":"You cannot select a URL and see its issues, and cannot see which branch of the app is where the bugs are. Triage is a flat scroll.","w":"Confirmed. Corrected line numbers (IssuesTab is app.jsx:927, not 742) and verified the SiteMap component's prop list to be certain it cannot overlay anything.","v":"ui-v2/app.jsx:1781 `function IssuesTab({ dispatch })` still renders a flat list with only severity/kind filters, plain-text location (`{f.host} · {f.url}`) -- no per-branch tree, no map overlay. ui-v2/proxy.jsx:660 `function SiteMap({ entries, rows, selectedOrigin, selectedRowId, onSelect, onSelectLeaf, totalRows, onRowContextMenu, annotations, annotatedOnly })` -- the prop list carries no findings/issues data of any kind, confirming the map component still cannot overlay a severity/confidence icon or receive a per-node issue count.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-read IssuesTab (line moved 927 -> 1781) and SiteMap's full prop signature (line moved 172 -> 660, gained an `annotations`/`annotatedOnly` pair for the #299 highlight-colour feature but still nothing findings-shaped) -- confirms the map still cannot show per-node issues or overlay severity icons. No code change this pass."},{"a":"target","f":"Site map filter — Filter by request type: \"Show only in-scope items\", \"Show only requested items\", \"Show only parameterized requests\", \"Hide not-found items\"","s":"present","i":"medium","e":"days","g":"None -- proxy.jsx FilterBar/HistoryTable gain IN-SCOPE, PARAMS, and HIDE 404 toggle chips (client-side predicates over r.params/r.status/r.host, the last via a new hostInScope() glob matcher against scope.in). 'Requested only' stays trivially true for every row since Nullock does not yet distinguish requested-vs-inferred URLs (no inference engine exists), so it was not given a separate toggle -- an honest limitation, not a missing control.","w":"Closed 2026-08-09: ProxyFilterModel/proxy.jsx previously exposed only host/status-class/method/search filters. Added three concrete toggle chips wired into both HistoryTable's filtered useMemo and ProxyTab's own `shown` count, all pure frontend over fields already present on every row.","v":"ui-v2/proxy.jsx globToRegex()/hostInScope() (glob match r.host against scope.in); HistoryTable paramsOnly/hideNotFound/inScopeOnly props applied in its filter predicate; FilterBar IN-SCOPE/PARAMS/HIDE 404 chip row.","o":"absent","r":"Wave 2 Target/Scope batch -- Site map filter — Filter by request type: \"Show only in-scope items\", \"Show only requested items\", \"Show only parameterized requests\", \"Hide not-found items\" closed (absent -> present), frontend-only, no backend change."},{"a":"target","f":"Site map / history annotations: per-item Comment and Highlight (six colours), used to drive filters and reporting","s":"present","i":"high","e":"days","g":"None for this history/Site map workflow. Other message tables and global report formats remain outside this item; see the platform annotation item.","w":"Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action.","v":"Src/Core/Storage/project_store.cpp (historyAnnotations, annotateHistory, HAR import/export); Src/BackEnd/Control/control_server.cpp (/api/history/annotations, /api/history/annotation); ui-v2/real-data.js and proxy.jsx; bin/nullock; scripts/annotations_regression.py; Tests/ui/annotations_data_test.cjs and annotations_browser_test.cjs.","o":"partial","r":"Project-persisted comments and nine highlight colours synchronize across browser clients, survive restart/index rebuild, and round-trip through HAR. API/CLI field patches reject stale history generations. Selected-item XML and branch HTML reports include escaped notes. Legacy browser notes have an explicit migration action."},{"a":"target","f":"Manual application mapping / unrequested items: adding items to the site map by hand, and Burp inferring unrequested nodes from links, robots.txt and sitemap.xml so they show greyed-out in the tree","s":"partial","i":"medium","e":"days","g":"Both named legs now have a real UI path, but neither is automatic the way Burp's is: (1) hand-mapping is a one-URL-at-a-time text box (ui-v2/proxy.jsx), not a right-click 'add to site map' on an arbitrary selection; (2) robots.txt Disallow paths and sitemap.xml <loc> URLs each need an explicit '+ map' click per hit (ui-v2/app.jsx DiscoverTab) rather than being auto-inferred the moment they're discovered. There is still no link-graph inference (Burp also greys out same-page HTML links never actually requested) -- only the two backend-known sources (robots/sitemap) can be promoted, since content_discovery.cpp/robots_recon.cpp are the only C++ that surfaces candidate paths never sent.","w":"Closed the two frontend legs the prior why-text correctly identified as missing, reusing the existing synthetic-import mechanism rather than adding a backend route: a new NL.actions.addUrlToSiteMap(originUrl, path, method) thin wrapper (ui-v2/real-data.js) builds a one-path, one-operation OpenAPI-shaped spec and posts it through the already-proven /api/openapi/import endpoint, so a hand-typed URL or a promoted robots/sitemap hit lands as the exact same status-0 'OpenAPI imported (not yet sent)' unrequested row the spec-paste importer already produces -- confirmed by reading control_server.cpp:6231-6241 (resp.statusCode=0, reasonPhrase='OpenAPI imported (not yet sent)', persisted via appendEntry+entryLoaded) and confirming no other code path in the repo ever persists a status-0 row, so status===0 is an unambiguous unrequested marker for the frontend to grey on.","v":"ui-v2/proxy.jsx SiteMap(): a `.sm-add-row` text input + ADD button calls addUrlToMap() -> NL.actions.addUrlToSiteMap(origin, path, \"GET\"); each leaf row now computes `const unrequested = r.status === 0` and adds an `unrequested` class (opacity 0.55, dashed underline, status text replaced with \"not sent\") -- ui-v2/styles.css .sm-leaf.unrequested. ui-v2/app.jsx DiscoverTab(): each robots-scan \"Disallowed paths\" and \"Sitemap URLs\" table row gains a MapBtn calling addHitToMap(key, origin, path) -> the same wrapper, tracked per-hit in a mappedHits Set so a promoted hit shows \"✓ mapped\" instead of the button again. Src/BackEnd/Control/control_server.cpp:6057-6252 /api/openapi/import (unchanged, reused as-is) and :7814-7876 /api/robots/scan (unchanged, already returned `disallowed`/`sitemapUrls` -- only their existing UI table gained the per-row button).","o":"partial","r":"Manual add-to-map text box + unrequested (status-0) greying in the Site Map tree, plus a per-hit \"+ map\" promotion button on robots.txt Disallow paths and sitemap.xml URLs in the Discover tab -- all three reuse the existing /api/openapi/import synthetic-entry endpoint, no backend change."},{"a":"target","f":"Site map \"Crawl paths\" view (path a crawl took to reach each location)","s":"absent","i":"low","e":"days","g":"No way to see how a resource was reached. Low value outside large automated crawls, and moot until a tree exists.","w":"Confirmed. Read the crawler's queue structure directly -- depth is tracked, the referrer is not persisted.","v":"Src/Core/Networking/crawler.hpp:74-77 `struct PendingUrl { QString url; int depth = 0; };` -- no parent/referrer field. hpp:80 `void extractAndEnqueue(const QString &fromUrl, const QByteArray &body, int depth);` takes fromUrl but only to resolve relative URLs; hpp:106-107 `QSet<QString> m_seenUrls; QQueue<PendingUrl> m_queue;` stores no edges. `grep -rail \"crawl path|crawlPath\" Src ui-v2 extension","o":"absent","r":"Wave 0 register-accuracy audit: held at absent, verbatim. Re-read crawler.hpp:74-107 -- `PendingUrl` is still `{ QString url; int depth = 0; }` with no parent/referrer field, `m_seenUrls`/`m_queue` store no edges, and a fresh `grep -rail \"crawl path|crawlPath\" Src ui-v2 extensions` still returns nothing. Cited line numbers (74-77, 80, 106-107) matched exactly with zero drift. No code change this pass."},{"a":"target","f":"Scope: \"Include subdomains\" checkbox on a prefix rule","s":"present","i":"low","e":"hours","g":"None -- an 'include subdomains when adding' checkbox in the Scope tab's pane-head applies to both scope columns: when checked, adding a host also adds its *.host wildcard via the same scope-add-in/out dispatch. Implemented as a shared toggle above both columns rather than per-input (functionally equivalent: still adds both entries per Add action), and the placeholder text was corrected to show a bare host works too.","w":"Closed 2026-08-09: scope is still a flat glob list server-side (no per-rule subdomain flag), so the fix is the two-entry UI convenience the plan called for -- ScopeColumn's commit() adds both `host` and `*.host` when the checkbox is on and the value isn't already a wildcard.","v":"ui-v2/tabs.jsx ScopeTab include-subdomains checkbox (pane-head) threaded into both ScopeColumn instances via the includeSubdomains prop; ScopeColumn.commit() dispatches a second scope-add-* with '*.'+value when set.","o":"absent","r":"Wave 2 Target/Scope batch -- Scope: \"Include subdomains\" checkbox on a prefix rule closed (absent -> present), frontend-only, no backend change."},{"a":"target","f":"Advanced scope control: per-rule Protocol (HTTP/HTTPS/Any) + Host-or-IP-range (regex) + Port (regex) + File (regex, query ignored), toggled by the \"Use advanced scope control\" checkbox","s":"present","i":"high","e":"days","g":"","w":"Active tools check every concrete outbound request against host, protocol, port and path scope. Raw TCP/TLS probes require an unrestricted endpoint grant. Invalid enabled rules fail closed; invalid editor saves preserve the prior policy.","v":"Src/Core/Networking/outbound_scope.cpp; HttpClient::send; raw port/TLS/WebSocket guards; Tests/scope_logic/scope_logic_test.cpp; Tests/proxy_shutdown/proxy_shutdown_test.cpp; scripts/outbound_scope_regression.py; Tests/ui/scope_browser_test.cjs","o":"present","r":"Full outbound scope boundary, live policy updates, full-URL redirect/crawler checks and visible validation errors."},{"a":"target","f":"\"Add to scope\" / \"Remove from scope\" from the right-click context menu on any site map or Proxy history item","s":"present","i":"medium","e":"hours","g":"None -- right-click (onContextMenu) on any site-map or HTTP history row opens a small menu with Add to scope / Remove from scope, both dispatching the existing scope-add-in/scope-remove-in reducer actions.","w":"Closed 2026-08-09: there was no context-menu infrastructure anywhere in ui-v2. Added a lightweight menu (ProxyTab ctxMenu state + a fixed-position panel closed by an overlay click) wired to both SiteMap and HistoryTable rows via a shared onRowContextMenu callback.","v":"ui-v2/proxy.jsx ProxyTab ctxMenu state + openRowMenu/closeRowMenu; SiteMap and HistoryTable both gain an onRowContextMenu prop invoked from each row's onContextMenu; menu body dispatches scope-add-in / scope-remove-in.","o":"absent","r":"Wave 2 Target/Scope batch -- \"Add to scope\" / \"Remove from scope\" from the right-click context menu on any site map or Proxy history item closed (absent -> present), frontend-only, no backend change."},{"a":"target","f":"Target > Issue definitions: a browsable library of every issue type the scanner can report, independent of whether it has been found","s":"present","i":"low","e":"days","g":"None remaining for the browse capability itself. The library exists as data + an endpoint (GET /api/issue-definitions, 198 issue kinds) AND is now reachable in-app: the ISSUES tab's view toggle gained a third \"Definitions\" mode (ui-v2/app.jsx) that lazily fetches the catalog and renders it as a filterable list (search by kind/CWE/OWASP), independent of whether any of those kinds have actually been found yet -- exactly Burp's Target > Issue definitions library. What's still tracked separately: each entry's prose is the one-line canonical remediation rather than Burp's multi-paragraph background/remediation prose (a backend data-model gap, see the 'Per-issue definition content' item) -- that does not gate this item, which was specifically about the browsable-independent-of-found-status capability.","w":"UPGRADED partial->present: the prior audit's remaining blocker was \"no in-app browse UI yet\" -- that is now false. Added a Definitions view to the existing ISSUES tab's Flat/Grouped toggle (now Flat/Grouped/Definitions): a lazy-loaded fetch of NL.actions.issueDefinitions() -> GET /api/issue-definitions, rendered as a scrollable list (kind, CWE, OWASP, CVSS, compliance tags, confidence, description) with a client-side filter box matching kind/CWE/OWASP substrings. Every field the component reads (kind/cwe/owasp/cvssScore/compliance/confidence/description) matches the endpoint's actual JSON shape exactly -- no new field invented, nothing read that the backend doesn't send.","v":"ui-v2/app.jsx IssuesTab: defs/defsLoading/defsQuery state + loadDefs() + visibleDefs filter; switchView(\"definitions\") lazy-loads via NL.actions.issueDefinitions(); Definitions toggle button next to Flat/Grouped; content branch renders visibleDefs when view===\"definitions\". ui-v2/real-data.js NL.actions.issueDefinitions() -> fetch(\"/api/issue-definitions\").then(r=>r.json()). Backend unchanged: control_server.cpp:6152 /api/issue-definitions already served {ok,count,definitions[]} with exactly the fields read. Verified: bundled-babel transform of app.jsx succeeds; a standalone functional test of the visibleDefs filter logic (kind/CWE/OWASP substring match, case-insensitive, null/empty-safe) passes against sample data shaped like the real endpoint response.","o":"partial","r":"Wave 2 UI wiring: added a Definitions view to the ISSUES tab (ui-v2/app.jsx + real-data.js) that browses the existing GET /api/issue-definitions catalog -- closes the \"no in-app browse UI\" gap the prior audit flagged; the endpoint was already implemented and tested server-side, only the UI was missing."},{"a":"target","f":"Issue detail view with Advisory / Request / Response sub-tabs and per-instance evidence highlighting","s":"present","i":"medium","e":"days","g":"None for the core pane -- clicking a finding in the flat ISSUES list opens an inline detail pane (Advisory / Request / Response tabs) instead of navigating away. Advisory renders the enrichment fields the backend already attaches (cwe/owasp/cvssScore/cvssVector/confidence/compliance/fixSummary); Request/Response pull the same raw history bytes proxy.jsx's DetailPane uses, with every literal occurrence of the finding's evidence string highlighted inline. One honest remainder: extension-sourced findings (rowId 0) have no underlying HTTP transaction to show -- the pane says so rather than fetching row 0, tied to item #390's rowId-0 gap, not a new one.","w":"Closed 2026-08-11: ui-v2/app.jsx IssuesTab's flat-view row click now toggles an inline IssueDetailBody (Advisory/Request/Response tabs) instead of calling jumpToRow() directly; jumpToRow is still reachable via an explicit \"Open in proxy\" button in the pane's header. A new highlightEvidence() pure helper marks every occurrence of the finding's evidence string in the raw request/response text.","v":"ui-v2/app.jsx IssueDetailBody()/highlightEvidence()/toggleDetail() + IssuesTab's detailOpenId/detailTab state; NL.requestRawById/responseRawById (ui-v2/real-data.js) for the raw pair; control_server.cpp:1311-1328 finding JSON contract (cwe/owasp/cvssScore/cvssVector/compliance/fixSummary/confidence/rowId) matched field-for-field.","o":"absent","r":"Issue-detail batch: inline Advisory/Request/Response pane with evidence highlighting replaces the old navigate-away-on-click behavior in the ISSUES tab."},{"a":"target","f":"Content discovery: no UI at all vs Burp's dedicated discovery window","s":"present","i":"high","e":"days","g":"None — a DISCOVER tab now wraps all three engines (wordlist content/directory discovery, robots.txt + sitemap recon, BFS crawler start/stop) with results rendered generically and content-discovery/robots hits also flowing to Issues.","w":"Closed 2026-08-08: all three engines and their control endpoints were already complete server-side; only the client had no wrapper. Added discoverContent/scanRobots/crawlerStart/crawlerStop to ui-v2/real-data.js and a DISCOVER tab that runs each and renders its result. Verified via bundled-babel transform; response fields matched against control_server.cpp's /api/content/discover, /api/robots/scan, /api/crawler/start|stop handlers.","v":"ui-v2/real-data.js: discoverContent (POST /api/content/discover), scanRobots (POST /api/robots/scan), crawlerStart/crawlerStop (POST /api/crawler/start|stop); ui-v2/app.jsx DiscoverTab renders hits/disallowed/sitemapUrls per the control_server.cpp JSON shape.","o":"absent","r":"DISCOVER tab surfaces content-discovery, robots/sitemap recon, and crawler start/stop."},{"a":"target","f":"Content discovery: recursive descent into discovered directories (Burp's discovery recurses into every folder it finds)","s":"absent","i":"high","e":"days","g":"One directory level per invocation. Finding /admin never leads to /admin/users -- the tester must re-POST manually for each hit, which is the core of what Burp's engine automates.","w":"Confirmed by reading the loop. base is computed once and never reassigned; there is no queue, no depth field, and no re-entry into discover().","v":"content_discovery.cpp:96 `const QString base = normBase(req.basePath);` is still the sole assignment -- base is never reassigned into a discovered subdirectory. The probe loop (now :169-176, building a flat `probes` list fanned out across a concurrency pool added since the last pass) still has no queue of discovered directories and no re-entry into discover() -- the concurrency addition parallelizes the SAME flat wordlist, it does not add a second level.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-read the probe-building loop (moved 154-176 -> 169-176 after a concurrency-pool addition) -- still exactly one directory level per invocation, `base` assigned once, no depth field or requeue anywhere. The new concurrency/throttle controls speed up the flat scan, they do not add recursion. No code change this pass."},{"a":"target","f":"Content discovery: file-extension bruteforce (probe each word against a list of extensions) and filename mutation rules","s":"present","i":"medium","e":"hours","g":"None -- filename-mutation rules are built end-to-end: ContentDiscovery::mutateFilenames (content_logic.cpp) expands each candidate to word~, word.bak/.old/.orig/.save/.tmp/.1 and a dir-aware .leaf.swp, wired into discover() via req.mutations, exposed as a `mutations` boolean on POST /api/content/discover (control_server.cpp:9518), and now toggled from a \"filename mutations\" checkbox in ui-v2 DiscoverTab (sibling of the extensions field). The extension-bruteforce half already had its GUI field.","w":"CONFIRMED end-to-end. Backend: content_discovery.hpp Request::mutations (default false); content_discovery.cpp:101 `words = mutateFilenames(words, req.mutations)`; control_server.cpp:9518 `cr.mutations = bodyJson.value(\"mutations\").toBool(false)`. Frontend: ui-v2/app.jsx DiscoverTab now has a `mutations` boolean state + checkbox next to the extensions field, threaded through NL.actions.discoverContent(url, max, {..., mutations}) -> real-data.js POST body `mutations`. Both touched ui-v2 files transform cleanly under the bundled babel.","v":"ui-v2/app.jsx DiscoverTab `mutations` checkbox -> NL.actions.discoverContent opts.mutations; ui-v2/real-data.js discoverContent() posts `mutations`; control_server.cpp:9518 cr.mutations; content_discovery.cpp:101 mutateFilenames(words, req.mutations); content_discovery.hpp:51 bool mutations = false.","o":"present","r":"Wave 2 frontend wiring: added the ui-v2 `mutations` checkbox (DiscoverTab) that was the sole remaining gap on this item, closing it to present."},{"a":"target","f":"Content discovery results as a live tree merged into the site map, with the discovery session's own request count / status","s":"absent","i":"high","e":"days","g":"Discovered paths cannot be sent to Repeater, re-requested, or inspected. You get a status code and a byte count in a flat findings list, and the request that produced them is discarded.","w":"Confirmed. Hits become findings with rowId 0 and a JSON array; no history row is created, so nothing can reach the map. Corrected line numbers (8467-8480, not 8328-8339).","v":"control_server.cpp:9682-9697 `for (const auto &h : cres.hits) { hits.append(QJsonObject{ { \"path\", h.path }, { \"status\", h.status }, { \"size\", h.size }, { \"location\", h.location }, { \"note\", h.note } }); if (m_wiring.scanner) m_wiring.scanner->reportFinding(0, \"info\", \"content-discovered\", ...` -- still rowId 0, i.e. no history row, so nothing a discovered path produces can be sent to Repeater or re-requested. SiteMapModel still exposes no insertion API a discovery session could stream into.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. Re-read the hit-to-finding loop (moved 8467-8480 -> 9682-9697) -- still `reportFinding(0, ...)`, no history row, no site-map tree insertion, matching the prior pass's finding with refreshed line numbers only. No code change this pass."},{"a":"target","f":"Engagement tools > Analyze target (Target Analyzer): counts of static vs dynamic URLs, unique parameter names, and per-URL entry points across a site map branch","s":"partial","i":"low","e":"days","g":"Query-string parameter names only -- request bodies aren't held client-side, so form/JSON body parameter names never appear in the unique-parameter list or an entry point's params column, a real gap vs. Burp's whole-body-aware analyzer. Static/dynamic classification is also a URL-shape heuristic (recognized static extension + no query string), not Burp's own algorithm, so edge cases (e.g. a static-looking path served dynamically with no query) can misclassify.","w":"Closed the frontend half via a client-side ANALYZE TARGET overlay (ui-v2/proxy.jsx TargetAnalyzerOverlay) reached from the HTTP HISTORY pane-head, computed entirely from HTTP history rows already in state -- no backend endpoint needed or added, since r.path already carries the full path+query (control_server.cpp:1515-1516 map both \"url\" and \"path\" to ProxyModel::UrlRole, which is request.path verbatim). Pure helpers classifyUrlKind/queryParamNames/analyzeTargetSurface produce unique-URL, static, and dynamic counts, a unique query-parameter-name list (each tagged with the entry-point count it appears across), and a per-path entry-point table (methods + param names + kind), scoped to whatever the site-map tree currently has selected (a host, a branch, or all hosts) via the existing originRows the SiteMap/HistoryTable pair already computes -- so \"across a site map branch\" is a real, working scope, not just the whole history. Moved absent -> partial rather than present: body-parameter names are a genuine, honestly-named remaining gap (see gap text).","v":"ui-v2/proxy.jsx: classifyUrlKind/queryParamNames/analyzeTargetSurface (pure helpers) + TargetAnalyzerOverlay (new component) + an \"ANALYZE TARGET\" button in ProxyTab's HTTP HISTORY pane-head, wired to originRows (the same site-map-scoped row set HistoryTable/SiteMap already use) and selectedOrigin for the scope label. Field contract: r.path/r.method already present on every row (control_server.cpp:1515-1516 url/path -> ProxyModel::UrlRole -> proxy_model.cpp:22 request.path); no new fields invented, no backend endpoint added.","o":"partial","r":"Target Analyzer wave: client-side ANALYZE TARGET overlay in the Proxy tab closes the URL-count/parameter-name/entry-point legs of this item, scoped to the current site-map selection; body-parameter names stay an honest remaining gap."},{"a":"target","f":"Engagement tools > Simulate manual testing (generates decoy traffic)","s":"absent","i":"cosmetic","e":"days","g":"Missing. Rarely used; exists mainly to make an automated scan look human in target logs.","w":"Confirmed. Grepped for the feature name and for the concept (decoy/noise/synthetic traffic); the single 'decoy' hit is an unrelated comment about stale robots.txt directives.","v":"`grep -rlia \"decoy|simulate manual|manual testing simulat\" .` now matches 15 files (up from 1 at the prior pass, driven mostly by Lab 24's clickjacking PoC which legitimately uses \"decoy\" for its overlay button) -- every hit re-checked by hand is either the Lab 24 clickjacking PoC (labs/24-clickjacking/*, docs/labs/24-clickjacking.html, ui-v2/labs-data.js, scripts/labs_site.py, ui-v2/proxy.jsx's own clickjacking-PoC generator) or an unrelated code comment using \"decoy\" colloquially (js_recon_logic.cpp:144 stale-directive comment; ssrf_scan.hpp:74/ssrf_scan.cpp:201/ssrf_logic.cpp:58 \"decoy param\" in SSRF sink-detection comments; two test-file comments about a decoy secret/value in unrelated regression tests). None is a decoy-TRAFFIC-generation feature -- still nothing shipped that fires synthetic background traffic to disguise an automated scan.","o":"absent","r":"Wave 0 register-accuracy audit: held at absent. The literal grep now returns far more hits than the prior pass's \"exactly one file\" (new labs and comments added \"decoy\" in unrelated senses since), so re-checked every match by hand rather than trusting the count -- all are Lab 24's clickjacking PoC or unrelated SSRF/regression-test comments. No decoy-traffic feature exists. No code change this pass."},{"a":"target","f":"Engagement tools > Schedule task (run a scan/crawl at a set time or interval)","s":"absent","i":"low","e":"days","g":"No in-app scheduling and no shipped scheduled job. A user would have to write their own cron around --scan, and there is no crawl/discovery equivalent to schedule anyway.","w":"Confirmed, and I tightened the compensating-control claim. The first pass said the CI direction partly compensates; the shipped workflow is workflow_dispatch (manual) only, with no cron: schedule block, so nothing shipped schedules anything.","v":"`grep -rain \"schedul|cron|recurring\" Src/BackEnd/Control/control_server.cpp` -> no matches. .github/workflows/nullock-scan-example.yml:5-8 `# Manual-dispatch only so it never runs against a target without an explicit opt-in.` / `on:` / `  workflow_dispatch:` -- no `schedule:` key anywhere in the file. The CLI gate it drives is one-shot: Src/App/app.cpp:658-661 `if (!scanUrl.isEmpty()) { ... return","o":"absent","r":"Wave 0 register-accuracy audit: held at absent, verbatim. Re-ran both greps: `schedul|cron|recurring` (case-insensitive, proper alternation) against control_server.cpp still returns zero matches, and `.github/workflows/nullock-scan-example.yml` still declares only `workflow_dispatch:` with no `schedule:` key. No code change this pass."},{"a":"target","f":"Qt desktop Target UI (the project ships a Qt6 front end as well as the browser UI)","s":"partial","i":"low","e":"weeks","g":"Real, but the same flat host list and host-glob scope as ui-v2 -- no tree, no per-node issues, no context menu, no annotations. The misleading part is the repo layout, not the capability: the four blank Components files read as an unfinished Target UI while the finished one lives in app.qml. Also carries the relative-path load bug for installed builds.","w":"UPGRADED, and this is the first pass's largest error. It read the four 8-line placeholder .qml files and concluded the Qt Target UI is blank. Those files are dead scaffolding -- registered in the QML module but never instantiated. The QML the app actually LOADS is Src/App/app.qml, which contains a working Site Map pane bound to the siteMap model and a complete Scope tab with both lists and add/rem","v":"The loaded file: Src/App/app.cpp:1485-1487 `// run from project root so this relative path resolves to Nullock/Src/App/app.qml` / `const QUrl url(QStringLiteral(\"./Src/App/app.qml\"));` / `engine.load(url);`. Working site map, app.qml:159 `HeaderCell { text: \"Site Map (\" + siteMap.rowCount() + \")\"; ... }` with a bound ListView beneath it; the Scope tab (app.qml:111 TabHeader, :428 onward) has real in-scope/out-of-scope lists bound to `projectStore.inScopeList`/`outOfScopeList` with add/remove wired to `projectStore.addInScope`/`removeInScope` -- still the same flat host list and host-glob scope as ui-v2, no tree, no per-node issues, no context menu.","o":"partial","r":"Wave 0 register-accuracy audit: held at partial (the prior pass's UPGRADE from absent-looking to a real, if limited, Qt Target UI stands). Re-verified app.cpp still loads ./Src/App/app.qml by relative path (line moved 1159-1161 -> 1485-1487, same relative-path-for-installed-builds bug) and app.qml's site map + scope tab are functionally unchanged. No code change this pass."},{"a":"platform","f":"AI payload generator (local Ollama mutates a seed payload set into novel-but-shaped variants on demand) -- Burp has no equivalent, an extension is required for any AI payload assist","s":"present","i":"medium","e":"hours","g":"None -- the PAYLOADS tab's AI GENERATE control (count field + button) calls the endpoint and renders the returned payloads (or the seed-list fallback with a clear \"ollama unreachable\" badge) alongside the existing static Payload Forge list.","w":"The backend endpoint (control_server.cpp /api/payloads/generate) existed but had no ui-v2 caller anywhere -- confirmed by grep across ui-v2/*.jsx and real-data.js before this change. Closed by wiring it: NL.actions.aiGeneratePayloads(kind, count) in real-data.js, and an AI generate section in PayloadsTab (app.jsx) that reuses the technique already selected for the static forge, shows the model name on success, and distinguishes the deterministic fallback (ok:false, fallback:true) from a genuine model response.","v":"ui-v2/real-data.js aiGeneratePayloads() -> POST /api/payloads/generate {kind,count}; ui-v2/app.jsx PayloadsTab's aiGenerate()/aiData state + render block reading aiData.payloads/model/fallback, matching control_server.cpp's response shape verbatim ({ok,model,payloads} or {ok:false,fallback:true,model,payloads,error}).","o":"present","r":"Wired the previously-orphaned /api/payloads/generate (AI payload mutation via local Ollama) into the PAYLOADS tab: a count field + AI GENERATE button, rendering the model's variants or the deterministic seed-list fallback with a distinct badge."}]</script>
 <script>
 (function () {
   "use strict";
@@ -141,7 +142,7 @@ <h2>How this stays true</h2>
 
       var body = el("div", "rm-body"); body.hidden = true;
       if (d.o && d.o !== d.s) {
-        body.appendChild(el("div", "rm-moved mono", "closed since audit: " + d.o + " \u2192 " + d.s));
+        body.appendChild(el("div", "rm-moved mono", "changed since audit: " + d.o + " \u2192 " + d.s));
       }
       if (d.r) { var p0 = el("p", "rm-note", d.r); body.appendChild(p0); }
       if (d.g) { body.appendChild(el("h4", null, "Gap")); body.appendChild(el("p", null, d.g)); }
diff --git a/docs/roadmap/parity.json b/docs/roadmap/parity.json
index 1ba255ba..bcd5068f 100644
--- a/docs/roadmap/parity.json
+++ b/docs/roadmap/parity.json
@@ -4843,17 +4843,18 @@
     {
       "area": "repeater",
       "feature": "Repeater: out-of-scope send guard",
-      "state": "exceeds",
+      "state": "present",
       "impact": "low",
       "effort": "hours",
-      "gap": "The guard protects the browser UI and the CLI (the paths that matter) but not the Qt desktop Send button, which invokes Repeater::send() directly. There is also a narrow TOCTOU: the check reads the ACTIVE tab's host, then the send is posted with Qt::QueuedConnection, so a scripted client can activate a different tab between the two.",
-      "why": "The guard is real and refuses the send (Burp Repeater has no scope enforcement at all), so 'exceeds' holds. But I found a bypass the auditor missed: the check lives in the HTTP handler, not in Repeater::send(), and the Qt desktop Send button calls the Q_INVOKABLE directly.",
-      "evidence": "Src/BackEnd/Control/control_server.cpp:3557-3558 `if (path == \"/api/repeater/send\") {\\n        if (m_wiring.repeater && blocksScope(m_wiring.repeater->host()))`. `blocksScope` at control_server.cpp:1263-1265 `return m_wiring.proxy && !host.isEmpty() && !m_wiring.proxy->isInScope(host);` -- out-of-scope wins via ProxyServer::isInScope. Confirmed the bypass still holds: Src/Core/Networking/repeater.cpp:135 `Repeater::send()` has no scope check at all -- only the HTTP control-server path (used by the browser UI and CLI) enforces it; the Qt desktop Send button calling the Q_INVOKABLE directly would skip it.",
+      "gap": "Shared outbound scope checks protect the actual destination, port, protocol and path before each HttpClient connection, including redirects. The former API-only bypass and queued-tab-switch descriptions are obsolete. Native QML sends still block the UI; that separate responsiveness gap is tracked under cancellation.",
+      "why": "HttpClient::send checks OutboundScope before connecting, so direct Repeater::send calls also use the registered project policy. The API performs its early host check and synchronously copies the active request into sendAsync before scheduling the worker. Live regressions verify path, port, scheme, redirects and dynamic scope edits.",
+      "evidence": "Src/Core/Networking/networking.cpp HttpClient::send; Src/Core/Networking/outbound_scope.cpp; Src/App/app.cpp OutboundScope::Registration; Src/BackEnd/Control/control_server.cpp /api/repeater/send; Src/Core/Networking/repeater.cpp sendAsync; scripts/outbound_scope_regression.py (41 checks).",
       "reconciled": {
-        "date": "2026-08-27",
-        "commit": "",
-        "note": "Wave 0 register-accuracy audit: re-verified against live source (symbol/line spot-check across the referenced files) -- no code change, register was already correct; refreshed evidence line numbers that had drifted from intervening waves and this closes the missing audit trail (audited_state + reconciled) that Wave 0 exists to add."
-      }
+        "date": "2026-09-29",
+        "commit": "927aed0e",
+        "note": "Rechecked the existing shared scope implementation and reran 41 live scope checks. Removed obsolete API-only and queued-tab-switch claims; use present rather than an unverified comparison-based exceeds grade."
+      },
+      "audited_state": "exceeds"
     },
     {
       "area": "repeater",
@@ -5459,13 +5460,13 @@
       "state": "partial",
       "impact": "high",
       "effort": "days",
-      "gap": "Send runs on a worker and the UI remains responsive. Stop marks cancellation and prevents later redirects after the current response finishes; it does not immediately abort a stalled socket. One request can run at a time across all tabs.",
-      "why": "sendAsync copies the request into a worker and applies the result without replacing newer edits. Browser/API Stop and the CLI stop command share the cancellation flag. Live API and browser regressions verify responsiveness, busy state, draft preservation and redirect cancellation.",
-      "evidence": "Src/Core/Networking/repeater.cpp sendAsync/cancel; ui-v2/tabs.jsx Repeater Stop; bin/nullock repeater stop; scripts/control_responsiveness_regression.py; Tests/ui/repeater_responsiveness_browser_test.cjs; scripts/repeater_cli_test.py.",
+      "gap": "Browser/API/CLI sends run on a worker and remain responsive. Native QML still calls synchronous send directly. Stop marks cancellation and prevents later redirects after the current response; it does not immediately abort a stalled socket. One asynchronous request can run at a time across all tabs.",
+      "why": "sendAsync copies the request into a worker and applies the result without replacing newer edits. Browser/API Stop and CLI stop share the cancellation flag. Live API/browser regressions cover those paths; Src/App/app.qml uses repeater.send() and has no Stop affordance.",
+      "evidence": "Src/Core/Networking/repeater.cpp sendAsync/cancel; ui-v2/tabs.jsx Repeater Stop; bin/nullock repeater stop; scripts/control_responsiveness_regression.py; Tests/ui/repeater_responsiveness_browser_test.cjs; scripts/repeater_cli_test.py. Src/App/app.qml native Repeater Send handler.",
       "reconciled": {
         "date": "2026-09-29",
         "commit": "c2af0a33",
-        "note": "Reconciled against current source and focused CLI, application and browser checks. Correct stale behavior/evidence and state the remaining limits. Grade changed from absent to partial."
+        "note": "Reconciled browser/API/CLI asynchronous sends and Stop, while recording the native QML synchronous-send path separately. Immediate socket cancellation and concurrent sends remain incomplete; grade stays partial."
       }
     },
     {
diff --git a/scripts/parity_report.py b/scripts/parity_report.py
index 0556c334..4a549a31 100644
--- a/scripts/parity_report.py
+++ b/scripts/parity_report.py
@@ -1,7 +1,7 @@
 #!/usr/bin/env python3
 """Generate docs/roadmap/index.html -- the Nullock-vs-Burp parity roadmap.
 
-WHAT THIS IS FOR. docs/roadmap/parity.json holds 409 Burp Suite capabilities,
+WHAT THIS IS FOR. docs/roadmap/parity.json holds the Burp Suite capabilities,
 each graded against Nullock's actual source. It is not a one-off report: it is
 the ROADMAP. Everything not yet `present` or `exceeds` is the remaining work, in
 priority order, and every commit that closes a gap is expected to update the
@@ -56,10 +56,10 @@ def build(doc):
     done = counts["present"] + counts["exceeds"]
     total = len(items)
     pct = round(done * 100.0 / total)
-    # Newest first: a just-closed gap must land at the TOP of "Recently closed",
+    # Newest first: a reconciled entry belongs at the top of "Recently updated",
     # not wherever it happens to sit in parity.json's array order. Dates are ISO
     # (YYYY-MM-DD) so a string sort is chronological; a missing/blank date sorts
-    # last. Python's sort is stable, so same-day closes keep their array order.
+    # last. Python's sort is stable, so same-day updates keep their array order.
     reconciled = sorted(
         (i for i in items if "reconciled" in i),
         key=lambda i: (i.get("reconciled") or {}).get("date", ""),
@@ -118,7 +118,7 @@ def build(doc):
                     "the full set is in the capability table below." % (RECENT_CAP, len(reconciled)))
         recent = ("""<section class="panel">
     <h2>Recently updated</h2>
-    <p class="muted" style="font-size:13.5px;">Capabilities reconciled since the audit, including closed gaps and corrections, newest first. Each entry records its date and implementation commit.%s</p>
+    <p class="muted" style="font-size:13.5px;">Capabilities reconciled since the audit, including closed gaps and corrections, newest first. Each entry records its date and source or verification commit.%s</p>
     <ul class="rm-recent">%s</ul>
   </section>""" % (cap_note, rows))
 
@@ -180,6 +180,7 @@ def build(doc):
 
   <section class="panel">
     <h2>Where the work is</h2>
+    <p>Start with the <a href="https://github.com/Bikebrainz/Nullock/blob/Nullock/docs/reviews/2026-09-29-build-follow-up.md">September 29 build follow-up</a> for reproduced gaps, priorities and acceptance checks.</p>
     <p class="muted" style="font-size:13.5px;">One bar per functional area, ordered worst-first. Click an area to filter the register.</p>
     <div class="rm-matrix">%s</div>
     <div class="rm-legend">%s</div>
@@ -270,7 +271,7 @@ def build(doc):
 
       var body = el("div", "rm-body"); body.hidden = true;
       if (d.o && d.o !== d.s) {
-        body.appendChild(el("div", "rm-moved mono", "closed since audit: " + d.o + " \\u2192 " + d.s));
+        body.appendChild(el("div", "rm-moved mono", "changed since audit: " + d.o + " \\u2192 " + d.s));
       }
       if (d.r) { var p0 = el("p", "rm-note", d.r); body.appendChild(p0); }
       if (d.g) { body.appendChild(el("h4", null, "Gap")); body.appendChild(el("p", null, d.g)); }

From 2551e6bcd7e7cfd083b3f449af9b45641c73270e Mon Sep 17 00:00:00 2001
From: Bikebrainz <133275931+Bikebrainz@users.noreply.github.com>
Date: Tue, 29 Sep 2026 02:40:02 -0600
Subject: [PATCH 2/9] Clarify draft release status and final verification
 evidence

---
 CHANGELOG.md                               |  2 ++
 docs/changelog.html                        |  6 +++---
 docs/docs/index.html                       |  4 ++--
 docs/reviews/2026-09-29-build-follow-up.md | 10 +++++++---
 4 files changed, 14 insertions(+), 8 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index ce5c9ceb..a98d45fd 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -12,6 +12,8 @@ developer-facing record.
 
 ### Build follow-up
 - Add the September 29 to-do list with reproduced gaps and acceptance checks.
+- Correct website release labels: v3.7.0 is the latest public release; v3.8.0
+  remains an unpublished draft.
 - Correct stale scope-enforcement evidence and distinguish native QML Send
   behavior from asynchronous browser/API/CLI sends.
 - Label roadmap grade changes as changes, including downward corrections.
diff --git a/docs/changelog.html b/docs/changelog.html
index b25dc8ea..9e3bf26b 100644
--- a/docs/changelog.html
+++ b/docs/changelog.html
@@ -50,7 +50,7 @@ <h1 class="h1-page grad-text" style="margin:10px 0 0;">What shipped</h1>
           <span class="badge"><span class="dot"></span>development</span>
         </div>
         <div class="rel-body">
-          <p class="rel-note">Security checks now distinguish effective response headers from malformed lookalikes. These changes are in the development build; v3.8.0 remains the latest release listed below.</p>
+          <p class="rel-note">Security checks now distinguish effective response headers from malformed lookalikes. These changes are in the development build; v3.7.0 remains the latest public release, and the v3.8.0 notes below are a draft.</p>
           <ul>
             <li><span class="tag fix">fix</span> <strong>Build follow-up and roadmap corrections.</strong> The <a href="https://github.com/Bikebrainz/Nullock/blob/Nullock/docs/reviews/2026-09-29-build-follow-up.md">September 29 checklist</a> records remaining byte-fidelity, HTML-context, cancellation, fixture-isolation and certificate-lifecycle work. Scope enforcement evidence is refreshed, and the native window's blocking Send path is called out separately.</li>
             <li><span class="tag fix">fix</span> <strong>Request files keep their binary bodies.</strong> Repeater CLI file and stdin loading preserves NUL bytes, non-UTF-8 data and trailing newlines. Invalid input leaves the draft unchanged; an empty file explicitly clears it. Tab summaries distinguish fresh tabs from completed responses, and duplicated tabs clear their old response metadata. Empty drafts and blank targets are rejected instead of reporting an old response as a successful send.</li>
@@ -71,8 +71,8 @@ <h1 class="h1-page grad-text" style="margin:10px 0 0;">What shipped</h1>
       <article class="rel">
         <div class="rel-meta">
           <span class="rel-ver">v3.8.0</span>
-          <span class="caption">Aug 20, 2026</span>
-          <span class="badge"><span class="dot"></span>released</span>
+          <span class="caption">Draft notes &middot; Aug 20, 2026</span>
+          <span class="badge"><span class="dot"></span>unpublished draft</span>
         </div>
         <div class="rel-body">
           <p class="rel-note">The pre-launch blocker push &mdash; five of the first-hour blockers fixed: scan findings and Repeater tabs now survive app close and project reopen, Repeater auto-updates Content-Length, the proxy can bind off-loopback for device testing, and interception is now rule-driven &mdash; alongside a detector-hardening pass over the passive scanner (mutation-proven regression coverage around every finding kind), the false-negative bugs those tests surfaced, and new Burp-parity features on the roadmap.</p>
diff --git a/docs/docs/index.html b/docs/docs/index.html
index 7b77406d..dc46eae5 100644
--- a/docs/docs/index.html
+++ b/docs/docs/index.html
@@ -57,7 +57,7 @@
 
   <!-- CONTENT -->
   <main class="docs-content">
-    <p class="eyebrow">// docs · v3.8.0</p>
+    <p class="eyebrow">// docs · development build</p>
     <h1 class="h1-page" style="margin:8px 0 0;">Documentation</h1>
     <p class="lead" style="margin:14px 0 0;">Self-host first. Everything here runs on your machine, offline, with no account.</p>
 
@@ -86,7 +86,7 @@ <h2 class="h2-section">Install</h2>
 <span class="c-purple">cmake</span> --build build --target NullockApp</pre>
       </div>
       <p>On first run the app generates a local CA and prints its path. Download its public certificate from Settings → CA &amp; TLS and trust it in a dedicated test browser when you need HTTPS interception. Nullock does not automatically modify the OS trust store.</p>
-      <p>Sections marked <strong>unreleased</strong> describe the current development build and supplied beta packages. They may not be included in the latest public release. See the <a href="https://github.com/Bikebrainz/Nullock#readme">repository build instructions</a> for platform prerequisites.</p>
+      <p>Sections marked <strong>unreleased</strong> describe the current development build and supplied beta packages. The latest public release is <a href="https://github.com/Bikebrainz/Nullock/releases/tag/v3.7.0">v3.7.0</a>; v3.8.0 remains an unpublished draft. See the <a href="https://github.com/Bikebrainz/Nullock#readme">repository build instructions</a> for platform prerequisites.</p>
     </section>
 
     <section id="first-capture" class="doc-sec">
diff --git a/docs/reviews/2026-09-29-build-follow-up.md b/docs/reviews/2026-09-29-build-follow-up.md
index 36919fe7..ee605059 100644
--- a/docs/reviews/2026-09-29-build-follow-up.md
+++ b/docs/reviews/2026-09-29-build-follow-up.md
@@ -12,11 +12,13 @@ session. An unchecked item is not implemented.
 | Effective security headers and strict TLS certificate compatibility | [#21](https://github.com/Bikebrainz/Nullock/pull/21) | Merged |
 | Reflected-XSS media types and HTML boundaries; certificate-cache validation | [#22](https://github.com/Bikebrainz/Nullock/pull/22) | CI pending |
 | Stable history IDs, asynchronous CLI send polling and Stop | [#25](https://github.com/Bikebrainz/Nullock/pull/25) | CI pending |
-| Binary file/stdin requests and accurate tab response indicators | [#26](https://github.com/Bikebrainz/Nullock/pull/26) | CI pending |
+| Binary file/stdin requests, tab indicators and empty-send rejection | [#26](https://github.com/Bikebrainz/Nullock/pull/26) | CI pending |
 
 Every implementation PR also updates the public changelog and roadmap. These
 are development changes; they do not create a release or change the latest
-published version. Certificate details from #23 and HTML-context details from
+published version. GitHub release metadata checked on September 29 identifies
+v3.7.0 as the latest public release and v3.8.0 as an unpublished draft.
+Certificate details from #23 and HTML-context details from
 #24 were incorporated into #22.
 
 ## Next work, in priority order
@@ -139,7 +141,9 @@ blocking Send behavior is a separate issue described above.
   additional 1,238 generated media-type comparisons found no mismatches.
 - CLI fixtures and real-app checks cover stable IDs, binary history bodies,
   multiple busy polls, refusal/timeouts, Stop, binary files/stdin, UTF-8, invalid
-  base64 and fresh/completed/duplicated tab indicators.
+  base64, empty-send rejection and fresh/completed/duplicated tab indicators.
+  The final CLI build also passed all 102 native suites and 20 control
+  responsiveness checks.
 - Website checks cover links, script integrity, generated-page freshness and
   desktop/mobile roadmap and changelog layout.
 

From 5764e47a18d665965efea9b40844b3690679379a Mon Sep 17 00:00:00 2001
From: Bikebrainz <133275931+Bikebrainz@users.noreply.github.com>
Date: Tue, 29 Sep 2026 02:41:08 -0600
Subject: [PATCH 3/9] Identify unpublished release notes in both changelogs

---
 CHANGELOG.md        | 4 +++-
 docs/changelog.html | 2 +-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index a98d45fd..257d409c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1659,7 +1659,9 @@ developer-facing record.
   the mechanism the doc comment always described actually produces a report
   now instead of only ever being reachable from a crash signal.
 
-## [3.8.0] — 2026-08-20
+## 3.8.0 — unpublished draft
+
+Notes prepared August 20, 2026. This version has not been published as a GitHub release.
 
 This release folds in a large security-and-correctness pass: a whole-codebase
 security review (16 findings, from a CRITICAL CI-action fix down to
diff --git a/docs/changelog.html b/docs/changelog.html
index 9e3bf26b..5aa2722f 100644
--- a/docs/changelog.html
+++ b/docs/changelog.html
@@ -149,7 +149,7 @@ <h1 class="h1-page grad-text" style="margin:10px 0 0;">What shipped</h1>
       <article class="rel">
         <div class="rel-meta">
           <span class="rel-ver">v3.7.0</span>
-          <span class="caption">Jul 5, 2026</span>
+          <span class="caption">Published Jul 21, 2026</span>
           <span class="badge ok"><span class="dot"></span>latest</span>
         </div>
         <div class="rel-body">

From 325c3a6d5533879fa5028348bcee852b9d9f9d9a Mon Sep 17 00:00:00 2001
From: Bikebrainz <133275931+Bikebrainz@users.noreply.github.com>
Date: Tue, 29 Sep 2026 02:45:33 -0600
Subject: [PATCH 4/9] Record merged build fixes in the follow-up checklist

---
 docs/reviews/2026-09-29-build-follow-up.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/reviews/2026-09-29-build-follow-up.md b/docs/reviews/2026-09-29-build-follow-up.md
index ee605059..3379c452 100644
--- a/docs/reviews/2026-09-29-build-follow-up.md
+++ b/docs/reviews/2026-09-29-build-follow-up.md
@@ -10,8 +10,8 @@ session. An unchecked item is not implemented.
 | Change | Pull request | Status |
 | --- | --- | --- |
 | Effective security headers and strict TLS certificate compatibility | [#21](https://github.com/Bikebrainz/Nullock/pull/21) | Merged |
-| Reflected-XSS media types and HTML boundaries; certificate-cache validation | [#22](https://github.com/Bikebrainz/Nullock/pull/22) | CI pending |
-| Stable history IDs, asynchronous CLI send polling and Stop | [#25](https://github.com/Bikebrainz/Nullock/pull/25) | CI pending |
+| Reflected-XSS media types and HTML boundaries; certificate-cache validation | [#22](https://github.com/Bikebrainz/Nullock/pull/22) | Merged |
+| Stable history IDs, asynchronous CLI send polling and Stop | [#25](https://github.com/Bikebrainz/Nullock/pull/25) | Merged |
 | Binary file/stdin requests, tab indicators and empty-send rejection | [#26](https://github.com/Bikebrainz/Nullock/pull/26) | CI pending |
 
 Every implementation PR also updates the public changelog and roadmap. These

From 4987314f8c3c6f4b95769b0cfca125d86fce2ee4 Mon Sep 17 00:00:00 2001
From: Bikebrainz <133275931+Bikebrainz@users.noreply.github.com>
Date: Tue, 29 Sep 2026 02:46:43 -0600
Subject: [PATCH 5/9] Include release-label verification in the follow-up
 checklist

---
 docs/reviews/2026-09-29-build-follow-up.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/reviews/2026-09-29-build-follow-up.md b/docs/reviews/2026-09-29-build-follow-up.md
index 3379c452..6f6b6211 100644
--- a/docs/reviews/2026-09-29-build-follow-up.md
+++ b/docs/reviews/2026-09-29-build-follow-up.md
@@ -123,6 +123,8 @@ key permissions and test both OpenSSL and LibreSSL certificate generation.
   their implementations differ.
 - [ ] Require a runnable regression or a precise source reference for each
   reconciliation; retain limitations instead of inferring full parity.
+- [ ] When publishing a release, update draft/latest labels and public dates
+  against the GitHub release metadata as part of the same release checklist.
 
 This pass corrects the obsolete Repeater scope-bypass claim: the shared
 `HttpClient` checks outbound scope before connecting, including redirects, and

From 7b42056c92aeb599c28a9af8959526bd07561274 Mon Sep 17 00:00:00 2001
From: Bikebrainz <133275931+Bikebrainz@users.noreply.github.com>
Date: Tue, 29 Sep 2026 02:49:12 -0600
Subject: [PATCH 6/9] Record Windows OAST listener ownership reproduction

---
 docs/reviews/2026-09-29-build-follow-up.md | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/docs/reviews/2026-09-29-build-follow-up.md b/docs/reviews/2026-09-29-build-follow-up.md
index 6f6b6211..fd283449 100644
--- a/docs/reviews/2026-09-29-build-follow-up.md
+++ b/docs/reviews/2026-09-29-build-follow-up.md
@@ -86,16 +86,23 @@ newer edits survive completion, and shutdown joins the worker cleanly.
 - [ ] Allocate separate HTTP and DNS sink ports for each smoke run, alongside
   the control/proxy ports, and verify startup on the requested listeners.
 - [ ] Report callback failures from the mock instead of discarding exceptions.
-- [ ] Check concurrent isolated runs and deliberate port conflicts.
+- [ ] Check concurrent isolated runs and deliberate IPv4/IPv6 port conflicts.
+- [ ] Verify that a callback to the advertised address reaches this app; a
+  running flag alone is insufficient on the reproduced Windows bind path.
 
 **Evidence:** one integrated run passed 193 checks and missed three HTTP OAST
 callbacks (SSRF, RCE and XXE); an isolated retry passed all 196. The cause of
 that first failure is not established. `scripts/probe_smoke.sh` uses the default
-OAST ports and suppresses exceptions from its HTTP callback mock.
+OAST ports and suppresses exceptions from its HTTP callback mock. In a separate
+controlled Windows experiment, occupying the requested port on IPv4 loopback
+left the app reporting `oast.running=true`, while a request to its advertised
+IPv4 address reached the pre-existing owned fixture. Occupying that port on a
+dual-stack listener instead left `running=false, port=0` while the control API
+remained available. Neither experiment proves the earlier transient cause.
 
 **Done when:** concurrent runs do not share sinks or state, listener failures
-produce a clear startup error, and callback diagnostics identify the failed
-operation. Retain token-specific positive assertions and safe-target negative
+produce a clear startup error, and a minted callback confirms ownership of the
+advertised address. Callback diagnostics must identify the failed operation. Retain token-specific positive assertions and safe-target negative
 controls; do not replace them with longer blind waits or automatic pass-on-retry.
 
 ### 5. Complete CA and certificate-cache lifecycle controls

From 0b7cc2d40eb16d0e6dcaf925d860a977ade48493 Mon Sep 17 00:00:00 2001
From: Bikebrainz <133275931+Bikebrainz@users.noreply.github.com>
Date: Tue, 29 Sep 2026 02:50:00 -0600
Subject: [PATCH 7/9] Summarize the current development changes in the public
 changelog

---
 docs/changelog.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/changelog.html b/docs/changelog.html
index 5aa2722f..3e6561ab 100644
--- a/docs/changelog.html
+++ b/docs/changelog.html
@@ -50,7 +50,7 @@ <h1 class="h1-page grad-text" style="margin:10px 0 0;">What shipped</h1>
           <span class="badge"><span class="dot"></span>development</span>
         </div>
         <div class="rel-body">
-          <p class="rel-note">Security checks now distinguish effective response headers from malformed lookalikes. These changes are in the development build; v3.7.0 remains the latest public release, and the v3.8.0 notes below are a draft.</p>
+          <p class="rel-note">The development build includes corrected security checks, certificate-cache validation and Repeater CLI fixes; v3.7.0 remains the latest public release, and the v3.8.0 notes below are a draft.</p>
           <ul>
             <li><span class="tag fix">fix</span> <strong>Build follow-up and roadmap corrections.</strong> The <a href="https://github.com/Bikebrainz/Nullock/blob/Nullock/docs/reviews/2026-09-29-build-follow-up.md">September 29 checklist</a> records remaining byte-fidelity, HTML-context, cancellation, fixture-isolation and certificate-lifecycle work. Scope enforcement evidence is refreshed, and the native window's blocking Send path is called out separately.</li>
             <li><span class="tag fix">fix</span> <strong>Request files keep their binary bodies.</strong> Repeater CLI file and stdin loading preserves NUL bytes, non-UTF-8 data and trailing newlines. Invalid input leaves the draft unchanged; an empty file explicitly clears it. Tab summaries distinguish fresh tabs from completed responses, and duplicated tabs clear their old response metadata. Empty drafts and blank targets are rejected instead of reporting an old response as a successful send.</li>

From 69b8f6a50ef3a8856229a59b7884039e098a7440 Mon Sep 17 00:00:00 2001
From: Bikebrainz <133275931+Bikebrainz@users.noreply.github.com>
Date: Tue, 29 Sep 2026 02:53:29 -0600
Subject: [PATCH 8/9] Record final native-window and runtime validation

---
 docs/reviews/2026-09-29-build-follow-up.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/reviews/2026-09-29-build-follow-up.md b/docs/reviews/2026-09-29-build-follow-up.md
index fd283449..69ebf23f 100644
--- a/docs/reviews/2026-09-29-build-follow-up.md
+++ b/docs/reviews/2026-09-29-build-follow-up.md
@@ -144,8 +144,8 @@ blocking Send behavior is a separate issue described above.
 - Native suites: 102 passed on the combined XSS/certificate implementation.
 - Public probe smoke: 196 passed on the isolated rerun; the earlier OAST misses
   remain recorded above.
-- Strict TLS and runtime regressions: 64 checks with the native-window option;
-  the later CLI build also passed 62 headless runtime checks.
+- Strict TLS and runtime regressions: all 64 checks, including native-window
+  startup, passed on the final CLI build.
 - Pinned Chromium: 72 media-type and 95 HTML-context comparisons passed. An
   additional 1,238 generated media-type comparisons found no mismatches.
 - CLI fixtures and real-app checks cover stable IDs, binary history bodies,

From 1ed7abd3fe5de81a08d060d8b143e2d06b55ceac Mon Sep 17 00:00:00 2001
From: Bikebrainz <133275931+Bikebrainz@users.noreply.github.com>
Date: Tue, 29 Sep 2026 03:08:37 -0600
Subject: [PATCH 9/9] Record all completed implementation merges in the to-do
 handoff

---
 docs/reviews/2026-09-29-build-follow-up.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docs/reviews/2026-09-29-build-follow-up.md b/docs/reviews/2026-09-29-build-follow-up.md
index 69ebf23f..172c285b 100644
--- a/docs/reviews/2026-09-29-build-follow-up.md
+++ b/docs/reviews/2026-09-29-build-follow-up.md
@@ -12,9 +12,10 @@ session. An unchecked item is not implemented.
 | Effective security headers and strict TLS certificate compatibility | [#21](https://github.com/Bikebrainz/Nullock/pull/21) | Merged |
 | Reflected-XSS media types and HTML boundaries; certificate-cache validation | [#22](https://github.com/Bikebrainz/Nullock/pull/22) | Merged |
 | Stable history IDs, asynchronous CLI send polling and Stop | [#25](https://github.com/Bikebrainz/Nullock/pull/25) | Merged |
-| Binary file/stdin requests, tab indicators and empty-send rejection | [#26](https://github.com/Bikebrainz/Nullock/pull/26) | CI pending |
+| Binary file/stdin requests, tab indicators and empty-send rejection | [#26](https://github.com/Bikebrainz/Nullock/pull/26) | Merged |
 
-Every implementation PR also updates the public changelog and roadmap. These
+Each implementation PR passed all eight CI jobs on its reviewed head before
+merge. Every implementation PR also updates the public changelog and roadmap. These
 are development changes; they do not create a release or change the latest
 published version. GitHub release metadata checked on September 29 identifies
 v3.7.0 as the latest public release and v3.8.0 as an unpublished draft.