Repository navigation
✨ meetings: Quorum v0.2.0 and Discord speech through the TTS service - #18416
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Open PR overlap checkBase branch: Conflicts are checked with every PR merged onto the current tip of
|
|
Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor. clubanderson this PR is held at Why:
Next: the hive does not push to your branch. Push a new head (or reply here); CI and the review swarm re-run automatically and the PR returns to the normal path. hive/awaiting-ci: CI pending — sweep will merge when green. 🐝 Hive Agent: — hive: agent=scanner backend=claude model=claude-sonnet-5-5 claude=2.1.325 Evidence bundle `#18416c0d3764` sha256:fc66cb2e8ac6630cf4952ef74ccd20809c5dccc1fa9dd9dd9b5d6518059ea446 — download from the dashboard or `hivectl review evidence #18416`. |
d32130f
ℹ️ Sentinel notice — informational; author is trusted (owner), merge is not blockedHive flagged this PR (author @clubanderson, head
Hive did not add the |
Mutation testing1 mutant(s) in changed files are not reached by any test (NOT COVERED). A maintainer may apply the
Verdict: |
d32130f to
b600441
Compare
- Dockerfile: pin hivecommons/quorum v0.2.0 (quorum.mjs sha256 9233653115baffcd884c3181a0bf7714145ca858e84abb1d2411a4f255e75e03, verified against the release asset), @snazzah/davey 0.1.12 unchanged (matches quorum's package-lock.json at v0.2.0) - config: meetings.tts_url (HIVE_MEETINGS_TTS_URL) and the write-only meetings.tts_token_file / HIVE_MEETINGS_TTS_TOKEN, keystore-sealed like the transcription token - quorumproc: writes the TTS token to a 0600 file in the private runtime dir and passes QUORUM_TTS_URL, QUORUM_TTS_TOKEN_FILE and QUORUM_TTS_VOICE (the persona's voice) to the child - meeting.join carries voice_id = the persona's voice - Settings, Meetings: write-only TTS token field (API reports only tts_token_set); hint names the in-cluster TTS URL - docs: meetings.md (TTS setup, Discord voice-off gate), env-vars.md, api-reference, openapi; static bundle updated with static-src Part of #18393 Signed-off-by: Andy Anderson <andy@clubanderson.com>
Signed-off-by: Andy Anderson <andy@clubanderson.com>
b600441 to
c0d3764
Compare
Part of #18393 (phase B of #18391). Companion to #18413 (Betty web/voice/deep dive); independent files apart from docs.
What
QUORUM_VERSION=v0.2.0,QUORUM_SHA256=9233653115baffcd884c3181a0bf7714145ca858e84abb1d2411a4f255e75e03(verified: downloaded release asset hashes to this and matchesquorum.mjs.sha256).@snazzah/davey@0.1.12unchanged; quorum'spackage-lock.jsonat v0.2.0 pins 0.1.12.meetings.tts_url/HIVE_MEETINGS_TTS_URL(in-clusterhttp://vexa-tts.meetings.svc.cluster.local:8880) and a write-onlymeetings.tts_token_file/HIVE_MEETINGS_TTS_TOKEN, keystore-sealed exactly like the transcription token (✨ meetings: pass the transcription token to Quorum so Discord meetings transcribe #18359 pattern). The supervisor writes a 0600 file and passesQUORUM_TTS_URL,QUORUM_TTS_TOKEN_FILEandQUORUM_TTS_VOICE(= persona voice) to the child.meeting.joincarriesvoice_id= persona voice.tts_token_set. Docs note the operator copies the token from Secretvexa-ttsin namespacemeetings.voice:falseon Discord; hive's say gate is platform-agnostic and is pinned by a test in ✨ meetings: Betty answers from the web, speaks when asked and digs into hard questions (phase B) #18413.Tests
config (defaults, yaml, env, secret round trip, validation), quorumproc env/token file, wiring (options + unreadable-secret logs), manager join voice_id, JoinArgs JSON, dashboard API (set/clear/never echoed/unwritable) and UI wiring.
🤖 Generated with Claude Code