gcf-harness-aif-ext 0.31.0 → 0.33.0
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/README.md +4 -0
- package/extension.json +1 -1
- package/package.json +2 -2
- package/skills/gcf-run/SKILL.md +7 -1
package/README.md
CHANGED
|
@@ -43,6 +43,10 @@ ai-factory extension update gcf-harness-aif-ext
|
|
|
43
43
|
|
|
44
44
|
Updating keeps the hook entry valid — it points into the extension's install directory, which an update refreshes in place.
|
|
45
45
|
|
|
46
|
+
0.33.0 needs gcf-aif-ext 0.34 (docs/Until-Records-Plan.md): update both together with gcf-board 0.34.0, then run `ai-factory gcf init` (the `AGENTS.md` block changed). `/gcf-run` hands the readset's `d2_fired` to its subagents with the `d2` lines and plans on no fired value: a plan that needs one blocks the item once, naming the record (`needs the human's answer to <q-NNN> (its until fired)`), and the human answers on that record, never on a new D1. The core's audit now names a fired D2 on its first line and the board shows it among the decisions; `retune(<sys>)` counts only the tunes after the record.
|
|
47
|
+
|
|
48
|
+
0.32.0 changes nothing but the peer range: it runs with `gcf-aif-ext` 0.33, where an operator's move from a terminal or the board waits behind a card's main run instead of a refusal (docs/Main-Run-Moves-Plan.md). Update it together with gcf-aif-ext 0.33.0 and gcf-board 0.33.0.
|
|
49
|
+
|
|
46
50
|
0.31.0 needs gcf-aif-ext 0.32 (docs/Fallback-Fidelity-Plan.md): update both together with gcf-board 0.32.0 (`gcf board --json` is `schema: 6`), then run `ai-factory gcf init`. `run_mode` is `main` by default now; set `run_mode: worktree` to keep parallel runs. Without `--mode` an item runs where the core says (`runs_in`): its own `run_mode`, else where its kept session ran (the record `<id>.agent.json` now carries `mode`; `--fresh` drops the session, not that place), else `worktree` while its worktree copy or `work/<id>` branch lives, else the project's. A review row that cannot make its pass (codex-review `failed`, `skipped` for no Codex, the Agent tool's refusal, a subagent with no answer or at its usage limit) gives way to the next of its `fallback`, then to the session's own model; the pass records `--by <who> --for <the row>`. A subagent's usage limit no longer stops the session (bundled gcf-session).
|
|
47
51
|
|
|
48
52
|
0.25.1 changes nothing but the peer range: it runs with `gcf-aif-ext` 0.26 and 0.27.
|
package/extension.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "https://raw.githubusercontent.com/lee-to/ai-factory/2.x/schemas/extension.schema.json",
|
|
3
3
|
"name": "gcf-harness-aif-ext",
|
|
4
|
-
"version": "0.
|
|
4
|
+
"version": "0.33.0",
|
|
5
5
|
"description": "GCF orchestration harness for Claude Code: one-command card pipeline, readset guard",
|
|
6
6
|
"skills": [
|
|
7
7
|
"skills/gcf-run",
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "gcf-harness-aif-ext",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.33.0",
|
|
4
4
|
"description": "GCF orchestration harness for Claude Code: one-command card pipeline, readset guard",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|
|
@@ -28,7 +28,7 @@
|
|
|
28
28
|
"prepack": "node -e \"const p=require('./package.json'),e=require('./extension.json');if(p.version!==e.version)throw new Error('version mismatch: package.json '+p.version+' vs extension.json '+e.version);require('node:fs').statSync('node_modules/gcf-session/lib/index.js')\""
|
|
29
29
|
},
|
|
30
30
|
"peerDependencies": {
|
|
31
|
-
"gcf-aif-ext": ">=0.
|
|
31
|
+
"gcf-aif-ext": ">=0.34.0 <0.35.0"
|
|
32
32
|
},
|
|
33
33
|
"dependencies": {
|
|
34
34
|
"gcf-session": "file:../gcf-session"
|
package/skills/gcf-run/SKILL.md
CHANGED
|
@@ -108,9 +108,15 @@ forbidden_behaviors:
|
|
|
108
108
|
- a call the handoff guard denies with "context at", "the operator holds this item" or "reserve" is no refusal: block nothing, write the `## Handoff` it asks for and end the reply
|
|
109
109
|
- an aif-implement the implement guard denies for the planning phase or an unconverged plan is no refusal either: record the pass, if any, and end the reply; the harness starts the next session
|
|
110
110
|
- a read the readset guard denies is no refusal either: drop that read; never add a `system:` or `depends:` only to read a file - when one of them is wrong in substance, fix it on main, and under `--worktree` stop with a block that names the fix
|
|
111
|
-
- the context's `graveyard_hits` and `
|
|
111
|
+
- the context's `graveyard_hits`, `d2` and `d2_fired` lines belong to the readset: hand them to every fresh subagent of steps 8 and 14 in its prompt
|
|
112
112
|
- a design question of step 12 also gets a D1 record: `ai-factory gcf question add --class D1 --question "<question>" --proposed "<your answer>" --blocks <id>`, before the block
|
|
113
113
|
- under `--worktree` that question goes into the block reason only, and the human files its D1 on main
|
|
114
|
+
- do not rely on a value of a D2 that step 6 lists in `d2_fired`: its trigger fired, and the value is the human's call now
|
|
115
|
+
- a fired D2 is not re-filed as a D1: the human answers its own record (the board's Overrule, or `ai-factory gcf question answer <q-NNN>`)
|
|
116
|
+
- only a plan that needs such a value stops: `ai-factory gcf block <id> --reason "needs the human's answer to <q-NNN> (its until fired)"`
|
|
117
|
+
- an item already blocked on that `<q-NNN>` gets no second block; under `--worktree` the reason goes to step 22
|
|
118
|
+
- an assumption with no record - a fired inline `until` annotation, or a belief the work shows false - is a D1 of step 12
|
|
119
|
+
- a fired assumption never goes to the inbox as a finding
|
|
114
120
|
- delete one file with `rm -f <file>` or `Remove-Item -Force <file>`, never with `-r`: the deny rules refuse a recursive delete
|
|
115
121
|
- do not run `git stash`: its stack is the checkout's and every worktree's, and a pop may take the human's work
|
|
116
122
|
- for a clean tree to build or check in, run `git worktree add --detach <tmp> HEAD` and work there
|