Tidy your Chorus playlist library, one approved change at a time

**Objective:** Review the Chorus playlist library and recommend what to fix, then apply only the changes that are approved. Treat a playlist as stale if it has not been modified in `{stale-days}` days (default 180).

**Step 1: Read the library**

Call `chorus-get-playlists` with a generous `max-records`. For each playlist keep `name`, `playlist-id`, `owner-name`, `private`, `size`, `child-count`, `created-at` and `modified-at`. If `{owner-name}` was supplied, narrow with `owner-name.contains` and review only that person's playlists.

**Step 2: Classify**

Sort every playlist into the problems it has:

* **Empty** - `size` and `child-count` both zero. Created and never used.
* **Stale** - `modified-at` older than the staleness window and not empty.
* **Unexpectedly private** - `private` is true but the name suggests shared coaching material.
* **Badly named** - a name that will not tell a new joiner what is inside, such as a bare date, a person's initials, or test.
* **Ownerless in practice** - owned by someone who is not an active Chorus user. Check with `chorus-get-users` using `name.contains` on the `owner-name`, and note whether `active` is false.

A playlist can appear in more than one group.

**Step 3: Recommend**

For each problem playlist, propose one specific action: rename it to a stated new name, move it under a stated parent folder, mark it private or not, or leave it and archive the question to its owner. Never propose deleting anything, because no tool here can delete a playlist.

**Step 4: Confirm before writing**

Present the recommendations as a table: current name, owner, problem, proposed change. Ask which ones to apply and stop.

**Step 5: Apply**

Only for the approved rows, call `chorus-update-playlist` once each, with `playlist-id` and `record-id` both set to that playlist's `playlist-id`, and only the fields being changed among `name`, `description`, `private` and `parent`. The two id fields carry the same value and both are required; sending one without the other fails.

**Step 6: Report**

List what was changed, what was left alone, and anything that failed.

**Rules & Guidelines:**

* `chorus-update-playlist` is the only write tool permitted. Do not call `chorus-create-playlist`, `chorus-add-playlist-moment`, `chorus-add-moment`, `chorus-update-playlist-moment`, `chorus-update-moment`, `chorus-export-recordings` or `chorus-export-scorecards`.
* Do not change a playlist you were not explicitly approved to change, even if it looks worse than one that was.
* Do not flip `private` to false on anything holding customer conversation material without saying plainly in the recommendation that it widens who can see it.

**Validation:**

* If no playlists come back, report the library is empty and stop.
* If `{owner-name}` matches no playlist owner, say so and offer the owner names that do exist.