[dylanjeffers]

What

Flips the track_rows code default to false. This turns the dense TrackRow UI (Trending, profile, search, collections, Library, dashboard on web and mobile) back to tiles in production.

Why

The rows went live on web prod today, and the Optimizely flag can't turn them off on its own. getFeatureEnabled returns (isFeatureEnabled(flag) || ...) ?? defaultVal, so when Optimizely says false the result is undefined, which then falls back to the code default. Only an Optimizely true ever overrides the default. With the default at true, the "remote kill switch" did nothing.

This needs both halves:

1. This PR (code default false)
2. The track_rows flag turned off in Optimizely production. It's currently serving on to 100% (datafile revision 3207). Until that's done, it overrides this default back to on.

After that, Optimizely true turns it back on, and this time the switch works both ways.

now_playing_comments has the same "default on, remote flag is the kill switch" comment and the same problem. That's left as is here.

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: bf46c33

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR