@artblocks/abx-indexer 0.1.0-alpha.3 → 0.1.0-alpha.30

package/CHANGELOG.md

@@ -0,0 +1,645 @@
+# @artblocks/abx-indexer
+
+## 0.1.0-alpha.30
+
+### Minor Changes
+
+- c198237: Closes the remaining 2026-08-27 w7 agent sweep backlog (B60-B65): a new command, a real behavior
+  change, and several truthfulness/legibility fixes.
+
+  - **`abx remote set <name> --url <url>`** — the third-party twin of `abx auth login`. Installs
+    `ABX_REMOTE_<NAME>_URL`/`_TOKEN` into `.env` for any hosted metadata provider, not just the
+    first-party `abx` remote. The token is read from stdin (piped, or a TTY prompt) — never a
+    command-line argument, never printed — and re-running replaces the pair in place rather than
+    duplicating it. Reuses `auth login`'s own safety rails (symlink/git-tracked/unignored refusal,
+    atomic write) via newly-exported `saveEnvSecret`/`assertPrivateEnvPath`.
+  - **`abx scaffold solidity [<dir>]`** replaces the proposed `scaffold-minter-hook` with one Foundry
+    workspace for ABX's real Solidity extension surfaces. Renderers and configure/transfer/augment
+    hooks remain separate deployable roles; canonical ERC-721/ERC-1155 minters are imported rather than
+    reinvented. The unsafe burn-to-combine example was removed.
+  - **`abx-contracts~2.0.0`** is the canonical Soldeer package boundary (B49): interfaces,
+    implementations, minters and reference hooks ship from the existing contracts source tree, with an
+    exact compatibility version. Generated projects no longer vendor drift-prone interface copies.
+    B50 is resolved without a mock protocol: reference-hook tests deploy a real canonical SeriesCode
+    clone and exercise schema auth, empty-blob refusal, hook ordering and transfers against it.
+  - **`.env` duplicate keys are now last-wins**, matching conventional dotenv tooling instead of the
+    previous (surprising, backwards) first-wins behavior. `parseEnvContent` keeps the last value at the
+    key's original position; the printed warning updated to match.
+  - **`abx state` now says when it can't enumerate PostParams**, instead of silently showing nothing —
+    a non-canonical/pre-enumeration contract used to read as "confirmed no params" when it actually meant
+    "this node couldn't check." New human-readable line + `params.enumerable` in `--json`.
+  - **A throttled progress line during a large `abx add`/`abx verify` scan** — a range-capped RPC's scan
+    could run 15+ minutes with zero output after one line up front. Now prints `… still scanning:
+N/total blocks (X%)` periodically via a new `onChunk` hook threaded through
+    `getLogsAdaptive`→`reconstructProject`/`reconstructIncremental`→the indexer's `reindex()`.
+  - **Three smaller truthfulness fixes**: `abx remote <url>` now flags a loopback descriptor
+    `baseUrl` the same way it already flags an unsupported chain; `configure-param` now notes when the
+    canonical display differs from what was typed (a bare `ff7f50` normalizing to `#ff7f50`, a Select
+    index resolving to its label); and owner-op `--dry-run --json` now emits the prepared transaction,
+    expected signer, signing lane, and simulation result as structured data.
+
+### Patch Changes
+
+- Updated dependencies [c198237]
+  - @artblocks/abx-sdk@0.1.0-alpha.29
+
+## 0.1.0-alpha.29
+
+### Patch Changes
+
+- c5e0d84: Published package `homepage` and `bugs` fields now point at docs.abx.io instead of a private GitHub
+  repo that 404s. File reports with `abx feedback`; `npm bugs` no longer names a repository the public
+  cannot open.
+
+  Reported in the 2026-08-27 tester batch (feedback 40142396).
+
+- Updated dependencies [c5e0d84]
+- Updated dependencies [c5e0d84]
+  - @artblocks/abx-sdk@0.1.0-alpha.28
+
+## 0.1.0-alpha.28
+
+### Patch Changes
+
+- Updated dependencies [4072f0c]
+  - @artblocks/abx-sdk@0.1.0-alpha.27
+
+## 0.1.0-alpha.27
+
+### Patch Changes
+
+- Updated dependencies [b182f23]
+  - @artblocks/abx-sdk@0.1.0-alpha.26
+
+## 0.1.0-alpha.26
+
+### Patch Changes
+
+- Updated dependencies [8f2f78a]
+  - @artblocks/abx-sdk@0.1.0-alpha.25
+
+## 0.1.0-alpha.25
+
+### Patch Changes
+
+- Updated dependencies [61503c3]
+  - @artblocks/abx-sdk@0.1.0-alpha.24
+
+## 0.1.0-alpha.24
+
+### 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-sdk@0.1.0-alpha.23
+
+## 0.1.0-alpha.23
+
+### Patch Changes
+
+- Updated dependencies [993e095]
+  - @artblocks/abx-sdk@0.1.0-alpha.22
+
+## 0.1.0-alpha.22
+
+### Patch Changes
+
+- Updated dependencies [c9f7aeb]
+  - @artblocks/abx-sdk@0.1.0-alpha.21
+
+## 0.1.0-alpha.21
+
+### Patch Changes
+
+- Updated dependencies [84ca9dd]
+- Updated dependencies [84ca9dd]
+  - @artblocks/abx-sdk@0.1.0-alpha.20
+
+## 0.1.0-alpha.20
+
+### Patch Changes
+
+- Updated dependencies [b1c333d]
+- Updated dependencies [b1c333d]
+  - @artblocks/abx-sdk@0.1.0-alpha.19
+
+## 0.1.0-alpha.19
+
+### Patch Changes
+
+- Updated dependencies [77a6248]
+- Updated dependencies [77a6248]
+  - @artblocks/abx-sdk@0.1.0-alpha.18
+
+## 0.1.0-alpha.18
+
+### 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
+
+## 0.1.0-alpha.17
+
+### Minor Changes
+
+- b5744a1: An RPC that has pruned its log history is now detected, named, and routed around
+
+  A public endpoint that no longer holds old logs does not fail your scan — it answers `eth_getLogs`
+  with `[]` and HTTP 200, which is a success. Everything downstream believed it:
+
+  - **`abx doctor` graded it `best`.** The archive probe was
+    `getLogs({address: zeroAddress, fromBlock: old, toBlock: old})` and counted any non-throw as archive
+    access — but `zeroAddress` never emits logs, so an empty result is exactly what a _perfect_ archive
+    node returns too. The assertion could not fail; it only ever caught endpoints that _error_ on old
+    blocks. `ARCHIVE_DEPTH` was also 100k blocks, which on a 2-second chain is inside the retained window
+    of the very endpoints that prune.
+  - **The client never failed over.** The read transport is a viem `fallback` across every configured
+    endpoint, and `fallback` rotates on an _error_. So every retry asked the same endpoint the same
+    question, and a project whose logs sit ready on the SECOND configured endpoint reconstructed as
+    empty.
+  - **`abx add` then registered the project with no state at all**, after grinding half a million blocks,
+    and suggested re-running `--full` "in a minute" — advice that can never work for a pruned index.
+
+  Measured on the two default Base Sepolia endpoints, same address and same window: one returns zero
+  logs for the project's entire history, the other returns them instantly. Ethereum Sepolia's keyless
+  default endpoint shows the same shape past a few hundred thousand blocks.
+
+  - **The probe asserts on something that must come back.** Blocks are retained by everyone; receipts
+    and the log index are what get pruned. `probeHistoryAt` (new SDK export) reads the probe block, asks
+    for one of its transactions' receipts, and — when that receipt carries a log — requires `getLogs` to
+    return that same log. No hardcoded address, no fixture block. `ARCHIVE_DEPTH` is now 500k.
+    It fails **safe**: a probe block with no transactions, or whose transactions logged nothing, keeps the
+    old lenient verdict rather than inventing a failure.
+  - **`abx doctor` names a reachable endpoint that can't serve history**, with the fault and the fix
+    ("history pruned ~500000 blocks back … list a full-archive endpoint FIRST in `ABX_RPC_URLS_<CHAIN>`").
+    Collapsing to the best endpoint hid this, and ordering is what decides who answers the scan.
+  - **An empty scan now retries each endpoint on its own** before giving up, and says which one served
+    the logs. Cheap by construction: each endpoint is first asked whether it holds history at _this
+    project's_ deploy block — three calls — and only one that passes gets a scan.
+  - **`SelfHostIndexer.reindex(address, {rpcUrl})`** pins a single endpoint instead of the pool, which is
+    what makes that rotation expressible. Clients are pooled per (chain, endpoint), so the default path
+    is unchanged.
+  - The final failure message now separates the two cases it had merged: a project you _just_ deployed
+    (transient, retry) from one that is not new (retention — check `abx doctor`).
+
+  Found by direct probing during the 2026-08-17 agent sweep, after an `abx add` of a 12-day-old Base
+  Sepolia edition reconstructed zero of its 18 events.
+
+### Patch Changes
+
+- Updated dependencies [9c287c0]
+- Updated dependencies [b5744a1]
+- Updated dependencies [9c287c0]
+  - @artblocks/abx-sdk@0.1.0-alpha.16
+
+## 0.1.0-alpha.16
+
+### Minor Changes
+
+- 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
+
+## 0.1.0-alpha.15
+
+### 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
+
+## 0.1.0-alpha.14
+
+### Patch Changes
+
+- Updated dependencies [528c6c6]
+  - @artblocks/abx-sdk@0.1.0-alpha.13
+
+## 0.1.0-alpha.13
+
+### 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.
+
+- 8c254d5: The self-host projection no longer stores or pre-fetches composed URI documents, and the event log
+  is append-only (from the abx-services 2026-08-05 projection memo, `docs/11`).
+
+  - **`contractURI`/`tokenURI` are live reads, never projected.** `reconstructProject`/
+    `reconstructIncremental` gain `readUriDocuments` (default **false**) — with it off, the whole
+    `contractURI`/`tokenURI` head-read batch is skipped entirely, not fetched-and-discarded. These
+    fields have no settled value (a renderer can change the composed document with no log at all) and,
+    on the on-chain lane, can run hundreds of KB per token — a real 32-token project measured 13.4 MB
+    serialized, 99.8% of it `tokenURI`. A stale-but-rendering `data:` URI is worse than a missing one,
+    because nothing about it looks wrong. `abx demo` is the one caller that passes `readUriDocuments:
+true`, for its read-back teaching step; `abx deploy`/`deploy-series`/`deploy-code` don't, and
+    `abx verify`/`tokenuri`/`contracturi` were already doing independent live reads. **For
+    integrators:** `ProjectState.contractURI` / `TokenState.tokenURI` are now `null` unless you opt in
+    — including in a self-host node's `/api/project/:addr` responses (shape unchanged, values now
+    null). Nothing that composes served metadata reads either field (the settled `fields`/
+    `collectionFields` do); the settled scalars — `tokenURIRenderer`/`tokenURILocked`/
+    `contractURIRenderer`/`contractURILocked` — are unaffected and still projected.
+  - **The events table is append-only.** `seq` is now chain-derived (`(blockNumber << 32) |
+logIndex`, BigInt-safe) instead of the array index at write time, so it's stable across re-folds —
+    a re-index appends via `ON CONFLICT DO NOTHING` instead of deleting and reinserting the whole
+    history on every delta. `putProject` upserts the project and token rows in place (a token whose id
+    vanishes from state is still removed) rather than delete-and-reinsert. `deregister` still deletes
+    a forgotten project's events in full; a routine re-fold does not. **A full replay (`abx index
+--full`) purges the project's event log before rebuilding it** — append-only must not let a
+    reorg-replaced event survive as a stale row, so the documented repair path stays a real repair.
+    Existing stores migrate their positional `seq` values to the chain-derived form once, automatically
+    (`PRAGMA user_version`-gated, transactional).
+  - **Self-healing eventCount guard.** An incremental fold that would reduce `eventCount` below what's
+    already stored is discarded rather than written, with one automatic full-reconstruct fallback (the
+    memo's own war story: a bad fold once silently zeroed a live projection with nothing to catch it).
+  - **New self-host stores open with `auto_vacuum = INCREMENTAL`.** Existing stores are unaffected
+    (the pragma only takes on a database with no tables yet) — recorded as backlog B29.
+
+### Patch Changes
+
+- Updated dependencies [afa9dd4]
+- Updated dependencies [8c254d5]
+  - @artblocks/abx-sdk@0.1.0-alpha.12
+
+## 0.1.0-alpha.12
+
+### Patch Changes
+
+- Updated dependencies [d40caf4]
+- Updated dependencies [d40caf4]
+  - @artblocks/abx-sdk@0.1.0-alpha.11
+
+## 0.1.0-alpha.11
+
+### Patch Changes
+
+- Updated dependencies [11fa933]
+- Updated dependencies [11fa933]
+- Updated dependencies [11fa933]
+  - @artblocks/abx-sdk@0.1.0-alpha.10
+
+## 0.1.0-alpha.10
+
+### Patch Changes
+
+- Updated dependencies [df298d8]
+- Updated dependencies [df298d8]
+  - @artblocks/abx-sdk@0.1.0-alpha.9
+
+## 0.1.0-alpha.9
+
+### Patch Changes
+
+- Updated dependencies [e325b46]
+  - @artblocks/abx-sdk@0.1.0-alpha.8
+
+## 0.1.0-alpha.8
+
+### Patch Changes
+
+- Updated dependencies [1b50f9d]
+- Updated dependencies [1b50f9d]
+  - @artblocks/abx-sdk@0.1.0-alpha.7
+
+## 0.1.0-alpha.7
+
+### Patch Changes
+
+- Updated dependencies [1158420]
+- Updated dependencies [1158420]
+- Updated dependencies [1158420]
+  - @artblocks/abx-sdk@0.1.0-alpha.6
+
+## 0.1.0-alpha.6
+
+### 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
+
+## 0.1.0-alpha.5
+
+### Patch Changes
+
+- Updated dependencies [67b686b]
+  - @artblocks/abx-sdk@0.1.0-alpha.4
+
+## 0.1.0-alpha.4
+
+### 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
+
+## 0.1.0-alpha.3
+
+### Patch Changes
+
+- Updated dependencies [3745bd3]
+- Updated dependencies [3745bd3]
+  - @artblocks/abx-sdk@0.1.0-alpha.2
+
+## 0.1.0-alpha.2
+
+### Patch Changes
+
+- Updated dependencies [4074766]
+  - @artblocks/abx-sdk@0.1.0-alpha.1
+
+## 0.1.0-alpha.1
+
+### Patch Changes
+
+- c21ea30: Publish the `dropProjection` API that `abx demo` depends on. `dropProjection` was added to the
+  indexer and called from the CLI's demo in the same commit, but no changeset bumped
+  `@artblocks/abx-indexer` — so it was never republished, and the CLI published at `0.1.0-alpha.5`
+  pinned `@artblocks/abx-indexer@0.1.0-alpha.0`, which has no such method. Installing from npm and
+  running `abx demo` therefore died at step [4] with `indexer.dropProjection is not a function`. In-repo
+  runs never saw it because `workspace:*` resolves to source, where the method exists.

package/dist/index.d.ts

@@ -4,6 +4,6 @@
  * Replays the event spine from chain into a disposable, rebuildable projection.
  * The canonical re-index: how every service onboards or exits a project.
  */
-export { SelfHostIndexer, type IndexResult } from './indexer.js';
+export { SelfHostIndexer, type IndexResult, type ReindexOptions } from './indexer.js';
 export { SqliteStore, type Store, type ProjectRegistration, type EffectStatusRow, type EffectArtifactRow, } from './store.js';
 //# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,OAAO,EAAC,eAAe,EAAE,KAAK,WAAW,EAAC,MAAM,cAAc,CAAC;AAC/D,OAAO,EACL,WAAW,EACX,KAAK,KAAK,EACV,KAAK,mBAAmB,EACxB,KAAK,eAAe,EACpB,KAAK,iBAAiB,GACvB,MAAM,YAAY,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,OAAO,EAAC,eAAe,EAAE,KAAK,WAAW,EAAE,KAAK,cAAc,EAAC,MAAM,cAAc,CAAC;AACpF,OAAO,EACL,WAAW,EACX,KAAK,KAAK,EACV,KAAK,mBAAmB,EACxB,KAAK,eAAe,EACpB,KAAK,iBAAiB,GACvB,MAAM,YAAY,CAAC"}

package/dist/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,OAAO,EAAC,eAAe,EAAmB,MAAM,cAAc,CAAC;AAC/D,OAAO,EACL,WAAW,GAKZ,MAAM,YAAY,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,OAAO,EAAC,eAAe,EAAwC,MAAM,cAAc,CAAC;AACpF,OAAO,EACL,WAAW,GAKZ,MAAM,YAAY,CAAC"}