Release 0.6.0

Author: Jamesllllllllll

AGENTS.md

@@ -7,6 +7,19 @@
 - Write UI copy in present tense.
 - If a beta or testing action is intentionally exposed in the UI, keep the copy short and action-oriented without internal implementation details.
 
+## Public Release Copy
+
+- Treat `CHANGELOG.md` as public end-user copy. It is shown inside the app, so write it for a broad audience.
+- Write changelog entries in plain language around visible improvements, new capabilities, and user-facing fixes.
+- Do not describe internal debugging, implementation mistakes, infrastructure failures, or engineering process details unless they matter directly to users.
+- Avoid technical internals such as SQL, database query behavior, CI, hooks, migration mechanics, deployment plumbing, or exact failure modes in public changelog entries.
+- If a change is mostly internal, summarize the user-facing benefit or omit it from the public changelog.
+
+## Catalog References
+
+- Do not use specific song titles, artist names, chart examples, or catalog contents as public examples in UI copy, documentation, or repo instructions unless the user explicitly asks for them.
+- Keep public-facing copy neutral about catalog contents and focus on product behavior instead of example entries.
+
 ## Runtime And Browser Checks
 
 - For this repo, assume the app is normally already running at `http://localhost:9000`.

CHANGELOG.md

@@ -2,6 +2,19 @@
 
 All notable changes to this project are documented here.
 
+## [0.6.0] - 2026-04-14
+
+### Added
+- Song search now keeps alternate chart versions together so requesters can choose a song without having to guess which chart is the right one.
+
+### Changed
+- Favoriting a song now applies across grouped versions, so saved favorites stay consistent wherever that song appears.
+- Search results, request handling, and playlist version selection now stay aligned around the same grouped-song view.
+
+### Fixed
+- Streamers and moderators now get a more complete version list when a song has alternate charts.
+- Admin tools are cleaner in production, while development-only review tools stay limited to development.
+
 ## [0.5.0] - 2026-04-13
 
 ### Added
@@ -15,38 +28,37 @@ All notable changes to this project are documented here.
 - Documentation now explains the current catalog grouping and charter preference behavior.
 
 ### Fixed
-- Full-text search falls back cleanly when D1 rejects oversized MATCH queries, and the UI now shows friendly error messages instead of raw SQL details.
+- Search failure handling is smoother, with clearer messages when a search cannot be completed.
 - Manual adds, viewer adds, and chart version switching now surface sibling chart versions more consistently in the playlist manager.
 
 ## [0.4.4] - 2026-04-12
 
 ### Changed
-- Local verification now catches formatting problems earlier, including JSON and translation files.
-
-### Fixed
-- Formatting mistakes now fail before CI instead of only showing up after a push.
+- Behind-the-scenes quality checks were tightened to keep updates more stable.
+
+### Fixed
+- Release preparation is more reliable.
 
 ## [0.4.3] - 2026-04-12
 
-### Changed
-- Release notes and contributor guidance now follow clearer versioning rules.
-
-### Fixed
-- Old local file path examples were removed from the repo history and test data.
+### Changed
+- Documentation was cleaned up and clarified.
+
+### Fixed
+- Examples and references were cleaned up for consistency.
 
 ## [0.4.2] - 2026-04-12
 
-### Changed
-- Release and deployment steps are clearer and more consistent.
-
-### Fixed
-- CI no longer builds the standalone Twitch panel package when it is not needed.
-- The unused dashboard panel preview route and preview copy were removed.
+### Changed
+- General release housekeeping and documentation were cleaned up.
+
+### Fixed
+- The dashboard no longer includes an unused panel preview page.
 
 ## [0.4.1] - 2026-04-12
 
-### Fixed
-- The Twitch panel CI build now uses the configured live app URL instead of a hardcoded domain.
+### Fixed
+- Twitch panel release configuration is more reliable.
 
 ## [0.4.0] - 2026-04-12
 

CONTRIBUTING.md

@@ -5,7 +5,7 @@
 1. Branch from `main`.
 
 Never commit directly to `main` and never push directly to `main`. If you start work while checked out on `main`, create a feature branch before staging, committing, or pushing. Do not bypass the repo hook that blocks commits on `main`.
-2. Install dependencies and bootstrap local data:
+2. Install dependencies and prepare the local app:
 
 ```bash
 npm install
@@ -94,6 +94,9 @@ Do not leave code that expects a schema change without a checked-in migration.
 - Keep [CHANGELOG.md](CHANGELOG.md), [package.json](package.json), and [package-lock.json](package-lock.json) aligned when preparing a release.
 - Update the version and changelog for every branch that merges into `main`.
 - Use a versioned changelog entry for shipped work. Do not keep an `Unreleased` section for merged changes.
+- Treat [CHANGELOG.md](CHANGELOG.md) as public release notes for a broad audience because it is shown in the app.
+- Write changelog entries around user-visible outcomes, not internal implementation details or engineering process notes.
+- Avoid internal-only language in changelog entries, such as SQL, database query behavior, CI, hooks, migrations, deployment plumbing, or exact failure modes.
 - Use `0.x.x` while the app is still pre-`1.0`.
 - Use a patch release for routine shipped work, fixes, docs, workflow updates, and cleanup.
 - Use a minor release when the shipped product scope expands materially.

README.md

@@ -36,7 +36,7 @@ The local app runs on:
 http://localhost:9000
 ```
 
-Use the bundled sample catalog for normal local development. For Twitch auth, EventSub, bot flows, or panel testing, fill in the Twitch-related values in [`.env.example`](.env.example) and follow [docs/local-development.md](docs/local-development.md).
+For Twitch auth, EventSub, bot flows, or panel testing, fill in the Twitch-related values in [`.env.example`](.env.example) and follow [docs/local-development.md](docs/local-development.md).
 
 ## Verification
 

docs/catalog-grouping-and-charter-preferences.md

@@ -10,7 +10,7 @@ When `grouped_project_id` is present on catalog rows, the app treats those chart
 - song-group blacklists
 - channel-scoped version handling in requests and management tools
 
-Some catalog rows are not grouped upstream even though they are effectively alternate charts of the same song. In that case, RockList.Live uses a fallback grouping rule when it builds the version list for a playlist item:
+Some catalog rows are not grouped upstream even though they are effectively alternate charts of the same song. In that case, RockList.Live uses a fallback grouping rule across grouped search results, request handling, and playlist version lists:
 
 - same title
 - same normalized artist name
@@ -21,9 +21,9 @@ Artist normalization is intentionally conservative. It currently:
 - lowercases the name
 - strips a leading `The `
 
-That fallback is used when a viewer or manager adds a song and the app needs to preserve alternate chart versions on the resulting playlist item. It helps cases like `The Smashing Pumpkins` and `Smashing Pumpkins` when the upstream catalog does not provide a shared `grouped_project_id`.
+That fallback keeps requester and streamer views aligned even when the upstream catalog does not provide a shared `grouped_project_id`.
 
-Search results still render chart-level rows. The app does not persist a separate internal canonical grouping table yet, so fallback grouping is computed at request and add time rather than stored as new catalog metadata.
+The app does not persist a separate internal canonical grouping table yet, so fallback grouping is computed from the catalog data rather than stored as new catalog metadata.
 
 ## Preferred Charters
 
@@ -47,4 +47,4 @@ Today, the app uses two layers:
 1. upstream catalog grouping from CustomsForge when it exists
 2. request-time fallback grouping for same-title and normalized-artist matches when upstream grouping is missing
 
-That gives the streamer a fuller version list when requests are added, while keeping search and moderation behavior predictable.
+That keeps search results, request handling, and playlist version selection consistent while preserving a fuller version list for streamers and moderators.

docs/deployment-workflow.md

@@ -101,7 +101,7 @@ echo "<SENTRY_DSN>" | npx wrangler secret put SENTRY_DSN --config wrangler.aux.j
 
 ## Remote Database Setup
 
-Initialize the remote D1 database and the bundled sample catalog:
+Initialize the remote D1 database:
 
 ```bash
 npm run db:bootstrap:remote

docs/local-development.md

@@ -49,13 +49,13 @@ Add these when you test Twitch auth, EventSub, bot flows, or the panel:
 
 Use `VITE_ALLOWED_HOSTS` when you need extra local hostnames, and `VITE_TWITCH_EXTENSION_API_BASE_URL` when the standalone panel build needs a different app origin.
 
-4. Bootstrap the local D1 database:
+4. Bootstrap the app database:
 
 ```bash
 npm run db:bootstrap:local
 ```
 
-That resets local D1, applies migrations, and seeds the bundled sample catalog.
+That resets D1, applies migrations, and prepares the app database.
 
 5. Start the app:
 
@@ -82,15 +82,15 @@ For this repo, treat `http://localhost:9000` as the default existing dev app. Be
 
 Use `npm run db:migrate` for normal local schema updates.
 
-Use `npm run db:bootstrap:local` only when you intentionally want to reset local data back to the bundled sample catalog.
+Use `npm run db:bootstrap:local` only when you intentionally want to reset the app database.
 
-## What Works With The Sample Catalog
+## What Works Locally
 
 - home page and channel pages
 - search and filters
 - settings and moderation UI
 - playlist management flows
-- Twitch panel UI against local data
+- Twitch panel UI
 
 Twitch sign-in, EventSub, bot replies, and hosted Twitch panel testing need valid Twitch credentials.
 

package-lock.json

@@ -2,7 +2,7 @@
   "name": "request-bot",
   "private": true,
   "type": "module",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "engines": {
     "node": ">=22"
   },

package.json

@@ -90,7 +90,7 @@ export function AdminDesignSystemReference() {
                 <Label htmlFor="design-preview-search">Search field</Label>
                 <Input
                   id="design-preview-search"
-                  defaultValue="Smashing Pumpkins"
+                  defaultValue="Example Artist"
                 />
               </div>
               <div className="grid gap-2">
@@ -127,9 +127,9 @@ export function AdminDesignSystemReference() {
             </div>
             <div className="grid grid-cols-[minmax(0,2.1fr)_minmax(0,1.4fr)_minmax(0,1.2fr)_minmax(0,1fr)_72px] gap-4 bg-(--panel-strong) px-4 py-4">
               <div>
-                <p className="font-semibold text-(--text)">Cherub Rock</p>
+                <p className="font-semibold text-(--text)">Sample Song One</p>
                 <p className="mt-1 text-sm text-(--brand-deep)">
-                  Smashing Pumpkins
+                  Example Artist
                 </p>
               </div>
               <div>
@@ -155,9 +155,9 @@ export function AdminDesignSystemReference() {
             </div>
             <div className="grid grid-cols-[minmax(0,2.1fr)_minmax(0,1.4fr)_minmax(0,1.2fr)_minmax(0,1fr)_72px] gap-4 bg-(--panel-soft) px-4 py-4">
               <div>
-                <p className="font-semibold text-(--text)">Mayonaise</p>
+                <p className="font-semibold text-(--text)">Sample Song Two</p>
                 <p className="mt-1 text-sm text-(--brand-deep)">
-                  Smashing Pumpkins
+                  Example Artist
                 </p>
               </div>
               <div>