@artblocks/abx-cli 0.1.0-alpha.16 → 0.1.0-alpha.17

package/CHANGELOG.md

@@ -1,5 +1,238 @@
 # @artblocks/abx-cli
 
+## 0.1.0-alpha.17
+
+### Patch Changes
+
+- df298d8: `abx attach` takes several `<key> <uri>` pairs and sends ONE transaction
+
+  The safety half of backlog B20. The CLI's most-documented flow — mint, then attach each artifact, then
+  refresh — sent one transaction per step with **no all-or-nothing boundary**, so a failure partway
+  through left a permanently half-written token, and a mint cannot be undone. An integrator hit exactly
+  that and folded 8 operations into 1 transaction (846,556 gas) using the SDK's `batchOps` — a primitive
+  the CLI already shipped and did not call. Now it calls it.
+
+  ```bash
+  abx attach 0x… stems ipfs://…/stems.wav score ipfs://…/score.pdf readme ar://…
+  # → 3 artifacts, one multicall: a revert lands NONE of them
+  ```
+
+  Three things make the batch safe rather than merely shorter:
+
+  - **Every pair is validated before anything is sent.** A bad locator in pair 5 stops pair 1 — otherwise
+    batching would defeat its own purpose.
+  - **A key repeated inside one batch is refused.** A field holds one active value, so the later write
+    would silently win — the same full-column-upsert hazard that was a real bug in the resolver's
+    `register` and a real trap in `lock-field`.
+  - **A single pair is unchanged.** `batchOps` passes a lone op through untouched, so the one-artifact
+    case sends the identical plain field transaction it always did — no multicall wrapper, no new gas.
+
+  An odd number of positionals is refused and names the dangling argument, rather than silently ignoring
+  it.
+
+  Still open in B20, and recorded there rather than quietly skipped: batching **`set-field` across several
+  fields** needs a flag-grammar decision first (`attach` batched cleanly because its arguments are
+  positional pairs; `set-field` takes one `--field` with a correlated `--text`/`--value`, and the parser
+  has no notion of correlated repeats). Same for an all-or-nothing "mint and configure" — mint and
+  configure are separate commands, so that needs a verb that owns both.
+
+- df298d8: `abx deploy-code --resume <address>` — finish a deploy whose setup transaction failed
+
+  Closes backlog B15. A code project deploys in **two** transactions: create the clone, then one atomic
+  `multicall` carrying the script chunks, the PostParam schemas, the dependency declarations, the
+  on-chain-URI legs, and any reserve mints. There is no rollback. When the second one fails you own a
+  live-but-unusable contract — and the CREATE2 salt reserved for its address is **spent**, so the dry
+  run's pinned-salt reproduce command can never be run again. One reporter session produced three
+  orphaned contracts from three attempts; another produced five.
+
+  The useful half of that report is that those contracts were **recoverable, not lost**: resending the
+  setup with an adequate gas limit completed one, after which `abx verify` reported chain-complete and the
+  token returned its on-chain `animation_url`. The tester did it by hand with `cast`. We deliberately
+  never documented that as a recipe — telling a creator to hand-assemble a multicall is worse than telling
+  them nothing — so this is the verb.
+
+  ```bash
+  abx deploy-code --resume 0x… <the same content flags the original deploy used> --dry-run
+  ```
+
+  It deploys nothing. It reads what the contract already holds and sends only the missing legs, in one
+  transaction — safe to run twice, and if nothing is missing it sends nothing and says so. Three judgments
+  carry it:
+
+  - **Chunks compare by content, not by count.** A count check would call a chunk "present" when a hand
+    repair wrote different bytes at that index — and a hand repair with `cast` is exactly what happened.
+  - **A schema that already exists is left alone.** Re-writing one is an upsert that can strand values
+    already stored under it; that hazard belongs to `set-schema` and its guard, never to a repair.
+  - **Mints are a shortfall against current supply, never a re-send.** `mint` is the one non-idempotent
+    leg, and a token cannot be un-minted.
+
+  `--salt`, `--721c`, `--bootstrap-factory` and `--mint-all` are refused rather than ignored: they all
+  describe how a contract is _created_, and this creates nothing. ERC-721C especially — enrollment is
+  deploy-time-only and permanent, so silently accepting the flag would imply it can be added later.
+
+  It shares the deploy's own setup-leg builder, so a resume can never drift from what a fresh deploy would
+  have written — a second implementation of that sequence is the failure mode a repair verb most easily
+  introduces. Signing goes through the same choke point as every other write, so `--sign` / `--unsigned` /
+  the owner check / the chain-id guard all apply, and `--dry-run` previews the repair (one bug found and
+  fixed while building this: the deploy's dry-run block returned first, so `--resume … --dry-run` printed a
+  fresh-deploy plan with a newly-reserved salt and a different predicted address).
+
+  15 tests, including every diff branch and the four refusals.
+
+- df298d8: `--json` on every value-emitting command: `mint`, `deploy`, `deploy-series`, `deploy-code`, `state`, `verify`
+
+  Closes backlog B19. The rule it enforces, from an integrator who drove the CLI from a server: **a value
+  a program needs must be obtainable without parsing prose.** They had to regex-scrape ANSI-coloured
+  stdout for every value — and an escape code was captured into a locator, written into a _stored_ player
+  URL, and 404'd in production. The cause was found only by inspecting stored bytes.
+
+  Under `--json`, **stdout carries exactly one JSON document and nothing else.** Every narration line the
+  command would print for a human moves to **stderr** — diverted, not suppressed, because a human
+  watching a deploy still wants to see it while a program redirecting stdout still gets a clean parse.
+  (The update check already wrote to stderr for exactly this reason; this carries the instinct through to
+  the values themselves.)
+
+  - **`mint --json`** → `{tokenIds, txHash, blockNumber, sent, …}`. The token ids come from the mint's own
+    `Transfer(from=0x0)` logs, not from re-reading `nextTokenId` afterwards — a concurrent mint would make
+    that answer wrong, and a number that is usually right is worse than no number. A `--count N` batch
+    reports all N.
+  - **`deploy` / `deploy-series` / `deploy-code --json`** → the address, emitted _the moment it is known_
+    rather than at the end, so a failure in the indexing steps that follow still leaves the caller with
+    the address of a contract that really exists. That matters most for `deploy-code`, which is two
+    transactions: if the setup tx fails, the address of the live-but-incomplete contract is exactly what a
+    recovery needs (backlog B15). With `--dry-run` it reports the **predicted** address plus
+    `saltPinned` — false meaning a plain re-run reserves a fresh salt and lands elsewhere, so a caller
+    must not treat it as reserved.
+  - **`state --json`** → the on-chain snapshot as data, with canonical **names** for param types and auth
+    legs rather than raw Solidity enum indices (a caller must not have to know the enum ordering), and
+    `undefined` (getter absent) kept distinct from a zero address (present, deliberately unset).
+  - **`verify --json`** → the findings, with `ok` matching the exit code. This is the one command a CI job
+    would gate on, since it already exits non-zero on a byte mismatch. The tri-states stay tri-states:
+    `canonical` and each check's `verified` are `true | false | null`, because collapsing "couldn't check"
+    into "failed" would report a normal state as a failure.
+
+  The mechanism is a single shared helper (`withJson`) rather than a `quiet` flag threaded through every
+  command body — deliberately, since the alternative is touching dozens of call sites where the one that
+  gets missed is a stray line that corrupts a parse, i.e. the exact failure being fixed. A command that
+  emits no payload leaves stdout **empty** and exits non-zero rather than printing a `{}` a caller would
+  trust. 8 tests cover the channel contract itself, including that the swap is restored when a body
+  throws.
+
+- df298d8: `abx storage status <locator>` — is it retrievable yet, or only accepted?
+
+  Backlog B21, and the second half of a gap two independent integrations hit eight days apart. An upload
+  service answers "accepted" the moment it holds your bytes; a gateway serves them only once they
+  propagate, and on Arweave that runs to minutes. Nothing in the upload result distinguished the two, so
+  the natural implementation — upload during a mint, write the locator into the token — mints a token
+  that renders broken for the first minutes of its life.
+
+  The first reporter rebuilt this layer themselves (ranged GETs, a propagating/ready model, retry ladders
+  lengthened after measuring real times) and concluded "every serious integrator will rebuild some
+  version of this." The second published 32 renders and found **32/32 404ing on `arweave.net` while 22/32
+  already served from `permagate.io` and `vilenarios.com`**, with the uploader reporting `CONFIRMED`
+  throughout — and the expensive part is what a creator does next, since a placeholder on a fresh drop
+  reads as a failed render, so you re-run `abx render --force` and re-upload everything for nothing.
+
+  That second observation shapes the design: propagation is **per-gateway**, so the check probes the
+  gateway your project actually uses _plus two others_, which buys a third verdict the reporters' own
+  two-state model couldn't express.
+
+  - **`ready`** — your gateway serves the bytes. Safe to reference.
+  - **`propagating`** — another gateway serves them, so the data **provably exists** on the network and
+    yours is merely behind. Waiting is the fix, and the command says plainly not to re-upload.
+  - **`unreachable`** — nothing probed serves them. Deliberately _not_ called propagating: from outside,
+    a locator that is still settling and one that is simply wrong look identical, and reporting the
+    friendlier of the two is how a tool teaches someone to ignore it. When every gateway rejects the id
+    itself (a 4xx that isn't 404) rather than just missing it, that _is_ evidence, and the output says
+    "malformed locator, waiting will not fix it" — the inverse mistake of waiting out a typo costs more
+    than a needless re-upload.
+
+  Accepts every form a locator arrives in (`ar://`, `ipfs://`, a gateway URL, a bare txid/CID, with a
+  directory path suffix), reads **headers only** via a ranged request with the body cancelled — so
+  checking a 40 MB asset doesn't download it — and **exits non-zero unless ready**, which makes waiting a
+  one-liner instead of a retry ladder: `until abx storage status <loc> --json; do sleep 10; done`.
+
+  The primitive is `locatorStatus()` in `@artblocks/abx-storage`, not CLI-only (per B20): anything
+  programmatic should call it in-process rather than spawning the CLI per check. `abx render`'s existing
+  propagation note now points at the command, so the advisory has an answer attached.
+
+- df298d8: `abx tokens <address>` — every token's owner, seed, and params, from chain alone
+
+  The most obvious post-deploy question about a generative collection — _what did the seeds actually
+  deal?_ — had no command. `abx verify` reports per-token minted/render status but no seed; `abx
+tokenuri` prints one token and the seed lives inside its base64 `animation_url`; `abx inspect` is
+  pre-deploy and static. An agent's workaround was to start `abx serve`, `GET /api/project/<addr>`,
+  base64-decode each `tokenURI`, base64-decode the `animation_url` inside it, then regex
+  `0x[0-9a-f]{64}` out of the resulting HTML — 32 times. Every input to that was already a plain
+  contract read.
+
+  `abx tokens <address> [--json] [--from <id>] [--limit <n>]` is chain-only: no indexer projection, no
+  running resolver, no event scan. The params store maintains its own key lists inside its write paths
+  (`tokenParamKeys` / `contractParamKeys`) and `seed` is a reserved param read by name, so the whole
+  listing is `eth_call`s — available to anyone with an RPC URL, including before any indexing has
+  happened. Seeds print in full (truncating the one value the command exists for would repeat the
+  `tokenuri` bug); `--json` emits `{tokenId, owner, seed, params}` per token, contract-scope params
+  once on the parent rather than copied into every row.
+
+  It reports honestly across all three token types rather than failing: a 1/1 has no params extension
+  and says so (owners still list), a pre-enumeration project still yields seeds and flags that params
+  can't be enumerated, and an id whose `ownerOf` reverts is `null` — not "not minted", because a
+  burned id and an unminted id revert identically and a chain-only read can't tell them apart.
+
+  Two things it deliberately is not. It is not a trait spread: a trait comes from running the script
+  against the seed, which is `abx render`'s job — the token-scope _param_ spread it does print is
+  labelled as such. And the reader is in the **SDK** (`listTokens`), not just the CLI, so a
+  programmatic integrator gets it without reimplementing it.
+
+  Backlog B25 (from the 2026-08-04 tester batch, feedback `dcfdc6f4`).
+
+- df298d8: `abx tokenuri --fetch` — follow the URL the contract commits to and print what is actually served
+
+  Closes backlog B14. No command printed the served JSON body: `tokenuri` read the chain, `verify`
+  re-hashed bytes, `status` reported the indexing lifecycle — each a different slice, none of them the
+  document a marketplace actually reads. An agent in a cold sweep fell back to raw `curl` for exactly
+  this, which is the tell that a command was missing.
+
+  ```bash
+  abx tokenuri 0x… --fetch          # GET the baked URL, print the served body + HTTP status
+  abx tokenuri 0x… --fetch --json   # {tokenURI, onChain, served: {url, status, contentType, body}}
+  ```
+
+  It also answers the question a _warning_ could not, which is why the other half of B14 stays declined.
+  "Nothing tells you the provider you registered with isn't the base baked on-chain" is a real gap, but
+  the obvious check — compare the remote's base URL to the on-chain one — false-positives on the common
+  custom-domain case (a baked `meta.artist.xyz` fronting `api.provider.xyz`), and a warning that cries
+  wolf on the correct setup is worse than none. Fetching what the **baked** base returns makes the
+  mismatch self-evident instead: you see the other provider's 404, or another project's document, with no
+  guessing and no false positive.
+
+  Three judgments worth naming:
+
+  - **A `data:` URI is not a failure.** It IS the document, and a fully-on-chain project's whole point is
+    that there is no server to ask — so it reports "nothing to fetch" and exits 0. Treating it as an error
+    would punish the strongest configuration the protocol offers.
+  - **A dead host and a served error are different answers**, because they route to different fixes ("your
+    provider said no" vs "the URL a marketplace will ask is unreachable").
+  - **A non-2xx says it is about the SERVICE, never a mistyped path** — the URL came from the chain, so it
+    is right by construction, and the readout points at `abx status --remote` for the lifecycle.
+
+  Under `--json` the body is verbatim and untruncated and a non-2xx exits non-zero, so CI can gate on it;
+  the human readout clips at 1200 chars and says how many it clipped. The fetch itself lives in
+  `src/served.ts` with an injectable `fetch`, since `main.ts` exports nothing — the same reason
+  `scaffold.ts` was extracted.
+
+  This retired the last two `curl` recommendations in the shipped skill: verifying an attach is now
+  `abx tokenuri <addr> --fetch` (the served document carries the `artifacts` manifest), and the skill's
+  claim that `tokenuri` "follows" the URL — previously true only of `contracturi` — is now accurate.
+
+- Updated dependencies [df298d8]
+- Updated dependencies [df298d8]
+- Updated dependencies [df298d8]
+  - @artblocks/abx-sdk@0.1.0-alpha.9
+  - @artblocks/abx-token-api@0.1.0-alpha.12
+  - @artblocks/abx-storage@0.1.0-alpha.9
+  - @artblocks/abx-indexer@0.1.0-alpha.10
+
 ## 0.1.0-alpha.16
 
 ### Patch Changes

package/dist/jsonout.d.ts

@@ -0,0 +1,37 @@
+import type { Flags } from './flags.js';
+/**
+ * `--json`: make **stdout a machine channel**.
+ *
+ * The rule this enforces, from an integrator who drove the CLI from a server: *a value a program
+ * needs must be obtainable without parsing prose.* They had to regex-scrape ANSI-coloured stdout for
+ * every value — and an escape code ended up inside a locator, was written into a stored player URL,
+ * and 404'd in production. The cause was found only by inspecting stored bytes.
+ *
+ * So under `--json`, stdout carries exactly one JSON document and nothing else. Every narration line
+ * the command would print for a human goes to **stderr** instead — not suppressed, because a human
+ * watching a deploy still wants to see it, and a program redirecting stdout still gets a clean parse.
+ * The update-check already wrote to stderr for precisely this reason; this carries that instinct
+ * through to the values themselves.
+ *
+ * It works by swapping `console.log` for the duration rather than threading a `quiet` flag through
+ * every command body. That is deliberate: the alternative is touching dozens of call sites, where the
+ * one that gets missed is a stray line that corrupts a parse — the exact failure mode being fixed.
+ * `console.error`/`console.warn` are untouched (already stderr), and the payload is written through a
+ * captured reference to the real `console.log`, so nothing can intercept it back.
+ */
+export declare function jsonMode(flags: Flags): boolean;
+/**
+ * Run `body` and, under `--json`, print whatever it returns as the sole contents of stdout.
+ *
+ * `body` receives an `emit` it may call to contribute the payload incrementally — for a command that
+ * discovers its value midway (a deploy learning its address) and would otherwise have to restructure
+ * to return it at the end. The last `emit` wins; a returned value overrides both.
+ *
+ * Without `--json` this is a plain pass-through: zero behaviour change on the human path.
+ */
+export declare function withJson<T extends Record<string, unknown>>(flags: Flags, body: (emit: (payload: T) => void) => Promise<T | void>): Promise<void>;
+/** BigInt-safe JSON: bigints become decimal strings rather than throwing. Every on-chain number a
+ *  payload carries (supply, a token id, a block) arrives as a bigint, and `JSON.stringify` refuses
+ *  them outright — so a payload builder that forgets one would fail at the last line of a deploy. */
+export declare function jsonSafe<T>(value: T): T;
+//# sourceMappingURL=jsonout.d.ts.map

package/dist/jsonout.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"jsonout.d.ts","sourceRoot":"","sources":["../src/jsonout.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAC,KAAK,EAAC,MAAM,YAAY,CAAC;AAEtC;;;;;;;;;;;;;;;;;;;GAmBG;AACH,wBAAgB,QAAQ,CAAC,KAAK,EAAE,KAAK,GAAG,OAAO,CAE9C;AAED;;;;;;;;GAQG;AACH,wBAAsB,QAAQ,CAAC,CAAC,SAAS,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAC9D,KAAK,EAAE,KAAK,EACZ,IAAI,EAAE,CAAC,IAAI,EAAE,CAAC,OAAO,EAAE,CAAC,KAAK,IAAI,KAAK,OAAO,CAAC,CAAC,GAAG,IAAI,CAAC,GACtD,OAAO,CAAC,IAAI,CAAC,CA2Bf;AAED;;qGAEqG;AACrG,wBAAgB,QAAQ,CAAC,CAAC,EAAE,KAAK,EAAE,CAAC,GAAG,CAAC,CAEvC"}

package/dist/jsonout.js

@@ -0,0 +1,68 @@
+/**
+ * `--json`: make **stdout a machine channel**.
+ *
+ * The rule this enforces, from an integrator who drove the CLI from a server: *a value a program
+ * needs must be obtainable without parsing prose.* They had to regex-scrape ANSI-coloured stdout for
+ * every value — and an escape code ended up inside a locator, was written into a stored player URL,
+ * and 404'd in production. The cause was found only by inspecting stored bytes.
+ *
+ * So under `--json`, stdout carries exactly one JSON document and nothing else. Every narration line
+ * the command would print for a human goes to **stderr** instead — not suppressed, because a human
+ * watching a deploy still wants to see it, and a program redirecting stdout still gets a clean parse.
+ * The update-check already wrote to stderr for precisely this reason; this carries that instinct
+ * through to the values themselves.
+ *
+ * It works by swapping `console.log` for the duration rather than threading a `quiet` flag through
+ * every command body. That is deliberate: the alternative is touching dozens of call sites, where the
+ * one that gets missed is a stray line that corrupts a parse — the exact failure mode being fixed.
+ * `console.error`/`console.warn` are untouched (already stderr), and the payload is written through a
+ * captured reference to the real `console.log`, so nothing can intercept it back.
+ */
+export function jsonMode(flags) {
+    return flags.json !== undefined;
+}
+/**
+ * Run `body` and, under `--json`, print whatever it returns as the sole contents of stdout.
+ *
+ * `body` receives an `emit` it may call to contribute the payload incrementally — for a command that
+ * discovers its value midway (a deploy learning its address) and would otherwise have to restructure
+ * to return it at the end. The last `emit` wins; a returned value overrides both.
+ *
+ * Without `--json` this is a plain pass-through: zero behaviour change on the human path.
+ */
+export async function withJson(flags, body) {
+    let payload;
+    const emit = (p) => {
+        payload = p;
+    };
+    if (!jsonMode(flags)) {
+        await body(emit);
+        return;
+    }
+    const realLog = console.log;
+    // Route human narration to stderr. Mirrors console.log's own formatting closely enough for
+    // progress text; nothing structured goes through here.
+    console.log = (...args) => process.stderr.write(args.map((a) => String(a)).join(' ') + '\n');
+    try {
+        const returned = await body(emit);
+        const out = returned ?? payload;
+        // A command that emitted nothing is a bug in that command, not a silent empty object — say so on
+        // stderr and leave stdout empty rather than writing `{}` that a caller would trust.
+        if (out === undefined) {
+            process.stderr.write('abx: --json produced no payload for this command (please report it)\n');
+            process.exitCode = 1;
+            return;
+        }
+        realLog(JSON.stringify(out, null, 2));
+    }
+    finally {
+        console.log = realLog;
+    }
+}
+/** BigInt-safe JSON: bigints become decimal strings rather than throwing. Every on-chain number a
+ *  payload carries (supply, a token id, a block) arrives as a bigint, and `JSON.stringify` refuses
+ *  them outright — so a payload builder that forgets one would fail at the last line of a deploy. */
+export function jsonSafe(value) {
+    return JSON.parse(JSON.stringify(value, (_k, v) => (typeof v === 'bigint' ? v.toString() : v)));
+}
+//# sourceMappingURL=jsonout.js.map

package/dist/jsonout.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"jsonout.js","sourceRoot":"","sources":["../src/jsonout.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,UAAU,QAAQ,CAAC,KAAY;IACnC,OAAO,KAAK,CAAC,IAAI,KAAK,SAAS,CAAC;AAClC,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,CAAC,KAAK,UAAU,QAAQ,CAC5B,KAAY,EACZ,IAAuD;IAEvD,IAAI,OAAsB,CAAC;IAC3B,MAAM,IAAI,GAAG,CAAC,CAAI,EAAE,EAAE;QACpB,OAAO,GAAG,CAAC,CAAC;IACd,CAAC,CAAC;IACF,IAAI,CAAC,QAAQ,CAAC,KAAK,CAAC,EAAE,CAAC;QACrB,MAAM,IAAI,CAAC,IAAI,CAAC,CAAC;QACjB,OAAO;IACT,CAAC;IACD,MAAM,OAAO,GAAG,OAAO,CAAC,GAAG,CAAC;IAC5B,2FAA2F;IAC3F,uDAAuD;IACvD,OAAO,CAAC,GAAG,GAAG,CAAC,GAAG,IAAe,EAAE,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,GAAG,IAAI,CAAC,CAAC;IACxG,IAAI,CAAC;QACH,MAAM,QAAQ,GAAG,MAAM,IAAI,CAAC,IAAI,CAAC,CAAC;QAClC,MAAM,GAAG,GAAI,QAA0B,IAAI,OAAO,CAAC;QACnD,iGAAiG;QACjG,oFAAoF;QACpF,IAAI,GAAG,KAAK,SAAS,EAAE,CAAC;YACtB,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,uEAAuE,CAAC,CAAC;YAC9F,OAAO,CAAC,QAAQ,GAAG,CAAC,CAAC;YACrB,OAAO;QACT,CAAC;QACD,OAAO,CAAC,IAAI,CAAC,SAAS,CAAC,GAAG,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC;IACxC,CAAC;YAAS,CAAC;QACT,OAAO,CAAC,GAAG,GAAG,OAAO,CAAC;IACxB,CAAC;AACH,CAAC;AAED;;qGAEqG;AACrG,MAAM,UAAU,QAAQ,CAAI,KAAQ;IAClC,OAAO,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,SAAS,CAAC,KAAK,EAAE,CAAC,EAAE,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,OAAO,CAAC,KAAK,QAAQ,CAAC,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAM,CAAC;AACvG,CAAC"}