Browse activity dates from the keyboard #92

New Issue

2026-09-17T10:33:44Z

xavierk commented

2026-09-17 10:33:44 +00:00

Parent

Implement live daily drive activity, keyboard date navigation, and an endurance outlook

What to build

Let a user move from the live view to a chosen local date, inspect its available activity, and return to live monitoring using discoverable keyboard and mouse actions. Keep historical selection stable while collection continues. This slice covers the existing reader-to-user workflow, including fetching the selected date at its available precision; it does not require waiting for the aged-history retention slice.

All behavior follows the parent specification, including its precedence over conflicting earlier TUI requirements. The approved proof uses controlled acquisition and time through a real observation store into public TUI/CLI results; preserve the existing collector/reader ownership and no-fabrication rules.

Acceptance criteria

From normal TUI launch, [ and ] select previous/next day, g opens date entry, t returns to today/live, and arrows inspect the selected view. Visible hints and clickable equivalents describe the same actions.
Date entry accepts a valid local date, reports malformed or unavailable dates visibly, and returns to the prior graph selection when cancelled. Typing must not trigger monitoring, graph, or theme actions.
Selecting a date obtains the correct local-day evidence through the normal read path and displays measured data at its available precision. Provide transitions between the recent live view, a selected day, and longer history without an arbitrary latest-90-days barrier for retained summaries.
Historical date, plotted measurement, and selected-point context remain stable across background refresh where that evidence still exists. Returning to live is an explicit user action; never jump away merely because a new sample arrived.
Resolve the existing t theme binding in favor of today/live, preserve themes through a discoverable non-conflicting control, and update help. Preserve pause/resume, collect-now, quit, disclosures, and reduced motion.
Drill-down must show available data rather than overwrite synchronous rendering with a stuck loading placeholder. Loading, unavailable history, measured zero, and partial/gap states must be distinguishable.
Verify keyboard actions with the existing headless driver from normal launch rather than manually assigning focus. Assert visible selected dates, readouts, data, and action results rather than private indices.
Verify equivalent clickable actions, date-entry focus behavior, theme control, and accessible date/totals/evidence output at 80×24 and constrained widths. Data and totals must not change with graph width.

Blocked by

Plot live drive activity every three minutes

## Parent [Implement live daily drive activity, keyboard date navigation, and an endurance outlook](https://git.bongbetic.com/xavierk/Fenris/issues/88) ## What to build Let a user move from the live view to a chosen local date, inspect its available activity, and return to live monitoring using discoverable keyboard and mouse actions. Keep historical selection stable while collection continues. This slice covers the existing reader-to-user workflow, including fetching the selected date at its available precision; it does not require waiting for the aged-history retention slice. All behavior follows the parent specification, including its precedence over conflicting earlier TUI requirements. The approved proof uses controlled acquisition and time through a real observation store into public TUI/CLI results; preserve the existing collector/reader ownership and no-fabrication rules. ## Acceptance criteria - [ ] From normal TUI launch, `[` and `]` select previous/next day, `g` opens date entry, `t` returns to today/live, and arrows inspect the selected view. Visible hints and clickable equivalents describe the same actions. - [ ] Date entry accepts a valid local date, reports malformed or unavailable dates visibly, and returns to the prior graph selection when cancelled. Typing must not trigger monitoring, graph, or theme actions. - [ ] Selecting a date obtains the correct local-day evidence through the normal read path and displays measured data at its available precision. Provide transitions between the recent live view, a selected day, and longer history without an arbitrary latest-90-days barrier for retained summaries. - [ ] Historical date, plotted measurement, and selected-point context remain stable across background refresh where that evidence still exists. Returning to live is an explicit user action; never jump away merely because a new sample arrived. - [ ] Resolve the existing `t` theme binding in favor of today/live, preserve themes through a discoverable non-conflicting control, and update help. Preserve pause/resume, collect-now, quit, disclosures, and reduced motion. - [ ] Drill-down must show available data rather than overwrite synchronous rendering with a stuck loading placeholder. Loading, unavailable history, measured zero, and partial/gap states must be distinguishable. - [ ] Verify keyboard actions with the existing headless driver from normal launch rather than manually assigning focus. Assert visible selected dates, readouts, data, and action results rather than private indices. - [ ] Verify equivalent clickable actions, date-entry focus behavior, theme control, and accessible date/totals/evidence output at 80×24 and constrained widths. Data and totals must not change with graph width. ## Blocked by - [Plot live drive activity every three minutes](https://git.bongbetic.com/xavierk/Fenris/issues/91)

xavierk added the ready-for-agent label 2026-09-17 10:33:44 +00:00

xavierk added a new dependency 2026-09-17 10:34:08 +00:00

#91 Plot live drive activity every three minutes

xavierk referenced this issue from a commit

2026-09-18 08:48:52 +00:00

Browse activity dates from the keyboard (#92)

xavierk closed this issue

2026-09-18 08:49:19 +00:00

Sign in to join this conversation.