chore(classmap): re-verify four keys on stock Linux clients

[afonsojramos]

Summary

Spotify's Snap store still serves older Linux builds by revision. Flathub's manifest history maps each revision to a version:

Key	Build	Snap revision	In stock CSS	Observed live	Steps
1020084	1.2.84.475	93	33/36	30/36	10/10
1020092	1.2.92.147	97	32/36	25/36	10/10
1020095	1.2.95.453	99	33/36	29/36	10/10
1020096	1.2.96.518	101	33/36	30/36	10/10

• Each client ran unpatched in an Ubuntu 24.04 VM, with its own browser cache and the existing login.
• The deep CDP run came from feat(scripts): match CDP menu labels in any language and finish on slow clients cli#3978, with each key's overlay applied.
• All four keys now bind verified_classmap_sha256. Maps and overlays are unchanged, and the earlier history stays in each VERIFICATION.md.
• 1020084 and 1020092 record the Snap builds they were verified on (.475 and .147), one build number below the earlier .476 and .148. Same key.
• 1020092 was derived from 1020040, which chore(classmap): remove the pre-pipeline 1.2.38, 1.2.40 and 1.2.45 keys #19 removed, so its source.key is now null, with a note naming 1020040.
• Status changes: mostly upgrades. 1020092's legacy "verified, method unknown" statuses become verified_cdp, except search_chips.wrapper, which becomes verified_static. The dialogs and Settings paths move to verified_cdp on all four keys. On 1020096 the output-device Settings header was observed live: that section renders on Linux.
• Stale leaves: unchanged. They were passed back in explicitly.
• Tooling: publish-key --inherit-from now accepts --overlay. 1020096 inherits 1020094's map but keeps its own three-entry overlay, which a plain inherited publish would have replaced.

Verification

pnpm check passes (62 tests).