Re-prioritising to Medium during an Engineering Backlog triage. The silent-data-loss concern is real (orchestrator drops Wikidata statements it can't represent — e.g. Julian dates — without surfacing that to the caller), and the deliverable is concrete (emit a warning into the Z22 evaluation-result metadata, modulo the transform.js / Z22-construction refactor the description notes). But 10 months without movement says High wasn't actually driving action; Medium is the honest signal. Related Wikidata-fetch reliability cards for context when this is picked up: T379441 (now Medium — large entities tripping rate limits) and T407827 (Medium — too many statements exceeding orchestrator time limits). All three are different angles on Wikidata-fetch robustness; a person picking up this card should consider whether a shared metadata-warning channel can serve all three rather than building three separate paths.