Fenris/CHANGELOG.md

Changelog

[Unreleased]

[0.7.0] - 2026-10-06

Added

• Show a provisional usage-adjusted theoretical lifespan after 3 observed hours, with the hours observed and a short-horizon spread, instead of waiting for a full local day.
• Show the projection stage and an evidence ladder of Supported conditions, each met or unmet with its reason, so confidence visibly strengthens with each collection run.
• Show the sustained-regime write rate when no endurance baseline applies.
• Enter a rated TBW from the dashboard with b, saved as an unverified override, so the lifespan appears without the CLI.
• Jump to the first or last point with Home and End on every graph, and a week at a time with PgUp and PgDn in the Day and History views.
• Move through graph points with the mouse wheel, focus any panel by clicking it, and click the footer and activity tool chips to run their actions.
• Open a Diagnostics panel with i: the decoded critical warning, power-on hours, power cycles, unsafe shutdowns, media errors and available spare with their change over the selection, plus hourly or daily temperature, active/idle/powered-off/unknown split and coverage. History bars draw reads beside writes while it is open, and a set critical warning shows as a badge in the endurance outlook.
• Record more drive evidence from each collection run (host read and write commands, controller busy time, error log entries, warning and critical temperature time, and thermal management transitions where the drive reports them) and show it in the Diagnostics panel. Existing stores migrate automatically; earlier samples show n/a for the new counters.

Changed

• Generate the footer and help screen from the dashboard's key bindings so they always agree, and collapse the footer to "? help · q quit" under 80x24.
• Make Tab and Shift+Tab visit only the dashboard panels.
• Show every dashboard time in local time with its timezone, keep a secondary UTC line when a point is inspected, and report the monitoring period start in local time from fenris-monitor enable.
• Treat the complete-local-day requirement as a contributing fact rather than a gate, and stop the TUI and CLI from deciding when a projection can be shown.

[0.6.0] - 2026-09-29

Added

• Preserve local-day read and write evidence separately, including ambiguous midnight-spanning volume as shared evidence instead of assigning it to either day.
• Keep valid observations pending when publication fails, and recover them without exposing partial history or counting activity twice.
• Preserve live-point inspection and historical activity selection through graph refresh.

Changed

• Prune old detail only after durable summaries and required boundary evidence are published.
• Require a complete local day to fit within one monitoring period before it can open the endurance outlook.

[0.5.0] - 2026-09-19

Changed

• Make drive activity the focus of a Chalktone dashboard with Live, Day, and History tabs, panel zoom, and fixed monitoring controls.
• Replace block bars with labelled dotted volume plots that fit the terminal and preserve gaps, partial evidence, and point inspection.

Fixed

• Preserve historical selections and store-fault messages through graph refresh and resize.
• Show hourly drill-down results without overwriting them with a loading placeholder.
• Keep known unallocated daily volume visible across coverage gaps, and distinguish missing hourly evidence from zero on small terminals.
• Stage package directories with consistent public permissions, avoiding openSUSE RPM conflicts and inaccessible runtime paths when built with a restrictive umask.

[0.4.0] - 2026-09-18

Added

• Show local-day read and write totals with their recorded timezone, labelled as totals so far for the current day.
• Open the dashboard on a live three-hour written-volume graph with a read/write toggle and selected-point inspection.
• Browse history by day from the keyboard with [, ], g date entry, and t for today and the live view.

Changed

• Collect every three minutes on systemd and runit, plot live points at their actual timestamps, and retain three-minute detail for 14 days before durable summaries.
• Withhold the endurance outlook until one full local observation day has usable evidence, then show it with categorical confidence.

Fixed

• Keep midnight-spanning activity once as shared boundary evidence instead of adding it to both days.
• Publish derived hour and day history consistently with each collection run.

[0.3.7] - 2026-09-16

Changed

• Make usage-history axes, units, UTC boundaries, active 7/14/30/90-day window, gaps, partial periods, stacked write attribution, and hourly drill-down explicit; keep live graph data refreshed on the current three-minute cadence.

[0.3.6] - 2026-09-16

Changed

• Use sentence case throughout the dashboard and add persistent keyboard and sudo guidance.
• Share read-only status acquisition between the CLI and TUI, preserving unknown monitoring state and store-fault recovery guidance.
• Use one authenticated action path for the CLI and TUI; let valid collection runs finish without the former 30-second dashboard cutoff.
• Remove the unused sparkline and habit-bar rendering path while retaining the interactive history graph.
• Align all package formats on the MIT license and Python 3.10 minimum; include the license text in native packages.

Fixed

• Correct observation-store directory permissions in native packages, including repair of older runit installations during upgrade.

[0.3.5] - 2026-09-14

Added

• Show trustworthy first-use history, qualifying-day progress, and confidence in the dashboard.
• Add an interactive daily-writes graph with hourly drill-down and evidence-anchored scenario windows.
• Repair retained observation history safely and keep its retention state visible.
• Present a unified monitoring status, drive-health context, and Fenris identity in the dashboard.
• Remember accessible colour and motion preferences and keep the dashboard usable at constrained terminal sizes.

[0.3.4] - 2026-09-10

Added

• Add Fenris identity and a polkit authentication notice to the dashboard.
• Clarify monitoring continuity, deliberate pauses, and quitting in the dashboard and status output.
• Add per-release notes with installation, verification, and rollback guidance.