Keep Registry interfaces aligned across networks

Author: a19q3

CHANGELOG.md

@@ -2,6 +2,14 @@
 
 ## Unreleased
 
+- Keep the production and Pudge Testnet Registry websites on one UI contract.
+  The website gate now builds both environments from the same source, verifies
+  six shared Registry routes, and requires every generated CSS/JavaScript asset
+  to be byte-identical. Testnet now ships the LS-IDL route, defaults LS-IDL
+  lookups and API examples to `testnet`, and no longer preloads production
+  package records into Manage or artifact-detail fallbacks. Network-specific
+  origins, chain selection, sandbox expiry, no-index policy, and storage remain
+  isolated.
 - Correct the 0.24 website release lineage after the first production build
   retained stale 0.22 release metadata and Playground assets. The homepage now
   advertises the official `v0.23.0` stable release and its 2026-08-11 date, the

docs/CELLSCRIPT_GATE_POLICY.md

@@ -79,7 +79,10 @@ Node-backed CI uses Node 22. After one checked Registry-data generation pass,
 the unified gate and manual website workflow both run
 `npm --prefix website run build:ci`; that target owns the complete Registry,
 playground, visual, homepage, preference, documentation, dist, deploy, Astro
-check, and Astro build regression contract.
+check, and Astro build regression contract. It builds both production and
+Pudge Testnet Registry outputs, checks the six shared routes in each, and
+requires their generated CSS and JavaScript assets to be byte-identical while
+allowing only explicit network authority and admitted-data differences.
 
 The 0.23 line also has one edition contract: every package declares
 `edition = "2026"`, and all emitted evidence binds the resolved compatibility

docs/releases/CELLSCRIPT_0_24_RELEASE_NOTES.md

@@ -117,6 +117,21 @@ implements the described decoder correctly, and they are not a security audit.
 The full profile and operator boundary are documented in the
 [LS-IDL Registry profile](../CELLSCRIPT_LS_IDL_REGISTRY_PROFILE.md).
 
+## Mainnet And Testnet Registry Parity
+
+The production and Pudge Testnet Registry websites now build from one shared
+interface contract. Browse, Publish, LS-IDL, API, Manage, and dynamic artifact
+detail are present in both outputs and load the same byte-identical generated
+CSS and JavaScript. The website CI build produces both environments and rejects
+a missing route, divergent asset, or missing shared workflow hook.
+
+Network context remains explicit rather than cosmetically erased. Testnet uses
+its own API and object origins, `ckt` address prefix, Pudge chain, expiry policy,
+and isolated records. Its LS-IDL form and copied API example default to
+`testnet`; Manage and artifact details do not preload or fall back to mainnet
+records. Production continues to default to mainnet. The environment control
+is the intended visible distinction between otherwise matching interfaces.
+
 ## Playground Experience Upgrade
 
 The browser Playground is now a recoverable Cell-oriented workbench rather

roadmap/CELLSCRIPT_0_24_ROADMAP.md

@@ -46,6 +46,14 @@ Registry compatibility route. The website names this surface `LS-IDL`
 explicitly and aligns it with the full-width Browse surface. This does not
 expand the language edition or claim implementation correctness.
 
+The mainnet and Pudge Testnet Registry sites also share one versioned interface
+contract. Both builds must expose the same six Registry routes and load the
+same byte-identical visual and interactive assets. Only network authority and
+network-derived state may differ: API/static origins, address prefix, chain,
+sandbox expiry and indexing policy, and the records admitted to each isolated
+store. Testnet lookup, API examples, Manage defaults, and artifact fallbacks
+must never silently select mainnet.
+
 ## Why This Is The Next Boundary
 
 CellScript 0.23 completed an operational distribution and evidence layer: