primitive-admin 1.1.0 → 1.2.0-alpha.0

package/dist/src/lib/generated-config-surfaces.js

@@ -2265,6 +2265,23 @@ export function unknownRequestKeysMessage(keys) {
         `${keys.join(", ")}. This endpoint rejects keys it does not accept rather ` +
         "than ignoring them.");
 }
+// #3997 — the three type configs author their rule-set reference by name
+// (#2644): an id names a row in one app and resolves to nothing in another, so
+// a copied file failed instead of resolving. One sentence serves all three
+// tables. The `request` half is never surfaced: `ruleSetId` is the live body key
+// on all three routes, and both `rememberRetiredKeys` (`request-schema.ts`) and
+// the admin API's unknown-key path skip a key the schema accepts. It exists
+// because the interface requires both halves.
+const RULE_SET_ID_RETIRED = {
+    toml: "`ruleSetId` is no longer authored in TOML (#3997). A rule-set id names " +
+        "a row in one app and resolves to nothing in another, so the reference " +
+        'is authored by name: replace this line with `ruleSetName = "<name>"`, ' +
+        "where the name is the `name` the rule set's own `rule-sets/<key>.toml` " +
+        "declares, and push again. A file pulled since #2644 already spells it " +
+        "that way.",
+    request: "`ruleSetId` is the live request key on this surface; only its TOML " +
+        "spelling is retired (#3997). Send the rule set's id.",
+};
 export const RETIRED_CONFIG_KEYS = {
     // #2891 — the app-settings auth surface was reshaped so that `app.toml` can
     // state what the server holds. All five keys below stay DECLARED in
@@ -2381,6 +2398,12 @@ export const RETIRED_CONFIG_KEYS = {
                 "`primitive cron-triggers archive` to retire the trigger (#2907).",
         },
     },
+    // #3997 — keyed by each table's TOML prefix. Only `database-type-config`
+    // uses `[type]`, so that entry cannot reach another surface; the blob
+    // bucket's `[bucket] ruleSetId` is its live key and is not listed.
+    type: { ruleSetId: RULE_SET_ID_RETIRED },
+    groupTypeConfig: { ruleSetId: RULE_SET_ID_RETIRED },
+    collectionTypeConfig: { ruleSetId: RULE_SET_ID_RETIRED },
     // #2803 — the OBJECT-level availability leaves TOML. The per-version
     // `[[configs]] status` (`active | archived`) is a different question — which
     // named config is retired — and stays authorable.
@@ -2396,6 +2419,26 @@ export const RETIRED_CONFIG_KEYS = {
                 "`primitive prompts archive` to retire the prompt (#2907).",
         },
     },
+    // #3999 — the prompt `[[configs]]` table (its TOML path is `configs`; no
+    // other field table has that path — the workflow file's `[[configs]]` is a
+    // document key with its own retired list). The live-config marker has one
+    // spelling since #2645, `active`. The legacy `isActive` is refused rather
+    // than ignored: a file whose only marker it is would otherwise push without
+    // activating anything and leave a different config live.
+    configs: {
+        isActive: {
+            toml: "`isActive` is no longer accepted on a `[[configs]]` entry (#3999). " +
+                "The live-config marker has one spelling since #2645: write " +
+                "`active = true` on exactly one entry (pull writes it there), delete " +
+                "the `isActive` line and push again. The line is refused rather than " +
+                "ignored because a file that still carries it would otherwise leave a " +
+                "different config live.",
+            request: "`isActive` is not a config-body key (#3999). Which config a prompt " +
+                "runs is set through " +
+                "`POST …/prompts/{promptId}/configs/{configId}/activate`; omit the " +
+                "field.",
+        },
+    },
     integration: {
         status: {
             toml: "`status` is no longer authored in TOML (#2803), and `draft` no longer " +
@@ -7335,20 +7378,13 @@ export const PROMPT_SURFACE = {
                 // carry `active = true`; pull writes it on the active entry and push
                 // honors it on create AND update by calling the activate endpoint
                 // (activatePromptConfig). It is a control, never a key in the config
-                // body.
+                // body. It has one spelling (#3999, `retired-keys.ts`).
                 active: {
                     kind: "structural",
                     note: "Which config the prompt runs (#2645). Pull writes it on the " +
                         "active entry; push enacts it through the activate endpoint " +
                         "(activatePromptConfig), never as a config-body key.",
                 },
-                isActive: {
-                    kind: "structural",
-                    note: "Legacy spelling of `active` — the create leg read it before pull " +
-                        "ever wrote a marker. Declared here so the unrecognized-key " +
-                        "rejection does not fail a file that has always used it; pull " +
-                        "never writes it.",
-                },
                 // #3626 §4 — the nine chat keys in their pre-kind FLAT spelling.
                 ...DEPRECATED_FLAT_CHAT_KEYS,
             },
@@ -8517,7 +8553,8 @@ export const DATABASE_TYPE_SURFACE = {
                     emit: "always",
                     writableOn: BOTH,
                     // Authored as a portable name and sent as an id; the server checks
-                    // the set exists and has `resourceType: "database"`.
+                    // the set exists and has `resourceType: "database"`. The id
+                    // spelling is retired in TOML (#3997): `retired-keys.ts`, `type`.
                     validation: handledBy(DB_TYPE_HANDLER, "DatabaseTypeConfigController", "apply"),
                 },
                 {
@@ -8604,11 +8641,6 @@ export const DATABASE_TYPE_SURFACE = {
                 },
             },
             tomlOnlyKeys: {
-                ruleSetId: {
-                    kind: "deprecated",
-                    note: "The legacy id-based rule-set reference. Still accepted on push " +
-                        "so an unmigrated file pushes unchanged; pull writes `ruleSetName`.",
-                },
                 metadataAccess: {
                     kind: "deprecated",
                     note: "The legacy spelling of `celContextAccess`. Read on push when the " +
@@ -8785,8 +8817,8 @@ export const RULE_SET_SURFACE = {
  * `ruleSetName`, because a name is portable across apps and an id is not. The
  * name → id resolution is the CLI's (`config push` resolves against the app's
  * rule sets); the server validates that the id exists and has
- * `resourceType: "group"`. The legacy id spelling stays accepted on push and is
- * declared in `tomlOnlyKeys`.
+ * `resourceType: "group"`. The id spelling is refused on push (#3997), with
+ * the guidance in `retired-keys.ts`.
  */
 const GROUP_TYPE_HANDLER = "src/app-api/controllers/group-type-config-controller.ts";
 export const GROUP_TYPE_CONFIG_SURFACE = {
@@ -8815,7 +8847,9 @@ export const GROUP_TYPE_CONFIG_SURFACE = {
                     emit: "always",
                     writableOn: BOTH,
                     // Authored as a name, sent as an id; existence and resourceType are
-                    // checked server-side, and an empty value clears the reference.
+                    // checked server-side, and an empty value clears the reference. The
+                    // id spelling is retired in TOML (#3997): `retired-keys.ts`,
+                    // `groupTypeConfig`.
                     validation: handledBy(GROUP_TYPE_HANDLER, "GroupTypeConfigController", "apply"),
                 },
                 {
@@ -8855,13 +8889,7 @@ export const GROUP_TYPE_CONFIG_SURFACE = {
                     note: "User who created the config; assigned server-side.",
                 },
             },
-            tomlOnlyKeys: {
-                ruleSetId: {
-                    kind: "deprecated",
-                    note: "The legacy id-based rule-set reference. Still accepted on push " +
-                        "so an unmigrated file pushes unchanged; pull writes `ruleSetName`.",
-                },
-            },
+            tomlOnlyKeys: {},
             responseOnlyKeys: {},
         },
     ],
@@ -8908,7 +8936,9 @@ export const COLLECTION_TYPE_CONFIG_SURFACE = {
                     emit: "always",
                     writableOn: BOTH,
                     // Authored as a name, sent as an id; existence and resourceType are
-                    // checked server-side, and an empty value clears the reference.
+                    // checked server-side, and an empty value clears the reference. The
+                    // id spelling is retired in TOML (#3997): `retired-keys.ts`,
+                    // `collectionTypeConfig`.
                     validation: handledBy(COLLECTION_TYPE_HANDLER, "CollectionTypeConfigController", "apply"),
                 },
             ],
@@ -8938,13 +8968,7 @@ export const COLLECTION_TYPE_CONFIG_SURFACE = {
                     note: "User who created the config; assigned server-side.",
                 },
             },
-            tomlOnlyKeys: {
-                ruleSetId: {
-                    kind: "deprecated",
-                    note: "The legacy id-based rule-set reference. Still accepted on push " +
-                        "so an unmigrated file pushes unchanged; pull writes `ruleSetName`.",
-                },
-            },
+            tomlOnlyKeys: {},
             responseOnlyKeys: {},
         },
     ],