@plainconceptsplatform/agent-harness 2.4.0 → 2.4.1

package/harness/.agents/skills/pc-plan-apply/simple-mode.md

@@ -9,7 +9,7 @@ When the plan lives in the Todo pane (from `/plan-quick`) and no OpenSpec change
    - Mark it `in_progress` via `todowrite`.
    - Implement it (edit files, run commands as needed).
    - Mark it `completed` via `todowrite`.
-   - Commit the change: `git add -A && git commit -m "task {id}: {summary}"`.
+   - Commit the change: `git add <the paths this task wrote> && git commit -m "task {id}: {summary}"`. Never `-A` or `.`: a working tree is shared, and staging all of it commits somebody else's edits, possibly half-finished, under your message.
 4. After all tasks are done, run the project's typecheck/build check if one exists. Fix any errors.
 5. Report: tasks N/N completed, commits made, branch name.
 

package/harness/.agents/skills/pc-plan-goal/SKILL.md

@@ -12,7 +12,9 @@ Keep this checklist visible:
 
 Move forward only when a phase returns its required result. On a hard failure, follow the [failure policy](failure-policy.md). Continue after each phase skill returns; the run ends only after every checklist item is complete.
 
-**Token efficiency rules:** Batch git operations within a phase (combine `git add -A && git commit` in one tool call). Do not run status checks between sequential operations in the same phase. Minimize model turns: if a phase requires 3 git commands, call them in one tool call, not 3.
+**Token efficiency rules:** Batch git operations within a phase (combine `git add <paths> && git commit` in one tool call). Do not run status checks between sequential operations in the same phase. Minimize model turns: if a phase requires 3 git commands, call them in one tool call, not 3.
+
+**Stage paths, never `git add -A` or `git add .`.** A working tree is shared: a person or another agent may have edits in it, and staging everything puts their work in your commit under your message. It is not hypothetical. A Teams tool and its tests were committed inside a commit named after a YAML input rename, and nothing in that message said so. Two things go wrong, and the second is worse: the history lies about what changed, and unreviewed or half-finished work reaches the default branch under a heading nobody would look twice at. Saving a model turn is not worth either.
 
 Input: `$ARGUMENTS`
 
@@ -44,14 +46,14 @@ Tick `explore` when `pc-plan-explore` returns its findings handoff.
 
 ## Phase 3: Propose
 
-**Skip if `{refined}` is `true`.** Instead, create a minimal OpenSpec change directly: run `openspec new change "{change-id}"`, write `tasks.md` from the issue's acceptance criteria (one task per criterion or artifact group), create `.openspec.yaml` with `skip_specs: true` (the issue already has the spec content), and commit: `git add -A && git commit -m "propose: {title} ({change-id})"`.
+**Skip if `{refined}` is `true`.** Instead, create a minimal OpenSpec change directly: run `openspec new change "{change-id}"`, write `tasks.md` from the issue's acceptance criteria (one task per criterion or artifact group), create `.openspec.yaml` with `skip_specs: true` (the issue already has the spec content), and commit: `git add openspec/changes/{change-id}/ && git commit -m "propose: {title} ({change-id})"`.
 
 Load `pc-plan-propose` in autonomous mode with `{resolved_input}`, `EXPLORATION_BRIEF`, and `scope_classification`.
 
 Confirm its change directory and actionable `tasks.md` exist. Rename `$BRANCH` when the canonical change slug differs from `{slug}`, then commit the proposal:
 
 ```bash
-git add -A && git commit -m "propose: {title} ({change-id})"
+git add openspec/changes/{change-id}/ && git commit -m "propose: {title} ({change-id})"
 ```
 
 Tick `propose` when the proposal commit exists.
@@ -69,7 +71,7 @@ Require `verify` and a clean working tree. Load `pc-plan-archive` in autonomous
 Require `ARCHIVED_OK` and the archive path, then commit:
 
 ```bash
-git add -A && git commit -m "archive: {title} ({change-id})"
+git add openspec/changes/ && git commit -m "archive: {title} ({change-id})"
 ```
 
 Tick `archive` when the archive commit exists.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plainconceptsplatform/agent-harness",
-  "version": "2.4.0",
+  "version": "2.4.1",
   "description": "Installs the Plain Concepts Platform Harness into any codebase, and keeps it up to date. Wires OpenCode, OpenSpec, codegraph, and agentmemory into a multi-agent workflow that runs on native parallel subagents.",
   "keywords": [
     "opencode",