@plainconceptsplatform/agent-harness 3.3.1 → 3.5.0

package/cli/fragments/archive/gl.md

@@ -1,96 +1,96 @@
-2. **Find the oldest change with a completed MR**
-
-   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 merge requests:
-
-   ```bash
-   glab mr list --repo {owner}/{repo} --merged --output json --jq 'sort_by(.merged_at) | .[] | {name: .title, sourceRefName: .source_branch, mergedAt: .merged_at, mergeRequestId: .iid}'
-   ```
-
-   Match each change to a completed MR using its ID and slug as search hints:
-   - No match → skip (record as blocked: `no merged MR found`).
-   - One match → eligible.
-   - Multiple matches → ask the user which MR belongs to that change.
-
-   If nothing is eligible, report a blocker and stop. Otherwise select the eligible change with the **oldest** MR `merged_at` as the candidate.
-
-3. **Confirm the candidate**
-
-   Show the candidate (ID, title, MR ID, merged date) and any blocked changes, then ask:
-
-   ```text
-   Oldest unarchived merged change found:
-     ID: {change-id}
-     Title: {title from resolved MR}
-     MR ID: {iid}
-     Merged: {merged_at}
-
-   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 MR**
-
-   ```bash
-   # Stage specific paths only: a shared tree may hold another agent's or a
-   # person's edits, and -A commits them under this message.
-   git add openspec/changes/   # plus ARCHITECTURE.md / DESIGN.md if step 5 updated them
-   git commit -m "archive: {title} ({change-id})"
-   git push origin archive/{change-id}
-
-   glab mr create \
-      --repo {owner}/{repo} \
-      --source-branch "archive/{change-id}" \
-      --target-branch "$DEFAULT_BRANCH" \
-      --title "archive: {title} ({change-id})" \
-      --description "Archive SDD artifacts for {change-id} after merge."
-   ```
-
-   If work was stashed in step 1, restore it after the MR is created unless the user opts out.
-
-7. **Report**
-
-   Display:
-
-   ```text
-   Archive complete
-
-     Change ID: {change-id}
-     Title: {title}
-     Original MR: {original-mr-link}
-     Archive MR: {archive-mr-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 MR if multiple match one change).
-- Never proceed if the selected MR is not completed.
-- Never use browser tools or direct web requests for GitLab. Use `glab` CLI only.
-- Never invent or guess MR, branch, or merge metadata.
+2. **Find the oldest change with a completed MR**
+
+   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 merge requests:
+
+   ```bash
+   glab mr list --repo {owner}/{repo} --merged --output json --jq 'sort_by(.merged_at) | .[] | {name: .title, sourceRefName: .source_branch, mergedAt: .merged_at, mergeRequestId: .iid}'
+   ```
+
+   Match each change to a completed MR using its ID and slug as search hints:
+   - No match → skip (record as blocked: `no merged MR found`).
+   - One match → eligible.
+   - Multiple matches → ask the user which MR belongs to that change.
+
+   If nothing is eligible, report a blocker and stop. Otherwise select the eligible change with the **oldest** MR `merged_at` as the candidate.
+
+3. **Confirm the candidate**
+
+   Show the candidate (ID, title, MR ID, merged date) and any blocked changes, then ask:
+
+   ```text
+   Oldest unarchived merged change found:
+     ID: {change-id}
+     Title: {title from resolved MR}
+     MR ID: {iid}
+     Merged: {merged_at}
+
+   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 MR**
+
+   ```bash
+   # Stage specific paths only: a shared tree may hold another agent's or a
+   # person's edits, and -A commits them under this message.
+   git add openspec/changes/   # plus ARCHITECTURE.md / DESIGN.md if step 5 updated them
+   git commit -m "archive: {title} ({change-id})"
+   git push origin archive/{change-id}
+
+   glab mr create \
+      --repo {owner}/{repo} \
+      --source-branch "archive/{change-id}" \
+      --target-branch "$DEFAULT_BRANCH" \
+      --title "archive: {title} ({change-id})" \
+      --description "Archive SDD artifacts for {change-id} after merge."
+   ```
+
+   If work was stashed in step 1, restore it after the MR is created unless the user opts out.
+
+7. **Report**
+
+   Display:
+
+   ```text
+   Archive complete
+
+     Change ID: {change-id}
+     Title: {title}
+     Original MR: {original-mr-link}
+     Archive MR: {archive-mr-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 MR if multiple match one change).
+- Never proceed if the selected MR is not completed.
+- Never use browser tools or direct web requests for GitLab. Use `glab` CLI only.
+- Never invent or guess MR, branch, or merge metadata.

package/cli/fragments/archive/none.md

@@ -1,75 +1,75 @@
-2. **Find the oldest unarchived change**
-
-   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. Otherwise select the **oldest** change (by directory creation/sort order) as the candidate.
-
-   This mode has no platform PR integration, so completion is judged from local state only. Do not look up remote PRs or work items.
-
-3. **Confirm the candidate**
-
-   Show the candidate (ID, title) and any other unarchived changes, then ask:
-
-   ```text
-   Oldest unarchived change found:
-     ID: {change-id}
-     Title: {title from proposal.md}
-
-   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. **Commit the archive**
-
-   ```bash
-   # Stage specific paths only: a shared tree may hold another agent's or a
-   # person's edits, and -A commits them under this message.
-   git add openspec/changes/   # plus ARCHITECTURE.md / DESIGN.md if step 5 updated them
-   git commit -m "archive: {title} ({change-id})"
-   ```
-
-   No PR is created in this mode. Leave the `archive/{change-id}` branch for the user to merge or push manually if they choose.
-
-   If work was stashed in step 1, restore it after the commit unless the user opts out.
-
-7. **Report**
-
-   Display:
-
-   ```text
-   Archive complete
-
-     Change ID: {change-id}
-     Title: {title}
-     Archive branch: archive/{change-id}
-
-     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 unarchived change is the only candidate: never ask the user which change to archive.
-- This mode has no GitHub or Azure DevOps integration. Never call `gh` or `az`, and never use browser tools or direct web requests for PR/work-item lookups.
-- Never invent or guess PR, branch, or merge metadata.
+2. **Find the oldest unarchived change**
+
+   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. Otherwise select the **oldest** change (by directory creation/sort order) as the candidate.
+
+   This mode has no platform PR integration, so completion is judged from local state only. Do not look up remote PRs or work items.
+
+3. **Confirm the candidate**
+
+   Show the candidate (ID, title) and any other unarchived changes, then ask:
+
+   ```text
+   Oldest unarchived change found:
+     ID: {change-id}
+     Title: {title from proposal.md}
+
+   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. **Commit the archive**
+
+   ```bash
+   # Stage specific paths only: a shared tree may hold another agent's or a
+   # person's edits, and -A commits them under this message.
+   git add openspec/changes/   # plus ARCHITECTURE.md / DESIGN.md if step 5 updated them
+   git commit -m "archive: {title} ({change-id})"
+   ```
+
+   No PR is created in this mode. Leave the `archive/{change-id}` branch for the user to merge or push manually if they choose.
+
+   If work was stashed in step 1, restore it after the commit unless the user opts out.
+
+7. **Report**
+
+   Display:
+
+   ```text
+   Archive complete
+
+     Change ID: {change-id}
+     Title: {title}
+     Archive branch: archive/{change-id}
+
+     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 unarchived change is the only candidate: never ask the user which change to archive.
+- This mode has no GitHub or Azure DevOps integration. Never call `gh` or `az`, and never use browser tools or direct web requests for PR/work-item lookups.
+- Never invent or guess PR, branch, or merge metadata.

package/cli/fragments/guardrails/codegraph.md

@@ -1,5 +1,5 @@
-## CodeGraph
-
-- `codegraph_explore` replaces grep, glob and read for anything indexed: one call returns the relevant symbols' verbatim, line-numbered source plus the call paths between them, where finding the same thing by hand takes a dozen. Give it a symbol name, a file path, or a plain question.
-- Fall back to grep, glob and read when it returns nothing, or for what it does not index: config files, plain-text docs, `.env` patterns, raw string searches. Say that it returned nothing when you do.
-- It is an MCP server, not a CLI. Never run `codegraph` in bash.
+## CodeGraph
+
+- `codegraph_explore` replaces grep, glob and read for anything indexed: one call returns the relevant symbols' verbatim, line-numbered source plus the call paths between them, where finding the same thing by hand takes a dozen. Give it a symbol name, a file path, or a plain question.
+- Fall back to grep, glob and read when it returns nothing, or for what it does not index: config files, plain-text docs, `.env` patterns, raw string searches. Say that it returned nothing when you do.
+- It is an MCP server, not a CLI. Never run `codegraph` in bash.

package/cli/fragments/guardrails/humanizer.md

@@ -1,4 +1,4 @@
-## Humanizer (optimization skill)
-
-- Load `skill("humanizer")` before writing prose (commit messages, PR descriptions, docs, proposals); unhumanized prose reads as machine-written. Editing, shell and spawning stay blocked until it is loaded (pc-system-reminders).
-- Never apply it to code, config files, or terminal output: prose only.
+## Humanizer (optimization skill)
+
+- Load `skill("humanizer")` before writing prose (commit messages, PR descriptions, docs, proposals); unhumanized prose reads as machine-written. Editing, shell and spawning stay blocked until it is loaded (pc-system-reminders).
+- Never apply it to code, config files, or terminal output: prose only.

package/cli/fragments/guardrails/memory.md

@@ -1,4 +1,4 @@
-## Agentmemory
-
-- Cross-session context lives in the agentmemory MCP tools: `memory_smart_search` for prior decisions before working somewhere unfamiliar, `memory_save` for architecture decisions and anything the next agent will need, plus `memory_sessions` and `memory_governance_delete`.
-- It is an MCP server, not a CLI. Never run `agentmemory` in bash; start it with `agentmemory` in a separate terminal and use the tools.
+## Agentmemory
+
+- Cross-session context lives in the agentmemory MCP tools: `memory_smart_search` for prior decisions before working somewhere unfamiliar, `memory_save` for architecture decisions and anything the next agent will need, plus `memory_sessions` and `memory_governance_delete`.
+- It is an MCP server, not a CLI. Never run `agentmemory` in bash; start it with `agentmemory` in a separate terminal and use the tools.

package/cli/fragments/guardrails/rtk.md

@@ -1,3 +1,3 @@
-## RTK
-
-- Prefix CLI commands with `rtk` (`rtk git diff`, `rtk pnpm test`); it strips the output down to what matters. Read-only commands like `cat`, `ls` and `Get-Content` are exempt.
+## RTK
+
+- Prefix CLI commands with `rtk` (`rtk git diff`, `rtk pnpm test`); it strips the output down to what matters. Read-only commands like `cat`, `ls` and `Get-Content` are exempt.

package/cli/fragments/guardrails/simple-english.md

@@ -1,4 +1,4 @@
-## Simple English (optimization skill)
-
-- Apply Simplified Technical English to all prose: `skill("simple-english")`. Editing, shell and spawning stay blocked until it is loaded (pc-system-reminders).
-- Keep code blocks, identifiers, CLI commands, file paths, quoted errors, and product names exact.
+## Simple English (optimization skill)
+
+- Apply Simplified Technical English to all prose: `skill("simple-english")`. Editing, shell and spawning stay blocked until it is loaded (pc-system-reminders).
+- Keep code blocks, identifiers, CLI commands, file paths, quoted errors, and product names exact.

package/cli/fragments/ops-backlog/az.md

@@ -1,29 +1,29 @@
-Azure DevOps data comes from the `az` CLI; a page fetch of dev.azure.com is denied (pc-system-reminders). If `az` is unavailable, report it as a blocker.
-
----
-
-### Step 1: Parse input
-
-`$ARGUMENTS` is the work item title/description. If it contains a title and body separated by a newline or `---`, split them. Otherwise use the full text as the title with an empty body.
-
-### Step 2: Create work item
-
-```bash
-az boards work-item create \
-  --title "{title}" \
-  --description "{body}" \
-  --type "User Story"
-```
-
-### Step 3: Report
-
-```text
-Work item created
-  ID: {id}
-  Title: {title}
-  URL: {work-item-url}
-```
-
-Tell the user: "Use `/plan-propose {work-item-url}` to turn this into a plan."
-
+Azure DevOps data comes from the `az` CLI; a page fetch of dev.azure.com is denied (pc-system-reminders). If `az` is unavailable, report it as a blocker.
+
+---
+
+### Step 1: Parse input
+
+`$ARGUMENTS` is the work item title/description. If it contains a title and body separated by a newline or `---`, split them. Otherwise use the full text as the title with an empty body.
+
+### Step 2: Create work item
+
+```bash
+az boards work-item create \
+  --title "{title}" \
+  --description "{body}" \
+  --type "User Story"
+```
+
+### Step 3: Report
+
+```text
+Work item created
+  ID: {id}
+  Title: {title}
+  URL: {work-item-url}
+```
+
+Tell the user: "Use `/plan-propose {work-item-url}` to turn this into a plan."
+
 ---

package/cli/fragments/ops-backlog/gh.md

@@ -1,29 +1,29 @@
-GitHub data comes from the `gh` CLI; a page fetch of github.com is denied (pc-system-reminders). If `gh` is unavailable, report it as a blocker. Always pass `--repo {owner}/{repo}` explicitly, never rely on git context to resolve the repo.
-
----
-
-### Step 1: Parse input
-
-`$ARGUMENTS` is the issue title/description. If it contains a title and body separated by a newline or `---`, split them. Otherwise use the full text as the title with an empty body.
-
-### Step 2: Create issue
-
-```bash
-gh issue create \
-  --repo {owner}/{repo} \
-  --title "{title}" \
-  --body "{body}"
-```
-
-### Step 3: Report
-
-```text
-Issue created
-  URL: {issue-url}
-  Number: #{number}
-  Title: {title}
-```
-
-Tell the user: "Use `/plan-propose {issue-url}` to turn this into a plan."
-
+GitHub data comes from the `gh` CLI; a page fetch of github.com is denied (pc-system-reminders). If `gh` is unavailable, report it as a blocker. Always pass `--repo {owner}/{repo}` explicitly, never rely on git context to resolve the repo.
+
+---
+
+### Step 1: Parse input
+
+`$ARGUMENTS` is the issue title/description. If it contains a title and body separated by a newline or `---`, split them. Otherwise use the full text as the title with an empty body.
+
+### Step 2: Create issue
+
+```bash
+gh issue create \
+  --repo {owner}/{repo} \
+  --title "{title}" \
+  --body "{body}"
+```
+
+### Step 3: Report
+
+```text
+Issue created
+  URL: {issue-url}
+  Number: #{number}
+  Title: {title}
+```
+
+Tell the user: "Use `/plan-propose {issue-url}` to turn this into a plan."
+
 ---

package/cli/fragments/ops-backlog/jira.md

@@ -1,29 +1,29 @@
-Jira data comes from the `acli` CLI; a page fetch of atlassian.net is denied (pc-system-reminders). If `acli` is unavailable, report it as a blocker.
-
----
-
-### Step 1: Parse input
-
-`$ARGUMENTS` is the issue title/description. If it contains a title and body separated by a newline or `---`, split them. Otherwise use the full text as the title with an empty body.
-
-### Step 2: Create issue
-
-```bash
-acli jira issue create \
-  --summary "{title}" \
-  --description "{body}" \
-  --type "Story"
-```
-
-### Step 3: Report
-
-```text
-Issue created
-  Key: {key}
-  Title: {title}
-  URL: {issue-url}
-```
-
-Tell the user: "Use `/plan-propose {issue-url}` to turn this into a plan."
-
+Jira data comes from the `acli` CLI; a page fetch of atlassian.net is denied (pc-system-reminders). If `acli` is unavailable, report it as a blocker.
+
+---
+
+### Step 1: Parse input
+
+`$ARGUMENTS` is the issue title/description. If it contains a title and body separated by a newline or `---`, split them. Otherwise use the full text as the title with an empty body.
+
+### Step 2: Create issue
+
+```bash
+acli jira issue create \
+  --summary "{title}" \
+  --description "{body}" \
+  --type "Story"
+```
+
+### Step 3: Report
+
+```text
+Issue created
+  Key: {key}
+  Title: {title}
+  URL: {issue-url}
+```
+
+Tell the user: "Use `/plan-propose {issue-url}` to turn this into a plan."
+
 ---