chore(data): assign venues to the 22 Vol-17 (lwbc17) performances — schedule/venue views are empty

[BreakableHoodie]

What

All 22 Vol-17 performances have no venue assigned (venue_id NULL → venue_count: 0). Until assigned, the by-venue schedule and venue displays for Vol-17 stay empty.

(This is also what surfaced the "Venue not found" save bug — fixed in #464, which makes venue optional so editing works in the meantime.)

Venue reconciliation — CONFIRMED by boss

Two renames, then assign. The canonical 6 Vol-17 venues are: Blue Room, Princess Cafe, Prohibition Warehouse, Revive Karaoke, Room 47, Roost.

id	current DB name	action
15	The Roost	rename → "Roost"
16	Revive Karaoke (Blue Room)	rename → "Blue Room" (distinct venue, a room within Revive Karaoke — both are real venues)
7	Revive Karaoke	keep as-is (its own venue)
8	Princess Cafe	keep as-is
6	Prohibition Warehouse	keep as-is
4	Room 47	keep as-is
17	Jane Bond	Vol-16 only — keep in DB for Vol-16 history, do NOT assign to Vol-17

Steps

1. Rename venue 15 → "Roost" and venue 16 → "Blue Room" (admin → Venues tab).
2. Assign each of the 22 Vol-17 performances to one of the 6 canonical venues — per-band in the admin Lineup tab, or faster via the bulk venue-assign tool (functions/api/admin/bands/bulk.js supports setting venue_id for a group).

Done when

All 22 Vol-17 performances have a venue (one of the 6), the two renames are applied, and the by-venue schedule renders for lwbc17.

[BreakableHoodie]

Code review feedback

Strengths: Stakeholder-confirmed venue mapping, clear rename table, explicit steps, good "Done when" statement.

Gaps / suggestions:

• No labels, no assignee, no priority. With the event 32 days away, this should be priority:p1 — empty venue views are a critical functional gap for attendees.
• A verification query would help the person doing the data entry confirm completion:

  SELECT COUNT(*) FROM performances p
  JOIN events e ON p.event_id = e.id
  WHERE e.slug = 'lwbc17' AND p.venue_id IS NULL;
  -- expected: 0

• No mention of whether this is a one-time admin task or needs a follow-up migration. If done through the UI only, a compensating SQL statement would make it reproducible in staging/dev.

[BreakableHoodie]

Verification against production D1 (2026-07-02): not closable yet.

Done-when criterion	Status
Rename venue 15 → "Roost"	✅ Applied (audit log 2026-07-01 21:13)
Rename venue 16 → "Blue Room"	✅ Renamed 2026-07-01 21:13 — note it became "Blue Room (Inside Revive Karaoke)" rather than the confirmed "Blue Room"; fine if intentional
All 22 Vol-17 performances assigned a venue	❌ 22 of 22 still have venue_id NULL

Verification query (expected 0, got 22):

SELECT COUNT(*) FROM performances p JOIN events e ON p.event_id = e.id
WHERE e.slug = 'lwbc17' AND p.venue_id IS NULL;

Also checked the audit log for failed venue-assignment attempts — none found (the three band.updated entries from 2026-07-01 list venueId in changedFields, but that array is the endpoint's full field list, not a diff; they were bio edits). So nothing was lost — the assignment step just hasn't happened yet, per-band in the Lineup tab or via the bulk venue-assign tool.

🤖 Claude Code