I4003 — Devtask.implement runs readiness, preflight, claim, worktree and one execution

✕BLOCKED wave 2 · p1 · implementation profile · runs alone

Part of a-session-proceeds-through-the-mesh — A session proceeds through the mesh: it finds the work, claims it once, runs it watched and stops when the intent is met.

Objective

devtask.implement: issue readiness and intents.preflight, then mesh.claim, worktree.create and an agent run through executions.start; it refuses an overlap or an invalid intent with a reason and answers pending when no worker is attached (Mission Control B4).

Why

Taking an issue is a hand-run sequence; two sessions can follow it at once and a double request starts two runs.

Current state

Not built: this issue is planned by the milestone a-session-proceeds-through-the-mesh and nothing of it exists.

Desired state

The acceptance criteria below hold and case 4003 proves them.

Scope

• apps/majordomus-cli/src/capability/builtin/devtask.rs
• apps/majordomus-cli/src/execution
• docs/EXECUTIONS.md
• test/cases/4003_devtask_implement_claims_creates_and_starts_once.sh
• .ai/repo/project/issues/I4003.yaml

Dependencies

• I4000○READY A repeated executions.start with the same key answers one execution
• I4001✕BLOCKED The execution state machine has Authorizing, Claimed, Verifying, Refused and UnknownOutcome
• I4002○READY Worktree.create is a typed writing capability
• I4004✕BLOCKED The executor takes the issue's mesh claim in the handler and releases it when the run ends

What waits on this

• I4005✕BLOCKED Proceed.step answers one idempotent work order

Acceptance criteria

• A ready issue with a valid intent starts one execution holding its mesh claim in a new worktree
• An overlapping claim or an invalid intent is refused with the reason and nothing is created
• No attached worker answers pending, not failed
• The same request twice answers the same execution (I4000)

Validation

• env -u MAJORDOMUS_SHARE -u MAJORDOMUS_HTTP_HOST -u MJ_ROOT bash test/run.sh 4003_devtask_implement_claims_creates_and_starts_once

Evidence required

• case_4003_devtask_implement_claims_creates_and_starts_once

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