# V314 browser audit summary

Static/runtime:
- `node --check assets/nexprod/nexprod01-runtime-candidate.mjs`: PASS
- Browser/player load: PASS
- Finger release: BLOCKED

Right control:
- actual MCP palm gate: PASS
- index distance/penetration: 0.73 mm
- pinky distance/penetration: 0.49 mm

Left after cutting old target-palm authority:
- V314 actual MCP-only authority: applied
- actual MCP palm gate: FAIL
- wrongWay: false
- index penetration: 0
- pinky penetration: 0
- best candidate chooses index-first; index is now close to surface at 2.59 mm
- pinky remains too far out at 58.37 mm

Interpretation:
V314 successfully removes the stale/phantom point authority and prevents wrong-way/inside penetration from being promoted to finger release. The remaining left failure is no longer “old pointA/pointB says pass while actual palm penetrates”. It is now a real actual-MCP contact solve issue: once one actual palm point is locked, the second actual MCP+20mm palm point is still far from the lower-leg surface. The next step must be an actual-MCP-only second-palm wrist/forearm roll/meet solve, not any return to PalmIndexBase/PalmPinkyBase target authority.