Claude Agent 2 - Production Logging Lane

The AI photoshoot lane already has a real runtime: phones/iPads capture, `multicam-server` coordinates, Live Director runs Photoshoot Mode, stills can be uploaded, and a Convex production ledger already exists. The missing piece is not architecture. The missing piece is making the live shoot write its own history. Your job is to wire the live photoshoot path into the already-built Convex production backend so a session produces durable production memory: sessions, cameras, cuts, holds, still markers, and other creative events. You are not here to redesign the schema, build the training model, or rework transport. You are here to make the live shoot leave behind a coherent ledger. Owns runtime convergence, device registration truth, placement metadata, and final rebuild/redeploy validation. - hero-feed transport - mobile registry repair - placement metadata debugging - deployment reporting as the final source of truth Use the **existing Convex production ledger** as the source of truth for the photoshoot session. - `Start Shoot` creates or updates a `photoshoot_performance` production session - participating cameras are written into `productionCameras` - live direction writes meaningful events into `productionDirectorEvents` - still capture creates at least one production still record or event linkage - session completion closes out the production session