@spences10/pi-harness 0.0.2 → 0.0.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@spences10/pi-harness",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.3",
|
|
4
4
|
"description": "Ephemeral task harness runtime for my-pi agent workflows",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"agent",
|
|
@@ -36,7 +36,7 @@
|
|
|
36
36
|
"access": "public"
|
|
37
37
|
},
|
|
38
38
|
"devDependencies": {
|
|
39
|
-
"@earendil-works/pi-coding-agent": "0.80.
|
|
39
|
+
"@earendil-works/pi-coding-agent": "0.80.3",
|
|
40
40
|
"@types/node": "^25.8.0",
|
|
41
41
|
"typebox": "^1.1.38",
|
|
42
42
|
"typescript": "^6.0.3",
|
|
@@ -19,13 +19,16 @@ execution contract.
|
|
|
19
19
|
before editing.
|
|
20
20
|
3. Call `harness_update` with `status: running` and the current phase.
|
|
21
21
|
4. If the `team` tool is available and you are the team lead, create
|
|
22
|
-
or reuse a team, create/claim a task for the harness, and use
|
|
23
|
-
`member_spawn` with `
|
|
24
|
-
to
|
|
22
|
+
or reuse a team, create/claim a task for the harness, and use one
|
|
23
|
+
`member_spawn` executor with `mutating: true` for file-editing
|
|
24
|
+
work. Default to the contract `cwd`; use `workspace_mode: worktree`
|
|
25
|
+
only when the user asks for isolation or the plan covers setup,
|
|
26
|
+
runtime state, merge, and cleanup ownership.
|
|
25
27
|
5. The teammate prompt must tell it to read `harness.json`,
|
|
26
28
|
`SYSTEM.md`, `TASK.md`, and `status.json`, execute only inside the
|
|
27
29
|
contract, run `validate.sh` and `review.sh`, update harness
|
|
28
|
-
evidence, and report changed files plus risks.
|
|
30
|
+
evidence, and report changed files plus risks. If using a worktree,
|
|
31
|
+
set `HARNESS_CWD` to that worktree for validation and review.
|
|
29
32
|
6. Recover any remaining source-of-truth context needed to act safely.
|
|
30
33
|
7. Execute surgically inside `allowed_paths`; do not fight
|
|
31
34
|
enforcement.
|