Files
3590cd1bcf control: say why the control server is not serving (#3436) (#3535)
* control: say why the control server is not serving (#3436)

With --control but a missing or malformed FILMCRAFT_CONTROL_TOKEN the
server declined to start and said so only on stderr, which a desktop
launch has no reader for: the window opened, nothing listened, and the
bridge blamed the launch command.

- control server: log the disable reason and the listening state through
  log::warn!/log::info! so they land in filmcraft.log; start returns a
  typed Option<DisabledWhy> instead of hiding the reason
- desktop app: show the token reason in the status bar whenever it is
  idle (persistent but replaceable by any real status)
- --control-input-only: exit with an error when the server cannot start
  instead of parking a window that ignores all native input
- bridge: the connection-refused error names the token requirement
- i18n: status-bar string translated in the 8 active locales

Co-Authored-By: Claude <noreply@anthropic.com>

* control: drop the unused ControlNotice::Bind and its catalog rows

A bind failure is only logged until #3318; nothing constructed the variant.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Brandon Thomas <echelon@gmail.com>
2026-10-30 01:46:18 -04:00
..