agent-control-plane 0.1.0

package/tools/dashboard/styles.css

@@ -0,0 +1,351 @@
+:root {
+  --bg: #f4f3ee;
+  --panel: #fffdf7;
+  --panel-strong: #f8f4e6;
+  --ink: #192126;
+  --muted: #5a6872;
+  --line: #d7d0c0;
+  --accent: #0f766e;
+  --accent-soft: #d8f1ec;
+  --warn: #a16207;
+  --warn-soft: #fce7b2;
+  --danger: #b42318;
+  --danger-soft: #fdd8d2;
+  --shadow: 0 18px 50px rgba(25, 33, 38, 0.08);
+}
+
+* {
+  box-sizing: border-box;
+}
+
+body {
+  margin: 0;
+  font-family: "Iowan Old Style", "Palatino Linotype", "Book Antiqua", serif;
+  background:
+    radial-gradient(circle at top right, rgba(15, 118, 110, 0.08), transparent 34%),
+    linear-gradient(180deg, #faf7ef 0%, var(--bg) 100%);
+  color: var(--ink);
+}
+
+.page {
+  max-width: 1440px;
+  margin: 0 auto;
+  padding: 32px 20px 48px;
+}
+
+.hero {
+  display: flex;
+  justify-content: space-between;
+  gap: 24px;
+  align-items: flex-start;
+  padding: 24px;
+  border: 1px solid var(--line);
+  border-radius: 28px;
+  background: rgba(255, 253, 247, 0.92);
+  box-shadow: var(--shadow);
+}
+
+.eyebrow {
+  margin: 0 0 8px;
+  text-transform: uppercase;
+  letter-spacing: 0.08em;
+  font-size: 12px;
+  color: var(--accent);
+}
+
+.hero h1 {
+  margin: 0;
+  font-size: clamp(34px, 5vw, 56px);
+  line-height: 0.95;
+}
+
+.subtitle {
+  max-width: 760px;
+  margin: 16px 0 0;
+  color: var(--muted);
+  font-size: 18px;
+  line-height: 1.45;
+}
+
+.hero-actions {
+  min-width: 220px;
+  display: flex;
+  flex-direction: column;
+  gap: 14px;
+  align-items: flex-end;
+}
+
+button {
+  appearance: none;
+  border: 0;
+  border-radius: 999px;
+  padding: 12px 18px;
+  font: inherit;
+  background: var(--ink);
+  color: white;
+  cursor: pointer;
+}
+
+button:hover {
+  background: #0f1720;
+}
+
+.meta {
+  text-align: right;
+  color: var(--muted);
+  font-size: 14px;
+}
+
+.overview {
+  margin-top: 24px;
+  display: grid;
+  grid-template-columns: repeat(auto-fit, minmax(180px, 1fr));
+  gap: 14px;
+}
+
+.card {
+  padding: 18px;
+  border-radius: 22px;
+  border: 1px solid var(--line);
+  background: var(--panel);
+  box-shadow: var(--shadow);
+}
+
+.stat-label {
+  color: var(--muted);
+  font-size: 13px;
+  text-transform: uppercase;
+  letter-spacing: 0.06em;
+}
+
+.stat-value {
+  margin-top: 8px;
+  font-size: 34px;
+  font-weight: 700;
+}
+
+.profiles {
+  margin-top: 28px;
+  display: flex;
+  flex-direction: column;
+  gap: 22px;
+}
+
+.profile {
+  padding: 22px;
+  border-radius: 28px;
+  border: 1px solid var(--line);
+  background: rgba(255, 253, 247, 0.94);
+  box-shadow: var(--shadow);
+}
+
+.profile-header {
+  display: flex;
+  justify-content: space-between;
+  gap: 16px;
+  align-items: flex-start;
+}
+
+.profile-title {
+  display: flex;
+  flex-wrap: wrap;
+  gap: 10px;
+  align-items: center;
+}
+
+.profile-title h2 {
+  margin: 0;
+  font-size: 28px;
+}
+
+.profile-subtitle {
+  margin-top: 8px;
+  color: var(--muted);
+}
+
+.badge-row {
+  display: flex;
+  flex-wrap: wrap;
+  gap: 8px;
+  justify-content: flex-end;
+}
+
+.badge {
+  display: inline-flex;
+  align-items: center;
+  gap: 6px;
+  padding: 7px 10px;
+  border-radius: 999px;
+  font-size: 13px;
+  border: 1px solid transparent;
+  background: var(--panel-strong);
+}
+
+.badge.good {
+  background: var(--accent-soft);
+  color: #0d5a54;
+}
+
+.badge.warn {
+  background: var(--warn-soft);
+  color: #855500;
+}
+
+.badge.danger {
+  background: var(--danger-soft);
+  color: var(--danger);
+}
+
+.profile-grid {
+  margin-top: 18px;
+  display: grid;
+  grid-template-columns: repeat(12, minmax(0, 1fr));
+  gap: 14px;
+}
+
+.panel {
+  grid-column: span 12;
+  padding: 16px;
+  border-radius: 22px;
+  border: 1px solid var(--line);
+  background: var(--panel);
+}
+
+.panel.half {
+  grid-column: span 6;
+}
+
+.panel.third {
+  grid-column: span 4;
+}
+
+.panel h3 {
+  margin: 0 0 12px;
+  font-size: 18px;
+}
+
+.panel-subtitle {
+  margin: -6px 0 12px;
+  color: var(--muted);
+  font-size: 14px;
+}
+
+.table-wrap {
+  overflow-x: auto;
+}
+
+table {
+  width: 100%;
+  border-collapse: collapse;
+  font-size: 14px;
+}
+
+th,
+td {
+  padding: 10px 8px;
+  text-align: left;
+  vertical-align: top;
+  border-top: 1px solid var(--line);
+}
+
+th {
+  color: var(--muted);
+  font-size: 12px;
+  text-transform: uppercase;
+  letter-spacing: 0.06em;
+  border-top: 0;
+}
+
+.mono {
+  font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
+  font-size: 12px;
+}
+
+.muted {
+  color: var(--muted);
+}
+
+.status-pill {
+  display: inline-flex;
+  align-items: center;
+  padding: 4px 8px;
+  border-radius: 999px;
+  font-size: 12px;
+  font-weight: 700;
+  background: var(--panel-strong);
+}
+
+.status-pill.RUNNING,
+.status-pill.waiting-worker,
+.status-pill.launching,
+.status-pill.reconciling {
+  background: var(--accent-soft);
+  color: #0d5a54;
+}
+
+.status-pill.waiting-provider,
+.status-pill.waiting-due,
+.status-pill.waiting-open-pr,
+.status-pill.idle,
+.status-pill.sleeping {
+  background: var(--warn-soft);
+  color: #855500;
+}
+
+.status-pill.FAILED,
+.status-pill.stopped,
+.status-pill.launch-failed {
+  background: var(--danger-soft);
+  color: var(--danger);
+}
+
+.status-pill.implemented {
+  background: #dcfce7;
+  color: #166534;
+}
+
+.status-pill.reported,
+.status-pill.completed {
+  background: #dbeafe;
+  color: #1d4ed8;
+}
+
+.status-pill.blocked {
+  background: #fef3c7;
+  color: #92400e;
+}
+
+.status-pill.failed,
+.status-pill.unknown {
+  background: var(--danger-soft);
+  color: var(--danger);
+}
+
+.status-pill.running {
+  background: var(--accent-soft);
+  color: #0d5a54;
+}
+
+.empty-state {
+  color: var(--muted);
+  padding: 10px 4px;
+}
+
+@media (max-width: 960px) {
+  .hero,
+  .profile-header {
+    flex-direction: column;
+  }
+
+  .hero-actions,
+  .badge-row {
+    align-items: flex-start;
+    justify-content: flex-start;
+    text-align: left;
+  }
+
+  .panel.half,
+  .panel.third {
+    grid-column: span 12;
+  }
+}

package/tools/templates/issue-prompt-template.md

@@ -0,0 +1,109 @@
+# Task
+
+Implement issue #{ISSUE_ID} in `{REPO_SLUG}`.
+
+# Issue Context
+
+- Title: {ISSUE_TITLE}
+- URL: {ISSUE_URL}
+- Auto-merge requested: {ISSUE_AUTOMERGE}
+
+{ISSUE_BODY}
+{ISSUE_RECURRING_CONTEXT}
+{ISSUE_BLOCKER_CONTEXT}
+
+# MANDATORY WORKFLOW (follow in order, no skipping)
+
+You MUST complete ALL 5 phases in order. Do not skip any phase. Do not commit until Phase 4 passes.
+
+## Phase 1: READ & SCOPE
+
+- Read the repo instructions: `AGENTS.md`, relevant spec or design docs, and any repo conventions tied to this issue.
+- Identify the single primary product surface you will touch.
+- If the issue spans multiple surfaces, pick ONE and create follow-up issues for the rest using:
+  ```bash
+  bash "$ACP_FLOW_TOOLS_DIR/create-follow-up-issue.sh" --parent {ISSUE_ID} --title "..." --body-file /tmp/follow-up.md
+  ```
+- Treat a broad umbrella issue as a coordination brief rather than permission to ship every slice in one PR.
+- Write down your scope decision before coding.
+
+## Phase 2: IMPLEMENT
+
+- Make the smallest root-cause fix that satisfies the issue.
+- Work only inside the dedicated worktree.
+- Add or update tests when feasible.
+- STOP after implementation. Do not commit yet.
+
+## Phase 3: VERIFY (MANDATORY)
+
+After implementing, you MUST run verification commands and record each one.
+Every successful command must be recorded or the host publish will fail.
+After each successful verification command, record it with `record-verification.sh`.
+
+```bash
+{ISSUE_VERIFICATION_COMMAND_SNIPPET}
+```
+
+Required verification coverage:
+- Run the narrowest repo-supported `typecheck`, `build`, `test`, or `lint` command that proves the touched surface is safe.
+- If you changed tests only, run the most relevant targeted test command and record it.
+- If you changed localization resources or user-facing copy, run repo locale validation or hardcoded-copy scans if the repo provides them.
+- If a verification command fails, fix the issue and rerun until it passes.
+
+CRITICAL: `verification.jsonl` must exist in `$ACP_RUN_DIR` with at least one `pass` entry before you can write `OUTCOME=implemented`.
+
+## Phase 4: SELF-REVIEW (MANDATORY)
+
+Before committing, perform this checklist:
+
+- [ ] Run `git diff --check`.
+- [ ] Count non-test product files: if the change is broad, stop and split scope instead of publishing one large PR.
+- [ ] If you touched auth, login, session, or reset flows, verify existing users and legacy data still behave correctly.
+- [ ] If you touched public endpoints, public routes, or operator workflows, search downstream consumers in `scripts/`, `docs/`, and specs.
+- [ ] If you changed localization resources or user-facing copy, confirm localization coverage and scanning are still valid.
+- [ ] If you touched mobile routes or screens, keep route scope narrow and verify loading, empty, and error states.
+
+Before committing, verify the journal exists:
+```bash
+test -s "$ACP_RUN_DIR/verification.jsonl" && echo "OK: verification.jsonl exists" || echo "BLOCKED: missing verification.jsonl"
+```
+
+## Phase 5: COMMIT & REPORT
+
+- Commit with a conventional commit message.
+- Do NOT push or open a PR; the host handles that.
+- Write `$ACP_RESULT_FILE`:
+  ```bash
+  cat > "$ACP_RESULT_FILE" <<'OUTER_EOF'
+  OUTCOME=implemented
+  ACTION=host-publish-issue-pr
+  ISSUE_ID={ISSUE_ID}
+  OUTER_EOF
+  ```
+- In your final output, include the changed files, verification commands actually run, and one short self-review note naming the main regression risk you checked.
+
+# STOP CONDITIONS
+
+Stop and report blocked if:
+- The issue is ambiguous, blocked by missing credentials, or expands into high-risk scope.
+- You cannot complete verification successfully.
+- The issue needs full decomposition into focused follow-up issues.
+
+If stopped blocked, write `$ACP_RUN_DIR/issue-comment.md` with a blocker summary, then:
+```bash
+cat > "$ACP_RESULT_FILE" <<'OUTER_EOF'
+OUTCOME=blocked
+ACTION=host-comment-blocker
+ISSUE_ID={ISSUE_ID}
+OUTER_EOF
+```
+
+If fully decomposed into follow-up issues, start the first line of `issue-comment.md` with exactly:
+`Superseded by focused follow-up issues: #...`
+
+# Git Rules
+
+- Do NOT push the branch from inside the worker.
+- Do NOT open a PR from inside the worker.
+- Do NOT comment on the source issue with a PR URL from inside the worker.
+- Exit successfully after writing the result file.

package/tools/templates/pr-fix-template.md

@@ -0,0 +1,120 @@
+You are the PR repair worker for `{REPO_SLUG}`.
+
+Before making any change:
+
+1. Read `{REPO_ROOT}/AGENTS.md`.
+2. Read `{REPO_ROOT}/openspec/AGENT_RULES.md`.
+3. Read `{REPO_ROOT}/openspec/AGENTS.md`.
+4. Read `{REPO_ROOT}/openspec/project.md`.
+5. Read `{REPO_ROOT}/openspec/CONVENTIONS.md`.
+6. Read `{REPO_ROOT}/docs/TESTING_AND_SEED_POLICY.md`.
+7. Stay on this PR branch worktree. Do not push or mutate GitHub from inside the worker.
+
+PR metadata:
+
+- PR: {PR_NUMBER} - {PR_TITLE}
+- URL: {PR_URL}
+- Base branch: {PR_BASE_REF}
+- Head branch: {PR_HEAD_REF}
+- Linked issue: {PR_LINKED_ISSUE_ID}
+- Risk classification: {PR_RISK}
+- Risk reason: {PR_RISK_REASON}
+- Merge state: {PR_MERGE_STATE_STATUS}
+- Mergeable: {PR_MERGEABLE_STATUS}
+
+Changed files:
+{PR_FILES_TEXT}
+
+Required targeted verification coverage before `updated-branch`:
+{PR_REQUIRED_TARGETED_VERIFICATION_TEXT}
+
+Pre-approved local verification fallbacks:
+{PR_PREAPPROVED_VERIFICATION_FALLBACKS_TEXT}
+
+Current CI / merge blockers:
+{PR_CHECK_FAILURES_TEXT}
+
+Current GitHub checks:
+{PR_CHECKS_TEXT}
+
+Current missing reasons:
+{PR_MISSING_REASONS_TEXT}
+
+Current local merge-conflict paths:
+{PR_CONFLICT_PATHS_TEXT}
+
+Actionable current-head review findings:
+{PR_REVIEW_FINDINGS_TEXT}
+
+Current host-side publish blocker summary:
+{PR_LOCAL_HOST_BLOCKER_SUMMARY_TEXT}
+
+Current final-review blocker summary:
+{PR_BLOCKER_SUMMARY_TEXT}
+
+PR body:
+{PR_BODY}
+
+Required flow:
+
+1. Inspect the current diff and the failing/pending CI signals first:
+   - `openspec list`
+   - `git diff --stat origin/main...HEAD`
+   - `git status --short`
+   - if `Merge state` is not `CLEAN` or `Mergeable` is `FALSE`, treat branch drift/conflicts as the concrete blocker first
+   - if `Actionable current-head review findings` is not `- none`, treat those findings as the concrete blockers to address first
+   - otherwise, if `Current host-side publish blocker summary` is not `- none`, treat that summary as the concrete blocker to address first
+   - otherwise, if `Current final-review blocker summary` is not `- none`, treat that summary as the concrete blocker to address first
+2. Never run dependency bootstrap or workspace-mutating commands here:
+   - do not run `pnpm install`, `npm install`, `yarn install`, or `bun install`
+   - do not mutate the retained dependency checkout under `{DEPENDENCY_SOURCE_ROOT}`
+   - do not repair the shared `node_modules` baseline from this worker
+   - do not run `git fetch`, `git merge`, `git rebase`, `git commit`, `git push`, or other Git metadata-writing commands from inside this worker; host-side wrappers own those steps
+3. If the blocker is branch drift or a merge conflict, use the already-prepared local refs and make the smallest branch-local source update needed to restore mergeability on this PR branch. Keep the resolution scoped to the PR intent; do not rewrite unrelated code.
+   - Treat `Current local merge-conflict paths` as the authoritative conflict list to clear.
+   - Do not stop after fixing only one file if other conflict paths remain.
+   - Before you declare success, rerun local merge simulation and confirm there are no remaining conflict paths for this branch against `{PR_BASE_REF}`.
+4. Make the smallest change that fixes the concrete PR blockers on this existing branch.
+5. Run the narrowest verification that proves the fix for the blocker you changed.
+   - This is an unattended automated repair run. Do not ask the user for clarification, approval, or a next-step choice from inside the worker. Treat this prompt as the full execution contract for the run.
+   - After each successful verification command, record it with:
+     `bash "$ACP_FLOW_TOOLS_DIR/record-verification.sh" --run-dir "$ACP_RUN_DIR" --status pass --command "<exact command>"`
+   - If you changed a `*.spec.*` or `*.test.*` file, include a targeted test command for that file or the directly related surface.
+   - The host verification guard is literal. If `Required targeted verification coverage before updated-branch` is not `- none`, every listed file must have at least one recorded successful command whose command text clearly names that file, its direct stem, or the scoped e2e/mobile runner you used for that exact spec.
+   - If a changed web Playwright spec hits a local bind/listen failure while starting Next or Playwright (for example `listen EPERM ... 0.0.0.0:3000`), retry exactly once with the matching command from `Pre-approved local verification fallbacks` before declaring the run blocked.
+   - Do not write `updated-branch` until every listed coverage item is satisfied in `verification.jsonl`.
+6. If you make source changes, leave them as local file edits in this worktree. Do not run Git staging/commit/push commands yourself; host reconcile will stage, commit, validate mergeability, and push only if the branch is actually clean.
+7. Write a short markdown summary for the PR to `$ACP_RUN_DIR/pr-comment.md`.
+8. If the reported blocker is already resolved on the current PR branch and no code change is needed, or the only remaining blocker is external worktree dependency state while the branch diff itself already satisfies the requested fix:
+   - make that explicit in `$ACP_RUN_DIR/pr-comment.md`
+   - write `$ACP_RESULT_FILE` exactly like this:
+   ```bash
+   cat > "$ACP_RESULT_FILE" <<'EOF'
+   OUTCOME=no-change-needed
+   ACTION=host-refresh-pr-state
+   PR_NUMBER={PR_NUMBER}
+   ISSUE_ID={PR_LINKED_ISSUE_ID}
+   EOF
+   ```
+   - exit successfully after saving the summary comment
+9. If you are blocked or cannot fix the branch safely after addressing any actionable review findings and running the narrowest feasible verification, write `$ACP_RESULT_FILE` exactly like this:
+   ```bash
+   cat > "$ACP_RESULT_FILE" <<'EOF'
+   OUTCOME=blocked
+   ACTION=host-comment-pr-blocker
+   PR_NUMBER={PR_NUMBER}
+   ISSUE_ID={PR_LINKED_ISSUE_ID}
+   EOF
+   ```
+   Then exit successfully after saving the blocker summary in `$ACP_RUN_DIR/pr-comment.md`. Do not stop after printing a question or suggestion; always finish by writing one of the allowed result contracts.
+10. If you fixed the branch and left only the intended source changes ready for host-side commit/push, write `$ACP_RESULT_FILE` exactly like this:
+   ```bash
+   cat > "$ACP_RESULT_FILE" <<'EOF'
+   OUTCOME=updated-branch
+   ACTION=host-push-pr-branch
+   PR_NUMBER={PR_NUMBER}
+   ISSUE_ID={PR_LINKED_ISSUE_ID}
+   EOF
+   ```
+   Only use this outcome after you have confirmed the branch no longer has remaining local merge-conflict paths against `{PR_BASE_REF}`, you did not run Git commit/push commands yourself, and `$ACP_RUN_DIR/verification.jsonl` contains the successful verification commands you actually ran.
+11. Exit after writing the result file. The host reconciler will push the updated branch, comment on the PR, refresh labels, and leave CI to rerun on GitHub. Never end this run with a question to the user instead of a result file.

package/tools/templates/pr-merge-repair-template.md

@@ -0,0 +1,91 @@
+You are the PR merge-repair worker for `{REPO_SLUG}`.
+
+Before making any change:
+
+1. Read `{REPO_ROOT}/AGENTS.md`.
+2. Read `{REPO_ROOT}/openspec/AGENT_RULES.md`.
+3. Read `{REPO_ROOT}/openspec/AGENTS.md`.
+4. Read `{REPO_ROOT}/openspec/project.md`.
+5. Read `{REPO_ROOT}/openspec/CONVENTIONS.md`.
+6. Read `{REPO_ROOT}/docs/TESTING_AND_SEED_POLICY.md`.
+7. Stay on this PR branch worktree. Do not push or mutate GitHub from inside the worker.
+
+PR metadata:
+
+- PR: {PR_NUMBER} - {PR_TITLE}
+- URL: {PR_URL}
+- Base branch: {PR_BASE_REF}
+- Head branch: {PR_HEAD_REF}
+- Linked issue: {PR_LINKED_ISSUE_ID}
+- Risk classification: {PR_RISK}
+- Risk reason: {PR_RISK_REASON}
+- Merge state: {PR_MERGE_STATE_STATUS}
+- Mergeable: {PR_MERGEABLE_STATUS}
+- Host-prepared merge status: {PR_HOST_MERGE_STATUS}
+
+Changed files:
+{PR_FILES_TEXT}
+
+Current unresolved merge-conflict paths:
+{PR_CONFLICT_PATHS_TEXT}
+
+Host merge preparation notes:
+{PR_HOST_MERGE_SUMMARY_TEXT}
+
+Current GitHub checks:
+{PR_CHECKS_TEXT}
+
+Current missing reasons:
+{PR_MISSING_REASONS_TEXT}
+
+Actionable current-head review findings:
+{PR_REVIEW_FINDINGS_TEXT}
+
+PR body:
+{PR_BODY}
+
+Required flow:
+
+1. Treat this worktree as an already-prepared merge repair state from host control-plane.
+   - `origin/{PR_BASE_REF}` has already been merged into this worktree locally.
+   - if `Current unresolved merge-conflict paths` is not `- none detected after host merge preparation`, resolve those files first.
+2. Never run Git control commands from inside the worker:
+   - do not run `git fetch`, `git pull`, `git merge`, `git rebase`, `git commit`, `git push`, or any command that writes Git metadata
+   - do not abort or restart the prepared merge state
+3. Inspect only the concrete branch-repair state you were given:
+   - `openspec list`
+   - `git status --short`
+   - `git diff --check`
+   - `git diff --name-only --diff-filter=U`
+   - if you need context for a conflicted file, inspect the local conflict markers and surrounding source in this worktree
+4. Make the smallest source-only edits needed to finish the merge repair while preserving the PR intent.
+   - keep unrelated auto-merged files alone
+   - do not reformat broad areas or rewrite unrelated logic
+5. Run the narrowest verification that proves the repaired conflict is safe.
+   - After each successful verification command, record it with:
+     `bash "$ACP_FLOW_TOOLS_DIR/record-verification.sh" --run-dir "$ACP_RUN_DIR" --status pass --command "<exact command>"`
+   - If you changed a `*.spec.*` or `*.test.*` file while resolving the merge, include a targeted test command for that file or the directly related surface.
+6. If host already prepared a clean merge state and no unresolved conflict paths remain, do not use `no-change-needed`.
+   - write `updated-branch` so host reconcile can commit and push the prepared merge repair
+7. Save a short markdown summary to `$ACP_RUN_DIR/pr-comment.md`.
+8. If you cannot safely resolve the prepared merge state, write `$ACP_RESULT_FILE` exactly like this:
+   ```bash
+   cat > "$ACP_RESULT_FILE" <<'EOF'
+   OUTCOME=blocked
+   ACTION=host-comment-pr-blocker
+   PR_NUMBER={PR_NUMBER}
+   ISSUE_ID={PR_LINKED_ISSUE_ID}
+   EOF
+   ```
+   Then exit successfully after saving the blocker summary.
+9. If the prepared merge state is now clean and ready for host commit/push, write `$ACP_RESULT_FILE` exactly like this:
+   ```bash
+   cat > "$ACP_RESULT_FILE" <<'EOF'
+   OUTCOME=updated-branch
+   ACTION=host-push-pr-branch
+   PR_NUMBER={PR_NUMBER}
+   ISSUE_ID={PR_LINKED_ISSUE_ID}
+   EOF
+   ```
+   Only use this outcome after `$ACP_RUN_DIR/verification.jsonl` contains the successful verification commands you actually ran.
+10. Exit after writing the result file. Host reconcile owns the commit/push/label refresh.