@cat-factory/app 0.214.0 → 0.215.1

package/app/components/pipeline/BinaryOutputStepPicker.vue

@@ -227,6 +227,20 @@ function setMediaTypes(text: string) {
   patch({ mediaTypes: lastWritten })
 }
 
+/**
+ * The overlap, as `content type: id, id` per shared content type.
+ *
+ * Assembled here rather than in the read model because it needs `modalityLabel`, and it renders a
+ * RETIRED content type through the same guard every other line does: a step saved under an older
+ * vocabulary can hold one, and two integrations serving it would otherwise put a `TypeError` on
+ * the surface where the re-pick has to be made.
+ */
+const overlapSummary = computed(() =>
+  pick.value.generatorOverlaps
+    .map((overlap) => `${modalityLabel(overlap.modality)}: ${overlap.generatorIds.join(', ')}`)
+    .join('; '),
+)
+
 /** What the SELECTED integrations say they emit — the discoverable half of the free-text field. */
 const declaredFormats = computed(() => {
   const byId = new Map(agents.binaryGenerators.map((generator) => [generator.id, generator]))
@@ -423,6 +437,17 @@ const declaredFormats = computed(() => {
         })
       }}
     </p>
+    <!-- ADVISORY, and grouped with the line above it rather than the refusals: selecting two
+         producers of one content type is the reason the selection is a list, and nothing about
+         the step is wrong. What it costs is a decision nobody wrote down, so the remedy this
+         line carries is the step's own prompt, which is the field right beside it. -->
+    <p
+      v-if="has('generator_overlap')"
+      class="text-[10px] text-slate-500"
+      data-testid="binary-output-generator-overlap"
+    >
+      {{ t('pipeline.builder.binaryOutputGeneratorOverlap', { overlaps: overlapSummary }) }}
+    </p>
     <p
       v-if="unusableMediaTypes.length"
       class="text-[10px] text-amber-400"

package/app/utils/binaryOutput.spec.ts

@@ -428,8 +428,9 @@ describe('binaryOutputPickIssues, generative half', () => {
     expect(pick.issues).toEqual([])
   })
 
-  // The FORMAT half, mirroring kernel's `binaryFormatCoverage` — and its three outcomes, which
-  // are what a second copy of the rule most easily loses.
+  // The FORMAT half. The rule itself is contracts' `binaryFormatCoverage`, tested there; what
+  // these pin is the picker's own job, which is mapping its three outcomes onto two issues that
+  // read differently: a refusal and an advisory.
   const meshy = {
     id: 'meshy',
     modalities: ['3d-model' as const],
@@ -490,6 +491,59 @@ describe('binaryOutputPickIssues, generative half', () => {
     expect(pick.uncoveredModalities).toEqual([])
   })
 
+  it('flags an OVERLAP as ADVISORY, where the content type stops deciding', () => {
+    // The step saves and starts: two producers of one content type is the reason the selection is
+    // a list. What it costs is a decision nobody wrote down, and this is the surface where the
+    // person who knows the answer has the step's prompt already open.
+    const pick = binaryOutputPickIssues(
+      { storageServiceId: 'files', generatorIds: ['retro', 'flux'] },
+      catalog,
+      true,
+      [...generators, { id: 'flux', modalities: ['image' as const] }],
+    )
+    expect(pick.issues).toEqual(['generator_overlap'])
+    expect(pick.generatorOverlaps).toEqual([{ modality: 'image', generatorIds: ['retro', 'flux'] }])
+  })
+
+  it('reads a repeated id as ONE integration, exactly as the backend resolves it', () => {
+    // A step naming one integration twice holds one producer, so there is no choice to advise
+    // about, and the unknown-id list must not name the same missing id twice either.
+    const pick = binaryOutputPickIssues(
+      { storageServiceId: 'files', generatorIds: ['retro', 'retro', 'ghost', 'ghost'] },
+      catalog,
+      true,
+      generators,
+    )
+    expect(pick.issues).toEqual(['unknown_generator'])
+    expect(pick.unknownGeneratorIds).toEqual(['ghost'])
+    expect(pick.generatorOverlaps).toEqual([])
+  })
+
+  it('says nothing about an overlap while one integration produces each content type', () => {
+    const pick = binaryOutputPickIssues(
+      { storageServiceId: 'files', generatorIds: ['retro', 'studio'] },
+      catalog,
+      true,
+      generators,
+    )
+    expect(pick.issues).not.toContain('generator_overlap')
+    expect(pick.generatorOverlaps).toEqual([])
+  })
+
+  it('claims no overlap about a set nobody could read', () => {
+    // Same rule every other generative judgement here follows: an unreachable mothership answers
+    // the same empty list a deployment registering nothing does, and only one of them is a fact.
+    const pick = binaryOutputPickIssues(
+      { storageServiceId: 'files', generatorIds: ['retro', 'flux'] },
+      catalog,
+      true,
+      [],
+      true,
+    )
+    expect(pick.issues).toEqual(['generators_unavailable'])
+    expect(pick.generatorOverlaps).toEqual([])
+  })
+
   it('still judges an EMPTY set, which is a real answer about the deployment', () => {
     // The distinction the flag exists for: same empty list, opposite fact, opposite message.
     const pick = binaryOutputPickIssues(

package/app/utils/binaryOutput.ts

@@ -1,5 +1,14 @@
-import { ASSET_STORAGE_CAPABILITY, normalizeMediaType } from '@cat-factory/contracts'
-import type { BinaryModality, RegisteredBinaryGenerator } from '@cat-factory/contracts'
+import {
+  ASSET_STORAGE_CAPABILITY,
+  binaryFormatCoverage,
+  binaryModalityOverlaps,
+  normalizeMediaType,
+} from '@cat-factory/contracts'
+import type {
+  BinaryModality,
+  BinaryModalityOverlap,
+  RegisteredBinaryGenerator,
+} from '@cat-factory/contracts'
 import type {
   BinaryOutputArtifact,
   BinaryOutputConfig,
@@ -412,6 +421,22 @@ export type BinaryOutputPickIssue =
    * comes to look exactly like "this is fine".
    */
   | 'media_type_unverifiable'
+  /**
+   * Two or more selected integrations produce the SAME content type, so the content type no
+   * longer decides which one the agent calls.
+   *
+   * ADVISORY, like `media_type_unverifiable` and unlike everything above it: the step saves, it
+   * starts, and selecting two producers of one kind is the whole reason the selection is a list.
+   * What it costs is a decision nobody has written down, and the agent resolves an unstated
+   * choice by picking one and picking it consistently, which is invisible in the artifacts,
+   * since every one of them has the right modality, the right format and a clean storage verdict.
+   *
+   * It is raised HERE as well as in the agent's brief because this is the surface where it can be
+   * acted on: the person selecting two integrations is the one who knows why, and the step's
+   * prompt is a field they already have open. The brief catches the step whose author did not
+   * think to write it; this catches the author.
+   */
+  | 'generator_overlap'
 
 /** What the builder found wrong with one step's selection, and which ids to name. */
 export interface BinaryOutputPickState {
@@ -426,6 +451,12 @@ export interface BinaryOutputPickState {
   uncoveredMediaTypes: readonly string[]
   /** The declared formats that could not be judged, kept apart from the refusal above. */
   unverifiableMediaTypes: readonly string[]
+  /**
+   * The content types more than one selected integration produces, with the ids that share each.
+   * Computed through the SAME `binaryModalityOverlaps` the agent's brief renders from, so the
+   * picker and the brief cannot describe one selection two ways.
+   */
+  generatorOverlaps: readonly BinaryModalityOverlap[]
 }
 
 /**
@@ -433,6 +464,12 @@ export interface BinaryOutputPickState {
  * `binaryGeneratorSelectionIssues` so the builder surfaces the `binary_output_generator_invalid`
  * refusal before the round trip rather than inventing a second opinion.
  *
+ * What is mirrored is the DISPOSITION: which conditions refuse, which advise, and what each is
+ * called on this surface. The two rules underneath are IMPORTED (`binaryFormatCoverage`,
+ * `binaryModalityOverlaps`), because a rule restated on both sides of a wire is one that can come
+ * to two answers about the same selection, and the reader here is the person who would then be
+ * told the builder's version and the agent the other.
+ *
  * `unavailable` is the one state that is NOT derivable from the list, which is why the snapshot
  * carries it as its own flag. An empty list normally IS a real empty — this deployment registers
  * none — and that is exactly why a selected id in that state is `unknown_generator` rather than
@@ -453,16 +490,21 @@ function generatorPickIssues(
   uncovered: BinaryModality[]
   uncoveredMediaTypes: string[]
   unverifiableMediaTypes: string[]
+  overlaps: BinaryModalityOverlap[]
 } {
   const none = {
     unknownGeneratorIds: [],
     uncovered: [],
     uncoveredMediaTypes: [],
     unverifiableMediaTypes: [],
+    overlaps: [],
   }
   if (unavailable) return { issues: ['generators_unavailable'], ...none }
   const byId = new Map(generators.map((g) => [g.id, g]))
-  const selectedIds = config?.generatorIds ?? []
+  // Deduplicated on the way in, exactly as `resolveBinaryGeneratorSelection` does it on the
+  // backend: a step that names one integration twice holds ONE, and every line below states a
+  // count or a list a repeat would double.
+  const selectedIds = [...new Set(config?.generatorIds ?? [])]
   const unknownGeneratorIds = selectedIds.filter((id) => !byId.has(id))
   // Coverage is judged against what RESOLVED, exactly as admission judges it: an unknown id
   // contributes no content types, so a step whose only audio generator is unregistered is told
@@ -470,49 +512,28 @@ function generatorPickIssues(
   const selected = selectedIds.flatMap((id) => byId.get(id) ?? [])
   const covered = new Set(selected.flatMap((g) => g.modalities))
   const uncovered = (config?.modalities ?? []).filter((m) => !covered.has(m))
-  const format = formatCoverage(config?.mediaTypes ?? [], selected)
+  const format = binaryFormatCoverage(config?.mediaTypes ?? [], selected)
+  // Judged against what RESOLVED, like every rule above it, and against the SELECTION rather than
+  // the step's declared content types: the case that most often puts two producers of one kind on
+  // one step is the one where neither is the deliverable (an image generated to feed a mesh API),
+  // and gating on `modalities` would go silent on exactly that step.
+  const overlaps = binaryModalityOverlaps(selected)
   const issues: BinaryOutputPickIssue[] = []
   if (unknownGeneratorIds.length) issues.push('unknown_generator')
   if (uncovered.length) issues.push('modality_uncovered')
   if (format.uncovered.length) issues.push('media_type_uncovered')
   if (format.unverifiable.length) issues.push('media_type_unverifiable')
+  if (overlaps.length) issues.push('generator_overlap')
   return {
     issues,
     unknownGeneratorIds,
     uncovered,
     uncoveredMediaTypes: format.uncovered,
     unverifiableMediaTypes: format.unverifiable,
+    overlaps,
   }
 }
 
-/**
- * The SPA's copy of kernel's `binaryFormatCoverage`, restated for the reason the two `*_service`
- * members above are: the builder cannot see kernel, and the wire vocabulary that does cross
- * (`@cat-factory/contracts`) carries the schema, not the rule.
- *
- * The THIRD outcome is what must not be lost in the copying. A generator that declares no formats
- * has said "only my modality is known" — a documented state, not an empty answer — so a
- * requirement it cannot be judged against is unverifiable and the step still starts. Collapsing
- * that into `uncovered` would flag steps the backend admits (and send someone editing a selection
- * that is fine); collapsing it into silence would present an unchecked requirement as a checked
- * one.
- */
-function formatCoverage(
-  required: readonly string[],
-  selected: readonly Pick<RegisteredBinaryGenerator, 'mediaTypes'>[],
-): { uncovered: string[]; unverifiable: string[] } {
-  const emitted = new Set(selected.flatMap((g) => g.mediaTypes ?? []))
-  const undeclared = selected.some((g) => (g.mediaTypes ?? []).length === 0)
-  const uncovered: string[] = []
-  const unverifiable: string[] = []
-  for (const mediaType of required) {
-    if (emitted.has(mediaType)) continue
-    if (undeclared) unverifiable.push(mediaType)
-    else uncovered.push(mediaType)
-  }
-  return { uncovered, unverifiable }
-}
-
 /**
  * Validate a step's selection against the workspace's RESOLVED catalog — the same catalog run
  * admission re-validates against, which is the whole reason the picker offers only resolved
@@ -572,6 +593,7 @@ export function binaryOutputPickIssues(
       uncoveredModalities: generative.uncovered,
       uncoveredMediaTypes: generative.uncoveredMediaTypes,
       unverifiableMediaTypes: generative.unverifiableMediaTypes,
+      generatorOverlaps: generative.overlaps,
     }
   }
 
@@ -595,5 +617,6 @@ export function binaryOutputPickIssues(
     uncoveredModalities: generative.uncovered,
     uncoveredMediaTypes: generative.uncoveredMediaTypes,
     unverifiableMediaTypes: generative.unverifiableMediaTypes,
+    generatorOverlaps: generative.overlaps,
   }
 }

package/i18n/locales/de.json

@@ -3931,6 +3931,7 @@
       "binaryOutputMediaTypeUnverifiable": "Keine ausgewählte Integration gibt {formats} an, aber eine von ihnen gibt überhaupt keine Formate an, daher konnte das nicht geprüft werden. Der Schritt startet trotzdem; prüfe in der API der Integration, ob sie das erzeugen kann.",
       "binaryOutputMediaTypeUnusable": "Nicht gespeichert, denn dies sind keine Medientypen: {entries}. Schreibe jeden als type/subtype.",
       "binaryOutputGeneratorMissing": "Diese Installation registriert diese generativen Integrationen nicht: {ids}. Sie werden im Code der Installation registriert, nicht in diesem Workspace.",
+      "binaryOutputGeneratorOverlap": "Mehrere ausgewählte Integrationen erzeugen denselben Inhaltstyp ({overlaps}). Daran ist nichts falsch, aber der Inhaltstyp entscheidet nicht mehr, welche der Agent aufruft: Lege im Prompt dieses Schritts fest, welche wofür verwendet wird, sonst wählt er eine aus und bleibt dabei.",
       "binaryOutputModalityUncovered": "Keine ausgewählte Integration erzeugt {modalities}, was dieser Schritt liefern soll.",
       "binaryOutputModalityRetired": "{modality} (nicht mehr verfügbar — wähle die Inhaltstypen dieses Schritts neu)",
       "binaryOutputModality": {

package/i18n/locales/en.json

@@ -4424,6 +4424,8 @@
       "binaryOutputMediaTypeUnverifiable": "No selected integration declares {formats}, but one of them declares no formats at all, so this could not be checked. The step still starts; confirm from the integration's API that it can emit this.",
       "binaryOutputMediaTypeUnusable": "Not saved, because these are not media types: {entries}. Write each one as type/subtype.",
       "binaryOutputGeneratorMissing": "This deployment does not register these generative integrations: {ids}. They are registered in the deployment's code, not in this workspace.",
+      "binaryOutputGeneratorOverlap": "More than one selected integration produces the same content type ({overlaps}). Nothing is wrong with that, but the content type no longer decides which one the agent calls: say in this step's prompt which to use for what, or it will pick one and keep picking it.",
+      "@binaryOutputGeneratorOverlap": "{overlaps} is assembled by the app, not prose: a semicolon-separated list of 'content type: id, id' (e.g. 'Images: flux, retro-diffusion'). The ids are raw machine values and must not be translated; only the content-type label before each colon is translated, and it comes from its own key. This is advice, not an error: the step saves and runs either way, so keep the tone neutral.",
       "binaryOutputModalityUncovered": "No selected integration produces {modalities}, which this step is set to deliver.",
       "binaryOutputModalityRetired": "{modality} (no longer offered — re-pick this step's content types)",
       "@binaryOutputModalityRetired": "A content type saved on a step that this build no longer defines. {modality} is a raw machine value (e.g. 3d) and must not be translated. Appears inside the binaryOutputModalityUncovered sentence, so keep it a short noun phrase, not a sentence.",

package/i18n/locales/es.json

@@ -4293,6 +4293,7 @@
       "binaryOutputMediaTypeUnverifiable": "Ninguna integración seleccionada declara {formats}, pero una de ellas no declara ningún formato, así que no se pudo comprobar. El paso se inicia igualmente; confirma en la API de la integración que puede emitirlo.",
       "binaryOutputMediaTypeUnusable": "No se guardó, porque esto no son tipos de medio: {entries}. Escribe cada uno como type/subtype.",
       "binaryOutputGeneratorMissing": "Esta instalación no registra estas integraciones generativas: {ids}. Se registran en el código de la instalación, no en este espacio de trabajo.",
+      "binaryOutputGeneratorOverlap": "Más de una integración seleccionada produce el mismo tipo de contenido ({overlaps}). No hay nada malo en ello, pero el tipo de contenido ya no decide a cuál llama el agente: indica en el prompt de este paso cuál usar para qué, o elegirá una y seguirá usando esa.",
       "binaryOutputModalityUncovered": "Ninguna integración seleccionada produce {modalities}, que este paso debe entregar.",
       "binaryOutputModalityRetired": "{modality} (ya no disponible: vuelve a elegir los tipos de contenido de este paso)",
       "binaryOutputModality": {

package/i18n/locales/fr.json

@@ -4293,6 +4293,7 @@
       "binaryOutputMediaTypeUnverifiable": "Aucune intégration sélectionnée ne déclare {formats}, mais l’une d’elles ne déclare aucun format, cela n’a donc pas pu être vérifié. L’étape démarre quand même ; confirmez dans l’API de l’intégration qu’elle peut l’émettre.",
       "binaryOutputMediaTypeUnusable": "Non enregistré, car ce ne sont pas des types de média : {entries}. Écrivez chacun sous la forme type/subtype.",
       "binaryOutputGeneratorMissing": "Ce déploiement n'enregistre pas ces intégrations génératives : {ids}. Elles s'enregistrent dans le code du déploiement, pas dans cet espace de travail.",
+      "binaryOutputGeneratorOverlap": "Plusieurs intégrations sélectionnées produisent le même type de contenu ({overlaps}). Ce n’est pas un problème en soi, mais le type de contenu ne décide plus laquelle l’agent appelle : indiquez dans le prompt de cette étape laquelle utiliser et pour quoi, sinon il en choisira une et s’y tiendra.",
       "binaryOutputModalityUncovered": "Aucune intégration sélectionnée ne produit {modalities}, que cette étape doit livrer.",
       "binaryOutputModalityRetired": "{modality} (n'est plus proposé — resélectionnez les types de contenu de cette étape)",
       "binaryOutputModality": {

package/i18n/locales/he.json

@@ -4304,6 +4304,7 @@
       "binaryOutputMediaTypeUnverifiable": "אף אינטגרציה שנבחרה אינה מצהירה על {formats}, אבל אחת מהן אינה מצהירה על פורמטים כלל, ולכן לא ניתן היה לבדוק זאת. השלב יתחיל בכל מקרה; ודאו ב-API של האינטגרציה שהיא יכולה להפיק את זה.",
       "binaryOutputMediaTypeUnusable": "לא נשמר, כי אלה אינם סוגי מדיה: {entries}. כתבו כל אחד בצורה type/subtype.",
       "binaryOutputGeneratorMissing": "ההתקנה הזו אינה רושמת את האינטגרציות הגנרטיביות האלה: {ids}. הן נרשמות בקוד ההתקנה, לא במרחב העבודה הזה.",
+      "binaryOutputGeneratorOverlap": "יותר מאינטגרציה אחת שנבחרה מפיקה את אותו סוג תוכן ({overlaps}). אין בכך שום פסול, אבל סוג התוכן כבר לא קובע באיזו מהן הסוכן ישתמש: ציינו בהנחיות של השלב הזה באיזו להשתמש ולשם מה, אחרת הוא יבחר אחת וימשיך איתה.",
       "binaryOutputModalityUncovered": "אף אינטגרציה שנבחרה אינה מייצרת {modalities}, שהשלב הזה אמור לספק.",
       "binaryOutputModalityRetired": "{modality} (כבר לא נתמך — בחרו מחדש את סוגי התוכן של השלב)",
       "binaryOutputModality": {

package/i18n/locales/it.json

@@ -3931,6 +3931,7 @@
       "binaryOutputMediaTypeUnverifiable": "Nessuna integrazione selezionata dichiara {formats}, ma una di esse non dichiara alcun formato, quindi non è stato possibile verificarlo. Il passaggio parte comunque; verifica nell’API dell’integrazione che possa emetterlo.",
       "binaryOutputMediaTypeUnusable": "Non salvato, perché questi non sono tipi di media: {entries}. Scrivi ciascuno come type/subtype.",
       "binaryOutputGeneratorMissing": "Questa installazione non registra queste integrazioni generative: {ids}. Si registrano nel codice dell'installazione, non in questo spazio di lavoro.",
+      "binaryOutputGeneratorOverlap": "Più di un’integrazione selezionata produce lo stesso tipo di contenuto ({overlaps}). Non c’è nulla di sbagliato, ma il tipo di contenuto non decide più quale l’agente chiama: indica nel prompt di questo passaggio quale usare e per cosa, altrimenti ne sceglierà una e continuerà a usare quella.",
       "binaryOutputModalityUncovered": "Nessuna integrazione selezionata produce {modalities}, che questo passaggio deve fornire.",
       "binaryOutputModalityRetired": "{modality} (non più disponibile: riseleziona i tipi di contenuto di questo passaggio)",
       "binaryOutputModality": {

package/i18n/locales/ja.json

@@ -4305,6 +4305,7 @@
       "binaryOutputMediaTypeUnverifiable": "選択されたどの統合も {formats} を宣言していませんが、うち一つは形式をまったく宣言していないため、確認できませんでした。ステップはそのまま開始されます。その統合の API で出力できるか確認してください。",
       "binaryOutputMediaTypeUnusable": "メディアタイプではないため保存されませんでした: {entries}。それぞれ type/subtype の形で入力してください。",
       "binaryOutputGeneratorMissing": "このデプロイメントは次の生成統合を登録していません: {ids}。これらはこのワークスペースではなくデプロイメントのコードで登録します。",
+      "binaryOutputGeneratorOverlap": "選択された統合のうち複数が同じコンテンツタイプを生成します（{overlaps}）。それ自体は問題ありませんが、どれを呼び出すかをコンテンツタイプが決められなくなります。このステップのプロンプトで、どれを何に使うかを指定してください。指定がなければエージェントは一つを選び、そのまま使い続けます。",
       "binaryOutputModalityUncovered": "このステップが提供することになっている {modalities} を、選択されたどの統合も生成できません。",
       "binaryOutputModalityRetired": "{modality}（現在は提供されていません。このステップのコンテンツ種別を選び直してください）",
       "binaryOutputModality": {

package/i18n/locales/pl.json

@@ -4293,6 +4293,7 @@
       "binaryOutputMediaTypeUnverifiable": "Żadna wybrana integracja nie deklaruje {formats}, ale jedna z nich nie deklaruje żadnych formatów, więc nie dało się tego sprawdzić. Krok i tak wystartuje; potwierdź w API integracji, że potrafi to wytworzyć.",
       "binaryOutputMediaTypeUnusable": "Nie zapisano, bo to nie są typy mediów: {entries}. Zapisz każdy jako type/subtype.",
       "binaryOutputGeneratorMissing": "Ta instalacja nie rejestruje tych integracji generatywnych: {ids}. Rejestruje się je w kodzie instalacji, a nie w tym obszarze roboczym.",
+      "binaryOutputGeneratorOverlap": "Więcej niż jedna wybrana integracja tworzy ten sam typ treści ({overlaps}). Nie ma w tym nic złego, ale typ treści nie decyduje już, którą wywoła agent: napisz w promptcie tego kroku, której użyć i do czego, bo inaczej wybierze jedną i będzie jej używał dalej.",
       "binaryOutputModalityUncovered": "Żadna wybrana integracja nie tworzy {modalities}, które ten krok ma dostarczyć.",
       "binaryOutputModalityRetired": "{modality} (już niedostępne — wybierz ponownie typy treści tego kroku)",
       "binaryOutputModality": {

package/i18n/locales/tr.json

@@ -4305,6 +4305,7 @@
       "binaryOutputMediaTypeUnverifiable": "Seçili entegrasyonların hiçbiri {formats} bildirmiyor, ancak içlerinden biri hiç biçim bildirmiyor; bu yüzden denetlenemedi. Adım yine de başlar; entegrasyonun API’sinden bunu üretebildiğini doğrulayın.",
       "binaryOutputMediaTypeUnusable": "Kaydedilmedi, çünkü bunlar ortam türü değil: {entries}. Her birini type/subtype olarak yazın.",
       "binaryOutputGeneratorMissing": "Bu kurulum şu üretken entegrasyonları kaydetmiyor: {ids}. Bunlar bu çalışma alanında değil, kurulumun kodunda kaydedilir.",
+      "binaryOutputGeneratorOverlap": "Seçili entegrasyonlardan birden fazlası aynı içerik türünü üretiyor ({overlaps}). Bunda bir sakınca yok, ancak artık hangisinin çağrılacağına içerik türü karar vermiyor: bu adımın isteminde hangisinin ne için kullanılacağını belirtin, yoksa ajan birini seçip onu kullanmayı sürdürür.",
       "binaryOutputModalityUncovered": "Seçili entegrasyonların hiçbiri, bu adımın teslim etmesi gereken {modalities} içeriğini üretmiyor.",
       "binaryOutputModalityRetired": "{modality} (artık sunulmuyor — bu adımın içerik türlerini yeniden seçin)",
       "binaryOutputModality": {

package/i18n/locales/uk.json

@@ -4293,6 +4293,7 @@
       "binaryOutputMediaTypeUnverifiable": "Жодна вибрана інтеграція не заявляє {formats}, але одна з них взагалі не заявляє форматів, тому перевірити це не вдалося. Крок все одно запуститься; перевірте в API інтеграції, чи може вона це створити.",
       "binaryOutputMediaTypeUnusable": "Не збережено, бо це не типи медіа: {entries}. Запишіть кожен як type/subtype.",
       "binaryOutputGeneratorMissing": "Ця інсталяція не реєструє ці генеративні інтеграції: {ids}. Їх реєструють у коді інсталяції, а не в цьому робочому просторі.",
+      "binaryOutputGeneratorOverlap": "Кілька вибраних інтеграцій створюють той самий тип вмісту ({overlaps}). Нічого поганого в цьому немає, але тип вмісту більше не визначає, яку з них викличе агент: зазначте в промті цього кроку, яку і для чого використовувати, інакше він обере одну й користуватиметься лише нею.",
       "binaryOutputModalityUncovered": "Жодна вибрана інтеграція не створює {modalities}, які має надати цей крок.",
       "binaryOutputModalityRetired": "{modality} (більше не пропонується — виберіть типи вмісту цього кроку заново)",
       "binaryOutputModality": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cat-factory/app",
-  "version": "0.214.0",
+  "version": "0.215.1",
   "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.224.0"
+    "@cat-factory/contracts": "0.226.0"
   },
   "devDependencies": {
     "@toad-contracts/testing": "0.3.2",