feat(classmap): 1020094 verified classmap for Spotify 1.2.94

[afonsojramos]

What

1020094 for Spotify 1.2.94.583, captured on release day with the classmap pipeline (spicetify/cli#3896), chained from the verified 1020092 map.

Verification

• 27 of 28 good 1020092 leaves survived unchanged into 1.2.94 (identity migration).
• The only non-identity migrate hit was the known artist-artistDiscography-topBar false friend (already CDP-falsified during 1020092 work); reverted to stale.
• 20/36 leaves CDP-verified on a live stock 1.2.94.583 client with deep navigation, including all required paths (playbar, topbar, navbar, tracklist, context menu, search box/chips, sort box, settings header/section).
• settings.button.wrapper is present in 1.2.94 CSS but was not rendered during navigation; left unverified. 6 modal leaves unverified as before. 9 stale leaves flagged in META.json.
• Includes the css-map.json overlay (2 verified settings corrections), validated end to end: a dev CLI build applied with this overlay rewrote both hashes to semantic names, confirmed in the live DOM of the applied client.

This was the first exercise of the capture-on-release operating model: Spotify 1.2.94 shipped, the on-disk stock xpui was captured, migrated, CDP-verified, and published the same day.

[coderabbitai]

Warning

Review limit reached

@afonsojramos, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c5e341a0-0ba8-408f-826b-611056609e5f

📥 Commits

Reviewing files that changed from the base of the PR and between 3b305f0 and 9cadf75.

📒 Files selected for processing (6)

• 1020092/META.json
• 1020092/classmap-19f8522e902.json
• 1020092/css-map.json
• 1020094/META.json
• 1020094/classmap-19f856aefd5.json
• 1020094/css-map.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/classmap-1020094

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}