Skip to content

fix: persist monitor responses and preserve Claude ETA history - #75

Merged
gyng merged 2 commits into
mainfrom
fix/persistent-monitor-cache
Oct 21, 2026
Merged

gyng merged 2 commits into
mainfrom
fix/persistent-monitor-cache

Conversation

@gyng

@gyng gyng commented Oct 21, 2026

Copy link
Copy Markdown
Owner

Monitor Switch restores validated per-monitor responses across app restarts, keeping cached controls visible and disabled during refresh. A fixed-size loading indicator preserves row geometry, and polling now waits for slow input switches instead of overwriting their pending highlight.

Claude ETA history now tolerates small reset-timestamp variations. This fixes live observations being discarded on every refresh while preserving genuine quota-reset boundaries.

Includes the requested human summary for v0.0.68 and future release guidance. New fixes are recorded under Unreleased; there is no version bump or release tag.

Validation: 4,687 unit/component tests pass with 100% coverage (rerun with four workers after an unrelated timing-sensitive test missed its bound; that test also passes in isolation). Type check, lint and production build pass. The monitor changes passed all 125 browser tests, including persistent-cache geometry; focused browser checks also pass. Backend tests and all-target Clippy passed during the monitor implementation.

@gyng
gyng merged commit f19b72c into main Oct 21, 2026
6 checks passed
@gyng
gyng deleted the fix/persistent-monitor-cache branch October 21, 2026 07:20
@gyng gyng mentioned this pull request Oct 22, 2026
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.

1 participant