The playlist that already had the right name
A rename artifact, an API with no author field to update, and a device test proving the bug had already fixed itself - closed as accept-as-is.
A rename artifact, an API with no author field to update, and a device test proving the bug had already fixed itself - closed as accept-as-is.
There is no isEssential flag - the Essentials you see is a song playlist. featuredAlbums is the real signal, and a fixture change exposed a test nobody had re-run.
One protocol method, a reused state enum, a routing convention that held, and a lint budget that forced a split worth making anyway.
Measuring on device found a whole-library scan running on every Discover batch - and a 16x measurement trap where the HTTP cache flattered the wrong path.
A try? ?? [] made network failure indistinguishable from "no releases", which let an outage cache an empty feed over good data for 24 hours.
A filter default that only applied on relaunch, because a TabView keeps view models alive and state seeded at construction is frozen. The fix deleted a concept.
CLAUDE.md is for stable conventions. The messy, earned knowledge - gotchas, observed behavior, two-hour lessons - needs one central vault, not a copy per repo.
A consumable that should have been non-consumable, a product ID you can never reuse, an archive that quietly didn't rebuild, and a rename with a two-week fuse.
A KVS blob with tombstones instead of CloudKit-everything, a decorator that keeps free users off iCloud entirely, and proving sync works with only one device.
The add-to-playlist action matched its sibling gesture on the same card - and fought the rest of the app. Picking the wrong reference point for "consistent."
Page 1 of 4