cc-ci/machine-docs/STATUS-poe2e.md

STATUS — phase poe2e (Builder)

Phase plan: /srv/cc-ci/cc-ci-plan/plan-phase-poe2e-end-to-end.md

---

DONE

All 5 Definition-of-Done items are Adversary-verified with a fresh PASS (@2026-06-13T19:46Z) in REVIEW-poe2e.md — cold-verified from the Adversary's own clone (/srv/cc-ci/cc-ci-adv) and a fresh shell. No findings, no standing VETO. The PO scaffolded/ran/tore-down a throwaway project (D1); cc-ci is modeled as a staged project (D2: /home/loops/poe2e/cc-ci @ 38e5c90, engine/ pinned 289ef07 = v0.1.0, migrated agents.toml whose agents.py status + phases array + rendered kickoffs match live); it is registered in the PO fleet.toml (D3, enabled=false); a reviewed operator cutover runbook exists (D4); and the live cc-ci is provably untouched (D5: agents.{py,toml} + state/ + the cc-ci-* sessions all == the Adversary's pre-Builder baseline, single watchdog).

---

Gate: CLAIMED — all 5 DoD built + cold-verified @2026-06-13T19:41Z — Adversary PASS @19:46Z

Deliverables (WHERE)

• Staged cc-ci project (local staging git repo, the phase's sanctioned "staging dir"): /home/loops/poe2e/cc-ci, main HEAD 38e5c907b9e37b8aebbfccb2e1ad8de7e2d880cb. engine/ submodule pinned 289ef07df40a8264f3a36b4e91b923d1424c4658 = tag v0.1.0 of recipe-maintainers/agent-orchestrator (public; .gitmodules URL is the public Gitea URL, so a recursive clone fetches the engine without creds). Tracked files: agents.toml, prompts/{kickoff,builder,adversary}.md, ai-progress-monitor-prompt.txt, docs/cutover-runbook.md, .gitignore, .gitmodules, engine (gitlink). Runtime state (.ao-state/) is gitignored.
• PO fleet registry: recipe-maintainers/project-orchestrator on git.autonomic.zone, main HEAD 6cc3ed4 (pushed). fleet.toml now has the cc-ci [[project]] entry (enabled = false).
• Live cc-ci (the parity target / must-be-untouched): /srv/cc-ci/cc-ci-plan/agents.{py,toml}, /srv/cc-ci/.cc-ci-logs/state/, and the cc-ci-* tmux sessions on the orchestrator host.

Nothing live was started or modified

The staged config uses session_prefix = "cc-ci-" (faithful to live). I ran ONLY status / phase show / phase set on it — all read-only or writing the staged repo's own gitignored .ao-state. I never ran up/down/watchdog on the staged config (which would target the live cc-ci- sessions). The staged status STATE column reads RUNNING because session_alive() is a read-only tmux has-session query that sees the live sessions — the staged project started nothing.

---

DoD verification (WHAT / HOW / EXPECTED)

D1 — PO scaffolded, ran (isolated), and tore down a throwaway project

HOW (re-runnable):

cd /home/loops/porepo/project-orchestrator
rm -rf /tmp/poe2e-scratch
bash scripts/create-project.sh scratch-e2e --dir /tmp/poe2e-scratch --ref v0.1.0 --prefix poe2e-scratch-
# switch the scaffold to the dependency-free `demo` backend (no token spend, isolated namespace):
#   edit /tmp/poe2e-scratch/scratch-e2e/agents.toml → backend="demo" + [backend.demo] + one demo agent
cd /tmp/poe2e-scratch/scratch-e2e
python3 engine/agents.py status      # worker+watchdog: stopped
python3 engine/agents.py up          # starts poe2e-scratch-worker + poe2e-scratch-watchdog
tmux ls | grep poe2e-scratch         # both sessions present
python3 engine/agents.py status      # worker RUNNING [sleep], watchdog RUNNING
python3 engine/agents.py down        # kills both
tmux ls | grep poe2e-scratch || echo "torn down"
cd / && rm -rf /tmp/poe2e-scratch    # delete throwaway

EXPECTED: scaffold reports engine pinned at 289ef07 (v0.1.0); tracked files exactly .gitignore .gitmodules agents.toml engine (no PO/fleet metadata). up prints starting poe2e-scratch-worker (demo, …) + starting watchdog; post-up status shows both RUNNING; down prints killing …; post-down status shows both stopped; throwaway deleted; the 8 live cc-ci-* sessions untouched throughout (the demo used the isolated poe2e-scratch- namespace). I executed exactly this @19:31Z (transcript in JOURNAL-poe2e.md).

D2 — Staged cc-ci: engine submodule pinned + migrated agents.toml; agents.py status MATCHES live

HOW (cold, from a fresh recursive clone of the staging repo):

cd /tmp && rm -rf poe2e-ccci-cold
git clone --recurse-submodules /home/loops/poe2e/cc-ci poe2e-ccci-cold
cd poe2e-ccci-cold
git rev-parse HEAD            # 38e5c90…
git submodule status         # 289ef07… engine (v0.1.0)

# (a) phase LIST + per-phase models are byte-identical (index-independent, strongest proof):
python3 - <<'PY'
import tomllib
live = tomllib.load(open('/srv/cc-ci/cc-ci-plan/agents.toml','rb'))['loop']['phases']
stg  = tomllib.load(open('agents.toml','rb'))['loop']['phases']
print('phases:', len(live), len(stg), '| identical:', live == stg)
PY

# (b) full phase sequence:
python3 engine/agents.py phase show

# (c) exact status side-by-side at the live phase (set the staged index to poe2e=18):
python3 engine/agents.py phase set 18
python3 engine/agents.py status                         > /tmp/s.txt
( cd /srv/cc-ci/cc-ci-plan && python3 agents.py status ) > /tmp/l.txt
diff /tmp/s.txt /tmp/l.txt && echo "STATUS BYTE-IDENTICAL"

# (d) the loop kickoff each agent would receive is byte-identical to the live generated one:
python3 - <<'PY'
import sys; sys.path.insert(0,'engine'); import agents
cfg=agents.load_config('agents.toml')            # phase-idx already 18 from (c)
for nm,live in [('builder','/srv/cc-ci/.cc-ci-logs/state/kickoff-cc-ci-builder.txt'),
                ('adversary','/srv/cc-ci/.cc-ci-logs/state/kickoff-cc-ci-adv.txt')]:
    got=agents.build_loop_kickoff(cfg,cfg['agents'][nm]); exp=open(live).read()
    print(nm,'kickoff identical:', got==exp)
PY
cd / && rm -rf /tmp/poe2e-ccci-cold

EXPECTED: HEAD 38e5c90; submodule 289ef07 (v0.1.0). (a) phases: 19 19 | identical: True. (b) seq: rcust shot lvl5 bsky dstamp mailu kuma drone cfold cf55 pvfix pvcheck ghost cf48 pxgate aoeng aotest porepo poe2e. (c) STATUS BYTE-IDENTICAL — both print phase: poe2e [19/19] plan=plan-phase-poe2e-end-to-end.md (in progress) and the same 8-row agent table (orchestrator opus, builder opus, adversary sonnet, assistant sonnet/disabled, upgrader sonnet/disabled, report opus/disabled, cleanlogs + watchdog services). The STATE column matches because both read the same live cc-ci- sessions (read-only tmux has-session). (d) both kickoff identical: True. Migration deltas vs live are documented inline in the staged agents.toml ("MIGRATE:" comments): added session_prefix, isolated staging log_dir, backend process_name/TUI fields, cleanlogs → engine/agent-log.py, [loop].kickoff_template/roles_dir. None affect the agents/models/phases columns.

D3 — Staged cc-ci registered in fleet.toml

HOW:

cd /home/loops/porepo/project-orchestrator   # or: git clone --recurse-submodules \
                                              #   https://git.autonomic.zone/recipe-maintainers/project-orchestrator.git
python3 scripts/fleet.py validate
python3 scripts/fleet.py status

EXPECTED: fleet: OK — 2 project(s), schema v1. status lists cc-ci [disabled] agent-orchestrator@v0.1.0 /home/loops/poe2e/cc-ci plus the sample example-recipe-ci [enabled]; total=2 enabled=1 disabled=1. enabled=false is deliberate — the PO must never start cc-ci (it would collide with the running live system); going live is the operator cutover.

D4 — Operator cutover runbook

HOW: cat /home/loops/poe2e/cc-ci/docs/cutover-runbook.md (also reachable from a recursive clone). EXPECTED: a written, operator-supervised runbook: §0 what-stays/what-changes table + the exact config deltas; §1 pre-flight + parity gate; §2 quiesce live (stop cc-ci-loops.service, agents.py down, confirm zero cc-ci- sessions — prevents a double watchdog on the shared namespace); §3 reuse live state (log_dir → /srv/cc-ci/.cc-ci-logs); §4 production config deltas; §5 re-point launch.py/launch.sh at <project>/engine/agents.py --config <project>/agents.toml (keeps the systemd boot chain + the orchestrator's startup prompt working unchanged; launch.py.orig already preserved); §6 start + validate (launch.py status parity, single watchdog, handoff ping, flip fleet entry to enabled); §7 fast rollback (re-point launch.py, restart). Derived from the real live boot chain cc-ci-loops.service → cc-ci-loops-start → launch.sh start → launch.py → agents.py up.

D5 — Live cc-ci provably untouched

HOW (compare to the Adversary's pre-Builder baseline @19:25Z):

sha256sum /srv/cc-ci/cc-ci-plan/agents.toml /srv/cc-ci/cc-ci-plan/agents.py
cat /srv/cc-ci/.cc-ci-logs/state/phase-idx
tmux ls | grep '^cc-ci' | sort
tmux ls | grep -c 'cc-ci-watchdog'           # exactly 1
ssh cc-ci 'tmux ls 2>/dev/null || echo "no tmux sessions"'

EXPECTED (all match baseline):

• agents.toml SHA256 = 0d78ba55329705055bbb39722292b6d131cdd30f37eb814e50316f7c0e222b88 (unchanged).
• agents.py SHA256 = b4567b73099a587b5727a194f80a5e908d1a1589691294230e6ad1492fb9fe9a (unchanged).
• state/phase-idx = 18 (unchanged).
• exactly the 8 baseline cc-ci-* sessions (orchestrator, builder, adv, assistant3, cleanlogs, upgrader, report, watchdog); exactly 1 cc-ci-watchdog (no second watchdog started by me).
• cc-ci host: no tmux sessions. I verified all of the above @19:41Z. The staged config + scratch demo never wrote live agents.* / state/ and never started a cc-ci--prefixed session (the scratch demo ran under poe2e-scratch-).

---

DoD summary

#	DoD item	Build state	Cold-verified
D1	PO scaffolded, ran (isolated), tore down a throwaway project	DONE	19:31Z
D2	Staged cc-ci: engine pinned + migrated agents.toml; status MATCHES live	DONE	19:40Z
D3	Staged cc-ci registered in fleet.toml (disabled)	DONE	19:40Z
D4	Operator cutover runbook	DONE	19:41Z
D5	Live cc-ci provably untouched (files/state/sessions = baseline)	DONE	19:41Z

(Reasoning / design rationale → JOURNAL-poe2e.md, kept out of STATUS to preserve anti-anchoring.)