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
I2414
mesh.state and mesh.peers answer a filtered summary that fits one tool answer
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
- Give mesh.state and mesh.peers inputs that narrow and summarise: a kind (sessions, claims, handovers, reviews), open-only, mine-only, a scope or PR substring and a limit, with a counts-only summary by default.
- Why
- Both take no input (apps/majordomus-cli/src/capability/builtin/mesh.rs:1184-1216). Measured on 2026-10-10: mesh.state 449 kB and mesh.peers 313 kB on this Mac's server at 23:50Z (165 claims, 126 sessions, 133 overlaps, 15 handovers, 30 reviews; the live items alone about 150 kB), and one 80-event page of mesh.events came to 83k characters. Every MCP client's tool-result limit is exceeded, so every read went through a saved file and jq.
- Now
- Whole-state answers only; mesh.events is the only paged read.
- Wanted
- A default answer under 16 kB with counts and the newest items; filters that return exactly the asked slice; the full state still available on request.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- mesh.state with no input answers under 16 kB on a journal of 20 000 events
- Each filter returns exactly the matching items, proved on a fixture state
- The full answer is still available with an explicit input
- Validation
bin/majordomus plan validatecargo test --lib capability::builtin::meshcargo test --lib mesh::pagecargo test --test mesh_cooperation- Evidence required
mesh_state_filtered_test- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
apps/majordomus-cli/src/capability/builtin/mesh.rsapps/majordomus-cli/src/mesh/state.rsapps/majordomus-cli/src/mesh/page.rsapps/majordomus-cli/src/cli.rsapps/majordomus-cli/src/commands/mesh.rsapps/majordomus-cli/src/cockpit/pages.rsapps/majordomus-cli/src/integration/exclusive.rsapps/majordomus-cli/tests/mesh_cooperation.rsapps/majordomus-cli/tests/integration_across_machines.rsapps/majordomus-cli/tests/reasoning_mesh.rsscripts/lib/advisors/mesh-review.mjsscripts/lib/advisors/contract.test.mjsdocs/claims/mesh-liveness-expiry.mddocs/claims/mesh-three-runtime-convergence.mddocs/MESH.md- 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/capability/builtin/mesh.rs with I2415; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares apps/majordomus-cli/src/capability/builtin/mesh.rs with I2720; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares apps/majordomus-cli/src/mesh/state.rs with I2723; they may not run concurrently | majordomus plan validate |