@haposoft/cafekit 0.16.7 → 0.18.1

package/src/claude/skills/test/references/execution-strategy.md

@@ -20,27 +20,20 @@ marker. Resolve all accepted paths inside the target feature directory.
   marker, malformed or duplicate task fields, symlink, directory, device, or
   other nonregular flat marker returns `BLOCKED`.
 
-### Legacy markers
+### Packets the runtime no longer reads
 
-- Legacy markers are `spec.json`, nested legacy tasks, or separate legacy
-  receipts. Detect them even when orphaned or broken.
-- Legacy is selected only when a regular schema-valid `spec.json` has one
-  consistent identity and registry resolving every contained nested task and
-  receipt, and no flat marker exists.
-- Orphan nested tasks/receipts, absent or schema-invalid root, conflicting
-  identities, symlinks, nonregular markers, or unresolved/out-of-root entries
-  return `BLOCKED`.
+- A packet directory with no `plan.md` that holds the old JSON planning state is not
+  read by CafeKit. Return `BLOCKED` and name it; never migrate it while testing.
+- Other files beside a valid `plan.md` do not change its classification.
 
 ### Precedence truth table
 
-| Flat state | Legacy state | Result |
+| Flat state | Old planning state without `plan.md` | Result |
 |---|---|---|
-| valid | absent | process-first |
-| absent | valid | legacy adapter |
+| valid | any | process-first |
+| invalid | any | `BLOCKED` |
+| absent | present | `BLOCKED`: unsupported, move the work to a `plan.md` packet |
 | absent | absent | ordinary non-Spec scope |
-| any marker | any marker | `BLOCKED` mixed state |
-| invalid | absent | `BLOCKED` |
-| absent | invalid | `BLOCKED` |
 
 Do not infer that an invalid marker is absent. Testing never repairs, migrates,
 renames, deletes, or chooses between conflicting packet identities.
@@ -59,6 +52,13 @@ and runtime surfaces. Escalate to a wider suite when configuration or shared
 infrastructure changes, mapped scope exceeds roughly 60 percent, or a required
 surface cannot be isolated. `--full` widens selection; it does not loosen proof.
 
+Before an Ordinary non-Spec `PASS` or `PASS_WITH_WARNINGS`, read the tests that
+cover the target or changed code (every test file when the suite is small). A
+nondeterministic source in an assertion or its pass condition is `FAIL`, naming
+the source, even when every run passes. A source only in setup means rerunning
+just the suspect tests at least twice more; any differing outcome is `FAIL` as
+flaky (`failure-triage.md`). A process-first Named probe still runs exactly once.
+
 Run cheap project-provided prechecks before expensive tests. Do not auto-install
 missing runners, packages, browsers, or linters. A missing prerequisite is
 `BLOCKED`; a precheck that actually runs and fails is `FAIL`.
@@ -149,6 +149,79 @@ and `skipped` each equal the element-wise sum of that field across every branch;
 any unattributed, multiply attributed, or unequal count is contradictory and
 returns `BLOCKED`.
 
+A pre-execution `BLOCKED` payload for a task with two Named probes, when the
+packet failed classification after the repository had a commit:
+
+```json
+{
+  "schema_version": "test-proof-v1",
+  "target": {
+    "feature": "user-auth",
+    "task_path": "specs/user-auth/task-01-login.md"
+  },
+  "verdict": "BLOCKED",
+  "command": null,
+  "exit": null,
+  "counts": {
+    "executed": 0,
+    "passed": 0,
+    "failed": 0,
+    "skipped": 0
+  },
+  "provenance": {
+    "base": "4f2a9c0e7b1d3a5f6e8c9b0a1d2e3f4a5b6c7d8e",
+    "head": "9e8d7c6b5a4f3e2d1c0b9a8f7e6d5c4b3a2f1e0d"
+  },
+  "proof_level": "source",
+  "expected": "both Named probes pass under `node --test test/login.test.js`",
+  "observed": "BLOCKED before execution: specs/user-auth/task-01-login.md is a symlink",
+  "reachability": {
+    "status": "BLOCKED",
+    "evidence": [
+      "not executed: the packet failed classification"
+    ]
+  },
+  "artifacts": [],
+  "branches": [
+    {
+      "id": "login accepts a valid password",
+      "required": true,
+      "verdict": "BLOCKED",
+      "command": null,
+      "exit": null,
+      "counts": {
+        "executed": 0,
+        "passed": 0,
+        "failed": 0,
+        "skipped": 0
+      },
+      "proof_level": "source"
+    },
+    {
+      "id": "login rejects a wrong password",
+      "required": true,
+      "verdict": "BLOCKED",
+      "command": null,
+      "exit": null,
+      "counts": {
+        "executed": 0,
+        "passed": 0,
+        "failed": 0,
+        "skipped": 0
+      },
+      "proof_level": "source"
+    }
+  ],
+  "raw_output": "not executed: the packet failed classification",
+  "redactions": [],
+  "payload_sha256": "b62c65f70d9cba41c4ab92c7dfb5a7db371aff609095525cc10a8adf147631f7"
+}
+```
+
+`FAIL` variants: a branch with a nonzero exit or a failed count is `FAIL` and
+makes the payload `FAIL`; a reachability `FAIL` with every branch passing keeps
+the branches `PASS` and makes the payload `FAIL`.
+
 ## 5. Aggregation and integrity
 
 Aggregate required branches in strict order:
@@ -199,14 +272,13 @@ must not write project state.
 Return the validated `test-proof-v1` handoff to the controller and a separate
 concise report containing only verdict, scope, exact redacted command, exit,
 counts, reachability, proof level, project-command drift, and next action.
+Place the handoff as `SKILL.md` "Verdict and report" says: after the concise
+report, under `### Machine handoff (test-proof-v1)`, one fenced `json` block
+that follows the report and is not part of it.
 
 Do not paste verbose raw output, full JSON, credentials, PII, or screenshots into
 the report. Do not write a report file during proof. Process-first Status and
 inline `## Receipt` remain controller-only.
 
-## Legacy workflow compatibility
-
-After a valid legacy route, preserve its v2.1 task/receipt adapter and existing
-proof rules. Separate legacy receipts remain legacy-only. Never search for or
-create a separate receipt for a process-first task, and never copy a legacy
-receipt into a flat task.
+Proof for a process-first task lives only in its inline `## Receipt`; never
+search for or create a receipt file beside it.

package/src/claude/skills/test/references/failure-triage.md

@@ -10,7 +10,7 @@ implementation owner. Testing never edits implementation or tests.
 | Compilation or packaging | command, exit, relevant file/line | `FAIL` |
 | Logic/contract | named probe, expected, observed | `FAIL` |
 | Environment/prerequisite | missing tool, service, variable, permission | `BLOCKED` before execution; otherwise `FAIL` after an attempted command |
-| Flaky/nondeterministic | repeated current runs with differing outcomes | `FAIL` |
+| Flaky/nondeterministic | repeated current runs with differing outcomes, or an assertion or pass condition that depends on a nondeterministic source | `FAIL` |
 | Coverage/reachability gap | exact uncovered branch or unreachable surface | `FAIL`, or `PASS_WITH_WARNINGS` only when explicitly non-required |
 | UI console/network/flow | URL path, safe status, redacted error | `FAIL` when required |
 | Accessibility/visual/performance/SEO | metric or element plus declared threshold | requirement decides `FAIL` or `PASS_WITH_WARNINGS` |

package/src/claude/skills/ui-ux/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Tuấn Trần
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.