I2693 — A session whose MCP server did not connect says so on the board, and a worker with nothing to do takes an open ask
Close the two behavioural gaps of 2026-10-13: a silent fall-back from MCP to the bare CLI, and a free worker that looks for work of its own while asks to everybody are open.
BLOCKED wave 1 · p0 · implementation profile · runs alone
Part of development-runtime — The runtime has a development surface.
Blocked. This issue cannot start until I2690 is done. The status is derived from that, not declared.
Objective
Close the two behavioural gaps of 2026-10-13: a silent fall-back from MCP to the bare CLI, and a free worker that looks for work of its own while asks to everybody are open.
Why
The owner, 2026-10-13, after a session worked three hours stale and unannounced in a cluster of nineteen workers: this must never happen again; it must be formalized, derived, inferred, enforced, in .ai, announced, a hard requirement, on GitHub Pages, tested, documented and on the landing page. See ADR 0226.
Current state
Measured on master f0696ec535 on 2026-10-13: the session start line showed the majordomus MCP server as failed to connect and no session announced the fall-back; a peer's 'ASKS ALL: I am free, what is unheld' stood unanswered.
Desired state
The provider start hook announces the transport it found and, when it is CLI only, opens the mesh session itself with that fact in its intent; an idle worker's briefing lists the open asks to all, and answering one is one command.
Scope
- .claude/hooks/
- apps/majordomus-cli/src/capability/builtin/
- .ai/repo/providers/
Out of scope
- Making the MCP server connect: that is the runtime lifecycle milestone's
Dependencies
Acceptance criteria
- A start with the MCP server absent produces a board row naming the CLI as the transport
- A worker with no claim is shown the open asks to all and the command that answers one
Validation
- bin/majordomus plan validate
- MJ_TEST_JOBS=2 bash test/run.sh 3010_a_session_joins_the_cluster
Evidence required
- cli_fallback_announced
- open_ask_shown
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I2693.yaml. Read it back with majordomus plan show I2693.