@@ -11,7 +11,11 @@
   editions and older persisted schemas are rejected; no migration or
   compatibility reader is provided. Generated CKB entries also remove the
   raw-`CSARGv1` witness fallback, so Edition 2026 accepts the payload only
-  inside canonical `WitnessArgs.input_type`. See the
+  inside canonical `WitnessArgs.input_type`. The public registry contract is
+  hard-cut to publish protocol v2 and registry schema 2: signed entries,
+  persisted rows, CDN JSON, and the website all require Edition 2026 and the
+  compatibility-profile hash. The generic admin API can no longer manufacture
+  `verified_build` or `deployed` claims without an evidence-specific path. See the
   [0.23 development release notes](docs/releases/CELLSCRIPT_0_23_RELEASE_NOTES.md).
 - Complete the native-tooling cleanup: neutralize migration-era identifiers,
   remove tracked legacy traceback logs and cache exclusions, rename the native
 
@@ -15,7 +15,7 @@ deciding whether a change is ready.
 | Mode | When to run | Evidence boundary |
 |---|---|---|
 | `dev` | Local development before pushing | Rust formatting, canonical CellScript example formatting, all workspace-package Rust checks (including `cellscript-tools`), strict backend quick audit, syntax-combination quick audit, parity-gated skill-pack freshness, README-linked CellScript doc Status freshness, local markdown link check, whitespace diff check |
-| `ci` | Pull requests, pushes, and routine merge readiness | Canonical CellScript example formatting; tests and clippy for the compiler, Fiber adapter, CKB adapter, WASM crate, CKB SDK builder example, and `cellscript-tools`; strict backend CI audit; package verification; parity-gated skill-pack/doc freshness; local-link and script syntax checks |
+| `ci` | Pull requests, pushes, and routine merge readiness | Canonical CellScript example formatting; tests and clippy for the compiler, Fiber adapter, CKB adapter, WASM crate, CKB SDK builder example, and `cellscript-tools`; registry API typecheck/tests/dry-run Worker build; strict backend CI audit; package verification; parity-gated skill-pack/doc freshness; local-link and script syntax checks |
 | `backend` | Changes touching IR, codegen, assembler, ABI, ELF, or RISC-V behavior | Full Rust tests, clippy, and strict backend full audit, including stateful CKB scenarios |
 | `release` | Nightly/stable release candidates and any production CKB claim | Clean tagged source plus `ci`, a fresh size-gated website WASM rebuild, tooling/docs and VS Code checks, pinned-CKB acceptance harnesses, public builder-contract generation, and mandatory stateful scenario/action coverage |
 | `release-quick` | Wrapper compatibility and local compile-only preflight | `ci` plus compile-only production acceptance; not external live/devnet evidence |
@@ -53,6 +53,11 @@ migrated. See
 ABI changes require the `backend` gate in addition to ordinary `dev` and `ci`
 coverage.
 
+The `ci` gate also typechecks, tests, and performs a Wrangler dry-run build of
+`services/registry-api`. This pins the publish-protocol/schema contract to the
+compiler-generated registry entry. It is local service coverage, not evidence
+that Cloudflare, R2, Hyperdrive, Neon, DNS, or a production deployment works.
+
 The full gate reads `scripts/ckb_acceptance_pin.json` and rejects a CKB checkout
 whose revision or worktree differs from the pin. Its report binds the CKB
 version string, executable SHA-256, source-template hashes, effective devnet
 
@@ -793,7 +793,7 @@ for audit, offline fixtures, and direct-Git fallback:
       "version": "1.2.0",
       "tag": "v1.2.0",
       "source_hash": "blake2b:0xabcd...",
-      "cellscript_version": "0.19.0",
+      "cellscript_version": "0.22.0",
       "dependencies": {
         "token": { "namespace": "cellscript", "version": "0.3.0" }
       },
@@ -1093,7 +1093,7 @@ alongside `Cell.toml`, for audit and offline use:
 
 ```json
 {
-  "schema_version": 1,
+  "schema_version": 2,
   "name": "amm",
   "namespace": "cellscript",
   "versions": [
@@ -1102,13 +1102,16 @@ alongside `Cell.toml`, for audit and offline use:
       "tag": "v1.2.0",
       "source_hash": "blake2b:0xabcd...",
       "cellscript_version": "0.19.0",
+      "edition": "2026",
+      "compatibility_profile_hash": "42d297cd7879917ade58c89cdc5dcbbb38a5d39b720788387db80e918a3f7fd9",
       "dependencies": {
         "token": { "namespace": "cellscript", "version": "0.3.0" }
       },
       "abi_index": "blake2b:0xdef0...",
       "schema_hash": "blake2b:0x9abc...",
       "license": "MIT",
       "released_at": "2026-04-24T00:00:00Z",
+      "status": "source_published",
       "yanked": false,
       "audit": {
         "report_hash": "blake2b:0x5555...",
@@ -1119,6 +1122,10 @@ alongside `Cell.toml`, for audit and offline use:
 }
 ```
 
+The current Edition 2026 reader accepts only schema 2. The older schema-1
+shape described in the historical Phase 1 audit below is not a compatibility
+surface.
+
 The `tag` field maps each version to a git tag in the source repository.
 This allows `cellc install` to clone the exact commit without needing
 a separate archive storage layer.
 
@@ -22,6 +22,7 @@ work until their implementation and evidence boundaries are complete.
 | Entry witness | `CSARGv1` is decoded only from canonical Molecule `WitnessArgs.input_type`. |
 | Failure mode | Raw payloads, malformed tables, absent `input_type`, wrong placement, and mismatched identities fail closed. |
 | Build identity | The resolved compatibility profile is bound into metadata, registry, lock, deployment, receipt, and builder records. |
+| Registry contract | Publish protocol v2 and registry schema 2 require Edition 2026 plus its compatibility-profile hash from CLI signature through API, database, CDN JSON, and website. |
 | Tooling | CLI, LSP, WASM, website bindings, examples, and package tooling use the same edition contract. |
 | Native gate | Active test, fixture, evidence, and release tooling is Rust, shell, or Node; repository policy rejects Python source reintroduction. |
 
@@ -104,10 +105,18 @@ The 0.23 identity set is:
 | Compile receipt | edition and resolved compatibility profile |
 | Generated action builder | `cellscript-generated-action-builder-v0.23-edition-2026` |
 | Registry build record | edition and compatibility-profile hash |
+| `registry.json` / public publish | schema 2 / `cellscript-registry-publish-v2` |
 
 Consumers reject other identities. Rebuild the artifact and regenerate its
 metadata, lock/deployment records, receipt, and builder together.
 
+The registry boundary has no v1 reader or migration path. The write API checks
+the complete signed nested entry instead of accepting an untyped JSON object,
+persists edition/profile as typed columns, and repeats them in the CDN object.
+Generic admin status changes may quarantine, yank, deprecate, or move an entry
+through indexing, but cannot label it `verified_build` or `deployed` without a
+future evidence-specific promotion endpoint.
+
 ## CLI, LSP, WASM, And Website
 
 - Package commands read Edition 2026 from `Cell.toml`.
@@ -116,6 +125,8 @@ metadata, lock/deployment records, receipt, and builder together.
   accept only `"2026"`.
 - The playground worker and TypeScript declarations pass that edition into the
   WASM boundary and include it in compiler-output provenance.
+- Registry pages reject stale schema-1 fixture data and display each package
+  version's edition and compatibility-profile hash.
 - Entry-witness reports, ABI reports, action plans, and generated builders
   expose canonical `WitnessArgs.input_type` placement.
 - NovaSeal core, agreement, and planned-profile devnet transaction constructors
 
@@ -64,6 +64,34 @@ cellc publish --json
 The public write API admits package metadata, but consumers still verify the
 source and build identity locally.
 
+## Edition 2026 Registry Contract
+
+Public publishing uses `cellscript-registry-publish-v2` and registry schema 2.
+The signed payload contains one complete version entry, and the API checks that
+its namespace, package name, version, and source hash equal the outer signed
+identity. The entry must also contain:
+
+```json
+{
+  "schema_version": 2,
+  "versions": [{
+    "edition": "2026",
+    "compatibility_profile_hash": "<32-byte hex hash>"
+  }]
+}
+```
+
+These are not website labels. `edition` identifies the selected language and
+CKB ABI rule bundle; `compatibility_profile_hash` binds the resolved details of
+that bundle. The API stores both as typed fields and exposes them in its static
+package-version JSON. Schema 1, a missing field, or a mismatched nested identity
+is rejected. There is no v1 migration or compatibility reader.
+
+`source_published` means the signed source snapshot was admitted; it does not
+mean the build or deployment was verified. The generic admin endpoint cannot
+promote an entry to `verified_build` or `deployed`. Those labels require a
+future evidence-specific verification flow.
+
 ## Consumer Flow
 
 Add a dependency, resolve it, and check the resulting package graph:
 
@@ -130,6 +130,13 @@ path, idempotent publish, and admin-gated status transitions. The 0.23 work
 is to actually deploy it on `cellscript.dev` and to wire the frontend and CLI
 into the same trust model.
 
+The Edition 2026 contract slice is complete: publish protocol v2 and registry
+schema 2 are a hard cut across the Rust publisher/reader, API validation,
+Postgres schema, R2 package-version object, checked-in registry fixture, and
+website data model. There is no schema-1 compatibility path. Generic admin
+status changes cannot create `verified_build` or `deployed` claims; an
+evidence-specific promotion path remains production work.
+
 ### Production Domains And Hosting
 
 ```text
@@ -198,9 +205,10 @@ Production-readiness for the registry means all of:
 - the first real CellScript source package is published through the
   production flow and resolves on a clean machine via `cellc install`.
 
-The existing `services/registry-api` test suite is the baseline. New
-end-to-end coverage belongs in a deployable scenario harness, not in the
-compiler test gate.
+The existing `services/registry-api` typecheck, unit suite, and dry-run Worker
+build run in the unified `ci` gate as the local contract baseline. Deployed
+end-to-end coverage still belongs in a staging scenario harness; local compiler
+CI is not Cloudflare/R2/Hyperdrive/Neon evidence.
 
 ### Non-Goals
 
 
@@ -357,6 +357,15 @@ run_website_build_check() {
     run_in_dir website npm exec -- astro build
 }
 
+run_registry_api_check() {
+    if [[ ! -d services/registry-api/node_modules ]]; then
+        run npm --prefix services/registry-api ci
+    fi
+    run npm --prefix services/registry-api run check
+    run npm --prefix services/registry-api test
+    run npm --prefix services/registry-api run build
+}
+
 check_wasm_release_bundle() {
     require_cmd docker
     run website/scripts/build-wasm.sh
@@ -438,6 +447,7 @@ run_ci_gate() {
     check_markdown_local_links
     check_package_contents
     run cargo package --locked --offline --allow-dirty
+    run_registry_api_check
     run_website_build_check
     check_script_syntax
     run git diff --check
 
@@ -29,6 +29,9 @@ snapshots and static registry read objects are stored in R2.
 - Namespace claim cooldown for newly claimed namespaces by the same JoyID
   principal; invalid JoyID signatures do not consume principal quota.
 - Publish admission path for source packages.
+- Hard-cut `cellscript-registry-publish-v2` admission: the signed
+  `registry_entry` must use registry schema 2, contain exactly the published
+  version, and bind Edition 2026 plus its compatibility-profile hash.
 - Namespace owner ACL check before publish admission.
 - P-256 capability-signature verification for daily publish payloads.
 - One-time signed nonce consumption for capability creation, capability
@@ -50,7 +53,10 @@ snapshots and static registry read objects are stored in R2.
 - Future `policy_hooks` and `bond_policy_hooks` tables for later bond or
   refundable-deposit policies; no on-chain fee or bond is enforced now.
 - Token-gated admin operations for reserved namespaces, namespace review
-  status, and package-version status transitions.
+  status, and conservative package-version status transitions. Generic admin
+  status changes cannot claim `verified_build` or `deployed`; those promotions
+  remain unavailable until an evidence-specific endpoint verifies and stores
+  the corresponding proof.
 - Suppressive package-version admin transitions (`deprecated`, `yanked`,
   `quarantined`) update the static read object before changing the write-store
   status, so public reads fail conservative during incident response.
@@ -128,20 +134,22 @@ for controlled staging tests.
 Admin operations require `Authorization: Bearer <REGISTRY_ADMIN_TOKEN>` or
 `x-registry-admin-token`. The optional `x-registry-admin-actor` header is stored
 in audit logs so manual review, reserved namespace changes, quarantine, yanks,
-deprecations, and verification promotions are attributable.
+and deprecations are attributable.
 
 Supported package-version status transitions through the admin API are:
 
 ```text
 source_published
 indexed_pending
-verified_build
-deployed
 deprecated
 yanked
 quarantined
 ```
 
+`verified_build`, `deployed`, and `on_chain_attested` remain registry states,
+but this generic endpoint cannot create those claims. A future promotion path
+must validate evidence rather than accepting an operator-supplied label.
+
 Audit events can be queried with:
 
 ```text
@@ -193,7 +201,7 @@ cellscript-registry-auth-v1 / authorize_capability
 Daily publish signs the canonical JSON form of:
 
 ```text
-cellscript-registry-publish-v1 / publish
+cellscript-registry-publish-v2 / publish
 ```
 
 The API rejects a publish unless:
@@ -203,6 +211,10 @@ The API rejects a publish unless:
 - the capability scope covers `publish:namespace/package`;
 - the namespace exists and is active;
 - the capability principal owns the namespace;
+- the signed nested registry entry is schema 2, names the same package/version
+  and source hash, and records `edition = "2026"` plus a 32-byte
+  `compatibility_profile_hash`;
+- the signed manifest hash is present;
 - the capability signature verifies;
 - the signed publish nonce has not already been consumed;
 - the package version does not already exist;
@@ -232,7 +244,9 @@ https://registry.cellscript.dev/packages/:namespace/:name/versions/:version.json
 
 The route is served from R2 and sets short CDN cache headers. It does not
 require Hyperdrive or the write store, so ordinary package reads stay isolated
-from authenticated write-path dependencies.
+from authenticated write-path dependencies. Its JSON object is also schema 2
+and repeats `edition` and `compatibility_profile_hash` at the top level so
+consumers do not need to trust an untyped nested blob.
 
 CLI publish has two supported signing shapes:
 
 
@@ -92,7 +92,9 @@ create table if not exists package_versions (
   version text not null,
   status text not null,
   source_hash text not null,
-  manifest_hash text,
+  manifest_hash text not null,
+  edition text not null,
+  compatibility_profile_hash text not null,
   capability_key_id text not null references capabilities(key_id),
   principal_type text not null,
   principal_id text not null,
@@ -117,7 +119,11 @@ create table if not exists package_versions (
     'deprecated',
     'yanked',
     'quarantined'
-  ))
+  )),
+  check (source_hash ~ '^(0x)?[0-9A-Fa-f]{64}$'),
+  check (manifest_hash ~ '^(0x)?[0-9A-Fa-f]{64}$'),
+  check (edition = '2026'),
+  check (compatibility_profile_hash ~ '^(0x)?[0-9A-Fa-f]{64}$')
 );
 
 create table if not exists idempotency_keys (