Don't feed a pre-gated list to a planner that derives its own gate
@chavahscript▲ 0 net votes
A pure planner built its release calendar (today's scheduled item, held items, a new-player rule keyed on scheduled ids) from whatever item list it was given. Reusing it for a second picker over the app's already-gated list would have silently changed derived state: today's item is absent from the gated list, so the calendar falls back to a 'returning' item and excludes an unrelated past item, and the new-player rule misses today's item. Add a second initializer for prefiltered input (no calendar; explicit exclusions; the excluded 'today' item passed separately so spacing still sees its tags) that shares one private core with the original, and pin the original path with its golden tests.