Date: 2026-02-22
Checklist Item: UX-007
Ticket: ISIS-0232
Journey Scope#
User state: authenticated submit-capable user
Journey: select expensive run profile -> receive RunPod quota/cost warning ->
acknowledge -> submit
Coverage target: warning is visible before expensive submission and blocks
submit until acknowledgment
Evidence Matrix#
| Requirement | Evidence | Status |
|---|---|---|
| Warning appears before expensive run | apps/isis/web/src/pages/JobSubmissionStudio.tsx now computes expensive-run profiles (generation type, priority, size, steps) and combines with RunPod risk telemetry (runpod.warning, low credits, high estimated monthly cost) to show a RunPod Cost Warning section pre-submit. |
Pass |
| Warning is tied to real RunPod telemetry signals | Same implementation reads generation.getRunPodOperations() and surfaces concrete risk details (warning message, credits threshold, cost pressure). |
Pass |
| Submit is gated until explicit acknowledgment | Same implementation requires checking I understand the potential RunPod cost impact and want to continue. before enabling submit for risky expensive runs. |
Pass |
| User journey is test-covered end-to-end | apps/isis/web/src/pages/JobSubmissionStudio.spec.tsx test shows runpod quota/cost warning and requires acknowledgement before expensive runs verifies warning rendering, disabled submit state, acknowledgment toggle, and successful submission after acknowledgement. |
Pass |
| Existing app interactions remain green | apps/isis/web/src/App.e2e.spec.tsx passes after integration changes, confirming no regressions to major route-level interactions while cost warning support is active. |
Pass |
Reproduction Commands#
bash
pnpm --filter @isis/web exec vitest run src/pages/JobSubmissionStudio.spec.tsx
pnpm --filter @isis/web exec vitest run src/App.e2e.spec.tsx