Upload 6 files

docs/RELEASE_VALIDATION.md

@@ -1,4 +1,4 @@
-# Release Candidate Validation — v188.8
+# Release Candidate Validation — v189.4
 
 This archive is based on `agentic-space-factory-v188-7.zip` and hotfixes partial progress plus Space log diagnostics before deployment for the v188 sequence.
 
@@ -29,7 +29,7 @@ This archive is based on `agentic-space-factory-v188-7.zip` and hotfixes partial
 - Eval records use schema `1.2` and expose `process_completed`, `verdict`, `outcome`, `validation`, `failure_owner`, and `failure_reason`.
 - Backend eval archive publication is observable through `eval_publish_status.json` and is not confused with run-local `eval_record.json` creation.
 - Active Run hides cancel actions for terminal/partial states and renders partial validation, eval publish, report, recovery and hardware fallback consistently.
-- The default ASF app/eval version is centralized in `src/version.py` and defaults to `v188.8`.
+- The default ASF app/eval version is centralized in `src/version.py` and defaults to `v189.4`.
 - Space log collection writes `logs/space_logs_index.json`, `logs/space_runtime_snapshot.json`, and `logs/space_log_diagnostics.json`.
 - Runtime/build logs are marked unavailable with a clear reason when neither SDK nor REST log collection works.
 - Backend progress payloads keep partial terminal states visually partial/warn, not success.
@@ -61,3 +61,29 @@ After deploying this archive, run the same Z-Image style scenario again and chec
 - The smoke payload file includes `negative_prompt`.
 - `health_passed` is true when `/health` passes.
 - The eval archive bucket receives a dated record, or `eval_publish_status.json` explains why it did not.
+
+## v189.4 validation
+
+Validate that `timeline_model` is present on run view payloads and correctly distinguishes full-inference success from partial validation. Eval archive sidebar restoration from v188.9 must remain intact alongside the per-run Eval archive card.
+
+
+## v189.4 semantic progress validation
+
+- Active Run progress uses `timeline_model.progress` when available.
+- The progress bar represents process completion; the badge/result represents the verdict.
+- A 100% partial validation renders as warning/amber, not success/green.
+- Legacy payloads without `timeline_model` continue to render through the previous fallback.
+
+## v189.4 mobile timeline validation
+
+- Active Run renders the canonical `timeline_model` as phase steps plus `timelinePhaseDetails`.
+- Mobile layouts switch the canonical timeline to a vertical single-column list.
+- Phase details expose the active phase summary, details, and “Needs attention” warnings without changing worker/runtime behavior.
+- Legacy timeline fallback remains available when no canonical model is present.
+
+
+## v189.5 timeline state validation
+
+- Terminal full-inference success runs must not leave early phases such as Start in `running` because of historical `started` events.
+- Resolved log collection warnings must not keep Deploy in warning when the final logs index reports full quality.
+- The active phase should focus the most useful terminal proof, especially Live test for full-inference success, while non-blocking warnings remain grouped separately.