Spawn-Flow: confirmRestarts flag and replace-in-place rows for running targets
Sync the wiki with the post-release fix pass: one resolution predicate, persistent pending rows, orphan-only reaping, mid-start suppression as fetch rule 4; record the deliberately deferred gaps
Record why the multi-start confirm is now the root-search path's alone
Finder selection reaches the dashboard: rewrite the Start entry section, mark the roadmap item shipped
Sync docs with the pending-start-rows branch: failure table on rows, third suppression rule, reap call sites, preference-scope rule, removeRecent reintroduction
docs: link the auto-open investigation from Spawn Flow and Menu Bar
docs: one source of truth for auto-open
docs: pending rows belong to their project's section
docs: keep the pending-row summary current with restarts
docs: restarts get rows, and how resolution generalised
docs: attempt-scoped logs, and exactly how long a failed row lives
docs: spinner step size vs frame rate, and the leaner log view
docs: spinner at 20fps, and why that is affordable
docs: grey arc spinner, and why selection crosses in render
docs: spinner, background auto-open, and why the ring went
docs: pending start rows, and where each failure now reports
Toast copy budget: cause in the title, fix as an action Records why the failure toast puts the cause in the title and the fix on a button: the message is dimmed onto the title line and elides to a word or two, so prose there is unreadable.
Spawn Flow + Portless: restart shares the failure naming; match portless's full sentence - Restart now takes the same logStart baseline and runs the same diagnoseSpawnFailure, so both entry points name the same causes. - Document why the match is on the full no-TTY sentence: portless prints the 'Proxy is not running' prefix from proxy stop and doctor too, neither of which means a failed start. - Note that the log scan seeks to the offset rather than reading the whole append-only log.
Portless proxy requirement, named spawn failures, Phase 1 checked off - Portless: new section on why a `portless run` dev script needs the proxy already up, and why NOPASSWD sudoers does not help. - Spawn Flow: the 15s failure toast now names two causes, not just port conflicts; document diagnoseSpawnFailure and its scoped log scan. - Roadmap: Phase 1 (menu bar) shipped 2026-07-02 and was polished in the 2026-07-09 release; current phase moves to 2. Noted that F3 still awaits Phase 5 to reach the Start picker. - Home: Shopify start support has shipped, so drop "planned".
docs: sync pages with the June 10 and port-fallback releases
docs: correct dedupe guidance, document fast-poll loop and forcePicker - Raycast Quirks: sameServers compares pid+port only; do not include volatile portless-derived fields. Add an entry on fast-polling while a modal is open being a render-loop source on its own. - Spawn Flow: document the Start command entry points and the forcePicker rule, and that fast-poll is scoped to the spawning phase only.
docs: normalize dash formatting across wiki pages Apply the project's dash-formatting convention to all pages. Punctuation only; no content change.
docs: add Favicons + Framework Detection pages; fill gaps - New Favicons page: detection order, CORS/data-URI inlining rationale, the two-tier (port on dashboard / cwd in recents) cache, the 24 KB persistence cap. - New Framework Detection page: the two detection paths (detectTool from the live process vs guessFramework from package.json) and why they're separate, plus the tool-display label/color styling and theme-adaptive hex overrides. - Spawn Flow: Start-vs-Restart detection strategies (appears-by-cwd vs rises-above-baseline). - Recents: defer the favicon detail to the new Favicons page. - Home: link the two new pages.
Restructure: split design doc into focused single-topic pages Home.md is now an index. Each page covers one concern (Spawn Flow, Paths, Process Detection, Spawn Primitives, Script Picker, Recents, Raycast Quirks, Portless, UI Conventions) so an AI or contributor can load only the page they need.