@artblocks/abx-cli 0.1.0-alpha.62 → 0.1.0-alpha.64

package/skill/reference/capabilities.md

@@ -65,8 +65,10 @@ One external contract may implement several hook/minter roles. Test it against a
 not a mock that approximates ABX callbacks.
 
 ABX scaffolds a Foundry renderer project but does not compile, link, or audit custom Solidity.
-`abx deploy-contract` can send exact compiled creation bytecode through any signing lane. The creator
-or their contract engineer owns code review, verification, upgrade policy, and audits.
+`abx deploy-contract` can send exact compiled creation bytecode through any signing lane. The
+sponsored lane calls the keyless CREATE2 proxy, so the constructor caller is that proxy; use explicit
+constructor arguments for ownership. Hot, wallet, and unsigned lanes retain direct CREATE. The
+creator or their contract engineer owns code review, verification, upgrade policy, and audits.
 
 ### Custom minter
 

package/skill/reference/code.md

@@ -148,8 +148,9 @@ effects runner.
 
 Start with `abx scaffold-renderer`, then build and test the Solidity project using Foundry. Deploy
 with Foundry or send the exact compiled initcode through `abx deploy-contract`; ABX does not compile,
-link, audit, or infer constructor types. A real collection deploy refuses a renderer address with no
-code.
+link, audit, or infer constructor types. With `--sponsor`, use explicit constructor arguments for
+ownership because the keyless CREATE2 proxy—not the creator wallet—is the constructor caller. A real
+collection deploy refuses a renderer address with no code.
 
 Enforce these invariants in renderer tests:
 

package/skill/reference/services.md

@@ -100,12 +100,13 @@ production-network warning before confirmation. Before using it:
    and beta status;
 5. after approval, repeat with `--sponsor`.
 
-The lane accepts zero-value factory calls, direct contract creation, and receipt-dependent staged
-content groups up to the live network and provider policy. ABX does not impose an additional
-per-transaction gas ceiling. Use `abx deploy-contract` for exact already-compiled creation bytecode;
-ABX does not compile or audit it. Never add retries around a sponsored write. An `unknown` outcome
-means the provider may have submitted it: preserve the operation ID and reconcile status before any
-new send.
+The lane accepts zero-value calls and receipt-dependent staged content groups up to the live network
+and provider policy. ABX does not impose an additional per-transaction gas ceiling. Use
+`abx deploy-contract` for exact already-compiled creation bytecode; its sponsored path calls the
+keyless CREATE2 proxy because provider-backed raw creation is unsupported. The constructor therefore
+sees the proxy as `msg.sender`; use explicit constructor arguments for ownership. ABX does not
+compile or audit it. Never add retries around a sponsored write. An `unknown` outcome means the
+provider may have submitted it: preserve the operation ID and reconcile status before any new send.
 
 Sponsorship is optional service policy, not protocol support. `--send`, `--sign`, and `--unsigned`
 remain first-class bring-your-own alternatives. Honor an explicit choice of any of them. If the