test: prove clean-machine onboarding and stable-staging isolation

Summary

Run final acceptance from clean supported macOS and Windows environments and prove the complete install, onboarding, integration, recall, desktop, and isolation experience.

Why This Matters

Unit and component tests cannot prove that a non-technical user can go from a pasted prompt to durable cross-chat memory without risking their stable data.

Proposed Approach

• Use clean Apple Silicon 16 GB and Windows 11/WSL2 8 GB+ GPU environments.
• Execute the canonical prompt without repository-local assumptions.
• Verify preflight, installation, desktop launch, first import, folder preview, organization proposal, client wiring, and cross-chat recall.
• Run a destructive staging test fixture and prove stable database/archive hashes and service state do not change.
• Exercise upgrade, repair, rollback, uninstall/reinstall, cancellation, and failure recovery.
• Capture desktop and 375px visual evidence and verify package checksums.

Acceptance Criteria

• Both supported platform baselines complete zero-to-first-memory onboarding.
• Every selected supported client passes a real MCP or CLI recall check.
• Stable state remains unchanged throughout staging development and mutation tests.
• No login or manual Answer Engine API-key creation is required for the local UI.
• Background services recover after reboot and Electron remains only the control plane.
• All child acceptance criteria, learning files, merged PRs, and issue checklists are complete.
• pnpm verify and final installer/package verification pass from clean checkouts.
• No paid enterprise code is present in OSS and no npm package was published.

Out of Scope

• Adding features discovered during acceptance; file linked regression issues instead.
• Weakening checks to accommodate platform failures.

Related

• Parent epic: #40
• Depends on: #41, #42, #43, #44, #45, #46, #47, #48, #68, #71, #74, #76, #77, #78, #79, #86, #88, #89, #80, #81, #82, #83
• Keep Graphify excluded.
• Do not publish npm.

Start with the canonical prompt and the clean Apple Silicon macOS and Windows 11/WSL2 environments described in the issue. Run the onboarding, recall, isolation, upgrade, recovery, and package checks, including pnpm verify, from clean checkouts. Done means all listed acceptance criteria and child checklists pass, with stable state unchanged and the required visual and checksum evidence captured.