Update to LeftLane

{
  "name": "add-dealership-note",
  "description": "Add one confirmed private note to an exact LeftLane vehicle, customer deal, or deal finance account with CreateComment. Use when a user asks to record, add, attach, or save a dealership note or comment.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 180
    }
  ],
  "skill_md_contents": "---\nname: add-dealership-note\ndescription: Add one confirmed private note to an exact LeftLane vehicle, customer deal, or deal finance account with CreateComment. Use when a user asks to record, add, attach, or save a dealership note or comment.\n---\n\n# Add Dealership Note\n\nTreat `CreateComment` as a non-idempotent write. Follow this sequence exactly:\n\n1. Discover the target with a read tool before preparing the write, even when the user supplies an id. Use `ActiveVehicles` for a vehicle, `CustomerDeal` for a customer deal, or `DealFinanceAccounts` for a finance account.\n2. Resolve exactly one returned record and retain its integer id. If the read returns no match or multiple plausible matches, do not prepare the write; refine the search or ask the user to choose.\n3. Obtain the complete note body. Do not silently rewrite material facts; show any cleanup to the user.\n4. Display the target type, target id, identifying facts from the discovery result, and exact note body. Ask for explicit confirmation to create that one comment.\n5. Call `CreateComment` exactly once only after the user confirms the displayed target and body.\n6. Report the returned comment id, timestamp, and target relationship.\n\nNever call the tool when discovery, an exact target, the body, or confirmation is missing. Never guess between multiple targets. If the response is ambiguous, times out, or fails after dispatch, do not retry automatically because a retry can create a duplicate note; inspect state or ask the user how to proceed.\n"
}