gcf-harness-aif-ext 0.8.7 → 0.8.9

package/commands/activity.js

@@ -25,7 +25,7 @@ const firstLines = (text, n) =>
     .join(' ');
 
 // The input field that tells most about a tool call, in this order; with none, the name alone.
-const TELLING = ['file_path', 'command', 'pattern', 'url'];
+const TELLING = ['file_path', 'command', 'pattern', 'url', 'description'];
 
 function toolLine(use) {
   const key = TELLING.find((k) => typeof use.input?.[k] === 'string');
@@ -67,8 +67,13 @@ function costOf(e) {
   };
 }
 
-function summary(e, c) {
-  const end = e.is_error ? `ended (${e.subtype ?? 'error'})` : 'done';
+function summary(e, c, limited) {
+  // A limit ends with subtype `success`: name the limit, not that.
+  const end = limited
+    ? 'ended (usage limit)'
+    : e.is_error
+      ? `ended (${e.subtype ?? 'error'})`
+      : 'done';
   const t = c.tokens;
 
   return (
@@ -87,6 +92,8 @@ function summary(e, c) {
  */
 function limitIn(text, whole = true) {
   const s = String(text ?? '').trim();
+  // shortcut: any "You've hit your … limit" counts, so an agent's whole-line "You've hit your WIP
+  // limit" would pause its item; narrow it once Claude's wordings (Opus, weekly…) are all known.
   const hit = whole ? /^You['’]ve hit your [^\n]*limit[^\n]*$/i : /hit your .*limit/i;
   if (!hit.test(s)) return {};
 
@@ -152,10 +159,12 @@ function ended(e, at) {
   const cost = costOf(e);
   const text =
     typeof e.result === 'string' && e.result.trim() ? [`${at} result:\n${e.result}`] : [];
+  // An error result counts the message anywhere in it; any other only as the whole text.
+  const limit = limitIn(e.result, !e.is_error);
 
   return {
-    lines: [...text, `${at} ${summary(e, cost)}`],
+    lines: [...text, `${at} ${summary(e, cost, Boolean(limit.limit))}`],
     cost,
-    ...(e.is_error ? limitIn(e.result, false) : {}),
+    ...limit,
   };
 }

package/extension.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://raw.githubusercontent.com/lee-to/ai-factory/2.x/schemas/extension.schema.json",
   "name": "gcf-harness-aif-ext",
-  "version": "0.8.7",
+  "version": "0.8.9",
   "description": "GCF orchestration harness for Claude Code: one-command card pipeline, readset guard",
   "skills": [
     "skills/gcf-run",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gcf-harness-aif-ext",
-  "version": "0.8.7",
+  "version": "0.8.9",
   "description": "GCF orchestration harness for Claude Code: one-command card pipeline, readset guard",
   "type": "module",
   "license": "MIT",

package/skills/gcf-run/SKILL.md

@@ -25,6 +25,18 @@ forbidden_behaviors:
 - do not compare the audit numbers yourself: the gate command is the only judge of whether an item may go
 - do not ask the human about a reversible choice during planning: pick the safe default and write it into the plan
 - do not edit `status:` or `gcf/LIVE.md` by hand: `submit`, `close` and `block` own them
+- do not write a plan task's first implementation outside the aif-implement skill: it ticks the task done in the plan, and the board shows the item's progress from those ticks
+- a fix for a red DoD or a review finding goes in directly, without aif-implement
+- do not let aif-implement commit, stash or merge: answer its questions yourself
+- at aif-implement's uncommitted-changes question pick none of its three options - not "No", which stashes - and go on with the plan
+- at aif-implement's commit checkpoints go on to the next task; skip its rules and docs checkpoints; keep the plan file; at its merge question answer that you handle it
+- a ticked task whose code aif-implement's re-entry check finds missing stays pending and gets implemented, with no question to the human
+- at aif-implement's last question, verify or commit, pick neither: go on with step 13, which verifies, and steps 14-16, which review and commit
+- do not leave a task ticked that the tune note or the answer reopens: untick it and add the note before step 13, or aif-implement's re-entry check ticks it again over the old code
+- do not route a command the permission system refused through a script, a wrapper or another spelling or shell (a full exe path, `cmd /c`, `node`, `npm run`)
+- do not write a refused command into a DoD command or a config that `ai-factory gcf` runs
+- a dedicated tool doing the same job (Read, Grep, Glob, Edit) is no wrapper, nor is a refused pipe or `;` chain split into single allowed commands
+- a refusal none of those replaces is a stop: run `ai-factory gcf block <id> --reason "needs permission: <command>"` and stop the item; under `--worktree` step 22 records it instead
 
 workflow:
 1. session ritual: delete a `.gcf-session/readset.json` left by a killed run; run `ai-factory gcf integrate` to merge the verified branches a dead run left; run `ai-factory gcf audit --json`; read `gcf/INDEX.md`; report the audit first line
@@ -39,16 +51,16 @@ workflow:
 10. after each pass run `ai-factory gcf plan check <id>`; a failure blocks the item with its reason; a pass that changes no task ends the loop - the plan converged
 11. passes <= `plan_passes` from `gcf/config.yml` (5 by default); a plan still changing after the last pass: run `ai-factory gcf block <id> --reason "plan did not converge"` and stop
 12. a question only the human can answer - a save format, a public API, a new dependency, a pillar conflict: run `ai-factory gcf block <id> --reason "<question>"` and stop
-13. implement with aif-implement, write the item's `live:` delta, then run `ai-factory gcf verify <id>` and check the item's negative constraints; a non-zero exit is a red DoD; attempts <= `dod_attempts`, each with a diagnosis
+13. run the aif-implement skill on `@<plan path>`, write the item's `live:` delta, then run `ai-factory gcf verify <id>` and check the item's negative constraints; a non-zero exit is a red DoD; attempts <= `dod_attempts`, each with a diagnosis
 14. review the diff with a fresh subagent; fix what it finds before the commit; DoD still red after the attempts: commit no code, run `ai-factory gcf block <id> --reason "<diagnosis>"` - its commit carries the item file with its delta
 15. the reviewer also answers the `review_question` of each pillar in `gcf/PILLARS.md` over the diff: an answer that breaks the pillar is a finding
-16. commit the implementation and the `live:` delta via aif-commit
+16. commit the implementation, its plan and the `live:` delta via aif-commit
 17. gate `verdict` or `decision`: run `ai-factory gcf submit <id>`; gate `auto`: run `ai-factory gcf close <id>` - a soft unit closes unplayed
 18. a dependency still waiting for its verdict refuses the close: run `ai-factory gcf block <id> --reason "waits for <dep>"`
 19. close the run: delete `.gcf-session/readset.json`, run `ai-factory gcf playtest session` and hand its checklist to the human, with one report row per plan pass: pass, tasks changed, result
 20. after a tune verdict or an unblock, re-enter this pipeline at step 5: the gates re-run because the counters moved
 21. with `--worktree`: skip the integrate of step 1, steps 2-4 and the playtest of step 19, and change no `gcf/` file but the item's `live:`
-22. with `--worktree`, every stop - a failed gate, an over budget readset, a failed plan check, steps 11, 12, 14, 18 - writes `{"block": "<reason>"}` to `.gcf-session/outcome.json` and ends the session
+22. with `--worktree`, every stop - a failed gate, an over budget readset, a failed plan check, a refused command, steps 11, 12, 14, 18 - writes `{"block": "<reason>"}` to `.gcf-session/outcome.json` and ends the session
 23. with `--worktree`, run no `ai-factory gcf block`, `submit` or `close`: the core refuses them on a `work/` branch, and the harness records the move on main
 24. with `--worktree`, step 17 is: commit everything but `gcf/.metrics`, then run `ai-factory gcf verify <id> --mark`; the harness merges the branch