@robmclarty/volley 0.9.0 → 0.10.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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@robmclarty/volley",
3
- "version": "0.9.0",
3
+ "version": "0.10.0",
4
4
  "description": "A CLI harness that runs a builder/critic loop until a task passes both a deterministic check pipeline and a natural-language acceptance review.",
5
5
  "type": "module",
6
6
  "license": "Apache-2.0",
@@ -71,7 +71,7 @@
71
71
  "@mozilla/readability": "0.6.0",
72
72
  "ai": "7.0.140",
73
73
  "cac": "7.1.0",
74
- "fascicle": "0.16.3",
74
+ "fascicle": "0.17.1",
75
75
  "ipaddr.js": "2.5.0",
76
76
  "linkedom": "0.18.13",
77
77
  "picocolors": "1.1.1",
@@ -79,8 +79,9 @@ Work this way:
79
79
  4. If edit_file fails repeatedly on the same file, stop retrying variations
80
80
  of old_text — read the file once more and rewrite the whole file with
81
81
  write_file instead.
82
- 5. Verify before finishing: run the project's checks or tests with
83
- run_command, through the package manager its lockfile names, and fix
84
- what they report rather than calling the work done.
82
+ 5. Verify as you go: run the project's checks or tests with run_command,
83
+ through the package manager its lockfile names, after each batch of
84
+ edits and again before finishing, and fix what they report rather than
85
+ calling the work done.
85
86
  6. When the work is done and verified, call finish with a short summary of
86
87
  what you changed.
@@ -35,7 +35,8 @@ Work this way:
35
35
  4. If edit_file fails repeatedly on the same file, stop retrying variations
36
36
  of old_str — read the file once more and rewrite the whole file with
37
37
  write_file instead.
38
- 5. Verify before finishing: run the project's checks or tests with bash and
39
- fix what they report.
38
+ 5. Verify as you go: run the project's checks or tests with bash after
39
+ each batch of edits and again before finishing, and fix what they
40
+ report.
40
41
  6. When the work is done and verified, call finish with a short summary of
41
42
  what you changed.