Stabilize Windows terminal and pull request sidebar indicators

[badcuban]

Summary

• correlate PowerShell command-completion markers with the command generation that produced them
• keep the terminal-running sidebar indicator from being cleared by a stale queued prompt marker on Windows
• preserve the last-known pull request status during transient source-control provider lookup failures
• clear retained pull request status only after a successful empty lookup, without carrying it across branch changes

Root cause

PowerShell can emit an OSC 633 completion marker before a newly submitted command while the terminal event drain is still processing queued output. The marker was previously applied to whichever command was current when it was drained, so the terminal icon could flash and disappear.

Pull request lookup errors were also collapsed into pr: null, making a transient GitHub/GitLab failure indistinguishable from a successful “no pull request” result and allowing an existing sidebar icon to disappear.

Impact

Windows terminal activity remains visible for the actual command lifetime, and pull request indicators remain stable through temporary provider failures on every platform.

Validation

• vp fmt
• vp lint (passes with existing repository warnings)
• vp run typecheck
• vp run '@threadlines/server#test' GitManager — 64 tests
• vp run '@threadlines/server#test' Manager — 108 tests
• vp run '@threadlines/server#test' VcsStatusBroadcaster — 13 tests

No web browser suite was required because the changes are server-only.

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
threadlines	Skipped		Aug 12, 2026 5:55am