@descent-vtt/spec-harness 0.10.0 → 0.11.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.
Files changed (29) hide show
  1. package/.claude-plugin/marketplace.json +1 -1
  2. package/.claude-plugin/plugin.json +1 -1
  3. package/CHANGELOG.md +90 -0
  4. package/README.md +8 -3
  5. package/bin/spec-harness.js +9 -0
  6. package/dist/branch.js +2 -0
  7. package/dist/branch.js.map +1 -1
  8. package/dist/briefs.js +2 -0
  9. package/dist/briefs.js.map +1 -1
  10. package/dist/cli.d.ts +15 -3
  11. package/dist/cli.js +33 -7
  12. package/dist/cli.js.map +1 -1
  13. package/dist/commands.js +6 -2
  14. package/dist/commands.js.map +1 -1
  15. package/dist/config.js +2 -0
  16. package/dist/config.js.map +1 -1
  17. package/dist/git.d.ts +8 -6
  18. package/dist/git.js +11 -6
  19. package/dist/git.js.map +1 -1
  20. package/dist/probe.d.ts +59 -1
  21. package/dist/probe.js +88 -1
  22. package/dist/probe.js.map +1 -1
  23. package/dist/reader.js +4 -0
  24. package/dist/reader.js.map +1 -1
  25. package/dist/sandbox.d.ts +25 -1
  26. package/dist/sandbox.js +134 -29
  27. package/dist/sandbox.js.map +1 -1
  28. package/package.json +3 -3
  29. package/skills/draft-brief/SKILL.md +10 -2
package/skills/draft-brief/SKILL.md CHANGED
@@ -61,7 +61,14 @@ For a `defect` brief, write a probe: a test that fails now, for the reason
61
61
  the brief states, declared in the brief as a `probe` block (with the test in
62
62
  a `probe-file` block if it is new). Give it a `signature` - text the failure
63
63
  must contain - or a JUnit `test` name, so a compile error is never taken for
64
- the defect. Then:
64
+ the defect.
65
+
66
+ The probe runs in a fresh worktree, where nothing is installed until its
67
+ `setup` line installs it, as `setup: npm ci` does. Make `run` one of the
68
+ project's own scripts, such as `npm test -- <file>`, and never `npx` with a
69
+ tool's name alone: where the tool is not installed, npm would fetch whatever
70
+ the registry has under that name, so `probe` has it stop there and the probe
71
+ is `invalid`. Never add `--yes` to get past that. Then:
65
72
 
66
73
  ```bash
67
74
  npx --no-install @descent-vtt/spec-harness probe <id> --at base
@@ -69,7 +76,8 @@ npx --no-install @descent-vtt/spec-harness probe <id> --at base
69
76
 
70
77
  `measured` means the defect is real; paste the evidence table into the
71
78
  brief. `vacuous` means it is not there: say so to the person and stop.
72
- `invalid` or `flaky` means the probe proves nothing yet: fix the probe.
79
+ `invalid` or `flaky` means the probe proves nothing yet: read the end of its
80
+ command's output, printed after the table, and fix the probe.
73
81
 
74
82
  ## 4. Check, then hand over
75
83