create-cmp-cli 0.14.1 → 0.15.0

package/template/README.md

@@ -1,5 +1,6 @@
 # __APP_NAME__
 
+<!-- >>> cmp:feature harness -->
 <!-- cmp:generated evidence -->
 [![No evidence receipt](https://img.shields.io/badge/evidence-none_yet-9E9E9E)](https://github.com/kvdm-co-pilot/create-cmp) — no verify receipt yet. Run `node qa/verify.mjs`.
 <!-- /cmp:generated -->
@@ -9,6 +10,14 @@ A Kotlin / Compose Multiplatform app, generated by
 the architecture, testing conventions, and definition of done are enforced mechanically, not
 by convention. Start with [`docs/ARCHITECTURE.md`](./docs/ARCHITECTURE.md); AI collaborators
 follow the contract in [`CLAUDE.md`](./CLAUDE.md).
+<!-- <<< cmp:feature harness -->
+<!-- >>> cmp:feature !harness -->
+A Kotlin / Compose Multiplatform app, generated by
+[create-cmp](https://github.com/kvdm-co-pilot/create-cmp) as a **minimal scaffold**: the
+full app architecture with its tests, without the verification harness (one command adds
+it — see "Full mode" below). Start with [`docs/ARCHITECTURE.md`](./docs/ARCHITECTURE.md);
+AI collaborators follow the guide in [`CLAUDE.md`](./CLAUDE.md).
+<!-- <<< cmp:feature !harness -->
 
 ## Quick start
 
@@ -29,8 +38,10 @@ follow the contract in [`CLAUDE.md`](./CLAUDE.md).
 # Unit tests (fast inner loop)
 ./gradlew :composeApp:desktopTest
 
+<!-- >>> cmp:feature harness -->
 # The verify lane — build + tests + every shipped gate, with an evidence receipt
 node qa/verify.mjs
+<!-- <<< cmp:feature harness -->
 ```
 
 <!-- >>> cmp:feature inspector -->
@@ -55,7 +66,9 @@ before shipping — from Claude Code, the `cmp-firebase-connect` skill drives it
 ## Project structure
 
 ```
+<!-- >>> cmp:feature harness -->
 specs/                       behavior specifications — new behavior starts here
+<!-- <<< cmp:feature harness -->
 composeApp/src/commonMain/   shared UI + logic (presentation / domain / data / di)
 composeApp/src/commonTest/   unit tests — exemplar pattern in presentation/home
 composeApp/src/desktopTest/  conformance gates + Compose UI tests + golden trees (JVM tier)
@@ -66,8 +79,10 @@ composeApp/src/iosMain/      iOS actuals · iosApp/ is the Xcode shell
 <!-- >>> cmp:feature dev-client -->
 composeApp/src/desktopMain/  desktop dev-client (see docs/dev-client.md)
 <!-- <<< cmp:feature dev-client -->
+<!-- >>> cmp:feature harness -->
 qa/verify.mjs                the verify lane — this repo's definition of done
 qa/evidence/latest.json      the committed evidence receipt (see CONTRIBUTING.md)
+<!-- <<< cmp:feature harness -->
 <!-- >>> cmp:feature e2e -->
 qa/e2e/                      Maestro E2E flows (device smoke)
 <!-- <<< cmp:feature e2e -->
@@ -82,9 +97,26 @@ docs/                        architecture, testing, ADRs
 | [`docs/TESTING.md`](./docs/TESTING.md) | The test pyramid, conventions, how to run everything |
 | [`docs/adr/`](./docs/adr/) | Architecture decision records |
 | [`CONTRIBUTING.md`](./CONTRIBUTING.md) | Workflow, definition of done, commit style |
+<!-- >>> cmp:feature harness -->
 | [`CLAUDE.md`](./CLAUDE.md) | The AI delivery contract |
+<!-- <<< cmp:feature harness -->
+<!-- >>> cmp:feature !harness -->
+| [`CLAUDE.md`](./CLAUDE.md) | The AI working guide |
+<!-- <<< cmp:feature !harness -->
 | [`CHANGELOG.md`](./CHANGELOG.md) | Notable changes (Keep a Changelog) |
 
+<!-- >>> cmp:feature !harness -->
+## Full mode
+
+This scaffold is deliberately light: no verify lane, evidence receipts, behavior specs,
+approval gates, or generators. The full harness — a machine-checked definition of done,
+with an audit trail — installs in place, idempotently, with one command:
+
+```bash
+npx create-cmp-cli harden
+```
+<!-- <<< cmp:feature !harness -->
+<!-- >>> cmp:feature harness -->
 ## Verification
 
 Every change must pass the verify lane (`node qa/verify.mjs`) and commit its updated receipt
@@ -115,6 +147,7 @@ in [`.claude/settings.json`](./.claude/settings.json) — nothing else depends o
 CI independently enforces the same "receipt attests HEAD" check on every push
 (`.github/workflows/verify.yml`), so disabling the local hook only trades an immediate
 signal for a later one.
+<!-- <<< cmp:feature harness -->
 
 ---
 

package/template/docs/ARCHITECTURE.md

@@ -1,17 +1,29 @@
 # Architecture
 
+<!-- >>> cmp:feature harness -->
 > **Reading this document.** Every normative sentence below carries a tier tag.
 > `[enforced: CLAUSE-ID]`: a named gate in `node qa/verify.mjs` fails the lane on violation.
 > `[governed]`: the sentence lives inside a hash-bound human approval (`qa/approvals.json`);
 > changing it without re-approval fails the `approvals` gate. `[advisory]`: a documented
 > convention with no mechanical check yet. Every sentence is law, signed intent, or advice —
 > and says which.
+<!-- <<< cmp:feature harness -->
+<!-- >>> cmp:feature !harness -->
+> **Reading this document.** Every normative sentence below carries a tier tag.
+> `[enforced: CLAUSE-ID]`: a named source-scanning gate in the desktopTest conformance
+> suite fails the tests on violation. `[governed]` / `[advisory]`: conventions this
+> minimal scaffold checks by review, not by machine — the full harness
+> (`npx create-cmp-cli harden`) adds the mechanical gates.
+<!-- <<< cmp:feature !harness -->
 
 ## 1. Purpose & quality goals
 
+<!-- >>> cmp:feature harness -->
 This app's purpose, audience, and shape are recorded in [`specs/intent.md`](../specs/intent.md)
 — the root brief this document, the component registry, and the exemplar feature all trace
-back to. The table below is the default quality-goal set a fresh scaffold ships with. The
+back to.
+<!-- <<< cmp:feature harness -->
+The table below is the default quality-goal set a fresh scaffold ships with. The
 genesis walk's architecture conversation is where a human promotes, demotes, or replaces
 them for this app's actual priorities ("offline matters more than a11y for a field-work
 app").
@@ -423,6 +435,11 @@ demotes to a regular feature. To add a feature, mirror the exemplar exactly:
    empty/content split) (+ test using a fake from `testing/fakes/`).
 4. DI: register in `di/AppModule.kt`.
 5. Navigation: add the route in `presentation/navigation/`.
+<!-- >>> cmp:feature harness -->
 6. Run `node qa/verify.mjs` — done means PASS + committed receipt.
+<!-- <<< cmp:feature harness -->
+<!-- >>> cmp:feature !harness -->
+6. Run `./gradlew :composeApp:desktopTest` — green is the bar this scaffold can check.
+<!-- <<< cmp:feature !harness -->
 
 Significant decisions get an ADR in [`docs/adr/`](./adr/) — see the template there.

package/template/docs/TESTING.md

@@ -13,12 +13,20 @@ copy their shape.
 <!-- >>> cmp:feature e2e -->
 | E2E smoke (few) | `qa/e2e/*.yaml` (Maestro) | `maestro test qa/e2e/smoke.yaml` |
 <!-- <<< cmp:feature e2e -->
+<!-- >>> cmp:feature harness -->
 | The lane (all of it) | `qa/verify.mjs` | `node qa/verify.mjs` |
 
 Every durable test cites the spec clause it verifies (`// SPEC: HOME-02` — see
 [`specs/`](../specs/README.md)); **new behavior begins as a spec clause.** The lane's
 `specCoverage` step enforces this: it fails on orphan clauses (no citing test) and orphan tags
 (no matching clause, or one citing a withdrawn clause).
+<!-- <<< cmp:feature harness -->
+<!-- >>> cmp:feature !harness -->
+
+Durable tests may cite a spec clause id in a comment (`// SPEC: HOME-02`) — the shipped
+tests do. This minimal scaffold carries no `specs/` directory or coverage gate; both
+arrive with `npx create-cmp-cli harden`.
+<!-- <<< cmp:feature !harness -->
 
 ## Unit conventions
 
@@ -140,6 +148,7 @@ one: a search assert that passed standalone failed in-lane behind a 33s type gap
 asserts are for static post-navigation elements only.
 <!-- <<< cmp:feature e2e -->
 
+<!-- >>> cmp:feature harness -->
 ## The verify lane
 
 `node qa/verify.mjs` is the definition of done: spec coverage → build → unit tests →
@@ -235,3 +244,4 @@ rung is the coarse grade; the per-step list stays the fine print. A FAILed lane
 | **L1 desktop** | Full static + JVM evidence: build, unit tests, conformance, golden trees, a11y, release COMPILE, and the pure-Node gates. | That the app runs on a device at all — no APK was installed or driven; platform behavior (alarms, notifications) is invisible from this rung. |
 | **L2 device** | L1 plus executed on-device evidence: the debug APK installed and driven (`e2eSmoke`), instrumented platform assertions (`androidChecks`), and/or live token drift. | That the release variant behaves (R8 differs from debug — that is L3's job), nor that alarms/notifications actually land unless an instrumented behavior test asserts them. |
 | **L3 release** | L2 plus `releaseSmoke` PASSed: the signed release APK installed and driven on a device. | Real-backend behavior (the emulator/dev backend is a documented tier boundary — see the instrumented-tier section) and store-review compliance. |
+<!-- <<< cmp:feature harness -->

package/template/manifest.json

@@ -57,6 +57,18 @@
     "whenDisabled": "Remove the marker lines AND the body between them."
   },
   "features": {
+    "harness": {
+      "enabledByDefault": true,
+      "paths": [
+        "specs",
+        ".claude/skills",
+        ".githooks",
+        "qa/approvals.json",
+        "qa/comments.json",
+        "qa/evidence"
+      ],
+      "notes": "The verification harness — the mode split (`--minimal` disables it; `create-cmp harden` installs it back). Three mechanisms share the subtraction, each already owned by the engine: (1) the paths above delete the app-owned governance surfaces (specs/, approvals+comments ledgers, evidence, generator skills, the pre-push receipt hook); (2) `cmp:feature harness`/`!harness` marker blocks give CLAUDE.md, AGENTS.md, README.md, CONTRIBUTING.md, docs/TESTING.md and .github/workflows/verify.yml their two honest renderings from one file; (3) the machine-owned lane region is subtracted by the ENGINE (src/lib/minimal.mjs), which keeps qa/preview-gallery.mjs plus its transitive qa/lib imports — derived from import statements, never listed here, so it cannot rot. .claude/settings.json is rewritten to the advisory-only hook set via the src/lib/hooks.mjs classifier (Stop hook and qa/-referencing nudges are full-mode only). qa/golden/ stays in BOTH modes — the desktopTest golden-tree tests read it and minimal keeps the full JVM test tier. qa/e2e is its own feature and stays orthogonal (Maestro flows run standalone)."
+    },
     "ios": {
       "enabledByDefault": true,
       "paths": [
@@ -113,6 +125,7 @@
   },
   "verify": {
     "android": "node qa/verify.mjs --profile scaffold",
+    "androidMinimal": "./gradlew :composeApp:desktopTest :composeApp:assembleDebug",
     "androidBuildOnly": "./gradlew :composeApp:assembleDebug",
     "androidSmoke": "./gradlew :composeApp:installDebug && maestro test qa/e2e/smoke.yaml",
     "iosLink": "./gradlew :composeApp:linkDebugFrameworkIosSimulatorArm64",

package/template/qa/lib/harness-lock.mjs

@@ -8,7 +8,7 @@
 //              Answered LOCALLY, offline, on every lane run. Needs nothing
 //              but the tree and this file.
 //
-//   AUTHENTICITY  "is my lane the real published create-cmp-harness@X?"
+//   AUTHENTICITY  "is my lane the real published @create-cmp/harness@X?"
 //              Answered REMOTELY, on request, by comparing this file's
 //              `sha256` against the published version's — `create-cmp
 //              upgrade --harness` does it, and so can any third party
@@ -61,7 +61,7 @@ export function readHarnessLock(root) {
  * @param {{name?: string, version: string}} harness identity to record
  * @returns {{sha256: string, fileCount: number}}
  */
-export function writeHarnessLock(root, { name = "create-cmp-harness", version }) {
+export function writeHarnessLock(root, { name = "@create-cmp/harness", version }) {
   if (typeof version !== "string" || version.length === 0) {
     throw new Error("writeHarnessLock: a harness version is required");
   }

package/template/qa/lib/inputs-hash.mjs

@@ -5,7 +5,7 @@
 // there is exactly one definition of the surface and the algorithm.
 //
 // SINGLE SOURCE OF TRUTH: packages/receipts/src/inputs-hash.mjs in the
-// create-cmp repo (the `cmp-receipts` package). The copy in a generated
+// create-cmp repo (the `@create-cmp/receipts` package). The copy in a generated
 // project's qa/lib/ is vendored byte-identical at scaffold time and pinned by
 // test/receipts-parity.test.mjs — edit the package source, then run
 // `node scripts/sync-harness.mjs`.

package/template/qa/lib/receipt-validate.mjs

@@ -6,7 +6,7 @@
 // tarball rather than the working tree.
 //
 // SINGLE SOURCE OF TRUTH: packages/receipts/src/receipt-validate.mjs in the
-// create-cmp repo (the `cmp-receipts` package). The copy in a generated
+// create-cmp repo (the `@create-cmp/receipts` package). The copy in a generated
 // project's qa/lib/ is vendored byte-identical at scaffold time and pinned by
 // test/receipts-parity.test.mjs — edit the package source, then run
 // `node scripts/sync-harness.mjs`.

package/template/qa/receipt-check.mjs

@@ -39,7 +39,7 @@ function readStdinJson() {
 }
 
 // The predicate itself lives in qa/lib/receipt-validate.mjs (vendored from the
-// cmp-receipts package — one definition everywhere a receipt is judged); this
+// @create-cmp/receipts package — one definition everywhere a receipt is judged); this
 // CLI only reads the receipt and frames the exit codes.
 function evaluate() {
   const receipt = readReceipt(ROOT);