@andresmassello/uscha 2.5.0 → 2.6.0

package/uscha-kit/templates/CONSTITUTION.md

@@ -199,6 +199,20 @@ enforcing the record is the engine's job. It is never resolved by "working aroun
   convergence blocked, and `phase --require pr-ready` refuses naming the missing check. A CI
   system this engine does not read is reported `unknown`, never green and never red. Release,
   reset and the RUNBOOK are part of done, not of the last week.
+- The **QA-tool readiness** invariant is measured by `qa_ledger.py qa-tools-check --repo R` (ADR-051):
+  every tool in the effective `qa_tools_order` is resolved to a SOURCE — a project skill, a global
+  skill (under any agent skills root the installer knows), an installed+enabled plugin, a harness
+  built-in (`code-review`, assumed and reported honestly as *not measured*), a tool the human
+  declared in `defaults.qa_tools_external` (per key: the LIVE project config wins over the
+  ledger's frozen copy when it declares the key, and falls back to it when it omits it), or
+  **MISSING**. A MISSING tool is a **BLOCKER** persisted as
+  `gate:qa-tools` — readiness cap ≤ 65, convergence blocked, and `phase --require pr-ready`
+  refuses naming the tool — under **every** profile: "a declared QA tool is not installed" is a
+  fact, not an opinion, so there is no profile knob. `qa-tools` is a FACT kind written only by
+  `qa-tools-check`: there is no `log-gate --kind qa-tools` door, because the engine measures this
+  fact itself and a typed pass would be a narrated one. With no `qa_tools_order` declared there
+  is nothing to resolve: UNMEASURED, never a pass. A loop can no longer converge trusting a QA
+  tool that never ran.
 - The **Golden (INV-GOLDEN-01)** invariant is measured by `qa_ledger.py golden-diff`: any `.received`
   that does not match its `.approved` (or is unapproved) = **DIVERGE**, cutting the chain before judgment-day.
   The agent does not touch `.approved` (ideally a `PreToolUse` hook makes it impossible).

package/uscha-kit/uscha.config.json

@@ -1,6 +1,6 @@
 {
   "_comment": "COMPREHENSIVE REFERENCE, not a project config. Every knob the engine and the skills understand, at the kit's own value, so a human can read what can be declared. `uscha init` does NOT copy this file: it GENERATES a minimal project config, because a copied default is an explicit declaration and an explicit declaration outranks the preset named by defaults.risk_profile (ADR-001, as amended). Copy a block from here into your project only when you mean to override the engine default or the preset. NOTE: no version string may be written into this comment -- the release script requires exactly one occurrence of the version in this file (I3), and a second one refuses the next release.",
-  "version": "2.5.0",
+  "version": "2.6.0",
   "project": null,
   "defaults": {
     "coverage_threshold": 60,
@@ -16,6 +16,7 @@
       "judgment-day",
       "improve"
     ],
+    "qa_tools_external": [],
     "test_command_maven": "mvn -q -DskipITs=false test",
     "test_command_flutter": "flutter test --coverage",
     "test_command_python": "pytest --cov --cov-report=xml:reports/coverage.xml --junitxml=reports/junit.xml",