Completes milestone 3: frames render over the map, play as a loop, and can be
scrubbed, with the legend drawn from the manifest rather than a constant that
could drift from what the worker actually rendered.
The overlay alternates two MapLibre image sources. Updating one source in place
flickers, because the layer briefly shows a half-written texture; adding every
frame as its own layer avoids that but pins them all in GPU memory, and twenty
512x512 RGBA frames is about 80 MB. Two buffers cost the same whether the
timeline holds six frames or sixty. Platform-channel work is serialised because
`show` is called faster than the round trip completes during playback, and
overlapping updates would swap visibility out of order and strobe.
Prefetching loads a window around the playhead, nearest first and forward
before backward, since playback moves forward and that frame is needed
soonest. `FrameCache` is byte-budgeted rather than entry-counted because frame
size tracks how much precipitation is on screen, and it evicts by distance from
the playhead: plain LRU would keep frames the prefetcher touched a moment ago
even after the playhead moved to the far end of the timeline.
Also adds DpcRadarSource, which reads published frames from our CDN and never
from the DPC API. Without it, the `dpc` adapter would have had to fall back to
mock, putting demo frames on screen under the label of live data — exactly the
confusion the adapter split exists to prevent. It now fails naming the missing
setting instead.
Running it on the emulator caught three things the tests had not:
- The notifier wrote to `state` from inside `build()`, which Riverpod rejects
as an uninitialised provider. That broke startup, not just tests.
- Eight-month-old demo frames rendered as "Aggiornato 342535 minuti fa". The
age formatter now steps up to hours and days.
- Demo mode sat permanently behind a stale-data warning and so never showed the
working state it exists to demonstrate. MockRadarSource now shifts the
bundled timestamps onto the present, leaving images, order and spacing
untouched, so the timeline behaves exactly as it would on live data.
Corrects docs/stack-decisions.md, which described a disk cache that was not
built: mock frames already live in the asset bundle, so a disk layer belongs
with the network adapter where it would save a real request.
Verified: analyze clean, 129 tests passing, and on the emulator the loop
advances, wraps, and reports "Aggiornato ora".
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sets up the Nuvolari monorepo layout (app/, backend/, docs/, tool/) with the
groundwork that does not depend on the Flutter toolchain: gitignore covering
Flutter, Python and every secret file shape; env.example.json as the template
for --dart-define-from-file; a verification script that skips stages whose
target does not exist yet so it is runnable from day one; and a CI workflow in
GitHub Actions syntax so it runs unchanged on Gitea or GitHub.
The documentation records facts verified against the live services rather than
restated from the brief. Two of them change the design:
- DPC VMI rasters are 1200x1400 Float32 on a 1 km grid in a custom projection
centred on Italy, not EPSG:4326 or EPSG:3857, and their GeoKeys are
internally inconsistent. Reprojection is mandatory and the source CRS must be
read from each file rather than hardcoded.
- The ARPA CAP feed carries six level values, not four: BIANCO for the
avalanche scale out of season and "-" for no data. Collapsing either into
VERDE would report "no alert" where the bulletin reports "not assessed".
Also documents why the frames we publish inherit CC BY-SA from the DPC source,
and why rain notifications subscribe to cell topics from the device so no user
location ever reaches a server.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Alby96andClaude Opus 5