feat: add canonical Registry Type Script

Author: a19q3

AGENTS.md

@@ -88,8 +88,8 @@ require extra tooling.
 
 | Mode | What it does |
 | --- | --- |
-| `dev` | Explicit workspace-package formatting and checks for the compiler, Fiber adapter, CKB adapter, WASM crate, CKB SDK builder example, `cellscript-tools`, and the independent Registry verifier crate; native source-policy enforcement; strict backend audit (quick); syntax combo audit (quick); parity-gated skill-pack freshness; `git diff --check`. Run before committing. |
-| `ci` | `dev` coverage plus tests and clippy for every workspace package, `cellscript-tools`, and the Registry verifier; Registry API tests plus Node API/verifier bundles; full package contents check, website build check (requires `npm`), shell syntax and native source-policy checks, parity-gated skill-pack freshness, and trailing-whitespace check. Run before claiming merge-readiness. |
+| `dev` | Explicit workspace-package formatting and checks for the compiler, Fiber adapter, CKB adapter, WASM crate, CKB SDK builder example, `cellscript-tools`, and the independent Registry verifier crate; reproducible Registry Type Script build and CKB-VM tests; native source-policy enforcement; strict backend audit (quick); syntax combo audit (quick); parity-gated skill-pack freshness; `git diff --check`. Run before committing. |
+| `ci` | `dev` coverage plus tests and clippy for every workspace package, `cellscript-tools`, the Registry verifier, and the Registry Type Script; Registry API tests plus Node API/verifier bundles; full package contents check, website build check (requires `npm`), shell syntax and native source-policy checks, parity-gated skill-pack freshness, and trailing-whitespace check. Run before claiming merge-readiness. |
 | `backend` | For IR / codegen / assembler / ABI / ELF / RISC-V changes: explicit workspace-package format checking, `cargo check --locked -p cellscript --all-targets`, `cargo test --locked -p cellscript`, `cargo clippy ... -D warnings`, strict backend audit (full, which itself fires the CKB stateful-scenarios harness via `cellscript_ckb_stateful_scenarios.sh`), `git diff --check`. |
 | `release` / `release-quick` | Everything `ci` does plus release-auxiliary checks (CKB acceptance, NovaSeal pinning, NovaSeal Rust tooling for RISC-V, fresh WASM + VS Code packaging, CKB tx measure tool, etc.) and the CKB acceptance harness (`scripts/ckb_cellscript_acceptance.sh`). These modes need the pinned sibling CKB checkout from `scripts/ckb_acceptance_pin.json`, the NovaSeal submodule, a sibling `ckb-sdk-rust` checkout at tag `v5.1.0`, Docker for the canonical Linux/amd64 WASM build, and `riscv64imac-unknown-none-elf` for NovaSeal verifier builds. Do not run them casually. |
 
@@ -121,7 +121,7 @@ The root `Cargo.toml` declares a virtual workspace with these members:
 - `examples/ckb-sdk-builder`
 
 Excluded from the workspace (still buildable through their own manifests):
-`services/registry-verifier`,
+`contracts/registry-type-script`, `services/registry-verifier`,
 `proposals/novaseal/v0-mvp-skeleton/{harness,verifier}` and
 `proposals/novaseal/agreement-profile-v0/harness/ckb_vm`. `tools/ckb-tx-measure`
 defines its own `[workspace]` (no parent) because it pulls `ckb-jsonrpc-types`

CODING_STYLE.md

@@ -28,6 +28,28 @@ project contract.
   short reason; crate-wide or module-wide clippy allowances are only for
   documented legacy or transition boundaries.
 
+## On-Chain Registry Script Rules
+
+`contracts/registry-type-script` is an independent `no_std` CKB Script crate.
+Its release binary is part of the Registry trust boundary, not a host utility.
+
+- Build only with the pinned repository toolchain and
+  `build_reproducible_release.sh`; the script path-remaps sources, strips the
+  RISC-V ELF, and verifies both SHA-256 and CKB data hash against the tracked
+  release manifest.
+- Keep Script args equal to the 32-byte custody Lock Script hash and the
+  accepted Cell data exactly `CSREGv1 || 32-byte commitment hash`. Every group
+  Cell must use that Lock and every transition must consume a Cell using it;
+  otherwise an unauthorised creator could impersonate an official commitment.
+  Format changes require a new protocol prefix and migration plan, not a
+  permissive parser.
+- Run the `ckb-testtool` suite for every Script change. Positive creation,
+  replacement, and destruction plus unauthorised creation, incorrect custody
+  Locks, malformed input/output, and non-canonical args are mandatory evidence.
+- Production deployment requires a live mainnet code Cell, the standard
+  custody Lock CellDep, sufficient confirmations, and a committed deployment
+  manifest. Local CKB-VM tests are not mainnet deployment evidence.
+
 ## Backend And Codegen Rules
 
 `src/codegen/mod.rs` is the orchestration layer of a multi-file backend.

Cargo.toml

@@ -8,6 +8,7 @@ members = [
     "examples/ckb-sdk-builder",
 ]
 exclude = [
+    "contracts/registry-type-script",
     "services/registry-verifier",
     "proposals/novaseal/agreement-profile-v0/harness/ckb_vm",
     "proposals/novaseal/v0-mvp-skeleton/harness/ckb_vm",

contracts/registry-type-script/.gitignore

@@ -0,0 +1 @@
+/target/