@nuanu-ai/agentify 0.2.4

package/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Nuanu AI
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,2 @@
+Agentify
+Copyright 2026 Nuanu AI

package/README.md

@@ -0,0 +1,135 @@
+# `@nuanu-ai/agentify`
+
+Agentify puts a merchant's existing products where AI agents buy. Each product
+gets a card in an agent-facing storefront and a paid address of its own,
+`/x402/<item>/purchase`, where an agent pays for it with the x402 payment
+protocol; the money goes from the buyer's wallet to the merchant's without
+passing through us.
+
+This package is the merchant's side of it. It publishes the cards, receives
+paid orders and price questions through one outgoing connection, and closes
+each order with the goods or with a refusal. Nothing of the merchant's has to
+be reachable from outside — the process opens that connection itself, so no
+public address and no open port are needed.
+
+## Install
+
+```sh
+npm install @nuanu-ai/agentify
+```
+
+Node.js 24 or newer is required. What arrives with it is our own contracts
+package and zod underneath that, and nothing else.
+
+## The address you give it is the world you are in
+
+```ts
+import { createClient } from '@nuanu-ai/agentify'
+
+const agentify = createClient({
+  apiKey: process.env.AGENTIFY_API_KEY,
+  baseUrl: process.env.AGENTIFY_URL,
+})
+```
+
+There are two addresses, one per world. At `https://test.agentify.ad` you
+build: payments settle on a test chain and the money there is not real. At
+`https://app.agentify.ad` you sell, and it is. A key issued in one does not
+open the other, and the key says which one you are holding: `csk_test_` for the
+first, `csk_live_` for the second. This package picks neither address for you,
+and the worker's first log line names the one it started against and whether
+the money there is real.
+
+## A card, and the handler that fills the orders
+
+The card is the whole of what an agent reads before it buys: what you sell, at
+what price, and what the buyer receives. This one is complete.
+
+```ts
+await agentify.catalog.publish({
+  merchant_item_id: 'access-monthly',
+  title: 'One month of access to the service',
+  description: 'Access for 30 days from delivery, renewal not included',
+  price: '5.00 USD',
+  result: { access_url: 'string', expires_at: 'string' },
+})
+```
+
+Then say what this process answers with, and open the subscription. Paid
+orders, price questions and order events all travel that one connection.
+`grantAccess` below is the seller's own delivery; the handler returns its
+answer and this package sends it, because an answer that has to be returned is
+one nobody can forget to send.
+
+```ts
+agentify.on('order', async (order) => {
+  const access = await grantAccess({ idempotencyKey: order.id })
+
+  if (!access.ok) {
+    return order.refused({
+      code: 'out_of_stock',
+      message: 'No seats left on that plan',
+    })
+  }
+
+  return order.delivered({
+    access_url: access.url,
+    expires_at: access.expiresAt,
+  })
+})
+
+await agentify.start()
+```
+
+The same order can arrive twice, after a dropped connection or a restart of
+yours, so its `id` is also its idempotency key: pass it into your own delivery
+system and the second arrival hands back the first result instead of delivering
+again.
+
+A call that can fail hands the failure back rather than throwing it, in one
+envelope: `ok` says which it was, and a failure carries a code, a sentence a
+person can read, and whether repeating could change the outcome. A card we
+would not publish carries its findings under `problems`, and what no envelope
+can carry — a call that reached nothing at all — is thrown as an `AgentifyError`
+under those same codes.
+
+## The check that needs no key
+
+```sh
+npm exec --offline --package=@nuanu-ai/agentify -- agentify verify card.json
+```
+
+It reads a card the way we read it at publication and names what is wrong,
+offline: no key, no address, no order raised, nothing asked of us. The same
+check is exported as `checkCard`, for cards assembled in code rather than kept
+in files.
+
+That is one half of checking yourself. The other half — whether your handler
+holds against a real order, and against that same order arriving twice — is a
+test purchase on the test site rather than anything this command can do; the
+[quickstart](https://app.agentify.ad/docs/quickstart) walks you through one.
+
+## Where the rest of it is written
+
+The merchant documentation is public. [The first test
+sale](https://app.agentify.ad/docs/quickstart) walks from an empty project to
+a test purchase your side runs end to end; the other three pages are [the
+product card](https://app.agentify.ad/docs/cards) field by field, [orders and
+fulfillment modes](https://app.agentify.ad/docs/orders) for delivering later
+rather than in the answer to the purchase, and [what can go
+wrong](https://app.agentify.ad/docs/failures).
+
+## Versions
+
+This is an early `0.x` pilot surface and the names in it can still change. What
+does not change quietly is the wire: the SDK and the gateway agree on a
+contract version, and a worker whose version the gateway does not share stops
+before it takes an order rather than half reading a document and misreporting
+its own successes. Register `agentify.on('problem', …)`, which is where you
+hear about that and about everything else that did not get through.
+
+## License
+
+Licensed under the Apache License 2.0. Distributions that include this package
+must retain the notices required by that license, including the attribution to
+Nuanu AI in `NOTICE`.

package/dist/backoff.d.ts

@@ -0,0 +1,55 @@
+/**
+ * How long the worker waits before asking a gateway that did not answer.
+ *
+ * This is protocol behaviour rather than infrastructure, which is why it is
+ * written here at all. The hand-rolling rule (ADR-0003 §9) reads a wish to
+ * build retries by hand as a signal that the wrong component was chosen — and
+ * it is right about the general case. This is not the general case: it is the
+ * one wait between two calls of one long poll, three constants and a formula,
+ * and a retry framework brought in to hold them would be a dependency in the
+ * tree a merchant installs (ADR-0003 §8) for something the loop above it does
+ * in four lines. If this file ever grows a policy, a registry or a second
+ * caller with different needs, that is the trigger to stop and choose one.
+ *
+ * The numbers are ours and they are not a claim about the gateway. Half a
+ * second is short enough that a dropped connection costs a merchant nothing
+ * visible, and thirty seconds is close to the long poll's own window, so a
+ * worker that waited out an outage comes back within about one window of the
+ * gateway returning rather than an hour later.
+ *
+ * The jitter is the part that is easy to leave out and expensive to lack. Every
+ * worker that lost the same gateway failed in the same second; without jitter
+ * they all come back in the same millisecond, forever, and the gateway that was
+ * struggling is now being hit by the whole fleet in step. Half the delay is
+ * fixed and half is drawn, so the delay stays inside the bounds above while no
+ * two workers keep the same phase.
+ */
+/** The wait after the first failed call. */
+export declare const FIRST_RETRY_MS = 500;
+/**
+ * The longest this file will ever ask a worker to wait.
+ *
+ * Copied outside this package, and the copy is named here rather than only
+ * where it is read, because whoever raises this number opens this file and not
+ * that one. `DOUBT_MS` in packages/slice/src/subscription.ts is the window a
+ * mock merchant waits before it decides its subscription is alive again, and it
+ * is this ceiling plus the poll deadline plus a margin. Raise this and that
+ * window is too narrow, which makes a healthcheck report a dead subscription as
+ * a live one.
+ */
+export declare const RETRY_CEILING_MS = 30000;
+/** What the wait is multiplied by for each further failure in a row. */
+export declare const RETRY_GROWTH = 2;
+/**
+ * The wait before attempt number `attempt`, given one draw from [0, 1].
+ *
+ * The draw is a parameter rather than a call to `Math.random` inside, because
+ * a test cannot assert a bound it cannot reproduce, and a delay whose bounds
+ * are not tested is a delay nobody has checked.
+ *
+ * Both refusals are bugs in the caller rather than conditions to handle, so
+ * they are thrown. A zeroth attempt or a draw outside the range would produce
+ * a number outside the bounds this file promises, and nothing downstream could
+ * tell that it had.
+ */
+export declare const retryDelayMs: (attempt: number, random: number) => number;

package/dist/backoff.js

@@ -0,0 +1,64 @@
+/**
+ * How long the worker waits before asking a gateway that did not answer.
+ *
+ * This is protocol behaviour rather than infrastructure, which is why it is
+ * written here at all. The hand-rolling rule (ADR-0003 §9) reads a wish to
+ * build retries by hand as a signal that the wrong component was chosen — and
+ * it is right about the general case. This is not the general case: it is the
+ * one wait between two calls of one long poll, three constants and a formula,
+ * and a retry framework brought in to hold them would be a dependency in the
+ * tree a merchant installs (ADR-0003 §8) for something the loop above it does
+ * in four lines. If this file ever grows a policy, a registry or a second
+ * caller with different needs, that is the trigger to stop and choose one.
+ *
+ * The numbers are ours and they are not a claim about the gateway. Half a
+ * second is short enough that a dropped connection costs a merchant nothing
+ * visible, and thirty seconds is close to the long poll's own window, so a
+ * worker that waited out an outage comes back within about one window of the
+ * gateway returning rather than an hour later.
+ *
+ * The jitter is the part that is easy to leave out and expensive to lack. Every
+ * worker that lost the same gateway failed in the same second; without jitter
+ * they all come back in the same millisecond, forever, and the gateway that was
+ * struggling is now being hit by the whole fleet in step. Half the delay is
+ * fixed and half is drawn, so the delay stays inside the bounds above while no
+ * two workers keep the same phase.
+ */
+/** The wait after the first failed call. */
+export const FIRST_RETRY_MS = 500;
+/**
+ * The longest this file will ever ask a worker to wait.
+ *
+ * Copied outside this package, and the copy is named here rather than only
+ * where it is read, because whoever raises this number opens this file and not
+ * that one. `DOUBT_MS` in packages/slice/src/subscription.ts is the window a
+ * mock merchant waits before it decides its subscription is alive again, and it
+ * is this ceiling plus the poll deadline plus a margin. Raise this and that
+ * window is too narrow, which makes a healthcheck report a dead subscription as
+ * a live one.
+ */
+export const RETRY_CEILING_MS = 30_000;
+/** What the wait is multiplied by for each further failure in a row. */
+export const RETRY_GROWTH = 2;
+/**
+ * The wait before attempt number `attempt`, given one draw from [0, 1].
+ *
+ * The draw is a parameter rather than a call to `Math.random` inside, because
+ * a test cannot assert a bound it cannot reproduce, and a delay whose bounds
+ * are not tested is a delay nobody has checked.
+ *
+ * Both refusals are bugs in the caller rather than conditions to handle, so
+ * they are thrown. A zeroth attempt or a draw outside the range would produce
+ * a number outside the bounds this file promises, and nothing downstream could
+ * tell that it had.
+ */
+export const retryDelayMs = (attempt, random) => {
+    if (!Number.isInteger(attempt) || attempt < 1) {
+        throw new TypeError(`the attempt is a whole number from 1 upwards, and was ${attempt}`);
+    }
+    if (!(random >= 0 && random <= 1)) {
+        throw new TypeError(`the random draw is a number from 0 to 1, and was ${random}`);
+    }
+    const capped = Math.min(RETRY_CEILING_MS, FIRST_RETRY_MS * RETRY_GROWTH ** (attempt - 1));
+    return capped / 2 + (capped / 2) * random;
+};

package/dist/check-card.d.ts

@@ -0,0 +1,33 @@
+/**
+ * Is this card enough for an agent to buy from?
+ *
+ * The check is the contracts schema and nothing beside it. A second opinion
+ * written here would be a second definition of a complete card, and the day the
+ * two disagreed a merchant would pass one and be refused by the other.
+ *
+ * What the check cannot see is worth stating, because a merchant reading a
+ * short list of findings would otherwise assume it is the whole list. A card is
+ * checked in two stages: first its shape — which fields are there, what they
+ * hold, whether any field was invented — and then the rules that compare one
+ * field against another, such as a delivery deadline being allowed only on the
+ * modes that wait. The second stage is only reached when the first passes. So a
+ * card that failed on its shape may still have a finding waiting behind the
+ * ones it was given, and the report says so instead of implying a clean second
+ * run. A card that passes has passed both stages and there is nothing behind
+ * it.
+ *
+ * What no local check can decide at all: whether the gateway will accept the
+ * card. Publishing is the authority — a currency we do not settle in, a
+ * merchant key already in use, a policy nobody has written into a schema — and
+ * this check makes no claim about any of that.
+ */
+import { type Problem } from "@nuanu-ai/agentify-contracts";
+export interface CardCheck {
+    /**
+     * Everything wrong with the card that one pass could see, under the same word
+     * and in the same shape the publish call answers in. Empty means the card is
+     * complete as far as the contract can tell.
+     */
+    readonly problems: readonly Problem[];
+}
+export declare const checkCard: (card: unknown) => CardCheck;

package/dist/check-card.js

@@ -0,0 +1,29 @@
+/**
+ * Is this card enough for an agent to buy from?
+ *
+ * The check is the contracts schema and nothing beside it. A second opinion
+ * written here would be a second definition of a complete card, and the day the
+ * two disagreed a merchant would pass one and be refused by the other.
+ *
+ * What the check cannot see is worth stating, because a merchant reading a
+ * short list of findings would otherwise assume it is the whole list. A card is
+ * checked in two stages: first its shape — which fields are there, what they
+ * hold, whether any field was invented — and then the rules that compare one
+ * field against another, such as a delivery deadline being allowed only on the
+ * modes that wait. The second stage is only reached when the first passes. So a
+ * card that failed on its shape may still have a finding waiting behind the
+ * ones it was given, and the report says so instead of implying a clean second
+ * run. A card that passes has passed both stages and there is nothing behind
+ * it.
+ *
+ * What no local check can decide at all: whether the gateway will accept the
+ * card. Publishing is the authority — a currency we do not settle in, a
+ * merchant key already in use, a policy nobody has written into a schema — and
+ * this check makes no claim about any of that.
+ */
+import { CardSchema } from "@nuanu-ai/agentify-contracts";
+import { problemsOf } from "./schema.js";
+export const checkCard = (card) => {
+    const result = CardSchema.safeParse(card);
+    return { problems: result.success ? [] : problemsOf(result.error.issues) };
+};

package/dist/cli.d.ts

@@ -0,0 +1,21 @@
+#!/usr/bin/env node
+/**
+ * The command installed by `@nuanu-ai/agentify` as `agentify`.
+ *
+ * It is glue and nothing else: the work is in `verify.ts`, which answers with
+ * a number and a stream of lines, so that everything the command does can be
+ * tested without a process, a shell or a temporary directory of output.
+ *
+ * What a merchant runs is not this file but `dist/cli.js` compiled from it, and
+ * the distinction is the whole reason the package has a build. These sources
+ * import each other with `.js` specifiers; Node's type stripping does not
+ * rewrite such a specifier, so it would look for a `.js` file that is not
+ * there and stop. `tsc` writes exactly that file, and `publishConfig.bin` in
+ * `package.json` is what points the installed `agentify` command at it.
+ *
+ * Nothing in this repository runs the compiled command, so nothing in
+ * `pnpm test` can tell you it still starts. `pnpm outside` is what does: it
+ * installs the packed tarball into a directory with no path back here and runs
+ * the installed `agentify verify` command there.
+ */
+export {};

package/dist/cli.js

@@ -0,0 +1,24 @@
+#!/usr/bin/env node
+/**
+ * The command installed by `@nuanu-ai/agentify` as `agentify`.
+ *
+ * It is glue and nothing else: the work is in `verify.ts`, which answers with
+ * a number and a stream of lines, so that everything the command does can be
+ * tested without a process, a shell or a temporary directory of output.
+ *
+ * What a merchant runs is not this file but `dist/cli.js` compiled from it, and
+ * the distinction is the whole reason the package has a build. These sources
+ * import each other with `.js` specifiers; Node's type stripping does not
+ * rewrite such a specifier, so it would look for a `.js` file that is not
+ * there and stop. `tsc` writes exactly that file, and `publishConfig.bin` in
+ * `package.json` is what points the installed `agentify` command at it.
+ *
+ * Nothing in this repository runs the compiled command, so nothing in
+ * `pnpm test` can tell you it still starts. `pnpm outside` is what does: it
+ * installs the packed tarball into a directory with no path back here and runs
+ * the installed `agentify verify` command there.
+ */
+import { runVerify } from "./verify.js";
+process.exitCode = await runVerify(process.argv.slice(2), (line) => {
+    process.stdout.write(`${line}\n`);
+});