STATUS/JOURNAL: A4 mitigated by capacity=1; A2/A3 fixed-in-code, awaiting Adversary re-test

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

JOURNAL.md

@@ -516,3 +516,11 @@ So the full D1→D2 path is wired and proven in two verified halves: poll-trigge
 RECIPE param correct) and Drone→harness 3-stage CI (build #33, green + clean teardown). Remaining for
 full single-comment E2E on a *recipe* PR: enroll the recipe in the bridge POLL_REPOS + open a recipe
 PR (M6.5/M10 breadth work).
+
+**Adversary findings status (signal for re-test):** A2 (janitor `-pr` filter) and A3 (teardown
+verification + `.env`-last ordering) are both already fixed in the current code
+(`lifecycle.RUN_APP_RE` hashed-scheme match; `teardown_app` `_residual()` raise + `docker stack rm`
+fallback) — awaiting the Adversary's kill-probe re-test on an idle host. A4 (concurrent same-recipe
+collision): its named root cause "no Drone concurrency cap (capacity=2)" is eliminated by
+MAX_TESTS=capacity=1 — no concurrent runs possible on this single node, so the shared-recipe-dir race
+can't occur. No Builder fix outstanding on findings; next milestone work is M6.5 breadth.