chore(campaign): intake + triage judgment-transaction and config-resolution deliveries

.agent/handoffs/external-agent-campaigns/2026-07-17-gpt-pro-wave-2/results/ann-04/r01/receipt.json

@@ -4,11 +4,20 @@
   "workload_id": "warroom-wave2",
   "job_id": "ann-04",
   "package_revision": "r01",
-  "state": "needs_rebase_review",
+  "state": "superseded",
   "artifact": {
     "filename": "PATCH.diff",
     "sha256": "a72c7e066521721cec2de5784d3e8071f2604496c5bb27ea2bb90b7699e7ec76",
     "size_bytes": 189695
   },
-  "verification": "Loose-file delivery (no ZIP); clipboard FINAL-SUMMARY captured and matches HANDOFF.md. PATCH.diff built against 536a53e; git apply --check fails on current master (docs/cli-reference.md, archive_tiers/archive.py, archive_tiers/user_write.py, help snapshots). 41ow writer-slot fix (BEGIN IMMEDIATE/SAVEPOINT) with two-connection race regression is the load-bearing content; adjudicate via rebase-review before Lane G's 41ow item."
+  "verification": "Loose-file delivery (no ZIP); clipboard FINAL-SUMMARY captured and matches HANDOFF.md. PATCH.diff built against 536a53e; git apply --check fails on current master (docs/cli-reference.md, archive_tiers/archive.py, archive_tiers/user_write.py, help snapshots). 41ow writer-slot fix (BEGIN IMMEDIATE/SAVEPOINT) with two-connection race regression is the load-bearing content; adjudicate via rebase-review before Lane G's 41ow item.",
+  "reassessments": [
+    {
+      "date": "2026-07-20",
+      "trigger": "identical-SHA duplicate re-download landed at /realm/tmp/gpt-pro-intake-0719/judgment-*.md/.diff on 2026-07-19; per custody policy (results/README.md: 'Duplicated browser downloads with identical SHA-256 values are deliberately not copied twice') no new package revision or raw/extracted copy was created -- sha256 of PATCH.diff/HANDOFF.md/EVIDENCE.md/TESTS.md all match this r01 record exactly (diff -q reports no differences).",
+      "state_change": "needs_rebase_review -> superseded",
+      "finding": "Supersession is now total, not partial as originally judged before Lane G's follow-through PRs landed. bd polylogue-41ow (closed) shows master independently fixed the writer-slot TOCTOU race via PR #3101 (SAVEPOINT + zero-row-write lock upgrade, a different mechanism than this delivery's BEGIN IMMEDIATE/SAVEPOINT approach but covering the same invariant) plus PR #3110 (foreign_keys pragma normalization, this delivery's completeness addendum). bd polylogue-2o3d (closed, PR #3138) shows the delivery's entire non-overlapping additive scope -- bounded evidence previews (list_assertion_candidate_reviews), queue health (assertion_candidate_queue_health in judge --status/daemon status/polylogue status), mark-candidates-to-root-judge consolidation, actor-scoped capture idempotency (--idempotency-key on note) -- was independently rebased and landed after 2o3d's own line-by-line audit found the MCP-surface hunks obsolete (six-tool cutover, commit d2cd05973/PR #3095) and the delivery's own transaction mechanism redundant with #3101 (both auto-merged with zero textual conflict during a rebase attempt; the redundant one was dropped as a real defect, not shipped). No portable residual remains: every acceptance-matrix row this delivery claims has an independent, already-merged, already-adjudicated master implementation.",
+      "reverification": "git apply --check re-run against the stated snapshot 536a53efac0cbe4a2473ad379e4db49ef3fce74d: still passes cleanly. Re-run against origin/master at both e963e87f5 and (after rebase) 1c0f4eccd: fails identically both times on all 20 production files -- polylogue/mcp/server_mutation_tools.py and two MCP test files report 'No such file or directory' (retired by the six-tool cutover), the rest report 'patch does not apply' (user_write.py, archive_tiers/archive.py, cli/commands/judge.py, query_verbs.py, api/archive.py, daemon/status.py, surfaces/payloads.py, etc. all diverged)."
+    }
+  ]
 }

.agent/handoffs/external-agent-campaigns/2026-07-17-gpt-pro-wave-2/results/index.json

@@ -22,7 +22,7 @@
   {
    "job": "ann-04",
    "revision": "r01",
-   "state": "needs_rebase_review"
+   "state": "superseded"
   },
   {
    "job": "ann-05",

.agent/handoffs/external-agent-campaigns/2026-07-17-gpt-pro-wave-2/results/misc-01/r01/receipt.json

@@ -10,5 +10,14 @@
     "sha256": "9223e943cc1db08f58c1b0b47bd7bc510da95727f81c340e9f7e1643e32e0d81",
     "size_bytes": 227848
   },
-  "verification": "Second delivery copy of the config-resolution-closure mission as loose files; mission already superseded by merged PR #3079 (ResolvedRuntimeConfig) per prior r01 adjudication. Retained for provenance only."
+  "verification": "Second delivery copy of the config-resolution-closure mission as loose files; mission already superseded by merged PR #3079 (ResolvedRuntimeConfig) per prior r01 adjudication. Retained for provenance only.",
+  "reassessments": [
+    {
+      "date": "2026-07-20",
+      "trigger": "identical-SHA duplicate re-download landed at /realm/tmp/gpt-pro-intake-0719/config-*.md/.diff on 2026-07-19; per custody policy (results/README.md: 'Duplicated browser downloads with identical SHA-256 values are deliberately not copied twice') no new package revision or raw/extracted copy was created -- sha256 of PATCH.diff/HANDOFF.md/EVIDENCE.md/TESTS.md all match this r01 record exactly (diff -q reports no differences).",
+      "state_change": "superseded -> superseded (confirmed, rationale made explicit)",
+      "finding": "PR #3079 (merged 2026-07-18T04:23Z, 'feat(config): close the 5-layer resolution gap with ResolvedRuntimeConfig') already shipped ResolvedRuntimeConfig/single-resolver/archive_root-fix from an earlier revision of this exact GPT-Pro packet family -- its own PR body states it was 'recovered as config-closure-current.diff from a GPT Pro packet' (a 1717-line variant is preserved at misc-01/r01/raw/config-closure-current (3).diff, distinct sha 9010ddf7e..., vs. this delivery's fuller 5377-line/73-file diff). Live-checked polylogue/config.py:1514 _merge_toml/_deep_merge_table: nested health tables (health_convergence_debt, health_cursor_lag) already deep-merge on master, closing the polylogue-cxlk bug shape this delivery also targets. There is no viable rebase target for this patch against the current config API: #3079 shipped a differently-shaped ResolvedRuntimeConfig with different composition-root injection points and no shared ancestor with this delivery's own implementation, so applying or reconciling this patch's hunks is not the right motion -- any further work must be RE-DERIVED against the already-landed API, not revived from this diff. bd polylogue-fd2s and polylogue-9gh1 (epic) still read status=open (epic_closed_children=0) in bd -- read as bookkeeping lag behind #3079's landing, not evidence the architecture is unfixed; flagged for a separate bd housekeeping pass, out of this triage's scope. GENUINE RESIDUAL, TRACKED DURABLY: bd polylogue-uu8r (open, P2) targets ~31 direct-os.environ call sites outside config.py; spot-checked two files this delivery's own bypass-caller table names -- polylogue/daemon/backup.py:695 (POLYLOGUE_BACKUP_VERIFY_TMPDIR) and polylogue/pipeline/services/archive_ingest.py:48 (POLYLOGUE_INGEST_COMMIT_BATCH_MESSAGES) -- both still read os.environ.get() directly on current master, i.e. NOT migrated by #3079. This delivery's migration for those two files plus ~5-6 more (sources/live/batch_support.py, sources/parsers/antigravity.py, sources/hooks.py, ui/theme.py, readiness/__init__.py, logging.py) is real, uncaptured value, but is small-to-medium re-derivation work against the current config API, not a portable hunk from this patch. The residual is tracked as polylogue-uu8r directly, not as a pending state on this package.",
+      "reverification": "git apply --check re-run against the stated snapshot 536a53efac0cbe4a2473ad379e4db49ef3fce74d: still passes cleanly. Re-run against origin/master at both e963e87f5 and (after rebase) 1c0f4eccd: fails identically both times on all 21 production files that touch the config/services/paths core (polylogue/config.py, services.py, paths/_roots.py, cli/click_app.py, cli/shared/types.py, daemon/cli.py, mcp/server.py, storage/embeddings/*, etc.) plus 4 of its core test modules. #3175 (feat(cli): converge first-run onboarding, landed between the two checks) touches cli/click_app.py, cli/commands/dashboard.py, and cli/commands/tutorial.py -- all three appear in this delivery's file list -- adding incremental drift on peripheral CLI files, but does not touch config.py/services.py/paths/_roots.py, so it does not change the core-architecture supersession finding."
+    }
+  ]
 }