@cat-factory/app 0.233.0 → 0.234.0

package/app/components/settings/TaskTypeSuppressionsPanel.vue

@@ -0,0 +1,119 @@
+<script setup lang="ts">
+// Workspace settings: which of the deployment's REUSABLE OPERATIONS this board offers
+// (`backend/docs/reusable-operations.md`). An org registers its operations process-wide, so a
+// team that runs three of twenty needs a way to clear the rest out of its create picker.
+//
+// The list comes from its OWN read, not from the board snapshot's `customTaskTypes`: a suppressed
+// operation is by construction absent from that catalog, so this screen is the only surface that
+// can offer the way back. Every write answers with the whole list AND invalidates the catalog the
+// picker renders, so a change is followed by a board refresh rather than a local patch.
+//
+// Labels and descriptions are DEPLOYMENT-authored English rendered verbatim (the descriptor
+// convention); only the chrome around them is i18n.
+import { onMounted, ref } from 'vue'
+import type { TaskTypeSuppression } from '~/types/domain'
+
+const { t } = useI18n()
+const api = useApi()
+const workspace = useWorkspaceStore()
+const toast = useToast()
+
+const rows = ref<TaskTypeSuppression[]>([])
+const loading = ref(false)
+/** The single id being written, so only its own switch shows the pending state. */
+const busyId = ref<string | null>(null)
+
+onMounted(() => void load())
+
+async function load() {
+  if (!workspace.workspaceId) return
+  loading.value = true
+  try {
+    rows.value = (await api.listTaskTypeSuppressions(workspace.requireId())).taskTypes
+  } catch (e) {
+    fail(e)
+  } finally {
+    loading.value = false
+  }
+}
+
+/**
+ * Flip one operation. The board snapshot's task-type catalog is derived from this state, so a
+ * successful write refreshes the workspace: leaving it stale would keep offering a hidden
+ * operation in the create picker until the next unrelated reload.
+ */
+async function toggle(row: TaskTypeSuppression, offered: boolean) {
+  const id = row.taskType.taskType
+  busyId.value = id
+  try {
+    const result = offered
+      ? await api.restoreTaskType(workspace.requireId(), id)
+      : await api.suppressTaskType(workspace.requireId(), id)
+    rows.value = result.taskTypes
+    await workspace.refresh()
+  } catch (e) {
+    fail(e)
+  } finally {
+    busyId.value = null
+  }
+}
+
+function fail(e: unknown) {
+  toast.add({
+    title: t('settings.taskTypeSuppressions.saveFailed'),
+    description: e instanceof Error ? e.message : String(e),
+    icon: 'i-lucide-triangle-alert',
+    color: 'error',
+  })
+}
+</script>
+
+<template>
+  <div class="space-y-4">
+    <p class="text-xs text-slate-400">
+      {{ t('settings.taskTypeSuppressions.intro') }}
+    </p>
+
+    <p v-if="loading" class="text-[11px] text-slate-500">
+      {{ t('settings.taskTypeSuppressions.loading') }}
+    </p>
+    <p v-else-if="!rows.length" class="text-[11px] text-slate-500">
+      {{ t('settings.taskTypeSuppressions.empty') }}
+    </p>
+    <ul v-else class="space-y-2" data-testid="task-type-suppressions">
+      <li
+        v-for="row in rows"
+        :key="row.taskType.taskType"
+        class="flex items-start justify-between gap-3 rounded border border-slate-800 px-3 py-2"
+        data-testid="task-type-suppression"
+        :data-task-type="row.taskType.taskType"
+      >
+        <div class="min-w-0">
+          <div class="flex items-center gap-1.5">
+            <UIcon :name="row.taskType.presentation.icon" class="h-3.5 w-3.5 shrink-0" />
+            <span class="truncate text-xs font-medium text-slate-200">
+              {{ row.taskType.presentation.label }}
+            </span>
+            <UBadge
+              v-if="row.taskType.presentation.category"
+              color="neutral"
+              variant="subtle"
+              size="sm"
+            >
+              {{ row.taskType.presentation.category }}
+            </UBadge>
+          </div>
+          <p class="mt-0.5 text-[11px] text-slate-500">
+            {{ row.taskType.presentation.description }}
+          </p>
+        </div>
+        <USwitch
+          :model-value="!row.suppressed"
+          :loading="busyId === row.taskType.taskType"
+          :aria-label="t('settings.taskTypeSuppressions.offer')"
+          @update:model-value="(offered: boolean) => toggle(row, offered)"
+        />
+      </li>
+    </ul>
+  </div>
+</template>

package/app/components/settings/WorkspaceSettingsPanel.vue

@@ -15,6 +15,7 @@ import type { InputGateMode, ReviewFrictionMode, TaskLimitMode } from '~/types/d
 import RiskPolicyPanel from '~/components/settings/RiskPolicyPanel.vue'
 import IssueTrackerPanel from '~/components/settings/IssueTrackerPanel.vue'
 import ServiceFragmentDefaultsPanel from '~/components/settings/ServiceFragmentDefaultsPanel.vue'
+import TaskTypeSuppressionsPanel from '~/components/settings/TaskTypeSuppressionsPanel.vue'
 import BudgetSettings from '~/components/settings/BudgetSettings.vue'
 import UsageSettings from '~/components/settings/UsageSettings.vue'
 import WorkspaceMembersSettings from '~/components/layout/WorkspaceMembersSettings.vue'
@@ -29,6 +30,10 @@ const workspace = useWorkspaceStore()
 const access = useWorkspaceAccess()
 const toast = useToast()
 const slots = useReactiveSlots<AppSlots>()
+// Whether the deployment registers any reusable operation at all, hidden or not, so the
+// Operations tab exists only where there is something for it to manage. Not the OFFERED catalog:
+// hiding the last operation would then take away the only screen that un-hides one.
+const taskTypes = useTaskTypesStore()
 
 // The Metadata tab exists only where the deployment DECLARES custom fields — an unwired
 // capability is invisible, not an empty tab in every deployment. Declared-but-malformed fields
@@ -86,6 +91,18 @@ const tabs = computed(() => [
     icon: 'i-lucide-book-open-check',
     slot: 'fragments',
   },
+  // Which of the deployment's reusable operations this board offers. Only where the deployment
+  // registers any: on the stock product the tab would name a catalog that does not exist.
+  ...(taskTypes.hasRegisteredOperations
+    ? [
+        {
+          value: 'operations',
+          label: t('settings.workspaceSettings.tabs.operations'),
+          icon: 'i-lucide-plug',
+          slot: 'operations',
+        },
+      ]
+    : []),
   ...(hasMetadataFields.value
     ? [
         {
@@ -605,6 +622,11 @@ async function save() {
           <ServiceFragmentDefaultsPanel />
         </template>
 
+        <!-- Reusable operations this board offers (only where the deployment registers any) -->
+        <template v-if="taskTypes.hasRegisteredOperations" #operations>
+          <TaskTypeSuppressionsPanel />
+        </template>
+
         <!-- Custom workspace metadata (only where the deployment declares fields) -->
         <template v-if="hasMetadataFields" #metadata>
           <WorkspaceMetadataSettings />

package/app/composables/api/taskTypeSuppressions.ts

@@ -0,0 +1,25 @@
+import {
+  listTaskTypeSuppressionsContract,
+  restoreTaskTypeContract,
+  suppressTaskTypeContract,
+} from '@cat-factory/contracts'
+import type { ApiContext } from './context'
+
+/**
+ * Which of the deployment's REUSABLE OPERATIONS this board offers
+ * (`backend/docs/reusable-operations.md`). Every call answers with the WHOLE list, because the
+ * board snapshot's `customTaskTypes` changes with it: hiding one removes it from the picker's own
+ * catalog, so a point response would leave the caller reconciling against data it just invalidated.
+ */
+export function taskTypeSuppressionsApi({ send, ws }: ApiContext) {
+  return {
+    listTaskTypeSuppressions: (workspaceId: string) =>
+      send(listTaskTypeSuppressionsContract, { pathPrefix: ws(workspaceId) }),
+
+    suppressTaskType: (workspaceId: string, taskType: string) =>
+      send(suppressTaskTypeContract, { pathPrefix: ws(workspaceId), pathParams: { taskType } }),
+
+    restoreTaskType: (workspaceId: string, taskType: string) =>
+      send(restoreTaskTypeContract, { pathPrefix: ws(workspaceId), pathParams: { taskType } }),
+  }
+}

package/app/composables/useApi.ts

@@ -4,6 +4,7 @@ import type { ApiContext } from './api/context'
 import { accountsApi } from './api/accounts'
 import { agentPromptsApi } from './api/agentPrompts'
 import { agentSettingsApi } from './api/agentSettings'
+import { taskTypeSuppressionsApi } from './api/taskTypeSuppressions'
 import { platformObservabilityApi } from './api/platformObservability'
 import { reportsApi } from './api/reports'
 import { authApi } from './api/auth'
@@ -144,6 +145,7 @@ export function useApi() {
     ...presetsApi(ctx),
     ...agentPromptsApi(ctx),
     ...agentSettingsApi(ctx),
+    ...taskTypeSuppressionsApi(ctx),
     ...preflightsApi(ctx),
     ...publicApiKeysApi(ctx),
     ...sharedStacksApi(ctx),

package/app/composables/usePipelineHealth.spec.ts

@@ -37,6 +37,7 @@ function scan(
   pipelines: Pipeline[],
   versions: Record<string, number> = {},
   retired: { id: string; replacedBy?: string }[] = [],
+  names: Record<string, string> = {},
 ) {
   const store = usePipelinesStore()
   const retiredIds = new Set(retired.map((r) => r.id))
@@ -46,7 +47,7 @@ function scan(
       ...versions,
     }).filter(([id]) => !retiredIds.has(id)),
   )
-  store.hydrate(pipelines, catalogVersions, retired)
+  store.hydrate(pipelines, catalogVersions, retired, names)
   return usePipelineHealth()
 }
 
@@ -202,6 +203,19 @@ describe('usePipelineHealth', () => {
     expect(outdated.value).toHaveLength(0)
   })
 
+  it("names an un-adopted catalog entry from the catalog's own name map, not its id", () => {
+    // The case that made the humanised fallback wrong: a deployment's registered pipeline behind a
+    // reusable operation. `pl_org_introduce_api` humanises to "org introduce api", a name that
+    // appears nowhere else in the product, and this advisory is shown on exactly the boards that
+    // predate the operation. With the map, the offer reads as the pipeline actually is.
+    const stored = builtin(['coder', 'reviewer'], { id: 'pl_full', version: 1 })
+    const { newPipelines } = scan([stored], { pl_full: 1, pl_org_introduce_api: 1 }, [], {
+      pl_full: 'Full build',
+      pl_org_introduce_api: 'Introduce API',
+    })
+    expect(newPipelines.value).toEqual([{ id: 'pl_org_introduce_api', name: 'Introduce API' }])
+  })
+
   it('reports no new pipelines when every catalog id is already stored', () => {
     const stored = builtin(['coder', 'reviewer'], { id: 'pl_full', version: 1 })
     const { newPipelines, hasIssues } = scan([stored], { pl_full: 1 })

package/app/composables/usePipelineHealth.ts

@@ -57,12 +57,17 @@ export interface NewPipeline {
 }
 
 /**
- * A built-in's display name for the "new pipeline" advisory, humanised from its catalog id
- * (`pl_review` -> "review", rendered capitalised) — used only until the row is reseeded into
- * existence, at which point its real catalog name is stored. Mirrors `useRiskPolicyHealth`.
+ * A catalog entry's display name for the "new pipeline" advisory, used only while the entry has no
+ * stored row to take a name off. The snapshot's companion name map answers it; the humanised id
+ * (`pl_review` -> "review", rendered capitalised) is the FALLBACK for a facade that ships no map.
+ *
+ * The map is not a nicety. Humanising was fine for the shipped built-ins, whose ids read as their
+ * names, and wrong the moment a deployment registers its own: a reusable operation's
+ * `pl_org_introduce_api` was offered as "org introduce api", a name appearing nowhere else in the
+ * product, on exactly the boards that predate the operation and therefore see this advisory.
  */
-function builtinPipelineName(id: string): string {
-  return id.replace(/^pl_/, '').replace(/_/g, ' ')
+function builtinPipelineName(id: string, names: Record<string, string>): string {
+  return names[id] ?? id.replace(/^pl_/, '').replace(/_/g, ' ')
 }
 
 /** Producers a companion kind is allowed to review (inverse of {@link COMPANION_FOR_PRODUCER}). */
@@ -207,7 +212,7 @@ export function usePipelineHealth() {
     const storedIds = new Set(store.pipelines.map((p) => p.id))
     return Object.keys(store.catalogVersions)
       .filter((id) => !storedIds.has(id))
-      .map((id) => ({ id, name: builtinPipelineName(id) }))
+      .map((id) => ({ id, name: builtinPipelineName(id, store.catalogNames) }))
   })
 
   // Retired built-ins this workspace still stores: the ones seeded before the withdrawal. A
@@ -238,7 +243,8 @@ export function usePipelineHealth() {
   function resolveReplacement(id: string): { id: string; name: string } | undefined {
     const stored = store.getPipeline(id)
     if (stored) return { id, name: stored.name }
-    if (id in store.catalogVersions) return { id, name: builtinPipelineName(id) }
+    if (id in store.catalogVersions)
+      return { id, name: builtinPipelineName(id, store.catalogNames) }
     return undefined
   }
 

package/app/docs/consumer-extensions.md

@@ -206,7 +206,13 @@ stray `API delivery` / `API Delivery` pair does not split a category in half.
 
 Your own strings (labels, category captions, descriptions) are rendered verbatim and never enter a
 locale catalog; only the platform's own chrome around them is i18n, which is why the "Other" heading
-is the one caption you do not supply. Each row carries `data-testid="task-type-row"` plus
+is the one caption you do not supply.
+
+**A workspace admin can HIDE any registered type from that board** (Workspace settings → Operations).
+Only backend-REGISTERED types are hideable: a type your frontend module ships as a code
+contribution has no backend row to suppress, so it is offered on every board. If your catalog is
+large enough that teams will want to trim it, register the types on the backend rather than
+contributing them here. Each row carries `data-testid="task-type-row"` plus
 `data-task-type-row="<id>"`, and each choice `data-testid="task-type-<taskType>"`, so your own e2e
 suite can address a row and the caption inside it.
 

package/app/stores/pipelines.ts

@@ -32,6 +32,13 @@ export const usePipelinesStore = defineStore('pipelines', () => {
    * a newer definition available (see `usePipelineHealth`).
    */
   const catalogVersions = ref<Record<string, number>>({})
+  /**
+   * The catalog's own NAME per id in {@link catalogVersions}, from the same snapshot field pair.
+   * Read only where a catalog entry has no stored row to take a name off (the "new built-ins"
+   * advisory and the replacement a retirement points at); everywhere else the stored row's authored
+   * name is the answer. Empty for a facade that ships no name map.
+   */
+  const catalogNames = ref<Record<string, string>>({})
   /**
    * Built-in pipelines WITHDRAWN from the catalog (`retiredPipelines()`), from the workspace
    * snapshot. A stored pipeline whose id appears here is no longer relevant and can be REMOVED —
@@ -75,18 +82,27 @@ export const usePipelinesStore = defineStore('pipelines', () => {
   const editingId = ref<string | null>(null)
 
   /**
-   * Replace the cached pipelines (and the current built-in catalog versions + retirements) from a
-   * snapshot. `retired` is applied even when EMPTY, unlike `versions`: an absent list means the
-   * facade shipped no retirements, and carrying the previous board's forward would offer a delete
-   * for a pipeline this deployment still ships.
+   * Replace the cached pipelines (and the current built-in catalog versions + names +
+   * retirements) from a snapshot. `retired` is applied even when EMPTY, unlike `versions`: an
+   * absent list means the facade shipped no retirements, and carrying the previous board's forward
+   * would offer a delete for a pipeline this deployment still ships. `names` rides `versions`,
+   * being the other half of one read.
    */
   function hydrate(
     next: Pipeline[],
     versions?: Record<string, number>,
     retired?: RetiredPipelineWire[],
+    names?: Record<string, string>,
   ) {
     pipelines.value = next
-    if (versions) catalogVersions.value = versions
+    // The two catalog maps move TOGETHER, because they are one snapshot read split in two and are
+    // keyed identically by construction. Assigning names on their own truthiness would let a
+    // facade that ships versions and no names leave the previous board's names indexed against
+    // this board's ids, which is the one way the pair can disagree.
+    if (versions) {
+      catalogVersions.value = versions
+      catalogNames.value = names ?? {}
+    }
     retiredPipelines.value = retired ?? []
   }
 
@@ -133,6 +149,7 @@ export const usePipelinesStore = defineStore('pipelines', () => {
   return {
     pipelines,
     catalogVersions,
+    catalogNames,
     retiredPipelines,
     gateConfigForms,
     draft,

package/app/stores/taskTypes.spec.ts

@@ -86,6 +86,35 @@ describe('taskTypes store — custom task-type catalog (extension slice B)', ()
     expect(isKnownTaskType('acme:ws1')).toBe(false)
   })
 
+  it('still reports registered operations when the board has hidden every one of them', () => {
+    // The regression this exists for: the workspace-settings Operations tab was gated on the
+    // OFFERED catalog, which suppression empties. Hiding the last operation therefore removed the
+    // only screen that un-hides one, and nothing failed: the tab simply was not there.
+    const store = useTaskTypesStore()
+    expect(store.hasRegisteredOperations).toBe(false)
+
+    hydrate(store, [backendType('acme:kept'), backendType('acme:hidden')])
+    store.hydrateSuppressed([])
+    expect(store.hasRegisteredOperations).toBe(true)
+
+    // Every registered operation hidden: the offered catalog is empty and the screen must remain.
+    hydrate(store, [])
+    store.hydrateSuppressed(['acme:kept', 'acme:hidden'])
+    expect(store.customTaskTypes).toEqual([])
+    expect(store.hasRegisteredOperations).toBe(true)
+  })
+
+  it('drops the previous board’s suppressions on re-hydrate (per-workspace state)', () => {
+    // Assigned unconditionally rather than on truthiness: carrying a hidden list forward would
+    // leave the Operations tab standing on a board that registers nothing.
+    const store = useTaskTypesStore()
+    hydrate(store, [])
+    store.hydrateSuppressed(['acme:ws1'])
+    expect(store.hasRegisteredOperations).toBe(true)
+    store.hydrateSuppressed([])
+    expect(store.hasRegisteredOperations).toBe(false)
+  })
+
   it('get() returns the full registration (for the create-form field descriptors)', () => {
     const store = useTaskTypesStore()
     hydrate(store, [

package/app/stores/taskTypes.ts

@@ -28,6 +28,11 @@ export const useTaskTypesStore = defineStore('taskTypes', () => {
   // The active per-workspace capability manifest (shared with the agents store), or null before
   // the first hydrate. This store reads only its own `taskTypes` slot off it.
   const capabilitiesManifest = ref<RemoteModuleManifest<AppSlots> | null>(null)
+  // The BACKEND-registered ids this board HIDES (`snapshot.suppressedTaskTypes`). Not part of the
+  // catalog above by construction (a suppressed type must not be creatable), but the board did
+  // decide about it, and that decision is the difference between a deployment with no operations
+  // and one whose operations are all hidden. See {@link hasRegisteredOperations}.
+  const suppressedTaskTypes = ref<string[]>([])
 
   /**
    * The merged CUSTOM task types (consumer-slot → backend-manifest), de-duplicated and never
@@ -47,6 +52,23 @@ export const useTaskTypesStore = defineStore('taskTypes', () => {
     return out
   })
 
+  /**
+   * Whether this deployment registers any REUSABLE OPERATION on the backend, hidden or not: what
+   * decides whether the workspace-settings Operations tab exists.
+   *
+   * Deliberately NOT `customTaskTypes.length`. That list is what the board OFFERS, so hiding the
+   * last operation empties it and the tab that un-hides one would disappear with it, leaving no
+   * way back short of an API call. The suppressed ids are the other half of the same catalog.
+   *
+   * Consumer CODE-shipped types are excluded on purpose: they have no backend row to suppress, so
+   * a deployment that ships only those has nothing for that screen to manage.
+   */
+  const hasRegisteredOperations = computed<boolean>(
+    () =>
+      (capabilitiesManifest.value?.slots?.taskTypes ?? []).length > 0 ||
+      suppressedTaskTypes.value.length > 0,
+  )
+
   /** The custom types indexed by id, for a per-type lookup (e.g. the create-form field descriptors). */
   const byTaskType = computed<Record<string, CustomTaskType>>(() =>
     Object.fromEntries(customTaskTypes.value.map((t) => [t.taskType, t])),
@@ -84,5 +106,22 @@ export const useTaskTypesStore = defineStore('taskTypes', () => {
     capabilitiesManifest.value = manifest
   }
 
-  return { customTaskTypes, get, registerConsumerTaskTypes, hydrateCapabilities }
+  /**
+   * The suppressed-id half of the same snapshot read. Assigned unconditionally (an absent field is
+   * an empty list): this is per-WORKSPACE state, so carrying the previous board's answer forward
+   * would leave the Operations tab standing on a board that hid nothing.
+   */
+  function hydrateSuppressed(ids: readonly string[]) {
+    suppressedTaskTypes.value = [...ids]
+  }
+
+  return {
+    customTaskTypes,
+    suppressedTaskTypes,
+    hasRegisteredOperations,
+    get,
+    registerConsumerTaskTypes,
+    hydrateCapabilities,
+    hydrateSuppressed,
+  }
 })

package/app/stores/workspace/hydrate.ts

@@ -71,6 +71,7 @@ export function applySnapshotToStores(snapshot: WorkspaceSnapshot, boardSince?:
     snapshot.pipelines,
     snapshot.pipelineCatalogVersions,
     snapshot.retiredPipelines,
+    snapshot.pipelineCatalogNames,
   )
   useExecutionStore().hydrate(snapshot.executions, snapshot.workspace.id)
   useAgentRunsStore().hydrate(snapshot.bootstrapJobs ?? [], snapshot.workspace.id)
@@ -114,6 +115,10 @@ export function applySnapshotToStores(snapshot: WorkspaceSnapshot, boardSince?:
     snapshot.binaryGeneratorsUnavailable === true,
   )
   useTaskTypesStore().hydrateCapabilities(capabilities)
+  // The complement of the offered catalog above: the registered operations this board HIDES. Both
+  // halves come from the one snapshot, so the settings screen can exist for a board that hid
+  // every one of them (the state whose only way back is that screen).
+  useTaskTypesStore().hydrateSuppressed(snapshot.suppressedTaskTypes ?? [])
   // The per-step parameters each registered gate declares, so a gated step's config form in the
   // builder comes from the gate's own registration rather than a form hard-coded per gate.
   usePipelinesStore().hydrateGateConfigForms(snapshot.gateConfigForms ?? [])

package/app/types/domain.ts

@@ -67,6 +67,9 @@ export type {
   TaskTypePresentation,
   TaskTypeFieldDescriptor,
   TaskTypeFieldOption,
+  // One row of the workspace's operation-suppression screen: a registered custom task type plus
+  // whether THIS board hides it (`backend/docs/reusable-operations.md`).
+  TaskTypeSuppression,
   // The shared descriptor-driven form vocabulary (`contracts/src/form-fields.ts`): one field
   // shape and one filled-value bag behind both the initiative-preset form and a custom task
   // type's per-case form, so `DescriptorFields.vue` renders either.

package/app/utils/descriptorFields.ts

@@ -1,40 +1,26 @@
+import { descriptorFieldDefaults } from '@cat-factory/contracts'
 import type { DescriptorField, DescriptorFieldValue, DescriptorFieldValues } from '~/types/domain'
 
 // Form-side helpers over the shared descriptor-field vocabulary (`contracts/src/form-fields.ts`),
 // used by every surface that renders one through `DescriptorFields.vue`: an initiative preset's
 // create form and a reusable operation's per-case form on a custom task type.
 //
-// The RULES (visibility, validation, sanitization, prose rendering) live in contracts, because the
-// server has to agree about them. What lives here is what only a FORM decides: which values to
-// start it with, and how one edit changes the bag. Both are pure functions over the value bag
-// rather than methods inside the SFC, so the mutation rules a wrong answer would freeze on an
-// entity are unit-testable without mounting a component.
+// The RULES (visibility, validation, sanitization, prose rendering, and now default seeding) live
+// in contracts, because the server has to agree about them. What lives here is what only a FORM
+// decides: how one edit changes the bag. Pure functions over the value bag rather than methods
+// inside the SFC, so the mutation rules a wrong answer would freeze on an entity are unit-testable
+// without mounting a component.
 
 /**
- * The initial, typed values a field list implies: its declared DEFAULTS folded into the
- * `DescriptorFieldValues` shape the renderer and the wire contract expect (`checkbox-group` to
- * `string[]`, `checkbox` to a boolean, `number` to a number, everything else a string). Only fields
- * with a meaningful default are seeded, so an unfilled optional field stays absent (which is what
- * validation reads as unset) and never freezes an empty value. A repo-detection probe's prefill and
- * the user's own edits layer on top.
+ * The initial values a field list implies, for seeding a freshly opened form. A repo-detection
+ * probe's prefill and the user's own edits layer on top.
+ *
+ * The SHARED helper, not a form-side copy: the server folds the same defaults in at the creation
+ * door (`withDescriptorFieldDefaults`), so a duplicate here would be the drift that made a headless
+ * caller and this form disagree about what a descriptor's default means.
  */
 export function defaultDescriptorValues(fields: readonly DescriptorField[]): DescriptorFieldValues {
-  const values: DescriptorFieldValues = {}
-  for (const field of fields) {
-    if (field.type === 'checkbox-group') {
-      if (field.defaultValues?.length) values[field.key] = [...field.defaultValues]
-    } else if (field.type === 'checkbox') {
-      if (field.default === 'true') values[field.key] = true
-    } else if (field.type === 'number') {
-      const parsed = Number(field.default)
-      if (field.default !== undefined && field.default !== '' && Number.isFinite(parsed)) {
-        values[field.key] = parsed
-      }
-    } else if (field.default) {
-      values[field.key] = field.default
-    }
-  }
-  return values
+  return descriptorFieldDefaults(fields)
 }
 
 /**

package/i18n/locales/de.json

@@ -353,6 +353,13 @@
         "manageAccount": "Kontofragmente verwalten →"
       }
     },
+    "taskTypeSuppressions": {
+      "intro": "Wählen Sie aus, welche wiederverwendbaren Operationen dieses Deployments auf diesem Board angeboten werden. Wird eine ausgeblendet, verschwindet sie hier aus der Aufgabenauswahl und das Anlegen von Arbeit darunter wird abgelehnt; andere Boards bleiben unberührt.",
+      "loading": "Operationen werden geladen…",
+      "empty": "Dieses Deployment registriert keine wiederverwendbaren Operationen.",
+      "offer": "Auf diesem Board anbieten",
+      "saveFailed": "Die angebotenen Operationen konnten nicht geändert werden"
+    },
     "issueTracker": {
       "filing": {
         "heading": "Wo Tickets abgelegt werden",
@@ -932,6 +939,7 @@
         "merge": "Risikorichtlinien",
         "tracker": "Issue-Tracker",
         "fragments": "Dienst-Best-Practices",
+        "operations": "Operationen",
         "metadata": "Metadaten",
         "members": "Mitglieder"
       },

package/i18n/locales/en.json

@@ -2914,6 +2914,13 @@
         "manageAccount": "Manage account fragments →"
       }
     },
+    "taskTypeSuppressions": {
+      "intro": "Choose which of this deployment's reusable operations this board offers. Hiding one removes it from the create-task picker here and refuses creating work under it; other boards are unaffected.",
+      "loading": "Loading operations…",
+      "empty": "This deployment registers no reusable operations.",
+      "offer": "Offer on this board",
+      "saveFailed": "Could not change which operations this board offers"
+    },
     "issueTracker": {
       "filing": {
         "heading": "Where tickets are filed",
@@ -3502,6 +3509,7 @@
         "merge": "Risk policies",
         "tracker": "Issue tracker",
         "fragments": "Service best practices",
+        "operations": "Operations",
         "metadata": "Metadata",
         "members": "Members"
       },

package/i18n/locales/es.json

@@ -2666,6 +2666,13 @@
         "manageAccount": "Gestionar los fragmentos de la cuenta →"
       }
     },
+    "taskTypeSuppressions": {
+      "intro": "Elige qué operaciones reutilizables de este despliegue ofrece este tablero. Ocultar una la quita del selector de creación de tareas aquí y rechaza crear trabajo con ella; otros tableros no se ven afectados.",
+      "loading": "Cargando operaciones…",
+      "empty": "Este despliegue no registra ninguna operación reutilizable.",
+      "offer": "Ofrecer en este tablero",
+      "saveFailed": "No se pudieron cambiar las operaciones que ofrece este tablero"
+    },
     "issueTracker": {
       "filing": {
         "heading": "Dónde se registran los tickets",
@@ -3245,6 +3252,7 @@
         "merge": "Políticas de riesgo",
         "tracker": "Gestor de incidencias",
         "fragments": "Buenas prácticas del servicio",
+        "operations": "Operaciones",
         "metadata": "Metadatos",
         "members": "Miembros"
       },

package/i18n/locales/fr.json

@@ -2666,6 +2666,13 @@
         "manageAccount": "Gérer les fragments du compte →"
       }
     },
+    "taskTypeSuppressions": {
+      "intro": "Choisissez les opérations réutilisables de ce déploiement proposées sur ce tableau. En masquer une la retire du sélecteur de création de tâche ici et refuse la création de travail associée ; les autres tableaux ne sont pas affectés.",
+      "loading": "Chargement des opérations…",
+      "empty": "Ce déploiement n'enregistre aucune opération réutilisable.",
+      "offer": "Proposer sur ce tableau",
+      "saveFailed": "Impossible de modifier les opérations proposées sur ce tableau"
+    },
     "issueTracker": {
       "filing": {
         "heading": "Où les tickets sont créés",
@@ -3245,6 +3252,7 @@
         "merge": "Politiques de risque",
         "tracker": "Suivi des tickets",
         "fragments": "Bonnes pratiques du service",
+        "operations": "Opérations",
         "metadata": "Métadonnées",
         "members": "Membres"
       },

package/i18n/locales/he.json

@@ -2807,6 +2807,13 @@
         "manageAccount": "נהל מקטעי חשבון ←"
       }
     },
+    "taskTypeSuppressions": {
+      "intro": "בחרו אילו פעולות רב-פעמיות של פריסה זו יוצעו בלוח הזה. הסתרה של פעולה מסירה אותה מבורר יצירת המשימות כאן ומונעת יצירת עבודה תחתיה; לוחות אחרים אינם מושפעים.",
+      "loading": "טוען פעולות…",
+      "empty": "פריסה זו אינה רושמת פעולות רב-פעמיות.",
+      "offer": "הצעה בלוח הזה",
+      "saveFailed": "לא ניתן היה לשנות אילו פעולות מוצעות בלוח הזה"
+    },
     "issueTracker": {
       "filing": {
         "heading": "היכן מוגשים כרטיסים",
@@ -3386,6 +3393,7 @@
         "merge": "מדיניות סיכון",
         "tracker": "מעקב כרטיסים",
         "fragments": "שיטות עבודה מומלצות לשירות",
+        "operations": "פעולות",
         "metadata": "מטא-נתונים",
         "members": "חברים"
       },

package/i18n/locales/it.json

@@ -353,6 +353,13 @@
         "manageAccount": "Gestisci i frammenti dell'account →"
       }
     },
+    "taskTypeSuppressions": {
+      "intro": "Scegli quali operazioni riutilizzabili di questo deployment vengono offerte su questa board. Nasconderne una la rimuove dal selettore di creazione attività qui e rifiuta la creazione di lavoro con essa; le altre board non sono interessate.",
+      "loading": "Caricamento delle operazioni…",
+      "empty": "Questo deployment non registra operazioni riutilizzabili.",
+      "offer": "Offri su questa board",
+      "saveFailed": "Impossibile modificare le operazioni offerte su questa board"
+    },
     "issueTracker": {
       "filing": {
         "heading": "Dove vengono registrati i ticket",
@@ -932,6 +939,7 @@
         "merge": "Criteri di rischio",
         "tracker": "Tracker degli issue",
         "fragments": "Best practice dei servizi",
+        "operations": "Operazioni",
         "metadata": "Metadati",
         "members": "Membri"
       },

package/i18n/locales/ja.json

@@ -2807,6 +2807,13 @@
         "manageAccount": "アカウントのフラグメントを管理 →"
       }
     },
+    "taskTypeSuppressions": {
+      "intro": "このデプロイメントの再利用可能オペレーションのうち、このボードで提供するものを選びます。非表示にするとここのタスク作成ピッカーから消え、そのタイプでの作成は拒否されます。他のボードには影響しません。",
+      "loading": "オペレーションを読み込んでいます…",
+      "empty": "このデプロイメントには再利用可能オペレーションが登録されていません。",
+      "offer": "このボードで提供する",
+      "saveFailed": "このボードで提供するオペレーションを変更できませんでした"
+    },
     "issueTracker": {
       "filing": {
         "heading": "チケットの起票先",
@@ -3386,6 +3393,7 @@
         "merge": "リスクポリシー",
         "tracker": "課題トラッカー",
         "fragments": "サービスのベストプラクティス",
+        "operations": "オペレーション",
         "metadata": "メタデータ",
         "members": "メンバー"
       },

package/i18n/locales/pl.json

@@ -2666,6 +2666,13 @@
         "manageAccount": "Zarządzaj fragmentami konta →"
       }
     },
+    "taskTypeSuppressions": {
+      "intro": "Wybierz, które operacje wielokrotnego użytku tego wdrożenia są dostępne na tej tablicy. Ukrycie usuwa operację z listy wyboru przy tworzeniu zadania i blokuje tworzenie pracy tego typu; inne tablice pozostają bez zmian.",
+      "loading": "Wczytywanie operacji…",
+      "empty": "To wdrożenie nie rejestruje żadnych operacji wielokrotnego użytku.",
+      "offer": "Udostępnij na tej tablicy",
+      "saveFailed": "Nie udało się zmienić operacji dostępnych na tej tablicy"
+    },
     "issueTracker": {
       "filing": {
         "heading": "Gdzie są zgłaszane zgłoszenia",
@@ -3245,6 +3252,7 @@
         "merge": "Zasady ryzyka",
         "tracker": "System zgłoszeń",
         "fragments": "Dobre praktyki usługi",
+        "operations": "Operacje",
         "metadata": "Metadane",
         "members": "Członkowie"
       },

package/i18n/locales/tr.json

@@ -2807,6 +2807,13 @@
         "manageAccount": "Hesap parçalarını yönet →"
       }
     },
+    "taskTypeSuppressions": {
+      "intro": "Bu dağıtımın yeniden kullanılabilir operasyonlarından hangilerinin bu panoda sunulacağını seçin. Birini gizlemek onu buradaki görev oluşturma seçicisinden kaldırır ve o türde iş oluşturmayı reddeder; diğer panolar etkilenmez.",
+      "loading": "Operasyonlar yükleniyor…",
+      "empty": "Bu dağıtım hiçbir yeniden kullanılabilir operasyon kaydetmiyor.",
+      "offer": "Bu panoda sun",
+      "saveFailed": "Bu panoda sunulan operasyonlar değiştirilemedi"
+    },
     "issueTracker": {
       "filing": {
         "heading": "Biletlerin nereye açıldığı",
@@ -3386,6 +3393,7 @@
         "merge": "Risk ilkeleri",
         "tracker": "Sorun takipçisi",
         "fragments": "Servis en iyi uygulamaları",
+        "operations": "Operasyonlar",
         "metadata": "Meta veriler",
         "members": "Üyeler"
       },

package/i18n/locales/uk.json

@@ -2666,6 +2666,13 @@
         "manageAccount": "Керувати фрагментами облікового запису →"
       }
     },
+    "taskTypeSuppressions": {
+      "intro": "Оберіть, які багаторазові операції цього розгортання пропонує ця дошка. Приховування прибирає операцію з вибору при створенні завдання тут і забороняє створювати роботу під нею; інші дошки не змінюються.",
+      "loading": "Завантаження операцій…",
+      "empty": "Це розгортання не реєструє багаторазових операцій.",
+      "offer": "Пропонувати на цій дошці",
+      "saveFailed": "Не вдалося змінити операції, які пропонує ця дошка"
+    },
     "issueTracker": {
       "filing": {
         "heading": "Де реєструються тикети",
@@ -3245,6 +3252,7 @@
         "merge": "Політики ризику",
         "tracker": "Трекер задач",
         "fragments": "Найкращі практики сервісу",
+        "operations": "Операції",
         "metadata": "Метадані",
         "members": "Учасники"
       },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cat-factory/app",
-  "version": "0.233.0",
+  "version": "0.234.0",
   "description": "Reusable Nuxt layer for the Agent Architecture Board SPA (components, stores, composables, pages). Consume it from a thin deployment app via `extends: ['@cat-factory/app']` and point it at your backend with NUXT_PUBLIC_API_BASE. See deploy/frontend for an example.",
   "repository": {
     "type": "git",
@@ -40,7 +40,7 @@
     "valibot": "^1.4.2",
     "vue": "3.5.40",
     "wretch": "^3.0.9",
-    "@cat-factory/contracts": "0.251.0"
+    "@cat-factory/contracts": "0.252.0"
   },
   "devDependencies": {
     "@toad-contracts/testing": "0.3.2",