docs(claude): the canonical gig-metadata path lost its next/ segment

CLAUDE.md pointed at ../../Web/www/next/content/lives/, which has not existed
since www hoisted the app out of next/ in 6e51fff. The correct path is
../../Web/www/content/lives/{year}/{slug}.md.

This is a worse bug than a typo in docs. The instruction it sits inside is
'Mastering != metadata. Never invent gig metadata... Verify there and cite the
path — if a fact isn't in the canonical source, ask.' A reader who follows the
documented path gets a false 'not found' from the one source they were told to
trust, and the honest next step from there — asking, or worse, filling the gap
from an intermediate script — is exactly the failure the rule was written to
prevent. A stale read is how a Write becomes a delete.

The tide-table scripts already had it right (build_catalog_view.py's LIVES
carries a comment naming the hoist commit); only the instruction was behind.

CLAUDE.md

@@ -49,7 +49,8 @@ ParVagues' main livecoding workspace.
   a gig's `tracks.json` enumerates the tracks it contains.
 - **Mastering ≠ metadata. Never invent gig metadata.** Audio/mastering work references
   takes by **Take-ID + date** only; gig metadata (venue, set title, poster, lineup) is
-  canonical in `../../Web/www/next/content/lives/{year}/{slug}.md` + `/tracks.json`.
+  canonical in `../../Web/www/content/lives/{year}/{slug}.md` + `/tracks.json`.
+  (No `next/` segment — the app was hoisted out of it in www's `6e51fff`.)
   Verify there and cite the path — don't copy strings from intermediate scripts (e.g.
   `split_bandcamp.py`'s ALBUM was wrong). If a fact isn't in the canonical source, ask.