Update to Wingspan

{
  "name": "connect",
  "description": "Check the Wingspan connection and report who it is signed in as. Run this after installing the plugin, after re-authorizing, or whenever the user explicitly wants to confirm ChatGPT is reading the correct Wingspan account.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 329
    }
  ],
  "skill_md_contents": "---\nname: connect\ndescription: Check the Wingspan connection and report who it is signed in as. Run this after installing the plugin, after re-authorizing, or whenever the user explicitly wants to confirm ChatGPT is reading the correct Wingspan account.\n---\n\n# Check the Wingspan connection\n\nCall `who_am_i`. It takes no arguments and performs a real authenticated read,\nso a successful answer proves the whole connection works end to end.\n\nThen report, in plain sentences:\n\n- **Connected as** — the person's email address, when the connection\n  identifies an individual. No name is returned. An authorization granted\n  through the browser identifies the company account rather than the\n  individual, and the person comes back unavailable; say that it identifies the\n  account, and do not present it as a problem.\n- **Reading as** — the account from `account` when present, otherwise the\n  matching entry in `accounts`. `actingAsAccountId` is always null here,\n  because `who_am_i` takes no `accountId`; ignore it.\n- **Accounts reachable** — the entries in `accounts`, by name, noting any that\n  sit under a parent account. Mention that a tool can be pointed at one of them\n  with its `accountId` if the user needs a different one. An empty `accounts`\n  list is legitimate, not a fault.\n\nThen say what the connection is for in one line: these tools read the\ncontractors this account pays, what it owes them, and their onboarding\npaperwork, and they can create contractor records and draft payments after\nshowing a preview. Paying, approving and anything requiring an extra identity\nchallenge stay in the Wingspan app.\n\n## If it fails\n\nFollow the `troubleshooting` skill. In short: an authentication\nfailure means re-authorizing through `/mcp`; no Wingspan tools at all means the\nserver is not connected, and that skill says how to tell the two apart.\n"
}