Update to Nexusplus

{
  "description": "Use when the user asks to sync, send or push their Nexusplus contacts to their phone, Outlook or iCloud, wants one of their contacts to go only to certain accounts (\"only to work\", \"just iCloud\"), asks where one of their contacts will go or why it is not showing up in a connected account, wants to publish several contacts at once, or asks whether a publish can be undone.",
  "included_files": [],
  "name": "publish-and-destinations",
  "skill_md_contents": "---\nname: publish-and-destinations\ndescription: Use when the user asks to sync, send or push their Nexusplus contacts to their phone, Outlook or iCloud, wants one of their contacts to go only to certain accounts (\"only to work\", \"just iCloud\"), asks where one of their contacts will go or why it is not showing up in a connected account, wants to publish several contacts at once, or asks whether a publish can be undone.\n---\n\nControls what leaves Nexusplus for the user's connected accounts, and which accounts it reaches.\n\nInput to expect: \"sync this to my phone\", \"only send her to my work account\", \"publish all of these\", \"why isn't he in Outlook\".\n\nSteps:\n\n1. `publish_contact` takes a contact's unpublished change live and sends it to the user's connected Outlook and iCloud accounts, overwriting the matching fields of the record already there. Edits and merges that are still unpublished stay inside Nexusplus until published. A contact with nothing pending is skipped (`nothing_to_publish`), which is not an error. Publishing needs admin access to the contact list.\n2. A send can also delete cards, and the user must hear that before it happens. When Nexusplus successfully sends a contact to a connected Outlook or iCloud account that holds more than one card linked to that contact (typically the absorbed contact's card after a merge), it then deletes the extra cards from that account after marking each as superseded, keeping any extra card it cannot read or that changed after it read it. This happens on any successful send, so a later scheduled sync can do it too, not only a publish. It never touches accounts the contact is not sent to, and excluding an account (step 6) does not delete anything there.\n3. By default a contact goes to every connected account that accepts new contacts, plus any account that already holds a record of it; with a destination setting, only to the accounts it allows. To answer \"where will it go\", read `destinations` (`designated`, `allowed`, `denied`) in `get_contact_dossier`. Call `list_integrations` for the connected accounts and their status.\n4. To route a contact, call `set_contact_destinations` with its `masterId` and the complete set. Each entry is a connected account's name as `list_integrations` shows it (not case-sensitive) or an alias: `work` (every Outlook work account), `personal` (Outlook Personal and iCloud), `all`, or `default` on its own to clear the destination setting. Every connected account you do not name is excluded. `create_contact` takes the same set of names as `destinations`.\n5. Never guess a name. An unknown name, a name that matches more than one account, or an alias that matches no connected account is refused, even when other names in the same call do match, and the refusal names the valid choices. Show them and ask. If no accounts are connected, say that.\n6. Setting destinations sends nothing; it takes effect at the next publish or scheduled sync. Read the allowed and excluded accounts back to the user. Excluding an account stops future updates to it and does not delete a record already sent there. Say so.\n7. Publishing rule (the same in every Nexusplus skill). Before any call that will publish, say what will be sent and to which accounts (`list_integrations` names them), and wait for a yes unless the user has already asked for this exact send (\"sync it to my phone\" is such a request). For more than a few contacts, say how many first. Above 25 in one call the tool requires `confirmCount` equal to the number of contacts; set it only to the number the user just approved, never to get past an error. `create_contact` and `submit_contact_revision` also publish by default unless the contact list is set to hold changes for review or you pass `disposition: stage_for_review`, so the same rule applies to them.\n8. Pass `reason` as one short sentence in the user's own words to either write tool. The publish is applied within a few seconds, so re-read `get_contact_dossier` and report what it shows.\n9. If a contact did not publish on its own, the usual reasons are that the contact list is set to hold changes for review, that the user's access does not allow publishing, or that an unresolved possible duplicate holds automatic publishing (`list_duplicate_candidates`). Say which apply, and suggest resolving a duplicate first with the duplicate-review skill.\n10. Undo: every earlier version stays in version history (`get_contact_versions`), so a wrong field or tag change is corrected by revising the contact again with `submit_contact_revision` and publishing again. An email, phone, address, role or web address that was added by mistake cannot be removed this way, because adding only ever appends: say that it cannot yet be removed through the assistant and has to be fixed in the Nexusplus app. There is no unpublish: a record already sent to an account stays there until it is changed, and a card Nexusplus deleted from an account (step 2) is not restored by version history.\n\nOutput: what was published or routed, to which accounts, and what has not yet left Nexusplus.\n\nStop and ask when the user has not said which accounts, when a destination name is refused, or before publishing more than a few contacts.\n"
}