@andresmassello/uscha 1.56.1 → 1.60.1

package/README.md

@@ -40,8 +40,8 @@ Requires **Python 3.8+** on the machine (the engine is Python stdlib — no pip
 runtime dependencies). The npm package is a thin router; the canonical installer is
 `uscha-kit/install-uscha.py`.
 
-**Kit v1.56.1** <!-- uscha:version --> · [uscha.dev](https://uscha.dev) ·
-[changelog](https://github.com/andresmassello/uscha/blob/main/uscha-kit/CHANGELOG-1.56.1.md)
+**Kit v1.60.1** <!-- uscha:version --> · [uscha.dev](https://uscha.dev) ·
+[changelog](https://github.com/andresmassello/uscha/blob/main/uscha-kit/CHANGELOG.md)
 (the per-release changelogs live in the repo, not in the npm tarball)
 
 ---
@@ -76,7 +76,7 @@ and see which file, which test, and when.
 | `/uscha-mirador` | Bird's-eye HTML dashboard: readiness, trail, acceptance, loops |
 | `/uscha-status` | One-line progress readout, in chat |
 
-**A measurement engine** (`qa_ledger.py`, 29 subcommands, Python stdlib) that ingests
+**A measurement engine** (`qa_ledger.py`, 32 subcommands, Python stdlib) that ingests
 evidence from **11 language stacks** — maven, gradle, ant, python, node, go, rust, dotnet,
 cpp, swift, flutter — and computes a readiness score with hard caps and visible provenance.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@andresmassello/uscha",
-  "version": "1.56.1",
+  "version": "1.60.1",
   "description": "Spec-driven development for LLM coding agents: 9 skills + a stdlib evidence engine. Facts block, guesses advise; the human approves.",
   "author": {
     "name": "Andres Massello",
@@ -18,6 +18,7 @@
     "!uscha-kit/**/*.pyc",
     "!uscha-kit/**/*.pyo",
     "!uscha-kit/CHANGELOG-*.md",
+    "!uscha-kit/CHANGELOG.md",
     "README.md",
     "LICENSE"
   ],

package/uscha-kit/.claude/skills/uscha-characterize/SKILL.md

@@ -190,3 +190,21 @@ covered.
 
 Never overwrite an existing approved golden. If a `.received` already exists, regenerate it;
 if a `.approved` exists, it is the human's — leave it untouched and surface the diff.
+
+## Record the coverage map (ADR-006)
+
+After the `.received` is produced and while the harness is still the thing that just ran,
+record WHICH source files it exercised — the mapping that lets the fast-path veto a change
+touching code a golden froze:
+
+```bash
+python qa_ledger.py golden-coverage --harness <harness> --golden <the .approved sibling>
+```
+
+This is **derived measurement, not judgment**: the agent may write `golden.coverage.json`.
+INV-GOLDEN-01 governs the `.approved` bytes, which encode judgment, and nothing here changes
+that — the human still approves the golden itself.
+
+`coverage.py` is a capture-time dependency. Without it the command writes **nothing** and exits
+2: an empty map would read as "this golden covers nothing", which is exactly the lie that would
+let the veto pass. Skipping the map is honest; recording an empty one is not.

package/uscha-kit/.claude/skills/uscha-devloop/SKILL.md

@@ -169,6 +169,27 @@ install `hooks/block-approved-writes.py` as a `PreToolUse` hook in
 `settings.json`, and add `*.approved.* binary` to `.gitattributes` (ships in
 `templates/.gitattributes`) so line endings can't lie in the byte-compare.
 
+## Phase 0a — Fast-path check (ADR-003; run FIRST, before planning ceremony)
+
+If `defaults.fast_path` exists in config, run the measured classifier before demanding a
+full spec package:
+
+```bash
+python qa_ledger.py fastpath-eval --repo <name> --json          # dry-run first
+```
+
+- **ALLOW** and the operator wants the shortcut: re-run with
+  `--intent "<one sentence: what and why>"` to record it, then skip Phase 0's full-package
+  demand. The micro-contract replaces it: the recorded INTENT plus at least one new/modified
+  asserting test (readiness stays capped until that test shows up in measured evidence).
+- **DENY**: state WHICH measured signal denied it — echo the engine's breakdown verbatim.
+  The skill wires; it never computes and never argues with the verdict. Proceed with the
+  normal full path. The operator may always choose the full path over an ALLOW; nothing —
+  operator, agent or flag — can force ALLOW over a DENY (INV-RIGOR-02).
+- **Re-evaluate before the PR step** (same command, same intent): thresholds exceeded mid-run
+  flip the run to `ESCALATED` — the derived phase blocks pr-ready and readiness is capped.
+  Produce the ADR + ACCEPTANCE the change turned out to deserve, then `resolve-escalation`.
+
 ## Phase 0 — Plan (ADR-first)
 
 - **Read `CONSTITUTION.md` first (if present).** It lists the project invariants no SPEC