Exact

Exact Union RegExp

iamtoruk 7c54cf85c2 optimize: classify findings as fix/nudge/keep and mark measured vs estimated ... Every finding now resolves to a class (apply-able fix, habit nudge, or informational keep) and a basis (measured from provider-counted usage, or estimated from a schema/heuristic model), both from one table next to the FindingId union. The class follows the plan layer: an id is 'fix' only when buildPlan routes it, and an instance drops to 'nudge' when it lacks the payload or cause its builder needs. CLI, TUI and the desktop app group findings under Fix now / Habits / FYI with continuous numbering; the CLI header reports 'N measured · M estimated' in place of the blanket 'Estimates only.' footer. The JSON report gains class + basis per finding and summary.measuredSavingsUSD; existing fields are unchanged. The menubar's top three follow the same order, since every surface reads the sorted findings list. Sessions whose cost the provider never reported leave the cost-outliers peer math; when nothing else is priced the comparison falls back to them and the finding reports itself as estimated instead of disappearing.		2026-08-18 02:26:57 -07:00
..
indigo.css	app,dash: render pre-history days as no data, not a currency zero (#765)	2026-07-20 08:03:24 -07:00
plain.css	optimize: classify findings as fix/nudge/keep and mark measured vs estimated	2026-08-18 02:26:57 -07:00