Graham McIntire c56bb91f71 chore(grid-rs): retrigger Rust CI after runner restart ... 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.		2026-04-21 16:13:03 -05:00
..
src	chore(grid-rs): retrigger Rust CI after runner restart	2026-04-21 16:13:03 -05:00
tests	feat(grid-rs): Rust worker for HRRR f01..f18 propagation chain	2026-04-19 15:42:49 -05:00
.gitignore	feat(grid-rs): Rust worker for HRRR f01..f18 propagation chain	2026-04-19 15:42:49 -05:00
Cargo.lock	feat(rust): OTLP trace export to cluster OTel Collector	2026-04-20 11:59:49 -05:00
Cargo.toml	feat(rust): OTLP trace export to cluster OTel Collector	2026-04-20 11:59:49 -05:00
Dockerfile	fix(grid-rs): build wgrib2 in-tree instead of pulling from prop:latest	2026-04-20 08:33:53 -05:00