Daemon reports fully booted after SIP bind failure

[ryanmurf]

Problem\n\nWhen SipStack::new cannot bind a configured transport, startup logs a warning and continues. The daemon then emits FullyBooted, serves core waitfullybooted, and can appear healthy even though it has no usable SIP listener.\n\nRFC 3261 section 18 makes the transport listener the entry point for SIP messages. A PBX configured with a SIP transport cannot be ready when that transport failed to initialize.\n\n## Expected\n\nPropagate any configured SIP stack startup failure out of the startup sequence, exit non-zero, and never set the fully-booted state.\n\n## Regression test\n\nRun the real CLI against a pjsip.conf whose exact UDP port is occupied. Assert it exits promptly and non-zero, identifies the SIP startup failure, and never logs the fully-booted state.

[github-actions]

🤖 Auto-triage: Automated evaluation failed. A human should review this issue.

Error

GitHub Models API returned 401: {"error":{"code":"unauthorized","message":"Bad credentials","details":"Bad credentials"}}

[ryanmurf]

Fixed by #65 (merged).