Skip to content
Cockpit0.29.0
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

I2140

Paging mesh.events returns every event exactly once

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
ACTIVE
Wave
0
Waiting on
none
Holds back
Behind it in all
1
Evidence
0 of 1
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2140

majordomus plan verify I2140

majordomus plan done I2140

What it is

Objective
Page mesh.events by the causal key and return the last key returned as the next cursor.
Why
EventList.lamport is documented as 'the after of the next page' (apps/majordomus-cli/src/capability/builtin/mesh.rs:594-596) but is the journal's maximum lamport (apps/majordomus-cli/src/mesh/journal.rs:2124-2133), so a truncated page skips the rest of the journal. Paging by the last returned lamport also skips events that share it across streams, because the filter is lamport > after (apps/majordomus-cli/src/capability/builtin/mesh.rs:601-619). No test covers events_after. Baseline audit of 2026-10-09 at master 1fb8d6be44, mesh gap 8 and drift 9.
Now
A client that follows the documented cursor misses events.
Wanted
Pages are cut by the causal key (lamport, stream, seq) (apps/majordomus-cli/src/mesh/journal.rs:858), the answer carries the last returned key as the next cursor, and mesh events --after accepts it.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • Walking mesh.events with limit 1 over a journal where several streams share a lamport returns every event once, in causal order
  • The cursor the schema documents is the cursor the next page accepts
Validation
bin/majordomus plan validatecargo test --test meshcargo test --lib mesh::journal
Evidence required
events_paging_test
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/capability/builtin/mesh.rsapps/majordomus-cli/src/mesh/journal.rsapps/majordomus-cli/src/cli/local.rsapps/majordomus-cli/tests/mesh.rsdocs/MESH.md
Not
unknown: the record declares no `non_scope`
Depends on
none
Priority
p2
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-09
Updated
2026-10-09
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

LevelCodeMessageReproduce
WARNscope_conflictshares apps/majordomus-cli/src/mesh/journal.rs with I2410; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares docs/MESH.md with I2411; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares docs/MESH.md with I2412; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares docs/MESH.md with I2413; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares apps/majordomus-cli/src/capability/builtin/mesh.rs with I2414; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares apps/majordomus-cli/src/capability/builtin/mesh.rs with I2415; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares apps/majordomus-cli/src/capability/builtin/mesh.rs with I2720; they may not run concurrentlymajordomus plan validate
WARNscope_conflictshares apps/majordomus-cli/src/mesh/journal.rs with I2723; they may not run concurrentlymajordomus plan validate