v4.3.0: web console parity + report redaction + per-finding wire evidence & re-test

Harness / CLI
- redact: credentials become $SECRET_n in every human-facing report
  (md/html/json/sarif/typ, findings.md); findings.json & vault keep raw values.
- poc: `--only <id> --json` re-tests a single finding (powers the web Re-test).
- version bump 4.2.4 → 4.3.0 (Cargo, CLI banner, web).

Web console
- Attack graph replaces "Generative Attack Path Chaining": one tab, findings
  ordered by kill-chain stage, click a finding to open it. Mounted in detail + live.
- Finding modal: Wire evidence — the real request/response pairs behind a finding
  (baseline/attack, identity pair, matrix probes, oracle) with wire provenance,
  the wire-check summary, and recorded flows on the same endpoint.
- Per-finding Re-test with dated history (reproduced/changed/gone/unverifiable).
- Transcript viewer in the Traces tab (navigable blocks; search spans all agents).
- Regression vs the previous run of the same target: new / recurring badges and a
  "fixed since" banner.
- Chains tab: readable formatting (node refs as chips, relations as labels).
- Custom lead: describe-it (Claude writes it) OR paste your own agent/system
  prompt (verbatim); remove a custom lead from the board.
- GDPR added to compliance mapping; LLM API keys tab clarified; Reasoning-budget
  and Authorization layouts fixed; NeuroSploit logo added.

Docs / config
- README rewritten as a concise landing page; TUTORIAL.md updated to v4.3.0 with
  new web/graph/Neo4j/wire sections and first-time configuration.
- .env.example: v4.3.0, Z.ai/Moonshot keys, Neo4j + graph-salt + capability env.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

web/README.md

@@ -18,6 +18,15 @@ CLI binary, never a reimplementation of harness logic.
   credential → impact, every edge marked confirmed / needs validation / hypothesis, findings ordered
   by kill-chain stage. Refreshed live at each graph checkpoint; click a finding to open it. Chains
   and Dependencies list the same paths as text and as the step-by-step todolist.
+- **Wire evidence in the finding** — the finding modal shows the real request/response pairs the
+  harness measured (baseline vs. attack, the identity pair, matrix probes, the oracle), each tagged
+  with its wire provenance, plus the finding's wire-check summary and any recorded flow on the same
+  endpoint. The proof as bytes, not as the agent's prose.
+- **Per-finding re-test with history** — ⟳ Re-test re-runs one finding's recorded proof through the
+  scope-guarded replay engine and keeps a dated history (reproduced / changed / gone / unverifiable),
+  so a finding drifting to "gone" over time is visible. Nothing is written back to the findings.
+- **Transcript viewer** — the Traces tab renders a chosen agent's transcript split into navigable,
+  collapsible blocks at each tool-call / HTTP-request boundary; search still spans every agent.
 - **Terminal dock (xterm.js)** — `❭_` in the sidebar, the topbar button, or `Ctrl+\`` opens a
   docked terminal running a real `neurosploit` REPL session. Its stdout is streamed **unstripped**,
   so the harness's own colour and box-drawn panels render as they do in a local shell. Line