grok-build-supervisor

# Grok Build Supervisor Use the `grok-build-supervisor` MCP tools as a guarded transport. A user-level daemon owns the shared Leader, ACP connection, visible TUI records, and event journal independently of any one host task. Each task gets a thin authenticated MCP client. Keep transport diagnostics internal during normal work and report only ready, working, needs permission, needs input, completed, or failed. ## User-facing messages - Render user-facing explanations in this order: an explicit language request, otherwise the language of the user's latest substantive message/current task, otherwise a genuinely known host or OS locale, otherwise English. Never persist an inferred language. Keep JSON keys, states, enum values, tool names, permission/form option values, paths, commands, hashes, task/session/agent IDs, and error/status codes verbatim. - Keep preflight silent. Tool availability, tool counts or names, Supervisor reachability, ACP/Leader state, the working directory, and presentation details are internal unless they block the request or the user explicitly asks for diagnostics. - Do not ask the user to create, open, show, resume, or select a TUI as a separate step. `/grok_execute on` owns workspace selection and session setup. If startup takes long enough to merit an update, give only a short localized statement that Grok is connecting. - For `/grok_execute on`, return one concise standalone result after the visible TUI is ready: executor mode is on, the terminal i...