Summary
All checks in this review passed, yet the reproduced issues above are outside their assertions. Frontend tests focus on stores/helpers rather than complete rendered workflows. The release-verification report marks R01-R18 verified using a mix of mocks, storage-unit tests, source inspection, and build success; that does not establish complete current-head acceptance. CI does not establish a packaged clean-machine desktop user journey.
Environment and evidence
- Review finding: F43 (2026-10-05 product/technical review).
- Baseline: Windows,
dev at c1c5dbe. The remote dev matched this commit when filing.
- Evidence: Code + Validation.
- Priority recommendation: P2 - material improvement or integration validation. This is review triage, not a production-incident severity declaration.
- No real credentials, paid inference, engine installation, or unrelated process termination were used for review probes. Mocked observations establish the stated code behavior, not live-provider/GPU acceptance.
Reproduction or validation
The review baseline passed 157 backend tests, 41 frontend tests, 3 launcher tests, frontend build/lint, and Tauri cargo check. Nevertheless the current probes reproduce missing project durability, invalid cache reuse, false install completion, and model/provider mismatches. RELEASE_VERIFICATION_REPORT marks R01-R18 verified using mixed mocks, primitive tests, source inspection, and builds; that is not full user acceptance.
User impact
Regression gates can remain green while a release-critical workflow is broken.
Proposed approach
Map every requirement to an end-to-end assertion and evidence level; record the tested commit, environment, provider/engine versions, and output artifacts. Gate release on persistence, first image, masked edit, upscale/export, external ownership, interrupted install/update, and safe exit.
Acceptance criteria
Additional source references
Verification scope
Real GPU inference, paid-provider compatibility, and a clean-machine packaged desktop journey remain unverified. Any follow-up implementation should target dev under the repository's contribution/branching rules.
Summary
All checks in this review passed, yet the reproduced issues above are outside their assertions. Frontend tests focus on stores/helpers rather than complete rendered workflows. The release-verification report marks R01-R18 verified using a mix of mocks, storage-unit tests, source inspection, and build success; that does not establish complete current-head acceptance. CI does not establish a packaged clean-machine desktop user journey.
Environment and evidence
devat c1c5dbe. The remotedevmatched this commit when filing.Reproduction or validation
The review baseline passed 157 backend tests, 41 frontend tests, 3 launcher tests, frontend build/lint, and Tauri cargo check. Nevertheless the current probes reproduce missing project durability, invalid cache reuse, false install completion, and model/provider mismatches. RELEASE_VERIFICATION_REPORT marks R01-R18 verified using mixed mocks, primitive tests, source inspection, and builds; that is not full user acceptance.
User impact
Regression gates can remain green while a release-critical workflow is broken.
Proposed approach
Map every requirement to an end-to-end assertion and evidence level; record the tested commit, environment, provider/engine versions, and output artifacts. Gate release on persistence, first image, masked edit, upscale/export, external ownership, interrupted install/update, and safe exit.
Acceptance criteria
Additional source references
Verification scope
Real GPU inference, paid-provider compatibility, and a clean-machine packaged desktop journey remain unverified. Any follow-up implementation should target
devunder the repository's contribution/branching rules.