@synap-core/cli 1.13.0 → 1.13.1-next.20261102.3a66eb1

package/dist/commands/market.d.ts

@@ -22,10 +22,11 @@
  * handle fall back to a route-to-browser message.
  */
 import { type CatalogEntry, type TemplateUpdateCheck } from "@synap-core/workspace-templates";
+import { type HubConfig } from "../lib/hub-client.js";
 import { type PackageFilters, type TierInfo } from "../lib/cp-packages.js";
 import { type InstalledKind, type InstalledRow, type InstalledTemplateInfo, type WorkspaceAttachment } from "../lib/installed.js";
 import { type TemplateUpdateStep } from "../lib/template-steps.js";
-import { type PendingDataChanges } from "../lib/template-lifecycle.js";
+import { type DataChange, type PendingDataChanges } from "../lib/template-lifecycle.js";
 export interface MarketCatalog {
     entries: CatalogEntry[];
     tierBySlug: Map<string, TierInfo>;
@@ -218,8 +219,8 @@ export interface ApplyVerdict {
  */
 export declare function podApplyState(res: Record<string, unknown>): "not-finished" | "awaiting-approval" | null;
 /**
- * The verdict of one `/packages/apply` response — the ONE reader both
- * `marketInstall` and `applyOnePackage` call. Layer 2's outcome comes from the
+ * The verdict of one `/packages/apply` response — the ONE reader
+ * `marketInstall` calls. Layer 2's outcome comes from the
  * pod's own state (`podApplyState`): an apply the pod says is unfinished is
  * never "updated", and never a stamp contradiction (the pod held the version
  * on purpose — redeploying fixes nothing).
@@ -230,12 +231,11 @@ export declare function classifyApplyResponse(entry: CatalogEntry, res: Record<s
     stampVerified?: boolean | null;
 }): ApplyVerdict;
 /**
- * Classify one `/packages/apply` response into the honest verdict both
- * `marketInstall` and `applyOnePackage` print (and both put in `--json`).
+ * Classify one `/packages/apply` response into the honest verdict
+ * `marketInstall` prints (and puts in `--json`).
  * `wasUnstamped` = the slug was already installed with no recorded version
  * BEFORE this call (only `marketInstall` can detect this today — see its
- * `fetchInstalledTemplates` call; `applyOnePackage` only ever re-applies
- * already-versioned slugs, so it always passes `false`).
+ * `fetchInstalledTemplates` call).
  */
 export declare function classifyApplyResult(entry: CatalogEntry, ws: WorkspaceApplyResult | undefined, dependencies: ResolvedDependencyLike[] | undefined, seedSummary: SeedSummary | undefined, ctx: {
     remoteVersionSent?: string;
@@ -266,7 +266,7 @@ export declare function deferredPlacementLines(res: Record<string, unknown>): st
  * older pod that does not say).
  */
 export declare function heldVersionLine(res: Record<string, unknown>): string | null;
-/** Render a `classifyApplyResult` verdict — the ONE honest-text door for both `marketInstall` and `applyOnePackage`. */
+/** Render a `classifyApplyResult` verdict — the ONE honest-text door of `marketInstall`. */
 export declare function printApplyVerdict(entry: CatalogEntry, verdict: ApplyVerdict): void;
 export declare function market(opts: {
     list?: boolean;
@@ -325,28 +325,34 @@ export interface UpdateCheck extends TemplateUpdateCheck {
      * see `InstalledTemplateInfo.version`'s doc in `lib/installed.ts`.
      */
     noVersionInfo: boolean;
-    /** The installed row's kind (absent = `"workspace"`, the only kind an older pod reports). Picks the update door — see {@link updateDoorFor}. */
+    /** The installed row's kind (absent = `"workspace"`, the only kind an older pod reports). */
     kind?: InstalledKind;
+    /** The pod's reason when it could not compare this package (`market update`). */
+    reason?: string;
 }
 /**
- * Which pod door UPDATES an installed package of this kind, or `null` when the
- * pod has no per-package updater for it.
- *
- * ⚠️ Never default to `/packages/apply`. That is the WORKSPACE door: it mints a
- * workspace for any body carrying a `_meta.slug`. On 2026-10-12 `market update`
- * sent the `creative-director` SKILL through it and the pod created an empty
- * "New Workspace" — the update-time twin of the 2026-09-05 install bug that
- * {@link declaredCategoryOf} fixed.
- *
- *  - view / skill / automation converge through the source-linked 3-way-merge
- *    reconcile (`POST /configs/reconcile`) — the SAME comparator whose dry run
- *    marked the row drifted (`GET /installed?drift`). Re-running `market.install`
- *    is not an update: the skill arm always creates (unique slug ⇒ fails), the
- *    automation arm returns "reused".
- *  - cell / capability have no per-package updater here: `null`.
+ * The slugs with an update that `synap market update <slug>` can apply. Every
+ * installed kind (space, capability, view, skill, automation) updates through
+ * the pod's ONE update door (`POST /package-updates/{slug}/apply`), so every
+ * slug with an update is offered; what only the person can do is said by the
+ * pod at apply time (`NEEDS_PERSON`), never guessed here. Next-step
+ * suggestions use it.
+ */
+export declare function cliUpdatableSlugs(checks: ReadonlyArray<{
+    slug: string;
+    kind?: InstalledKind;
+    updateAvailable: boolean;
+}>): string[];
+/** The status of an update left for the person to apply in pod admin (not a failure). */
+export declare const APPLY_IN_POD_ADMIN = "apply-in-pod-admin";
+/**
+ * Where the person finishes ONE package's update: pod admin's review page for
+ * it (`/marketplace/updates/<slug>`), when the pod-admin origin derives from
+ * the pod's; else the pod's own link (`reviewUrl`, pod-relative
+ * `/open/update/<slug>`, which the pod sends on to pod admin); else the
+ * Updates tab's words.
  */
-export type UpdateDoor = "packages-apply" | "configs-reconcile";
-export declare function updateDoorFor(kind: InstalledKind | undefined): UpdateDoor | null;
+export declare function packageReviewLink(podUrl: string, slug: string, reviewUrl?: unknown): string | undefined;
 /**
  * Per-installed-slug drift check. SERVER-FIRST: when the pod runs the
  * server-side TemplateHealth code (Hub `/workspaces` returns `drifted`/
@@ -363,6 +369,55 @@ export declare function updateDoorFor(kind: InstalledKind | undefined): UpdateDo
 export declare function computeUpdates(installedTemplates: InstalledTemplateInfo[], cat: MarketCatalog): UpdateCheck[];
 /** First check per slug, order preserved — an update is applied per PACKAGE, not per installed object. */
 export declare function dedupeBySlug(checks: UpdateCheck[]): UpdateCheck[];
+/** One update's outcome, as `market update` reports it. */
+export interface UpdateApplyResult {
+    slug: string;
+    outcome: string;
+    /** The coarse status the summary counts (see `summarizeApplyResults`). */
+    status: string;
+    warnings: string[];
+    error?: string;
+    /** The catalog definition's failing fields, when the pod refused it. */
+    fieldErrors?: Record<string, string[]>;
+    /** Set when the update was filed for the person's approval. */
+    proposalId?: string;
+    proposalIds?: string[];
+    /** Where the person approves it, or finishes it on pod admin. */
+    reviewUrl?: string;
+    pendingDataChanges?: DataChange[];
+}
+/**
+ * Apply ONE installed package's update through the pod's ONE update door,
+ * `POST /package-updates/{slug}/apply`, whatever its kind (space, capability,
+ * view, skill, automation) and whoever holds the key. The pod applies the
+ * rule (backend `services/package-updates/`): a person's apply lands; an
+ * agent key's is filed for the person's approval (`proposed`) and lands when
+ * they approve it; what only the person can do (agree to changes to existing
+ * records, choose for a field both sides changed, change a view) is
+ * `NEEDS_PERSON` / `CHOICES_NEEDED` with that package's review page. An
+ * older pod that refuses an agent here (403, no `reasonCode`) keeps today's
+ * line: to apply in pod admin.
+ */
+export declare function applyUpdateThroughDoor(c: {
+    slug: string;
+    kind?: InstalledKind;
+    latestVersion?: string;
+}, cfg: HubConfig, opts: {
+    json?: boolean;
+}, applyTimeoutMs?: number, acceptDataChanges?: string[]): Promise<UpdateApplyResult>;
+/**
+ * Where the person approves a filed update: pod admin's proposal page, the
+ * approval door (`/proposal/<id>`), when the pod-admin origin derives from the
+ * pod's; else the link the pod sent (`reviewUrl`); else nothing.
+ */
+export declare function approvalLink(podUrl: string, proposalId: string | undefined, reviewUrl: unknown): string | undefined;
+/**
+ * Where the person applies a package update a limited key may not apply
+ * (a computer key's grant leaves out `workspace.update`, by design: applying a
+ * workspace package is the person's act). Pod admin's Marketplace, Updates
+ * tab, named by URL when the pod-admin origin derives from the pod's.
+ */
+export declare function marketUpdatesDoor(podUrl: string): string;
 export declare function marketUpdate(slugsArg: string[] | undefined, opts: {
     /** The literal `--yes` flag: apply every update AND agree to every data change listed. */
     yes?: boolean;
@@ -377,16 +432,18 @@ export declare function marketUpdate(slugsArg: string[] | undefined, opts: {
     timeout?: string;
 }): Promise<void>;
 /**
- * One-line rollup over a batch of `applyOnePackage` outcomes — computed from
- * the SAME per-item `status` (`classifyApplyResult`'s honest verdict) the
+ * One-line rollup over a batch of update outcomes (`applyUpdateThroughDoor`) — computed from
+ * the SAME per-item `status` the
  * loop already collects, not a separate tally. `"installed"`/`"updated"`/
  * `"composed"`/`"legacy-unknown"` count as a clean update, `"unchanged"` as
  * already-current, the `*-with-failures` and `"stamp-contradiction"` statuses
  * get their OWN bucket — a partial capability-seed failure or a stamp that
  * silently didn't take is never folded into a clean "updated" count.
- * `"timed-out"` is broken out from the generic `"failed"` bucket; everything
- * else (locked/proposed/fetch-failed/not-in-catalog/no-workspace/unknown)
- * rolls into "failed".
+ * `"timed-out"` is broken out from the generic `"failed"` bucket;
+ * `"proposed"`/`"awaiting-approval"` count as waiting for the person's
+ * approval (never failed); everything else
+ * (locked/fetch-failed/not-in-catalog/no-workspace/unknown) rolls into
+ * "failed".
  */
 export declare function summarizeApplyResults(results: Array<{
     slug: string;
@@ -399,6 +456,7 @@ export declare function summarizeApplyResults(results: Array<{
     timedOut: number;
     proposed: number;
     needsConsent: number;
+    toApplyInPodAdmin: number;
     line: string;
 };
 /**