chore(porepo): Builder claims STATUS/JOURNAL ownership, fill build backlog, inbox heads-up

machine-docs/JOURNAL-porepo.md

@@ -1,25 +1,32 @@
-# JOURNAL — phase porepo (Adversary)
+# JOURNAL — phase porepo (Builder)
 
-## 2026-06-13T19:05Z — Orientation
+## 2026-06-13T19:05Z — Bootstrap / orientation
 
-Phase porepo activated. Previous phase (aotest) is ## DONE — all 5 DoD items Adversary-verified
-PASS @2026-06-13T19:00Z.
+Read the phase plan, `plan-agent-orchestrator.md`, and the harness README at
+`/home/loops/aoeng/agent-orchestrator/README.md`. Key facts established:
 
-Builder has not yet started porepo:
-- `recipe-maintainers/project-orchestrator` → 404 on Gitea
-- No builder clone at `/srv/cc-ci/cc-ci`
+- Harness `agent-orchestrator` is built + tagged `v0.1.0` (tag object `a89d30f` → commit `289ef07`).
+  Working clone: `/home/loops/aoeng/agent-orchestrator`. Repo is **public** on Gitea
+  (`private:false`), so a fresh `git clone --recurse-submodules` fetches `engine/` without creds.
+- `engine/agents.py status` only needs a valid `agents.toml` (it reads config, prints a table;
+  does not require running sessions or live backends). So a PO config with one persistent
+  `project-orchestrator` agent will pass `status`.
+- Config schema (README): `[watchdog]`, `[backend.<name>]`, `[defaults]` (session_prefix + log_dir
+  REQUIRED), `[[agent]]`/`[[service]]`, `[loop]`. `project_dir` resolves relative paths.
+- One-directional knowledge: the PO repo holds the fleet registry (`fleet.toml`); a project repo
+  holds NO PO/fleet metadata — engine submodule pin + PO's fleet.toml are the only record of
+  project↔harness↔ref.
 
-Initialized Adversary phase files: STATUS-porepo.md, REVIEW-porepo.md, BACKLOG-porepo.md,
-JOURNAL-porepo.md.
+Decision: pin `engine/` at the **commit** the `v0.1.0` tag points to (`289ef07`), per DoD wording
+"pinned to agent-orchestrator v0.1.0". The tests commit `cdcece9` is *after* the tag and is not
+required.
 
-Key DoD items to cold-verify when Builder claims done:
-- DoD-1: repo exists, engine/ submodule at v0.1.0, main pushed
-- DoD-2: agents.py status works from cold recursive clone + nix develop
-- DoD-3: fleet.toml schema documented + sample parses
-- DoD-4: create-project flow documented + demonstrated (scratch project: no PO metadata inside)
-- DoD-5: nix develop works (tomllib import) + bootstrap doc present
+Gitea API reachable with bot creds (200); `recipe-maintainers/project-orchestrator` does not yet
+exist (404); org `recipe-maintainers` exists (id 65).
 
-Critical isolation checks:
-- Scratch project must NOT contain any PO/fleet metadata
-- Scratch project must be cleaned up (deleted from Gitea) after demo
-- Must NOT touch any live cc-ci system
+### File-ownership coordination note
+The Adversary had pre-created STATUS-porepo.md / JOURNAL-porepo.md as placeholders before I started.
+Per protocol §6.1 these are Builder-owned (STATUS is the authoritative `## DONE` handshake file the
+Adversary verifies against; JOURNAL is my reasoning). I took them over and left REVIEW-porepo.md +
+the `## Adversary findings` section of BACKLOG-porepo.md to the Adversary. Sent an ADVERSARY-INBOX.md
+heads-up so it keeps its tracking in REVIEW.