{
  "agent": "incident.meteorologist@web-summit.dinis",
  "state": "23:58: red rain moved to 09:00-18:00 (IPMA CAP sent 21:23; open data lagged 2 h+); CAP feed added (cap.json, issue times: red wind 07:18:40, red rain 16:30:01); met.no second model in forecast.json second_models; analysis section 6",
  "last_wake": "2026-11-10T23:51Z",
  "jobs": [
    "J1 (tonight): the weather as JSON for the dashboard, in incidents/2026-11-10-storm-charles/data/weather/ with a README per file: IPMA warnings for Lisboa (every level change with the time IPMA issued it and the time read), communiqués, Lisbon station observations (hourly), LPPT TAF and METAR (gusts). Read Vicky's desk's watch.mjs and snapshots (desks/weather-vicky/, read-only) and do not duplicate it: go deeper (series, not snapshots).",
    "J2 (tonight): how far ahead could it be known? The first public sign of CHARLES (communiqué no. 1, 9 Nov 13:17), each warning's lead time to its start, and what the models said against what is observed from Wednesday 05:00. Facts, evidence, hypotheses labelled.",
    "J3 (Wednesday, hourly): observed against warned at the Lisbon stations and LPPT, for the Weather pane.",
    "J4 (20:03): Thursday matters now (Day 3 on, subject to IPMA): at each wake, Lisbon's warnings for Thursday and the model for Thursday morning (residual wind, rain, sea) at the top of changes.json; from Wed 05:00, observed against warned as J3."
  ],
  "done": [
    "J1: incidents/2026-11-10-storm-charles/data/weather/ (warnings with history, communiqués, 8 Lisbon stations as series, LPPT TAF issues and METARs with gusts, IPMA daily and hourly model, gusts-vs-forecast, changes log; README covers every file; tools/refresh.py)",
    "J2: analysis.md / analysis.json (labelled analysis): worst Wed 12:00-18:00, peak likely 15:00-19:00, over by 21:00; lead times: storm ~47 h (communiqué no. 1), red wind ~27.5 h (IPMA 08:31 Tue, via Lusa), red rain ~18.5 h"
  ],
  "next": [
    "at each wake: the first TAF covering Thursday (due ~23:00) and any IPMA communiqué no. 3 go to the top of changes.json",
    "from Wed 05:00: observed against warned (gusts_above_warned first)"
  ],
  "asks": [
    "Dinis: the incident moved to PrompTugal/PrompTugal__News__Storm-Charles (21:15 UTC). Attaching it to this session with push access (add_repo) was refused at 21:18 UTC by the session's permission check (auto mode). Please attach the repo to this session or allow add_repo for it; until then I cannot write to incidents/2026-11-10-storm-charles/data/weather/, and I have not repointed my hourly wake (trig_01Nvhaw7sWVeMrLvV5md8sBg). I keep the data refreshing locally and write nothing more to the frozen 2026-11-10-the-storm/ folder."
  ],
  "notes": [
    "the session reported regenerating its key after private-key fragments were echoed in its own output; check the published key is the new one and nothing private was committed (security.repos@ may verify)",
    "incident.meteorologist@: the IPMA warnings feed carries no issue time; level-change times are bracketed by reads or taken from press (labelled). One README covers all files in data/weather/ (the brief asked for a README).",
    "21:25: IPMA's hourly aggregate can change values without changing dataUpdate; refresh.py now compares values (hourly_runs keeps the replaced run).",
    "23:55: every weather file now carries next_read_utc (the next :22 refresh), at incident.conductor@'s request for the librarian's now.json."
  ],
  "updated": "2026-11-10T23:55:00Z",
  "by": "incident.meteorologist@web-summit.dinis",
  "key": {
    "fingerprint": "sha256:ecbf013bbf6722e7",
    "signing_fingerprint": "sha256:3ab23559749449e4",
    "in": "data/keys.json",
    "note": "the regenerated key; the first one (sha256:3ee9ed2fb5a277d3) was deleted from the session before any commit and was never published"
  },
  "hosts": {
    "api.ipma.pt": "ok",
    "www.ipma.pt": "ok",
    "aviationweather.gov": "ok",
    "away.iol.pt": "ok",
    "github.com (PrompTugal__News__Website, read-only)": "ok",
    "feeds.meteoalarm.org": "ok",
    "api.met.no": "ok",
    "api.open-meteo.com": "429 daily limit (provider rate limit, 23:50 UTC), not an environment refusal"
  }
}