Crier 0.4.0

Crier 0.4.0 adds multiple independent Alpaca Host/Receive connections inside one app. Each route retains its own credentials, pairing, execution journal and controls. Changing the selected connection leaves other connected routes running; Quit/update drains every route. Up to 16 retained connections are supported. Restart remains disconnected with new entries paused.

Supported update source: 0.3.1. Profile and wire-protocol generation remain 1. The original profile stays in place and new route metadata/journals are additive; no legacy execution journal is copied or deleted. Account/environment ownership persists across disconnect and restart. A destination account/environment cannot belong to two routes; shared-account reservations remain unfinished. A rejected account change cannot reserve another account.

Preserve the entire root profile, including connections.sqlite3 and nested connections directories. Updates create a verified private root-profile recovery snapshot after all route workers drain. Existing broker orders remain active. Start Crier manually afterward, inspect each account and unresolved orders, then deliberately reconnect and enable entries. Do not downgrade or delete a journal/registry to bypass an ownership check.

Only the existing Alpaca executor is activated. Webull resource execution/Connect activation, Tradier execution, shared-account coordination, physical device acceptance, Apple signing and optional Windows publisher signing remain separate work. Mobile additional routes have explicitly scoped capability limits described in docs/multiple-connections.md.