chore: initialize POM 2 repo (docs guards green; release gates recorded NOT RUN pending install)

prompts/stage-run.md

@@ -0,0 +1,41 @@
+Execute POM Task {{STAGE_ID}} — {{STAGE_NAME}} for {{PROJECT_TITLE}}.
+
+Read first:
+- skill://pom
+- {{PROJECT_ROOT}}/00_admin/project_state.json
+- only canonical files relevant to this stage
+
+Operating contract:
+- initialize the exact stage todo blueprint with the built-in todo tool
+- use tool profile {{TOOL_PROFILE}}
+- use model role {{MODEL_ROLE}} when available
+- parallelize independent specialist work through one task batch
+- preferred agents: {{AGENTS}}
+- read files and static URLs with read; use browser only for interaction/authentication
+- use LSP for symbol-aware code work, AST tools for structural code work, edit for grounded local edits, eval for multi-step computation, and bash only for short binary calls
+- use generate_image only from a complete visual brief; inspect every generated asset
+- canonical files override memory and chat summaries
+- update state, canon, ledgers, manifest, and logs through POM tools
+- never claim an artifact, count, citation, validation, or completion without evidence
+- do not call pom_stage pass before pom_validate succeeds
+- on failure, preserve completed work and call pom_stage block with the exact blocker
+
+Required artifact targets:
+{{ARTIFACTS}}
+
+Completion gate:
+{{GATE}}
+
+Agent-studio contract:
+- use one native task batch with one shared context and complete assignments
+- use local:// for large shared context
+- use agent:// and history:// for outputs and follow-up
+- message existing agents through IRC instead of respawning them
+- do not poll jobs unless all useful parent work is blocked
+
+Finish:
+1. run pom_validate
+2. fix material defects
+3. call pom_stage pass on PASS or pom_stage block on failure
+4. mark todos done immediately
+5. present the configured POM UI with only real files and one next action