Fresh Gaia context stays unknown after four bounded HTTP502 failures

Can independent Gaia astrometric context be acquired for all four fixed fresh patches?

Four unfiltered 300-arcsecond Gaia DR3 cones with all29 astrometric fields and paired XML/FITS review, independent of the frozen WISE score or flag.

Fifteen cone/ID/null/unit/rounding controls pass. Four XML requests return HTTP502; failed-prefix reader independently reconstructs all centres, queries, URLs, raw hashes, byte/request budgets, terminal exit1 and every unknown state.

4GETs/1364bytes, four341-byte HTML proxy errors. No FITS requests or retries. All four contexts unknown; Gaia source count unmeasured, zero adopted counterparts/classes. Failure audit exits zero and seals60 bindings; full stage about0.11MiB.

Next: Acquire WISE coverage dates/errors for every fresh identity via Gator; register a separate bounded Gaia route before any epoch/motion/covariance/ambiguity association or reference validation.

Transport failure is not empty sky or a nonstellar label. Success-only paired input auditor is preserved but unrun; no Gaia inputs are adopted. Fresh96 flags,137 core unknowns and unmeasured precision/recall stay unchanged. No dust/youth/birth truth.