@synap-core/cli 1.10.0 → 1.12.2

package/dist/lib/key-state.js

@@ -0,0 +1,115 @@
+/**
+ * What the pod says about ONE key — asked by its holder.
+ *
+ * `GET /api/hub/auth/key-state` answers for a key whether or not it
+ * authenticates: active, awaiting approval (+ the approval page), revoked (+
+ * why, and when/where a replacing connection was made), expired, or unknown.
+ * A pod older than that door answers 404; we then fall back to `/auth/status`,
+ * which can only say "works" or "does not work" — reported as `inactive`, never
+ * guessed into "revoked" (that guess is what sent the 2026-10-12 incident down
+ * the wrong path: the key was only awaiting approval).
+ *
+ * Also the ONE write gate: a key is persisted into a config only when the pod
+ * has not positively said it is unusable (`writeGate`).
+ */
+const STATES = new Set(["active", "awaiting_approval", "revoked", "expired", "unknown"]);
+/** Ask the pod about `key`. Never throws. */
+export async function fetchKeyState(podUrl, key, deps = {}) {
+    const f = deps.fetch ?? fetch;
+    const base = podUrl.replace(/\/+$/, "");
+    const init = () => ({
+        headers: { Authorization: `Bearer ${key}` },
+        signal: AbortSignal.timeout(deps.timeoutMs ?? 15_000),
+    });
+    const failure = (err) => err?.name === "TimeoutError" ? `no answer in ${Math.round((deps.timeoutMs ?? 15_000) / 1000)}s` : err.message;
+    let res;
+    try {
+        res = await f(`${base}/api/hub/auth/key-state`, init());
+    }
+    catch (err) {
+        return { state: "unreachable", error: failure(err) };
+    }
+    if (res.ok) {
+        const body = (await res.json().catch(() => null));
+        if (body && typeof body.state === "string" && STATES.has(body.state))
+            return body;
+        return { state: "unreachable", error: "the pod answered key-state with an unreadable body" };
+    }
+    if (res.status !== 404)
+        return nonOkState(res.status, "/auth/key-state");
+    // Older pod: no key-state door. `/auth/status` says works / does not work.
+    let legacy;
+    try {
+        legacy = await f(`${base}/api/hub/auth/status`, init());
+    }
+    catch (err) {
+        return { state: "unreachable", error: failure(err), legacy: true };
+    }
+    if (legacy.ok) {
+        const s = (await legacy.json().catch(() => ({})));
+        return { state: "active", legacy: true, keyId: s.keyId, keyIdPrefix: s.keyIdPrefix, expiresAt: s.expiresAt ?? null };
+    }
+    if (legacy.status === 401) {
+        const env = (await legacy.json().catch(() => ({})));
+        if (env.reason === "expired")
+            return { state: "expired", legacy: true, keyIdPrefix: env.keyIdPrefix };
+        return { state: "inactive", legacy: true, keyIdPrefix: env.keyIdPrefix };
+    }
+    return { ...nonOkState(legacy.status, "/auth/status"), legacy: true };
+}
+/**
+ * A non-OK answer that is not the older-pod 404. Only a 5xx (or a rate-limit /
+ * request timeout, which says nothing about the key) is `unreachable`. Any
+ * other refusal — 401, 403 (a guest's key), 400… — is the pod saying NO to
+ * this key: `inactive`, which `writeGate` refuses. Reading a 403 as
+ * "unreachable" let the gate write a key the pod refuses.
+ */
+function nonOkState(status, door) {
+    if (status >= 500 || status === 408 || status === 429)
+        return { state: "unreachable", error: `HTTP ${status} from ${door}` };
+    // A pod with neither door cannot be asked at all — no answer, not a "no".
+    if (status === 404)
+        return { state: "unreachable", error: `this pod has no ${door} door` };
+    return { state: "inactive", error: `HTTP ${status} from ${door}` };
+}
+/**
+ * May this key be written into a config? Only a POSITIVE "unusable" refuses:
+ * pending, revoked, expired, unknown to the pod, or (older pod) rejected. An
+ * unreachable pod is not evidence — it allows, with a warning.
+ */
+export function writeGate(s) {
+    switch (s.state) {
+        case "active":
+            return { allow: true };
+        case "unreachable":
+            return { allow: true, warning: `could not confirm the key with the pod (${s.error ?? "unreachable"})` };
+        case "awaiting_approval":
+            return { allow: false, reason: "the key is still awaiting approval" };
+        case "revoked":
+            return { allow: false, reason: `the key was revoked${s.revokedReason ? ` (${s.revokedReason})` : ""}` };
+        case "expired":
+            return { allow: false, reason: "the key has expired" };
+        case "unknown":
+            return { allow: false, reason: "the pod does not know this key" };
+        case "inactive":
+            return { allow: false, reason: "the pod refuses this key" };
+    }
+}
+/** Thrown when a caller tries to persist a key the pod says is unusable. */
+export class KeyNotLiveError extends Error {
+    keyState;
+    constructor(keyState, reason) {
+        super(`Refusing to save this key: ${reason}.`);
+        this.keyState = keyState;
+        this.name = "KeyNotLiveError";
+    }
+}
+/** Ask the pod, then refuse (throw) unless the key may be written. */
+export async function assertKeyWritable(podUrl, key, deps = {}) {
+    const s = await fetchKeyState(podUrl, key, deps);
+    const gate = writeGate(s);
+    if (!gate.allow)
+        throw new KeyNotLiveError(s, gate.reason);
+    return s;
+}
+//# sourceMappingURL=key-state.js.map

package/dist/lib/key-state.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"key-state.js","sourceRoot":"","sources":["../../src/lib/key-state.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAiCH,MAAM,MAAM,GAAG,IAAI,GAAG,CAAC,CAAC,QAAQ,EAAE,mBAAmB,EAAE,SAAS,EAAE,SAAS,EAAE,SAAS,CAAC,CAAC,CAAC;AAIzF,6CAA6C;AAC7C,MAAM,CAAC,KAAK,UAAU,aAAa,CACjC,MAAc,EACd,GAAW,EACX,OAAkD,EAAE;IAEpD,MAAM,CAAC,GAAG,IAAI,CAAC,KAAK,IAAI,KAAK,CAAC;IAC9B,MAAM,IAAI,GAAG,MAAM,CAAC,OAAO,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC;IACxC,MAAM,IAAI,GAAG,GAAgB,EAAE,CAAC,CAAC;QAC/B,OAAO,EAAE,EAAE,aAAa,EAAE,UAAU,GAAG,EAAE,EAAE;QAC3C,MAAM,EAAE,WAAW,CAAC,OAAO,CAAC,IAAI,CAAC,SAAS,IAAI,MAAM,CAAC;KACtD,CAAC,CAAC;IACH,MAAM,OAAO,GAAG,CAAC,GAAY,EAAE,EAAE,CAC9B,GAAa,EAAE,IAAI,KAAK,cAAc,CAAC,CAAC,CAAC,gBAAgB,IAAI,CAAC,KAAK,CAAC,CAAC,IAAI,CAAC,SAAS,IAAI,MAAM,CAAC,GAAG,IAAI,CAAC,GAAG,CAAC,CAAC,CAAE,GAAa,CAAC,OAAO,CAAC;IACtI,IAAI,GAAa,CAAC;IAClB,IAAI,CAAC;QACH,GAAG,GAAG,MAAM,CAAC,CAAC,GAAG,IAAI,yBAAyB,EAAE,IAAI,EAAE,CAAC,CAAC;IAC1D,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,OAAO,EAAE,KAAK,EAAE,aAAa,EAAE,KAAK,EAAE,OAAO,CAAC,GAAG,CAAC,EAAE,CAAC;IACvD,CAAC;IACD,IAAI,GAAG,CAAC,EAAE,EAAE,CAAC;QACX,MAAM,IAAI,GAAG,CAAC,MAAM,GAAG,CAAC,IAAI,EAAE,CAAC,KAAK,CAAC,GAAG,EAAE,CAAC,IAAI,CAAC,CAAmC,CAAC;QACpF,IAAI,IAAI,IAAI,OAAO,IAAI,CAAC,KAAK,KAAK,QAAQ,IAAI,MAAM,CAAC,GAAG,CAAC,IAAI,CAAC,KAAK,CAAC;YAAE,OAAO,IAA2B,CAAC;QACzG,OAAO,EAAE,KAAK,EAAE,aAAa,EAAE,KAAK,EAAE,oDAAoD,EAAE,CAAC;IAC/F,CAAC;IACD,IAAI,GAAG,CAAC,MAAM,KAAK,GAAG;QAAE,OAAO,UAAU,CAAC,GAAG,CAAC,MAAM,EAAE,iBAAiB,CAAC,CAAC;IAEzE,2EAA2E;IAC3E,IAAI,MAAgB,CAAC;IACrB,IAAI,CAAC;QACH,MAAM,GAAG,MAAM,CAAC,CAAC,GAAG,IAAI,sBAAsB,EAAE,IAAI,EAAE,CAAC,CAAC;IAC1D,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,OAAO,EAAE,KAAK,EAAE,aAAa,EAAE,KAAK,EAAE,OAAO,CAAC,GAAG,CAAC,EAAE,MAAM,EAAE,IAAI,EAAE,CAAC;IACrE,CAAC;IACD,IAAI,MAAM,CAAC,EAAE,EAAE,CAAC;QACd,MAAM,CAAC,GAAG,CAAC,MAAM,MAAM,CAAC,IAAI,EAAE,CAAC,KAAK,CAAC,GAAG,EAAE,CAAC,CAAC,EAAE,CAAC,CAAC,CAAwE,CAAC;QACzH,OAAO,EAAE,KAAK,EAAE,QAAQ,EAAE,MAAM,EAAE,IAAI,EAAE,KAAK,EAAE,CAAC,CAAC,KAAK,EAAE,WAAW,EAAE,CAAC,CAAC,WAAW,EAAE,SAAS,EAAE,CAAC,CAAC,SAAS,IAAI,IAAI,EAAE,CAAC;IACvH,CAAC;IACD,IAAI,MAAM,CAAC,MAAM,KAAK,GAAG,EAAE,CAAC;QAC1B,MAAM,GAAG,GAAG,CAAC,MAAM,MAAM,CAAC,IAAI,EAAE,CAAC,KAAK,CAAC,GAAG,EAAE,CAAC,CAAC,EAAE,CAAC,CAAC,CAA8C,CAAC;QACjG,IAAI,GAAG,CAAC,MAAM,KAAK,SAAS;YAAE,OAAO,EAAE,KAAK,EAAE,SAAS,EAAE,MAAM,EAAE,IAAI,EAAE,WAAW,EAAE,GAAG,CAAC,WAAW,EAAE,CAAC;QACtG,OAAO,EAAE,KAAK,EAAE,UAAU,EAAE,MAAM,EAAE,IAAI,EAAE,WAAW,EAAE,GAAG,CAAC,WAAW,EAAE,CAAC;IAC3E,CAAC;IACD,OAAO,EAAE,GAAG,UAAU,CAAC,MAAM,CAAC,MAAM,EAAE,cAAc,CAAC,EAAE,MAAM,EAAE,IAAI,EAAE,CAAC;AACxE,CAAC;AAED;;;;;;GAMG;AACH,SAAS,UAAU,CAAC,MAAc,EAAE,IAAY;IAC9C,IAAI,MAAM,IAAI,GAAG,IAAI,MAAM,KAAK,GAAG,IAAI,MAAM,KAAK,GAAG;QACnD,OAAO,EAAE,KAAK,EAAE,aAAa,EAAE,KAAK,EAAE,QAAQ,MAAM,SAAS,IAAI,EAAE,EAAE,CAAC;IACxE,0EAA0E;IAC1E,IAAI,MAAM,KAAK,GAAG;QAAE,OAAO,EAAE,KAAK,EAAE,aAAa,EAAE,KAAK,EAAE,mBAAmB,IAAI,OAAO,EAAE,CAAC;IAC3F,OAAO,EAAE,KAAK,EAAE,UAAU,EAAE,KAAK,EAAE,QAAQ,MAAM,SAAS,IAAI,EAAE,EAAE,CAAC;AACrE,CAAC;AAID;;;;GAIG;AACH,MAAM,UAAU,SAAS,CAAC,CAAW;IACnC,QAAQ,CAAC,CAAC,KAAK,EAAE,CAAC;QAChB,KAAK,QAAQ;YACX,OAAO,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC;QACzB,KAAK,aAAa;YAChB,OAAO,EAAE,KAAK,EAAE,IAAI,EAAE,OAAO,EAAE,2CAA2C,CAAC,CAAC,KAAK,IAAI,aAAa,GAAG,EAAE,CAAC;QAC1G,KAAK,mBAAmB;YACtB,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,EAAE,oCAAoC,EAAE,CAAC;QACxE,KAAK,SAAS;YACZ,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,EAAE,sBAAsB,CAAC,CAAC,aAAa,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,aAAa,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC;QAC1G,KAAK,SAAS;YACZ,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,EAAE,qBAAqB,EAAE,CAAC;QACzD,KAAK,SAAS;YACZ,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,EAAE,gCAAgC,EAAE,CAAC;QACpE,KAAK,UAAU;YACb,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,MAAM,EAAE,0BAA0B,EAAE,CAAC;IAChE,CAAC;AACH,CAAC;AAED,4EAA4E;AAC5E,MAAM,OAAO,eAAgB,SAAQ,KAAK;IAE7B;IADX,YACW,QAAkB,EAC3B,MAAc;QAEd,KAAK,CAAC,8BAA8B,MAAM,GAAG,CAAC,CAAC;QAHtC,aAAQ,GAAR,QAAQ,CAAU;QAI3B,IAAI,CAAC,IAAI,GAAG,iBAAiB,CAAC;IAChC,CAAC;CACF;AAED,sEAAsE;AACtE,MAAM,CAAC,KAAK,UAAU,iBAAiB,CACrC,MAAc,EACd,GAAW,EACX,OAA8B,EAAE;IAEhC,MAAM,CAAC,GAAG,MAAM,aAAa,CAAC,MAAM,EAAE,GAAG,EAAE,IAAI,CAAC,CAAC;IACjD,MAAM,IAAI,GAAG,SAAS,CAAC,CAAC,CAAC,CAAC;IAC1B,IAAI,CAAC,IAAI,CAAC,KAAK;QAAE,MAAM,IAAI,eAAe,CAAC,CAAC,EAAE,IAAI,CAAC,MAAM,CAAC,CAAC;IAC3D,OAAO,CAAC,CAAC;AACX,CAAC"}

package/dist/lib/kind-package.d.ts

@@ -0,0 +1,181 @@
+/**
+ * Standalone (non-workspace) package files — view / cell / skill / workflow.
+ * ================================================================
+ * `market-authoring.ts`'s scaffold/publish loop is WorkspaceYaml-shaped (a
+ * `meta` + `workspace` envelope validated by `validateTemplate`). A lone view,
+ * cell, or skill has no such envelope — it IS its content. This file is the
+ * PURE half (no network, no `process.exit`) for that shape: parse a standalone
+ * package file, run the minimal structural check the CP's own
+ * `packageDefinitionSchema` needs (see synap-control-plane-api/src/routes/
+ * packages.ts), and hand back a definition `publishPackage` can post.
+ *
+ * File shape (explicit — no `_meta`/`meta` ambiguity, unlike the workspace
+ * envelope):
+ *   {
+ *     "category": "cell" | "view",
+ *     "slug": "my-cell",
+ *     "displayName": "My Cell",
+ *     "description": "...",           // optional
+ *     "tags": ["..."],                // optional
+ *     "definition": { "cells": [...] } | { "views": [...] }
+ *   }
+ *
+ * A `cells[]` entry may carry `codeFile` (a path to the cell's ESM entry
+ * source, resolved relative to the package file) INSTEAD of an inline `code`
+ * string — the indirection an author needs to publish from a real source file
+ * rather than hand-pasting a minified bundle into JSON. `codeFile` is CLI-only:
+ * the CP's `packageDefinitionSchema.cells[]` has no such slot (only `code`,
+ * required), so `resolveCellCodeFiles` bundles it (via `cell.ts`'s
+ * `buildCellFromSource` — the SAME esbuild path `cell build` uses) and inlines
+ * the result into `code` before the definition ever reaches `publishPackage`.
+ *
+ * ✅ RESOLVED 2026-09-04 — this block used to claim that
+ * `packageDefinitionSchema` requires `definition.profiles` to be non-empty
+ * UNCONDITIONALLY, so a profile-less view/cell/skill package would 400 against
+ * `POST /api/packages`. That is NO LONGER TRUE and had become a load-bearing
+ * lie: the rule moved to a category-gated `superRefine` on the OUTER schema
+ * (`synap-control-plane-api/src/routes/packages.ts:859-872` — only that schema
+ * can see the sibling `category`), and it now fires for `category === "workspace"`
+ * ONLY. Every other kind may publish with `profiles: []`.
+ *
+ * Left as a tombstone rather than deleted because the stale claim outlived its
+ * fix and was still being cited as fact months later.
+ *
+ * ✅ RESOLVED 2026-10-06 — "skill" NOW HAS A PAYLOAD SLOT. This block used to
+ * warn that `packageDefinitionSchema` carried no top-level slot for a standalone
+ * skill, so one had nowhere to land and `validateStandalonePackage` reported it
+ * rather than inventing a shape. Both halves are now false: the CP grew a
+ * SINGULAR `skill:` slot (`synap-control-plane-api/src/routes/packages.ts`,
+ * beside `capability:`) whose field names mirror the pod's own create door, and
+ * the pod grew an applier + resolver entry so a `skill` dependency installs
+ * itself. Note the shape is `skill`, NOT `skills` — the plural is the workspace
+ * template's DECLARED-skills array, an unrelated lane that already existed.
+ *
+ * Left as a tombstone, like the block above: the stale claim was load-bearing
+ * (it is why `skill` was refused at scaffold) and would otherwise be cited again.
+ */
+import type { PackageDefinitionLike } from "./template-file.js";
+/**
+ * The non-workspace package types this file knows how to shape. Mirrors the
+ * live subset of the CP's `PACKAGE_TYPES` SSOT (db/schema/packages.ts) —
+ * "workspace" has its own authoring loop (`template-file.ts`).
+ *
+ * `workflow` (the CP's rename of the old "automation" + "playbook") IS a lone
+ * file: its payload is `definition.automations[]` — a triggered/sequenced run,
+ * exactly the shape `POST /api/packages`' `packageDefinitionSchema.automations`
+ * validates (`routes/packages.ts`). The `category` posted upstream must be a
+ * live `PACKAGE_TYPES` value, so we use "workflow" verbatim (never the retired
+ * "automation" alias, which the publish enum rejects).
+ *
+ * `capability` used to be excluded here with the comment "authored/seeded
+ * elsewhere, not as a lone file here". That was a statement about how WE happen
+ * to author them, not about what the CP accepts — and it left the most complex
+ * kind we have with no CLI door at all. The server half already exists, all of
+ * it, and NO CP migration is involved:
+ *   • `capability` is a live `PACKAGE_TYPES` value (db/schema/packages.ts);
+ *   • `packageDefinitionSchema` declares `capability: z.record(z.unknown())`
+ *     (routes/packages.ts:824-832);
+ *   • `publish-package-core.ts` stores a non-workspace definition AS-IS and
+ *     hashes it into `definition.capability.contentHash`;
+ *   • `GET /api/marketplace/capabilities` unwraps `definition.capability` into
+ *     the card the pod's catalog sync caches (marketplace-apps.ts:398-410);
+ *   • `market.install` resolves `kind: "capability"` BY KEY, cache row or not
+ *     (marketplace-install.ts:263).
+ * So the whole loop — scaffold → validate → publish → install — closes.
+ *
+ * `skill` is a full member as of 2026-10-06: it has a CP payload slot, a
+ * scaffold arm, a validator arm, and a pod applier, so it scaffolds, validates,
+ * publishes and installs like the rest. (The old note here claimed it needed a
+ * CHECK-constraint migration "mirrored across ~24 files in 6 repos" — that was
+ * never true for `skill`: the category was ALREADY in `PACKAGE_TYPES` and in
+ * migration 0049's CHECK. What was missing was only the payload slot.)
+ */
+export declare const STANDALONE_KINDS: readonly ["view", "cell", "skill", "workflow", "capability"];
+export type StandaloneKind = (typeof STANDALONE_KINDS)[number];
+export interface StandalonePackageFile {
+    category: StandaloneKind;
+    slug: string;
+    displayName: string;
+    description?: string;
+    tags?: string[];
+    definition: PackageDefinitionLike;
+}
+/**
+ * True when a parsed JSON/YAML top-level object declares a standalone
+ * (non-workspace) `category`. A `WorkspaceYaml` file never carries a
+ * top-level `category` key (it uses `meta`/`workspace`), so this is a safe,
+ * non-overlapping discriminator `marketPublish` can branch on.
+ */
+export declare function isStandalonePackageFile(parsed: unknown): parsed is {
+    category: string;
+};
+/**
+ * Read + parse a standalone package file (JSON or YAML — the same
+ * JSON-superset parser `parseTemplateFile` uses). Throws a friendly Error,
+ * never `process.exit`.
+ */
+export declare function parseStandalonePackageFile(filePath: string): StandalonePackageFile;
+/**
+ * Minimal structural check BEFORE any network call — mirrors the fast
+ * author-feedback `marketValidate` gives workspace templates, scaled to what
+ * a standalone package actually needs: the `definition` must carry the array
+ * the CP's `packageDefinitionSchema` reads for that category. Returns an
+ * empty array when clean.
+ */
+export declare function validateStandalonePackage(pkg: StandalonePackageFile, opts?: {
+    baseDir?: string;
+}): string[];
+export interface ResolveCellCodeFilesResult {
+    definition: PackageDefinitionLike;
+    errors: string[];
+}
+/**
+ * Inline every cell's `codeFile` into `code` — the field the CP schema
+ * actually validates (`cells[].code: z.string().min(1)`, no `codeFile` slot).
+ * A no-op for anything but a `cell` package, and for a cell entry that has no
+ * `codeFile` (plain inline `code` is untouched).
+ *
+ * `codeFile` is bundled through the SAME esbuild path `cell build` uses
+ * (`buildCellFromSource`), so publishing from source needs no separate manual
+ * build step. `bundleDeps` defaults to `true` here — see `market-authoring.ts`
+ * `marketPublishStandalone` for why the DEFAULT flips only on this door.
+ * Author-declared `deps` on the cell entry win over the derived map, mirroring
+ * `cell build --deps`'s own override semantics.
+ *
+ * A cell declaring `rendererType: "mcp-app"` is built `--self-contained`
+ * instead, whatever `bundleDeps` says: its `code` is the complete HTML document
+ * a foreign MCP-Apps host loads verbatim (React, CSS and brand fonts inlined),
+ * and its `deps` is `{}` — that host's CSP admits no esm.sh, so an author
+ * `deps` on such a cell is refused rather than shipped inert.
+ */
+export declare function resolveCellCodeFiles(pkg: StandalonePackageFile, baseDir: string, opts?: {
+    bundleDeps?: boolean;
+}): Promise<ResolveCellCodeFilesResult>;
+/**
+ * The kinds `market scaffold --kind <k>` can write. This is the SSOT for that
+ * flag's accepted values AND for its help string (`src/index.ts`) — the two had
+ * drifted: the help advertised `skill` (which scaffold refuses) and hid
+ * `workflow` (which `validateStandalonePackage` has always accepted), so the
+ * documented loop offered a dead option and concealed a working one.
+ *
+ * `skill` joined this list when the CP grew its standalone `skill` payload slot
+ * and the pod grew an applier for it — before that, scaffold refused it because
+ * there was no publishable shape to write. The barrier is gone; the refusal
+ * went with it. (`SCAFFOLDABLE_KINDS` is still what the help string is built
+ * from, so the two cannot drift again — see `scaffold-kind-help-parity.test.ts`.)
+ */
+export declare const SCAFFOLDABLE_KINDS: readonly ["cell", "view", "workflow", "capability", "skill"];
+export type ScaffoldableKind = (typeof SCAFFOLDABLE_KINDS)[number];
+/**
+ * Build the minimal standalone-package JSON `market scaffold --kind
+ * cell|view|workflow|capability` writes — the smallest file that passes
+ * {@link validateStandalonePackage}, for the author to edit in place.
+ *
+ * The bar is USABLE, not merely valid. Every arm below has at least one field
+ * whose OMISSION is not neutral — the cell's `contentKind`/`viewTypes`, the
+ * workflow's `status`/`triggerType`/two-node flow — because the appliers
+ * default a missing value to something inert and report success. A scaffold
+ * that writes a file which installs and then does nothing is the same defect
+ * as a validator that passes a flow which never fires.
+ */
+export declare function scaffoldStandalonePackageJson(kind: ScaffoldableKind, slug: string): string;