ton-mesh-harness 0.13.0

package/dist/sdk/site-record.d.ts

@@ -0,0 +1,25 @@
+/**
+ * `mesh_site_record` SDK — build a Tonkeeper sign link that sets ONLY
+ * the `site` (dns_adnl_address) record for a `.ton` domain.
+ *
+ * Unlike `deploy()` with a site ADNL (which bundles a `storage` write and
+ * re-uploads a bag), this touches nothing but the site record: it resolves
+ * the domain NFT, builds the `change_dns_record` body, and returns a
+ * Tonkeeper transfer deeplink. No bag, no daemon, no TonConnect — the caller
+ * opens the deeplink in Tonkeeper and approves once.
+ *
+ * This is the programmatic twin of the `site-record` CLI subcommand; both
+ * render the same `SiteRecordResult`.
+ *
+ * NO `console.*` IN THIS FILE — lint-enforced.
+ */
+import { type SiteRecordResult } from './schemas';
+/**
+ * Build the site-record deeplink for a domain + ADNL identity.
+ *
+ * Throws `SdkError(ERR_INVALID_INPUT)` for malformed input (bad domain /
+ * non-hex ADNL) and `SdkError(ERR_NO_DOMAIN)` when the domain NFT can't be
+ * resolved via TONAPI. Does NOT broadcast anything — the returned deeplink
+ * is what actually writes the record, once a wallet signs it.
+ */
+export declare function siteRecord(rawInput: unknown): Promise<SiteRecordResult>;

package/dist/sdk/status.d.ts

@@ -0,0 +1,23 @@
+/**
+ * `mesh_status` SDK — one-shot snapshot of a bag's network state.
+ *
+ * Where `verifyBagOnNetwork` polls until accessible-or-timeout, `status()`
+ * is a single TONAPI query plus an optional DNS-record read. Designed for
+ * the post-deploy "is my bag propagated?" question agents ask.
+ *
+ * Spec: docs/v0.8/mcp-core-requirements.md §F2 (deferred mesh_status,
+ * landed in rc6).
+ *
+ * NO `console.*` IN THIS FILE — lint-enforced.
+ */
+import { type StatusResult } from './schemas';
+/**
+ * Single-shot status snapshot.
+ *
+ * Throws `SdkError(ERR_INVALID_INPUT)` for malformed input (bag_id empty,
+ * domain not a string). Network failures are absorbed — they surface as
+ * `bag_accessible: false` (TONAPI 404 / timeout / DNS error etc.) rather
+ * than thrown errors, because "is it propagated?" with no answer is
+ * meaningfully different from "the SDK crashed."
+ */
+export declare function status(rawInput: unknown): Promise<StatusResult>;

package/dist/sdk/walletkit-network.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Tiny isolation layer for walletkit-specific factories. Keeping this
+ * in its own module means modules that DON'T sign or look up txs
+ * (e.g. agentic-config.ts, endpoints.ts, deploy.ts) don't pull in
+ * `@ton/walletkit` — which matters because walletkit ships ESM files
+ * with directory imports that Node 22+ rejects unless the build inlines
+ * `@ton/walletkit` (bun build externalizes every other dep but bundles
+ * this one — see scripts/build.ts).
+ *
+ * Only `agentic-sign.ts` and `resolve-tx.ts` import from here.
+ *
+ * NO `console.*` IN THIS FILE — lint-enforced.
+ */
+import { ApiClientToncenter, Network } from '@ton/walletkit';
+import type { AgenticNetwork } from './agentic-config';
+/**
+ * Convert our string-discriminated `AgenticNetwork` to walletkit's
+ * chainId-tagged `Network` object.
+ */
+export declare function getWalletkitNetwork(network: AgenticNetwork): ReturnType<typeof Network.mainnet>;
+/**
+ * Build an `ApiClientToncenter` for the given network using the
+ * canonical Toncenter v3 endpoint (single source of truth in
+ * `endpoints.ts`). The API key is optional — without it the client
+ * uses the public per-IP rate limit.
+ *
+ * Centralised so the signer (`agentic-sign.ts`) and the tx-hash
+ * resolver (`resolve-tx.ts`) don't both reconstruct the same config.
+ */
+export declare function buildToncenterClient(network: AgenticNetwork, apiKey: string | undefined): ApiClientToncenter;

package/dist/sdk.d.ts

@@ -0,0 +1,46 @@
+/**
+ * Public SDK entry — what `import { ... } from 'ton-mesh-harness/sdk'`
+ * exposes to npm consumers.
+ *
+ * Stability contract:
+ *
+ *  - Exports added here are subject to semver. Removing or renaming
+ *    requires a major bump.
+ *  - The CLI (`dist/cli.js`) and MCP server (`dist/mcp.js`) consume
+ *    these same symbols internally — the surfaces stay aligned by
+ *    construction.
+ *  - We intentionally re-export from focused submodules rather than
+ *    `export * from './sdk/index'` to keep the public surface
+ *    enumerable in one file.
+ *
+ * Usage:
+ *
+ *    import {
+ *      checkEnv,
+ *      deploy,
+ *      status,
+ *      type DeployOptions,
+ *    } from 'ton-mesh-harness/sdk'
+ *
+ *    const result = await checkEnv()
+ *    if (!result.ready) {
+ *      // surface result.blocking[].fix_hint to the user
+ *      return
+ *    }
+ *
+ *    for await (const ev of deploy({
+ *      source_dir: './dist',
+ *      domain: 'myprotocol.ton',
+ *      wallet: { kind: 'tonconnect', connector: 'Tonkeeper' },
+ *    })) {
+ *      // handle event by ev.phase ...
+ *    }
+ */
+export { checkEnv } from './sdk/check';
+export { deploy, SdkError, type DeployInput, type DeployControl, } from './sdk/deploy';
+export { status } from './sdk/status';
+export { siteRecord } from './sdk/site-record';
+export { CheckEnvOptionsSchema, CheckEnvResultSchema, DeployOptionsSchema, DeployResultSchema, DeployEventSchema, ErrorPayloadSchema, ErrCodeSchema, SiteRecordOptionsSchema, SiteRecordResultSchema, StatusOptionsSchema, StatusResultSchema, WalletSpecSchema, parseWalletInput, type CheckEnvOptions, type CheckEnvResult, type DeployOptions, type DeployResult, type DeployEvent, type DeployPhase, type ErrCode, type ErrorPayload, type SiteRecordOptions, type SiteRecordResult, type StatusOptions, type StatusResult, type WalletSpec, } from './sdk/schemas';
+export { ALL_TOOLS, MESH_CHECK_ENV_TOOL, MESH_DEPLOY_TOOL, MESH_SITE_RECORD_TOOL, MESH_STATUS_TOOL, SUPPLEMENTARY_SCHEMAS, SCHEMA_VERSION, type ToolJsonSchema, type JsonSchema, } from './sdk/json-schemas';
+export { createSdkLogger, type SdkLogger } from './sdk/log';
+export { MESH_HARNESS_VERSION } from './version';