@artblocks/abx-cli 0.1.0-alpha.44 → 0.1.0-alpha.45

package/skill/SKILL.md

@@ -9,7 +9,7 @@ description: >-
   change an ABX collection, or to determine whether ABX supports a mechanic.
 compatibility: Drives @artblocks/abx-cli on Node 22.13+. Co-versioned with the CLI; install or refresh with `abx skill install`.
 metadata:
-  version: "0.1.0-alpha.44"
+  version: "0.1.0-alpha.45"
 ---
 
 # ABX
@@ -24,8 +24,9 @@ typed errors outrank remembered prose.
   inspect configuration safely.
 - Use `pnpm abx …` inside the ABX source repository. Use `abx …` in a creator project or installed
   environment. Run `abx version` if provenance is uncertain.
-- Operate only on chains reported by `abx capabilities`; the toolkit is testnet-only today. Select
-  the chain with `ABX_CHAIN=<chain>`; there is deliberately no `--chain` flag.
+- Read the full `chains` array from `abx capabilities --json` before choosing a network. Never
+  operate on a `disabled` chain. Call out `experimental` or `beta` status and its risks before a
+  transaction. Select with `ABX_CHAIN=<chain>`; there is deliberately no `--chain` flag.
 - Run `abx help <command>` immediately before composing a non-trivial command. Do not recover flag
   syntax from this skill.
 - Never infer that a capability is absent because a flag is absent. Run `abx capabilities --json`,

package/skill/reference/capabilities.md

@@ -160,7 +160,8 @@ salt/deployer and predicted address before deploying either side.
 
 The toolkit currently does not provide:
 
-- mainnet deployment or unsupported-chain recipes;
+- operation on a chain whose capability entry is `disabled`, including all production networks in
+  the current release;
 - a secondary-market listing/order-book feature;
 - Solidity compilation/deployment through `abx`;
 - CLI replacement of a deployed code project's script;

package/skill/reference/setup.md

@@ -58,9 +58,15 @@ output bug without repeating the secret.
 
 ## Select the chain explicitly through the environment
 
-The toolkit supports the chains printed by `abx capabilities`; today those are Base Sepolia by
-default and Ethereum Sepolia via `ABX_CHAIN=sepolia`. There is deliberately no `--chain` flag. The
-CLI refuses it because silently ignoring a wrong-chain request could spend on the wrong network.
+Read the full `chains` array from `abx capabilities --json`. Base Sepolia is the default; Sepolia is
+also supported. Arbitrum Sepolia is experimental and has no canonical ABX contracts yet, so use it
+only for explicit qualification with the required address overrides. Production entries are present
+but disabled, and the CLI refuses them. There is deliberately no `--chain` flag because silently
+ignoring a wrong-chain request could spend on the wrong network.
+
+Before any transaction on an `experimental` or future `beta` network, name the network and support
+level, explain what the transaction or transaction group will do, and state the relevant contract,
+configuration, and real-funds risks. Qualify the same flow on the paired testnet before production.
 
 Use per-chain RPC variables when operating more than one chain. `abx doctor` checks chain identity,
 wide-range `eth_getLogs`, archival reach, and nonce coherence. Put a healthy archive endpoint first: