Did Russia vote against the 2022 leap-second resolution to push the deadline to 2040, and does GLONASS's use of leap-second-adjusted UTC explain the objection?

The source capture (claim-2022-cgpm-voted-to-end-leap-seconds-by-2035) carries a claim flagged [unverified-quant/mechanism — needs primary]: that Russia voted against CGPM Resolution 4 (2022) not on principle but to push the phase-out deadline to 2040, because GLONASS — unlike GPS — synchronizes to leap-second-adjusted UTC and would face an architecture change GPS never had to make. The capture sourced this only to secondary press (Daily Star, Data Center Dynamics), never checked against a primary record. It should not anchor a promoted claim until verified.

This bundles two separable verifications:

1. The vote and the 2040 figure. Do the 27th CGPM (2022) official proceedings or BIPM voting records show how individual member states voted, whether Russia dissented, and whether a 2040 (vs 2035) deadline was formally proposed? Named numbers and a specific national position are a quantitative + historical claim requiring Tier 1–2 — pull the CGPM meeting report / résumé des décisions, not journalism.

2. The GNSS mechanism. Confirm from a GNSS primary that GPS time is a continuous atomic scale carrying no leap seconds, while GLONASS runs on UTC(SU) and therefore applies leap seconds. Read the GPS Interface Specification (IS-GPS-200) and the GLONASS Interface Control Document, or ESA's Navipedia GNSS-timescale pages, for the exact statements. This mechanism is what makes the political motivation plausible; it is currently held only as hop-4 web-search synthesis with no captured URL or quote, so it too needs a primary before it can support its own claim-note.

Why it matters: if confirmed, this is the vault's cleanest example of metrology as geopolitics — a satellite-navigation architecture used as a bargaining chip in a vote over the definition of civil time. If the 2040/dissent detail turns out to be press embellishment, that is itself worth recording. Resolving part 2 would also unlock a standalone GPS-vs-GLONASS timescale claim-note.