Desktop validation records
Current acceptance lists tested versions, platform results and source records. Plan.md maintains unfinished tasks and conditions; V01–V31 retains acceptance criteria. This directory preserves execution records from each phase. Pending items in historical records do not describe current status.
| Record category | Entry point |
|---|---|
| This batch’s three-platform CI and downloadable artifacts | CI jobs, tested commits, package digests and first failures |
| Windows/Linux installation and actual GUI | NSIS/deb/AppImage/FUSE lifecycle, Orca in ten languages |
| System credentials, native interaction and scale | Cross-platform credentials, native/cancellation/incremental tests, queries and resources |
| Native sources and field corrections | Current source index, Qwen/OpenCode, ten M8 sources, MiMo/Zoo/DSH |
| Design review and resources | Initial review, M0/M1 review, static assets |
Record rules: delivery requirements. Template: TEMPLATE.md.
- Mark a check passed only after running it and recording its result. Preserve cwd, command, versions, environment, exit code, counts, first failure, recovery and unexecuted items.
- Report static checks, synthetic data, native sources, simulated browser IPC, native desktop, WSL/containers and CI separately. One result does not verify another category.
- Keep private originals, comparison databases, extraction scripts and logs only in root build/. Anonymize public records and test data; exclude bodies, credentials and private paths.
- Put completed details in dedicated records. Active plans retain stable IDs, current status, remaining conditions and links, without repeating accumulated counts or each run’s history.