KofTwentyTwo/Jarvis
2
0 Fork 0
Code Issues 111 Pull Requests 16 Actions Packages Projects Releases 4 Wiki Activity

M-3: Diagnostics.streamReplayEvents + snapshotReplayEvents (R-017 single-emit) #112

New Issue
Open
opened 2026-05-12 19:37:03 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-05-12 19:37:03 +00:00 (Migrated from github.com)
Copy link
Copy source

Goal

Diagnostics.streamReplayEvents + snapshotReplayEvents. Replay event emission is a side effect of API event emission (one call → one replay row + one bus event), preserving R-017.

Scope

  • streamReplayEvents(since:) -> AsyncStream<ReplayEntry>
  • snapshotReplayEvents(range:) -> [ReplayEntry]
  • Replay-event side-effect contract: every API event emission ALSO writes one replay row
  • Single-emit invariant (G-008 / OQ-T5)

Files

  • packages/JarvisAPI/Sources/JarvisAPI/Surfaces/Diagnostics+Adapter.swift
  • packages/Replay/Sources/Replay/ReplayLog.swift — side-effect emit wiring

Acceptance

  • Stream API delivers events incrementally
  • Snapshot returns range
  • Memory.applyOp(.add, …) produces ONE replay row AND one bus event (R-017)
  • Replay roundtrip asserted in scenario S-DIAG-007

Test

S-DIAG-007 asserts 1:1 invariant between bus emit and replay row.

Parent epic

#7

Source

.planning/architecture/JARVIS-API-MIGRATION-PLAN.md §2.4 (M-3.4)
.planning/architecture/REVIEW-MIGRATION-RISK.md R-017

## Goal Diagnostics.streamReplayEvents + snapshotReplayEvents. Replay event emission is a side effect of API event emission (one call → one replay row + one bus event), preserving R-017. ## Scope - `streamReplayEvents(since:) -> AsyncStream<ReplayEntry>` - `snapshotReplayEvents(range:) -> [ReplayEntry]` - Replay-event side-effect contract: every API event emission ALSO writes one replay row - Single-emit invariant (G-008 / OQ-T5) ## Files - `packages/JarvisAPI/Sources/JarvisAPI/Surfaces/Diagnostics+Adapter.swift` - `packages/Replay/Sources/Replay/ReplayLog.swift` — side-effect emit wiring ## Acceptance - [ ] Stream API delivers events incrementally - [ ] Snapshot returns range - [ ] `Memory.applyOp(.add, …)` produces ONE replay row AND one bus event (R-017) - [ ] Replay roundtrip asserted in scenario `S-DIAG-007` ## Test `S-DIAG-007` asserts 1:1 invariant between bus emit and replay row. ## Parent epic #7 ## Source `.planning/architecture/JARVIS-API-MIGRATION-PLAN.md` §2.4 (M-3.4) `.planning/architecture/REVIEW-MIGRATION-RISK.md` R-017
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
area:agent
area:build
area:bus
area:devtool
area:hud
area:logging
area:mcp
area:memory
area:vision
area:voice
audit-finding
bug
Something isn't working
 carry-forward
comment-cleanup
Comment / docstring cleanup per .planning/code-commenting-guide.md
 dependencies
Dependency updates
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 epic
good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 javascript
Pull requests that update javascript code
 migration
question
Further information is requested
 severity:critical
severity:high
severity:low
severity:medium
wontfix
This will not be worked on
No labels area:logging enhancement migration
Milestone
No items
No Milestone v0.5 — API M-0..M-3 (Self / Settings / Diagnostics surfaces)
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/Jarvis#112