chore(classmap): re-verify 1030000 and 1030001 against stock clients - #18
Merged
Merged
Conversation
Both maps were checked on unpatched 1.3.0.277 and 1.3.1.234 clients with the verifier that reads @layer blocks: 33/36 and 32/36 leaves in the stock CSS, 23/36 observed live by stock class in each, with the key overlays applied. The maps are unchanged; META now binds them with verified_classmap_sha256.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Re-verified the two 1.3 keys on unpatched clients, with the fixed static verifier (refactor(scripts): port the classmap capture tooling to TypeScript cli#3973) and the overlay-aware CDP verifier (feat(scripts): verify a key's css-map overlay over CDP cli#3976).
The maps and overlays are unchanged. Both META files now bind the map with
verified_classmap_sha256, and both CDP runs recorded the overlay digest they applied.Required-path statuses, stale leaves and unverified leaves are unchanged. The earlier targeted probes of the modals and settings sections still apply, because the class and build are the same, and this deep run doesn't open those surfaces.
publish-key --replacenow keeps such statuses and says so in the notes.Each
VERIFICATION.mdleads with the new evidence and keeps its full earlier history under "Earlier verification".Tooling
publish-key --replacekeeps the replacedVERIFICATION.mdinstead of discarding it.publish-key --replacekeeps an earlierverified_cdporverified_targetedstatus for an unchanged class the new run didn't reach.Verification
pnpm checkpasses (60 tests). Both stock clients ran from scratch copies on port 9230, and no Spicetify apply or config change was involved.