fix(setup): complete Windows first-run setup

[badcuban]

Fresh Windows installs left users without setup guidance, required app restarts to find installed tools, and offered no GitHub sign-in. The clone picker omitted organization repositories. Testing found intermittent Windows cache writes and conversations reordered by clock corrections.

• Add Git and optional GitHub onboarding, native Codex and Claude installs without Node/npm, Windows PATH refresh, and persistent installation progress.
• Queue Git/GitHub installs; provide GitHub browser sign-in, cancellation, credential verification, and Git credential setup in either installation order.
• Include organization and collaborator repositories. Check Claude sign-in separately from its SDK model catalog, and explain installer cancellation/timeouts.
• Retry briefly when Windows locks an atomic cache replacement; permanent errors still propagate.
• Keep messages, plans, tools, and subagent results in durable event order. Backfill existing history and use that order for pending requests and native checkpoint rewind.

The clean Windows 11 VM walkthrough passed native tool installs without Node/npm, detection without restarting, queue navigation, all three sign-ins, organization listing and cloning, and real Codex/Claude Git commands. Upgrading to 0.3.8-test.221.2 repaired both existing clock-affected conversations while preserving timestamps. Both providers completed another follow-up. Saved order, replies, credentials, and a clean repository survived subsequent VM reset recovery; provider caches were freshly written to disk.

Validation: formatting, lint, full typecheck, full unit suite in CI, all 542 browser tests on Windows and CI, desktop build, package dry-run, release smoke, and security checks pass. The Windows cache reproduction failed 5/20 before the fix and passed 20/20 afterward; 111 affected cache/setup server checks pass. Transcript migration, restart, capped-history, optimistic acknowledgement, and native rewind regressions pass. Final CI: https://github.com/Threadlines/threadlines/actions/runs/33953916623.

Windows-specific limits: the earlier broad server run had baseline failures in path handling, symlink permissions, skill discovery, Claude quoting, and a worker memory failure. No expectation was weakened. VirtualBox stalled during a turn and during the final Windows restart; the latter required a VM reset after Guest Additions shut down. The freeze cause remains unconfirmed, so this is functional validation, not a claim of VM stability or physical Ryzen/GPU coverage.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
threadlines	Skipped		Sep 5, 2026 8:33am UTC