chore(poe2e): init Adversary phase files — D5 baseline snapshot, awaiting Builder

machine-docs/BACKLOG-poe2e.md

@@ -0,0 +1,9 @@
+# BACKLOG — phase poe2e
+
+## Build backlog
+
+(Builder-owned — read-only for Adversary)
+
+## Adversary findings
+
+(No findings yet — phase just initialized @2026-06-13T19:25Z)

machine-docs/BUILDER-INBOX.md

@@ -0,0 +1,10 @@
+# BUILDER-INBOX — poe2e phase start @2026-06-13T19:25Z
+
+Adversary initialized for poe2e. Phase files created: REVIEW-poe2e.md, BACKLOG-poe2e.md, JOURNAL-poe2e.md.
+
+D5 baseline snapshot taken: agents.toml + agents.py checksums captured, tmux sessions logged.
+
+Ready for your claim. Waiting on STATUS-poe2e.md with Gate: claimed + HOW/EXPECTED/WHERE.
+
+Key reminder for D5: keep agents.toml, agents.py, state/ untouched; do NOT start any watchdog
+using the cc-ci- session namespace. Adversary will verify from the baseline snapshot above.

machine-docs/JOURNAL-poe2e.md

@@ -0,0 +1,40 @@
+# JOURNAL — phase poe2e (Adversary)
+
+## 2026-06-13T19:25Z — Orientation
+
+New phase. Read plan-phase-poe2e-end-to-end.md in full. Phase has 4 DoD items:
+D1 = PO lifecycle demo (throwaway project); D2 = staged cc-ci project with agents.py status parity;
+D3 = fleet.toml registration; D4 = cutover runbook; D5 = live cc-ci untouched.
+
+Key guardrails:
+- Must NOT cut live cc-ci over to the new system
+- Must NOT start any watchdog/loop using cc-ci- session prefix
+- Staging + parity + runbook ONLY
+
+No poe2e files existed — initialized REVIEW, BACKLOG, JOURNAL now. Notified Builder via BUILDER-INBOX.
+Awaiting Builder claim.
+
+Key verification approach for D5 (live cc-ci untouched):
+- Snapshot live tmux sessions BEFORE Builder work begins
+- Re-check AFTER claimed done: same sessions running, no new watchdog, agents.toml/state/ unchanged
+
+### D5 Baseline snapshot @2026-06-13T19:25Z (pre-Builder)
+
+**agents.toml SHA256:** 0d78ba55329705055bbb39722292b6d131cdd30f37eb814e50316f7c0e222b88
+**agents.py SHA256:** b4567b73099a587b5727a194f80a5e908d1a1589691294230e6ad1492fb9fe9a
+**state/phase-idx:** 18 (poe2e)
+
+**tmux sessions on orchestrator (pre-Builder):**
+- cc-ci-adv (just started for this phase)
+- cc-ci-assistant3 (pre-existing, since 2026-06-09)
+- cc-ci-builder (just started for this phase)
+- cc-ci-cleanlogs (pre-existing, since 2026-06-02)
+- cc-ci-orchestrator (pre-existing, since 2026-06-13)
+- cc-ci-report (pre-existing, since 2026-06-12)
+- cc-ci-upgrader (pre-existing, since 2026-06-11)
+- cc-ci-watchdog (pre-existing, since 2026-06-13)
+
+**cc-ci host tmux:** `no tmux sessions` (cc-ci host has no tmux sessions at phase start)
+
+D5 PASS requires: after all Builder work, agents.toml and agents.py checksums unchanged; no new
+cc-ci-watchdog-like sessions started against live cc-ci namespace; state/ unchanged.

machine-docs/REVIEW-poe2e.md

@@ -0,0 +1,27 @@
+# REVIEW — phase poe2e (Adversary)
+
+**Phase plan:** `/srv/cc-ci/cc-ci-plan/plan-phase-poe2e-end-to-end.md`
+**Initialized:** 2026-06-13T19:25Z
+
+## Orientation
+
+Phase mission: prove the whole model works end-to-end — PO scaffolds, runs (isolated), and tears
+down a throwaway project; cc-ci is modeled as a project in STAGING; live cc-ci is provably untouched.
+
+### Definition of Done (poe2e)
+
+| # | DoD item | Status |
+|---|---|---|
+| D1 | PO scaffolded, ran (isolated), and tore down a throwaway project — evidence in REVIEW | pending |
+| D2 | Staged `cc-ci` project: engine submodule pinned + migrated `agents.toml`; `agents.py status` MATCHES live cc-ci (side-by-side shown) | pending |
+| D3 | Staged cc-ci registered in `fleet.toml` | pending |
+| D4 | Written, reviewed operator cutover runbook | pending |
+| D5 | Live cc-ci provably untouched: tmux sessions + `/srv/cc-ci/cc-ci-plan/agents.{py,toml}` + `state/` unchanged; no second watchdog started | pending |
+
+## Verdicts
+
+(awaiting Builder claim)
+
+## Break-it probes
+
+(will log independent probes here as they run)