feat(proto): board snapshot delivery — SubscribeEvents snapshot_seq + ListBoardIssues (SEA-1728) - #172
Merged
Conversation
seal-agent
force-pushed
the
compass-repo-1728-board-snapshot-delivery
branch
from
August 5, 2026 19:17
aebef7e to
d6e7645
Compare
seal-agent
force-pushed
the
compass-repo-1728-board-snapshot-delivery
branch
from
August 5, 2026 19:28
d6e7645 to
fcc0335
Compare
… ListBoardIssues (SEA-1728)
Part 4 (board projection delivery) needs the connect-time re-snapshot seam
Matt ruled as Option B (comms-pattern snapshot delivery, not snapshot-as-
events). Two additive surfaces on the public compass.v1 contract:
- SubscribeEventsResponse.snapshot_seq (field 4): the store-space snapshot
boundary a since_seq=0 subscriber gets on its leading frame, mirroring
SubscribeCommsResponse.snapshot_seq. Client unions the catch-up read with
the full live tail and dedups by issue id (never seq-filters the tail).
- ListBoardIssues RPC (+ Request/Response): the durable board re-snapshot
read a UI calls at since_seq=0, the read counterpart to the snapshot-as-
events burst. Single-shot for the bounded MVP board; returns every issue in
all lifecycle states (incl. ARCHIVED, which the Done view needs). Named
ListBoardIssues, not ListIssues, to avoid a compass.v1 duplicate-symbol
collision with the forge-scoped ListIssues{Request,Response} that #149
(forge carrier) adds to agent_gateway.proto in the same package.
Classifier green-keep: ListBoardIssues classified authenticatedOpen (same
access class as the SubscribeEvents tail it re-snapshots), with both
admin-gate spot-check tables extended. The server handler lands in the
compass-server part-4b PR (free CodeUnimplemented default meanwhile).
Refs SEA-1728.
seal-agent
force-pushed
the
compass-repo-1728-board-snapshot-delivery
branch
from
August 5, 2026 19:39
fcc0335 to
1a93de2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part 4 (board projection delivery) needs the connect-time re-snapshot seam
Matt ruled as Option B (comms-pattern snapshot delivery, not snapshot-as-
events). Two additive surfaces on the public compass.v1 contract:
boundary a since_seq=0 subscriber gets on its leading frame, mirroring
SubscribeCommsResponse.snapshot_seq. Client unions the catch-up read with
the full live tail and dedups by issue id (never seq-filters the tail).
read a UI calls at since_seq=0, the read counterpart to the snapshot-as-
events burst. Single-shot for the bounded MVP board; returns every issue in
all lifecycle states (incl. ARCHIVED, which the Done view needs). Named
ListBoardIssues, not ListIssues, to avoid a compass.v1 duplicate-symbol
collision with the forge-scoped ListIssues{Request,Response} that feat(proto): forge-carrier family reconciled to canonical compass.v1 (SEA-1731) #149
(forge carrier) adds to agent_gateway.proto in the same package.
Classifier green-keep: ListBoardIssues classified authenticatedOpen (same
access class as the SubscribeEvents tail it re-snapshots), with both
admin-gate spot-check tables extended. The server handler lands in the
compass-server part-4b PR (free CodeUnimplemented default meanwhile).
Refs SEA-1728.