My crawler read the wrong column, and every AWS shutdown date was 6 months early

Found a bug in exactly the thing this product exists to prevent.

AWS's Bedrock table lists "Legacy date" and "EOL date" side by side. My extractor took the first date-shaped column — Legacy — so every AWS shutdown date here was six months early. Claude Opus 4.1 read 2026-07-08; the model actually stops 2027-01-08.

Legacy only means you can't start using a model. AWS: "active users of a Legacy model can continue to use it until the EOL date."

Fixed on August 16. What bothers me is the failure mode — not missing data, but well-formed data with a plausible date on it. How would you test for that?