MC-4453

auto-triage: assigned to **luci** (confidence 1.00); moved to `todo` for pickup -- skill: `Mission Control internals, code changes, bug fixes, new features` > The ticket involves implementing code changes, bug fixes, and new features in a Python script for Mission Control internals.

Luci picking up this ticket (background worker).

Ticket picked up by Luci via MC dispatcher. MC-4453: Telegram per-target busy-lock + /stop_all admin command Work this ticket in the live tmux runtime. Use DONE:, REVIEW:, or QUESTION: when you need MC to reflect the next state.

Ticket runtime send failed while dispatching. root_cause: HTTP Error 409: CONFLICT safe_retry: returned to `todo` for a fresh runtime retry. human_input_required: no

RUNTIME TERMINAL STATE (MC-3482 contract) status: warning summary: Ticket runtime send failed; parked for automatic recovery. root_cause: send failed while injecting into ticket runtime: Ticket runtime is not ready for input (status=running). Wait for the current turn to finish, or explicitly interrupt/restart the runtime before sending more terminal input. This message was not sent. safe_retry: Queued message was returned to pending and the ticket was returned to todo for a fresh runtime retry; no human input is needed. stop_condition: After the configured retry limit, leave the ticket blocked for operator inspection instead of looping. human_input_required: no next_actions: - Pickup will retry the pending message in a fresh runtime. - Inspect runtime/send only if the retry fails again. artifacts: - ticket:MC-4457

MC-4453 is obsolete as written. Target scripts/mc_telegram_bridge.py is deprecated (lives only in _deprecated/), and mc-telegram-bridge.service is disabled+inactive — CCGram replaced it (MC-2617). Writing a busy-lock there = dead code. The requested per-target busy-lock + per-target queueing ALREADY EXIST in the live replacement (ccgram): tmux_manager.send_keys routes through _send_literal_then_enter, which takes a per-window asyncio.Lock (_vim_locks) — "serialized per-window to prevent interleaved probes". The broker also coalesces all pending messages to a target into one merged send per serial 2s cycle. Burst-corruption risk = designed out. Items 1 & 2 satisfied. Item 3 (/stop_all) has no live ccgram equivalent, but "arch-doc roadmap item 8" refers to the deprecated bridge's doc, and the spec is undefined (kill windows? pause delivery? interrupt agents?). Recommendation: close MC-4453 obsolete for items 1&2; if a global delivery kill-switch is wanted, open a new scoped ticket against ccgram with a defined /stop_all contract — don't graft onto dead code. Evidence: docs/findings/MC-4453-telegram-busy-lock-obsolete.md (committed, pushed slot1/mc-MC-4456). QUESTION for you: want /stop_all built on ccgram as a new ticket, or drop it?

Orchestrator gate: CLOSING obsolete-because-done for items 1&2; /stop_all spun out as new scoped ticket. Verified: - Target scripts/mc_telegram_bridge.py is GONE (not in scripts/, not in _deprecated/) and mc-telegram-bridge.service is disabled+inactive. Writing a lock there = dead code. Worker correct. - ccgram.service active and ALREADY has per-target locking: _rate_limit_locks[chat_id] and _queue_locks[user_id] (asyncio.Lock per target) plus a dedicated handlers/messaging_pipeline/message_queue.py drain/refill module. Per-target busy-lock (item 1) + per-target queueing not global (item 2) = designed in. Burst-corruption risk mitigated. (Worker cited _vim_locks; actual symbols are _rate_limit_locks/_queue_locks — same substance.) Decision on item 3 (/stop_all): BUILD IT, but as a new scoped ccgram ticket at LOW priority — the original HIGH safety risk is already covered by the per-target locks, so /stop_all is an emergency-brake nice-to-have, not a corruption fix. Contract defined in the new ticket. NOT grafted onto dead bridge code. FINAL-ASSESSMENT item #3 reconciled. No human input required.

Shadow reviewer verdict: FAIL (advisory only). Ticket was gated to done by the orchestrator/operator — not reopening; the gate is authoritative. Reasons: The ticket explicitly requires implementing a per-target busy-lock, per-target queueing, and a /stop_all admin command in scripts/mc_telegram_bridge.py. The worker circumvented these requirements by claiming the target file is deprecated and the features already exist in a replacement system, then committed only a documentation file rationalizing this decision. Even if the premise is genuinely obsolete, the worker did not implement the requested code changes or provide test evidence for them, and the /stop_all requirement was deferred to a future ticket rather than resolved. Gaps: - No implementation of per-target busy-lock in the specified file (scripts/mc_telegram_bridge.py) - No implementation of per-target message queueing in the specified file - No implementation of /stop_all admin command (arch doc roadmap item 8) - No test evidence or smoke tests added or exercised for any of the three requirements - Only committed change is a documentation/findings file, not functional code