[voidsteed]

Why

Copilot Bridge lets users manage a GitHub Copilot gateway from a desktop window and copy setup commands for coding agents. This PR builds on #8.

What changed

• Add the Electron and React app at version 0.0.1, with account, model, usage, agent setup, activity, and settings views.
• Own one Node gateway process and keep credentials behind the native boundary. Use OS encryption when available and session storage otherwise.
• Add native and packaged smoke tests, a live Copilot check, and macOS, Windows, and Linux CI with downloadable unsigned app archives.

Scope

The app manages one Copilot account. Agent setup copies terminal commands. It does not edit existing agent files. Installer signing and distribution are separate release steps.

Blast Radius

The desktop package has its own dependencies and version. CLI behavior is covered by the foundation suite in #8. Tests run separately to isolate global fixtures.

Verification

• Clean checkout: 242 proxy tests and 60 desktop tests pass, with one local PowerShell skip. Both type checks, lint, and both builds pass.
• The macOS development and packaged apps pass 13 native workflows, including login cancellation, streaming, PDF input, clipboard setup, settings, fixture profile isolation, and shutdown.
• A live gpt-4.1 request through the controller and local gateway returns Copilot Bridge is connected. using an existing CLI sign-in in memory. New device consent requires a user.

Native CI passes on macOS, Windows, and Linux, including 13 native and 13 packaged workflows on each OS. The run has unsigned app downloads and evidence.