MC-4496

Coder gate for MC-4494: implement the first safe/inert Control Room v2 foundation slice. Objective: Add a canonical 7-role registry and audit comment schema/formatter without changing dispatch, pickup, board, Telegram, runtime launch, or comment behavior. Roles to represent: - controller - planner - designer - coder - reviewer - tester - validator Requirements: - Treat roles as responsibilities/gates, not mandatory separate workers. - Include optional/core metadata: Designer and Tester are optional depending on work class; Controller/Planner/Coder/Reviewer/Validator are core gates for non-trivial implementation. - Include legacy/current capability mappings where appropriate: Larry/CLI/runtime as coder capability, Council/shadow review as reviewer capability, Tessa/browser/vision as designer/tester capability, Atlas/checklist/deterministic verification as validator capability. - Add audit comment formatter/schema with fields: Role, Runtime/capability/profile/model, Scope, Outcome, Evidence, Next step. - Runtime/model picker is advisory only; Controller may choose any suitable capability. - No behavior change in this slice. Likely files to inspect/modify: - /home/lucienne/workspace/mission-control/mc_role_guidance.py - /home/lucienne/workspace/mission-control/models.py - /home/lucienne/workspace/mission-control/tests/ or relevant test files - Consider new /home/lucienne/workspace/mission-control/control_room_roles.py only if cleaner. Verification: - Add/run focused tests proving role registry keys, core/optional metadata, mappings, and audit formatter output. - Run existing narrow workflow/runtime tests that touch role guidance if affected. - Confirm no new runtime_sessions are created by tests/actions for this inert slice. - No service restart required unless tests prove import/runtime issues. Gates: - Coder implements only. - Reviewer must be independent/different model/provider/tool where possible. - Validator confirms tests/evidence before Done. Expected check-in: 2026-05-31 17:40:56 UTC.