@artblocks/abx-effects 0.1.0-alpha.29 → 0.1.0-alpha.30

package/CHANGELOG.md

@@ -1,412 +1,14 @@
 # @artblocks/abx-effects
 
-## 0.1.0-alpha.29
+## 0.1.0-alpha.30
 
 ### Patch Changes
 
-- Updated dependencies [c198237]
-  - @artblocks/abx-sdk@0.1.0-alpha.29
-  - @artblocks/abx-storage@0.1.0-alpha.29
+- 64248d9: Establish the public source baseline and refresh dependency constraints.
+- Updated dependencies [64248d9]
+  - @artblocks/abx-sdk@0.1.0-alpha.30
+  - @artblocks/abx-storage@0.1.0-alpha.30
 
-## 0.1.0-alpha.28
+## Unreleased
 
-### 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
-  - @artblocks/abx-storage@0.1.0-alpha.28
-
-## 0.1.0-alpha.27
-
-### Patch Changes
-
-- Updated dependencies [4072f0c]
-  - @artblocks/abx-sdk@0.1.0-alpha.27
-  - @artblocks/abx-storage@0.1.0-alpha.27
-
-## 0.1.0-alpha.26
-
-### Patch Changes
-
-- Updated dependencies [b182f23]
-  - @artblocks/abx-sdk@0.1.0-alpha.26
-  - @artblocks/abx-storage@0.1.0-alpha.26
-
-## 0.1.0-alpha.25
-
-### Patch Changes
-
-- Updated dependencies [8f2f78a]
-  - @artblocks/abx-sdk@0.1.0-alpha.25
-  - @artblocks/abx-storage@0.1.0-alpha.25
-
-## 0.1.0-alpha.24
-
-### Patch Changes
-
-- Updated dependencies [61503c3]
-  - @artblocks/abx-sdk@0.1.0-alpha.24
-  - @artblocks/abx-storage@0.1.0-alpha.24
-
-## 0.1.0-alpha.23
-
-### 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-storage@0.1.0-alpha.23
-  - @artblocks/abx-sdk@0.1.0-alpha.23
-
-## 0.1.0-alpha.22
-
-### Patch Changes
-
-- Updated dependencies [993e095]
-  - @artblocks/abx-sdk@0.1.0-alpha.22
-  - @artblocks/abx-storage@0.1.0-alpha.22
-
-## 0.1.0-alpha.21
-
-### Patch Changes
-
-- Updated dependencies [c9f7aeb]
-  - @artblocks/abx-sdk@0.1.0-alpha.21
-  - @artblocks/abx-storage@0.1.0-alpha.21
-
-## 0.1.0-alpha.20
-
-### Patch Changes
-
-- Updated dependencies [84ca9dd]
-- Updated dependencies [84ca9dd]
-  - @artblocks/abx-sdk@0.1.0-alpha.20
-  - @artblocks/abx-storage@0.1.0-alpha.20
-
-## 0.1.0-alpha.19
-
-### Patch Changes
-
-- Updated dependencies [b1c333d]
-- Updated dependencies [b1c333d]
-  - @artblocks/abx-sdk@0.1.0-alpha.19
-  - @artblocks/abx-storage@0.1.0-alpha.19
-
-## 0.1.0-alpha.18
-
-### Patch Changes
-
-- Updated dependencies [77a6248]
-- Updated dependencies [77a6248]
-  - @artblocks/abx-sdk@0.1.0-alpha.18
-  - @artblocks/abx-storage@0.1.0-alpha.18
-
-## 0.1.0-alpha.17
-
-### Patch Changes
-
-- Updated dependencies [c5b8ec3]
-- Updated dependencies [5b29f53]
-  - @artblocks/abx-sdk@0.1.0-alpha.17
-  - @artblocks/abx-storage@0.1.0-alpha.17
-
-## 0.1.0-alpha.16
-
-### Patch Changes
-
-- Updated dependencies [9c287c0]
-- Updated dependencies [b5744a1]
-- Updated dependencies [9c287c0]
-  - @artblocks/abx-sdk@0.1.0-alpha.16
-  - @artblocks/abx-storage@0.1.0-alpha.16
-
-## 0.1.0-alpha.15
-
-### Patch Changes
-
-- Updated dependencies [7fec2d7]
-  - @artblocks/abx-sdk@0.1.0-alpha.15
-  - @artblocks/abx-storage@0.1.0-alpha.15
-
-## 0.1.0-alpha.14
-
-### 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-storage@0.1.0-alpha.14
-
-## 0.1.0-alpha.13
-
-### Patch Changes
-
-- Updated dependencies [528c6c6]
-  - @artblocks/abx-sdk@0.1.0-alpha.13
-  - @artblocks/abx-storage@0.1.0-alpha.13
-
-## 0.1.0-alpha.12
-
-### Patch Changes
-
-- Updated dependencies [afa9dd4]
-- Updated dependencies [8c254d5]
-  - @artblocks/abx-sdk@0.1.0-alpha.12
-  - @artblocks/abx-storage@0.1.0-alpha.12
-
-## 0.1.0-alpha.11
-
-### Patch Changes
-
-- Updated dependencies [d40caf4]
-- Updated dependencies [d40caf4]
-  - @artblocks/abx-sdk@0.1.0-alpha.11
-  - @artblocks/abx-storage@0.1.0-alpha.11
-
-## 0.1.0-alpha.10
-
-### 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).
-
-- 11fa933: Phase 1 of the simplification refactor: one transaction shape with one send-injection point, and an SDK that never touches `.env` or a Node-only global on its own. Two related passes, same release.
-
-  **One transaction shape, one executor.** `StagingTx`/`SendStagingTx` are gone — everything is a `PreparedTx` sent through a single `SendTx`. New `execute.ts` carries `makeHotSender` (pins the nonce once, detects an under-estimated gas limit against a just-deployed target, throws a typed `TxRevertedError` instead of reporting a reverted tx as confirmed) plus `pinGas`/`waitForCodeAt`, moved from the CLI (`gas.ts` is gone) with their design comments intact. Every `deployX` is now `prepareDeployX` (pure) + `deployX(send, ...)`; the CLI's hot lane and `abx deploy-code --resume` both delegate to the same sender instead of hand-rolling their own nonce/gas loop — the class of bug that reported a burned, reverted transaction as a successful deploy can't recur in a second call site because there is no longer a second implementation.
-
-  **The SDK never loads `.env` implicitly.** `loadDotEnv`/`parseEnvContent` moved to a new `@artblocks/abx-sdk/node` subpath — the only module that touches `node:fs`/`node:path`. The package's main entry is now browser-bundle-safe (a permanent esbuild smoke test guards it); a host calls `loadDotEnv()` once at startup (the CLI's `main()`, the effects runner's `main()`) and the SDK core reads whatever's already in `process.env` through a tiny `readEnv` that no-ops outside Node. `ClientOptions` gained `rpcUrls?: string[]` and `makeWalletClient`/`envSigningKey` gained a `privateKey`/`override` escape — explicit config now wins outright over env resolution, following the same override → env → manifest precedence `deployments.ts` already used for contract addresses.
-
-  **Single signing-key name.** `ABX_DEPLOYER_PK` is the only env var the SDK reads for a hot key — `SEPOLIA_FUNDED_PK` and `SEPOLIA_WALLET_PK` (earlier-alpha names) are no longer consulted. A caller with one of the old names set now gets a `MissingSigningKeyError` that names the new one explicitly and says the old ones are retired, rather than a plain "no key found" that leaves an upgrader hunting for why a key that's clearly _there_ isn't being read. Sandbox/e2e scripts and test fixtures move to the new name too.
-
-  **Shared, environment-neutral utilities.** New `sdk/src/util.ts`: `sleep`, a `linearBackoffDelay` helper (service.ts's retry ladder and the effects runner's resolver poll both use it now instead of hand-rolled backoff math), `parseDataUri` (replaces three near-identical `data:` URI regexes across the CLI and the tokenURI probe with one permissive parser), and `tryReadContract` (replaces three near-identical try/read-return-undefined helpers; the CLI's "no contract at this address" diagnostic still wraps it where that mattered). `Buffer` is gone from the SDK core (chunk hex-encoding and param base64-encoding now use viem's `bytesToHex` and a ~12-line dependency-free base64 codec) — nothing in the SDK's main import graph is Node-only any more.
-
-- 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
-
-## 0.1.0-alpha.9
-
-### Patch Changes
-
-- 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
-
-## 0.1.0-alpha.8
-
-### Patch Changes
-
-- Updated dependencies [e325b46]
-  - @artblocks/abx-sdk@0.1.0-alpha.8
-  - @artblocks/abx-storage@0.1.0-alpha.8
-
-## 0.1.0-alpha.7
-
-### Patch Changes
-
-- Updated dependencies [1b50f9d]
-- Updated dependencies [1b50f9d]
-  - @artblocks/abx-sdk@0.1.0-alpha.7
-  - @artblocks/abx-storage@0.1.0-alpha.7
-
-## 0.1.0-alpha.6
-
-### Patch Changes
-
-- Updated dependencies [1158420]
-- Updated dependencies [1158420]
-- Updated dependencies [1158420]
-  - @artblocks/abx-sdk@0.1.0-alpha.6
-  - @artblocks/abx-storage@0.1.0-alpha.6
-
-## 0.1.0-alpha.5
-
-### 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-storage@0.1.0-alpha.5
-
-## 0.1.0-alpha.4
-
-### Patch Changes
-
-- Updated dependencies [67b686b]
-  - @artblocks/abx-sdk@0.1.0-alpha.4
-  - @artblocks/abx-storage@0.1.0-alpha.4
-
-## 0.1.0-alpha.3
-
-### Patch Changes
-
-- Updated dependencies [a72723d]
-  - @artblocks/abx-sdk@0.1.0-alpha.3
-  - @artblocks/abx-storage@0.1.0-alpha.3
-
-## 0.1.0-alpha.2
-
-### 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
-
-- Updated dependencies [3745bd3]
-- Updated dependencies [3745bd3]
-  - @artblocks/abx-sdk@0.1.0-alpha.2
-  - @artblocks/abx-storage@0.1.0-alpha.2
-
-## 0.1.0-alpha.1
-
-### Patch Changes
-
-- Updated dependencies [4074766]
-  - @artblocks/abx-sdk@0.1.0-alpha.1
-  - @artblocks/abx-storage@0.1.0-alpha.1
+Public release history begins here.

package/dist/harness.d.ts

@@ -2,7 +2,7 @@ import { type Server } from 'node:http';
 import { type Hex, type ProjectState, type PublicClient, type TokenState, type TokenDataResult } from '@artblocks/abx-sdk';
 import type { StorageBackend } from '@artblocks/abx-storage';
 /**
- * The reference effect runner (`specs/protocol/effects.md → The reference runner`).
+ * The reference effect runner (`site/content/docs/protocol/effects.mdx → The reference runner`).
  *
  * An effect is a spine subscriber, so its natural form is a deployed, long-running
  * service. This harness is effect-agnostic: an effect registers `{key, outputs, run}`;
@@ -29,14 +29,14 @@ export interface EffectContext {
     liveViewUrl: string;
 }
 /** One declared output: the key naming the artifact + its MIME type, declared where the effect is
- *  declared (`specs/protocol/data-plane.md → Declared type, never sniffed`). The declared type is
+ *  declared (`site/content/docs/protocol/data-plane.mdx → Declared type, never sniffed`). The declared type is
  *  what the manifest and the serving surface speak; the per-run `EffectOutput.contentType` still
  *  travels with the bytes (a mismatch is logged, the declaration wins). */
 export interface EffectOutputDecl {
     key: string;
     mimeType: string;
     /**
-     * This output's content stitches into the metadata JSON (`specs/protocol/effects.md → Bound vs
+     * This output's content stitches into the metadata JSON (`site/content/docs/protocol/effects.mdx → Bound vs
      * referenced`) — `traits` today. Bound output is published as capped inline **bytes**, because a
      * locator can't work: the resolver assembles the content into `tokenURI`, so a pointer there would
      * put a third-party fetch on its hottest read.
@@ -83,7 +83,7 @@ export interface RunnerOptions {
     /** When set, register each artifact with the resolver's control plane
      *  (POST /v1/effect-artifacts) so a resolver that does NOT share this backend's disk can serve it
      *  — a locator for referenced output, capped content for bound output
-     *  (`specs/protocol/effects.md → Bound vs referenced`). Requires a backend that exposes a locator;
+     *  (`site/content/docs/protocol/effects.mdx → Bound vs referenced`). Requires a backend that exposes a locator;
      *  the constructor refuses otherwise. Bearer only; never signs on-chain. Omit for the co-located
      *  topology (runner + resolver share one backend). */
     adminToken?: string;
@@ -182,7 +182,7 @@ export declare class EffectRunner {
     /**
      * Register one stored output with the resolver's control plane so a node that doesn't share this
      * backend's disk can serve it. The form follows the output's DECLARED class
-     * (`specs/protocol/effects.md → Bound vs referenced`), and the resolver enforces the same rule
+     * (`site/content/docs/protocol/effects.mdx → Bound vs referenced`), and the resolver enforces the same rule
      * from its side — this is one contract, not a preference on either end:
      *
      *  - **bound** (`traits`) → the content, capped. The resolver stitches it into the token JSON.

package/dist/harness.js

@@ -346,7 +346,7 @@ export class EffectRunner {
     /**
      * Register one stored output with the resolver's control plane so a node that doesn't share this
      * backend's disk can serve it. The form follows the output's DECLARED class
-     * (`specs/protocol/effects.md → Bound vs referenced`), and the resolver enforces the same rule
+     * (`site/content/docs/protocol/effects.mdx → Bound vs referenced`), and the resolver enforces the same rule
      * from its side — this is one contract, not a preference on either end:
      *
      *  - **bound** (`traits`) → the content, capped. The resolver stitches it into the token JSON.

package/dist/render.d.ts

@@ -8,7 +8,7 @@ import type { EffectModule } from './harness.js';
  * captures actually run (the effects image, or a laptop that ran
  * `pnpm add playwright && npx playwright install chromium`).
  *
- * Capture contract (mirrors `specs/protocol/code-projects.md`): wait for `abx.done()`,
+ * Capture contract (mirrors `site/content/docs/protocol/code-projects.mdx`): wait for `abx.done()`,
  * else the project's `render.captureDelay` contract param (ms), else a default timeout.
  * Dimensions: `render.imageWidth` (default 1200 — pass a larger width for a hi-def
  * master when image is the primary display format) × `render.aspectRatio` (w/h,

package/dist/render.js

@@ -8,7 +8,7 @@ import { contractParamString } from '@artblocks/abx-sdk';
  * captures actually run (the effects image, or a laptop that ran
  * `pnpm add playwright && npx playwright install chromium`).
  *
- * Capture contract (mirrors `specs/protocol/code-projects.md`): wait for `abx.done()`,
+ * Capture contract (mirrors `site/content/docs/protocol/code-projects.mdx`): wait for `abx.done()`,
  * else the project's `render.captureDelay` contract param (ms), else a default timeout.
  * Dimensions: `render.imageWidth` (default 1200 — pass a larger width for a hi-def
  * master when image is the primary display format) × `render.aspectRatio` (w/h,

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@artblocks/abx-effects",
-  "version": "0.1.0-alpha.29",
+  "version": "0.1.0-alpha.30",
   "license": "MIT",
-  "description": "ABX Self-Host Toolkit (Layer 3) — the reference effect runner. A deployed, long-running service hosting spine-subscribing effects (render first) behind one harness; stateless via inputsHash addressing. The playwright npm package is a normal (small, browserless) dependency pinned EXACTLY to the Dockerfile.effects base-image tag; browsers install only where captures run (`npx playwright install chromium`).",
+  "description": "Reference rendering and effects runner for ABX projects.",
   "type": "module",
   "main": "./dist/index.js",
   "exports": {
@@ -26,7 +26,7 @@
     "directory": "packages/effects"
   },
   "homepage": "https://docs.abx.io",
-  "bugs": "https://docs.abx.io/docs/using-abx/remote-services",
+  "bugs": "https://github.com/ArtBlocks/abx/issues",
   "keywords": [
     "abx",
     "nft",
@@ -39,10 +39,10 @@
     "access": "public"
   },
   "dependencies": {
-    "playwright": "1.61.1",
-    "viem": "^2.21.0",
-    "@artblocks/abx-sdk": "0.1.0-alpha.29",
-    "@artblocks/abx-storage": "0.1.0-alpha.29"
+    "playwright": "1.62.1",
+    "viem": "^2.56.0",
+    "@artblocks/abx-sdk": "0.1.0-alpha.30",
+    "@artblocks/abx-storage": "0.1.0-alpha.30"
   },
   "scripts": {
     "build": "tsc -b tsconfig.build.json"