Louder Bridge v0.3.3

Louder Bridge 0.3.3

This prerelease fixes Hermes setup when a named profile is active.

What changed

• Louder Bridge now asks Hermes which profile is active and installs its plugin
  beside that profile's config file.
• Every command in the setup transaction stays pinned to the same profile,
  even if the active Hermes profile changes before setup finishes.
• Uninstall checks the default profile and every named profile for managed
  copies of the plugin.
• Setup, upgrades, removal, and rollback preserve unrelated Hermes settings
  and refuse to delete a plugin directory Louder Bridge does not own.
• Plugin-list cleanup rereads the current list before each removal instead of
  reusing an old numeric index.

Voice input, Agent Key navigation, send, and lighting behavior are unchanged.

Validation

The setup problem was found while installing Louder Bridge on a second Apple
Silicon Mac. The updated named-profile path passed a real Hermes CLI smoke test
with an isolated profile.

The source passed 385 automated tests, including Node.js 22, 24, and 26. The
GitHub release workflow also built and verified the downloadable ZIP, its
checksum, app signature, contents, and SPDX SBOM.

Install

Download the Apple Silicon ZIP, move Louder Bridge.app to Applications,
and open it once. If macOS blocks it, open System Settings → Privacy &
Security and choose Open Anyway. Approve Input Monitoring and
Accessibility for Louder Bridge. Ghostty may also ask for Automation permission
the first time an Agent Key selects a terminal.

The GitHub build uses an ad-hoc signature, so macOS may ask for permissions
again after an upgrade.

Privacy

Louder Bridge runs locally. It collects no telemetry, audio, transcripts,
prompt content, project names, or session identifiers. Local diagnostics
require a private authentication token.

This remains a prerelease. Ghostty labels its AppleScript API as a preview, and
the device driver uses an independently documented protocol.