v1.19.0
harness-bootstrap
Added
- A bar for what earns a task, and a hook that holds it. Task creation was unbounded: nothing
said what earns a task, and executing one agreed piece of work could leave a board with a dozen
rows nobody approved..claude/rules/task-tracking.mdnow states it plainly - a task is work the
USER agreed to, tasks are few and large, executing a task never creates more, and no agent opens
one on its own, subagents included. The newguard-task-scopehook refuses to create a task file
whoserequested_by:is missing, is a bareuser, or is an agent name (an agent cannot approve
its own task), and one with fewer than two real acceptance criteria. Both hook flavours, six new
eval cases, and the eval is now 112/112 per flavour. /new-taskasks and waits. Unless your own message already asked for the task, the command
puts it to you withAskUserQuestionbefore writing anything - the same discipline
/harness-toggleuses for a protected control, where a confirmation counts only when you gave it
yourself. The hook records the claim; the asking is the gate.
Fixed
- The scanner a bootstrapped repo runs gained the per-folder
CLAUDE.mdsupport that shipped
in harness-view a version ago but never reached this scanner. A project withsrc/api/CLAUDE.md
now shows all its contracts in the graph, not just the root one. - The published "bytes the model must write" figure stopped tracking the size of rules this skill
SHIPS. It was estimated asmedian(shipped rule size) x 3, so improving a shipped rule inflated
the figure and dropped the reduction headline. It is now a declared per-rule size with the basis
stated, plus a measuredvars.json.
spec-builder
No functional change. The version moves with harness-bootstrap.
Tools
Downloadable builds for Windows, macOS and Linux are attached to this release.
harness-view
Added
assessreports a per-folder contract that governs a subtree and says almost nothing. A
nestedCLAUDE.mdapplies to every change under its directory, so an empty one is worse than
none: the folder reads as governed and whoever opens the file to learn how stops looking. Whether
the rules inside are right is not something a scanner can know, and it does not pretend to.
Install
unzip harness-bootstrap-v1.19.0.zip -d ~/.claude/skills/unzip spec-builder-v1.19.0.zip -d ~/.claude/skills/- Verify with
sha256sum -c SHA256SUMS