primitive-admin 1.1.0-alpha.73 → 1.1.0-alpha.75

package/dist/src/commands/sync.d.ts

@@ -662,6 +662,20 @@ export declare function serializeBlobBucket(bucket: any, logger?: (message: stri
  * drift.
  */
 export declare function buildBlobBucketUpdatePayload(bucket: any): any;
+/**
+ * The status a freshly CREATED prompt config still owes the file, or null
+ * (#3201).
+ *
+ * `status` is update-only — `POST /prompts` and `POST /prompts/:id/configs`
+ * both assign `active` whatever the body says — so an authored
+ * `status = "archived"` was silently dropped on every create path: a pulled
+ * tree pushed from a clean clone into a fresh environment brought every
+ * retired config back into service. Read through the push payload builder, so
+ * a file that omits the key asks for the default and needs no request.
+ */
+export declare function createdConfigStatusPatch(tomlConfig: any): {
+    status: string;
+} | null;
 /**
  * Which `[[configs]]` entry a prompt file marks as live (issue #2645).
  *
@@ -767,6 +781,13 @@ export declare function buildPromptCreatePayload(key: string, tomlData: any): Re
  * `seededConfigName` is what the server called it — read from the create
  * response rather than assumed, so a handler that one day honors the name
  * produces no needless PATCH.
+ *
+ * #3201 — the entry's `status` is deferred the OTHER way and is deliberately
+ * not here. The create points the prompt's `activeConfigId` at this seeded
+ * config, so retiring it in this early patch would archive the config the
+ * prompt is serving from and leave it there until the marked entry is created
+ * and activated — a window a failed create or activation freezes. It is
+ * applied after activation instead (`createdConfigStatusPatch`).
  */
 export declare function seededOnlyPromptConfigFields(firstConfig: any, seededConfigName?: string): Record<string, any> | null;
 /**
@@ -1700,7 +1721,7 @@ export declare function configSemanticHash(label: string, filePath: string, maps
 /**
  * The sync state `config push` writes into (#2731 B6, closing #2374).
  *
- * `loadSyncState` answers `null` for an absent `.primitive-sync.json`, and
+ * `loadSyncState` answers `null` for an absent sync-state baseline, and
  * every per-entity state write in the push loops is guarded by `if (syncState)`
  * — so a first push created every resource and recorded none of them. The next
  * push then re-entered the create path for everything and depended on 409
@@ -1881,6 +1902,48 @@ selects?: (name: string) => boolean): Promise<{
     /** Names the server listed, empty when the listing failed. */
     serverKeys: string[];
 }>;
+/**
+ * Pull server-side `ServerFunction` rows into `functions/` (#3179).
+ *
+ * Two things make this different from every other type's pull:
+ *
+ *   1. **A function is more than its file.** The active config VERSION holds an
+ *      envelope with the authored TOML bytes and every source file, so the pull
+ *      writes `functions/<key>.toml` plus the TypeScript beside it, and records
+ *      the source paths so prune can remove the code with the function.
+ *   2. **Bytes, not a re-serialization.** The stored TOML is written verbatim,
+ *      so comments, key order and line endings survive the round trip (F-009).
+ *      A function that has never had code pushed has no stored bytes; that one
+ *      gets a canonical serialization of its header, which is still a pushable
+ *      file.
+ *
+ * A stored source path is never trusted: `planFunctionPull` refuses one that
+ * normalizes outside the tree, and the refusals are reported rather than
+ * swallowed.
+ */
+export declare function pullFunctions(client: ApiClient, appId: string, configDir: string, logger?: (msg: string) => void, selects?: (key: string) => boolean): Promise<{
+    functionEntities: Record<string, {
+        id: string;
+        modifiedAt: string;
+        contentHash?: string;
+        semanticHash?: string;
+        envelopeHash?: string;
+        activeConfigId?: string;
+        sources?: string[];
+    }>;
+    count: number;
+    presence: PresenceOutcome;
+    listOk: boolean;
+    serverKeys: string[];
+    /**
+     * Everything the server listed, archived rows included. Pull exports no file
+     * for a tombstone, so without the row here the archived function would be
+     * stranded: no file to delete and no managed key to prune, and its key would
+     * go on blocking the app's whole namespace with nothing able to reclaim it.
+     * The caller folds these into the state through `archivedTombstoneEntries`.
+     */
+    items: any[];
+}>;
 /** The outcome of one block's test-case pull (#2769). */
 export type TestCasePullOutcome = 
 /** The listing succeeded; `count` cases were written and stale files removed. */
@@ -2287,7 +2350,7 @@ export declare function applyTestCasePrune(params: {
  * `registerConfigCommands` created rather than making one of its own.
  *
  * The module keeps its name and its ~50 exported helpers: `sync.ts`,
- * `resolveSyncDir`, `.primitive-sync.json` and `.primitive/sync/<env>/<appId>/`
+ * `resolveSyncDir`, the sync-state baseline and `primitive/<env>/`
  * are internal identifiers, deliberately left alone (#2759 scope).
  */
 export declare function registerConfigSyncCommands(sync: Command): void;