From c56bb91f716adc0af7c9e2dbc9109fd6043ce0cc Mon Sep 17 00:00:00 2001 From: Graham McIntire Date: Tue, 21 Apr 2026 16:13:03 -0500 Subject: [PATCH] chore(grid-rs): retrigger Rust CI after runner restart MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The forgejo-runner was offline when 989d310..410a137 landed, so the build-grid-rs workflow never dispatched for those pushes. Empty CI retrigger commits don't match the path filter. Touching the crate root forces build-grid-rs.yaml to fire and pick up the HRRR S3 fallback + scores_file .prop rename + point lookup fix. Also corrects the now-stale "f01..f18 forecast hours only" note — as of Phase 3 Stream A, Rust owns the f00 analysis step too. --- rust/prop_grid_rs/src/lib.rs | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/rust/prop_grid_rs/src/lib.rs b/rust/prop_grid_rs/src/lib.rs index a7b46cdf..501f6463 100644 --- a/rust/prop_grid_rs/src/lib.rs +++ b/rust/prop_grid_rs/src/lib.rs @@ -4,7 +4,8 @@ //! tests can compare behavior 1:1. Module boundaries chosen so failures //! during TDD fall into the smallest possible blast radius. //! -//! Port targets (f01..f18 forecast hours only — f00 remains in Elixir): +//! Post-Phase-3: f00 analysis and f01..f18 forecasts both live here. +//! Port targets: //! band_config ← lib/microwaveprop/propagation/band_config.ex //! region ← lib/microwaveprop/propagation/region.ex //! scorer ← lib/microwaveprop/propagation/scorer.ex