Faster Onboarding, Cross-Project Safety

Improved

• Reworked roadmap step in onboarding — Each generated section (Vision, Phases, Architecture, Design System) lands directly in your project's knowledge base as soon as it's written, so you can flip between sections with Next and Back without waiting on a save. The per-section Approve button is gone — you read through the four sections at your own pace and click a single Continue at the end. Asking Trinity to rewrite a section through "Discuss Roadmap" updates the page in your knowledge base immediately, so the new version appears the moment it's ready instead of after a round-trip through your onboarding state.
• Onboarding finishes the moment you confirm — The final Confirm step now drops you onto the planning dashboard right away instead of holding you on a 10–30 second "Saving…" spinner. Because roadmap pages were already saved as each section generated, there's no large save left when you confirm.
• Dashboard shows your project list faster on cold load — When several panels on the dashboard ask for the same project list at once, Trinity now collapses them into a single fetch. The first paint after launching the app or switching scopes is noticeably snappier.
• Dashboard flips to Executing automatically when PRD generation finishes — The dashboard would sometimes stay stuck on the planning view after a PRD finished generating until you manually refreshed or switched projects. It now updates the moment the PRD save completes.
• App recovers cleanly from dev-mode server hiccups — In development, a brief auth fetch hiccup right at app startup could render the login screen even though you were still signed in. The first auth check now retries through transient failures.

Fixed

• Stories from one project could appear in another after a PRD save — In some cases a Confirm save on one project would silently re-parent a different project's PRD (and every story, phase, epic, tag, and chapter under it) onto the project you were working on. A "todo list" project could end up showing 26 stories that originally belonged to a crypto trading project, with no obvious way to tell which side was the original. The underlying ID collision is fixed; new PRDs use globally-unique IDs and the contamination path is closed. If you ran into this on an earlier 0.2.x build, contact support — we can help you sort out which stories belong to which project.