Clarify status telemetry and thread freshness in the UI and CLI - #81
Merged
Merged
Conversation
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
1 participant
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.
Collector timestamps currently look like response freshness, making the index appear both newer and older than the thread data it serves. Label status as collector telemetry in the web UI, both CLIs, and JSON; explain that bulk comment checkpoints do not track per-thread refreshes. Replace thread and outline “current to” stamps with “indexed at,” naming body/comment scope and the unknown later GitHub changes.
Closes #46.
Validation:
make checkwith SQLite and Postgres — 1,194 passed, 4 skipped; final JSON stamp assertion also passed on both backends. Includes renderer and status JSON regression coverage and UI JavaScript syntax checks.Live investigation: transformers polling is healthy (successful poll at 2026-09-16 08:37:54 UTC); the nightly files job also succeeded. The September 9 bulk-comment rows are historical checkpoints, not evidence of a stalled poller.
Bumps 0.3.16 → 0.3.17 for the visible/API changes. Deploy client and daemon together when merging; this PR has not been deployed.