loobric-cli 1.1.1 — MCP field-placement guidance

Fixed

• MCP: create_catalog_record now teaches field placement. Evidence from the first real-world agent session: spec fields sent at the top level (flute_count, hand_of_cut) were correctly rejected by the server's lane discipline, so the agent crammed the data into the name string. The tool description and input-schema example now document the nested geometry object, the canonical key names (flutes; extra geometry keys accepted), and that non-geometry manufacturer data (grade, coating, substrate, source URL, availability, alternate part numbers) belongs in the free-form client_data dict — stored, never discarded. The loobric://concepts resource gains the same guidance. No behavior change — the server accepted all of this all along; the agent just couldn't discover it.