## v190.10 Active Run timeline hotfix checks

- Active Run timeline remains horizontal and pulsing while live convergence is validated.
- Active Run polling, Runs Explorer cards, Run Stats, and Eval Archive converge without a page refresh.

## v190.10 live convergence validation

- Active Run polling, Runs Explorer cards, Run Stats, and Eval Archive must converge to the same terminal snapshot without a browser refresh.
- Intermediate fallback/live wait failures are diagnostics only; they must not mark the run failed unless the canonical timeline is terminal.

## v190.9 Active Run timeline hotfix checks

- Active Run timeline remains horizontal and pulsing while Space Test canonical persistence is validated.

## v190.9 Space Test canonical persistence checks

- Confirm a failed Space Test remains Failed after page reload.
- Confirm the delete validation modal shows Status: Failed and does not warn that the run still looks active.
- Confirm stale HF Job/running summary data cannot restart polling or relaunch a terminal validation.
- Confirm only an explicit Run validation again action can launch a new validation.

## v190.6 Space Test terminal-state lock checks

- Confirm a failed Space Test stays Failed in the panel and Runs Explorer during slow refreshes.
- Confirm stale running poll responses are ignored after a terminal validation state.
- Confirm prefill/new validation clears terminal lock only by switching to a new validation id.

## v190.5 Active Run timeline hotfix checks

- Verify Active Run canonical timeline renders horizontally on desktop/tablet center columns.
- Verify the current running phase pulses again.
- Verify `pi_run` started/running displays Agent as In progress, not Complete.

## v190.1 Space Test validation UI checks

- Verify Space Test validation timeline uses Start / Runtime / API / Endpoint / Payload / Smoke test / Result / Report.
- Verify validation runs that pass are shown as Success in Runs Explorer.
- Verify Gradio endpoint schemas do not render `[object Object]`.

# Release Candidate Validation — v190.0

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.

## Validation date

2026-06-06

## Automated checks

- Pytest suite: expected full pass from the archive root.
- JavaScript syntax:
  - `web/static/app.js`
  - `web/static/runs.js`
  - `web/static/progress.js`
  - `web/static/api.js`
  - `web/static/components.js`
- Python compile check:
  - `app.py`
  - `src/*.py`

## Critical v188 regression checks

- `full_inference_candidate_health_passed` and `health_only` are partial validation states, not green full-success states.
- `/health` validation from `gradio_client` maps to `health_passed=true` in the inference gate and eval record.
- Generation smoke tests prefer `INFERENCE_CONTRACT.json` payloads, then Gradio schema introspection, then generic fallbacks.
- Smoke test payloads include required text/image arguments such as `negative_prompt` when discovered in the schema.
- Smoke failures classify validator request errors separately from generated-app runtime errors.
- 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 `v190.0`.
- 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.
- Space log diagnostics only extract `first_error` from real available runtime/build logs, never from `[ASF_LOG_UNAVAILABLE]` placeholders.

## Live-run scenario covered

The v188 sequence was driven by the live run:

```text
universal-20260606-181620-5f6004b8
```

Expected honest verdict for that class of run:

```text
Completed with partial validation.
Space created and repaired.
/health passed.
Generation smoke failed only if the real generation call still fails after schema-aware payload construction.
Eval archive publication must be separately observable.
```

## Manual validation recommendation

After deploying this archive, run the same Z-Image style scenario again and check:

- Active Run top badge says partial only when generation remains unverified.
- 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.9 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.9 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.9 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.9 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.


## v189.9 visual polish validation

- README python_version is quoted and normalized to a safe value.
- torch is added when app.py imports torch.
- failed timeline phases prefer confirmed eval publication and final build blockers.


## v189.9 visual polish validation

- Recovery phase details are compact and point to Agent recovery for detailed diagnosis.
- Run notes replaces duplicated Pi-model-warning banners and does not show opaque +N counters.
- Runtime guardrails from v189.7/v189.8 remain unchanged.


## v190.0 layout consolidation validation

- Confirm the Active Run timeline uses a fit-to-width canonical row on desktop without horizontal scrolling.
- Confirm the redundant terminal Done dot is hidden from the rendered timeline while the verdict chip still communicates the result.
- Confirm Recovery phase details remain compact and Agent recovery carries the detailed diagnosis/patch/revalidation evidence.
- Confirm Run notes use explicit labels and no opaque +N counters.

## v190.0 visual polish validation

- Active Run layout consolidation keeps Run notes explicit and removes opaque counters.

## v190.6 Active Run timeline hotfix checks

- Active Run timeline remains horizontal and pulsing while Space Test terminal locks are validated.