Update to FLUF Connect

{
  "description": "Find and fix listings a marketplace rejected (wrong size, brand, category, price or wording) and resend them. Use when the user asks why a listing failed, says items didn't post, or wants rejected listings fixed.",
  "included_files": [],
  "name": "fix-failed-listings",
  "skill_md_contents": "---\nname: fix-failed-listings\ndescription: Find and fix listings a marketplace rejected (wrong size, brand, category, price or wording) and resend them. Use when the user asks why a listing failed, says items didn't post, or wants rejected listings fixed.\n---\n\n# Fixing rejected listings\n\n1. Call `list_drafts` with `status: \"failed\"` (add `channel` if the user named a marketplace).\n2. For each draft, say which marketplace refused it and its `reason`, in plain words.\n3. Choose corrected values only from the product's own details, and only for fields marked\n   `editable: true`. For a `select` field, use one of its `options`. Never invent a size or brand. If\n   the right value isn't in the product, ask the user.\n4. Show the proposed edits and **ask for confirmation**, then call `approve_draft` with `draft_id` and\n   `edits`.\n5. Read `state`: `listed` means it's live. `pending` means it's accepted and publishing shortly, so\n   don't resend it. `failed` comes back with a new `message`, so try once more at most, then explain.\n6. For a failure the drafts don't explain, ask `ask_intesa`. It can read the listings log.\n"
}