Weather plugin for the live screen, fetched from its own repo - #797

Local weather, emitted on a websocket channel a skin can read at
/ws/v1/plugins/weather.reaplugin/weather. Ben asked for it on the live
screen's bottom-right corner: temperature now, and rain split by part of
the day.
WHY THE PLUGIN DOES THE ARITHMETIC. Open-Meteo's daily answer carries one
rain probability for the whole day, which is not the question anyone asks
standing at a machine. Its hourly answer carries a value per hour, so the
parts of the day are bucketed here, where the location's own timezone is
already known and where one implementation serves every skin.
THREE PERIODS, EMITTED FORWARD ONLY, the running one first: AM 06-12,
PM 12-18, NIGHT 18-06. Ben's call, 30 Aug 2026 - "a rolling window with
current on the left and next on the right" - so the strip never shows a
period that is over. The night bucket wraps midnight, which is why it is
a start hour and a length rather than a pair of bounds: at 02:00 the
running night began at 18:00 YESTERDAY, and all four windows are proven
against a synthetic forecast whose probability equals the hour.
Peak across a bucket, not mean: one 90% hour inside a quiet afternoon is
exactly what the reader wanted warning of, and an average buries it.
Rainfall is summed, because that is what "how much" means over hours.
A failed fetch does not erase the cached reading - it keeps being
published with its true age, and the skin decides when it is too old to
show. A widget that blanks on one lost request is worse than one that
says how old its number is.
Settings are declared in the manifest, so the Plugins page generates the
form: location, refresh minutes, units. No new UI in the app.
Registered in all three places a bundled plugin must appear - pubspec
assets, plugin_loader_service's bundled list, and the permissions guard
that every other bundled plugin already has.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Ben, 30 August 2026, on the skin's weather corner: "its missing MIN/MAX temps
to the right of the temp in the weather." The corner had the room — its head
turned sideways when the bottom rail shortened — but the plugin was not asking
for the numbers.
One parameter: `daily=temperature_2m_max,temperature_2m_min`, read at index 0.
`timezone=auto` is already on the request, so the daily arrays are the
LOCATION's days rather than the tablet's, which matters for a machine set to
one timezone and asking about another.
`dayAt` checks the type before the value. `Number(null)` is 0 and 0 degrees is
a real temperature, so a truthy test would send a missing high as a real zero —
the same trap this plugin already guards for the temperature and the weather
code. Absent is null, and the skin draws no range at all rather than a dash.
Verified against the machine: high 22.9, low 11.9 for Tarragindi, read back off
the plugin's own websocket after installing 1.1.0 on the tablet.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

The bundled copy was 1.0.0 and declared log, emit and pluginStorage. The
plugin fetches from Open-Meteo, so without `api` the request is refused and
it emits nothing — a plugin that installs, runs and silently never reports.
The permissions test did not catch it. It asserts `containsAll`, so a MISSING
permission passes as long as the listed ones are present, and `api` was not
listed. It is now, with a note saying why, so dropping it again fails the
build rather than the machine.
Version goes to 1.1.0, matching the daily high/low already in this lane.
Verified: flutter analyze clean, test/plugins 242 passed, dart format clean.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Vid's review of the bundling PR: "please fetch instead of bundle. fetch
allows updates from upstream github repo without a new Decaid release."
So the plugin now follows the same route as dye2, shot-upload and dcamp.
It is published from ChampionDesigns/decaid-weather-plugin as a release
ZIP, and scripts/fetch_weather_plugin.sh downloads a pinned tag, checks
the SHA-256, checks the manifest id, version, apiVersion and the four
permissions it needs, checks plugin.js has a createPlugin entry point,
and unpacks it into assets/plugins/. The generated directory is
gitignored, exactly like the other three.
The 584 lines of plugin source leave the Decaid tree. What stays is the
wiring: the pubspec asset entry, the plugin_loader_service bundled list,
and the permissions test - all unchanged, because from the app's side a
fetched plugin and a committed one are the same thing.
bundledPluginRepos gains the repo, so an installed copy keeps receiving
releases from it rather than being frozen at whatever Decaid shipped.
That is the whole point of the change: the plugin can now be updated
without a Decaid release.
The fetch is added to all fourteen plugin-fetch blocks across
develop-builds.yml, pr-checks.yml and release.yml.
Note for the reviewer: the source repo sits under ChampionDesigns
because that is where it was published. The script honours a WEATHER_REPO
override, so moving it to decentespresso is a one-line change if you
would rather own it.
Verified: fetch_weather_plugin.sh installs v1.1.0 clean, flutter analyze
reports no issues, and test/plugins/ passes 243 tests - including the new
provenance test and the permissions test, which reads the fetched
manifest.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>