merge: integrate feat/backlog-burndown into master

master had advanced 16 commits past feat/backlog-burndown's base, and the two
branches independently built four of the same features. Resolved 26 conflicts.

Overlap features — kept master's implementation (more complete / production-wired /
more robust), dropped the feature branch's parallel constellation:
- llama-server health probe: kept master's event-store-backed tps probe; dropped the
  branch's LlamaLivenessClient (liveness-only, throughput unwired).
- event-store probe: kept master's EventStoreHealthProbe; dropped EventStoreLatencyProbe.
- brief echo-back gate: kept master's BriefEchoDiff (Jaccard, tolerates rewording);
  dropped the branch's exact-set-diff BriefEchoComparator/Extractor.
- static-first reviewer: kept master's command/exit-code gate (ProcessStaticAnalysisRunner,
  wired); dropped the branch's structured-finding static_check stage (no-op seam).
  Its structured-findings model is filed as a follow-up in BACKLOG.

Feature-branch net-new work brought in and kept (master had none):
- native task tracking (aggregate, agent tools wired into analyst/implementer/reviewer,
  dependency graph + gates, decompose, REST/CLI, TUI task board)
- critique-outcome producer (role-rel §6 — master had deferred it)
- stage-level plan checkpointing (C-A2, folded into runPostStageGates)
- CLAUDE.md/AGENTS.md L0 standing context
- cross-session grants + TUI (grant scopes/revoke, @ picker, session resume browser)

Verified: full Gradle compile (all modules + tests) green; tests pass for core:events,
core:kernel, infrastructure:workflow, apps:server, apps:cli, testing:integration; tui-go
go build + go test green.

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

BACKLOG.md

@@ -34,6 +34,17 @@ mutate a candidate in place, or exceed 2 gen rounds / 1 critique round. Defect d
 
 ## Ready to build (unblocked)
 
+- [ ] **structured static-analysis findings** (role-rel §5, salvaged from `feat/backlog-burndown` at
+      the 2026-06-26 merge) — the merge kept master's command/exit-code static gate; the feature
+      branch's richer model is worth rebuilding on top of it: parse tool output into
+      `StaticFinding{tool,file,line,column,severity,ruleId}` (detekt/compiler/ktlint parsers existed)
+      and mechanically strip already-recorded findings from the reviewer's context
+      (`excludeStaticFindingsFromReview`) instead of only gating on exit code. Needs a production
+      runner that resolves the command to the session workspace (the original was a no-op seam).
+- [ ] **§6 reviewer structured-findings emission** — the critique-outcome producer
+      (`CritiqueOutcomeCorrelator` → calibration) merged in from `feat/backlog-burndown` is dormant
+      until the reviewer/plan-critic actually emit `CritiqueFindingsRecordedEvent`s (a `review_report`
+      findings array + prompt change). Model-dependent → live-QA.
 - [ ] **architect contradiction-check** (role-rel §4) — L3 over decision journal + ADRs →
       `PossibleContradictionFlag` (display-only in v1).
 - [ ] **symbol grounding** (role-rel §3) — needs a real symbol index (file-path grounding done); also