Spaces:
Running on CPU Upgrade
Running on CPU Upgrade
Release Candidate Validation — v133
This archive is based on agentic-space-factory-v132-prescan-output-type-sync and contains no runtime feature changes beyond this validation report.
Validation date
2026-06-05
Automated checks
- Pytest suite:
342 passed, 2 warnings - JavaScript syntax:
web/static/app.jsweb/static/runs.jsweb/static/progress.jsweb/static/api.jsweb/static/components.js
- Python compile check: passed
- HTML parse check: passed
Critical demo-path checks
- Job launch uses bucket-mounted worker file via
WORKER_SCRIPT_PATH, avoiding the previousargument list too longfailure. - Build flow keeps
Qwen/Qwen3-Coder-Nextas the default Pi model. - Pi blockage protocol is present:
INCIDENT_BRIEF.mdPI_DIAGNOSIS_GOAL.mdREPAIR_DECISION.json- allowed actions such as
wait_for_logs,factory_rebuild_same_code,patch_code,declare_technical_blocker
- Unified agent traces are present via
agent_trace.jsonl. - Agent recovery panel is gated and does not show for normal Pi build steps.
- Run delete is gated until the run is finished, cancelled, failed, blocked, stale, or manual-action.
- Space Test prefill is gated until validation results exist.
- Run trace buttons stay disabled until bucket files exist.
- Overall progress timeline uses product-facing labels while preserving internal step mapping.
- Space Test endpoint UI no longer shows the confusing
Set API namebanner. - Model pre-scan can infer and sync
Expected output typewhen clear.
Manual demo recommendation
For the safest live demo, use:
- Model:
Tongyi-MAI/Z-Image-Turbo - Expected output: should auto-sync to
Imageafter pre-scan - Implementation mode:
Strict inference - Hardware: ZeroGPU first, fixed fallback allowed
- Confirm Billing dashboard before launch
Known non-blocking warnings
The local test environment emits Hugging Face OAuth experimental/local warnings. These are expected outside a Space environment and do not indicate a failing app test.