@credda/cli 0.1.6 → 1.0.0

package/dist/index.d.ts

@@ -1,6 +1,43 @@
-#!/usr/bin/env node
 /**
- * `credda`: entry point. All logic lives in cli.ts (testable); this file only
- * wires the real environment: env vars, stdin/file reading, process exit.
+ * `@credda/cli`: the public source mirror for the Credda CLI.
+ *
+ * ## What this package is
+ *
+ * The Credda CLI is published to npm as the unscoped package **`credda`**,
+ * which owns the `credda` executable. This package ships **no executable**.
+ * It is the public mirror of that CLI's command surface, and it exists so the
+ * surface is readable, diffable and issue-trackable outside the private
+ * engine repository.
+ *
+ * ## Why it ships no executable
+ *
+ * Up to 0.1.6 this package installed a binary called `credda` belonging to a
+ * different product (a trust-score client, retired). The engine CLI installs a
+ * binary called `credda` too, and two packages cannot own one name on a
+ * machine: whichever was installed second won, silently. 1.0.0 resolves that by
+ * giving the name up. See README.md, "The 0.1.6 break".
+ *
+ * ## What it exports
+ *
+ * `args.ts` and `commands.ts`, copied byte for byte from `apps/cli/src/` in the
+ * engine repository. Both are dependency-free by construction there — the
+ * parser is hand-rolled and the command table is plain data — which is the only
+ * reason a faithful copy is possible at all. Everything else in that CLI
+ * (`cli.ts`, `doctor.ts`, `triage.ts`, …) reaches into the engine, the
+ * database and the sandbox, and is not mirrored here.
+ *
+ * So what you can do with this package is ask, programmatically and offline,
+ * what commands and flags `credda` accepts and what its exit codes mean. What
+ * you cannot do with it is run an investigation. Install `credda` for that.
+ *
+ * The copies are verbatim, with no local edits, so that CI can compare them to
+ * the originals by hash. Do not add a header to them.
  */
-export {};
+export { GLOBAL_FLAGS, parseArgs, UsageError, boolFlag, numberFlag, stringFlag, type CommandSpec, type FlagKind, type FlagSpec, type FlagValue, type GlobalFlags, type ParsedCommand, } from './args.js';
+export { aliases, canonicalCommand, COMMANDS, commandUsage, EXIT, EXIT_CODE_HELP, RESERVED_EXIT_CODES, rootUsage, } from './commands.js';
+/** The npm package that ships the `credda` executable this surface describes. */
+export declare const EXECUTABLE_PACKAGE = "credda";
+/** Where the mirrored files come from, so a reader can find the original. */
+export declare const MIRROR_SOURCE = "apps/cli/src/ in the Credda engine repository";
+/** The files copied verbatim. CI compares each to its original by hash. */
+export declare const MIRRORED_FILES: readonly string[];

package/dist/index.js

@@ -1,76 +1,43 @@
-#!/usr/bin/env node
 /**
- * `credda`: entry point. All logic lives in cli.ts (testable); this file only
- * wires the real environment: env vars, stdin/file reading, process exit.
+ * `@credda/cli`: the public source mirror for the Credda CLI.
+ *
+ * ## What this package is
+ *
+ * The Credda CLI is published to npm as the unscoped package **`credda`**,
+ * which owns the `credda` executable. This package ships **no executable**.
+ * It is the public mirror of that CLI's command surface, and it exists so the
+ * surface is readable, diffable and issue-trackable outside the private
+ * engine repository.
+ *
+ * ## Why it ships no executable
+ *
+ * Up to 0.1.6 this package installed a binary called `credda` belonging to a
+ * different product (a trust-score client, retired). The engine CLI installs a
+ * binary called `credda` too, and two packages cannot own one name on a
+ * machine: whichever was installed second won, silently. 1.0.0 resolves that by
+ * giving the name up. See README.md, "The 0.1.6 break".
+ *
+ * ## What it exports
+ *
+ * `args.ts` and `commands.ts`, copied byte for byte from `apps/cli/src/` in the
+ * engine repository. Both are dependency-free by construction there — the
+ * parser is hand-rolled and the command table is plain data — which is the only
+ * reason a faithful copy is possible at all. Everything else in that CLI
+ * (`cli.ts`, `doctor.ts`, `triage.ts`, …) reaches into the engine, the
+ * database and the sandbox, and is not mirrored here.
+ *
+ * So what you can do with this package is ask, programmatically and offline,
+ * what commands and flags `credda` accepts and what its exit codes mean. What
+ * you cannot do with it is run an investigation. Install `credda` for that.
+ *
+ * The copies are verbatim, with no local edits, so that CI can compare them to
+ * the originals by hash. Do not add a header to them.
  */
-import { readFile, writeFile } from 'node:fs/promises';
-import { CreddaClient, verifyTrustCredential, verifyVerifiableCredential, verifyTrustExport, } from '@credda/js/headless';
-import { runCli } from './cli.js';
-import { startListener } from './listener.js';
-async function readInput(pathOrDash) {
-    if (pathOrDash === '-') {
-        const chunks = [];
-        for await (const chunk of process.stdin)
-            chunks.push(chunk);
-        return Buffer.concat(chunks).toString('utf8');
-    }
-    return readFile(pathOrDash, 'utf8');
-}
-// Raw authenticated GET for the CSV endpoints (?format=csv): the typed SDK
-// returns parsed JSON only and documents CSV as a raw-fetch use case. Built
-// from the same base URL the client is configured with.
-const API_BASE = (process.env.CREDDA_API_URL ?? 'https://api.credda.io').replace(/\/+$/, '');
-/**
- * The did:web identity of the API this CLI talks to, and the issuer every
- * verification expects. `https://api.credda.io` is `did:web:api.credda.io`;
- * point CREDDA_API_URL at staging and the expectation follows it.
- */
-const ISSUER_DID = `did:web:${new URL(API_BASE).host.toLowerCase()}`;
-async function fetchCsv(path, apiKey) {
-    const res = await fetch(`${API_BASE}/api/v1${path}`, {
-        headers: { Authorization: `Bearer ${apiKey}` },
-    });
-    if (!res.ok) {
-        let detail = '';
-        try {
-            const body = (await res.json());
-            detail = body.error ?? body.message ?? '';
-        }
-        catch {
-            /* non-JSON error body */
-        }
-        throw new Error(detail || `request failed (${res.status})`);
-    }
-    return res.text();
-}
-// process.exitCode (not process.exit()): a hard exit right after a fetch
-// trips a libuv assertion on Windows Node while handles are still closing.
-process.exitCode = await runCli(process.argv.slice(2), {
-    client: new CreddaClient({ apiBase: process.env.CREDDA_API_URL }),
-    fetchCsv,
-    writeFile: (path, content) => writeFile(path, content, 'utf8'),
-    apiKey: process.env.CREDDA_API_KEY,
-    webhookSecret: process.env.CREDDA_WEBHOOK_SECRET,
-    startListener,
-    out: (line) => console.log(line),
-    err: (line) => console.error(line),
-    readInput,
-    // ⚠️ EVERY VERIFIER IS TOLD WHICH ISSUER IT EXPECTS.
-    //
-    // `credda verify` reads a credential handed over by somebody else, which is
-    // the whole point of it. did:web resolution proves the credential was signed
-    // by whoever controls the DID's host; it does NOT prove that host is Credda.
-    // Without an expected issuer, a credential minted by anyone with a domain
-    // verifies clean and the CLI prints it as valid.
-    //
-    // Stated explicitly rather than left to the SDK default, because this CLI
-    // pins an SDK line that does not have that default, and because a call site
-    // that says what it expects keeps saying it after the dependency moves.
-    // ISSUER_DID follows CREDDA_API_URL, so a CLI pointed at staging expects
-    // staging's issuer rather than production's.
-    verifiers: {
-        trustCredential: (credential) => verifyTrustCredential(credential),
-        verifiableCredential: (vcJwt) => verifyVerifiableCredential(vcJwt, { apiBase: API_BASE, issuer: ISSUER_DID }),
-        trustExport: (bundle) => verifyTrustExport(bundle, { apiBase: API_BASE, issuer: ISSUER_DID }),
-    },
-});
+export { GLOBAL_FLAGS, parseArgs, UsageError, boolFlag, numberFlag, stringFlag, } from './args.js';
+export { aliases, canonicalCommand, COMMANDS, commandUsage, EXIT, EXIT_CODE_HELP, RESERVED_EXIT_CODES, rootUsage, } from './commands.js';
+/** The npm package that ships the `credda` executable this surface describes. */
+export const EXECUTABLE_PACKAGE = 'credda';
+/** Where the mirrored files come from, so a reader can find the original. */
+export const MIRROR_SOURCE = 'apps/cli/src/ in the Credda engine repository';
+/** The files copied verbatim. CI compares each to its original by hash. */
+export const MIRRORED_FILES = ['args.ts', 'commands.ts'];

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@credda/cli",
-  "version": "0.1.6",
-  "description": "Official Credda CLI: look up and offline-verify portable trust from the terminal. Public trust checks, credential verification, platform score reads, share-token minting. A thin client over @credda/js; no scoring logic lives here.",
+  "version": "1.0.0",
+  "description": "Public source mirror of the Credda CLI command surface. Ships no executable: install the `credda` package for the CLI itself. Replaces the retired 0.x, which was an unrelated product.",
   "license": "MIT",
   "homepage": "https://github.com/Credda-io/credda-cli#readme",
   "bugs": {
@@ -9,29 +9,31 @@
     "email": "martin@credda.io"
   },
   "type": "module",
-  "bin": {
-    "credda": "dist/index.js"
-  },
   "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "default": "./dist/index.js"
+    }
+  },
   "files": [
     "dist",
-    "!dist/**/*.test.*"
+    "!dist/**/*.test.*",
+    "CHANGELOG.md"
   ],
   "scripts": {
     "build": "tsc -p tsconfig.json",
-    "start": "node dist/index.js",
     "dev": "tsx src/index.ts",
     "typecheck": "tsc --noEmit",
-    "test": "vitest run"
-  },
-  "dependencies": {
-    "@credda/js": "^0.8.0"
+    "test": "vitest run",
+    "example": "node examples/surface.mjs"
   },
   "devDependencies": {
     "@types/node": "^20.14.2",
     "tsx": "^4.23.1",
     "typescript": "^5.4.5",
-    "vitest": "^3.2.6"
+    "vitest": "^3.2.7"
   },
   "publishConfig": {
     "access": "public"
@@ -43,11 +45,10 @@
   "keywords": [
     "credda",
     "cli",
-    "command-line",
-    "trust",
-    "reliability-score",
-    "verifiable-credentials",
-    "sdk"
+    "mirror",
+    "command-surface",
+    "debugging",
+    "bug-reproduction"
   ],
   "engines": {
     "node": ">=18"

package/dist/cli.d.ts

@@ -1,108 +0,0 @@
-/**
- * Command router: pure of process/env/fs so it's testable with a mocked
- * context (same pattern as packages/mcp's tools.ts).
- *
- * Every command is READ-ONLY against Credda's deterministic score. Nothing
- * here writes an Event, adjusts a score, or makes a trust decision: the CLI
- * looks up and offline-verifies EXISTING, already-computed trust facts.
- * `mint`/`revoke` manage a share token (a capability, not a score write).
- */
-import type { CreddaClient, VerifiedCredential, VerifiedVc, VerifiedTrustExport, TrustExport } from '@credda/js/headless';
-export interface CliContext {
-    client: CreddaClient;
-    /** Platform API key from CREDDA_API_KEY, only needed for keyed commands. */
-    apiKey?: string;
-    out: (line: string) => void;
-    err: (line: string) => void;
-    readInput: (pathOrDash: string) => Promise<string>;
-    /** Injected so tests can mock offline verification. */
-    verifiers: {
-        trustCredential: (credential: string) => Promise<VerifiedCredential>;
-        verifiableCredential: (vcJwt: string) => Promise<VerifiedVc>;
-        trustExport: (bundle: TrustExport) => Promise<VerifiedTrustExport>;
-    };
-    /** whsec_… signing secret from CREDDA_WEBHOOK_SECRET, used by `listen`. */
-    webhookSecret?: string;
-    /**
-     * Starts the local webhook receiver (`credda listen`). Injected so the pure
-     * router stays free of node:http; resolves when the server has stopped.
-     */
-    startListener?: (opts: {
-        port: number;
-        secret?: string;
-    }) => Promise<void>;
-    /**
-     * Raw authenticated GET returning the response body as text, for the CSV
-     * endpoints (`?format=csv`), which the typed SDK deliberately leaves to raw
-     * fetch. `path` is relative to the `/api/v1` prefix.
-     */
-    fetchCsv?: (path: string, apiKey: string) => Promise<string>;
-    /** Write a file to disk (CSV outputs). Injected so the router stays fs-free. */
-    writeFile?: (path: string, content: string) => Promise<void>;
-    /** Sleep between `screen --wait` polls. Injected so tests don't wait. */
-    sleep?: (ms: number) => Promise<void>;
-    /** Poll interval for `screen --wait` (default 2000ms). */
-    pollIntervalMs?: number;
-}
-export declare const VERSION = "0.1.6";
-export declare const HELP = "credda: portable trust from the terminal\n\nStart here (needs a sandbox CREDDA_API_KEY, the crd_test_ kind):\n  credda quickstart              Seed your sandbox with synthetic subjects, print\n                                 their real scores, read one back, and then close\n                                 the counterparty-confirmation loop end to end so\n                                 you finish holding a real VERIFIED event, not\n                                 just a number you read. One command, nothing\n                                 written outside the sandbox.\n       --no-confirm              Stop after the seed; skip the confirmation loop.\n\nSandbox (crd_test_ keys only; a live key is refused before anything happens):\n  credda sandbox seed            Populate the sandbox with synthetic subjects.\n                                 Idempotent: an already-seeded subject is left\n                                 alone, never doubled.\n  credda sandbox reset           Wipe the sandbox and start over.\n\nPublic (no API key):\n  credda lookup <token>          Trust check for a share token\n  credda export <token>          Full self-verifying trust export bundle\n  credda verify <file|->         Offline-verify a credential: a W3C VC-JWT,\n                                 a compact Trust Credential, or a saved trust\n                                 export bundle (auto-detected). '-' = stdin.\n  credda registry                Federated trust registry\n  credda did                     Issuer DID document\n  credda benchmarks              Cohort-benchmark catalog (dimensions + k-anonymity)\n  credda reason-codes            Adverse-action reason-code catalog (ECOA / Reg B)\n  credda outcome-templates [industry]\n                                 How a real-world business maps its work to\n                                 Credda events, and WHO confirms each outcome.\n                                 Guidance only. Optional industry slug filters.\n  credda badges list             Open Badges 3.0 achievements this issuer signs\n  credda badges get <badgeId>    One achievement definition\n  credda professional-record public <token>\n                                 The professional record behind a share token\n                                 (the subject's own consent to present it)\n  credda career-export --token <token>\n                                 The subject's whole verified record as a JSON\n                                 Resume document, behind a share token (the\n                                 subject's own consent, no API key sent)\n\nPlatform (needs CREDDA_API_KEY):\n  credda score <userId>          Current score\n  credda explain <userId>        Factor-level score explanation\n  credda components <userId>     Six named 0-100 score components\n  credda risk <userId>           Advisory risk signals\n  credda trust-summary <userId> [--narrative]\n                                 Deterministic, evidence-based trust summary\n                                 (explains; never a verdict). --narrative adds an\n                                 advisory AI retelling when the server has AI on.\n  credda benchmark <userId> [--dimension <d>]\n                                 Where a subject sits within its cohort:\n                                 percentile + the cohort distribution\n  credda distribution [--dimension <d>] [--cohort <c>]\n                                 Aggregate, k-anonymised cohort distribution.\n                                 Omit --cohort for every cohort on the dimension.\n  credda users [--score-min <n>] [--score-max <n>] [--band <b>]\n        [--subject-type <PERSON|AGENT|ORGANIZATION>] [--scored|--unscored] [--frozen]\n        [--active-since <iso>] [--registered-since <iso>] [--registered-before <iso>]\n        [--verified] [--min-verified <n>]\n        [--sort <score|lastActivity|registered|externalId>] [--order <asc|desc>]\n        [--cursor <c>] [--limit <n>]\n                                 Query + export your book of subjects.\n                                 A subject with no score yet reports null,\n                                 never a placeholder; list those with\n                                 --unscored.\n  credda book-summary [same filters as \"users\"]\n                                 Size a segment WITHOUT paging it: how many\n                                 match, how many are scored, band mix and\n                                 median/mean. Null (not 0) when nothing in the\n                                 segment is scored.\n  credda usage [days] [--from <date> --to <date>] [--csv <outfile>]\n                                 Your platform's metered API usage. Either a\n                                 trailing [days] window OR an inclusive\n                                 --from/--to date range (YYYY-MM-DD), not both.\n                                 --csv writes the flat CSV statement to a file.\n  credda activity [--action <A>] [--from <t> --to <t>] [--cursor <c>] [--limit <n>]\n                                 Your platform's own activity/audit log,\n                                 newest-first, cursor-paginated\n  credda verified-profile <userId>\n                                 How much of a subject's CLAIMED record\n                                 (education/skills/certifications/employment) is\n                                 third-party verified. Counts whether a claim is\n                                 verified, never how prestigious it is, and it\n                                 can never move the Reliability Score.\n  credda qualify <userId> --category <education|skill|certification|employment>\n        [--label <l>] [--issuer <i>] [--verified-by <witness>]\n                                 Record a qualification claim. Always recorded;\n                                 counts as VERIFIED only with a genuine\n                                 third-party --verified-by witness.\n  credda professional-record get <userId>\n                                 R\u00E9sum\u00E9-shaped summary of a VERIFIED work record.\n                                 Describes a record, not a hiring verdict, a\n                                 background check, or a consumer report.\n  credda professional-record credential <userId> [--ttl <seconds>]\n                                 Mint the signed, offline-verifiable Professional\n                                 Record Credential (+ an \"Add to LinkedIn\" link)\n  credda reliability-report <userId> [--recent <n>] [--benchmark]\n                                 The consolidated worker reliability report a\n                                 staffing agency or employer weighs: reliability,\n                                 metrics, verified experience, tenure, ranked\n                                 drivers, recent outcomes. EVIDENCE, not a hire /\n                                 place / rank verdict, a background check, or a\n                                 consumer report. Use --token <token> for the\n                                 public worker-consent route (NO API key).\n  credda career-export <userId>  The subject's whole verified record as an open\n                                 JSON Resume document (jsonresume.org). Describes\n                                 a record, not a hiring verdict or a consumer\n                                 report. Use --token <token> for the public route.\n  credda mint <userId>           Mint a share token for a user\n  credda revoke <userId>         Revoke a user's share token\n\nConfirmation requests: the counterparty-confirmation primitive. You PROPOSE an\noutcome and deliver the one-time token to the counterparty over YOUR OWN channel;\nthe event is written, verified, only when that distinct party confirms:\n  credda confirmations create --user <externalId> --type <eventType>\n        --counterparty <ref> [--counterparty-name <n>] [--description <d>]\n        [--stake <HIGH|MEDIUM|LOW>] [--value <n>] [--due <iso>] [--completed <iso>]\n        [--return-url <url>] [--expires-in <days>] [--idempotency-key <k>]\n                                 Needs CREDDA_API_KEY. Token shown ONCE.\n  credda confirmations batch <file.json> [--idempotency-key <k>]\n                                 The ACTIVATION ENGINE: bulk-create up to 100\n                                 requests from a JSON file (an array of request\n                                 bodies, or { \"requests\": [...] }). Warms a cold\n                                 ledger from your book. Needs CREDDA_API_KEY;\n                                 each ok item's token is shown ONCE.\n  credda confirmations list [--status <s>] [--cursor <c>] [--limit <n>]\n  credda confirmations get <id>\n  credda confirmations cancel <id>\n  credda confirmations preview <id> --token <t>\n                                 What the counterparty is asked to confirm.\n                                 NO API key; the token is the capability.\n  credda confirmations respond <id> --token <t> (--confirm | --decline)\n                                 The counterparty's decision. NO API key.\n                                 --confirm writes the event; --decline writes\n                                 nothing. Single-use either way.\n\nReference requests: the qualifications-half sibling of confirmations. A r\u00E9sum\u00E9\nclaim (employment / education / certification / skill) becomes VERIFIED when the\nnamed third party who was there confirms it. Records no qualification and never\nmoves the reliability score:\n  credda references create --user <externalId>\n        --category <employment|education|certification|skill>\n        --counterparty <ref> [--label <l>] [--issuer <i>] [--jurisdiction <j>]\n        [--reference <r>] [--counterparty-name <n>] [--description <d>]\n        [--return-url <url>] [--expires-in <days>] [--idempotency-key <k>]\n                                 Needs CREDDA_API_KEY. Token shown ONCE.\n  credda references list [--status <s>] [--cursor <c>] [--limit <n>]\n  credda references get <id>\n  credda references cancel <id>\n  credda references preview <id> --token <t>\n                                 What the reference is asked to confirm.\n                                 NO API key; the token is the capability.\n  credda references respond <id> --token <t> (--confirm | --decline)\n                                 The reference's decision. NO API key.\n                                 --confirm records the qualification; --decline\n                                 writes nothing. Single-use either way.\n\nThreshold policies (needs CREDDA_API_KEY): declarative \"tell me when this line\nis crossed\"; delivers policy.threshold_crossed through your webhooks. Config\nonly: a policy never reads into, blocks, or changes a score:\n  credda policies list [--cursor <c>] [--limit <n>]\n  credda policies get <id>\n  credda policies create --name <n> (--user <externalId> | --all)\n        --metric <score|component|band|verified_events>\n        [--direction <up|down|enter|leave>] [--threshold <n>]\n        [--component <reliability|timeliness|trustworthiness|verification|consistency|momentum>]\n        [--band <b>]\n  credda policies update <id> [--name <n>] [--direction <d>] [--threshold <n>]\n        [--component <c>] [--band <b>] [--activate | --deactivate]\n                                 The metric is immutable; delete + recreate.\n  credda policies delete <id>\n\nScore monitors (needs CREDDA_API_KEY): edge-triggered watches that deliver\n\"monitor.triggered\" through your webhooks; notification config only, a\nmonitor never affects a score:\n  credda monitors list [--cursor <c>] [--limit <n>]\n  credda monitors get <id>\n  credda monitors create --user <externalId> [--below <score>] [--above <score>] [--band-change]\n                                 At least one condition required. --below fires\n                                 on a downward crossing (and on a first score\n                                 already below it), --above on an upward\n                                 crossing, --band-change on any band change.\n  credda monitors delete <id>\n\nBulk screenings (needs CREDDA_API_KEY): async batch score reads, up to\n10,000 ids per job, strictly read-only:\n  credda screen <ids...>         Submit ids (comma/space separated), or:\n  credda screen --file <path>    One id per line, or a CSV whose FIRST column\n                                 is the id (a leading \"id\"/\"userId\"/\n                                 \"externalId\" header row is skipped).\n         [--wait]                Poll until the job finishes, then print the\n                                 summary (exit 1 if the job FAILED).\n  credda screenings list [--cursor <c>] [--limit <n>]\n  credda screenings get <id>     Job status + summary\n  credda screenings results <id> [--csv <outfile>]\n                                 Per-user results (JSON; --csv writes the CSV\n                                 attachment to a file instead)\n\nWebhooks (needs CREDDA_API_KEY):\n  credda webhooks list                     Your webhook subscriptions\n  credda webhooks create <url> <event..>   Subscribe (secret shown ONCE)\n  credda webhooks delete <id>              Remove a webhook\n  credda webhooks test <id>                Send a synthetic signed delivery\n  credda webhooks deliveries <id>          Recent delivery attempts (incl. retries)\n  credda webhooks recent [event..]         Recent events across ALL your endpoints\n                                           (sample data for automation platforms;\n                                           falls back to catalog examples, flagged\n                                           isExample, when nothing has fired yet)\n\nLocal development:\n  credda listen [port]           Local webhook receiver: verifies each delivery's\n                                 HMAC signature (CREDDA_WEBHOOK_SECRET) and\n                                 pretty-prints the payload. Default port 4141.\n                                 Credda delivers to public HTTPS only; expose\n                                 this port with your own tunnel (e.g. cloudflared).\n\nEnvironment:\n  CREDDA_API_URL                 API base (default https://api.credda.io)\n  CREDDA_API_KEY                 Platform API key for keyed commands\n  CREDDA_WEBHOOK_SECRET          whsec_\u2026 signing secret for \"credda listen\"\n\nExit codes: 0 ok/valid \u00B7 1 error \u00B7 2 credential failed verification";
-/** Raw-key prefix the API stamps on a sandbox key (lib/testMode.ts). */
-export declare const TEST_KEY_PREFIX = "crd_test_";
-/**
- * A sandbox key, or an error that says exactly what to do next.
- *
- * The server refuses a live key anyway (`403 TEST_MODE_ONLY`), but a first-run
- * user does not deserve a 403 to interpret: the prefix is visible locally, so
- * the actionable message costs one string comparison. This is the "better
- * first-run errors" rule applied to the single most likely first mistake.
- */
-export declare function requireSandboxKey(ctx: CliContext): string;
-/**
- * Extra stderr lines for a failed command.
- *
- * The important one is the **request id**: it is the single fastest way for
- * Credda to diagnose a failure, and a CLI user has nowhere else to find it.
- * Also surfaces the machine code (so it can be looked up in
- * `GET /api/v1/errors`) and any `Retry-After` the server asked for.
- *
- * Duck-typed rather than `instanceof CreddaError` on purpose: the router
- * imports only TYPES from the SDK, so it stays pure and trivially mockable.
- * Pure and exported for testing.
- */
-export declare function errorHints(e: unknown): string[];
-/**
- * Tiny flag parser: `--name value` for valued flags, bare `--name` for
- * booleans, everything else positional. Unknown `--flags` are an error rather
- * than silently becoming positionals.
- */
-export declare function parseFlags(args: string[], spec?: {
-    valued?: string[];
-    boolean?: string[];
-}): {
-    positional: string[];
-    flags: Record<string, string | true>;
-};
-/**
- * Parse the ids for `credda screen`. Inline args may be comma- and/or
- * space-separated. A file is one id per line, or a CSV, in which case only
- * the FIRST column is read (a leading header row named id/userId/externalId
- * is skipped). Deduped, order-preserving. Deliberately simple: no quoted-CSV
- * handling (an id containing a comma isn't a valid external id anyway).
- */
-export declare function parseIdList(input: {
-    inline?: string[];
-    fileText?: string;
-}): string[];
-/** Classify verify input: trust-export bundle JSON, VC-JWT, or compact credential. */
-export declare function classifyCredentialInput(raw: string): {
-    kind: 'export';
-    bundle: TrustExport;
-} | {
-    kind: 'vc-jwt';
-    jwt: string;
-} | {
-    kind: 'compact';
-    credential: string;
-};
-/** Run one CLI invocation. Returns the process exit code. */
-export declare function runCli(argv: string[], ctx: CliContext): Promise<number>;