@cat-factory/app 0.234.2 → 0.236.0

package/app/composables/workspaceStream/applyWorkspaceEvent.ts

@@ -0,0 +1,173 @@
+import type {
+  Block,
+  BootstrapJob,
+  EnvConfigRepairJob,
+  EnvironmentTestRun,
+  ExecutionInstance,
+  InfraSetupArea,
+  InfraSetupStatus,
+  Initiative,
+  KaizenGrading,
+  LlmCallActivity,
+  Notification,
+  WorkspaceEvent,
+} from '~/types/domain'
+import type { BrainstormSession } from '~/types/brainstorm'
+import type { ClarityReview } from '~/types/clarity'
+import type { ConsensusSession } from '~/types/consensus'
+import type { DocInterviewSession } from '~/types/doc-interview'
+import type { RequirementReview } from '~/types/requirements'
+
+/**
+ * Everything {@link applyWorkspaceEvent} needs to route one pushed event into the stores, as bound
+ * callbacks rather than the stores themselves: it makes the routing (above all the `board` branch's
+ * targeted-vs-coarse decision) unit-testable without a Pinia instance or a live socket.
+ *
+ * Each callback names the DOMAIN type it takes, not the event field it happens to be fed from
+ * today. `upsertBlock` is the reason that matters: three branches (`execution`, `board`,
+ * `bootstrap`) share it, so typing it off any one of their payloads would silently retype the
+ * other two the next time that event's shape moved.
+ */
+export interface WorkspaceEventTargets {
+  upsertExecution: (instance: ExecutionInstance) => void
+  upsertBlock: (block: Block) => void
+  upsertBootstrap: (job: BootstrapJob) => void
+  upsertEnvConfigRepair: (job: EnvConfigRepairJob) => void
+  upsertEnvironmentTest: (run: EnvironmentTestRun) => void
+  patchInfraSetup: (area: InfraSetupArea, status: InfraSetupStatus, detail?: string) => void
+  upsertNotification: (n: Notification) => void
+  appendLlmCall: (call: LlmCallActivity) => void
+  upsertRequirements: (r: RequirementReview) => void
+  upsertConsensus: (s: ConsensusSession) => void
+  upsertClarity: (r: ClarityReview) => void
+  upsertBrainstorm: (s: BrainstormSession) => void
+  upsertKaizen: (g: KaizenGrading) => void
+  upsertInitiative: (i: Initiative) => void
+  upsertDocInterview: (s: DocInterviewSession) => void
+  /** Debounced full `workspace.refresh()`: the fallback for a change no payload can state. */
+  refreshBoard: () => void
+}
+
+/**
+ * Route one pushed workspace event into the stores.
+ *
+ * The `board` branch is the one with a decision in it. A `board` event used to mean "re-fetch the
+ * whole snapshot", which on an active board is a REPLACE-style rehydrate of ~20 stores every ~300ms
+ * debounce window, for changes as small as one spawned task. The backend now carries the changed
+ * block whenever the change is fully described by it (see the `board` case in
+ * `@cat-factory/contracts`' `WorkspaceEvent`), so those patch in place exactly like an `execution`
+ * event's block does, through the same `upsert` whose monotonic stamp keeps a later stale refresh
+ * from clobbering them.
+ *
+ * A `board` event with NO block keeps the old behaviour, and that is not a fallback to tidy away:
+ * a removal, a reparent, a blueprint reconcile and every service-frame change genuinely need the
+ * refresh, because their new shape is not one block's contents.
+ */
+export function applyWorkspaceEvent(event: WorkspaceEvent, to: WorkspaceEventTargets): void {
+  switch (event.type) {
+    case 'execution':
+      // Full instance drives the step-level UI; agentRuns derives its coarse
+      // failure/retry summary from the same store, so no extra call is needed.
+      to.upsertExecution(event.instance)
+      if (event.block) to.upsertBlock(event.block)
+      return
+    case 'board':
+      // Targeted when the change fits in one block, coarse otherwise. Both shapes reach every
+      // board that mounts the affected service; only the cost differs.
+      if (event.block) to.upsertBlock(event.block)
+      else to.refreshBoard()
+      return
+    case 'bootstrap':
+      // Patch the run's live status/subtasks and its provisional/linked frame so
+      // the "bootstrapping…" card updates in place (then flips to a ready service
+      // or a failed badge) without a full refresh.
+      to.upsertBootstrap(event.job)
+      if (event.block) to.upsertBlock(event.block)
+      return
+    case 'env-config-repair':
+      // A provider config-repair run advanced: patch its live status/subtasks/outcome so the
+      // infrastructure-providers window's "repairing…" indicator updates in place (then flips to
+      // ok / residual issues / a failure) without a refetch. No board block.
+      to.upsertEnvConfigRepair(event.job)
+      return
+    case 'envTest':
+      // An ephemeral-environment self-test advanced a stage: patch the run so the service
+      // inspector's "Test environment creation" control shows the live stage + final outcome in
+      // place without a refetch. No board block.
+      to.upsertEnvironmentTest(event.run)
+      return
+    case 'infraSetup':
+      // The reachability watcher found a configured infrastructure area dead (or answering again):
+      // patch that one area so the setup banner appears/clears immediately. A full refresh would
+      // pay the whole snapshot aggregate for a one-field delta, and the projection the snapshot
+      // recomputes already folds the same recorded state.
+      to.patchInfraSetup(event.area, event.status, event.detail)
+      return
+    case 'notification':
+      // A PR needs a merge decision, a pipeline finished, or CI gave up: patch the
+      // inbox + per-block badge in place (resolved ones drop out of the inbox).
+      to.upsertNotification(event.notification)
+      return
+    case 'llmCall':
+      // A container agent just made a model call: fold the compact summary into the observability
+      // store so an open "Model activity" panel updates live (and keeps updating even when the
+      // durable driver is evicted, since the proxy emits these independently of the poll loop).
+      to.appendLlmCall(event.call)
+      return
+    case 'requirements':
+      // The async incorporate + re-review cycle changed a review's status: patch the cache so an
+      // open review window / inspector reflects it live ("incorporating…" → the next cycle /
+      // converged). The summons back, when needed, arrives as a `notification`.
+      to.upsertRequirements(event.review)
+      return
+    case 'consensus':
+      // A consensus session advanced (a round landed, the synthesis completed, or it failed):
+      // patch the cache so an open Consensus Session window renders the multi-model process live,
+      // round by round.
+      to.upsertConsensus(event.session)
+      return
+    case 'clarity':
+      // The clarity mirror of `requirements`.
+      to.upsertClarity(event.review)
+      return
+    case 'brainstorm':
+      // The async incorporate + re-run cycle changed a brainstorm session's status: patch the
+      // cache so an open brainstorm window / inspector reflects it live.
+      to.upsertBrainstorm(event.session)
+      return
+    case 'kaizen':
+      // A post-run Kaizen grading was scheduled, started or completed: fold it into the run cache
+      // (so an open run window shows scheduled→running→complete live) and the Kaizen screen
+      // history. Never surfaced on the board.
+      to.upsertKaizen(event.grading)
+      return
+    case 'initiative':
+      // An initiative changed (created, plan ingested, an item settled): patch the cache so an
+      // open tracker window / the board card reflects the transition live.
+      to.upsertInitiative(event.initiative)
+      return
+    case 'docInterview':
+      // The interactive document interview advanced (a fresh batch of questions, an answer, or
+      // convergence): patch the cache so an open interview window reflects it live.
+      to.upsertDocInterview(event.session)
+      return
+    default:
+      return dropUnknownEvent(event)
+  }
+}
+
+/**
+ * The exhaustiveness guard for the routing above.
+ *
+ * The COMPILE-TIME half is the point: `never` fails the build the moment `WorkspaceEvent` gains a
+ * member with no case, so a new pushed event cannot ship as a branch that silently does nothing.
+ * The spec's per-type table cannot do that job: a member absent from a hand-written list is just
+ * absent, and the suite stays green.
+ *
+ * At RUNTIME this deliberately drops the event. A backend one release ahead of the SPA legitimately
+ * pushes types this build has never heard of, and the connection carries every other event for the
+ * whole workspace: throwing would trade one unknown payload for the entire live session.
+ */
+function dropUnknownEvent(event: never): void {
+  void event
+}

package/app/stores/agents.ts

@@ -69,9 +69,11 @@ export const useAgentsStore = defineStore('agents', () => {
    * mapped to display metadata, de-duplicated, and never shadowing a built-in or
    * system kind. The old `registerCustomKinds` only guarded `AGENT_BY_KIND`; this
    * intentionally ALSO drops any custom kind colliding with a `SYSTEM_AGENT_META`
-   * kind (`ci` / `merger` / `blueprints` / gates …), so a snapshot can't override an
-   * engine kind's palette entry either — matching `agentKindMeta`'s precedence
-   * (built-in → system → custom), where a colliding custom kind would never win anyway.
+   * kind (`ci` / `merger` / gates …), so a snapshot can't override an engine kind's
+   * palette entry either — matching `agentKindMeta`'s precedence (built-in → system
+   * → custom), where a colliding custom kind would never win anyway. Note the cost of
+   * that guard: a SYSTEM_AGENT_META entry silently removes a registered kind from the
+   * palette, so the map must stay limited to kinds the engine inserts itself.
    */
   const customArchetypes = computed<AgentArchetype[]>(() => {
     const seen = new Set<string>()

package/app/stores/documents.ts

@@ -9,6 +9,7 @@ import type {
   DocumentOrigin,
   DocumentSourceDescriptor,
   DocumentSourceKind,
+  ResolvedDocumentRef,
   SourceDocument,
 } from '~/types/domain'
 import { isConnectableSource } from '@cat-factory/contracts'
@@ -82,6 +83,16 @@ export const useDocumentsStore = defineStore('documents', () => {
     documents.value = await api.listDocuments(workspace.requireId())
   }
 
+  /**
+   * Canonicalise a pasted URL/id into the reference this source would store it under, WITHOUT
+   * importing it. The backend's providers own the rule, so the picker validates against the same
+   * parse the import will run rather than a second copy of it that can drift; a ref the source
+   * cannot read comes back as a 422 whose `details.reason` says which correction it needs.
+   */
+  function resolveRef(source: DocumentSourceKind, ref: string): Promise<ResolvedDocumentRef> {
+    return api.resolveDocumentRef(workspace.requireId(), source, { ref })
+  }
+
   /** Import (fetch + persist) a page by id or URL from a source. */
   async function importDocument(source: DocumentSourceKind, ref: string): Promise<SourceDocument> {
     loading.value = true
@@ -211,6 +222,7 @@ export const useDocumentsStore = defineStore('documents', () => {
     connect,
     disconnect,
     loadDocuments,
+    resolveRef,
     importDocument,
     search,
     plan,

package/app/types/documents.ts

@@ -17,6 +17,8 @@ export type {
   DocumentConnection,
   SourceDocument,
   DocumentSearchResult,
+  DocumentRefReason,
+  ResolvedDocumentRef,
   PlanTask,
   PlanModule,
   PlanFrame,

package/app/utils/catalog.spec.ts

@@ -4,6 +4,8 @@ import {
   AGENT_ARCHETYPES,
   AGENT_BY_KIND,
   BLOCK_TYPE_META,
+  COMPANION_FOR_PRODUCER,
+  MODEL_CONFIGURABLE_SYSTEM_KINDS,
   STATUS_META,
   SYSTEM_AGENT_META,
   agentKindMeta,
@@ -20,9 +22,12 @@ const AGENT_KINDS: AgentKind[] = [
   'pr-reviewer',
   'spike',
   'task-estimator',
+  'spec-writer',
+  'blueprints',
   'architect',
   'researcher',
   'coder',
+  'deployer',
   'tester-api',
   'tester-ui',
   'reviewer',
@@ -80,6 +85,38 @@ describe('catalog', () => {
     expect(basic).toEqual(expect.arrayContaining(['architect', 'coder', 'tester-api']))
   })
 
+  it('never shadows a companion producer as a system kind', () => {
+    // A companion is never placed directly: the builder renders it as a toggle on its producer
+    // step, so a producer that cannot be placed takes its companion out of the builder with it.
+    // A producer reaches the palette either statically (AGENT_ARCHETYPES) or from the backend
+    // registry — and an entry in SYSTEM_AGENT_META DROPS the registry's copy (see the agents
+    // store's `customArchetypes`), which is how `spec-writer` and its `spec-companion` both
+    // became unreachable. The shadow is the half this file owns, so it is the half asserted.
+    for (const producer of Object.keys(COMPANION_FOR_PRODUCER)) {
+      expect(
+        producer in SYSTEM_AGENT_META,
+        `${producer} has a companion but is shadowed as a system kind, so neither can be placed`,
+      ).toBe(false)
+    }
+  })
+
+  it('resolves every kind the Model Defaults panel lists beside the palette', () => {
+    // The list is spelled as kind strings indexed into SYSTEM_AGENT_META through a non-null
+    // assertion, so a kind that MOVES to the palette (or is renamed) leaves an `undefined` in
+    // the array rather than a type error, and the panel renders a blank row it cannot pin a
+    // model on. Assert the relation the assertion claims.
+    for (const entry of MODEL_CONFIGURABLE_SYSTEM_KINDS) {
+      expect(entry, 'MODEL_CONFIGURABLE_SYSTEM_KINDS names a kind with no metadata').toBeDefined()
+      expect(entry.kind).toEqual(expect.any(String))
+    }
+    // And nothing is offered twice: a palette archetype is already listed by the panel, so a
+    // kind appearing in both would render a duplicate row.
+    const palette = new Set(AGENT_ARCHETYPES.map((a) => a.kind))
+    for (const entry of MODEL_CONFIGURABLE_SYSTEM_KINDS) {
+      expect(palette.has(entry.kind), `${entry.kind} is listed twice in Model Defaults`).toBe(false)
+    }
+  })
+
   it('resolves usable metadata for every kind via agentKindMeta', () => {
     // Palette archetypes resolve to their own entry.
     for (const a of AGENT_ARCHETYPES) {
@@ -88,8 +125,6 @@ describe('catalog', () => {
     // Engine system kinds (present in seeded pipelines but not the palette) resolve
     // to their system metadata rather than blowing up an undefined access.
     for (const kind of [
-      'spec-writer',
-      'blueprints',
       'conflicts',
       'conflict-resolver',
       'ci',

package/app/utils/catalog.ts

@@ -136,6 +136,21 @@ export const AGENT_ARCHETYPES: AgentArchetype[] = [
       'A structured dialogue that explores and finalizes a technical approach from the refined requirements — proposing options with explicit trade-offs and letting you converge, before the architect.',
     resultView: 'brainstorm',
   },
+  {
+    // Authors the service's in-repo specification from the clarified requirements, so it sits
+    // beside the design kinds and ahead of the architect that reads what it wrote. Registered on
+    // the backend so it also arrives via the workspace manifest, and modelled statically here for
+    // the same reason `pr-reviewer` is: a `pl_bugfix` / `pl_spec` timeline must name the step
+    // before the manifest hydrates. Mirrors the backend `presentation` in `spec-blueprints.ts`.
+    kind: 'spec-writer',
+    tier: 'intermediate',
+    label: 'Spec Writer',
+    icon: 'i-lucide-clipboard-list',
+    color: '#c084fc',
+    category: 'design',
+    description:
+      "Aggregates every task's clarified requirements into the service's in-repo specification (spec.json) with full acceptance-scenario coverage, derived into Gherkin.",
+  },
   {
     kind: 'architect',
     tier: 'basic',
@@ -145,6 +160,18 @@ export const AGENT_ARCHETYPES: AgentArchetype[] = [
     category: 'design',
     description: 'Designs the shape of the solution and breaks down the work.',
   },
+  {
+    // Refreshes the service → modules map the board projects. Statically modelled beside its
+    // backend `presentation` for the same reason the Spec Writer is: `pl_blueprint` timelines
+    // render before the manifest hydrates.
+    kind: 'blueprints',
+    tier: 'intermediate',
+    label: 'Blueprinter',
+    icon: 'i-lucide-map',
+    color: '#22d3ee',
+    category: 'design',
+    description: 'Maps the repository into the service → modules blueprint.',
+  },
   {
     kind: 'researcher',
     tier: 'intermediate',
@@ -181,6 +208,21 @@ export const AGENT_ARCHETYPES: AgentArchetype[] = [
     category: 'build',
     description: 'Builds WireMock mocks for external services and wires them into local/CI runs.',
   },
+  {
+    // Provisions the ephemeral environment the tester / human-test / playwright steps read, which
+    // is why it leads the testing group. A palette block for the same reason `disposer` is one:
+    // `assertDeployerBeforeConsumer` REFUSES a run whose chain reaches an env consumer with no
+    // Deployer in front of it on a deployable service, and a hand-built pipeline that hits that
+    // refusal has no reseed to fall back on.
+    kind: 'deployer',
+    tier: 'intermediate',
+    label: 'Deployer',
+    icon: 'i-lucide-cloud-upload',
+    color: '#34d399',
+    category: 'test',
+    description:
+      'Provisions the ephemeral environment the tester and human-test gate run against (kubernetes / custom services); a no-op for docker-compose / infraless. Place it before the first step that needs the environment.',
+  },
   {
     kind: 'tester-api',
     tier: 'basic',
@@ -491,29 +533,22 @@ export function isTesterKind(kind: string): boolean {
 
 /**
  * Display metadata for the engine-driven "system" kinds — the gate/automation
- * steps (blueprint mapper, conflicts gate + resolver, CI gate + fixer, merger)
- * that appear in seeded pipelines and run timelines but are NOT user-addable
- * palette archetypes, so they're intentionally absent from {@link AGENT_ARCHETYPES}
+ * steps (conflicts gate + resolver, CI gate + fixer, merger) that appear in
+ * seeded pipelines and run timelines but are NOT user-addable palette
+ * archetypes, so they're intentionally absent from {@link AGENT_ARCHETYPES}
  * / {@link AGENT_BY_KIND}. Looked up through {@link agentKindMeta}.
+ *
+ * An entry here also SHADOWS the backend's own catalog: the agents store drops any
+ * registered kind whose id appears in this map (see `customArchetypes`), so listing a
+ * kind that declares `presentation` silently overrides the deployment's decision to
+ * offer it. That is how `spec-writer` and `blueprints` stayed out of the palette while
+ * both collapse docs promised them as opt-in builder steps, and it took
+ * `spec-companion` with them: a companion renders as a toggle on its producer, so a
+ * shadowed producer removes both. Add a kind here only when the ENGINE decides the
+ * step exists — a gate it inserts, a helper it escalates to — and never when the
+ * backend registers it as a palette block.
  */
 export const SYSTEM_AGENT_META: Record<string, AgentArchetype> = {
-  'spec-writer': {
-    kind: 'spec-writer',
-    tier: 'intermediate',
-    label: 'Spec Writer',
-    icon: 'i-lucide-clipboard-list',
-    color: '#c084fc',
-    description:
-      "Aggregates every task's clarified requirements into the service's in-repo specification (spec.json) with full acceptance-scenario coverage, derived into Gherkin.",
-  },
-  blueprints: {
-    kind: 'blueprints',
-    tier: 'intermediate',
-    label: 'Blueprinter',
-    icon: 'i-lucide-map',
-    color: '#22d3ee',
-    description: 'Maps the repository into the service → modules blueprint.',
-  },
   // The read-only Challenge Investigator: dispatched off a parked `pr-reviewer` step when a human
   // challenges a finding, it re-examines that ONE finding against the full source and upholds
   // (strengthening) or retracts it. Never a palette block; modelled here purely so it is a
@@ -529,19 +564,6 @@ export const SYSTEM_AGENT_META: Record<string, AgentArchetype> = {
       'Re-examines a single challenged PR-review finding against the full source, then upholds ' +
       '(strengthening it) or retracts it with a justification. Configurable separately from the reviewer.',
   },
-  // The single environment provisioner: an operational (non-LLM) step that stands up the ephemeral
-  // environment the tester / human-test gate run against for a kubernetes/custom service, and is a
-  // fast no-op for docker-compose / infraless. Seeded before the first tester/human-test step in the
-  // built-in pipelines, so it needs display metadata (else it renders as a generic gray "Agent").
-  deployer: {
-    kind: 'deployer',
-    tier: 'intermediate',
-    label: 'Deployer',
-    icon: 'i-lucide-cloud-upload',
-    color: '#34d399',
-    description:
-      'Provisions the ephemeral environment the tester and human-test gate run against (kubernetes / custom services); a no-op for docker-compose / infraless.',
-  },
   // The Initiative Planning pipeline's steps. Only runnable on an initiative
   // block (pl_initiative — enforced by the engine), so they are display-metadata
   // system kinds, never palette archetypes. The analyst runs FIRST, ahead of the
@@ -766,8 +788,6 @@ export const OBSERVABILITY_GATE_ARCHETYPE: AgentArchetype =
  */
 export const MODEL_CONFIGURABLE_SYSTEM_KINDS: AgentArchetype[] = [
   ...[
-    'spec-writer',
-    'blueprints',
     'initiative-planner',
     'conflict-resolver',
     'ci-fixer',
@@ -798,7 +818,7 @@ const FALLBACK_AGENT_META: Omit<AgentArchetype, 'kind'> = {
  * {@link customAgentKindMeta} by the agents store), or an unknown one — ALWAYS
  * returning a usable icon/label/color. This is the single lookup every pipeline
  * / run renderer should use so a kind missing from the archetype map (e.g.
- * `ci`/`merger`/`blueprints` in a seeded pipeline) can never blow up a component
+ * `ci`/`merger` in a seeded pipeline) can never blow up a component
  * with an undefined access. Reading `customAgentKindMeta` reactively means a
  * component computed re-runs when the custom catalog changes.
  */

package/i18n/locales/de.json

@@ -2818,7 +2818,8 @@
         "derivedTitleFallback": "Pull Request prüfen",
         "prNotFound": "Pull Request #{number} wurde im Repository dieses Service nicht gefunden. Prüfe die Nummer, oder verknüpfe den Service mit dem Repository, in dem der Pull Request liegt.",
         "prRepoMismatch": "Dieser Pull Request liegt in einem anderen Repository. Dieser Service prüft {repo}; lege die Prüfaufgabe unter dem Service an, der mit dem Repository des Pull Requests verknüpft ist."
-      }
+      },
+      "contextFailed": "Aufgabe nicht erstellt: {count} Anhang konnte nicht gelesen werden | Aufgabe nicht erstellt: {count} Anhänge konnten nicht gelesen werden"
     },
     "recurring": {
       "title": "Eine wiederkehrende Pipeline hinzufügen",
@@ -3004,7 +3005,8 @@
     "attachDocDisabledEnable": "Aktivieren Sie zuerst die Dokumente-Integration",
     "attachIssueDisabledConnect": "Verbinden Sie zuerst einen Issue-Tracker (Integrationen)",
     "attachIssueDisabledEnable": "Aktivieren Sie zuerst die Issue-Tracker-Integration",
-    "importsOnAdd": "importiert beim Hinzufügen"
+    "importsOnAdd": "importiert beim Hinzufügen",
+    "unreadable": "Konnte nicht abgerufen werden: {error}"
   },
   "providers": {
     "presetMismatch": {
@@ -3783,7 +3785,15 @@
       "attachByReference": "{ref} per Referenz anhängen",
       "noMatches": "Keine passenden Seiten.",
       "emptySearchable": "Nach Titel suchen oder ein importiertes Dokument auswählen.",
-      "emptyRefOnly": "Fügen Sie eine Seiten-URL oder -ID ein, um sie anzuhängen."
+      "emptyRefOnly": "Fügen Sie eine Seiten-URL oder -ID ein, um sie anzuhängen.",
+      "refChecking": "Referenz wird geprüft…",
+      "refUnrecognized": "Keine {source}-Referenz. Erwartet: {expected}",
+      "refOtherSource": "Das ist ein {claimed}-Link, kein {source}-Link.",
+      "refSwitchSource": "Stattdessen {source} verwenden",
+      "refTrimmed": "Auf die unterstützte Form gekürzt",
+      "refWidened": "Nennt einen Frame, den diese Quelle nicht lesen kann ({scope}); daher wird die gesamte Datei angehängt.",
+      "refAlreadyAttached": "Diese Referenz ist bereits angehängt.",
+      "refCheckFailed": "Referenz konnte nicht geprüft werden: {error}"
     },
     "repoPicker": {
       "searchRepoPlaceholder": "Repositorys suchen…",
@@ -5040,7 +5050,8 @@
       "failedTitle": "Die Initiative konnte nicht erstellt werden",
       "contextDocsHint": "Hänge eine Anforderung, ein RFC oder ein PRD an, damit die Planungsagenten es beim Abstecken und Entwerfen des Plans lesen.",
       "contextIssuesHint": "Hänge ein Tracker-Issue an, damit die Planungsagenten beim Entwerfen des Plans seine Beschreibung und Kommentare sehen.",
-      "linkFailed": "Initiative erstellt, aber {count} Anhang konnte nicht verknüpft werden | Initiative erstellt, aber {count} Anhänge konnten nicht verknüpft werden"
+      "linkFailed": "Initiative erstellt, aber {count} Anhang konnte nicht verknüpft werden | Initiative erstellt, aber {count} Anhänge konnten nicht verknüpft werden",
+      "contextFailed": "Initiative nicht erstellt: {count} Anhang konnte nicht gelesen werden | Initiative nicht erstellt: {count} Anhänge konnten nicht gelesen werden"
     },
     "status": {
       "planning": "Planung",

package/i18n/locales/en.json

@@ -347,6 +347,10 @@
         "derivedTitleFallback": "Review pull request",
         "prNotFound": "Pull request #{number} was not found in this service's repository. Check the number, or link the service to the repository that pull request is on.",
         "prRepoMismatch": "That pull request is on a different repository. This service reviews {repo}, so create the review task under the service linked to the pull request's repository."
+      },
+      "contextFailed": "Task not created: {count} attachment could not be read | Task not created: {count} attachments could not be read",
+      "@contextFailed": {
+        "description": "Count-based: how many context attachments (docs/issues) could not be fetched, which is why nothing was created (count is always >= 1). Provide ALL plural forms your language needs (English has 2; Polish/Ukrainian need 3 - one/few/many - via the custom pluralRules in i18n.config.ts)."
       }
     },
     "recurring": {
@@ -548,7 +552,8 @@
     "attachDocDisabledEnable": "Enable the documents integration first",
     "attachIssueDisabledConnect": "Connect an issue tracker first (Integrations)",
     "attachIssueDisabledEnable": "Enable the issue-tracker integration first",
-    "importsOnAdd": "imports on add"
+    "importsOnAdd": "imports on add",
+    "unreadable": "Could not be fetched: {error}"
   },
   "errors": {
     "generic": {
@@ -4300,7 +4305,15 @@
       "attachByReference": "Attach {ref} by reference",
       "noMatches": "No matching pages.",
       "emptySearchable": "Search by title, or pick an imported document.",
-      "emptyRefOnly": "Paste a page URL or ID to attach it."
+      "emptyRefOnly": "Paste a page URL or ID to attach it.",
+      "refChecking": "Checking the reference…",
+      "refUnrecognized": "Not a {source} reference. Expected {expected}",
+      "refOtherSource": "That is a {claimed} link, not a {source} one.",
+      "refSwitchSource": "Use {source} instead",
+      "refTrimmed": "Trimmed to the supported form",
+      "refWidened": "Names a frame this source cannot read ({scope}), so the whole file is attached.",
+      "refAlreadyAttached": "This reference is already attached.",
+      "refCheckFailed": "Could not check the reference: {error}"
     },
     "repoPicker": {
       "searchRepoPlaceholder": "Search repositories…",
@@ -6515,6 +6528,10 @@
       "linkFailed": "Initiative created, but {count} attachment could not be linked | Initiative created, but {count} attachments could not be linked",
       "@linkFailed": {
         "description": "Count-based: how many context attachments (docs/issues) failed to link after the initiative was created (count is always >= 1). Provide ALL plural forms your language needs (English has 2; Polish/Ukrainian need 3 - one/few/many - via the custom pluralRules in i18n.config.ts)."
+      },
+      "contextFailed": "Initiative not created: {count} attachment could not be read | Initiative not created: {count} attachments could not be read",
+      "@contextFailed": {
+        "description": "Count-based: how many context attachments (docs/issues) could not be fetched, which is why nothing was created (count is always >= 1). Provide ALL plural forms your language needs (English has 2; Polish/Ukrainian need 3 - one/few/many - via the custom pluralRules in i18n.config.ts)."
       }
     },
     "status": {

package/i18n/locales/es.json

@@ -311,7 +311,8 @@
         "derivedTitleFallback": "Revisar la pull request",
         "prNotFound": "No se encontró la pull request n.º {number} en el repositorio de este servicio. Comprueba el número, o vincula el servicio al repositorio en el que está esa pull request.",
         "prRepoMismatch": "Esa pull request está en otro repositorio. Este servicio revisa {repo}, así que crea la tarea de revisión en el servicio vinculado al repositorio de la pull request."
-      }
+      },
+      "contextFailed": "Tarea no creada: no se pudo leer {count} adjunto | Tarea no creada: no se pudieron leer {count} adjuntos"
     },
     "recurring": {
       "title": "Añadir una pipeline recurrente",
@@ -497,7 +498,8 @@
     "attachDocDisabledEnable": "Activa primero la integración de documentos",
     "attachIssueDisabledConnect": "Conecta primero un gestor de incidencias (Integraciones)",
     "attachIssueDisabledEnable": "Activa primero la integración del gestor de incidencias",
-    "importsOnAdd": "se importa al añadir"
+    "importsOnAdd": "se importa al añadir",
+    "unreadable": "No se pudo obtener: {error}"
   },
   "errors": {
     "generic": {
@@ -4166,7 +4168,15 @@
       "attachByReference": "Adjuntar {ref} por referencia",
       "noMatches": "No hay páginas que coincidan.",
       "emptySearchable": "Busca por título o elige un documento importado.",
-      "emptyRefOnly": "Pega la URL o el ID de una página para adjuntarla."
+      "emptyRefOnly": "Pega la URL o el ID de una página para adjuntarla.",
+      "refChecking": "Comprobando la referencia…",
+      "refUnrecognized": "No es una referencia de {source}. Se esperaba {expected}",
+      "refOtherSource": "Es un enlace de {claimed}, no de {source}.",
+      "refSwitchSource": "Usar {source} en su lugar",
+      "refTrimmed": "Recortado al formato admitido",
+      "refWidened": "Nombra un marco que esta fuente no puede leer ({scope}), así que se adjunta el archivo completo.",
+      "refAlreadyAttached": "Esta referencia ya está adjunta.",
+      "refCheckFailed": "No se pudo comprobar la referencia: {error}"
     },
     "repoPicker": {
       "searchRepoPlaceholder": "Buscar repositorios…",
@@ -6296,7 +6306,8 @@
       "failedTitle": "No se pudo crear la iniciativa",
       "contextDocsHint": "Adjunta un requisito, RFC o PRD para que los agentes de planificación lo lean al delimitar y redactar el plan.",
       "contextIssuesHint": "Adjunta una incidencia para que los agentes de planificación vean su descripción y comentarios al redactar el plan.",
-      "linkFailed": "Iniciativa creada, pero no se pudo vincular {count} adjunto | Iniciativa creada, pero no se pudieron vincular {count} adjuntos"
+      "linkFailed": "Iniciativa creada, pero no se pudo vincular {count} adjunto | Iniciativa creada, pero no se pudieron vincular {count} adjuntos",
+      "contextFailed": "Iniciativa no creada: no se pudo leer {count} adjunto | Iniciativa no creada: no se pudieron leer {count} adjuntos"
     },
     "status": {
       "planning": "Planificando",

package/i18n/locales/fr.json

@@ -311,7 +311,8 @@
         "derivedTitleFallback": "Examiner la pull request",
         "prNotFound": "La pull request n° {number} est introuvable dans le dépôt de ce service. Vérifiez le numéro, ou reliez le service au dépôt qui héberge cette pull request.",
         "prRepoMismatch": "Cette pull request se trouve dans un autre dépôt. Ce service examine {repo} : créez la tâche de revue sous le service relié au dépôt de la pull request."
-      }
+      },
+      "contextFailed": "Tâche non créée : {count} pièce jointe illisible | Tâche non créée : {count} pièces jointes illisibles"
     },
     "recurring": {
       "title": "Ajouter une pipeline récurrente",
@@ -497,7 +498,8 @@
     "attachDocDisabledEnable": "Activez d’abord l’intégration de documents",
     "attachIssueDisabledConnect": "Connectez d’abord un suivi de tickets (Intégrations)",
     "attachIssueDisabledEnable": "Activez d’abord l’intégration du suivi de tickets",
-    "importsOnAdd": "importé à l’ajout"
+    "importsOnAdd": "importé à l’ajout",
+    "unreadable": "Récupération impossible : {error}"
   },
   "errors": {
     "generic": {
@@ -4166,7 +4168,15 @@
       "attachByReference": "Joindre {ref} par référence",
       "noMatches": "Aucune page correspondante.",
       "emptySearchable": "Recherchez par titre ou choisissez un document importé.",
-      "emptyRefOnly": "Collez l'URL ou l'ID d'une page pour la joindre."
+      "emptyRefOnly": "Collez l'URL ou l'ID d'une page pour la joindre.",
+      "refChecking": "Vérification de la référence…",
+      "refUnrecognized": "Ce n'est pas une référence {source}. Format attendu : {expected}",
+      "refOtherSource": "C'est un lien {claimed}, pas un lien {source}.",
+      "refSwitchSource": "Utiliser {source} à la place",
+      "refTrimmed": "Réduit au format pris en charge",
+      "refWidened": "Désigne un cadre que cette source ne peut pas lire ({scope}) : le fichier entier est donc joint.",
+      "refAlreadyAttached": "Cette référence est déjà jointe.",
+      "refCheckFailed": "Impossible de vérifier la référence : {error}"
     },
     "repoPicker": {
       "searchRepoPlaceholder": "Rechercher des dépôts…",
@@ -6296,7 +6306,8 @@
       "failedTitle": "Impossible de creer l'initiative",
       "contextDocsHint": "Joignez une exigence, une RFC ou un PRD pour que les agents de planification la lisent en cadrant et en rédigeant le plan.",
       "contextIssuesHint": "Joignez un ticket pour que les agents de planification voient sa description et ses commentaires en rédigeant le plan.",
-      "linkFailed": "Initiative créée, mais {count} pièce jointe n’a pas pu être liée | Initiative créée, mais {count} pièces jointes n’ont pas pu être liées"
+      "linkFailed": "Initiative créée, mais {count} pièce jointe n’a pas pu être liée | Initiative créée, mais {count} pièces jointes n’ont pas pu être liées",
+      "contextFailed": "Initiative non créée : {count} pièce jointe illisible | Initiative non créée : {count} pièces jointes illisibles"
     },
     "status": {
       "planning": "Planification",