Drag instrumentation — render counters, hot-path signposts, and the invariants that prove the gates

BoardRenderMetrics (DEBUG-only, the pathfinder's counter bag plus a
strip-body discriminator that tells a failed gate from a direct
Observation invalidation) counted at BoardView/LaneView/CardFaceView/
TrashLaneView bodies and MasonryLayout's callbacks. DragSignposts wraps
dropUpdated, retargetCards, commitDrop, and the commit-to-covering-
snapshot release pause; input latency reports honestly against
NSApp.currentEvent's mach base or labels itself base=none — no event
timestamp rides the drop path. BoardRenderPerformanceTests hosts the
real BoardView off-screen: a value-equal reload runs zero lane and zero
card bodies, a one-card edit repaints one card of 180. The lane-body
budget is <= laneCount with the headerInk chain documented and a
two-way tripwire that fails when the fix lands. Methodology in
RENDER-INSTRUMENTATION.md. Release build proves it all compiles out.

Drag-perf card a450ad09.

Claude-Session: https://claude.ai/code/session_01CqjXB7ASoWtbyoGod68k97

Kanban/UI/Board/CardFaceView.swift

@@ -198,6 +198,11 @@ struct CardFaceView: View, Equatable {
     /// gestures that fire and refuse (`CardFaceRole`).
     @ViewBuilder
     var body: some View {
+        // The lane's gate, observed (`BoardRenderMetrics`) — DEBUG only, and a `let _` because a
+        // `@ViewBuilder` body takes statements as views and a bare call would be one.
+        #if DEBUG
+        let _ = BoardRenderMetrics.countCardBody()
+        #endif
         switch role {
         case let .board(openCard):
             face