@cat-factory/app 0.270.2 → 0.270.3

package/README.md

@@ -348,8 +348,12 @@ picking what each of them runs on are halves of the same job.
 The builder's palette narrows on two axes, and both controls sit on one row above the catalog
 (`PipelinePurposeSelect` above `AgentTierSelect`), each with its own "n hidden" hint so neither
 narrowing reads as an empty catalog. The tier says how deep to look; the **purpose** says what
-the pipeline is for (`build` / `document` / `review` / `research` / `planning`), and the palette
-drops the categories that purpose has no use for. It reaches past the palette: the saved-pipeline
+the pipeline is for (`build` / `bugfix` / `document` / `review` / `research` / `planning`), and the
+palette drops the categories that purpose has no use for. `bugfix` is the one pair that shares a
+row with another member: it ships code exactly as `build` does, and differs only in being offered
+to a `bug` task and withheld from a `feature` one, because a preset that investigates a defect
+report and writes a failing reproduction test has neither input on a feature. It reaches past the
+palette: the saved-pipeline
 library in the builder's third column lists the pipelines built for the purpose being edited, so
 one dial narrows both ends of the slideover. The purpose is not a view preference either: it is
 saved on the pipeline and also decides which task pickers offer it, which is why the control

package/app/components/board/AddTaskModal.vue

@@ -380,13 +380,14 @@ const selectedModelPresetLabel = computed(() => {
 // still browsable.
 const fragmentPool = computed(() => fragments.forBlockType(frame.value?.type ?? 'service'))
 
-// Hide UI-testing pipelines (`tester-ui` / `visual-confirmation`) when the target frame has no
-// UI to exercise — they'd be refused server-side (see utils/pipeline + the backend gate). Also
-// hide `'recurring'`-only pipelines (a one-off task start of one is refused at run start) and every
-// pipeline whose purpose doesn't match the chosen task type (a doc task authors a doc, a review task
-// reviews a PR, and a `feature`/`bug` task ships code — so it is offered build + research only, not
-// the doc/review/planning presets). `blockLevel: 'task'` is passed literally because this modal only
-// ever creates a task leaf, which also drops the three planning presets the backend would refuse.
+// Hide UI-testing pipelines when the target frame has no UI for them to reach — a step scoped to
+// a frontend service excuses itself, so this only drops an UNCONDITIONAL one (see utils/pipeline
+// + the backend gate). Also hide `'recurring'`-only pipelines (a one-off task start of one is
+// refused at run start) and every pipeline whose purpose doesn't match the chosen task type (a doc
+// task authors a doc, a review task reviews a PR, a `bug` task ships code and may reach for a
+// bugfix preset, and a `feature` gets that set minus the bugfix ones, which have no defect report
+// to investigate). `blockLevel: 'task'` is passed literally because this modal only ever creates a
+// task leaf, which also drops the three planning presets the backend would refuse.
 // Re-filters as the chosen task type changes.
 const selectablePipelines = computed(() =>
   pipelines.pipelines.filter((p) =>
@@ -416,7 +417,15 @@ const DEFAULT_PIPELINE_FOR_TYPE: Partial<Record<TaskTypeChoice, string>> = {
  * deliberately does not name), the build rung this interface mode defaults to. Basic mode gets the
  * fixed Standard build, advanced the Adaptive one; `defaultBuildPipelineId` owns that rule so the
  * create form and the task card's plain "Start" cannot disagree about it. Empty when the resolved
- * preset is not in this workspace's library (an older seed, or a retired rung).
+ * preset is not in this workspace's library (an older seed, or a retired rung) or when the picker
+ * would not OFFER it for `type`.
+ *
+ * That second check is why it re-runs the picker's own predicate rather than scanning the whole
+ * library: a workspace whose declared interactive default is a bugfix preset would otherwise open a
+ * `feature` form on a selection with no matching row, and create the task pinned to a pipeline the
+ * same screen says is not allowed for its type. Parameterised by `type` rather than reading
+ * `selectablePipelines`, so the answer cannot depend on whether the watcher fires before or after
+ * the ref it filters on has settled.
  *
  * ONE definition, read by both the type watcher and the open-reset. They used to compute it
  * separately, the reset consulting `DEFAULT_PIPELINE_FOR_TYPE` alone and falling to `''` for every
@@ -433,7 +442,10 @@ function defaultPipelineIdFor(type: TaskTypeChoice): string {
     // and the task card's plain Start still cannot disagree (see `declaredDefaultId`).
     pipelines.declaredDefaultId('interactive') ??
     defaultBuildPipelineId(uiMode.isAdvanced)
-  return pipelines.pipelines.some((p) => p.id === preset) ? preset : ''
+  const resolved = pipelines.pipelines.find((p) => p.id === preset)
+  const offered =
+    !!resolved && pipelineAllowedForManualStart(resolved, frame.value, board.blocks, type, 'task')
+  return offered ? preset : ''
 }
 
 watch(taskType, (next) => {

package/app/components/board/RecurringPipelineModal.vue

@@ -131,7 +131,8 @@ function defaultRecurrence(): Recurrence {
   }
 }
 
-// Hide UI-testing pipelines when the frame has no UI to exercise — they'd be refused at run start.
+// Hide a pipeline whose UI-testing step would REACH a frame with no UI (one scoped to a frontend
+// service excuses itself) — it would be refused at run start.
 // Also hide `'one-off'`-only pipelines: attaching one to a schedule is refused server-side.
 const selectablePipelines = computed(() =>
   pipelines.pipelines.filter((p) => pipelineAllowedForSchedule(p, frame.value, board.blocks)),

package/app/components/palettes/PipelinePurposeSelect.vue

@@ -1,6 +1,6 @@
 <script setup lang="ts">
-// The pipeline-PURPOSE control: what the pipeline being built exists to do (build, document,
-// review, research, plan). It sits beside `AgentTierSelect` at the top of the agent palette
+// The pipeline-PURPOSE control: what the pipeline being built exists to do (build, fix a bug,
+// document, review, research, plan). It sits beside `AgentTierSelect` at the top of the agent palette
 // because the two are the same kind of dial (each narrows the catalog below to what is worth
 // offering), and a filter the user cannot see is a catalog that looks incomplete for no reason.
 //
@@ -25,6 +25,7 @@ const emit = defineEmits<{ (e: 'update:purpose', purpose: PipelinePurpose): void
 // typed-message-keys check covers them, the same shape `AgentTierSelect` uses for its tiers.
 const PURPOSE_LABELS = computed<Record<PipelinePurpose, string>>(() => ({
   build: t('pipeline.builder.purposeOption.build'),
+  bugfix: t('pipeline.builder.purposeOption.bugfix'),
   document: t('pipeline.builder.purposeOption.document'),
   review: t('pipeline.builder.purposeOption.review'),
   research: t('pipeline.builder.purposeOption.research'),

package/app/components/panels/inspector/TaskRunSettings.vue

@@ -148,12 +148,21 @@ const selectedPipeline = computed(() =>
 // drops the planning presets the engine would refuse. The task-type narrowing already excludes them
 // for `feature`/`bug`, but NOT for a `spike` / `ralph` / deployment-custom type — and a planning
 // preset settable as a task's DEFAULT pipeline is a 409 on every later Start.
+// The pipeline this task is ALREADY pinned to is kept in the list even when the narrowing would
+// drop it, the same rule `showOverrideField` states for a hidden override an entity already
+// carries: every one of these gates has been tightened at least once, and a task pinned under the
+// looser one is a legal pre-existing state (a `feature` on a bugfix preset, until the purpose
+// classifier split). Without it the badge below names a pipeline the dropdown does not contain,
+// and the first change to anything else is a one-way door out of a selection the panel is still
+// showing. It is only ever the CURRENT value, so nothing new can be pinned through it.
 const taskFrame = computed(() => board.serviceOf(props.block))
-const selectablePipelines = computed(() =>
-  pipelines.pipelines.filter((p) =>
+const selectablePipelines = computed(() => {
+  const offered = pipelines.pipelines.filter((p) =>
     pipelineAllowedForManualStart(p, taskFrame.value, board.blocks, props.block.taskType, 'task'),
-  ),
-)
+  )
+  const pinned = selectedPipeline.value
+  return pinned && !offered.some((p) => p.id === pinned.id) ? [pinned, ...offered] : offered
+})
 function setPipeline(id: string) {
   board.updateBlock(props.block.id, { pipelineId: id })
 }

package/app/stores/pipelines.ts

@@ -75,10 +75,10 @@ export const usePipelinesStore = defineStore('pipelines', () => {
   /** Organizational labels for the pipeline being assembled/edited. */
   const draftLabels = ref<string[]>([])
   /**
-   * The use-case classifier of the pipeline being assembled/edited (`build` / `document` /
-   * `review` / `research` / `planning`). Drives which task pickers offer the saved pipeline, which
-   * agent kinds the builder palette shows (a non-`build` purpose hides the Implementation/Testing
-   * kinds) and which saved pipelines the library lists.
+   * The use-case classifier of the pipeline being assembled/edited (`build` / `bugfix` /
+   * `document` / `review` / `research` / `planning`). Drives which task pickers offer the saved
+   * pipeline, which agent kinds the builder palette shows (a purpose that ships no code hides the
+   * Implementation/Testing kinds) and which saved pipelines the library lists.
    *
    * Never null: `Pipeline.purpose` is mandatory, so a draft is classified from the moment it
    * exists. `build` is the default because it is what an unclassified pipeline has always behaved

package/app/utils/pipeline.spec.ts

@@ -6,13 +6,17 @@ import {
   PIPELINE_PURPOSES,
   pipelineAllowedForBlockLevel,
   pipelineAllowedForTaskType,
+  pipelineMatchesPurpose,
+  pipelineRunsVisualStep,
   purposeAllowsAgentCategory,
   purposeSuggestsAgentCategory,
   purposeSuggestsAgentKind,
+  resolveRunServiceScope,
 } from '@cat-factory/contracts'
 import type { PipelinePurpose } from '@cat-factory/contracts'
 import type { Block, Pipeline } from '~/types/domain'
 import {
+  pipelineAllowedForFrame,
   pipelineAllowedForManualStart,
   pipelineAllowedForSchedule,
   pipelineConditionalCount,
@@ -136,6 +140,22 @@ describe('pipelineAllowedForTaskType', () => {
     }
   })
 
+  it('offers a bugfix preset to a bug task and withholds it from a feature', () => {
+    // "Triage & fix bug" investigates a defect REPORT, triages it with a person and writes a
+    // failing reproduction test before anything is fixed. A feature has no report to investigate
+    // and nothing red to turn green, so the front half of the run has no input at all. The bug
+    // task still gets the whole build ladder beside it — this narrows one preset, not the type.
+    const bugfix = pipeline({ purpose: 'bugfix' })
+    expect(pipelineAllowedForTaskType(bugfix, 'bug')).toBe(true)
+    expect(pipelineAllowedForTaskType(bugfix, 'feature')).toBe(false)
+    expect(pipelineAllowedForTaskType(pipeline({ purpose: 'build' }), 'bug')).toBe(true)
+    // And it stays out of the task types that demand their own explicit member.
+    expect(pipelineAllowedForTaskType(bugfix, 'document')).toBe(false)
+    expect(pipelineAllowedForTaskType(bugfix, 'review')).toBe(false)
+    // An un-narrowed type (spike, ralph, a deployment's own) is unrestricted as ever.
+    expect(pipelineAllowedForTaskType(bugfix, 'spike')).toBe(true)
+  })
+
   it('keeps a pipeline whose classifier this build cannot name on a feature / bug task', () => {
     // The one place this narrowing runs opposite to the document/review one, and it has to. The
     // value is persisted, so a deployment's own classifier (or one retired since the row was
@@ -189,8 +209,10 @@ describe('pipelineAllowedForBlockLevel (initiative binding)', () => {
 })
 
 describe('purposeAllowsAgentCategory (builder save gate)', () => {
-  it('a build pipeline, and one whose classifier this build cannot name, may use every category', () => {
-    for (const purpose of ['build', UNKNOWN_PURPOSE] as const) {
+  it('a code-shipping pipeline, and one whose classifier this build cannot name, may use every category', () => {
+    // `bugfix` rides with `build` here: the two differ only in the task type they are OFFERED to,
+    // and a bug fix designs, implements, tests and merges like any other change.
+    for (const purpose of ['build', 'bugfix', UNKNOWN_PURPOSE] as const) {
       for (const cat of AGENT_CATEGORIES) {
         expect(purposeAllowsAgentCategory(purpose, cat)).toBe(true)
       }
@@ -211,8 +233,8 @@ describe('purposeAllowsAgentCategory (builder save gate)', () => {
 })
 
 describe('purposeSuggestsAgentCategory (builder palette filter)', () => {
-  it('offers the whole catalog to a build pipeline, and to one it cannot name', () => {
-    for (const purpose of ['build', UNKNOWN_PURPOSE] as const) {
+  it('offers the whole catalog to a code-shipping pipeline, and to one it cannot name', () => {
+    for (const purpose of ['build', 'bugfix', UNKNOWN_PURPOSE] as const) {
       for (const cat of AGENT_CATEGORIES) {
         expect(purposeSuggestsAgentCategory(purpose, cat)).toBe(true)
       }
@@ -273,6 +295,23 @@ describe('purposeSuggestsAgentKind (what the palette actually filters on)', () =
     expect(purposeSuggestsAgentCategory('review', 'docs')).toBe(true)
   })
 
+  it('reads a `build` declaration as covering `bugfix`, but not the other way round', () => {
+    // The two purposes are the same WORK, split only so the pickers can withhold a defect-report
+    // preset from a feature task. Every kind declaring `build` predates the split, so without
+    // this the bugfix palette would open nearly empty — the Bug Investigator included.
+    const builder = { category: 'build', purposes: ['build'] } as const
+    expect(purposeSuggestsAgentKind('bugfix', builder)).toBe(true)
+    expect(purposeSuggestsAgentKind('document', builder)).toBe(false)
+    // One-way: naming only `bugfix` claims the defect-report context, not builds in general.
+    const bugOnly = { category: 'build', purposes: ['bugfix'] } as const
+    expect(purposeSuggestsAgentKind('bugfix', bugOnly)).toBe(true)
+    expect(purposeSuggestsAgentKind('build', bugOnly)).toBe(false)
+    // ONE relation, not one per surface: the saved-pipeline library reads it through the same
+    // helper, so a draft cannot find the build ladder in its palette and not in its library.
+    expect(pipelineMatchesPurpose({ purpose: 'build' } as Pipeline, 'bugfix')).toBe(true)
+    expect(pipelineMatchesPurpose({ purpose: 'bugfix' } as Pipeline, 'build')).toBe(false)
+  })
+
   it('is a declaration, not an exemption from the category', () => {
     // A kind cannot buy its way back into a purpose its section is not offered to: `docs` is gone
     // for `planning`, and the palette drops the kind whether or not it named `planning` itself.
@@ -341,6 +380,80 @@ describe('a purpose or category this build does not recognise', () => {
   })
 })
 
+describe('pipelineAllowedForFrame (the visual gate)', () => {
+  const serviceFrame = { id: 'blk_svc', level: 'frame', type: 'service' } as Block
+  const frontendFrame = { id: 'blk_fe', level: 'frame', type: 'frontend' } as Block
+
+  // Every build rung ships the CONDITIONAL tester pair: the browser pass declares the frontend
+  // scope, the API pass the backend one, so one preset covers both kinds of service.
+  const buildRung = pipeline({
+    purpose: 'build',
+    agentKinds: ['coder', 'tester-api', 'tester-ui', 'merger'],
+    stepOptions: [
+      null,
+      { condition: { serviceScope: 'backend' } },
+      { condition: { serviceScope: 'frontend' } },
+      null,
+    ],
+  })
+
+  it('offers a build rung on a plain backend service — its UI pass is scoped out', () => {
+    // The regression: reading "does the pipeline LIST a visual step" hid Standard / Simple /
+    // Adaptive / Complex build from the pickers on every non-frontend service, while the engine
+    // would have started any of them (it drops the condition-excluded steps before its own gate).
+    expect(pipelineAllowedForFrame(buildRung, serviceFrame, [serviceFrame])).toBe(true)
+    expect(pipelineAllowedForManualStart(buildRung, serviceFrame, [serviceFrame], 'feature')).toBe(
+      true,
+    )
+  })
+
+  it('offers it on a frontend frame too, where the UI pass is exactly what runs', () => {
+    // Stated as the premise, not just the answer: on this frame the condition ADMITS the browser
+    // pass, so the gate is passing on the frame half rather than on the step being scoped out.
+    // Without it the case reads identically against the pre-fix implementation, which reached the
+    // same `true` down the other branch and asserted nothing about the change.
+    expect(pipelineRunsVisualStep(buildRung, resolveRunServiceScope([frontendFrame]))).toBe(true)
+    expect(pipelineAllowedForFrame(buildRung, frontendFrame, [frontendFrame])).toBe(true)
+  })
+
+  it('offers everything on a service frame a FRONTEND binds as its backend', () => {
+    // The other half of `frameAllowsVisualPipeline`, and the branch with the widest reach: the
+    // linked frontend is the UI a change to this service is validated through, so the frame has a
+    // UI and even an unconditional visual pipeline may run on it.
+    const boundService = { id: 'blk_api', level: 'frame', type: 'service' } as Block
+    const binder = {
+      id: 'blk_fe',
+      level: 'frame',
+      type: 'frontend',
+      frontendConfig: {
+        backendBindings: [
+          { envVar: 'API_URL', source: { kind: 'service', serviceBlockId: 'blk_api' } },
+        ],
+      },
+    } as Block
+    const blocks = [boundService, binder]
+    const visual = pipeline({ purpose: 'build', agentKinds: ['coder', 'visual-confirmation'] })
+    expect(pipelineAllowedForFrame(buildRung, boundService, blocks)).toBe(true)
+    expect(pipelineAllowedForFrame(visual, boundService, blocks)).toBe(true)
+    // ...and it is the BINDING that does it, not the mere presence of a frontend on the board.
+    expect(pipelineAllowedForFrame(visual, boundService, [boundService, frontendFrame])).toBe(false)
+  })
+
+  it('still hides a pipeline whose visual step is UNCONDITIONAL on a frame with no UI', () => {
+    // The gate the conditional pair did not repeal: a `visual-confirmation` step with nothing to
+    // scope it out has no app to show a person, and the engine answers a 409.
+    const visual = pipeline({ purpose: 'build', agentKinds: ['coder', 'visual-confirmation'] })
+    expect(pipelineAllowedForFrame(visual, serviceFrame, [serviceFrame])).toBe(false)
+    expect(pipelineAllowedForFrame(visual, frontendFrame, [frontendFrame])).toBe(true)
+  })
+
+  it('hides a conditional visual pipeline when the frame cannot be resolved', () => {
+    // No frame ⇒ no scope to judge the condition against, so the step counts and the frame half
+    // refuses. The fail-safe direction, and the same answer the engine gives.
+    expect(pipelineAllowedForFrame(buildRung, undefined, [])).toBe(false)
+  })
+})
+
 describe('pipelineAllowedForManualStart composes the task-type gate', () => {
   const noFrame = undefined
   const blocks: Block[] = []

package/app/utils/pipeline.ts

@@ -3,6 +3,8 @@ import {
   pipelineAllowedForBlockLevel,
   pipelineAllowedForTaskType,
   pipelineHasVisualStep,
+  pipelineRunsVisualStep,
+  resolveRunServiceScope,
 } from '@cat-factory/contracts'
 import type { AgentKind, Block, BlockLevel, Pipeline } from '~/types/domain'
 
@@ -102,16 +104,40 @@ export { pipelineAllowedForBlockLevel, pipelineAllowedForTaskType }
 // the gate.
 
 /**
- * Whether `pipeline` may run on a task under `frame`. A non-visual pipeline is always allowed;
- * a visual one only when the frame has a UI (see {@link frameAllowsVisualPipeline}). `blocks` is
- * the board's block list, used to find frontend→service links.
+ * Whether `pipeline` may run on a task under `frame`. Allowed when the frame has a UI (see
+ * {@link frameAllowsVisualPipeline}), and otherwise only when no visual step would REACH a
+ * dispatch there ({@link pipelineRunsVisualStep}). `blocks` is the board's block list, used to
+ * find frontend→service links.
+ *
+ * The two halves mirror run admission, which filters the chain through the run conditions and
+ * then gates the survivors on the frame. Asking only "does it list a visual step" hid every
+ * build rung from every picker on every non-frontend service the moment the ladder adopted the
+ * conditional tester pair: each rung lists a `tester-ui` scoped to `frontend`, which a backend
+ * task skips.
+ *
+ * The coarse {@link pipelineHasVisualStep} runs FIRST and is the only work an ordinary pipeline
+ * costs: this is called once per row of every pipeline picker, recomputed on each task-type change
+ * and each live board push, and the other two halves each walk the whole block list or allocate a
+ * scope. A pipeline listing no visual step at all can reach neither answer, so nothing is decided
+ * before it that it could decide differently.
+ *
+ * The scope is derived from the FRAME alone, where the engine also folds in the task's involved
+ * services. That cannot disagree here: an involved service is always a non-frontend (only a
+ * `service` frame survives `validInvolvedServiceFrames`), so it can only ever re-confirm the
+ * `backend` half this frame already sets — and on a frontend frame the gate passes on the frame
+ * itself. `runServiceScope.test.ts` pins that filter as the invariant this omission rests on, so
+ * widening it fails there rather than here, where the symptom would be a rung this offers and the
+ * run-start gate then refuses. An unresolved frame yields an empty scope, which admits every
+ * condition and is then refused by the frame half, exactly as the engine refuses it.
  */
 export function pipelineAllowedForFrame(
   pipeline: Pipeline,
   frame: Block | undefined,
   blocks: readonly Block[],
 ): boolean {
-  return !pipelineHasVisualStep(pipeline) || frameAllowsVisualPipeline(frame, blocks)
+  if (!pipelineHasVisualStep(pipeline)) return true
+  if (frameAllowsVisualPipeline(frame, blocks)) return true
+  return !pipelineRunsVisualStep(pipeline, resolveRunServiceScope(frame ? [frame] : []))
 }
 
 // Launch-availability filters, the surface counterpart to the backend's start-origin gate (a
@@ -126,7 +152,8 @@ export function pipelineAllowedForFrame(
  *  - `'recurring'`-only pipelines the backend would refuse;
  *  - visual pipelines on a frame with no UI;
  *  - pipelines whose `purpose` doesn't fit the given `taskType` (a `document` task offers only
- *    document pipelines; a `feature`/`bug` task only build + research ones);
+ *    document pipelines; a `bug` task build + bugfix + research ones, and a `feature` the same
+ *    minus the bugfix presets, which have no defect report to work from);
  *  - pipelines whose `purpose` doesn't fit the given `blockLevel` (planning pipelines run only on
  *    an initiative block, and an initiative block runs only those).
  *

package/app/utils/pipelineLibrary.spec.ts

@@ -82,6 +82,22 @@ describe('narrowPipelineLibrary', () => {
     expect(shown.archivedInScope).toBe(1)
   })
 
+  it('lists a build pipeline in a BUGFIX library, but not the reverse', () => {
+    // The one relation `classifierSuits` admits, read here through the same helper the palette
+    // reads: a bugfix draft is doing build work, so the whole ladder belongs in front of it, and
+    // exact matching would open that library holding the two bugfix presets alone, the same
+    // near-empty catalog the palette rule exists to prevent. A build draft is NOT doing defect
+    // work, so the bugfix rows stay behind the dial, counted and one click away.
+    const lib = [...LIBRARY, row('bugfix-a', 'bugfix')]
+    expect(narrowPipelineLibrary(lib, { purpose: 'bugfix' }).offered.map((p) => p.id)).toEqual([
+      'build-a',
+      'bugfix-a',
+    ])
+    const atBuild = narrowPipelineLibrary(lib, { purpose: 'build' })
+    expect(atBuild.offered.map((p) => p.id)).toEqual(['build-a'])
+    expect(atBuild.hiddenByPurpose).toBe(4)
+  })
+
   it('narrows by neither purpose this build cannot name', () => {
     // Same disposition as the palette's: an unrecognised value is one this build has nothing to
     // narrow BY and nothing to narrow it AGAINST, never a reason to guess a current member. A

package/i18n/locales/de.json

@@ -4391,6 +4391,7 @@
       "purposeUnrecognized": "Nicht erkannt ({purpose})",
       "purposeOption": {
         "build": "Entwicklung",
+        "bugfix": "Fehlerbehebung",
         "document": "Dokumentation",
         "review": "Review",
         "research": "Recherche",
@@ -4459,7 +4460,7 @@
       "skillNoneAvailable": "Keine Skills verfügbar. Verknüpfe eine Skill-Quelle in den Kontoeinstellungen.",
       "skillMissing": "Dieser Skill ist nicht mehr im Katalog; wähle einen anderen.",
       "skillNeedsPick": "Ein Skill-Schritt braucht einen ausgewählten Skill, bevor du speichern kannst.",
-      "purposeStepsConflict": "Dieser Zweck schreibt keinen Code und führt keine Tests aus, doch die Pipeline enthält noch Implementierungs- oder Testschritte. Entfernen Sie diese oder setzen Sie den Zweck auf Entwicklung.",
+      "purposeStepsConflict": "Dieser Zweck schreibt keinen Code und führt keine Tests aus, doch die Pipeline enthält noch Implementierungs- oder Testschritte. Entfernen Sie diese oder wählen Sie einen Zweck, der Code liefert (Entwicklung oder Fehlerbehebung).",
       "promptEditTooltip": "Systemprompt dieses Agenten bearbeiten",
       "promptEditedTooltip": "Der Systemprompt dieses Agenten ist für diesen Arbeitsbereich bearbeitet",
       "consensusGroups": "Konsensgruppen",

package/i18n/locales/en.json

@@ -4998,6 +4998,7 @@
       },
       "purposeOption": {
         "build": "Build",
+        "bugfix": "Bug fix",
         "document": "Documentation",
         "review": "Review",
         "research": "Research",
@@ -5069,7 +5070,7 @@
       "skillNoneAvailable": "No skills available. Link a skill source in account settings.",
       "skillMissing": "This skill is no longer in the catalog; pick another.",
       "skillNeedsPick": "A Skill step needs a skill selected before you can save.",
-      "purposeStepsConflict": "This purpose writes no code and runs no tests, but the pipeline still has implementation or testing steps. Remove them or switch the purpose to Build.",
+      "purposeStepsConflict": "This purpose writes no code and runs no tests, but the pipeline still has implementation or testing steps. Remove them, or switch to a purpose that ships code (Build or Bug fix).",
       "promptEditTooltip": "Edit this agent's system prompt",
       "promptEditedTooltip": "This agent's system prompt is edited for this workspace",
       "consensusGroups": "Consensus groups",

package/i18n/locales/es.json

@@ -4834,6 +4834,7 @@
       "purposeUnrecognized": "No reconocido ({purpose})",
       "purposeOption": {
         "build": "Desarrollo",
+        "bugfix": "Corrección de errores",
         "document": "Documentación",
         "review": "Revisión",
         "research": "Investigación",
@@ -4902,7 +4903,7 @@
       "skillNoneAvailable": "No hay habilidades disponibles. Vincula una fuente de habilidades en la configuración de la cuenta.",
       "skillMissing": "Esta habilidad ya no está en el catálogo; elige otra.",
       "skillNeedsPick": "Un paso Skill necesita una habilidad seleccionada antes de poder guardar.",
-      "purposeStepsConflict": "Este propósito no escribe código ni ejecuta pruebas, pero la canalización todavía tiene pasos de implementación o de prueba. Quítalos o cambia el propósito a Desarrollo.",
+      "purposeStepsConflict": "Este propósito no escribe código ni ejecuta pruebas, pero la canalización todavía tiene pasos de implementación o de prueba. Quítalos o cambia a un propósito que entregue código (Desarrollo o Corrección de errores).",
       "promptEditTooltip": "Editar el prompt del sistema de este agente",
       "promptEditedTooltip": "El prompt del sistema de este agente está editado para este espacio de trabajo",
       "consensusGroups": "Grupos de consenso",

package/i18n/locales/fr.json

@@ -4834,6 +4834,7 @@
       "purposeUnrecognized": "Non reconnu ({purpose})",
       "purposeOption": {
         "build": "Développement",
+        "bugfix": "Correction de bug",
         "document": "Documentation",
         "review": "Revue",
         "research": "Recherche",
@@ -4902,7 +4903,7 @@
       "skillNoneAvailable": "Aucune compétence disponible. Reliez une source de compétences dans les paramètres du compte.",
       "skillMissing": "Cette compétence n'est plus dans le catalogue ; choisissez-en une autre.",
       "skillNeedsPick": "Une étape Skill a besoin d'une compétence sélectionnée avant de pouvoir enregistrer.",
-      "purposeStepsConflict": "Cet objectif n'écrit aucun code et n'exécute aucun test, mais le pipeline contient encore des étapes d'implémentation ou de test. Supprimez-les ou définissez l'objectif sur Développement.",
+      "purposeStepsConflict": "Cet objectif n'écrit aucun code et n'exécute aucun test, mais le pipeline contient encore des étapes d'implémentation ou de test. Supprimez-les ou choisissez un objectif qui livre du code (Développement ou Correction de bug).",
       "promptEditTooltip": "Modifier l'invite système de cet agent",
       "promptEditedTooltip": "L'invite système de cet agent est modifiée pour cet espace de travail",
       "consensusGroups": "Groupes de consensus",

package/i18n/locales/he.json

@@ -4834,6 +4834,7 @@
       "purposeUnrecognized": "לא מזוהה ({purpose})",
       "purposeOption": {
         "build": "פיתוח",
+        "bugfix": "תיקון באג",
         "document": "תיעוד",
         "review": "סקירה",
         "research": "מחקר",
@@ -4902,7 +4903,7 @@
       "skillNoneAvailable": "אין כישורים זמינים. קישר מקור כישורים בהגדרות החשבון.",
       "skillMissing": "כישור זה כבר אינו בקטלוג; בחר אחר.",
       "skillNeedsPick": "שלב Skill דורש כישור נבחר לפני שתוכל לשמור.",
-      "purposeStepsConflict": "מטרה זו אינה כותבת קוד ואינה מריצה בדיקות, אך הצינור עדיין כולל שלבי פיתוח או בדיקה. הסירו אותם או שנו את המטרה לפיתוח.",
+      "purposeStepsConflict": "מטרה זו אינה כותבת קוד ואינה מריצה בדיקות, אך הצינור עדיין כולל שלבי פיתוח או בדיקה. הסירו אותם או בחרו מטרה שמספקת קוד (פיתוח או תיקון באג).",
       "promptEditTooltip": "עריכת הנחיית המערכת של הסוכן הזה",
       "promptEditedTooltip": "הנחיית המערכת של הסוכן הזה נערכה עבור מרחב העבודה הזה",
       "consensusGroups": "קבוצות קונצנזוס",

package/i18n/locales/it.json

@@ -4391,6 +4391,7 @@
       "purposeUnrecognized": "Non riconosciuto ({purpose})",
       "purposeOption": {
         "build": "Sviluppo",
+        "bugfix": "Correzione di bug",
         "document": "Documentazione",
         "review": "Revisione",
         "research": "Ricerca",
@@ -4459,7 +4460,7 @@
       "skillNoneAvailable": "Nessuna competenza disponibile. Collega una fonte di competenze nelle impostazioni dell'account.",
       "skillMissing": "Questa competenza non è più nel catalogo; scegline un'altra.",
       "skillNeedsPick": "Un passo Skill richiede una competenza selezionata prima di poter salvare.",
-      "purposeStepsConflict": "Questo scopo non scrive codice né esegue test, ma la pipeline contiene ancora passaggi di implementazione o di test. Rimuovili o imposta lo scopo su Sviluppo.",
+      "purposeStepsConflict": "Questo scopo non scrive codice né esegue test, ma la pipeline contiene ancora passaggi di implementazione o di test. Rimuovili oppure scegli uno scopo che rilascia codice (Sviluppo o Correzione di bug).",
       "promptEditTooltip": "Modifica il prompt di sistema di questo agente",
       "promptEditedTooltip": "Il prompt di sistema di questo agente è modificato per questo spazio di lavoro",
       "consensusGroups": "Gruppi di consenso",

package/i18n/locales/ja.json

@@ -4834,6 +4834,7 @@
       "purposeUnrecognized": "認識できません ({purpose})",
       "purposeOption": {
         "build": "開発",
+        "bugfix": "バグ修正",
         "document": "ドキュメント",
         "review": "レビュー",
         "research": "調査",
@@ -4902,7 +4903,7 @@
       "skillNoneAvailable": "利用できるスキルがありません。アカウント設定でスキルソースをリンクしてください。",
       "skillMissing": "このスキルはカタログに存在しません。別のスキルを選んでください。",
       "skillNeedsPick": "Skill ステップを保存するにはスキルの選択が必要です。",
-      "purposeStepsConflict": "この目的はコードを書かず、テストも実行しませんが、パイプラインには実装またはテストのステップが残っています。それらを削除するか、目的を「開発」に切り替えてください。",
+      "purposeStepsConflict": "この目的はコードを書かず、テストも実行しませんが、パイプラインには実装またはテストのステップが残っています。それらを削除するか、コードを提供する目的（「開発」または「バグ修正」）に切り替えてください。",
       "promptEditTooltip": "このエージェントのシステムプロンプトを編集",
       "promptEditedTooltip": "このエージェントのシステムプロンプトは、このワークスペース用に編集されています",
       "consensusGroups": "コンセンサスグループ",

package/i18n/locales/pl.json

@@ -4834,6 +4834,7 @@
       "purposeUnrecognized": "Nierozpoznany ({purpose})",
       "purposeOption": {
         "build": "Programowanie",
+        "bugfix": "Poprawka błędu",
         "document": "Dokumentacja",
         "review": "Przegląd",
         "research": "Badania",
@@ -4902,7 +4903,7 @@
       "skillNoneAvailable": "Brak dostępnych umiejętności. Połącz źródło umiejętności w ustawieniach konta.",
       "skillMissing": "Tej umiejętności nie ma już w katalogu; wybierz inną.",
       "skillNeedsPick": "Krok Skill wymaga wybranej umiejętności, zanim będzie można zapisać.",
-      "purposeStepsConflict": "To przeznaczenie nie tworzy kodu ani nie uruchamia testów, ale potok nadal zawiera kroki programowania lub testowania. Usuń je lub zmień przeznaczenie na Programowanie.",
+      "purposeStepsConflict": "To przeznaczenie nie tworzy kodu ani nie uruchamia testów, ale potok nadal zawiera kroki programowania lub testowania. Usuń je lub zmień przeznaczenie na takie, które dostarcza kod (Programowanie lub Poprawka błędu).",
       "promptEditTooltip": "Edytuj prompt systemowy tego agenta",
       "promptEditedTooltip": "Prompt systemowy tego agenta jest zmieniony dla tego obszaru roboczego",
       "consensusGroups": "Grupy konsensusu",

package/i18n/locales/tr.json

@@ -4834,6 +4834,7 @@
       "purposeUnrecognized": "Tanınmayan ({purpose})",
       "purposeOption": {
         "build": "Geliştirme",
+        "bugfix": "Hata düzeltme",
         "document": "Dokümantasyon",
         "review": "İnceleme",
         "research": "Araştırma",
@@ -4902,7 +4903,7 @@
       "skillNoneAvailable": "Kullanılabilir beceri yok. Hesap ayarlarında bir beceri kaynağı bağlayın.",
       "skillMissing": "Bu beceri artık katalogda yok; başka birini seçin.",
       "skillNeedsPick": "Bir Skill adımı, kaydedebilmeniz için seçilmiş bir beceri gerektirir.",
-      "purposeStepsConflict": "Bu amaç kod yazmaz ve test çalıştırmaz, ancak işlem hattında hâlâ uygulama veya test adımları var. Bunları kaldırın veya amacı Geliştirme olarak değiştirin.",
+      "purposeStepsConflict": "Bu amaç kod yazmaz ve test çalıştırmaz, ancak işlem hattında hâlâ uygulama veya test adımları var. Bunları kaldırın veya kod teslim eden bir amaca geçin (Geliştirme ya da Hata düzeltme).",
       "promptEditTooltip": "Bu ajanın sistem istemini düzenle",
       "promptEditedTooltip": "Bu ajanın sistem istemi bu çalışma alanı için düzenlenmiş",
       "consensusGroups": "Uzlaşı grupları",

package/i18n/locales/uk.json

@@ -4834,6 +4834,7 @@
       "purposeUnrecognized": "Нерозпізнано ({purpose})",
       "purposeOption": {
         "build": "Розробка",
+        "bugfix": "Виправлення помилки",
         "document": "Документація",
         "review": "Рецензування",
         "research": "Дослідження",
@@ -4902,7 +4903,7 @@
       "skillNoneAvailable": "Немає доступних навичок. Пов'яжіть джерело навичок у налаштуваннях облікового запису.",
       "skillMissing": "Цієї навички більше немає в каталозі; виберіть іншу.",
       "skillNeedsPick": "Крок Skill потребує вибраної навички, перш ніж ви зможете зберегти.",
-      "purposeStepsConflict": "Це призначення не пише код і не запускає тести, але конвеєр досі містить кроки програмування або тестування. Видаліть їх або змініть призначення на Розробку.",
+      "purposeStepsConflict": "Це призначення не пише код і не запускає тести, але конвеєр досі містить кроки програмування або тестування. Видаліть їх або змініть призначення на таке, що постачає код (Розробка або Виправлення помилки).",
       "promptEditTooltip": "Редагувати системний промпт цього агента",
       "promptEditedTooltip": "Системний промпт цього агента змінено для цього робочого простору",
       "consensusGroups": "Групи консенсусу",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cat-factory/app",
-  "version": "0.270.2",
+  "version": "0.270.3",
   "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.41",
     "wretch": "^3.0.9",
-    "@cat-factory/contracts": "0.308.1"
+    "@cat-factory/contracts": "0.309.0"
   },
   "devDependencies": {
     "@toad-contracts/testing": "0.3.2",