Analysis: one selected period, one set of numbers, on every page

The dashboards told several stories at once. Overview asked for full
calendar years, meter detail for a fixed 12-month window that was really
13, Trends for 24 months with an Apply button, and the energy pages for
60. Each page derived "today" from UTC, so the first hours of a local day
belonged to yesterday. A missing tariff, a month nobody measured and a
genuine zero all rendered as 0. And a virtual meter -- the one thing the
spreadsheet leans on hardest -- was excluded from analysis outright:
MeterPeriodService returned null for it and the page offered a flow
diagram instead.

docs/DASHBOARD_ANALYSIS_CHANGE_BRIEF.md is the work order. Every choice it
left open is settled in docs/ANALYSIS_IMPLEMENTATION_NOTE.md as D-01..D-58
plus amendments A-01..A-30; code, tests and release notes cite those ids.

The analysis layer

Core/Analysis holds the pure rules: period presets resolved once in the
instance zone into a local date range and a half-open UTC range, bucket
plans, calendar-unit comparisons, coverage runs with a resolution class,
normalized quantities and units, the totals policy, the virtual formula
parser/validator/evaluator, and the cost calculator. "Now" comes from
TimeProvider; services never read the clock.

Normalization now writes, in the same transaction as consumption and by
diff, per-meter rollups by local day and month plus coverage runs and a
rollup state (AnalysisDataWriter). AnalysisReader answers a request from
those tables -- month rollups for month and year buckets, day rollups
otherwise, at most two partial edge days from consumption -- and
CostReader prices the result month by month. Pages, /api/v1 and the CSV
export read nothing else. The unused continuous aggregates are dropped.

The reader's statement count per request is constant whether it covers one
meter or a thousand. On a synthetic 1,000-meter, ten-year instance the
brief's target request (100 meters, ten years, monthly) takes 374 ms
against a two-second target, and the Overview went from 48,244 SQL
statements per load to 205.

Missing is not zero

Every bucket carries a status -- available, partial, missing, unresolved,
invalid, pending -- derived from coverage, never from the amount, with
provenance and a reason code beside it. A true zero is a number and a bar
on the baseline; an unknown bucket is a gap that says why; a month whose
data only exists monthly says so instead of inventing daily detail; a
scope with no tariff says "not priced" instead of 0. Rows whose interval
closes after now are reported separately rather than counted.

Virtual meters are analysis subjects

A virtual meter stores a canonical definition -- expression over m<id>
references, result kind, unit and cost rule -- validated on save and on
read for syntax, unknown or self references, loops and unit/kind rules.
It is evaluated on read from its sources' rollups over their joint
coverage: a missing source makes the bucket missing, an observed zero is
a valid input, a non-finite result is invalid with its dependency path,
and the page lists each source's contribution. Topology links are
topology only and never rewrite a saved calculation; expression-less
meters from older installs are converted once at startup. The editor has
Sum, Difference and Advanced modes with a live preview.

Totals and the bill

Per energy type the totals policy separates use, grid import, export,
generation and runtime, marks breakdown meters as breakdowns and virtual
meters as views, and never adds across units. The bill follows it: grid
import where there is one, separately priced subsections at their own
price, feed-in only on export meters, standing charges once per scope per
local day, manual costs once on their start day, categories as
non-overlapping covers whose composition reconciles to the bill. The
seeded demo's yearly totals now match the spreadsheet.

Pages and navigation

The period lives in the URL and every page reads the same contract, so a
link, a reload and the browser's Back button keep it. Shared components
carry it: page header with breadcrumbs, period toolbar, theme-aware chart
with an accessible table beside it, metric cards, comparison and
availability states, attention items that each link to the one action
that fixes them. Meter detail leads with an Analysis tab and resolves its
tabs by key; the energy page has Overview, History, Flow and Meters; the
old cost-only Trends page is a general Analysis page over portfolio, type,
category, meter or a meter comparison. Records tabs are paged server-side
instead of showing the latest 200. Everything is English and German,
light and dark, down to 360px.

Some figures change on purpose; docs/RELEASE_NOTES.md lists each one and
what the first start after the update does (it rebuilds all analysis data
before the web server listens). docs/SDD.md and CLAUDE.md describe the
system as it now is.

Tests: 1,733 Core and 746 integration, all green, plus an opt-in
performance suite with a synthetic 1,000-meter generator.

tests/Core.Tests/Analysis/TotalsSeed.cs

@@ -0,0 +1,105 @@
+using MeterVault.Core.Analysis;
+using MeterVault.Core.Analysis.Quantities;
+using MeterVault.Core.Analysis.Totals;
+using MeterVault.Core.Domain;
+
+namespace MeterVault.Core.Tests.Analysis;
+
+/// <summary>
+/// The reference data's topology as the totals policy sees it (ReferenceDataImporter): five electricity meters
+/// and the Summe Solar view, the water meter, and the oil tank with its burner. Ids follow the seed's creation
+/// order; the energy types are electricity 1, water 2, heating oil 3.
+/// </summary>
+/// <remarks>
+/// Roles are given as the stored tokens and turned into <see cref="TotalsMeter.Role"/> through
+/// <see cref="MeterRoleRules.Effective(MeterMode, string?)"/>, exactly as the reader does (A-07) — so a test that stores
+/// "GRID_IMPORT" or a role on a tank sees what production would.
+/// </remarks>
+internal static class TotalsSeed
+{
+    public const int Electricity = 1;
+    public const int Water = 2;
+    public const int Oil = 3;
+
+    public const int Haus = 1;
+    public const int Netz = 2;
+    public const int Auto = 3;
+    public const int Solar1 = 4;
+    public const int Solar2 = 5;
+    public const int Wasser = 6;
+    public const int Oeltank = 7;
+    public const int Brenner = 8;
+    public const int SummeSolar = 9;
+
+    /// <summary>Solar 1 → Summe, Solar 2 → Summe, Netz → Haus, Summe → Haus, Haus → Auto.</summary>
+    public static List<TotalsLink> Links() =>
+    [
+        new(Solar1, SummeSolar),
+        new(Solar2, SummeSolar),
+        new(Netz, Haus),
+        new(SummeSolar, Haus),
+        new(Haus, Auto),
+    ];
+
+    public static List<TotalsMeter> Meters() =>
+    [
+        Physical(Haus, "Zähler Haus", Electricity, MeterMode.CumulativeCounter, "kWh", MeterRoles.TotalLoad),
+        Physical(Netz, "Zähler Netz", Electricity, MeterMode.CumulativeCounter, "kWh", MeterRoles.GridImport),
+        Physical(Auto, "Zähler Auto", Electricity, MeterMode.CumulativeCounter, "kWh"),
+        Physical(Solar1, "Zähler Solar 1", Electricity, MeterMode.GenerationCounter, "kWh"),
+        Physical(Solar2, "Zähler Solar 2", Electricity, MeterMode.GenerationCounter, "kWh"),
+        Physical(Wasser, "Zähler Wasser", Water, MeterMode.CumulativeCounter, "m³"),
+        Physical(Oeltank, "Öltank", Oil, MeterMode.ConsumableBalance, "L"),
+        Physical(Brenner, "Brenner", Oil, MeterMode.RuntimeCounter, "h"),
+        Virtual(SummeSolar, "Summe Solar", Electricity, "kWh", QuantityKind.Generation, [Solar1, Solar2], pureSum: true),
+    ];
+
+    /// <summary>The seed with <paramref name="adjust"/> applied to the meter <paramref name="id"/>.</summary>
+    public static List<TotalsMeter> MetersWith(int id, Func<TotalsMeter, TotalsMeter> adjust) =>
+        [.. Meters().Select(m => m.Id == id ? adjust(m) : m)];
+
+    public static List<TotalsMeter> MetersWithOverride(params (int Id, TotalsOverride Override)[] overrides) =>
+        [.. Meters().Select(m => overrides.Any(o => o.Id == m.Id) ? m with { Override = overrides.First(o => o.Id == m.Id).Override } : m)];
+
+    /// <param name="role">The stored role token; the meter gets the effective role, as the reader gives it.</param>
+    public static TotalsMeter Physical(
+        int id,
+        string name,
+        int energyTypeId,
+        MeterMode mode,
+        string unit,
+        string? role = null,
+        TotalsOverride totals = TotalsOverride.Auto,
+        QuantityKind? kind = null,
+        DateOnly? installedAt = null,
+        DateOnly? retiredAt = null)
+    {
+        var effective = MeterRoleRules.Effective(mode, role);
+        return new(id, name, energyTypeId, mode, effective, kind ?? KindOf(mode, effective), unit, false, totals, installedAt, retiredAt,
+            [], false, null);
+    }
+
+    /// <param name="resultKind">The declared result kind; null for a definition that is not usable.</param>
+    /// <param name="role">A stored role token. A virtual meter never holds one (A-07), so it always reads as none.</param>
+    public static TotalsMeter Virtual(
+        int id,
+        string name,
+        int energyTypeId,
+        string unit,
+        QuantityKind? resultKind,
+        IReadOnlyList<int> sources,
+        bool pureSum,
+        string? role = null,
+        TotalsOverride totals = TotalsOverride.Auto) =>
+        new(id, name, energyTypeId, MeterMode.Virtual, MeterRoleRules.Effective(MeterMode.Virtual, role),
+            resultKind ?? QuantityKind.Consumption, unit, true, totals, null, null, sources, pureSum, resultKind);
+
+    // Mirrors NormalizedQuantity: an effective grid_export role makes a flow meter measure export.
+    private static QuantityKind KindOf(MeterMode mode, MeterRole? role) => mode switch
+    {
+        MeterMode.GenerationCounter => QuantityKind.Generation,
+        MeterMode.RuntimeCounter => QuantityKind.Runtime,
+        _ when role == MeterRole.GridExport => QuantityKind.Export,
+        _ => QuantityKind.Consumption,
+    };
+}