create-githolon 0.108.6 → 0.110.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-githolon",
-  "version": "0.108.6",
+  "version": "0.110.0",
   "type": "module",
   "description": "Scaffold a Nomos domain package: the starter domain + compile config + live e2e. `npm create githolon my-app`.",
   "license": "SEE LICENSE IN LICENSE.md",

package/template/CLAUDE.md

@@ -18,14 +18,16 @@ Model the business language. Do not recreate Nomos as application infrastructure
 npm run compile
 npm run proof
 # After the first deployed model, prove the candidate over copied real custody too:
-npx githolon proof --upgrade
+npx githolon test
 ```
 
 `compile` is the evolution gate. `proof` exercises the emitted candidate in the real local kernel, including
 cold custody restore. `proof --upgrade` resolves the workspace already bound in `nomos.project.ts`, copies
-its custody into a disposable local kernel, replays the candidate over the exact history, promotes it only
-in that copy, and cold-opens the result. If history changes meaning, it stops for an explicit
-`--acceptance-reason`; never invent one. Never make deployment the first place a candidate law is executed.
+its custody into a disposable local kernel, verifies the existing chain under its recorded eras, derives
+the candidate's current-frontier transition, promotes it only in that copy, and cold-opens the result.
+Stable-id retirements, retypes, or rebinds stop for an explicit `--acceptance-reason`; never invent one.
+Whole-history simulation is an explicitly requested counterfactual and is never an adoption gate. Never
+make deployment the first place a candidate law is executed.
 
 If either command exposes framework implementation machinery, treat that as a Nomos defect rather than
 teaching the application to handle it.

package/template/README.md

@@ -87,13 +87,14 @@ updated identity file beside the domain source, run `proof`, and deploy only tho
 Before upgrading an existing application, run the history-shaped proof as well:
 
 ```bash
-npx githolon proof --upgrade
+npx githolon test
 ```
 
 It uses the workspace binding in `nomos.project.ts` (or accepts a workspace/local-ledger argument), copies
-that custody into the local kernel, exercises the candidate against its exact history, promotes only in the
-copy, and proves a cold restart. The source is never modified. If the candidate deliberately changes an old
-business outcome, the command names the differences and requires an accountable `--acceptance-reason`.
+that custody into the local kernel, verifies the chain under its recorded eras, derives the candidate's
+current-frontier transition, promotes only in the copy, and proves a cold restart. The source is never
+modified. Stable-id retirements, retypes, or rebinds require an accountable `--acceptance-reason`.
+Whole-history simulation is available only as an explicit counterfactual and never gates adoption.
 
 Useful files:
 
@@ -102,7 +103,7 @@ Useful files:
 - [`nomos.project.ts`](nomos.project.ts): typed business-law authoring input; it emits the readable USDA law closure and its `.law.usdz` package;
 - [`nomos.application.ts`](nomos.application.ts): application-composition authoring input; only the emitted `.application.usda` travels;
 - `build/application/__APP_DART_NAME___application/`: the sole Flutter application dependency;
-- `build/__APP_NAME__.proof.mts`: the generated local proof.
+- `build/__APP_NAME__.reception.mjs`: the application's TypeScript Reception (drive it from vitest with `@githolon/testing`).
 
 If application code needs to understand workspaces, event sourcing, JWTs, signatures, retries, topology,
 serialization, or merge algorithms, a framework concern has leaked out of Nomos.

package/template/package.json

@@ -6,7 +6,6 @@
   "description": "A Nomos business application: public intents over private atomic consequences.",
   "scripts": {
     "compile": "githolon compile ./nomos.project.ts && githolon compile ./nomos.application.ts",
-    "proof": "githolon proof",
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {

package/template/tsconfig.json

@@ -11,8 +11,7 @@
   },
   "include": [
     "domains/**/*.ts",
-    "build/*.client.d.mts",
-    "build/*.proof.mts",
+    "build/*.reception.d.mts",
     "test/**/*.mts"
   ]
 }