Add per-user playlist routing preferences to replace env-driven defaults #2
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.
Per-user playlist routing should not depend on shared
.envdefaults; users must choose their default, uncertain playlist, and similarity threshold from the dashboard.Data model & defaults
default_playlist,uncertain_playlist,similarity_threshold) with migration; new users seeded from env defaults if present.API behavior
/addnow resolves target playlists using user preferences first, with env fallbacks normalized; guards missing playlists early.Dashboard UI & persistence
.envreliance.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.