Upload 6 files

CHANGELOG.md

@@ -1,29 +1,29 @@
 
-## v190.31 — Validation hotfix + terminal UI convergence
+## v190.32 — Validation hotfix + terminal UI convergence
 
 - Added the missing `write_live_status()` helper to the linked validation worker so validation Jobs no longer crash after Gradio API discovery.
 - Hardened Active Run terminal rendering so a terminal partial/success/error snapshot cannot be overwritten by stale `running` summary fields during live polling.
 - Improved canonical timeline phase selection so terminal partial runs focus the Live test/attention phase instead of falling back to Start.
 
-# v190.31 — Validation engine startup hardening
+# v190.32 — Validation engine startup hardening
 
 - Writes validation_engine.json and validation_preflight.json before fragile Gradio discovery/payload work.
 - Guarantees validation_failure_diagnosis.json when linked validation stops before payload resolution.
 - Fixes replay payload_source provenance to parent_automatic_smoke when backend replay source is present.
 - Writes terminal summary.json for linked validation success/failure, avoiding stale running summaries.
 
-## v190.31 Eval archive run-scoped reset and layout stability
+## v190.32 Eval archive run-scoped reset and layout stability
 
-- v190.31 makes the Active Run eval archive card strictly run-scoped: launching, deleting, or switching Build Runs clears stale eval archive state before the selected run snapshot arrives.
+- v190.32 makes the Active Run eval archive card strictly run-scoped: launching, deleting, or switching Build Runs clears stale eval archive state before the selected run snapshot arrives.
 - The eval archive key/value layout now uses a stable single-column grid with safe wrapping so long bucket names and record paths never collapse into letter-by-letter columns.
 
-## v190.31 — Runs Explorer linked validation parent metadata
+## v190.32 — Runs Explorer linked validation parent metadata
 
 - Build Run cards now show linked/manual validation strips from parent metadata (`manual_validation_status` and `linked_validations`) even when the child Validation Run is not present in the Runs Explorer cache.
 - Runs Explorer remains build-first: linked validations stay summarized on their parent Build Run, while automatic Build Run smoke results remain separate from manual linked validation state.
 
 
-## v190.31 — Space Test payload provenance and prefill correctness
+## v190.32 — Space Test payload provenance and prefill correctness
 
 - Uses automatic smoke artefacts as the visible Space Test prefill source when available.
 - Clears stale dirty validation args when a Build Run is selected from Runs Explorer.
@@ -31,26 +31,26 @@
 - Writes validation_launch_payload.json in validation runs before the worker resolves/predicts.
 - Surfaces payload source provenance across UI, backend launch metadata, and worker artefacts.
 
-# v190.31 — Replay uses parent smoke artefact as source of truth
+# v190.32 — Replay uses parent smoke artefact as source of truth
 
-## v190.31 — Linked validation replay hardening
+## v190.32 — Linked validation replay hardening
 
 - In Space Test replay mode, the validation worker now loads the parent Build Run's successful automatic smoke artefacts (`generation_smoke.json`, `generation_smoke_payload*.json`) as the canonical request before schema reconstruction.
 - Added `replay_source.json` and richer `resolved_validation_request.json` / failure diagnosis fields so replay failures can be compared against the parent smoke request.
 - The Payload stage now records `Payload replayed from parent automatic smoke` instead of remaining pending when replay data exists.
 
-# v190.31 — Linked validation worker schema coercion and replay fix
+# v190.32 — Linked validation worker schema coercion and replay fix
 
-## v190.31 — Validation worker reliability
+## v190.32 — Validation worker reliability
 
 - Normalizes linked validation replay payloads against the current Gradio endpoint schema before calling predict().
 - Preserves typed Gradio choices and converts dropdown/radio numeric-looking args such as 1024 to schema strings such as "1024" when required.
 - Writes validation_preflight.json, resolved_validation_request.json, schema_coercion.json, and validation_failure_diagnosis.json for every linked validation run.
 - Keeps Space Test copy linked-only while explaining that the separate validation run remains attached to the selected Build Run.
 
-# v190.31 — UI/CSS convergence and Space Test validation polish
+# v190.32 — UI/CSS convergence and Space Test validation polish
 
-## v190.31 — Space Test validation reliability
+## v190.32 — Space Test validation reliability
 
 - Treats Space Test Validation as a first-class linked validation workflow.
 - Adds a single resolved launch payload contract so replay/complete/recover/discovery-first modes only launch when coherent.

README.md

@@ -13,23 +13,28 @@ hf_oauth_scopes:
   - read-billing
 ---
 
-## v190.31 Eval archive run-scoped reset and layout stability
+## v190.32 Robust linked validation schema parsing
 
-- v190.31 makes the Active Run eval archive card strictly run-scoped: launching, deleting, or switching Build Runs clears stale eval archive state before the selected run snapshot arrives.
+- v190.32 hardens linked Space Test payload resolution when Gradio endpoint schemas contain heterogeneous parameter lists such as bare strings mixed with dict objects. The validation worker now normalizes schema parameters before reading metadata, preventing payload-resolution crashes like `'str' object has no attribute 'get'`.
+- Replay mode now fails fast with a clear launch error if a successful parent automatic-smoke payload cannot be resolved, instead of silently downgrading to endpoint-discovery-first while still presenting itself as replay.
+
+## v190.32 Eval archive run-scoped reset and layout stability
+
+- v190.32 makes the Active Run eval archive card strictly run-scoped: launching, deleting, or switching Build Runs clears stale eval archive state before the selected run snapshot arrives.
 - The eval archive key/value layout now uses a stable single-column grid with safe wrapping so long bucket names and record paths never collapse into letter-by-letter columns.
 
 
-## v190.31 Runs Explorer linked validation parent metadata
+## v190.32 Runs Explorer linked validation parent metadata
 
-- v190.31 makes Build Run cards display manual linked validation state directly from parent metadata (`manual_validation_status.json` / `linked_validations.json`), so the summary is visible even when linked Validation Runs are not listed as standalone rows. Automatic smoke status remains separate from manual linked validation status.
+- v190.32 makes Build Run cards display manual linked validation state directly from parent metadata (`manual_validation_status.json` / `linked_validations.json`), so the summary is visible even when linked Validation Runs are not listed as standalone rows. Automatic smoke status remains separate from manual linked validation status.
 
-## v190.31 Replay uses parent smoke artefact as source of truth
+## v190.32 Replay uses parent smoke artefact as source of truth
 
-- v190.31 makes linked Space Test replay mode load the parent Build Run's successful automatic smoke artefacts before attempting any schema reconstruction. The validation worker writes `replay_source.json`, `resolved_validation_request.json`, and diagnostics so a replay cannot fail opaquely at the Payload stage.
+- v190.32 makes linked Space Test replay mode load the parent Build Run's successful automatic smoke artefacts before attempting any schema reconstruction. The validation worker writes `replay_source.json`, `resolved_validation_request.json`, and diagnostics so a replay cannot fail opaquely at the Payload stage.
 
-## v190.31 Linked validation hardening
+## v190.32 Linked validation hardening
 
-- v190.31 hardens linked Space Test success/failure paths: parent Build Run updates read API/output metadata from the smoke result, failed manual attempts cannot downgrade an already validated parent, and latency/ZeroGPU recommendations expose their linked-test hardware provenance.
+- v190.32 hardens linked Space Test success/failure paths: parent Build Run updates read API/output metadata from the smoke result, failed manual attempts cannot downgrade an already validated parent, and latency/ZeroGPU recommendations expose their linked-test hardware provenance.
 - Runs Explorer and Run Stats now treat automatic and effective statuses explicitly so manually validated partial builds remain discoverable in both Partial and Validated views.
 - Space Test is contextualized from the selected Build Run even before pressing Prefill, while remaining linked-only for launches.
 
@@ -429,19 +434,19 @@ The Active Run progress header now separates pipeline completion from product ve
 
 - v190.9 makes terminal Space Test validation status survive page reloads. Failed, success, partial, and manual validation outcomes override stale `running` launch metadata in the Runs Explorer, delete modal, and progress polling.
 
-## v190.31 Eval archive effective outcomes
+## v190.32 Eval archive effective outcomes
 
 - Eval archive records now distinguish automatic verdicts from effective verdicts after linked Space Test validation.
 - Archived records include anonymized linked-validation, endpoint-discovery and smoke-retry metrics while preserving privacy constraints.
 - Instance owners can flush all archived eval records from the mounted eval bucket without deleting the eval archive configuration.
 
-## v190.31 Linked validation replay reliability
+## v190.32 Linked validation replay reliability
 
 - Linked Space Test validations now normalize replay/complete/recover payloads against the current Gradio schema before predict().
 - Validation runs write explicit preflight, resolved request, schema coercion, and failure diagnosis artifacts for debugging.
 - Replay from a full-inference-success Build Run should reuse the validated endpoint/payload and coerce Gradio dropdown/radio choices as needed.
 
 
-## v190.31 validation hardening
+## v190.32 validation hardening
 
 Linked Space Test validations now write engine/preflight/failure diagnostics before and after Gradio endpoint discovery so payload-resolution failures cannot appear as opaque smoke failures.

app.py

@@ -667,6 +667,8 @@ def register_custom_routes(fastapi_app: FastAPI) -> None:
                     api_name_for_validation = replay_source.get("api_name") or api_name_for_validation
                     test_args = replay_source.get("test_args") if isinstance(replay_source.get("test_args"), list) else test_args
                     test_kwargs = replay_source.get("test_kwargs") if isinstance(replay_source.get("test_kwargs"), dict) else test_kwargs
+                else:
+                    raise ValueError("Replay validation requires a successful parent automatic smoke payload. Select a Build Run with a completed smoke test, or use Complete/Recover validation instead of Replay.")
             if space_test_policy.get("requires_endpoint_discovery") and str(api_name_for_validation or "").strip() in {"", "/generate"} and not replay_source:
                 api_name_for_validation = ""
             # Compatibility anchor: "ui_payload_source": payload.get("payload_source") or ""