SenrokaiandClaude Opus 5 29d3ddb6ef Say so when Gaia is missing, rather than as 68 000 unmatched stars ...

With the merge gate in place, a Gaia DR3 outage no longer ships a HYG-only
catalogue: the ETL skips the unreachable source, and validateMerge then fails
on the survivor count. That is the right outcome and the wrong message: "68 000
HYG stars found no Gaia counterpart" sends the reader looking at the merge.
Gaia contributing nothing is now checked first, by name.

Two comments said Gaia was best-effort, in data-refresh.yml and on the merge
in fetchStars. They now say what happens instead.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016jxMkwA2rbicdGxHosecYi

2026-09-11 18:41:09 +02:00

..

ci.yml

Refresh the catalogues on a schedule, and republish when they change

2026-08-17 14:05:42 +00:00

data-refresh.yml

Say so when Gaia is missing, rather than as 68 000 unmatched stars

2026-09-11 18:41:09 +02:00

junie-review.yml

Pin the reviewer, bound its run, and wake it when a pull request reopens

2026-08-20 17:59:15 +02:00

pages.yml

Refresh the catalogues on a schedule, and republish when they change

2026-08-17 14:05:42 +00:00