joycraft 1.2.1 → 1.2.2

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 CHANGED
@@ -23,9 +23,10 @@ Install Joycraft in this project.
23
23
  docs, interview me about what the repo cannot tell you, then show me the
24
24
  AGENTS.md and CLAUDE.md changes on a page before you write them. If the project
25
25
  is new or empty, ask me what I want to build.
26
- 4. Run `node .joycraft/runtime/review-tools.mjs plan --root .`. Tell me which tools
27
- you need to check your own work, which ones I have, and which ones are missing.
28
- Ask me before you install anything.
26
+ 4. Show me the review loop that setup found: for each package, the tool that
27
+ checks it and what that tool can show. If setup did not do this, run
28
+ `node .joycraft/runtime/review-tools.mjs plan --root .`. Ask me before you
29
+ install anything.
29
30
  Do not commit, publish, or ask me for API keys.
30
31
  ```
31
32
 
@@ -47,8 +48,8 @@ bigger than one quick change:
47
48
  3. **The agent builds each spec with tests.**
48
49
  4. **A second agent checks each spec.** It did not write the code. It reads the spec,
49
50
  runs the checks, and says PASS or FAIL. Only a PASS completes the spec. For a
50
- screen or page, it looks at the real result in a browser or simulator, if you
51
- installed those tools in step 4 of the install.
51
+ screen or page, it looks at the real result with the package's review tool
52
+ (see [The review loop](#the-review-loop)).
52
53
  5. **The agent wraps up.** It records what it learned for the next session.
53
54
 
54
55
  You do not need to call the Joycraft skills by name. Describe the work and the agent
@@ -163,6 +164,35 @@ If your docs are step-by-step procedures, the agent can offer
163
164
  [Doc Detective](https://docs.doc-detective.com) to run them as tests. It is opt-in:
164
165
  the agent says what it does not cover and installs nothing without your yes.
165
166
 
167
+ ## The review loop
168
+
169
+ The reviewing agent needs a tool that shows the real result: a browser for a web
170
+ app, a simulator for a mobile app, an HTTP check for an API. Joycraft decides what
171
+ counts as evidence; your project keeps its own tools.
172
+
173
+ - **Setup finds your tools.** For each package it looks for the tool you already
174
+ use (Playwright, Cypress, WebdriverIO, Maestro, Newman, an e2e script, a CI job
175
+ and others) and records one row per package in AGENTS.md, with what that tool can
176
+ show. Tools that belong to this machine, such as your agent's built-in browser, go
177
+ to `.joycraft/local/`. Packages that are not declared workspaces are found too, or
178
+ name them with `--packages`.
179
+ - **A gap gets one recommendation.** If a package has no tool, the agent recommends
180
+ one with its trade-offs and offers to look at others. It installs only on your yes,
181
+ and never with `sudo`, a licence or a sign-in. A project with no app records that
182
+ once and is not asked again.
183
+ - **Limits you agreed to are not failures.** A claim the recorded tool cannot show,
184
+ or a package you skipped, is reported as a limit. `UNVERIFIED` means a check that
185
+ should have run and did not.
186
+ - **Skipping review for one feature.** Say "skip review" in the feature interview.
187
+ The feature's `waiver.json` records your words, and no reviewer runs for it. A
188
+ waiver never hides a FAIL, and a new install keeps every check on.
189
+ - **A broken tool holds one spec.** If the browser or server breaks, the agent
190
+ tries one repair (restart, free the port, relaunch). Then it holds that spec as
191
+ `UNVERIFIED`, tells you, and keeps the rest of the queue going.
192
+
193
+ After an update, the agent checks the review loop again and asks only about what
194
+ changed.
195
+
166
196
  ## Answering questions: the decision page
167
197
 
168
198
  When the agent needs you to choose between options, it asks in your question
@@ -215,7 +245,9 @@ day. The check sends no project data. If there is a new version, the agent tells
215
245
  whether it is a patch, a minor release or a migration, lists each release since
216
246
  yours, and asks: update now, not now, or turn off. Automatic updates apply only
217
247
  patches. On a yes, it does the update
218
- for you, checks the result, and tells you what is different. A new major version is
248
+ for you, checks the result, and tells you what is different. After a minor release
249
+ it names what you can now do, and asks how you want questions if you have not said
250
+ yet. A new major version is
219
251
  always your choice.
220
252
 
221
253
  This is an instruction the agent follows, so it can forget. To check yourself, ask:
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "schemaVersion": 1,
3
- "releaseVersion": "1.2.1",
3
+ "releaseVersion": "1.2.2",
4
4
  "manifestSchemas": [
5
5
  1
6
6
  ],
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "joycraft",
3
- "version": "1.2.1",
3
+ "version": "1.2.2",
4
4
  "description": "Install and update Joycraft, a skill bundle and runtime for agent-led software work, in any project",
5
5
  "type": "module",
6
6
  "bin": {
@@ -13,8 +13,8 @@
13
13
  "payload"
14
14
  ],
15
15
  "joycraft": {
16
- "release": "1.2.1",
17
- "summary": "Joycraft asks questions your way: one at a time or as a page, in chat or on the decision page, set at setup and changeable per feature; each question gives context, options with an example and a trade-off, and a recommendation.",
16
+ "release": "1.2.2",
17
+ "summary": "The README describes the 1.2 review loop, the install prompt shows what setup found, and an update names what is new and offers the question style.",
18
18
  "autoSafeEligible": false
19
19
  },
20
20
  "scripts": {
@@ -28,7 +28,12 @@ Use the version from `latest`:
28
28
  migration plan and stops: show the plan and follow its steps with the user. Never
29
29
  apply a migration without the user's yes.
30
30
  3. Run `npx joycraft@<latest> doctor .`.
31
- 4. Tell the user in plain words what is different now.
31
+ 4. Tell the user in plain words what is different now. For a `minor` or
32
+ `migration`, name what the user can now do or say, one line per release since
33
+ the old version, from the release summaries the check listed (and the
34
+ changelog, when you can read it). When
35
+ `node .joycraft/runtime/artifacts/cli.mjs questions` prints `unset: true`,
36
+ ask for the question style now, as [setup](setup.md) step 2 says.
32
37
  5. Run the review-loop plan
33
38
  ([review loop tools](setup.md#review-loop-tools)). When it prints
34
39
  `Review loop unchanged.`, say nothing about it. When it reports a newly
package/payload/PIN CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "schemaVersion": 1,
3
3
  "source": "joycraft-prototype",
4
- "tag": "field-16",
5
- "commit": "91bd7db1f2ac5ddaa587f81bf3c5db636d60e584",
4
+ "tag": "field-17",
5
+ "commit": "0e88e6da3adc605a306db1ec058a4690b2eb5cb2",
6
6
  "files": {
7
7
  ".agents/skills/joycraft-cleanup/SKILL.md": "99ce785e551be33412ac7a99ce44585a9b2be4440617caac273680383b4f7057",
8
8
  ".agents/skills/joycraft-context/SKILL.md": "e2f85baa47058fd61811fdb60d0cb41fb3f505f3957812d929db95bb99124f1b",
@@ -36,7 +36,7 @@
36
36
  ".joycraft/references/retro.md": "f359eae19747777fb4687c1bc7eb280f0319ae629ee62913346e60fc56551562",
37
37
  ".joycraft/references/setup.md": "a9bd9072adc9f021b46287ff0422281ddb2285ac34738b6e29ad11cc60e8a6e5",
38
38
  ".joycraft/references/testing.md": "ddbc0e69212f4bf29f32f65e139c016b12eb40c29f621a99510129bedf292950",
39
- ".joycraft/references/update.md": "b6ca2f6f4073ed9a566ae467cbe4c60bf79baead845cc45138eec4c4ae28891e",
39
+ ".joycraft/references/update.md": "36af36ab3d47b5ea46a8f71090333771e5e1deaa6ca19739a75c9fd4aea14eba",
40
40
  ".joycraft/references/workflow.md": "5b330debc6759b8f7975b159632f51074802067291fe4f4bebfb344f5b60cc52",
41
41
  ".joycraft/references/worktrees.md": "fb18af0cd76d4e3c5d5b892a7ae10946f21f189e642243235c188b571635f735",
42
42
  ".joycraft/runtime/archive.mjs": "82b4d9567942a4abd21594ea299c4d323a8306ec7545cb0030431c87bd37f8b2",