tier-check spec-tracking does not detect SDK releases published shortly before the spec release

tier-check's spec-tracking check (src/tier-check/checks/spec-tracking.ts) looks for the first SDK release published at or after the latest spec release. An SDK release published shortly before the spec release is tagged is not detected as the release for that spec, so the SDK reads as "no release yet" and the check turns fail (a Tier 1 blocker) 30 days after the spec release unless the SDK happens to publish again.

Example: the 2026-07-28 spec release was published at 16:47Z; python-sdk v2.0.0 went out at 13:41Z the same day (three hours earlier), so tier-check --repo modelcontextprotocol/python-sdk currently reports a growing "Nd gap" and will report fail from 2026-08-28. go-sdk v1.7.0 (13:09Z) and typescript-sdk's 2.0.0 packages (published the evening before) are in the same position; csharp-sdk v2.0.0 (21:27Z, after the tag) is detected fine.

Start in src/tier-check/checks/spec-tracking.ts and run tier-check --repo modelcontextprotocol/python-sdk to observe the current gap. Update the check so the SDK release published shortly before the latest spec release is detected, then verify that the example release no longer produces a growing gap or a Tier 1 failure.