fix: change previewnet TLD from .test to .testnet

.github/workflows/publish-prerelease.yml

@@ -26,7 +26,7 @@ jobs:
     # Baked into the genesis registry, so it decides which networks the artifact suits.
     # Job-level: five steps name the file derived from it and must not disagree.
     env:
-      DOTNS_TLD: test
+      DOTNS_TLD: testnet
     steps:
       # On workflow_dispatch the tag does not exist yet; the release step creates it
       # from the branch this run was started on. Read through an env var rather than

.github/workflows/publish-release.yml

@@ -26,7 +26,7 @@ jobs:
     # Baked into the genesis registry, so it decides which networks the artifact suits.
     # Job-level: five steps name the file derived from it and must not disagree.
     env:
-      DOTNS_TLD: test
+      DOTNS_TLD: testnet
     steps:
       # On workflow_dispatch the tag does not exist yet; the release step creates it
       # from the branch this run was started on. Read through an env var rather than

DEPLOYMENTS.md

@@ -449,7 +449,7 @@ Every network deployed through the shared CREATE3 factory lands on the same addr
 
 | Network | TLD |
 | --- | --- |
-| Paseo Asset Hub Previewnet | `.test` |
+| Paseo Asset Hub Previewnet | `.testnet` |
 | Paseo Asset Hub Next V2 | `.paseo` |
 
 Each release also publishes the same addresses as `deployments.json`, attached to the release and at the root of `dotns-abis-<tag>.zip`, for consumers outside this repository. See [`RELEASE_ARTIFACTS.md`](./RELEASE_ARTIFACTS.md).

scripts/deploy/BaseDeployer.s.sol

@@ -64,7 +64,7 @@ abstract contract BaseDeployer is Script {
 
     /// @notice Resolves the bare TLD label to initialise the protocol registry with.
     /// @dev Read from `DOTNS_TLD` because distinct networks can share one `block.chainid`, so the
-    ///      TLD cannot be keyed off the chain id. The operator sets `DOTNS_TLD=paseo` (or `test`,
+    ///      TLD cannot be keyed off the chain id. Operators set `DOTNS_TLD=paseo` (or `testnet`,
     ///      `dot`) per deployment; it is required, with no default, so an unset or empty value
     ///      aborts the deploy rather than silently landing the wrong TLD, which no setter can
     ///      correct afterwards. The label is passed straight into

scripts/genesis/build-genesis.sh

@@ -13,7 +13,7 @@ set -euo pipefail
 #   dotns-genesis-<tld>.json  pallet-revive GenesisConfig accounts
 #
 # The TLD is in the filename because it is baked into the registry initialiser: a genesis built
-# with DOTNS_TLD=test suits a test network and nothing else, and a file called plainly
+# with DOTNS_TLD=testnet suits a test network and nothing else, and a file called plainly
 # `dotns-genesis.json` is how a test registry ends up on a chain that wanted a real one.
 #
 # Addresses are NOT emitted here. `release-metadata.mjs build` already publishes deployments.json
@@ -73,7 +73,7 @@ WHITELIST_OPERATOR="${WHITELIST_OPERATOR:-}"
 # forge stage. This does not affect any address — only registry storage — but it
 # does decide which networks the resulting genesis is fit for, so it ends up in
 # the output filename.
-export DOTNS_TLD="${DOTNS_TLD:-test}"
+export DOTNS_TLD="${DOTNS_TLD:-testnet}"
 if ! printf '%s' "$DOTNS_TLD" | grep -Eq '^[a-z]{2,63}$'; then
     echo "Error: DOTNS_TLD ('$DOTNS_TLD') must be 2 to 63 lowercase ASCII letters (a-z)" >&2
     exit 1

scripts/genesis/extract-genesis.mjs

@@ -21,7 +21,7 @@
  *   node scripts/genesis/extract-genesis.mjs \
  *     --state ./release/anvil-state.json \
  *     --deployments ./deployments/localhost/31337.json \
- *     --output ./release/dotns-genesis-test.json
+ *     --output ./release/dotns-genesis-testnet.json
  */
 
 import { readFileSync, writeFileSync } from "fs";