fix: stabilize Codex usage monitoring for v1.1.2

[jelicanin]

Changes

Using a limits key and a usage dial together could start duplicate Codex processes, while broken pipes or malformed responses could prevent refresh recovery. Share initialization, retire failed clients, and wait for bounded shutdown even when reset and close overlap.

Daily cards and totals now use the same seven-calendar-day period; incomplete coverage and unknown reset/window data remain explicit. Dial settings show channel-specific connection status and refresh controls, support keyboard navigation and scrolling, and cancel obsolete animation frames and alerts. Invalid global settings preserve the last valid connection configuration.

Split Linux portable checks from macOS/Windows startup checks, update fast-uri to 3.1.8, derive client metadata from the package version, and prepare version 1.1.2.

Validation

• 237 tests, type checking, deterministic builds, startup smoke, and Elgato validation pass on the actual Stream Deck Node 24.13.1 runtime.
• Ten browser cases cover all five inspectors at narrow viewport sizes.
• Real Stream Deck host/account checks cover all actions, refresh, display settings, single-process startup, restart cleanup, and recovery after terminating the plugin-owned Codex child. The owner also reported successful physical-device testing.
• OSV, scoped TypeScript Semgrep, and current-tree/unpushed-range Gitleaks scans found no issues.
• The local 1.1.2 package passes archive inspection: five actions, 37 files, matching validated bundles, and no test/internal artifacts.

CI passed on Windows, macOS, and Linux, plus OSV and Gitleaks, for 9d52a21f73366baa97aba35fd6af77bab278abcb: verified run. Portable tests cover both stdin error callbacks and error events on every platform; the additional real-descriptor closure test is POSIX-only.

Marketplace submission and publication are separate from this change.