Machine Pin Medium Standard

What happens

This page's main model, MachinePin*.glb at the repo root, is not the part. It's a demo scene: an FR4 square (18 × 18 mm for Large, smaller for Medium) with nodes fr4_board, barrel, pad_top, pad_bot, silk, solder_top, solder_bot, plus a generated PIN mesh. Any app or AI that loads the file named after the part (a robot-arm assembly simulator did on 2026-10-20) draws every pin with a fake gold board slab around it.

Only adom/machinepinlargeshort has the real part: machinepinlargeshort-mpn.step/.glb ("MachinePin_Large_Short_Gold v74" from Fusion, with the etched MPN), which its page.json step field points to. The other three pages' step points at the bare-named file.

Proposed definition (John asked us to define this)

For every machine pin, machine contact and needle page:

1. One canonical part model, named <slug>-part.step and <slug>-part.glb: the pin alone, real geometry matching the dimension chart in adom/machine-pins docs/dimensions.md (D1–D7, L1–L6), Fusion-sourced, with the MPN etched.
   • Origin on the axis at the seating plane: the underside of the shoulder, where the pin sits on the board.
   • +Z up out of the board, millimetres.
2. Light LODs beside it for simulators (<slug>-part-lod{1,2}.glb).
3. page.json step and model_3d_part point at the part model. Demo or hero scenes carry -hero-/-demo- in their names and are never the bare part name.
4. Molecule, aiflow and simulator skills load model_3d_part (or the step field), never a bare-named GLB.

Ask

Replace the bare-named GLB/STEP with the real part (or rename the demo to -demo-), and add the part models for the three pages that don't have one yet.