Set Token A first → Load scripts → pick a Script (characters auto-load). For Tier B, set Token A/C then load their published perfs.
Tier A — reservation logic no uploads
Tier B — publish flows needs published perfs
Paste already-published performance IDs above (make them via the recording client). Tier B needs perfs with READY shots covering the script's characters.
B5: run B1 first (draft scene, pubA anchor), then B5 → PASS with the anchor-removal 400. After B4 the scene is published, so DELETE hits the published-scene guard instead of the anchor guard.
Set ANCHOR_PERFORMANCE_ENABLED=false in content-service .env, restart it, then run:
Manual building blocks
Scene State —
No scene yet
Performances (isAnchor = materialized truth)
—
Note: anchorPerformanceId is the API's resolved anchor — the materialized isAnchor performance, falling back to the pending reservation while it's still recording. The raw internal reservedAnchorPerformanceId column isn't exposed; to inspect it directly, peek the DB.