@@ -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, and `cellscript-tools`; strict backend audit (quick); syntax combo audit (quick); parity-gated skill-pack freshness; forbidden tracked-file check; `git diff --check`. Run before committing. |
-| `ci` | `dev` coverage plus tests and clippy for every workspace package, including `cellscript-tools`; full package contents check, website build check (requires `npm`), shell + Python syntax check, 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, and `cellscript-tools`; 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, including `cellscript-tools`; 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. |
 
@@ -126,11 +126,12 @@ Excluded from the workspace (still buildable through their own manifests):
 defines its own `[workspace]` (no parent) because it pulls `ckb-jsonrpc-types`
 and `ckb-types` from a sibling CKB checkout (`../ckb`).
 
-The 0.23 Python-to-Rust tooling migration is intentionally staged. Only
-`check-skill-pack` and `validate-tooling-release` are currently implemented in
-`cellscript-tools`; `scripts/dev/dual_run_tools.sh` requires their stdout and
-exit codes to match the retained Python implementations. Keep every other
-Python tool authoritative until its own port has equivalent parity evidence.
+The 0.23 tooling migration is complete. `cellscript-tools` is authoritative
+for gate, evidence, fixture, and release validation; website data generation
+uses the tracked Node modules under `website/scripts/`. Every gate runs the
+native source-policy check, which rejects retired interpreter sources,
+generated bytecode/cache artifacts, and interpreter references in active
+tooling source across the repository and initialized submodules.
 
 Features (root crate):
 
@@ -222,8 +223,9 @@ When extracting emitter methods from `codegen/mod.rs` into a sub-module:
    Fields of types shared across module boundaries also need `pub(crate)`.
 4. When removing code by line number with `sed`, delete later ranges first
    so earlier line numbers stay stable.
-5. After every deletion, brace-count with `python3 -c` to verify brace
-   balance before compiling.
+5. After every deletion, run formatting and a focused Rust check. The parser
+   and compiler are authoritative for brace balance; do not rely on textual
+   brace-count heuristics.
 
 ## CLI surface (where to add a new command)
 
@@ -273,8 +275,8 @@ Existing command families to be aware of:
 ## CKB / NovaSeal gotchas
 
 - The CKB acceptance harness is `scripts/ckb_cellscript_acceptance.sh`. It
-  expects a sibling `../ckb-sdk-rust` checkout at tag `v5.1.0` and runs
-  `scripts/validate_ckb_cellscript_production_evidence.py` against the build
+  expects a sibling `../ckb-sdk-rust` checkout at tag `v5.1.0` and runs the
+  `cellscript-tools validate-production-evidence` command against the build
   reports. Its build reports, source provenance hashes, and production
   hardening gate (`final_production_hardening_gate`) are referenced by
   string from the gate script; if you rename them, update
 
@@ -2,6 +2,13 @@
 
 ## Unreleased
 
+- Complete the native-tooling cleanup: neutralize migration-era identifiers,
+  remove tracked legacy traceback logs and cache exclusions, rename the native
+  tooling integration suite, and add a repository-wide source-policy command
+  to every gate. The policy traverses initialized submodules and rejects
+  retired interpreter sources, generated bytecode/cache artifacts, capture
+  logs, and active tooling references before they can re-enter the release
+  contract.
 - Restore the 0.23 release gate after the Python-to-Rust tooling migration by
   checking the semantic `requires_all_bundled_examples_strict_original_ckb`
   and emitted `source_provenance` CKB boundaries plus the Rust-backed NovaSeal