@artblocks/abx-token-api 0.1.0-alpha.3 → 0.1.0-alpha.30

package/CHANGELOG.md

@@ -0,0 +1,1233 @@
+# @artblocks/abx-token-api
+
+## 0.1.0-alpha.30
+
+### Patch Changes
+
+- Updated dependencies [4072f0c]
+  - @artblocks/abx-sdk@0.1.0-alpha.27
+  - @artblocks/abx-indexer@0.1.0-alpha.28
+  - @artblocks/abx-storage@0.1.0-alpha.27
+
+## 0.1.0-alpha.29
+
+### Patch Changes
+
+- Updated dependencies [b182f23]
+  - @artblocks/abx-sdk@0.1.0-alpha.26
+  - @artblocks/abx-indexer@0.1.0-alpha.27
+  - @artblocks/abx-storage@0.1.0-alpha.26
+
+## 0.1.0-alpha.28
+
+### Patch Changes
+
+- Updated dependencies [8f2f78a]
+  - @artblocks/abx-sdk@0.1.0-alpha.25
+  - @artblocks/abx-indexer@0.1.0-alpha.26
+  - @artblocks/abx-storage@0.1.0-alpha.25
+
+## 0.1.0-alpha.27
+
+### Patch Changes
+
+- Updated dependencies [61503c3]
+  - @artblocks/abx-sdk@0.1.0-alpha.24
+  - @artblocks/abx-indexer@0.1.0-alpha.25
+  - @artblocks/abx-storage@0.1.0-alpha.24
+
+## 0.1.0-alpha.26
+
+### Patch Changes
+
+- bd77ba2: Correct the Node floor to 22.13, and refuse to start with a remedy instead of a stack trace.
+
+  Every package declared `engines.node: ">=22.5.0"` — the version `node:sqlite` was **added**, not the
+  version it became usable. It shipped in v22.5.0 behind `--experimental-sqlite` and lost the flag in
+  v22.13.0 / v23.4.0. So `npm i -g @artblocks/abx-cli` on Node 22.5 installed silently (the engine
+  range was satisfied) and then `abx doctor` — the first command we tell everyone to run — died with a
+  raw `ERR_UNKNOWN_BUILTIN_MODULE: No such built-in module: node:sqlite` stack trace naming neither
+  abx nor a fix. Reported 2026-08-24; the floor is now `>=22.13.0` everywhere, so npm warns at install
+  time.
+
+  The crash happened while ESM _linked_ `main.ts`'s import graph (`output.ts` →
+  `@artblocks/abx-indexer` → `node:sqlite`), before any of our code ran, so no guard inside the CLI
+  could have caught it. The published binary is now a deliberately import-free shim (`dist/bin.js`)
+  that probes for `node:sqlite` and hands off to `main.js` — it prints the running version, the real
+  floor, and the upgrade command. It probes the **capability**, not the version number: an old Node
+  launched with `NODE_OPTIONS=--experimental-sqlite` genuinely works, and refusing that would be a
+  false negative. `engines` states what we support; the guard blocks only what is actually broken.
+
+  `abx doctor`'s header now also reports the running Node, since its output is what people paste when
+  something is wrong.
+
+- Updated dependencies [bd77ba2]
+  - @artblocks/abx-indexer@0.1.0-alpha.24
+  - @artblocks/abx-storage@0.1.0-alpha.23
+  - @artblocks/abx-sdk@0.1.0-alpha.23
+
+## 0.1.0-alpha.25
+
+### Patch Changes
+
+- 549a32d: The live-view route (`/a/:chainId/:address/:id`) tells the truth for renderer-only projects and for
+  ERC-1155 editions. Two inverse bugs in one branch:
+
+  - **A renderer-only code project answered `503 + Retry-After` forever.** `deploy-code --image-renderer
+… --onchain-uri` with no `--script` has no program and never will — image and traits are computed in
+    Solidity. The route told callers to keep retrying for content that does not exist. It is now the
+    terminal 404, which is the honest answer: there is no live view here, by design.
+  - **`edition-code` was missing from the code-contract check**, so an EditionCode whose chunks had not
+    been folded in yet answered the _terminal_ 404 instead of the retryable 503 — the exact inverse
+    failure the mid-index case was written to prevent, on the ERC-1155 lane.
+
+  The two are separated by `script.chunkCount`, which is a head read: a number is what the chain says
+  right now, so `0` means there is nothing to wait for, while `null` means nobody has asked yet and the
+  honest answer to unknown stays the retryable one.
+
+  Newly relevant because `deploy-code --copies --image-renderer` now makes a fully on-chain ERC-1155 a
+  supported lane, and every project on it is renderer-only.
+
+- Updated dependencies [993e095]
+  - @artblocks/abx-sdk@0.1.0-alpha.22
+  - @artblocks/abx-indexer@0.1.0-alpha.23
+  - @artblocks/abx-storage@0.1.0-alpha.22
+
+## 0.1.0-alpha.24
+
+### Patch Changes
+
+- Updated dependencies [c9f7aeb]
+  - @artblocks/abx-sdk@0.1.0-alpha.21
+  - @artblocks/abx-storage@0.1.0-alpha.21
+  - @artblocks/abx-indexer@0.1.0-alpha.22
+
+## 0.1.0-alpha.23
+
+### Patch Changes
+
+- Updated dependencies [84ca9dd]
+- Updated dependencies [84ca9dd]
+  - @artblocks/abx-sdk@0.1.0-alpha.20
+  - @artblocks/abx-indexer@0.1.0-alpha.21
+  - @artblocks/abx-storage@0.1.0-alpha.20
+
+## 0.1.0-alpha.22
+
+### Patch Changes
+
+- Updated dependencies [b1c333d]
+- Updated dependencies [b1c333d]
+  - @artblocks/abx-sdk@0.1.0-alpha.19
+  - @artblocks/abx-indexer@0.1.0-alpha.20
+  - @artblocks/abx-storage@0.1.0-alpha.19
+
+## 0.1.0-alpha.21
+
+### Patch Changes
+
+- Updated dependencies [77a6248]
+- Updated dependencies [77a6248]
+  - @artblocks/abx-sdk@0.1.0-alpha.18
+  - @artblocks/abx-indexer@0.1.0-alpha.19
+  - @artblocks/abx-storage@0.1.0-alpha.18
+
+## 0.1.0-alpha.20
+
+### Minor Changes
+
+- c5b8ec3: `ipfs` and `arweave` metadata fields now resolve on both planes, through a gateway the collection
+  chooses — renderer **spec v11**.
+
+  These are the two representations that are content-addressed, the two where the locator IS the
+  integrity hash, and the two this protocol tells creators to prefer. They were also the two the
+  on-chain renderer could not serve. So `abx deploy --onchain-uri --backend ipfs|arweave` worked around
+  it by baking a gateway HOST into a `url` field, which welded a hostname the creator could never
+  migrate and made `abx_provenance` report `source: url` for bytes that live on IPFS.
+
+  The fix separates the two facts that the baked URL had fused. The CID/txid stays in the field, as
+  identity, under that field's own lock. The HTTPS prefix becomes a project-wide preference in two
+  reserved collection-scope fields, `abx_gateway_ipfs` / `abx_gateway_arweave`, with `https://ipfs.io/ipfs/`
+  and `https://arweave.net/` as floors. The renderer, the canonical generator, and the off-chain
+  resolver all read those two fields and apply the same wrap, so a token served from the chain and from
+  a resolver produces the same URL.
+
+  A dead or slow gateway is now a **repoint**, not a rewrite:
+
+  ```bash
+  abx set-gateway 0xYourContract --ipfs https://your-dedicated.mypinata.cloud/ipfs/
+  ```
+
+  One transaction, every token, no re-upload — and it works on fields you have already locked, because
+  the locked value is the CID and the gateway was never in it.
+
+  **What changes for you**
+
+  - `--onchain-uri --backend ipfs|arweave` writes the bare CID (or `cid/{id}.ext` for the O(1) directory)
+    as an `ipfs`/`arweave` field instead of a gateway URL as `url`/`url-template`. `--backend cloud` is
+    unchanged — an HTTPS CDN locator _is_ the address.
+  - New `abx set-gateway <addr> [--ipfs <prefix>] [--arweave <prefix>]` (`none` clears to the public
+    default). Two flags, so a project can pay for a dedicated IPFS gateway and leave Arweave public.
+  - New `--ipfs-gateway` / `--arweave-gateway` on every deploy command. Plain `--gateway` (the
+    storage/upload gateway) seeds the preference for the backend in use, so passing it still does what
+    you meant. Nothing is written when no gateway is named — silence keeps the floor live.
+  - `abx set-field` refuses the two gateway keys and points at `set-gateway`, which validates the
+    prefix, the scope and the representation. Every way to set them by hand fails silently.
+  - The `display.gateway` contract param is **superseded and no longer read**. It could name only one
+    prefix for both schemes and existed only on code projects.
+  - SDK: `projectGatewayPrefix`, `projectGatewayUrl`, `gatewayPrefixFrom`, `contentIdFromLocator`,
+    `GATEWAY_FIELD`, `GATEWAY_FLOOR`. For a host running its own resolver, `ABX_IPFS_GATEWAY` /
+    `ABX_ARWEAVE_GATEWAY` are now a **floor**: a project that stated a preference on chain gets that
+    preference from every conforming resolver, and host config only fills a silence.
+
+  **New canonical addresses** (both testnets; nothing else moved — no token implementation, factory, or
+  `initialize` ABI changed):
+
+  | Contract                         | Address                                      |
+  | -------------------------------- | -------------------------------------------- |
+  | `AbxMetadataRenderer` (spec v11) | `0x85C1aE1F076d808fF7c1729F21B85038Fa16105E` |
+  | `AbxGenerator` (Sepolia)         | `0xb7104AdFa6Fb5615e46E2a681A2Ff043B08fADB5` |
+  | `AbxGenerator` (Base Sepolia)    | `0x2c1b7Cf6C54E4acBcB54FCc395f7Af88eB4fC8Ce` |
+
+  Also fixes a crash on `abx deploy-code --copies`: an undefined `bytes` reference threw a
+  `ReferenceError` at the end of the dry-run plan and, worse, at the confirmation prompt of a real
+  deploy.
+
+### Patch Changes
+
+- 5b29f53: Drop-in for every reconstruct caller; new exports for hosted/self-host watch loops so they stop
+  reimplementing `eth_getLogs` chunking and a second per-project fetch.
+
+  **`getLogsAdaptive` is public and accepts `Address | Address[]`.** Address-list chunking defaults to
+  1000 (ordinary RPC tier cap) via `addressBatch` — an RPC opinion, not a protocol constant; `0`
+  disables splitting. Per-tick block windows stay with the watcher (the reference one still uses 5000).
+
+  **`reconstructFromLogs(client, prior, logs, {toBlock})`** is the fold / head-read half of
+  `reconstructIncremental` given logs the caller already holds. `toBlock` is the inclusive scan head
+  those logs cover, so a capped window cannot stamp past the last block actually scanned.
+  `reconstructIncremental` is now a getLogs + that function.
+
+  **A Transfer no longer re-downloads every on-chain script chunk.** Chunk content has no log;
+  `ScriptUpdated` is the ping. `applyHeadReads` keeps the prior digest unless that ping is in `fresh`
+  (or the prior digest is missing). Same change helps the single-address path.
+
+  The reference token-api watcher now calls `getLogsAdaptive` for the registered set and hands each
+  touched project's logs to `reindex({logs, toBlock})`, so the watch tick is the only getLogs.
+
+- Updated dependencies [c5b8ec3]
+- Updated dependencies [5b29f53]
+  - @artblocks/abx-sdk@0.1.0-alpha.17
+  - @artblocks/abx-indexer@0.1.0-alpha.18
+  - @artblocks/abx-storage@0.1.0-alpha.17
+
+## 0.1.0-alpha.19
+
+### Patch Changes
+
+- Updated dependencies [9c287c0]
+- Updated dependencies [b5744a1]
+- Updated dependencies [9c287c0]
+  - @artblocks/abx-sdk@0.1.0-alpha.16
+  - @artblocks/abx-indexer@0.1.0-alpha.17
+  - @artblocks/abx-storage@0.1.0-alpha.16
+
+## 0.1.0-alpha.18
+
+### Minor Changes
+
+- 7fec2d7: Off chain, `animation_url` is now a link to this node's route instead of an inlined `data:` URI
+
+  The two URI-valued keys disagreed about the same thing. For on-chain **content**, `image` has always
+  been served as a link to the resolver's route — bytes should not ride inside a JSON document that
+  marketplaces re-fetch on every view — while `animation_url` was inlined as
+  `data:text/html;base64,…`. That is backwards on the rule's own logic: `animation_url` is usually the
+  _larger_ asset.
+
+  Worse, a reserved key's resolved value is repeated verbatim into the `artifacts` listing, so an
+  inlined document shipped **twice** in one response. A 3 MB on-chain HTML artwork meant roughly 8 MB of
+  JSON per metadata fetch, of which the sibling `image` — the small one — contributed a single line.
+
+  And the inline form was already the exception rather than the rule: a code project's `animation_url`
+  has always been the live-view route. Only a project with an explicit `animation` field holding
+  on-chain content took the `data:` path.
+
+  ```jsonc
+  // before                                        // after
+  "image":         "http://node/…/7/image",        "image":         "http://node/…/7/image",
+  "animation_url": "data:text/html;base64,PGh0…",  "animation_url": "http://node/…/7/data/animation_url",
+  "artifacts": [                                   "artifacts": [
+    {"key":"image",         "uri":"http://…"},       {"key":"image",         "uri":"http://…"},
+    {"key":"animation_url", "uri":"data:text/…"}     {"key":"animation_url", "uri":"http://…/data/animation_url"}
+  ]                                                ]
+  ```
+
+  - **The bytes are unchanged and still on chain.** `abx_provenance` still reports
+    `source: inline`/`reader`/`renderer` with `status: 'on-chain'` — the route changes where the bytes
+    ride, not where they live. The route (`/…/data/{field}`, the data plane's own serving route) returns
+    them with the declared Content-Type, and 302s to a durable locator when one exists.
+  - **Locators are untouched.** `url`, `url-template`, and a computed `text/uri-list` still land verbatim
+    on both planes: they are already URIs, and re-hosting one would hide it.
+  - **The on-chain renderer is unchanged** — a contract has no URL space, so `tokenURI` still inlines the
+    document, and that self-contained form is the durability floor. **No contract changed and no address
+    moved.**
+  - **`abx inspect`'s on-chain readout is unaffected**; it reads the contract's `tokenURI`, not this
+    document.
+
+  Adopts the position the abx-services team argued while upgrading their resolver — theirs already served
+  the route form, so this closes the divergence in their favor and the reference is what changed. The
+  class was invisible to the cross-implementation parity audit, whose fixtures are client-free while the
+  `renderer` representation needs a live `eth_call`; a new `animation-route.test.ts` boots a real server
+  on a real socket and follows the link, because a value promising bytes at a URL is a dead link if
+  nothing serves that URL.
+
+- 7fec2d7: An edition's per-id cap now folds from the log, so a capped edition stops reporting itself as open
+
+  `DefaultMaxSupplySet` — added in the contract-audit release precisely so the log could tell an open
+  edition from a capped one — reached the ABI and stopped there. `reconstruct.ts` had no fold case, so
+  the collection-wide default never landed in `ProjectState`, and **the common shape was the broken
+  one**: `--copies N` sets the cap at `initialize` and never calls `setMaxSupply`, so no id has a
+  `MaxSupplyUpdated` of its own and every capped edition ever deployed folded as _uncapped_. The
+  head-read lane (`listTokens`, which calls `maxSupply(id)`) said `N` the whole time — one field name,
+  two answers, on the value that decides whether a buy button renders. Found by the abx-services team
+  while upgrading their resolver/indexer to this release.
+
+  - **`ProjectState.defaultMaxSupply`** — the collection-wide per-id default (`'0'` = open; `null` ⇒ not
+    an edition). The 1155 analogue of `maxInvocations`.
+  - **`TokenState.maxSupply` is now the _effective_ cap** — an id's own override, else that default —
+    and so equals `maxSupply(id)` on chain and its head-read twin `TokenRow.maxSupply`. Previously it
+    was the override alone, and absent otherwise.
+  - **`TokenState.maxSupplyOverridden`** — whether this id has ever been explicitly overridden. The
+    distinction the on-chain getter cannot express (`maxSupply(id)` returns `0` for both "never capped"
+    and "deliberately closed") and the log now can, plus a signal that the monotonic never-increase rule
+    is in force for that id.
+  - **`editionCapOf(token)`** — new SDK export returning `{kind:'open'} | {kind:'capped', cap} |
+{kind:'closed'}`, so nothing re-derives the rule. Used by the dashboard and `abx tokens`; pass a
+    head-read row and a `'0'` cap reads `open`, which is all a state read can honestly say.
+  - **The dashboard stops lying twice.** It tested `maxSupply` for truthiness: a `--copies 10` id read
+    "(open)", and — because `'0'` is a non-empty string — an id deliberately closed would have read
+    "12 / 0". It now reads "12 / 10" and "12 (closed — no more can be minted)".
+  - **Projection columns**: `projects.default_max_supply`, `tokens.max_supply_overridden` (migration-added,
+    so an existing store keeps working; NULL stays NULL rather than becoming a fabricated `0`).
+
+  Also in this pass, from the same review:
+
+  - **`SPINE_EVENT_DOC` had drifted to 41 of 52 events**, so eleven folded events carried an empty
+    human description and defaulted to Register 2 — including `TransferValidatorUpdated`, which belongs
+    to Register 1, and the factory's `Deployed`. All eleven are described, and a new
+    `spine-doc-coverage.test.ts` fails the build if the table and the spine ABI drift apart again in
+    either direction.
+  - **One provenance body in the resolver's `renderer` branch.** The `text/uri-list` arm hand-built an
+    object byte-identical to `onChainProv(field, 'renderer', …)` — same keys, same order, the note string
+    typed a second time — so the only thing that branch could do was drift from `sourceNote`.
+  - **Dead `abx_params`-era test scaffolding deleted** (a `paramsOf(json) => json.abx_params` reader, an
+    RPC stub, a schema factory), including an import of a `ParamMember` type that no longer exists —
+    which nothing caught, because `tsconfig` includes only `src`, so test files are never typechecked.
+
+### Patch Changes
+
+- Updated dependencies [7fec2d7]
+  - @artblocks/abx-sdk@0.1.0-alpha.15
+  - @artblocks/abx-indexer@0.1.0-alpha.16
+  - @artblocks/abx-storage@0.1.0-alpha.15
+
+## 0.1.0-alpha.17
+
+### Minor Changes
+
+- 1b6b741: Rename "artist" to "creator" throughout, including the protocol vocabulary
+
+  ABX is a tool for creators generally. Art remains a first-class use case, but it should not be baked
+  into the product's framing — and it was, down to the on-chain identifiers.
+
+  **Breaking, and deliberately a clean break** (pre-launch, folded into the one redeploy that four
+  rounds of security remediation already required — deferring would have meant either living with the
+  old vocabulary permanently or spending a second deployment on a word):
+
+  - `AuthOption` is now `Creator`, `TokenOwner`, `Address`, `CreatorOrTokenOwner`, `CreatorOrAddress`,
+    `TokenOwnerOrAddress`, `CreatorOrTokenOwnerOrAddress`. Order is unchanged, so the `uint8` values
+    are identical — only the names moved. Users type these: `--schema key:Type:Creator`.
+  - The on-chain collection metadata field keys `artist` / `artist_links` are now `creator` /
+    `creator_links`. These are `bytes32` keys written on-chain and emitted verbatim into every
+    collection's `contractURI` JSON.
+  - CLI flags `--artist` / `--artist-links` are now `--creator` / `--creator-links`. No aliases.
+  - `@artblocks/abx-token-api` renames its `art` module to `content`: `generateArt` →
+    `generateContent`, `artContentHash` → `contentHash`.
+  - `AbxMetadataRenderer.SPEC_VERSION` is **7**, and `isCurrentRenderer` gates on it. A v6 renderer
+    emits a different member key, so it is genuinely behind, not cosmetically so.
+
+  Package CHANGELOGs are left alone on purpose: they record what past alpha versions actually shipped,
+  and rewriting them would make the release history lie about flag names that really were `--artist`.
+
+- 1b6b741: Renderer spec v10 projects four long-reserved keys; edition trust anchors move
+
+  **Renderer spec v10.** Four keys the spec reserved from the start were projected on chain by nothing:
+  `background_color` and `youtube_url` (token), `banner_image` and `featured_image` (collection). A
+  documented reserved key that no surface emits is a hole rather than a saved byte — a creator sets it,
+  observes nothing, and cannot tell whether the tool or the marketplace is at fault. All four now project
+  when their representation is chain-reachable, and are omitted when unset. `isCurrentRenderer` gates on
+  10; a v9 renderer silently drops them.
+
+  **`collaborators` is no longer a reserved key.** It was in the registry, projected by neither plane, and
+  because reserved keys are excluded from the resolver's `artifacts` listing, setting it on chain did
+  nothing observable anywhere. It is now an ordinary creator key — which means it **does** list in
+  `artifacts`. Put a collaborator list in a named artifact (`abx attach`) or in `description`.
+
+  **The resolver's two collection image keys are now symmetric with the renderer.** `featured_image` is a
+  top-level `contractURI` key instead of artifacts-only, and `banner_image` projects for every
+  chain-reachable representation instead of only `url` (an `inline` or `reader` banner used to vanish).
+
+  **Docs now carry the three-list split** — which keys both planes project, which are the off-chain
+  resolver's alone by design (`abx_provenance.status`, operator overlay, effects/live-view, the
+  `artifacts` listing, collection `image` courtesy, `image_data`, off-chain-decode values), and which are
+  not reserved at all. That split is the thing to read before adding a key to either surface: drift on a
+  key both planes _can_ emit is what produced three earlier remediations.
+
+  **Addresses.** The three edition factories move (trust anchors) along with their implementations, and
+  the renderer moves. `AbxEditionLib`, `AbxMetadataLib`, `AbxCodeLib`, `AbxParamsLib`, all three ERC-721
+  factories, the chunk store, the seed source, both minters and both generators keep their addresses.
+  Existing clones keep running their frozen implementations; re-point a live collection at the new
+  renderer with `abx set-renderer` rather than redeploying it.
+
+- 1b6b741: Independent-audit remediation: `abx_provenance` reshaped, `abx_params` removed, hook ABI widened
+
+  An independent adversarial audit of the contracts found no Critical or High issue, no theft path and
+  no cross-project reach — but four Mediums, eight Lows and five architectural notes. Everything is
+  addressed. Consumer-visible changes:
+
+  **`abx_provenance` entries are now `{field, source, note}`.** They lost `onChain`, which was wrong in
+  both directions — a `url` reported `false` although the URL string is stored on chain, while an
+  `inline` value of `"https://…"` reported `true` for a pure pointer — and `verifiedAgainstChain`,
+  which was hardcoded `null` on every entry. `source` says where the bytes came from; whether a value
+  resolves on chain is visible in the value, and that judgment belongs to the reader. The off-chain
+  resolver drops `onChain` for the same reason (it was exactly `status === 'on-chain'`) and keeps
+  `status`, which it can genuinely compute.
+
+  **`abx_params` no longer appears in `tokenURI`.** It was emitted by the on-chain renderer AND the
+  resolver and parsed back by nobody. Params enumerate directly from the contract — `tokenParamKeys`,
+  `tokenParam`, `paramSchemaKeys` — which is canonical, needs no indexer, and is what a chain-only
+  reader should use; a code project's script still receives them through `tokenData`. Traits for
+  marketplaces belong in `attributes`, unchanged.
+
+  **A computed `image` locator now lands verbatim.** A field renderer returning
+  `("text/uri-list", "ipfs://…")` was being data-wrapped into `data:text/uri-list;base64,…`, which no
+  marketplace dereferences. `image` and `animation_url` now share one implementation of the rule.
+
+  **`IAbxTransferHook.onTokenTransfer` gains `operator` and `amount`.** Without them a hook on a
+  shared-supply ERC-1155 cannot tell a real transfer from a zero-amount no-op — which let any address
+  fire the param lifecycle for an id it held no copy of. The token also refuses to notify on
+  zero-amount and self-transfers.
+
+  **`pingURI` is owner-only**, and `paramSchemaHead` / `selectOption` are new: resolving one selected
+  option no longer copies the whole option table on every render.
+
+  `AbxMetadataRenderer.SPEC_VERSION` is 8. Every canonical address moves — every token type is now
+  library-linked, including the two ERC-721 image factories, because the metadata field store was
+  externalized into the new `AbxMetadataLib` to restore EIP-170 headroom before any fix was stacked on
+  top of 187 bytes of margin.
+
+  The CLI now warns when `--copies` meets a holder-writable `--schema`: on an edition, params belong to
+  the id, so every holder shares one value and the last writer wins.
+
+- 1b6b741: Upgrading from alpha.12/alpha.13 — what breaks, in one place
+
+  This release lands the contract-audit branch. It is a **compatibility break with earlier alphas**, which
+  is fine at this stage (greenfield alpha, no backwards-compatibility promise) but is worth having in one
+  list rather than spread across a dozen changesets. Nothing here is a deprecation with a migration
+  window; the old shapes are gone.
+
+  **Every canonical address moved**, and four manifest fields are new (`metadataLib`, `paramsLib`,
+  `codeLib`, `editionLib` — the delegatecalled write-path libraries). Resolve through `getDeployment` and
+  the upgrade is transparent; anything you have _stored_ keyed by a factory address is not. A project
+  indexed from a superseded anchor reads `isCanonical: false` against the new manifest — correct, since it
+  is what a creator sees if they don't redeploy, but it is a data question, not a version bump.
+
+  **The metadata document changed: renderer spec v4 → v9.** If you assemble or assert on it:
+
+  - `abx_provenance` entries lost `onChain` (it was exactly `status === 'on-chain'`, and wrong in both
+    directions) and `verifiedAgainstChain` (hardcoded `null` on every entry). `source` and `status` stay.
+  - The `abx_params` block is gone from **both** lanes. Params enumerate from the contract —
+    `tokenParamKeys` / `tokenParam` / `paramSchemaKeys` — which is canonical and needs no indexer; a code
+    project's script still receives them through `tokenData`.
+  - `artist` / `artist_links` are now `creator` / `creator_links` (reserved on-chain collection field
+    keys), and `AuthOption.Artist*` is `AuthOption.Creator*` (numeric values unchanged).
+  - A computed `image` locator (`text/uri-list`) lands **verbatim** instead of being wrapped into a
+    `data:` URI no marketplace dereferences.
+  - The on-chain renderer no longer duplicates a computed image into `artifacts`. The off-chain resolver
+    still emits the complete listing — that asymmetry is specified, not a bug.
+  - Four long-reserved keys now project on chain: `background_color`, `youtube_url` (token) and
+    `banner_image`, `featured_image` (collection). `featured_image` also becomes a top-level resolver key
+    instead of artifacts-only, and `banner_image` projects for every chain-reachable representation
+    rather than `url` alone.
+  - `collaborators` is **no longer reserved** — projected by neither plane and excluded from `artifacts`
+    by its own reserved-ness, so it did nothing. It is now an ordinary creator key that does list.
+
+  **`tokenData` divergences fixed, so rendered output can change:** a contract-scope `seed` no longer
+  leaks into a token's `tokenData` (the on-chain generator never read one), `seed`'s wire format is always
+  raw 32-byte hex regardless of schema, and `</script` escaping is case-insensitive to match the on-chain
+  generator. Cached renders for affected code projects should be re-derived.
+
+  **Removed:** `paramKeysOf`, `paramSchemaOf`, `paramDataOf` on `AbxMetadataRenderer` — orphaned when
+  params left `tokenURI`. Read the token directly instead.
+
+  **Two hook interfaces widened** (`ConfigurableParams` is extension **v3**; a hook built for the old
+  signature reverts against a v3 token): `IAbxTransferHook.onTokenTransfer` gained `operator` + `amount`;
+  `IAbxConfigureHook.onParamConfigured` gained `dataLength` + `dataBlobAddress`.
+
+  **Additive:** `ParamHooksFrozen` folds into `ParamHooks.locked`; `paramSchemaHead` + `selectOption`
+  replace pulling a whole option table to resolve one index; `readParamHooks`; `abxJs()` / `gunzipScript()`
+  on the generator for piecewise document assembly; and the three ERC-1155 ABIs now carry
+  `MetadataUpdate` / `BatchMetadataUpdate` / `DefaultMaxSupplySet`, which were emitted but not decodable.
+
+### Patch Changes
+
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+- Updated dependencies [f64a31f]
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+- Updated dependencies [1b6b741]
+  - @artblocks/abx-sdk@0.1.0-alpha.14
+  - @artblocks/abx-indexer@0.1.0-alpha.15
+  - @artblocks/abx-storage@0.1.0-alpha.14
+
+## 0.1.0-alpha.16
+
+### Patch Changes
+
+- Updated dependencies [528c6c6]
+  - @artblocks/abx-sdk@0.1.0-alpha.13
+  - @artblocks/abx-indexer@0.1.0-alpha.14
+  - @artblocks/abx-storage@0.1.0-alpha.13
+
+## 0.1.0-alpha.15
+
+### Minor Changes
+
+- afa9dd4: ERC-1155 editions ship with full parity: a Series is many unique tokens (721); an **Edition** is
+  many copies of a token (1155). The creator's word is **copies** — `abx deploy img.png --copies 100`
+  (a single-artwork edition, `open` = uncapped), `abx deploy-series ./art --copies 50` (each image an
+  edition), `abx deploy-code sketch.js --copies 25` (code editions). Without `--copies`, the 721
+  lanes are unchanged.
+
+  Three new canonical contracts twin the 721 lineup — `OneOfOneEdition`, `EditionImage`,
+  `EditionCode` — plus `AbxFixedPriceMinter1155`, a per-id fixed-price sale singleton
+  (`minter configure/buy --token-id [--quantity]`). New owner ops: `mint --token-id --amount`,
+  `transfer --amount`, `set-max-supply` (per-id cap, only ever decreases), `ping-uri` (re-emit the
+  native `URI` event after a re-point). ERC-1155C creator-token enforcement is the same `--721c`
+  opt-in (same validator registry and ERC-165 ids as 721C). Editions announce one new extension
+  (`abx.extension.edition-supply`, per-id supply/cap); everything else — metadata fields, params,
+  royalties, renderer, storage, effects — is the same protocol surface on both standards.
+
+  **Integrator surface (audience line):** additive only. `ProjectState.contractType` gains
+  `'1of1-edition' | 'edition' | 'edition-code'`; `TokenState` gains `supply`/`maxSupply`/`holders`
+  (editions only; `minted` means supply > 0 there); the spine ABI now decodes
+  `TransferSingle`/`TransferBatch`/`URI`/`MaxSupplyUpdated`; `ChainDeployment` gains the four
+  edition anchors (recorded for Sepolia + Base Sepolia, CREATE2-identical); token-api summaries gain
+  an optional `copies` field. No existing export, route, column, or event shape changed.
+
+### Patch Changes
+
+- Updated dependencies [afa9dd4]
+- Updated dependencies [8c254d5]
+  - @artblocks/abx-sdk@0.1.0-alpha.12
+  - @artblocks/abx-indexer@0.1.0-alpha.13
+  - @artblocks/abx-storage@0.1.0-alpha.12
+
+## 0.1.0-alpha.14
+
+### Patch Changes
+
+- d40caf4: Requested by an integrator (abx-services) — the conformance surface now lives in the neutral
+  layer. Five pieces that only token-api or storage exposed before, and that any third-party
+  resolver needs to reproduce the reference behavior byte-for-byte, move into `@artblocks/abx-sdk`:
+
+  - **The generator-document family** (`ABX_JS`, `escapeInlineScript`/`escapeInlineJson`,
+    `buildGeneratorDocument`, `injectTokenDataIntoHtml` — new `src/generator-document.ts`): pure
+    string operations with no resolver-specific behavior, so the SDK, `abx preview`, and any
+    third-party provider now share one definition instead of the CLI importing token-api just for
+    this.
+  - **The registry-dependency family** (`DEPENDENCY_REGISTRY_ABI`, `activeRegistry`,
+    `resolveRegistryDep`, `registryDepUrl`, `dependencyScriptTags`, `URL_BUDGET_BYTES`), merged into
+    the SDK's existing `deps.ts` alongside its registry-pointer logic. `node:zlib` can't come along
+    — SDK core has to stay reachable from a browser bundle — so decompression is now an INJECTED
+    `inflate?: (bytes: Uint8Array) => Uint8Array` threaded through `resolveRegistryDep`/
+    `dependencyScriptTags`; omitting it when a resolved dep actually needs decompressing throws a
+    new typed `InflateRequiredError` naming the fix, rather than crashing opaquely or silently
+    degrading. `@artblocks/abx-sdk/node` gains `nodeInflate` (a one-line `gunzipSync` wrapper) so a
+    Node host wires it in one line; a browser host passes a `DecompressionStream`-based
+    implementation instead. (Merge note: the prior `dependencyRegistryReadAbi` and token-api's
+    `DEPENDENCY_REGISTRY_ABI` declared the identical `getDependencyDetails` entry twice — deduped
+    into one array that also carries `getDependencyScript`.)
+  - **`contentTypeFromPath`** (new `src/mime.ts`): the MIME extension-map lookup, verbatim.
+  - **Gateway resolution, split pure/env** (new `src/gateways.ts`): `resolveGatewayBase` is now PURE
+    (no env read — takes resolved `{ipfs?, arweave?}` overrides) and `gatewayUrlFor` moves alongside
+    it; `gatewayConfigFromEnv()` is the one place that reads `ABX_IPFS_GATEWAY`/
+    `ABX_ARWEAVE_GATEWAY`, kept separate so a host with its own gateway config never has to touch
+    `process.env` through this module at all.
+  - **`exponentialBackoffDelay(attempt, baseMs, capMs)`** (`util.ts`): `min(baseMs * 2^(attempt-1),
+capMs)`, 1-indexed like the existing `linearBackoffDelay`. Prefer it for a sustained rate limit
+    or an overloaded upstream; `linearBackoffDelay` stays right for a one-off transient failure.
+    `service.ts`'s own retry ladder is unchanged (still linear — its rationale comment stands).
+
+  Token-api and storage keep every existing export working, re-exported from the SDK where the
+  implementation moved — no removals, and token-api's own `nodeInflate`-pre-wired wrappers mean its
+  internal call sites (`code.ts`'s document assembly, `deps.ts`'s `depStatusReport`) needed no
+  signature changes at all. The browser-bundle test (`packages/sdk/test/browser-bundle.test.ts`)
+  stays green with all of this now exported from the core index — proof that the injected-`inflate`
+  design actually keeps `node:zlib` out of the bundle.
+
+- d40caf4: Two first-party consumers adopt the backoff/gateway/data-URI helpers hoisted into `@artblocks/abx-sdk`
+  last round, and `mint-page` refuses a 1/1 target instead of scaffolding a page that hangs. Drop-in for
+  everyone — no behavior change in the adoption itself, and the mint-page refusal only fires for a
+  contract type the page never worked against.
+
+  **`token-api`'s chain watcher now calls `exponentialBackoffDelay`/`linearBackoffDelay` instead of
+  re-deriving them inline.** `dueForRetry`'s failed-project retry and the tick loop's repeated-failure
+  delay were the sdk helpers reimplemented by hand; both now call the shared functions, with the exact
+  index mapping (`min(attempts, 8) + 1` into the 1-indexed exponential helper) that reproduces identical
+  delays for every `attempts`/`failures` value — proved by an old-formula-vs-sdk-helper equality table
+  in `packages/token-api/test/watcher-backoff.test.ts` (attempts/failures 0..12, several `baseMs`
+  values, and the cap boundary explicitly).
+
+  **The `mint-page` template's generated app now reads gateway URLs and `data:` URIs through the sdk**
+  (`gatewayUrlFor`/`resolveGatewayBase`/`parseDataUri`) instead of a hand-rolled `ipfs://`-slicing
+  `toGateway` and a hand-parsed comma-split in `fetchJson`. Same output for every input (plain
+  `https://`, empty string, `ipfs://`, `ar://`, base64 and percent-encoded `data:` bodies) — verified
+  byte-for-byte before the swap, and pinned by a new mintpage.test.ts assertion that the emitted
+  `lib/meta.ts` imports the sdk helpers and no longer contains the old hand-rolled body.
+
+  **`mint-page` now refuses a non-Series target.** The generated page reads `maxInvocations`/`paused`
+  and mints through the shared fixed-price minter — a 1/1 (`OneOfOneImage`) has none of that, so pointing
+  `mint-page` at one silently wrote a page that sat on "Loading…" forever with no diagnostic. `cmdMintPage`
+  now probes the same ERC-165 `supportsInterface(IAbxSequentialMint)` `sdk/anchors.ts`'s
+  `isCurrentSeriesFactory` uses, and refuses with a `CliError` pointing at `abx deploy-series --dir
+<folder> --count 1` (matching the existing guidance in `sales.mdx`). A probe that can't run at all (RPC
+  unreachable) is left undecided and does NOT refuse — scaffolding stays usable offline, same tolerance
+  the existing best-effort `name()` read already has.
+
+  Also folded in: `PUBLIC_RPC` (the mint-page template's keyless-RPC table) gains `base` and
+  `base-sepolia` — the toolkit's own default chain was missing from it, so every default-chain deploy
+  needed a manual `--rpc` just to scaffold its own mint page.
+
+- Updated dependencies [d40caf4]
+- Updated dependencies [d40caf4]
+  - @artblocks/abx-sdk@0.1.0-alpha.11
+  - @artblocks/abx-storage@0.1.0-alpha.11
+  - @artblocks/abx-indexer@0.1.0-alpha.12
+
+## 0.1.0-alpha.13
+
+### Patch Changes
+
+- 11fa933: The remaining phases of the simplification refactor that hadn't yet gotten a changeset: the CLI's
+  internal module split, the token-api/effects/mint-page convergence on the SDK, the shipped skill's
+  rewrite for the simplified surface, and a new SDK README.
+
+  - **`abx`'s `main.ts` split into domain command modules** (`commands/{deploy,project,reads,service,
+scaffold,storage}.ts`, shared `output.ts`/`errors.ts`), with one exit-discipline rule
+    (`process.exitCode` + return, or a typed `CliError`, everywhere — bare `process.exit` only at the
+    entry guard, the top-level catch, and the keep-alive SIGINT handler). Purely internal: a 207-fixture
+    byte-diff matrix (every help text, dry-run, error path, and exit code) confirmed identical output
+    before and after.
+  - **token-api / effects / mint-page converge on the SDK**: `@artblocks/abx-storage` gains one
+    `resolveGatewayBase` (`readiness.ts`), replacing three near-identical copies (two in token-api, one
+    inline in storage itself); token-api exports `buildGeneratorDocument` so the CLI's `abx preview`
+    consumes the real generator-document assembler instead of a hand-kept duplicate; the effects runner
+    now resolves its config via the SDK's `readEnv` and gets a `makePublicClient` fallback transport, so
+    `ABX_RPC_URL` accepts a comma-separated failover list like every other RPC var; the scaffolded
+    mint-page app now imports ABIs from `@artblocks/abx-sdk/abi` and a browser-safe `makePublicClient` +
+    typed `readSaleConfig` instead of hand-rolled fetch/decode, and pins its generated `package.json` to
+    the SDK's _resolved_ version via a new `@artblocks/abx-sdk/package.json` export (alpha version
+    counters diverge per package under changesets, so pinning the CLI's own number could produce an
+    unsatisfiable range).
+  - **The shipped skill (`.claude/skills/abx-self-host/`) is rewritten for the surface phases 0–5
+    actually shipped**: every warning made obsolete by an enforcement is deleted rather than softened —
+    predict-only deploy-preview addresses, the `approvals N` line, the single `ABX_REMOTE_SELF_*`
+    credential grammar, `doctor`'s version/provenance ladder, `storage show --check`, the render/storage
+    combo validator's dry-run row, and `ABX_DEPLOYER_PK` as the only key name. Retired names swept from
+    `dev-loop-test`, the agent-eval scenarios, and spec prose. The skill ships bundled inside this CLI
+    package (co-versioned via `SKILL.md` frontmatter), so it rides this same patch.
+  - **New `packages/sdk/README.md`**: what the SDK is, the send-injection model (`PreparedTx` +
+    `SendTx`, `makeHotSender` for a hot key, bring-your-own for a wallet/multisig), a complete
+    deploy → upload → mint → read walkthrough against real exports, and browser-use notes (explicit
+    `rpcUrls`, no env, the `/node` subpath is Node-only). Included in the npm tarball automatically
+    (README is one of the files npm always packs, regardless of the `files` allowlist).
+
+- Updated dependencies [11fa933]
+- Updated dependencies [11fa933]
+- Updated dependencies [11fa933]
+- Updated dependencies [11fa933]
+  - @artblocks/abx-sdk@0.1.0-alpha.10
+  - @artblocks/abx-storage@0.1.0-alpha.10
+  - @artblocks/abx-indexer@0.1.0-alpha.11
+
+## 0.1.0-alpha.12
+
+### Patch Changes
+
+- df298d8: Fix three ways the reference resolver misreported on-chain state — and the head-read bug underneath one of them
+
+  From an engineering audit by the abx-services team (2026-08-04), who run the same protocol on a
+  hosted node against real testers and so reach long-tail states a single-node run rarely does. All
+  three findings reproduced. Verifying the second one turned up a fourth defect that was its actual
+  cause, and that one is the most consequential of the set.
+
+  **1 · A renderer-computed TEXT field was dropped entirely.** `resolveImage` had an `R.renderer`
+  branch; `resolveText` did not. So a `renderer`-represented `description`, `external_url`,
+  `animation_url`, `background_color`, `youtube_url`, or `name` matched no branch and resolved **as if
+  unset** — silently replaced by the operator's off-chain value with provenance reporting `off-chain`,
+  or omitted from the metadata altogether. A creator who committed a computed field on-chain got the
+  operator's version served instead, and nothing errored anywhere.
+
+  `resolveText` now mirrors `AbxMetadataRenderer._appendText`'s `R_RENDERER` arm exactly, because the
+  two must agree: with `tokenURIRenderer` set the chain assembles this JSON and the resolver merely
+  re-serves it, so any difference is a resolver contradicting the token's own `tokenURI`. That means
+  the **declared** contentType is used verbatim (`renderer` is the one representation that types itself
+  on-chain) rather than an assumed `text/html`, and a `text/uri-list` result (RFC 2483 — the canonical
+  generator's directory branch) lands as the locator it is, never data-wrapped. This is a deliberate
+  divergence from the shape the audit recommended (pointing at the node's own `/data/{field}` route):
+  parity with the on-chain renderer is the stronger constraint here. A field renderer that reverts now
+  degrades that one field — with provenance saying the on-chain attempt failed, not a clean
+  `off-chain` — instead of being indistinguishable from an unset field.
+
+  **2 · The `name` fallback asserted an ERC-721 `name()` read it had not performed.** When
+  `state.name` is null the served value is the raw contract address, and the note still said
+  `on-chain (ERC-721 name() + #id)`. A hosted node served `"name": "0xb844…c35e56 #0"` beside that note
+  while the contract's `name()` was `"ABXdoku"`. The wrong name is cosmetic; provenance is the surface
+  you would point an artist at to audit their own metadata, so a false positive there costs more. The
+  note is now conditional, and deliberately does not adjudicate _why_ the value was empty — the
+  projection cannot tell an unnamed contract from a failed read, and guessing is how the original note
+  came to lie.
+
+  **3 · The live view answered "not a code project" for a code project that was merely mid-index.**
+  `/a/` collapsed every `resolveLiveView` null into one confident verdict about the **contract**, when
+  at least one is a statement about the **index**: `chunkCount` is a head read, so a template-mode
+  project whose chunks have not been folded in yet reads as zero. A tester got
+  `live · caught up · 127 events · 32 tokens` from the node and this 404, concluded the resolver did
+  not recognise the SeriesCode factory, and a `--full` re-index did not clear it — the confident
+  wording sent them looking in the wrong place. The route now consults `contractType` (folded from the
+  deployed extensions, so it knows before any code lands) and answers **503 + Retry-After** for "not
+  yet" versus 404 for "not ever". Both verdicts are answered before the chain client is touched, since
+  neither needs an RPC. The three-way decision is extracted as `liveViewAvailability(state)` so it has
+  a test seam at all.
+
+  **4 · The head-read multicall failed _whole_ on the flagship lane, and took identity, trust, and the
+  URI lane with it.** This was not in the audit — it is why finding 2 fires, found by reproducing it
+  instead of accepting "an RPC hiccup". `applyHeadReads` batched `name`, `symbol`, `owner`,
+  `contractURI`, `isAbxClone`, `implementation`, the four URI-config getters, and **one `tokenURI` per
+  token** into a single multicall. A multicall is one `eth_call`: on a fully-on-chain project
+  `tokenURI(id)` assembles the entire metadata document on-chain, so a handful of those legs exceeds a
+  public node's budget and _every_ leg in the aggregate reports failure — including legs that answer
+  fine alone.
+
+  Measured on Base Sepolia `0xB844F4D2137a8Ce785Cbc80D281A36DBD1c35E56` (32 tokens, chain-complete):
+  1 tokenURI leg → 5/5 succeeded; **4 legs → 0/8 succeeded**, while `name()` on its own returned
+  `"ABXdoku"`. Every resolver indexing that collection therefore believed it had no name, no symbol,
+  no `contractURI`, no canonical proof — and **no `tokenURIRenderer`, i.e. that it was not in the
+  on-chain-URI lane at all.** Deterministic for any sizable on-chain collection, not a hiccup.
+
+  Reads are now split by cost class: the cheap fixed-size ones that decide a project's identity and
+  lane go in a batch of their own and can never be collateral damage, while the unbounded ones
+  (`contractURI`, per-token `tokenURI`, script chunks) read in small chunks through a helper that
+  re-asks a failed chunk one leg at a time before believing it. After the fix, that same contract
+  reconstructs with its name, symbol, both URI renderers, and all 32 token URIs intact.
+
+  12 regression tests across the four, including the null-name case both surfaces missed because every
+  parity fixture on both sides hardcoded a non-null name.
+
+- Updated dependencies [df298d8]
+- Updated dependencies [df298d8]
+- Updated dependencies [df298d8]
+  - @artblocks/abx-sdk@0.1.0-alpha.9
+  - @artblocks/abx-storage@0.1.0-alpha.9
+  - @artblocks/abx-indexer@0.1.0-alpha.10
+
+## 0.1.0-alpha.11
+
+### Patch Changes
+
+- Updated dependencies [e325b46]
+  - @artblocks/abx-sdk@0.1.0-alpha.8
+  - @artblocks/abx-indexer@0.1.0-alpha.9
+  - @artblocks/abx-storage@0.1.0-alpha.8
+
+## 0.1.0-alpha.10
+
+### Patch Changes
+
+- Updated dependencies [1b50f9d]
+- Updated dependencies [1b50f9d]
+  - @artblocks/abx-sdk@0.1.0-alpha.7
+  - @artblocks/abx-storage@0.1.0-alpha.7
+  - @artblocks/abx-indexer@0.1.0-alpha.8
+
+## 0.1.0-alpha.9
+
+### Patch Changes
+
+- 1158420: Fixes from a parallel cold-agent sweep: a chain typo no longer crashes every command, and `inspect` stops over-promising on hand-written PRNGs.
+
+  **An unknown `ABX_CHAIN` printed a raw Node stack trace — from every command.** Chain-derived values
+  were resolved at module scope, in `token-api` (which the CLI imports) and in the CLI itself, so the
+  throw happened during module evaluation, before `main()` existed to catch it. `ABX_CHAIN=mainnet abx
+doctor` dumped an internal source path and exited 1 — including from the one command whose job is to
+  tell you what is wrong with your environment. Those resolutions are lazy now, and the CLI validates
+  the variable up front with an answer rather than a crash: unknown values list the shipped chains, and
+  a mainnet-shaped value says plainly that ABX is testnet-only today.
+
+  **`abx inspect` reported "(no PRNG)" for a hand-written seeded generator — with the _stronger_
+  reproducibility verdict attached.** The `seeded` check only recognized p5's `randomSeed(`, so a
+  vanilla LCG or xorshift matched no branch and fell through to "traits look derived from the
+  seed/params directly". That is the common case, not an edge one — the skill's own canonical
+  dependency-free example hand-rolls an LCG, and all three sketches written by agents in the sweep hit
+  it. A hand-rolled generator now gets the `careful` verdict and is told the truth: deterministic and
+  reproducible on-chain, but only by porting that exact generator and call order into Solidity.
+
+  Also: `--yes` is now documented in `deploy-code --help` (its own placeholder-identity refusal already
+  told you to pass it), and the `--onchain-uri` raster warning now names the two routes that actually
+  deliver a no-server image instead of only one.
+
+  Found by the 2026-08-03 parallel sweep (8 cold Sonnet/Haiku agents, isolated sandboxes).
+
+- Updated dependencies [1158420]
+- Updated dependencies [1158420]
+- Updated dependencies [1158420]
+  - @artblocks/abx-sdk@0.1.0-alpha.6
+  - @artblocks/abx-indexer@0.1.0-alpha.7
+  - @artblocks/abx-storage@0.1.0-alpha.6
+
+## 0.1.0-alpha.8
+
+### Minor Changes
+
+- feba8c2: A resolver is no longer an object store: effect outputs split into **bound** and **referenced**
+  (`specs/protocol/effects.md → Bound vs referenced`), and the artifact registry enforces the split.
+
+  An output is **bound** iff a binding stitches its _content_ into the metadata JSON (today exactly
+  `render/traits` → `attributes`); everything else is **referenced** — the projection carries its URL,
+  or it only appears in the `artifacts` manifest. That one distinction decides who holds the bytes, and
+  it is now the wire rule rather than a runner constant.
+
+  - **`POST /v1/effect-artifacts` derives the mode from the binding, and refuses both mismatches.**
+    Bytes for a referenced output → `400` (the resolver redirects either way, so the bytes buy no
+    capability and cost it storage, retention and egress). A locator for a bound output → `400` (its
+    content is assembled into `tokenURI`; a pointer there used to be recorded and then silently never
+    stitch — a wrong answer served confidently). Bound content is capped at **64 KB**, and a locator
+    that only the producer could resolve (loopback/private host, presigned expiring URL) is rejected.
+    The resolver never fetches a locator while handling the write, and serves registered locators by
+    `302` — never by proxying.
+  - **Bound content moved out of byte custody** into the artifact row (`effect_artifacts.bytes`). Two
+    distinct rules, deliberately not one: a node **MUST** serve and stitch bound content only at the
+    token's current settled `inputsHash`, and it **MAY** drop superseded content whenever it likes
+    (nothing may read it, and it is re-creatable). The reference drops eagerly, on each bound
+    registration, so it holds at most `64 KB × minted × bound outputs` — but retention is a service
+    policy, not an obligation. Either way "conforming means holding a bounded amount of JSON in the
+    database you already run" is now literally true: a resolver in the publish topology needs no object
+    storage at all.
+  - **`abx-effects-publish/v1` is gone** (not deprecated): the two routes ride `abx-control-plane/v1`.
+    Once referenced output is locator-only, accepting a registration is a database insert, so the
+    capability flag described a distinction that no longer exists. A service that won't take a caller's
+    artifacts refuses on the credential (`403`) — interfaces describe wire grammar, tokens describe
+    permission. The interface ids are also explicitly **all-or-nothing**, and the conformance fixture
+    now checks that every route a declared interface names actually answers.
+  - **The runner declares bound outputs** (`EffectOutputDecl.bound`), refuses to start when it has a
+    publish token but a backend that can't name a locator, preflights the descriptor + credential
+    before spending a render, and **latches** on a permanent (4xx) publish failure instead of
+    re-rendering every sweep forever. Skips now re-register rows, so a transient publish failure heals
+    without a re-render.
+  - **The CLI refuses the impossible combination up front**: `abx render --remote`, `abx effects`
+    against a remote resolver, and `abx deploy-effects` all require a backend that can name a reachable
+    URL — `cloud` (S3/R2 + public base), `ipfs`, or `arweave`, named as **peers**. Derived output is
+    re-creatable, so the protocol has no preference among schemes: a chosen `https://` gateway or
+    bucket URL is exactly as legitimate as `ipfs://`/`ar://`, and reachability — not durability — is
+    the requirement. Rendering **co-located** with the resolver remains fully supported on any backend,
+    including `fs`.
+
+  Breaking for producers that relied on pushing media bytes to a resolver: publish a locator instead,
+  or co-locate. Breaking for clients that read `abx-effects-publish/v1` from a descriptor.
+
+### Patch Changes
+
+- Updated dependencies [feba8c2]
+  - @artblocks/abx-sdk@0.1.0-alpha.5
+  - @artblocks/abx-indexer@0.1.0-alpha.6
+  - @artblocks/abx-storage@0.1.0-alpha.5
+
+## 0.1.0-alpha.7
+
+### Minor Changes
+
+- 67b686b: `abx contracturi`, and the read plane stops answering a bare 404 to three different problems.
+
+  Both halves come from one real failure: an agent driving a hosted resolver wanted collection
+  metadata, pattern-matched off `/t/{chainId}/{address}/{id}`, dropped the token id, got a bare `404`,
+  and reported the service as broken. The documented route (`/c/{chainId}/{address}`) was right there —
+  but there was also no command to just _ask_, and the 404 gave it nothing to correct.
+
+  - **New `abx contracturi <address>`** — the collection-level counterpart of `tokenuri`. Reads
+    `contractURI()` (ERC-7572) from the contract, **follows it**, and decodes: a `data:` URI inline
+    (the on-chain lane), an `https://` URL by fetching it (the off-chain lane). A contract commits its
+    own metadata base on-chain (`contractURIBase`), so the chain — not a doc, not a service
+    descriptor — is the authoritative answer to where a project's metadata lives. Nobody needs to
+    hand-build a resolver URL. When the fetch fails, the message says so plainly: the URL came from
+    the chain, so a bad status is about the _service_ (unregistered project · wrong chain · down),
+    never a mistyped path.
+  - **Read-plane responses now carry a machine `code`**, so the three causes of "no metadata came
+    back" are distinguishable — they were one indistinguishable `{"error": "…"}` `404`:
+    - `400 invalid_request` — a real route, wrong shape. Names the correct template, and carries
+      `didYouMean` when the fix is obvious (a `/t/…` missing its token id → `/c/{chainId}/{address}`).
+    - `404 unknown_route` — this node serves nothing at that path; the body lists what it does serve.
+    - `404 not_registered` — the path and chain were fine; this node doesn't index that contract.
+    - `400 unsupported_chain` — wrong chain, plus the `chains` this node does serve. Was a bare `404`;
+      now matches what the control plane already answered for the same condition.
+  - `ServiceErrorCode` gains `unknown_route`. The spec's Errors section now covers the read plane too,
+    with a **MUST** on distinguishing the three misses — and an explicit **MUST NOT** on treating
+    route templates as per-node discoverable configuration. The route grammar is fixed by the
+    `abx-token-api/v1` interface; these responses are diagnostics, not a discovery mechanism.
+  - **The conformance fixture checks all of it** (`pnpm conformance <base-url>`), so any provider can
+    self-verify in one command. Also fixed: the documented `pnpm conformance -- <base-url>` form
+    parsed `--` as a flag and swallowed the base URL, printing usage instead of running.
+
+### Patch Changes
+
+- Updated dependencies [67b686b]
+  - @artblocks/abx-sdk@0.1.0-alpha.4
+  - @artblocks/abx-indexer@0.1.0-alpha.5
+  - @artblocks/abx-storage@0.1.0-alpha.4
+
+## 0.1.0-alpha.6
+
+### Minor Changes
+
+- a72723d: A standard indexing lifecycle, and registration that no longer blocks on a slow chain RPC
+  (specs/self-host-toolkit/remote-services.md → The indexing lifecycle).
+
+  - **Fixed: a slow register triggered a retry storm.** The SDK's per-attempt timeout (30s) plus its
+    retry ladder meant a cold reconstruct that outran one request was **re-POSTed up to four times**,
+    each starting another full replay against the RPC that was already too slow to answer — and the
+    caller then saw "nothing responded" even though the registration was durable and indexing was
+    underway. A timed-out register now asks whether it landed (a status read) instead of re-POSTing, and
+    the resolver coalesces concurrent catch-ups for one project into a single run.
+  - **`POST /v1/projects` answers in two conformant shapes, discriminated by HTTP status:** `200` with
+    the completed summary, or `202` + `{accepted, project: {status}}` when catch-up is deferred. The
+    registration is normatively **durable before catch-up** and visible on the list immediately, so a
+    flaky RPC makes for a slower backfill rather than a lost add. No `?wait=`/`Prefer:` negotiation — the
+    status code is the discriminator, and clients handle both. The reference resolver answers _by
+    deadline_ (`ABX_REGISTER_DEADLINE_MS`, default 8s): the common case (a fresh deploy) stays
+    synchronous with real counts; only the pathological case defers.
+  - **Closed lifecycle enum + error classes, on the status and list routes:**
+    `queued | backfilling | live | stale | failed`, plus credential-free
+    `error.class ∈ {rpc_unavailable, rpc_rate_limited, not_abx_contract, internal}` (fixed per-class
+    messages, never a scrubbed upstream string). Status gains top-level `headBlock` (so lag / % complete
+    is computable without knowing a service has a watcher) and `attempts`; the list carries `status` +
+    the error class, so a client renders "3 live, 1 backfilling, 1 failed (rpc_rate_limited)" in one
+    request. SDK: `IndexStatus`, `IndexErrorClass`, `isAccepted()`, `indexProgress()`,
+    `classifyIndexError()`, and `AbxServiceClient.awaitIndexed()` — one wait loop for the CLI, the
+    effects runner, and any hosted agent.
+  - **The same five words on your own node.** `abx status [address] [--remote [name|url]] [--watch]`:
+    bare is the node summary (now with each project's state), an address gives lifecycle + scan floor +
+    blocks-indexed-vs-head + cause, and `--remote` asks a service. (`status` = who is serving it and how
+    fresh; `state` = what the chain says. Both `--help` texts now say so.)
+  - **New observability the self-hosted node never had:** the chain watcher marks projects `stale` when
+    it falls far behind head or its ticks keep failing (previously visible only in the node's log),
+    re-queues a backfill interrupted by a restart (previously left registered-but-empty until a manual
+    `abx index`), and retries a `failed` catch-up on exponential backoff instead of hammering a
+    rate-limited RPC every tick. Lifecycle rows live in their own table: they survive a projection wipe
+    and are never clobbered by a re-add.
+  - **CLI:** `abx add|index --remote` prints `registered — backfilling…`, polls to `live`, then prints
+    the same summary a synchronous service would have given; `--no-wait` returns at the 202 and names
+    the command to check later. A post-op nudge (`ownerops`) never blocks on someone else's backfill.
+    A caught-up project with **0 events** now warns instead of printing ✓ (a real ABX clone always emits
+    a spine, so zero means wrong chain/floor or an RPC that didn't serve the logs).
+  - **Conformance fixture** accepts either register shape, asserts durable-before-catch-up, lifecycle
+    membership, `headBlock`, that a deferred catch-up actually reaches `live`, and that no error message
+    carries a URL.
+  - Fixed `scripts/mock-remote-service.mts`, which imported the token API by a path that resolved
+    against `scripts/` and could silently fall back to a _published_ build outside the repo — the
+    fixture was testing the last release instead of the working tree. The fixture also re-points
+    scenarios by their fixture header now, so a new one can't keep a dead contract address.
+
+  Found by a cold-agent sweep over the above (10 parallel clean rooms, haiku + sonnet) and fixed here:
+
+  - **`abx status --remote <name>` with no address** parsed the flag itself as the address and sent it
+    as a URL path segment.
+  - **A register whose catch-up already failed** was announced as "registered — failed (…is catching
+    up…)", and with `--no-wait` it exited 0 and then claimed the provider "now serves" the project. A
+    known failure is now an error in both lanes — there is nothing left to wait for.
+  - **A `failed` status said what broke but not whose problem it was.** Both the failure error and
+    `abx status` now carry a per-class action line ("the SERVICE can't reach its chain RPC — not your
+    key, address, or chain…"), plus a `follow` line naming `--watch`, so a red word isn't a dead end.
+  - **A `live` project showed a misleading completion percentage.** `toBlock` only advances when a
+    project has _events_, so a fully current project on a busy chain read as `2/202 (0%)`.
+    `indexProgress()` now returns a ratio only while `backfilling`; `live` reads "caught up", `stale`
+    reads "not tracking head right now".
+  - **`--remote-token` was misattributed on a 401** — the error blamed `ABX_REMOTE_<NAME>_TOKEN` even
+    when the caller passed an override, making the override look ignored at exactly the moment someone
+    is testing a replacement key.
+  - **`not_registered` on a read** (status/reindex) now names the register command instead of echoing a
+    404, and a 5xx carrying a failure `class` becomes a wait-vs-broken error.
+  - **`abx verify`'s summary** read `✓ 0/1 up to date` for a project with no off-chain renders at all —
+    "zero of one succeeded" to two independent reviewers. It now says "nothing to render for this
+    project", and otherwise leads with polarity ("N of M token(s) current").
+  - **`abx doctor` now reports named remotes** and flags a credential stored under a name the CLI does
+    not read (`ABX_REMOTE_<NAME>_KEY`). That fault presents as "it acts like I never gave it a key" and
+    previously only surfaced from `abx remote <name>` — which a creator reaches _after_ doctor.
+  - **Skill: the `npx --no-install abx version` probe was documented as failing cleanly.** It doesn't —
+    npm will run any `abx` binary already in the npx cache, which in a real sweep reported a months-old
+    build as the project's CLI (and if a plain `npx abx` ever ran on that machine, the bare name is a
+    squatted package). The skill now probes `./node_modules/.bin/abx` directly.
+  - Also documented: how a multi-word provider name folds into `ABX_REMOTE_<NAME>_*`, and what
+    `watching: no` means on a status readout.
+
+  A second sweep round over those fixes caught three more, including one the first round's fix created:
+
+  - **`abx verify --remote` never checked byte integrity at all** — both of its lanes only ask "is there
+    a current render / is this a placeholder", and a green ✓ from that was standing in for "the served
+    bytes match the on-chain commitment". A reviewer hit the worst version of this: `--remote` (the form
+    the skill tells you to use for a hosted project) reported ✓ on a token whose bytes genuinely did NOT
+    hash-match, while bare `abx verify` on the same project reported `✗ keccak256 MISMATCH`. It now calls
+    the service's own purpose-built `GET /api/project/:addr/verify` (which holds both the bytes and the
+    chain) and reports that verdict separately from the render summary — and when it _can't_ run that
+    check (no credential, older node) it says "byte integrity NOT checked" instead of leaving a ✓ to
+    imply it passed. The remedy names both real causes (an unbridged durable locator vs. bytes that only
+    exist on the creator's machine, which a hosted resolver can never serve).
+  - **`abx verify` exited 0 while printing a byte MISMATCH**, in both lanes — nothing could gate on it.
+    An integrity mismatch now fails the command; a missing render or placeholder is a normal state and
+    still exits 0.
+  - **`abx add --dry-run` silently ignored the flag and performed the registration**, local or remote.
+    It now refuses and names the read-only commands (`abx state`, `abx status`) instead. Silently doing
+    the thing when the caller asked to preview is the one outcome that must never happen.
+  - **`PRAGMA busy_timeout` was set third in the store schema**, after the WAL switch it needs to
+    protect — so two processes opening the same store at once (parallel CLI runs, or a co-located
+    effects runner starting alongside the resolver) could fail outright with `database is locked`
+    instead of waiting the moment out. It is now the first statement.
+
+  A third round, re-running the scenario that found the verify bug (it now catches it) turned up:
+
+  - **`abx add --remote` ended on "it now serves <url>"** — true about indexing, silent about whether
+    the bytes are right, and two reviewers stopped there and reported a blank page as fixed. It now names
+    the byte check (`abx verify <addr> --remote <name>`) in the same breath.
+  - **`canonical:` collapsed a tri-state.** `isCanonical` is `true | false | null`, and both readouts
+    printed "unverified" for the last two — so "the chain says this is NOT a clone of the configured
+    factory" (a trust finding) looked identical to "the check never ran" (no factory on this chain, normal
+    on a dev chain). Two reviewers read the collapsed word as a second failure sitting next to a real one.
+  - **`abx verify --remote` gave a bare `fetch failed`** for an endpoint that was down, where
+    `abx status --remote` names the host and asks whether it's running. Two commands, one condition, two
+    error qualities — now consistent.
+  - `abx status <addr>` printed the address twice when the project has no name.
+  - Skill: registering with a provider on **their** hostname vs. a domain you control decides whether
+    leaving later costs a transaction — now stated in the managed-provider section, before you bake it.
+
+### Patch Changes
+
+- Updated dependencies [a72723d]
+  - @artblocks/abx-sdk@0.1.0-alpha.3
+  - @artblocks/abx-indexer@0.1.0-alpha.4
+  - @artblocks/abx-storage@0.1.0-alpha.3
+
+## 0.1.0-alpha.5
+
+### Minor Changes
+
+- 3745bd3: Remote services are first-class: a provider-neutral control plane, named remotes, and a service
+  descriptor (specs/self-host-toolkit/remote-services.md).
+
+  - **Control plane moves to `/v1`** (hard cutover; `/admin/*` is gone — redeploy self-hosted nodes):
+    `POST/GET /v1/projects`, `DELETE|reindex|status /v1/projects/{chainId}/{address}`,
+    `POST /v1/effect-artifacts|effect-status`. `chainId` is explicit and validated everywhere; every
+    error carries a machine `code` (`unauthorized` 401 · `forbidden` 403 · `unsupported_chain` ·
+    `not_registered` · `disabled`) replacing the old prose-sniffed 404. One bearer guard replaces the
+    four inline copies; OPTIONS preflight now answers so browser clients can send `Authorization`.
+  - **`GET /.well-known/abx-service`** — the public service descriptor: `interfaces` (present iff
+    actually enabled), `chains`, `auth` (with optional provider-set `signupUrl`/`docsUrl` via
+    `ABX_SERVICE_*` env), and `render.attached` (managed rendering, probed from the runner's
+    `/health`) — so an agent can match a project to a provider before registering.
+  - **Named remotes in the CLI**: `--remote <name>` reads `ABX_REMOTE_<NAME>_URL`/`_TOKEN`
+    (a managed provider's per-account key — never falls back to `ABX_RESOLVER_ADMIN_TOKEN`);
+    `--remote <url> [--remote-token <t>]` for ad-hoc targets; bare `--remote` stays the self-host
+    default. New `abx remote [name|url]` inspects a service's descriptor and the projects a token
+    sees. `migrate --from/--to` accept names; only the destination needs a credential.
+  - **The SDK gains its first HTTP surface**: `AbxServiceClient` (endpoint + injected bearer, retry
+    on 5xx/network, immediate typed `AbxServiceError` on 4xx) — shared by the CLI and the effects
+    runner's publish lane. `envSuffix()` is the shared env-name normalization.
+  - **Conformance fixture**: `pnpm conformance -- <base-url> [--token …]` self-verifies any
+    implementation; the e2e suite runs it against the reference container.
+
+### Patch Changes
+
+- 3745bd3: Membrane fixes found by a 20-run cold-agent regression sweep (sonnet + haiku, black-box clean rooms).
+
+  - **A 500 no longer leaks the node's own credentials.** An upstream RPC failure surfaced viem's
+    message, which embeds the endpoint URL — and a keyed RPC URL _is_ a credential, so on a
+    multi-tenant provider any tenant who could provoke a 500 got the operator's RPC key. The cause now
+    goes to the node's log; the wire gets a generic message, an `internal_error` code, and a
+    credential-free hint about the failure class. Normative in the remote-services spec.
+  - **The service client no longer discards a 5xx body.** The service's own words survive the retry
+    ladder, and an exhausted ladder says "failed — last response …" rather than mislabelling a
+    server that answered as "unreachable". The descriptor probe drops to 2 attempts, so a typo'd
+    provider URL fails in ~1s instead of grinding 5s, with distinct "nothing responded" vs
+    "answered, but serves no descriptor" messages.
+  - **Conflicting duplicate `.env` keys are reported.** First-wins is unchanged, but a stale second
+    `ABX_RPC_URLS_<CHAIN>` line silently pointed the CLI at another network while every check read
+    green — the symptom surfaced far away as "no contract at that address". Only genuinely
+    _conflicting_ duplicates warn (identical repeats stay quiet).
+  - **"No contract at …" errors now name the endpoint they asked** (redacted), because a chain key
+    can't distinguish two RPCs that both claim it.
+  - **A misnamed remote credential is called out.** `ABX_REMOTE_<NAME>_KEY` (or `_API_KEY`, `_SECRET`)
+    is not read, so it previously reported as "no token" while the value sat in `.env`; both
+    `abx remote` and the register path now name the near-miss and the correct `_TOKEN` name.
+  - **`--dry-run` explains a missing trust anchor instead of crashing.** On a chain where the
+    configured factory has no code, `deploy`/`deploy-series` previews died inside
+    `predictDeterministicAddress` with a raw `returned no data ("0x")`; they now report it the way
+    `abx predict` and a real deploy already did, and name the two ways forward. The keyless
+    `--for` requirement also fails fast instead of after several steps of output.
+  - **The placeholder-identity guard is one shared predicate** across all three deploy commands
+    (it was copy-pasted, and one copy's comment claimed coverage it didn't have), pinned by a new
+    regression test: a real send refuses tool defaults, a preview only warns.
+  - **The served dashboard's empty state no longer prints `pnpm abx demo`** — a contributor-only
+    invocation on a page a published user sees.
+
+- Updated dependencies [3745bd3]
+- Updated dependencies [3745bd3]
+  - @artblocks/abx-sdk@0.1.0-alpha.2
+  - @artblocks/abx-indexer@0.1.0-alpha.3
+  - @artblocks/abx-storage@0.1.0-alpha.2
+
+## 0.1.0-alpha.4
+
+### Patch Changes
+
+- 4074766: Fix the dashboard's block-explorer links, which were hardcoded to `https://sepolia.etherscan.io`. Every
+  link on the page — contract, owner, implementation, each event's tx — pointed at Ethereum Sepolia no
+  matter which chain was being served, so a dashboard for a normal `abx demo` (Base Sepolia by default)
+  sent you to an explorer where the contract does not exist. The SDK now derives the explorer from viem's
+  own chain metadata (`explorerUrl`/`chainById`), so adding a chain brings its explorer along and no
+  hand-maintained table can drift. The CLI's separate copy of that table is collapsed into the same
+  helper; `signer.ts` was already doing it correctly.
+
+  Drop the demo's opening "trust anchor" step. It asserted that only the canonical factory can make a
+  token that _is_ an ABX token, which is false — anything following the protocol's event spine is an ABX
+  token, and the factory is one route to that, not the definition. The same overclaim in the index step
+  ("verified real") now reports the fact instead: made by the canonical factory, or not. The demo opens
+  on the renderer step, and resolving the factory no longer prints a line of its own there.
+
+- Updated dependencies [4074766]
+  - @artblocks/abx-sdk@0.1.0-alpha.1
+  - @artblocks/abx-indexer@0.1.0-alpha.2
+  - @artblocks/abx-storage@0.1.0-alpha.1
+
+## 0.1.0-alpha.3
+
+### Patch Changes
+
+- Updated dependencies [c21ea30]
+  - @artblocks/abx-indexer@0.1.0-alpha.1
+
+## 0.1.0-alpha.2
+
+### Patch Changes
+
+- afb36a3: Fix three bugs that made the documented first run (`abx demo`) look broken.
+
+  **A 0-event index was reported as success, and served.** `eth_getLogs` is
+  read-after-write inconsistent on load-balanced RPCs: `waitForTransactionReceipt`
+  resolves against a node that has the block, then the log query lands on one that
+  doesn't yet and returns nothing for a block we _know_ contains our deploy. The CLI
+  took that single read at face value, printed `✓ reconstructed 0 events`, stored the
+  empty projection and served an empty dashboard — no events, no token, nothing to
+  look at. This reproduced 100% of the time against `https://sepolia.base.org`, which
+  is the **default endpoint when there is no `.env`** — so the documented first run
+  was the path that broke. Every post-deploy index (`deploy`, `demo`, `deploy-series`,
+  `deploy-code`, `add`) now re-scans with backoff instead of trusting one read, since
+  having just minted means the spine cannot legitimately be empty. If it still comes
+  back empty, that is now reported as a failure naming `abx index <addr> --full` as
+  the recovery, rather than dressed up as a ✓.
+
+  **The demo told you to press a button that does not exist.** It ended with _"Open
+  the dashboard, then hit 'Re-index from chain'"_. The dashboard is read-only —
+  re-index and verify are admin actions that 404 unless the node has an
+  `ABX_RESOLVER_ADMIN_TOKEN` — so that control isn't there to find. It now points at
+  the spine table (which _is_ the reconstruction) and at `abx index <addr> --full` to
+  replay it. The dashboard's own note also stopped printing a **shortened** address
+  inside a copy-pasteable command, and no longer suggests `--remote` for a local node.
+
+  **Re-running the demo crashed after spending a transaction.** With port 8787 already
+  busy — an `abx demo` or `abx serve` in another terminal, i.e. exactly what happens
+  when you run the demo twice — the deploy went through, was paid for, and _then_ the
+  serve step died with an unhandled Node `EADDRINUSE` stack trace. The port is now
+  preflighted before anything irreversible, so it refuses with "Nothing was deployed"
+  and suggests `--port <n+1>`.
+
+  **`abx demo` is now a walkthrough rather than a smoke test.** The docs point a
+  first-time reader here, but it asserted its interesting claims without ever showing
+  them — "reconstructed 9 events — no provider involved" with the events invisible.
+  It now teaches, continuously and without pauses (so agents and CI behave
+  identically): it explains why the trust anchor is the factory and not a spoofable
+  event, names what goes on chain versus what stays a keccak256 commitment, prints
+  the reconstructed event spine with what each event told us (tagged ABX vs plain
+  ERC-721/7572), then **deletes its own local projection and replays it from the
+  deploy block**, comparing a sha256 fingerprint of every chain-derived field to prove
+  it lands on identical state. Finally it reads the token back the way a marketplace
+  would. `abx deploy` is unchanged — it stays terse.
+
+  Adds `Store.dropProjection(address)` / `SelfHostIndexer.dropProjection()`: discard a
+  project's reconstructed projection while keeping its registration, so the next index
+  rebuilds from the deploy block. That's the primitive the rebuild proof needs, and it
+  makes "the projection is a disposable cache" a checkable claim rather than a comment.
+
+## 0.1.0-alpha.1
+
+### Patch Changes
+
+- 48d96c5: Add **`abx preview`** — the studio lane for code projects: run the program on
+  localhost, live, while it's still being made. No chain, no key, no deploy.
+
+  `abx preview --script art.js --schema "palette:HexColor:TokenOwner"` serves a
+  studio on `localhost:8788` — shuffle seeds, drive every declared PostParam from a
+  real typed input (a color picker for `HexColor`, a dropdown for `Select`), read the
+  traits the program actually reported, and `/grid` to see N seeds at once. `/view`
+  is the bare document. The program is re-read from disk on every render, so the loop
+  is edit-and-refresh with no watcher and no restart.
+
+  It serves the **same template-mode document the generator serves** — the real
+  `abx.js`, the real canonical `tokenData` shape, the real dependency script tags —
+  with a synthetic bytes32 seed in place of a minted one, so what you approve is what
+  deploys. There is no second copy of the runtime to drift from. (`@artblocks/abx-token-api`
+  now exports `ABX_JS` and the inline-safety escapes so the CLI can build that exact
+  document rather than reimplement it.)
+
+  `--shoot <dir>` drives the same server headlessly to PNGs plus a `traits.json` and
+  exits — that's how an agent, which can't open a browser, sees what the creator sees.
+  It also flags the two silent killers: no frame reporting traits (⇒ no marketplace
+  `attributes` on any lane) and identical traits across every seed (⇒ the program
+  isn't reading `abx.tokenData.seed`, so the drop mints N identical tokens).
+
+  Why a live server rather than a screenshot sweep: a still flattens every time-based
+  piece, and `abx.done()` exists precisely because stills need a settle point — so a
+  proof sheet of an animated piece is a set of arbitrary frozen frames presented as
+  the work. Frames render into a fixed 1000×1000 viewport and are scaled to fit their
+  slot, so a program that hardcodes its canvas size is never clipped to its own corner.
+
+  Skill: add **Phase 0**, an explicit authoring phase that puts every deploy decision
+  (hosting, thumbnail, traits, storage, wallet, supply, royalties, name/symbol) off
+  the table until the creator says ship, and points at `abx preview` for the loop. The
+  skill previously went straight from "the creator brought an idea" to "pick a deploy
+  lane", so an agent helping someone _design_ a piece front-loaded infrastructure
+  questions while there was still nothing to look at.
+
+  Skill: also teach CLI resolution — probe project-local (`npx --no-install abx`)
+  before global, install `@artblocks/abx-cli` (not `@artblocks/abx-sdk`, which ships
+  no binary), and default to a per-project install. The skill previously assumed `abx`
+  was already on PATH and gave no bootstrap path at all, so agents improvised — one
+  installed the SDK, then went global unprompted.