@brainervirus/workit-cursor 2.5.0 → 2.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brainervirus/workit-cursor",
-  "version": "2.5.0",
+  "version": "2.7.0",
   "private": false,
   "description": "Workit Cursor plugin — shared MCP transport, native hooks, and fourteen method skills",
   "keywords": [
@@ -44,8 +44,8 @@
     "build": "bun scripts/build.ts"
   },
   "dependencies": {
-    "@brainervirus/workit-core": "^2.5.0",
-    "@brainervirus/workit-mcp": "^2.5.0"
+    "@brainervirus/workit-core": "^2.7.0",
+    "@brainervirus/workit-mcp": "^2.7.0"
   },
   "engines": {
     "node": ">=24"

package/skills/workit-behavioral-tdd/SKILL.md

@@ -16,12 +16,16 @@ Use this method when assessment selects the `testing` dimension.
 2. State one behavior and its observable result. Choose the narrowest stable
    boundary a caller or user depends on; avoid private helpers and incidental
    representations.
-3. Write one vertical RED slice that fails for the missing behavior, run it, and
-   preserve the actual failure as evidence. Implement the smallest change, then
-   run the same slice GREEN and record its result. Close enforces the order: a
-   testing requirement with GREEN but no preceding RED evidence stays unsatisfied.
-4. Add only another slice for a distinct behavior or risk. Reconcile stale
-   evidence if the candidate changes.
+3. Write one vertical RED slice that fails for the missing behavior and run it
+   through the CLI so the failure is observed: `workit check test` (the repo's
+   configured `test` check; `npx -y @brainervirus/workit-cli check test` when
+   `workit` is not on PATH). Implement the smallest change, then run the same
+   check GREEN. Close accepts only a fresh passing run of the configured check
+   that `workit check` observed; a recorded "tests pass" is a note, and an
+   ad-hoc `workit check -- <cmd>` never satisfies the gate. If no `test` check
+   is configured or detected, add `workit.checks.json` (committed) with it.
+4. Add only another slice for a distinct behavior or risk. Any edit makes the
+   observed check stale: re-run `workit check test` before closing.
 
 ## Reject noisy tests
 
@@ -36,8 +40,10 @@ Use this method when assessment selects the `testing` dimension.
   type-only or CSS-class coupling. If the test still passes when every
   imported function returns undefined, rewrite the assertion or delete it.
 
-Use shared `evidence` operations for RED/GREEN results. Do not add a second
-lifecycle, approval chain, or test workflow outside the current task state.
+Run RED/GREEN through `workit check`, which records the observed result on the
+current task; shared `evidence` operations are for notes and non-test evidence.
+Do not add a second lifecycle, approval chain, or test workflow outside the
+current task state.
 
 ## Common mistakes
 
@@ -45,4 +51,4 @@ lifecycle, approval chain, or test workflow outside the current task state.
 | --- | --- |
 | "The pin changed, so assert the new string" | Exercise the affected consumer behavior. |
 | "The code is obvious" | A small vertical slice still proves the contract. |
-| Keeping a passing test after the boundary moved | Mark it stale and retest the current candidate. |
+| Keeping a passing test after the boundary moved | Re-run `workit check test` on the current tree. |

package/skills/workit-debug/SKILL.md

@@ -19,7 +19,8 @@ established root cause.
    inferences, and unknowns with references; trace the failing value and all
    relevant callers before editing.
 3. State the root-cause hypothesis and the smallest in-scope fix. Write a focused
-   regression at the boundary when practical, then run RED and GREEN checks.
+   regression at the boundary when practical, then run RED and GREEN through
+   `workit check <name>` so the results are observed, not reported.
 4. Acquire writer authority through `writer` before mutation. Reconcile the
    candidate, evidence, and findings after the change; investigate sibling paths
    and stale conclusions rather than assuming the first patch worked.