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
I2734
A session joins the mesh at its start and leaves it at its end
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
- Behind it in all
3- Evidence
0of1
Moves
plan.transitionWhat it is
- Objective
- The provider's start event opens the session on the mesh of the checkout's shared server as <provider>-<provider session>, with client, branch, head and the active task; the briefing names that id; a resume says it again; the end event closes it.
- Why
- On 2026-10-15 the owner asked why a new session did not join the mesh, report or start working, neither through direnv nor at session start, and why nothing enforces it. Measured: the start hook only printed the mesh's health (lib/capture.sh mj_capture_mesh_line); the only mesh session a Claude Code session got was its nameless board connection board-pN, with no intent and no claim, until the worker chose to announce. The milestone's first branches (I2285..I2292, 2026-10-10) never reached a pull request.
- Now
- The start event prints one health line about the mesh and opens no mesh session; the end event closes none.
- Wanted
- Every provider session with a session id is on the mesh from its start event under a durable id the provider's payload names again, and off it at its end event, best-effort and never failing the event.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- A start event with a ready server whose mesh runs opens claude-code-<session id> on the mesh with client, branch and head
- The briefing names the mesh session id under the Mesh line
- A resume after majordomus start carries the active task and its title
- The end event closes the mesh session
- Without a server the start event opens the episode and names no mesh session
- Validation
bin/majordomus plan validatebash test/run.sh 3066_a_session_joins_the_mesh_at_start 54_session_lifecycle_hooks 1054_every_session_is_told_the_stream- Evidence required
case_3066- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
lib/capture.shtest/cases/3066_a_session_joins_the_mesh_at_start.sh.ai/repo/project/issues/I2734.yaml.ai/repo/project/milestones/every-session-joins-the-mesh.yaml- Not
- unknown: the record declares no `non_scope`
- Depends on
- none
- Priority
- p0
- 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-15
- Updated
- 2026-10-15
- 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 .ai/repo/project/milestones/every-session-joins-the-mesh.yaml with I2742; they may not run concurrently | majordomus plan validate |