Update to Bits & Bolts Remote

{
  "name": "bits-and-bolts",
  "description": "Browse, inspect, and pick reusable CAD parts with Bits & Bolts Remote.",
  "included_files": [],
  "skill_md_contents": "---\nname: bits-and-bolts\ndescription: Browse, inspect, and pick reusable CAD parts with Bits & Bolts Remote.\n---\n\n# Bits & Bolts Remote\n\nUse the tools from this plugin's connected app.\n\nUse the Parts Library to browse CAD models and the registered file viewer to inspect them. Call `cad.pickFile` only when the user explicitly asks to pick, choose, or select a CAD file.\n\n## Inspect a part together\n\nKeep the conversation centered on the user's part and intended use. Open the library to find a component, or open a supplied CAD file. Viewer resources prefer the expanded view when the host supports it. Open one library surface: use `cad.tray` when the user asks for the side panel, otherwise `cad.library`; do not call both for the same request. Read the mounted viewer before changing its camera or display, and preserve the user's part, note, and geometry unless they ask to change them.\n\nTreat a selected surface point and its view as a concern to discuss, not a measurement. Report displayed dimensions as overall bounds. State when the source has no units and millimeters are assumed. Do not infer fit, tolerances, or manufacturing readiness from sample geometry.\n\nWhen the user asks to compare against other parts or drawings, use `cad.pickReferences` and read the returned resources that are available. When they ask to review requirements, use `cad.reviewForm` with the current catalog `partId` when known. Use accepted answers to discuss the requested tolerance and priority against the available evidence. A canceled form changes nothing; accepted answers are conversation input, not a saved review or manufacturing approval.\n\nKeep inspection notes and views attached to their originating conversation. Offer a separate discussion only when the user wants one. Link back to the same part when referring to it, and use file opening, saving, and export only when the host supports them. Exporting STL preserves mesh geometry, not a parametric feature history.\n"
}