I2288 — A task is on the mesh while it works

✓DONE wave 1 · p0 · implementation profile · runs alone

Part of every-session-joins-the-mesh — Every LLM session joins the Majordomus mesh at start, told the mesh as work.

Objective

majordomus start claims the task's scope on the checkout's running server as an advisory claim of the mesh session task-<id>, with the task's title as intent and its issue, and keeps the key on the task record; finish closes that session.

Why

The owner asked on 2026-10-10, and again on 2026-10-15, that every LLM session use the mesh automatically. A task's scope lived in the checkout's task record and on this machine's board; another machine saw it only if the worker remembered to claim it. The 2026-10-10 implementation (branch feature/a-task-is-on-the-mesh) never reached a pull request; this is its port onto master, after I2734 put the provider session itself on the mesh.

Current state

majordomus start reports overlaps with the local board and claims nothing on the mesh.

Desired state

After majordomus start the task's scope is an advisory claim of task-<id> on every linked runtime; after finish the session is closed and its claims end with it; with no server or no running mesh nothing is claimed and nothing fails.

Scope

• lib/common.sh
• lib/start.sh
• lib/finish.sh
• test/cases/3067_a_task_is_claimed_on_the_mesh.sh
• docs/MESH.md

Dependencies

• I2734✓DONE A session joins the mesh at its start and leaves it at its end

What waits on this

• I2289○READY A task built off the mesh is refused

Acceptance criteria

• After majordomus start the task's scope is a live claim on every linked runtime
• After finish the claim is released
• Without a server start records no claim and does not fail

Validation

• bin/majordomus plan validate
• bash test/run.sh 3067_a_task_is_claimed_on_the_mesh 04_start_check 06_finish

Evidence required

• case_3067

Evidence

Timeline

started

2026-10-19T13:53:11Z

verified

—

completed

2026-10-19T13:53:27Z

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/I2288.yaml. Read it back with majordomus plan show I2288.