-
docs(claude): the canonical gig-metadata path lost its next/ segment · 111c903e
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.PLN (Algolia) authored111c903e
×