A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I2413
A linked worktree cooperates through its repository's running server, and a start that cannot ensure one says why
Where it stands
devtask.issue- Readiness
- ready no dependency and no gate holds it; nobody has started it
- Status
- READY
- Can start
- startable
- Milestone
- Milestone status
- PLANNED
- Wave
0- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
0of1
Moves
plan.transitionWhat it is
- Objective
- Mesh commands in a linked worktree with no server of its own use a running server of the same repository (the primary's, or the first ready one), and the session-start hook reports, never silently skips, when it cannot ensure a server.
- Why
- `majordomus mesh handover publish` in a linked worktree answered 'cooperation inactive ... no running server for this checkout' (apps/majordomus-cli/src/commands/mesh.rs:272-279) because the lease is per checkout (lease.rs:465-467). The workaround `serve ensure` in that worktree started a second server on *:8741 beside the primary's 127.0.0.1:8741 (2026-10-10). The start hook skips with 'not ensured' when the binary is unbuilt or stale (lib/capture.sh:1613-1620).
- Now
- A worktree without its own server is off the mesh; the start hook skips silently.
- Wanted
- A worktree's mesh commands reach the repository's running runtime; a start that ensures nothing prints the reason and the remedy.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- In a linked worktree with no server, `mesh handover publish` and `mesh claim` reach the primary's running runtime
- No command run in a worktree starts a server bound beyond loopback
- A start whose binary is stale prints why no server was ensured and what to run
- Validation
bin/majordomus plan validatecargo test --test mcp_shared- Evidence required
worktree_publishes_through_primary_test- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
apps/majordomus-cli/src/commands/mesh.rsapps/majordomus-cli/src/lease.rslib/capture.shdocs/MESH.mdtest/cases- Not
- unknown: the record declares no `non_scope`
- Depends on
- unknown: the record declares no `depends_on`
- Priority
- p1
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-10-10
- Updated
- 2026-10-10
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
| Level | Code | Message | Reproduce |
|---|---|---|---|
| WARN | scope_conflict | shares apps/majordomus-cli/src/commands/mesh.rs with I2414; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares docs/MESH.md with I2415; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2653; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2713; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2714; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2716; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2717; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2718; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2720; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares docs/MESH.md with I2723; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2731; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares lib/capture.sh with I2734; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2740; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2742; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2747; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2760; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2786; they may not run concurrently | majordomus plan validate |