@cat-factory/app 0.67.0 → 0.68.0

package/app/components/testing/TestReportWindow.vue

@@ -66,6 +66,30 @@ const infraSetup = computed(() => testState.value?.infraSetup ?? null)
 // The captured stand-up logs are shown on demand (they can be long).
 const showInfraSetupLogs = ref(false)
 
+// Once ALL of a tester's infrastructure is up (its container is running, the ephemeral
+// environment (when it tests against one) is ready, and any in-container dependency stand-up
+// succeeded) the agent can actually begin exercising the change. Surface an explicit line
+// saying so, so a run's details don't jump silently from "provisioning" straight into a blank
+// "working" state. This only fills the gap BEFORE the first working signal, so it is scoped
+// to a still-running step that hasn't produced a report yet: a finished step (state 'done'),
+// a failed run, or one that already has a report is past "starting", so the banner clears.
+// (The backend keeps the raw container status at 'up' after the step ends; 'destroyed' is a
+// display-only derivation in StepContainerStatus, so gating on the step state is what stops
+// the banner lingering.) Requires the container to actually report 'up' (a not-yet-created
+// container is not "up"), and requires the tester to genuinely depend on a test environment
+// (an ephemeral env or an in-container stand-up); an infraless tester has nothing to announce.
+const infraReady = computed(() => {
+  const s = step.value
+  if (!s || runFailed.value || s.state === 'done' || report.value) return false
+  if (s.container?.status !== 'up') return false
+  const env = stepEnvironment.value
+  const infra = infraSetup.value
+  if (!env && !infra) return false
+  const envReady = !env || env.status === 'ready'
+  const standupReady = !infra || infra.started
+  return envReady && standupReady
+})
+
 const screenshots = computed<TestScreenshot[]>(() => report.value?.screenshots ?? [])
 // Resolve each capture into an object URL for the gallery + lightbox. The shared cache
 // dedupes, so the lightbox reuses what the thumbnails fetched. (The reference design is not
@@ -424,6 +448,19 @@ const GROUP_STATUS_META: Record<ScenarioGroup['status'], { icon: string; text: s
                 </template>
               </div>
 
+              <!-- Explicit confirmation that every piece of the tester's infrastructure is up
+                   (container running, the ephemeral environment ready, any in-container
+                   dependency stand-up done) and the agent is now starting its work — so the
+                   details don't jump silently from "provisioning" into a blank working state. -->
+              <div
+                v-if="infraReady"
+                data-testid="tester-env-ready"
+                class="flex items-center gap-2 rounded-lg border border-emerald-500/30 bg-emerald-500/10 px-3 py-2 text-[13px] text-emerald-200"
+              >
+                <UIcon name="i-lucide-rocket" class="h-4 w-4 shrink-0 text-emerald-400" />
+                <span>{{ t('testing.readyBanner') }}</span>
+              </div>
+
               <div v-if="executionId">
                 <UButton
                   :icon="showProvisioning ? 'i-lucide-chevron-up' : 'i-lucide-scroll-text'"

package/i18n/locales/en.json

@@ -3180,6 +3180,7 @@
       "showLogs": "Show stand-up logs",
       "hideLogs": "Hide stand-up logs"
     },
+    "readyBanner": "Test environment is up. The tester is starting its work.",
     "footer": "Scenarios are the areas the Tester chose to exercise (its spec acceptance scenarios). Outcomes and concerns are grouped under them by name.",
     "@screenshotAlt": {
       "description": "Alt text for a captured screenshot thumbnail; {view} is the screen/view name. The literal word 'screenshot' should be localized."

package/i18n/locales/es.json

@@ -3052,6 +3052,7 @@
       "blocking": "({count} bloqueante) | ({count} bloqueantes)"
     },
     "environment": "Entorno",
+    "readyBanner": "El entorno de pruebas está listo. El Tester está comenzando su trabajo.",
     "footer": "Los escenarios son las áreas que el Tester decidió ejercitar (sus escenarios de aceptación de la especificación). Los resultados y las incidencias se agrupan bajo ellos por nombre.",
     "infrastructure": "Infraestructura",
     "standup": {

package/i18n/locales/fr.json

@@ -3052,6 +3052,7 @@
       "blocking": "({count} bloquante) | ({count} bloquantes)"
     },
     "environment": "Environnement",
+    "readyBanner": "L'environnement de test est prêt. Le Testeur commence son travail.",
     "footer": "Les scénarios sont les domaines que le Testeur a choisi d'éprouver (ses scénarios d'acceptation de la spécification). Les résultats et les réserves y sont regroupés par nom.",
     "infrastructure": "Infrastructure",
     "standup": {

package/i18n/locales/he.json

@@ -3071,6 +3071,7 @@
       "showLogs": "הצג יומני הקמה",
       "hideLogs": "הסתר יומני הקמה"
     },
+    "readyBanner": "סביבת הבדיקה פעילה. הבודק מתחיל בעבודתו.",
     "footer": "תרחישים הם התחומים שהבודק בחר לבחון (תרחישי קבלת המפרט שלו). תוצאות וחששות מקובצים תחתם לפי שם."
   },
   "visualConfirm": {

package/i18n/locales/ja.json

@@ -3073,6 +3073,7 @@
       "showLogs": "スタンドアップログを表示",
       "hideLogs": "スタンドアップログを非表示"
     },
+    "readyBanner": "テスト環境が起動しました。テスターが作業を開始します。",
     "footer": "シナリオはTesterが検証対象に選んだ領域(スペックの受け入れシナリオ)です。結果と懸念は名前ごとにその下にグループ化されます。"
   },
   "visualConfirm": {

package/i18n/locales/pl.json

@@ -3052,6 +3052,7 @@
       "blocking": "({count} blokujące) | ({count} blokujące) | ({count} blokujących)"
     },
     "environment": "Środowisko",
+    "readyBanner": "Środowisko testowe jest gotowe. Tester rozpoczyna pracę.",
     "footer": "Scenariusze to obszary, które Tester postanowił sprawdzić (jego scenariusze akceptacyjne ze specyfikacji). Wyniki i zastrzeżenia są pod nimi grupowane według nazwy.",
     "infrastructure": "Infrastruktura",
     "standup": {

package/i18n/locales/tr.json

@@ -3073,6 +3073,7 @@
       "showLogs": "Başlatma günlüklerini göster",
       "hideLogs": "Başlatma günlüklerini gizle"
     },
+    "readyBanner": "Test ortamı hazır. Test aracı çalışmaya başlıyor.",
     "footer": "Senaryolar, Tester'ın test etmek için seçtiği alanlardır (spesifikasyon kabul senaryoları). Sonuçlar ve endişeler ada göre bunların altında gruplanır."
   },
   "visualConfirm": {

package/i18n/locales/uk.json

@@ -3052,6 +3052,7 @@
       "blocking": "({count} блокувальне) | ({count} блокувальні) | ({count} блокувальних)"
     },
     "environment": "Середовище",
+    "readyBanner": "Тестове середовище готове. Тестувальник починає роботу.",
     "footer": "Сценарії — це області, які Тестувальник вирішив перевірити (його сценарії приймання зі специфікації). Результати та зауваження групуються під ними за назвою.",
     "infrastructure": "Інфраструктура",
     "standup": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cat-factory/app",
-  "version": "0.67.0",
+  "version": "0.68.0",
   "description": "Reusable Nuxt layer for the Agent Architecture Board SPA (components, stores, composables, pages). Consume it from a thin deployment app via `extends: ['@cat-factory/app']` and point it at your backend with NUXT_PUBLIC_API_BASE. See deploy/frontend for an example.",
   "repository": {
     "type": "git",