User directive from Telegram: do not ask Elmar to approve MC restarts or similar operational restarts. The controller owns MC and should decide whether a restart is safe; if the...
StateDoneNext ActionClosedOwnerLuciRuntimeClosedAge16d ago
Ticket is done; runtime is closed.·profile codex · cwd /home/lucienne/workspace/mission-control · uptime 15d 22h · last activity 15d 20h ago
Description
MC-4377
User directive from Telegram: do not ask Elmar to approve MC restarts or similar operational restarts. The controller owns MC and should decide whether a restart is safe; if the controller is satisfied it is safe, approve/execute it, otherwise wait until it is safe.
Scope:
- Audit Mission Control / Luci controller restart/deploy approval prompts and workflows that currently escalate MC restarts or similar technical service restarts to Elmar.
- Update controller policy/prompting and/or MC gate logic so technical restart decisions are controller-owned, not human-owned, when safety can be determined by the controller.
- Keep genuine non-coding/product/spend/credential blockers escalated; this directive only covers MC restart / deploy-like operational safety decisions.
- Add tests/docs/runbook notes as needed.
Acceptance criteria:
- No normal MC restart/service reload approval asks are sent to Elmar when the controller can determine safety.
- Controller either proceeds with a safe restart or waits/parks until safe with ticket evidence.
- Any remaining human escalation path is limited to non-coding/product/spend/credential blockers.
- Changes are committed, pushed, and verified through the standard dev-loop.
Expected check-in: 2026-05-28T12:40+02:00
Activity
done
INTERACTIVE
Luci is working...
Details —
Done
· High
· Luci
▼
SState
Done
Closed
PPeople
TTiming / Details▼
telegram (human)
Mission Control
16d ago
16d ago
Advanced / Operator evidence
RRouting owner
ROperator console
Ticket is done; runtime is closed.terminal_state_reapprofile codex · cwd /home/lucienne/workspace/mission-control · uptime 15d 22h · last activity 15d 20h agoMC is visibility-only. Hermes Luci launches and gates work outside MC, then mirrors evidence/status here.Raw console: luci · codex/openai/gpt-5.5
WWorkflow
Start Dev Review + QA ▾
Select phases to include:
Agents
Review Gates
Decision
WAT routing: choose an agent, review gate, or decision. Buttons use the live runtime when one is attached.
REVIEW: MC-4377 — Approve-with-fixes. Shipping code (not the stale pasted
… +6 lines (ctrl + t to view transcript)
lists `deploy|promote|rollout` that the shipping ACTION regex no longer
contains.kiinWng9Wogor•rkkiinngg◦20•WWoorrkkiin◦Wng1Wogorrkkiinngg•2◦WWoorrk•kiinWng3Wogorrkkiin◦ngg•4W◦WoorrkkiinWng5Wogor•rkkiinngg◦6•WWoorrkkiin◦Wng7Wogorrkkiinngg•8◦WWoorrk•kiinWng9Wogorrkkiin◦ngg•30W◦WoorrkkiinWng1Wogor•rkkiinngg◦2•WWoorrkkiinWng◦3Wogorrkkiinngg
api16d ago
Triage: genuinely INCOMPLETE (no MC-4377 commit in any repo — shadow-review correct here; the worker analysed + found the regex gap but did not commit an implementation). The corrupted/spinner text in the review is MC-4357 harvest noise. Flipping to todo for real implementation.
DIRECTIVE ADOPTED NOW (Elmar, via this ticket): the controller owns MC restarts — do NOT ask Elmar to approve operational restarts; if the controller judges a restart safe, execute it; if not, wait. This SUPERSEDES the old "restart needs Elmar OK" pattern (MC-4342 / worktree-rule wording).
Implementation scope:
1. Codify controller-owned restart: remove the ask-Elmar-to-approve-restart path; controller decides on safety.
2. Fix the shipping ACTION regex to include deploy|promote|rollout (worker found it no longer matches these).
3. Reconcile the wording in CLAUDE.md rule 10 + any restart-approval prompts so they reflect controller ownership (restart in a safe/quiet window by controller judgement, not by Elmar gate).
Note for the pending slot2 deploy: the RESTART is now my call on safety — but the big bundle's safety still warrants careful judgement (don't rush), so 'wait for a clean controlled merge' stands on safety grounds, not on Elmar-approval grounds.
Luci16d ago
MC-4377 shipped: controller-owned MC restart/reload/deploy-like safety routing, prompts/docs updated, regression tests added, commits 2fca3c9 and eb4de42 pushed.
luci16d ago
Workflow action `review_ready` applied. Work ready for review.
api16d ago
Verified SOUND — 14/14 tests pass (tests/test_mc4377_controller_restart_approvals.py). Coherent impl on slot2 (2fca3c9): semantic_router.py controller-owned restart/deploy-like safety routing (+81), mc_interactive/orchestrator_triage/luci_operator/ticket_runtime wiring, docs+wiki updated. eb4de42 = test stub completion. Shadow-review fail (0.95) is STALE (reviewed the old MC-4375 doc, not these commits — slot-branch/timing blindness, MC-4371).
The directive itself is ALREADY ADOPTED in my behavior (controller owns restarts, don't ask Elmar). The CODE is slot2-bound → lands with the holistic merge. Added to MC-4357 batch; in_review until merge.
Separate finding (not blocking MC-4377): full-suite pytest collection is broken by tests/test_console_panel.py -> ModuleNotFoundError 'shared_console.blueprint' (not a package). A slot2 commit likely added a shared_console reference without packaging it. Flag for the merge/QA pass.
Luci16d ago
Controller gate: verified MC-4377 as complete. Evidence: `python -m pytest tests/test_mc4377_controller_restart_approvals.py -q` => 14 passed; commits 2fca3c9 and eb4de42 are on origin/slot2/mc-MC-4327. Closed as done. Note: existing untracked tests/test_mc4317_review_gate_edges.py is unrelated to this ticket and not part of the MC-4377 diff.