@tokenbuddy/tb-admin 1.0.35 → 1.0.37

package/src/upstream-balance-probe.ts

@@ -1,13 +0,0 @@
-export {
-  BalanceProbeCache,
-  defaultBalanceProbeCache,
-  probeUpstreamBalance
-} from "@tokenbuddy/contracts";
-export type {
-  BalanceCurrency,
-  BalanceProbeConfig,
-  BalanceProbeOptions,
-  BalanceProbeTemplate,
-  BalanceSnapshot,
-  BalanceSource
-} from "@tokenbuddy/contracts";

package/src/vendor-client.ts

@@ -1,23 +0,0 @@
-/**
- * Type alias for the seller entry shape vendor commands work with.
- * Mirrors the server-side `SellerRegistryEntry` but stays decoupled
- * from `wallet-bootstrap`'s internal types so this package does not
- * become a build-time dependency of the registry service.
- */
-export interface SellerRegistryEntry {
-  id: string;
-  name?: string;
-  profile?: string;
-  app?: string;
-  url: string;
-  status?: string;
-  region?: string;
-  modelsCount?: number;
-  sampleModels?: string[];
-  models?: string[];
-  supportedProtocols: string[];
-  paymentMethods: string[];
-  recommendedFor?: string[];
-}
-
-export { RegistryVendorClient, RegistryAdminClient } from "./client.js";

package/src/vendor-commands.ts

@@ -1,65 +0,0 @@
-import * as fs from "fs";
-import { RegistryVendorClient, SellerRegistryEntry } from "./vendor-client.js";
-
-/**
- * vendor CLI helpers for the `bootstrap sellers` and
- * `bootstrap release` subcommands. Step 5 of the registry redesign.
- *
- *  - `bootstrap sellers add --file <path>`: stage a single seller
- *    for inclusion in the next release request submitted by this
- *    vendor. The server validates the payload shape, persists it to
- *    `seller_pending`, and returns a `pendingSeller` row.
- *  - `bootstrap release submit --note <text> --staged <id>`: submit
- *    a release request that includes one or more staged sellers.
- *  - `bootstrap release list`: list the vendor's release requests.
- *  - `bootstrap release show <id>`: show one release request.
- *  - `bootstrap release force-publish <id>`: super-admin path; the
- *    vendor token cannot force-publish itself (the platform owns
- *    the scheduler loop in Step 7), but we keep the command here
- *    so CI scripts have a single entry point.
- */
-
-export interface StageSellerInput {
-  client: RegistryVendorClient;
-  file: string;
-}
-
-export async function stageSellerFromFile({ client, file }: StageSellerInput): Promise<{ pendingSeller: unknown }> {
-  const content = fs.readFileSync(file, "utf8");
-  const parsed = JSON.parse(content) as SellerRegistryEntry;
-  if (!parsed.id || typeof parsed.id !== "string") {
-    throw new Error(`seller id is required in ${file}`);
-  }
-  return client.stageSeller(parsed);
-}
-
-export interface SubmitReleaseInput {
-  client: RegistryVendorClient;
-  stagedSellerIds: string[];
-  note?: string;
-}
-
-export async function submitRelease({ client, stagedSellerIds, note }: SubmitReleaseInput): Promise<{ releaseRequest: unknown }> {
-  if (stagedSellerIds.length === 0) {
-    throw new Error("at least one --staged <seller-id> is required");
-  }
-  return client.submitRelease({ stagedSellerIds, note });
-}
-
-export function printReleaseRequestSummary(record: any): string {
-  if (!record) {
-    return "no release request";
-  }
-  const summary = record.payloadSummary || { count: 0, sellerIds: [] };
-  return [
-    `id:           #${record.id}`,
-    `status:       ${record.status}`,
-    `vendor:       ${record.vendorId}`,
-    `sellers:      ${summary.count} (${(summary.sellerIds || []).join(", ") || "—"})`,
-    `submittedAt:  ${record.submittedAt || "—"}`,
-    `decidedAt:    ${record.decidedAt || "—"}`,
-    `version:      ${record.publishedVersion !== null && record.publishedVersion !== undefined ? `v${record.publishedVersion}` : "—"}`,
-    record.note ? `note:         ${record.note}` : null,
-    record.errorMessage ? `error:        ${record.errorMessage}` : null
-  ].filter(Boolean).join("\n");
-}