gcf-aif-ext 0.28.0 → 0.29.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 +2 -2
- package/commands/gcf.js +35 -18
- package/extension.json +1 -1
- package/lib/board.js +6 -6
- package/lib/build-queue.js +8 -8
- package/lib/domain.js +15 -0
- package/lib/handoff.js +44 -19
- package/lib/play.js +640 -267
- package/lib/playtest-list.js +2 -2
- package/package.json +1 -1
- package/skills/gcf-chat/SKILL.md +4 -3
- package/templates/agents-block.md +4 -0
package/lib/playtest-list.js
CHANGED
|
@@ -4,7 +4,7 @@ import { readFile } from 'node:fs/promises';
|
|
|
4
4
|
import path from 'node:path';
|
|
5
5
|
import { gameMilestones } from './design-check.js';
|
|
6
6
|
import { listItems, readConfig, scalarOf, firstBullet } from './gcf-paths.js';
|
|
7
|
-
import {
|
|
7
|
+
import { itemBuilds, linksOf, playOf } from './play.js';
|
|
8
8
|
import { handoffOf } from './handoff.js';
|
|
9
9
|
import { recordsOf } from './verdict-fs.js';
|
|
10
10
|
|
|
@@ -81,7 +81,7 @@ export async function playtestList(root) {
|
|
|
81
81
|
system: c.data.system ?? [],
|
|
82
82
|
milestone: c.data.milestone ?? null,
|
|
83
83
|
play_on: c.data.play_on ?? builds ?? platforms,
|
|
84
|
-
|
|
84
|
+
builds: itemBuilds(path.dirname(root), String(c.data.id), c.data.status, links),
|
|
85
85
|
question: scalarOf(c.body, 'miss_criterion') || '(miss_criterion is empty)',
|
|
86
86
|
reach: recordsOf(c.body, 'behavior')
|
|
87
87
|
.map((r) => r.input)
|
package/package.json
CHANGED
package/skills/gcf-chat/SKILL.md
CHANGED
|
@@ -59,9 +59,10 @@ workflow:
|
|
|
59
59
|
14. then call `propose_play` with its `id`, a `target` and, for a target with devices, the `device` id: the human's click starts it and opens it, and the verdict stops it
|
|
60
60
|
15. the context file says no `play:` is set up and the project's `AGENTS.md` says how the game builds and starts: call `propose_play_setup` with those commands; say what is missing when it does not say
|
|
61
61
|
16. a Set up pass over a `play:` with no `plays_on`: propose `play.builds` with rows from the `platforms` of `gcf/game.md`, and targets with `build`, `for`, `devices` and `launches`
|
|
62
|
-
17.
|
|
63
|
-
18.
|
|
64
|
-
19.
|
|
62
|
+
17. one `propose_play_setup` per build, named in `of`; a release command goes with `profile: release`; `auto_build` names the build a run's card gets
|
|
63
|
+
18. in that pass, turn each line of platforms in a card's `play_on` and `played_on` into the name of its build
|
|
64
|
+
19. another move the human asks for: run its `ai-factory gcf` command; the human approves it on the card, or refuses it
|
|
65
|
+
20. say in one line what changed, or that nothing did
|
|
65
66
|
|
|
66
67
|
invocation:
|
|
67
68
|
- run at the start of a project chat thread the board opens, and when the user types `/gcf-chat`
|
|
@@ -50,6 +50,10 @@ gcf_work:
|
|
|
50
50
|
- Play main does the same for the checkout as it is, hand edits too; `ai-factory gcf playtest status` names the targets, the running player and the build queue
|
|
51
51
|
- `ai-factory gcf item show <id>` prints a waiting card's handoff: its outcome, its main question, Play by platform, what changed, what to try, what waits for the human
|
|
52
52
|
- `play.builds` names the builds of the project, each with its command, its output and the rows it `plays_on` (`device`, `os`, `os_min`, `model`, `input`)
|
|
53
|
+
- a build's command is one, or `build: { debug: <cmd>, release: <cmd> }`; `play.auto_build` is the build a run's card gets when its `play_on` names none
|
|
54
|
+
- `playtest build <id> --of <build> --profile release` builds one build in one profile; with neither, the card's build in debug; `playtest start --profile release` plays the target's build in release
|
|
55
|
+
- a card whose code has left the checkout builds in `.gcf-session/buildtree` at its own commit; its first build there is slow, the next ones reuse its caches
|
|
56
|
+
- `playtest setup --of <build> --build <cmd> [--profile release] --output <folder> --plays-on <row>` sets one build; `--auto-build <build>`, `--remove-build <build>`; a target's `--target-build <build>`
|
|
53
57
|
- a target names its `build`, the rows it serves (`for`), its `devices` script, and `launches: true` when it installs and ends
|
|
54
58
|
- `ai-factory gcf playtest devices <target>` lists the devices its script finds and why one does not fit; `playtest start <id> --target <t> --device <id>` plays on one
|
|
55
59
|
- a build while a run works in the checkout waits on a ticket: `playtest build <id> --wait` waits in its process, `--queue` prints `{ticket}` and ends; `ai-factory gcf playtest cancel <ticket>` takes it out or stops it
|