chore: planner run 2026-04-17

- Updated prerequisite tree: #425 closed, added Nomad backend and
  hire-an-agent objectives, tracked S2 verification bugs
- Filed vault procurement for #758 (ops repo branch protection)
- Memory update (runs 3-13 summarized): constraint focus shifted to
  #758 root blocker and hire-an-agent cascading bugs

knowledge/planner-memory.md

@@ -1,28 +1,37 @@
-<!-- summarized-through-run: 2 -->
+<!-- summarized-through-run: 13 -->
 # Planner Memory
-Last updated: 2026-04-08
+Last updated: 2026-04-17
 
 ## Run history
 - Run 1 (2026-04-05): First planning run. Established prerequisite tree from VISION.md.
-- Run 2 (2026-04-08): Foundation milestone completed. All 5 blockers resolved. Triaged 4 predictor predictions (all actioned). Filed #425 (ops repo migration) and #426 (website observability). Focus shifted to Adoption milestone.
+- Run 2 (2026-04-08): Foundation milestone completed. Triaged 4 predictions. Filed #425, #426.
+- Runs 3-12 (2026-04-12 to 2026-04-15): Maintained tree locally. Ops repo push blocked by #758 (branch protection). Nomad migration sprint filed and tracked. hire-an-agent bugs surfaced.
+- Run 13 (2026-04-17): Updated tree with Nomad migration and hire-an-agent objectives. Filed vault procurement for #758. Memory update (10 runs since last summary).
 
 ## Current constraint focus
-1. **Ops repo migration** (#425) — existing deployments missing evidence/, sprints/, portfolio.md, RESOURCES.md, vault subdirs. Blocks evidence collection for all agents. Priority+backlog.
-2. **Website observability** (#426) — disinto.ai has no analytics/measurement. Blocks Adoption landing page and Ship engagement measurement. Vision-level (design decisions needed).
-3. **Example project** — none exists. Blocked on bootstrap verification after #425.
-4. **Deploy profiles** — not started. Vision-level design needed for per-artifact-type deployment.
-5. **Assumptions register** — not started. Ship (Fold 2) prerequisite.
+1. **Ops repo branch protection** (#758) — HUMAN_BLOCKED. All agent writes to ops repo frozen since 2026-04-08. Vault procurement filed (vault/pending/disinto-ops-branch-protection.md). Gardener flagged 2x. Root blocker for Adoption.
+2. **hire-an-agent defects** (#834 umbrella) — compose generator, TOML parser, collaborator setup, image rebuild (#887). Blocks multi-agent parallel operation. Multiple priority sub-issues in-progress.
+3. **issue_claim race** (#830) — verify assignee after PATCH to prevent duplicate work. Priority, in-progress.
+4. **Re-seed ops dirs** (#820) — blocked on #758. Once branch protection resolved, seeds vault/evidence/sprint dirs.
+5. **Website observability** (#426) — vision-level. No analytics on disinto.ai. Blocks Adoption landing page completion.
 
 ## Patterns observed
-- Foundation milestone completed in ~10 days (2026-03-28 to 2026-04-08). High bug fix velocity once dev-agent pipeline was reliable.
-- Predictor-planner loop working: predictor filed 4 accurate predictions, planner actioned all 4. The adversarial feedback catches stale state and planner drift effectively.
-- Predictor correctly identified planner filing Fold 2/3 vision issues (#418, #419) while Foundation was incomplete — planner must verify milestone completion before advancing.
-- Ops repo structural debt: setup_ops_repo() creates dirs for new repos but doesn't migrate existing ones. Pattern will recur with future schema changes.
-- No observables exist — all 4 addressables (website, repo, skill, github org) lack measurement. This is the fundamental gap between Adoption and Ship.
+- #425 closed but effect blocked by #758 — code-level fix ≠ deployment-level fix. Pattern: migration code landing without the ops repo push path being verified.
+- Nomad migration is a major new initiative (step-0 through step-2, ~20 issues). Emerged organically from architect sprints. Not in original VISION.md milestones but supports Adoption (alternative backend).
+- hire-an-agent flow has cascading bugs: TOML parser → compose generator → entrypoint → collaborator setup. Each fix surfaces the next. Pattern: untested integration path now under first real multi-agent use.
+- Graph grew from 165→215 nodes, 137→259 edges. No cycles or bottlenecks. 11 orphans (benign: unused formulas/labels + orphan issue #843).
+- Predictor has been quiet — 0 unreviewed predictions in run 13. May indicate predictor hasn't run recently or all predictions were already triaged.
+- High dev velocity on Nomad work despite ops repo write freeze — work proceeds because it's in the code repo, not ops repo.
 
 ## Strategic direction
-- Foundation DONE. Adoption is now the active milestone.
-- #425 is the single blocking issue — once ops repo dirs exist, evidence collection unblocks and bootstrap is complete.
-- After #425: focus on example project (demonstrates full lifecycle) and website observability (#426).
-- Do NOT file Ship/Learn issues until Adoption objectives show progress. Predictor will check.
-- Graph report is healthy: 165 nodes, 137 edges, no cycles, no bottlenecks. 7 orphans are benign (closed issues, unused formulas/labels).
+- Foundation DONE. Adoption active with two new sub-objectives: Nomad backend and multi-agent operation.
+- **Critical path**: #758 (human action) → #820 (re-seed) → ops repo writes resume → evidence/vault/knowledge persistence.
+- Nomad migration is the largest active workstream but does NOT block other Adoption objectives. Track but don't gate on it.
+- hire-an-agent bugs are the main dev-pipeline constraint — until resolved, only single-agent operation is reliable.
+- Do NOT file Ship/Learn issues. Adoption has 3 blocked objectives and 2 in-progress workstreams.
+- After #758: immediately push accumulated ops state, then focus on example project (#697).
+
+## Lessons learned
+- Ops repo branch protection created a 9-day knowledge blackout (2026-04-08 to 2026-04-17). Container restart would lose all intermediate state. Vault procurement items for human-blocked constraints should be filed immediately, not deferred.
+- "Code fix merged" ≠ "deployed effect realized" — verify the push path, not just the code path.
+- Umbrella issues (#834) are useful for tracking cascading bug chains in integration paths.