Skip to content

feat(status): expose heartbeat journal progress - #26

Open
edenbuilds wants to merge 1 commit into
loop-js:masterfrom
edenbuilds:codex/heartbeat-progress-5
Open

feat(status): expose heartbeat journal progress#26
edenbuilds wants to merge 1 commit into
loop-js:masterfrom
edenbuilds:codex/heartbeat-progress-5

Conversation

@edenbuilds

Copy link
Copy Markdown
Contributor

Summary

  • track the latest durable journal sequence on each run heartbeat
  • expose that sequence through LoopStatus.progressSeq and loop status
  • keep pre-existing records readable, reporting unknown progress until their next heartbeat

Why

A fresh heartbeat proves liveness but not progress. Repeated status snapshots now show whether the durable event stream is advancing, which gives future watchdog/takeover logic a reliable progress signal. Stream-only reserved sequence numbers do not count as durable progress.

Verification

  • regression tests failed on current master: missing Journal.lastSeq, missing heartbeat seq, and status omitted journal progress
  • focused suite: 58 passed
  • bun run check
  • full bun test: 423 passed, 2 intentional live-Claude tests skipped, 0 failed
  • git diff --check

Fixes #5

Track the latest durable journal sequence on the run heartbeat and expose it through LoopStatus and the CLI so repeated snapshots distinguish liveness from progress. Preserve compatibility with records written before progress-bearing heartbeats.

Fixes loop-js#5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

status: heartbeat carries progress, not just liveness

1 participant