id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031)

Filed by queue triage task 6875 (2026-11-03) from the design record on main, doc/2026-11-01_design_id2031.md §2, which names this as "a prerequisite missing from #3788–#3790's current dependency graph" — it has no issue of its own, so the gap is invisible to the fleet.

The gap (per the design record, verified against main 2026-11-03)

ChainExt carries a free-string kind and optional group (pkgs/id/src/chain.rs, root id package), and the signed header commits to a body's hash and size while the body itself is separate.
Ingest accepts and verifies a supplied body (pkgs/id/src/event_store/ingest.rs), but store_event writes event.bytes (the signed header) only (pkgs/id/src/event_store/mod.rs); range sync sends stored events and fork-proof headers (pkgs/id/src/event_store/sync.rs).
Consequence: a didit.* CBOR body can be validated at ingest but is not yet available for later retrieval or cross-device replication.

Scope

Design + implement generic application event-body persistence, retrieval, and range-sync in pkgs/id (not didit-specific), so any kind with a CBOR body — starting with the four didit.* kinds from issue #3788 — round-trips: stored at ingest, retrievable by event id/hash, and carried by range sync with the same integrity checks as headers.

Acceptance

A stored event with a generic body can be retrieved byte-identically after restart.
Range sync between two nodes transfers bodies for events the peer lacks, with hash/size verification against the signed header.
Existing header-only kinds are unaffected; tests cover body-present and body-absent events.

Relations

Blocks the app phase: issue id(app): PoC — sticky notes + did-it tracker, the first ID app (Phase 3 of #2031) #3790 (Phase 3 of id: design+PoC: sticky-notes / did-it tracker — the first ID app #2031) cannot read tracker state back without this.
Does NOT block issue id(didit): schema types + pure evaluator in pkgs/id/src/didit/ (Phase 1 of #2031) #3788 (Phase 1: library-only schema types + pure evaluator, golden tests only).
Parent: issue id: design+PoC: sticky-notes / did-it tracker — the first ID app #2031.

Acceptance criteria

Generic event-body persistence exists for pkgs/id: bodies can be stored, retrieved by event id, and range-synced without per-type bespoke code.
Retrieval of a missing body returns a typed not-found (not a panic or silent empty).
Range-sync is idempotent: re-syncing a range does not duplicate bodies.
Covered by tests exercising persistence, retrieval, and a repeated range-sync.

Intake review

Related: see the issue body and its linked references; no merged PR was found that resolves this issue at intake time (checked at fleet-monitor run 2026-11-03 04:12 CST).

Notes: Design-bearing slice (generic event-body persistence for pkgs/id). Suggested approach: mirror the existing per-type body store's shape before inventing a new one, and confirm the range-sync contract with the slices that consume it. Risks: sync idempotency and body-size bounds — both are called out in the criteria.

Risks / suggested approach: as noted above; acceptance criteria have been appended to the issue body and labels normalized by the fleet monitor.

🤖 Agent note · filed

Agent: fleet monitor (repo-fleet-monitor)
Session / ID: repo-fleet-monitor run 2026-11-03 04:12 CST
Found via: monitor reconciliation (intake enrichment, protocol §5)
Task: Intake enrichment — acceptance criteria, labels, related context.

agent-note:v1
state: triaged (coverage pass)
Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
Found via: coverage pass 2026-11-03

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-j
Session / ID: task 9198
Found via: queue claim
Task: Task 9198 for issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837 is assigned to the opencode execution lane; handed off to the opencode claimant, which launches the bound session. Prior note warned this task was near its attempt cap — claimant binding before lease expiry matters here.
Expectation: claimant launches the bound opencode session for task 9198; this lane does not work it directly.
Links: task 9198; issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-h
Session / ID: task 9198
Found via: queue claim
Task: triage of issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837 (id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases) — claimed by lane code-h and assigned to the opencode execution lane
Expectation: the opencode-claimant launches a bound opencode session for task 9198, which drives the triage to its terminal state
Links: issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-a
Session / ID: task 9198, repo-queue-worker-shift 2026-11-04 18:40 CST
Found via: queue claim
Task: task 9198 (triage of issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837) is assigned to the opencode execution lane; handed off to the laptop claimant — this lane does not work it directly.
Expectation: claimant launches the bound opencode session, which drives task 9198 to a terminal state; if unlaunched, task 9198 returns to the queue at lease expiry.
Links: id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837

Picked up as task 9198 by lane code-c (repo-queue worker) and handed off to the opencode execution lane per the execution-lane assignment for task 9198. The laptop claimant launches the bound opencode session for task 9198; this lane does not work issue #4837 directly. Note: task 9198 is at attempts 15/24.

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-n
Session / ID: task 9198
Found via: queue claim
Task: Handing task 9198 (triage for issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837, id generic event-body persistence/retrieval/range-sync) to the opencode execution lane per the lane assignment; the bound opencode session drives it to a terminal state. Revalidated fresh this claim: issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837 state/labels checked via gh (see queue checkpoint); no hard-stop labels (held, user/owned, do-not-merge, do-not-auto-edit). Attempts 16/24.
Expectation: m — claimant launches the bound opencode session; triage outcome recorded on task 9198 / issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837.
Links: issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837; queue task 9198

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-t
Session / ID: task 9198
Found via: queue claim
Task: Handing task 9198 (triage of issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837) to the opencode execution lane; the bound claimant session drives it to its terminal state.
Expectation: Claimant triages issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837 per the task packet.
Links: issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-a
Session / ID: task 9198
Found via: queue claim
Task: task 9198 (triage, issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837) assigned to execution lane opencode; handing off to the opencode claimant for the bound session. Fresh revalidation: issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837 is OPEN with no hard-stop labels.
Expectation: the bound opencode session triages issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837 and drives task 9198 to a terminal state.
Links: issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-c
Session / ID: task 9198
Found via: queue claim · repo-health-code-pilot
Task: task 9198 (triage, issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837) claimed by lane code-c and assigned to the opencode execution lane; handing off to the laptop opencode claimant, which launches the bound session.
Expectation: done = task 9198 acceptance met for issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837.
Links: issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-r
Session / ID: task 9198
Found via: queue claim
Task: triage of issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837 handed off to the opencode execution lane; the laptop claimant launches the bound opencode session.
Expectation: effort/m triage verdict + routing recorded on issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837 by the claimant session.
Links: issue id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837

🤖 Agent note · handed off

Agent: fleet monitor
Session / ID: task 9198 (repo-fleet-monitor run 2026-11-05T15:32:18Z)
Found via: monitor reconciliation (Duty 1 claim/label divergence repair)
Task: Claim evaporated: task 9198 is queued and unclaimed in repo-health-code-pilot, but this issue still carried claimed labels. Labels reset to the truth (queue/queued + status/needs-triage). Checkpoint stage at evaporation: handed_off.
Expectation: The next lane claim picks task 9198 up from the queued state and posts a fresh pickup note.

Navigation Menu

Repository navigation

id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837

The gap (per the design record, verified against main 2026-11-03)

Scope

Acceptance

Relations

Acceptance criteria

Intake review

27 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id: generic event-body persistence, retrieval and range-sync — prerequisite for the didit tracker phases (#2031) #4837

Description

The gap (per the design record, verified against main 2026-11-03)

Scope

Acceptance

Relations

Acceptance criteria

Activity

dezren39 commented on Nov 3, 2026

Intake review

dezren39 commented on Nov 3, 2026

27 remaining items

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions