@plainconceptsplatform/agent-harness 2.0.0 → 2.0.1

package/src/content/.opencode/tui/pc-subagents.tsx

@@ -1,98 +1,98 @@
-/** @jsxImportSource @opentui/solid */
-import type { TuiPlugin, TuiPluginModule } from "@opencode-ai/plugin/tui"
-import { createSignal, For, Show } from "solid-js"
-import { readFile } from "node:fs/promises"
-import { join } from "node:path"
-
-const id = "ob.subagents"
-
-type Row = { id: string; agent: string; model: string; task: string; status: string }
-
-// Renders a live "Subagents" panel in the session sidebar.
-//
-// Server plugins (opencode.json) cannot draw UI, only TUI plugins (tui.json)
-// can, via the `sidebar_content` slot. This panel is fed by the
-// `.opencode/harness-run.json` state file that the `pc-subagent-monitor` server
-// plugin maintains, so the two cooperate: server plugin = data producer,
-// this TUI plugin = renderer.
-const tui: TuiPlugin = async (api) => {
-  const statePath = join(process.cwd(), ".opencode", "harness-run.json")
-  const [rows, setRows] = createSignal<Row[]>([])
-  // Only show live subagents, finished/failed ones are kept in harness-run.json
-  // for recovery but are not navigable targets the user cares about here.
-  // Entries marked stale (left "running" by a crashed process) are not live.
-  const active = () => rows().filter((r) => r.status === "running")
-
-  const refresh = async () => {
-    try {
-      const data = JSON.parse(await readFile(statePath, "utf-8"))
-      const agents = data?.agents ?? {}
-      setRows(
-        Object.entries(agents)
-          .filter(([, a]: [string, any]) => !a?.stale)
-          .map(([sid, a]: [string, any]) => ({
-            id: sid,
-            agent: a?.agent ?? "?",
-            model: a?.model ?? "",
-            task: Array.isArray(a?.tasks) && a.tasks.length ? a.tasks.join(",") : (a?.title ?? ""),
-            status: a?.status ?? "running",
-          })),
-      )
-    } catch (err: any) {
-      // Missing file = genuinely idle. Anything else (transient read/parse
-      // hiccup) keeps the last good rows instead of flashing "idle" mid-run.
-      if (err?.code === "ENOENT") setRows([])
-    }
-  }
-
-  await refresh()
-  // session.updated fires constantly; debounce so we don't re-read the file
-  // on every keystroke-sized event.
-  let timer: ReturnType<typeof setTimeout> | null = null
-  const scheduleRefresh = () => {
-    if (timer) return
-    timer = setTimeout(() => {
-      timer = null
-      void refresh()
-    }, 200)
-  }
-  for (const evt of ["session.created", "session.idle", "session.updated"]) {
-    try {
-      api.event.on(evt as any, scheduleRefresh)
-    } catch {
-      /* event type unavailable on this host, ignore */
-    }
-  }
-
-  api.slots.register({
-    order: 50,
-    slots: {
-      sidebar_content() {
-        return (
-          <box flexDirection="column">
-            <text>Subagents</text>
-            <Show when={active().length === 0}>
-              <text>  idle</text>
-            </Show>
-            <For each={active()}>
-              {(r) => (
-                <box onMouseUp={() => api.route.navigate("session", { sessionID: r.id })}>
-                  <text>
-                    {"▶ "}
-                    {r.agent}
-                    {r.model ? ` · ${r.model}` : ""}
-                    {r.task ? `, ${r.task}` : ""}
-                  </text>
-                </box>
-              )}
-            </For>
-          </box>
-        )
-      },
-    },
-  })
-}
-
-const pluginModule: TuiPluginModule & { id: string } = { id, tui }
-
-export default pluginModule
+/** @jsxImportSource @opentui/solid */
+import type { TuiPlugin, TuiPluginModule } from "@opencode-ai/plugin/tui"
+import { createSignal, For, Show } from "solid-js"
+import { readFile } from "node:fs/promises"
+import { join } from "node:path"
+
+const id = "ob.subagents"
+
+type Row = { id: string; agent: string; model: string; task: string; status: string }
+
+// Renders a live "Subagents" panel in the session sidebar.
+//
+// Server plugins (opencode.json) cannot draw UI, only TUI plugins (tui.json)
+// can, via the `sidebar_content` slot. This panel is fed by the
+// `.opencode/harness-run.json` state file that the `pc-subagent-monitor` server
+// plugin maintains, so the two cooperate: server plugin = data producer,
+// this TUI plugin = renderer.
+const tui: TuiPlugin = async (api) => {
+  const statePath = join(process.cwd(), ".opencode", "harness-run.json")
+  const [rows, setRows] = createSignal<Row[]>([])
+  // Only show live subagents, finished/failed ones are kept in harness-run.json
+  // for recovery but are not navigable targets the user cares about here.
+  // Entries marked stale (left "running" by a crashed process) are not live.
+  const active = () => rows().filter((r) => r.status === "running")
+
+  const refresh = async () => {
+    try {
+      const data = JSON.parse(await readFile(statePath, "utf-8"))
+      const agents = data?.agents ?? {}
+      setRows(
+        Object.entries(agents)
+          .filter(([, a]: [string, any]) => !a?.stale)
+          .map(([sid, a]: [string, any]) => ({
+            id: sid,
+            agent: a?.agent ?? "?",
+            model: a?.model ?? "",
+            task: Array.isArray(a?.tasks) && a.tasks.length ? a.tasks.join(",") : (a?.title ?? ""),
+            status: a?.status ?? "running",
+          })),
+      )
+    } catch (err: any) {
+      // Missing file = genuinely idle. Anything else (transient read/parse
+      // hiccup) keeps the last good rows instead of flashing "idle" mid-run.
+      if (err?.code === "ENOENT") setRows([])
+    }
+  }
+
+  await refresh()
+  // session.updated fires constantly; debounce so we don't re-read the file
+  // on every keystroke-sized event.
+  let timer: ReturnType<typeof setTimeout> | null = null
+  const scheduleRefresh = () => {
+    if (timer) return
+    timer = setTimeout(() => {
+      timer = null
+      void refresh()
+    }, 200)
+  }
+  for (const evt of ["session.created", "session.idle", "session.updated"]) {
+    try {
+      api.event.on(evt as any, scheduleRefresh)
+    } catch {
+      /* event type unavailable on this host, ignore */
+    }
+  }
+
+  api.slots.register({
+    order: 50,
+    slots: {
+      sidebar_content() {
+        return (
+          <box flexDirection="column">
+            <text>Subagents</text>
+            <Show when={active().length === 0}>
+              <text>  idle</text>
+            </Show>
+            <For each={active()}>
+              {(r) => (
+                <box onMouseUp={() => api.route.navigate("session", { sessionID: r.id })}>
+                  <text>
+                    {"▶ "}
+                    {r.agent}
+                    {r.model ? ` · ${r.model}` : ""}
+                    {r.task ? `, ${r.task}` : ""}
+                  </text>
+                </box>
+              )}
+            </For>
+          </box>
+        )
+      },
+    },
+  })
+}
+
+const pluginModule: TuiPluginModule & { id: string } = { id, tui }
+
+export default pluginModule

package/src/content/.opencode/tui.json

@@ -1,6 +1,6 @@
-{
-  "$schema": "https://opencode.ai/tui.json",
-  "plugin": [
-    "./tui/pc-subagents.tsx"
-  ]
-}
+{
+  "$schema": "https://opencode.ai/tui.json",
+  "plugin": [
+    "./tui/pc-subagents.tsx"
+  ]
+}

package/src/content/AGENTS.md

@@ -1,71 +1,71 @@
-# AGENTS.md
-
-<!-- PC-NOT-INITIALIZED -->
-
-# Agent operating guide
-
-This guide defines the common operating contract for AI agents in this repository.
-It is agent-agnostic and works with OpenCode, Claude Code, Codex, Gemini, and other agents.
-
-## Purpose and scope
-
-Use this file for repository-wide workflow rules. Keep product architecture, security constraints, and design rules in their source documents rather than duplicating them here.
-
-## Session context
-
-Before a non-trivial change, read these documents in order:
-
-1. `AGENTS.md` for workflow and repository rules.
-2. `ARCHITECTURE.md` for boundaries, dependencies, and component interactions.
-3. `DESIGN.md` for UI and design-system work.
-4. The active OpenSpec change or the relevant specification for the area being changed.
-
-Read each document once per session unless it changes or the task moves into a different area.
-
-Command aliases: OpenSpec skills may reference `/opsx-propose`, `/opsx-apply`, `/opsx-archive`, or `/opsx-explore`. Always substitute them with the `pc-plan-propose`, `pc-plan-apply`, `pc-plan-archive`, and `pc-plan-explore` skills respectively. User-facing command names are `/plan-propose`, `/plan-apply`, `/plan-archive`, and `/plan-explore`. Never mention the `opsx-` names to the user.
-
-## Workflow ownership
-
-<!-- PC-PLATFORM-WORKFLOW-START -->
-<!-- PC-PLATFORM-WORKFLOW-END -->
-
-## Planning and execution
-
-- Plan before delegating work. Use OpenSpec when the change needs explicit scope, decisions, or sequenced tasks.
-- Keep changes focused. Do not combine unrelated refactors with requested work.
-- Do not guess when requirements, architecture, or security constraints are unclear. Ask before proceeding.
-- Prefer the project's established patterns and source documents over introducing new conventions.
-
-## Engineer selection
-
-Inspect `.opencode/agents/*.md` before spawning. Prefer the most specialized custom engineer. `fullstack-engineer` is `mode: primary`, the planning agent, and is not a spawned worker. If no specialist matches, tell the user to create one with `/make-engineer`. Spawn only engineers present in that directory.
-
-The `pc-plan-apply` skill is authoritative for subagent waves, dependency ordering, retries, and concurrency. Read `agents.maxConcurrent` from `.opencode/harness.json` before spawning workers.
-
-## Tool and repository safety
-
-- Never expose or commit secrets, credentials, tokens, or production data.
-- Read before editing. Respect repository ownership, generated files, and existing local changes.
-- Run only commands appropriate to the task. Do not bypass checks, weaken tests, or silence lint rules to get a green result.
-- Commit, push, create pull requests, alter dependencies, or change deployment configuration only with the user's explicit approval and the repository's stated process.
-
-## Verification and completion
-
-- Run the applicable tests, lint, typecheck, and build before reporting completion.
-- A bug fix needs a test that would have caught the defect when practical.
-- Update specifications, architecture, or design documentation when the change makes their current statements inaccurate.
-- Report changed files, checks run, and any remaining risk or follow-up work.
-
-## Communication
-
-- Keep updates concise and factual.
-- State blockers early and explain the decision needed.
-- Use the repository's language and writing conventions for source, documentation, issues, commits, and pull requests.
-- Comments explain non-obvious reasons, constraints, or invariants. Do not add comments that restate code.
-
-## Skills
-
-Skills live in `.agents/skills/`. Always installed: `@pc-guardrails-generic`, `@pc-guardrails-project`, and `@browser-automation`. The always-installed `pc-system-reminders` plugin loads each agent's `## Abilities` before work, guardrails first. Skills can require mandatory transitive loads. Keep `## Abilities` complete and do not treat entries as passive references.
-
-<!-- PC-PLATFORM-SKILLS-GUIDE-START -->
-<!-- PC-PLATFORM-SKILLS-GUIDE-END -->
+# AGENTS.md
+
+<!-- PC-NOT-INITIALIZED -->
+
+# Agent operating guide
+
+This guide defines the common operating contract for AI agents in this repository.
+It is agent-agnostic and works with OpenCode, Claude Code, Codex, Gemini, and other agents.
+
+## Purpose and scope
+
+Use this file for repository-wide workflow rules. Keep product architecture, security constraints, and design rules in their source documents rather than duplicating them here.
+
+## Session context
+
+Before a non-trivial change, read these documents in order:
+
+1. `AGENTS.md` for workflow and repository rules.
+2. `ARCHITECTURE.md` for boundaries, dependencies, and component interactions.
+3. `DESIGN.md` for UI and design-system work.
+4. The active OpenSpec change or the relevant specification for the area being changed.
+
+Read each document once per session unless it changes or the task moves into a different area.
+
+Command aliases: OpenSpec skills may reference `/opsx-propose`, `/opsx-apply`, `/opsx-archive`, or `/opsx-explore`. Always substitute them with the `pc-plan-propose`, `pc-plan-apply`, `pc-plan-archive`, and `pc-plan-explore` skills respectively. User-facing command names are `/plan-propose`, `/plan-apply`, `/plan-archive`, and `/plan-explore`. Never mention the `opsx-` names to the user.
+
+## Workflow ownership
+
+<!-- PC-PLATFORM-WORKFLOW-START -->
+<!-- PC-PLATFORM-WORKFLOW-END -->
+
+## Planning and execution
+
+- Plan before delegating work. Use OpenSpec when the change needs explicit scope, decisions, or sequenced tasks.
+- Keep changes focused. Do not combine unrelated refactors with requested work.
+- Do not guess when requirements, architecture, or security constraints are unclear. Ask before proceeding.
+- Prefer the project's established patterns and source documents over introducing new conventions.
+
+## Engineer selection
+
+Inspect `.opencode/agents/*.md` before spawning. Prefer the most specialized custom engineer. `fullstack-engineer` is `mode: primary`, the planning agent, and is not a spawned worker. If no specialist matches, tell the user to create one with `/make-engineer`. Spawn only engineers present in that directory.
+
+The `pc-plan-apply` skill is authoritative for subagent waves, dependency ordering, retries, and concurrency. Read `agents.maxConcurrent` from `.opencode/harness.json` before spawning workers.
+
+## Tool and repository safety
+
+- Never expose or commit secrets, credentials, tokens, or production data.
+- Read before editing. Respect repository ownership, generated files, and existing local changes.
+- Run only commands appropriate to the task. Do not bypass checks, weaken tests, or silence lint rules to get a green result.
+- Commit, push, create pull requests, alter dependencies, or change deployment configuration only with the user's explicit approval and the repository's stated process.
+
+## Verification and completion
+
+- Run the applicable tests, lint, typecheck, and build before reporting completion.
+- A bug fix needs a test that would have caught the defect when practical.
+- Update specifications, architecture, or design documentation when the change makes their current statements inaccurate.
+- Report changed files, checks run, and any remaining risk or follow-up work.
+
+## Communication
+
+- Keep updates concise and factual.
+- State blockers early and explain the decision needed.
+- Use the repository's language and writing conventions for source, documentation, issues, commits, and pull requests.
+- Comments explain non-obvious reasons, constraints, or invariants. Do not add comments that restate code.
+
+## Skills
+
+Skills live in `.agents/skills/`. Always installed: `@pc-guardrails-generic`, `@pc-guardrails-project`, and `@browser-automation`. The always-installed `pc-system-reminders` plugin loads each agent's `## Abilities` before work, guardrails first. Skills can require mandatory transitive loads. Keep `## Abilities` complete and do not treat entries as passive references.
+
+<!-- PC-PLATFORM-SKILLS-GUIDE-START -->
+<!-- PC-PLATFORM-SKILLS-GUIDE-END -->

package/src/fragments/archive/az.md

@@ -1,95 +1,95 @@
-2. **Find the oldest change with a completed PR**
-
-   List unarchived changes (top-level only, excludes `archive/`):
-
-   ```bash
-   find "$REPO_ROOT/openspec/changes" -mindepth 1 -maxdepth 1 -type d -not -name 'archive' | sort
-   ```
-
-   If empty, report a blocker and stop.
-
-   List completed PRs:
-
-   ```bash
-   az repos pr list --repository {repo} --status completed --query "sort_by(@, &closedDate)[].{name:title,sourceRefName:sourceRefName,closedDate:closedDate,pullRequestId:pullRequestId}"
-   ```
-
-   Match each change to a completed PR using its ID and slug as search hints:
-   - No match → skip (record as blocked: `no merged PR found`).
-   - One match → eligible.
-   - Multiple matches → ask the user which PR belongs to that change.
-
-   If nothing is eligible, report a blocker and stop. Otherwise select the eligible change with the **oldest** PR `closedDate` as the candidate.
-
-3. **Confirm the candidate**
-
-   Show the candidate (ID, title, PR ID, merged date) and any blocked changes, then ask:
-
-   ```text
-   Oldest unarchived merged change found:
-     ID: {change-id}
-     Title: {title from resolved PR}
-     PR ID: {pullRequestId}
-     Merged: {closedDate}
-
-   Proceed with archiving? [yes/no]
-   ```
-
-   Stop if the user does not confirm.
-
-4. **Archive the change**
-
-   ```bash
-   git checkout -b archive/{change-id}
-   ```
-
-   Load `@openspec-archive-change` skill and follow it to archive the change.
-
-5. **Update docs**
-
-   Compare the archived change's specs against `ARCHITECTURE.md` and `DESIGN.md`. If updates are needed, show them and get user approval before applying.
-
-6. **Create the archive PR**
-
-   ```bash
-   git add -A
-   git commit -m "archive: {title} ({change-id})"
-   git push origin archive/{change-id}
-
-   az repos pr create \
-     --repository {repo} \
-     --source-branch refs/heads/archive/{change-id} \
-     --target-branch "refs/heads/$DEFAULT_BRANCH" \
-     --title "archive: {title} ({change-id})" \
-     --description "Archive SDD artifacts for {change-id} after merge of {sourceRefName}." \
-     --auto-complete
-   ```
-
-   If work was stashed in step 1, restore it after the PR is created unless the user opts out.
-
-7. **Report**
-
-   Display:
-
-   ```text
-   Archive complete
-
-     Change ID: {change-id}
-     Title: {title}
-     Original PR: {original-pr-link}
-     Archive PR: {archive-pr-link}
-
-     Documentation updates:
-     - ARCHITECTURE.md: {count} changes applied
-     - DESIGN.md: {count} changes applied
-   ```
-
-## Rules
-
-- All OpenSpec paths resolve from `git rev-parse --show-toplevel`. Never use `/openspec/...`.
-- Only process top-level directories in `$REPO_ROOT/openspec/changes/`; exclude `archive/`.
-- Use change ID and slug only as search hints; do not assume the source branch name.
-- The oldest eligible merged change is the only candidate: never ask the user which change to archive (but do ask which PR if multiple match one change).
-- Never proceed if the selected PR is not completed.
-- Never use browser tools or direct web requests for Azure DevOps. Use `az` CLI only.
-- Never invent or guess PR, branch, or merge metadata.
+2. **Find the oldest change with a completed PR**
+
+   List unarchived changes (top-level only, excludes `archive/`):
+
+   ```bash
+   find "$REPO_ROOT/openspec/changes" -mindepth 1 -maxdepth 1 -type d -not -name 'archive' | sort
+   ```
+
+   If empty, report a blocker and stop.
+
+   List completed PRs:
+
+   ```bash
+   az repos pr list --repository {repo} --status completed --query "sort_by(@, &closedDate)[].{name:title,sourceRefName:sourceRefName,closedDate:closedDate,pullRequestId:pullRequestId}"
+   ```
+
+   Match each change to a completed PR using its ID and slug as search hints:
+   - No match → skip (record as blocked: `no merged PR found`).
+   - One match → eligible.
+   - Multiple matches → ask the user which PR belongs to that change.
+
+   If nothing is eligible, report a blocker and stop. Otherwise select the eligible change with the **oldest** PR `closedDate` as the candidate.
+
+3. **Confirm the candidate**
+
+   Show the candidate (ID, title, PR ID, merged date) and any blocked changes, then ask:
+
+   ```text
+   Oldest unarchived merged change found:
+     ID: {change-id}
+     Title: {title from resolved PR}
+     PR ID: {pullRequestId}
+     Merged: {closedDate}
+
+   Proceed with archiving? [yes/no]
+   ```
+
+   Stop if the user does not confirm.
+
+4. **Archive the change**
+
+   ```bash
+   git checkout -b archive/{change-id}
+   ```
+
+   Load `@openspec-archive-change` skill and follow it to archive the change.
+
+5. **Update docs**
+
+   Compare the archived change's specs against `ARCHITECTURE.md` and `DESIGN.md`. If updates are needed, show them and get user approval before applying.
+
+6. **Create the archive PR**
+
+   ```bash
+   git add -A
+   git commit -m "archive: {title} ({change-id})"
+   git push origin archive/{change-id}
+
+   az repos pr create \
+     --repository {repo} \
+     --source-branch refs/heads/archive/{change-id} \
+     --target-branch "refs/heads/$DEFAULT_BRANCH" \
+     --title "archive: {title} ({change-id})" \
+     --description "Archive SDD artifacts for {change-id} after merge of {sourceRefName}." \
+     --auto-complete
+   ```
+
+   If work was stashed in step 1, restore it after the PR is created unless the user opts out.
+
+7. **Report**
+
+   Display:
+
+   ```text
+   Archive complete
+
+     Change ID: {change-id}
+     Title: {title}
+     Original PR: {original-pr-link}
+     Archive PR: {archive-pr-link}
+
+     Documentation updates:
+     - ARCHITECTURE.md: {count} changes applied
+     - DESIGN.md: {count} changes applied
+   ```
+
+## Rules
+
+- All OpenSpec paths resolve from `git rev-parse --show-toplevel`. Never use `/openspec/...`.
+- Only process top-level directories in `$REPO_ROOT/openspec/changes/`; exclude `archive/`.
+- Use change ID and slug only as search hints; do not assume the source branch name.
+- The oldest eligible merged change is the only candidate: never ask the user which change to archive (but do ask which PR if multiple match one change).
+- Never proceed if the selected PR is not completed.
+- Never use browser tools or direct web requests for Azure DevOps. Use `az` CLI only.
+- Never invent or guess PR, branch, or merge metadata.