[johnmatthewtennant]

Summary

berd-call already has a status sound runtime (Pop every five seconds while the agent works, Purr while it waits), and its session protocol accepts set_conversation_status. But berd-call start never sends it, and nothing outside the call could report status or change the mode. So the Buzz Berd Call plugin plays its own afplay cues, and the menu bar can't toggle them.

With this PR, berd-call plays the cues for any host that reports the agent's status:

• berd-call settings --conversation-status working|waiting reports whether the agent is working. Until something reports it, the call stays silent, so a terminal call whose agent never reports status is unchanged.
• berd-call settings --status-sounds off|working|working-and-waiting and a new Status Sounds submenu in the menu bar change the mode. The mode is saved in the call's settings file and used by later calls (default working, as before).
• status shows statusSounds and conversationStatus. Both survive settings --restart and the Spokesperson switch: the new session is sent the current status as soon as it is ready.
• The saved file only gets a status_sounds key once a mode is chosen, so an older berd-call can still read settings that never set one.

Related issue

Revives the status sounds part of #346 (closed). Unlike #346, berd-call doesn't guess when the agent is working from the transcript. The host reports it.

Testing

Live call from this branch's debug binary, with a temporary settings file:

export BERD_CALL_SETTINGS_FILE=/tmp/status-sounds/settings.json
berd-call start --port 5391 --stream --voice en-US-F --language en-US &
berd-call status --port 5391                                   # statusSounds: working, conversationStatus: null
berd-call settings --port 5391 --status-sounds off             # settings.json now has "status_sounds": "off"
berd-call settings --port 5391 --conversation-status working   # conversationStatus: working
berd-call settings --port 5391 --restart --voice en-US-F --language en-US
berd-call status --port 5391                                   # still off / working after the restart
berd-call settings --port 5391 --status-sounds working         # Pop starts, no playback errors
berd-call settings --port 5391 --conversation-status waiting   # conversationStatus: waiting
berd-call settings --port 5391 --conversation-status idle      # usage error, exit 2
berd-call stop --port 5391

New unit tests cover the menu (checkmark, title, and the request it sends), flag parsing, and the session actor holding the status until one is reported, sending it on later session starts, and saving the mode.

host_session::tests::spokesperson_results_change_and_save_only_its_voice also fails on main (629e0af). This PR doesn't touch it.

[morgmart]

🤖 Automated code review

REQUEST_CHANGES: one blocking state-consistency defect allows an acknowledged status-sound update to be reported as failed while still changing and persisting the preference. All supplied GitHub checks for the exact head SHA completed successfully.

Deterministic publication result: 1 blocking and 0 non-blocking inline finding(s) publishable; 0 duplicate(s) suppressed; 0 blocking screenshot-evidence requirement(s) in this review body.

[morgmart]

🤖 Automated code review

APPROVE: the prior status-sound acknowledgement and persistence defect is fixed at this head, the full changed behavior is covered without a new actionable finding, and all supplied GitHub checks for the exact head SHA completed successfully.

Deterministic publication result: 0 blocking and 0 non-blocking inline finding(s) publishable; 0 duplicate(s) suppressed; 0 blocking screenshot-evidence requirement(s) in this review body.

Pending checks: 1 check(s) are not complete.

This approval reflects the completed code review only; merge readiness remains governed by the repository's required checks.