Update to sajn

{
  "description": "End-to-end workflow for creating a sajn document, getting its content in place, adding signing parties, and sending it for e-signature. Use when the user wants to create, prepare, or send a document, contract, or agreement for signing.",
  "included_files": [],
  "name": "create-and-send-for-signing",
  "skill_md_contents": "---\nname: create-and-send-for-signing\ndescription: End-to-end workflow for creating a sajn document, getting its content in place, adding signing parties, and sending it for e-signature. Use when the user wants to create, prepare, or send a document, contract, or agreement for signing.\n---\n\n# Create and send a document for signing\n\nsajn documents move draft → (optional approval) → sent → signed. This skill takes a request from \"I want X signed\" to a sent document.\n\n## Workflow\n\n1. **Pick the starting point.**\n   - An existing template (\"our standard NDA\"): `findTemplates`, then `createDocument` with `templateId`.\n   - A file the user has (PDF/Office): `createDocument` blank, then the file handoff in step 2.\n   - From scratch: `createDocument` blank, then compose with `addTextField` / `addFormField` / `addTable` / `addProductTable`.\n2. **File handoff.** You cannot receive file bytes and must never ask the user to paste a document's contents. Give the user the document link `createDocument` returns, ask them to drag the file onto it, and continue once they confirm.\n3. **Missing facts become form fields.** Names, dates, amounts, and terms the user has not given you become FORM subfields via `addFormField` — never placeholders like \"[NAME]\" in text. Fill sender-side values with `listFieldValues` → `setFieldValues`. Values assigned to a party are filled by that party at signing — read them, never set them.\n4. **Never write signature blocks.** No \"Signature\", \"Ort och datum\", or signature lines in text content — sajn renders signing automatically.\n5. **Parties.** `addParty` per signer. Before setting `requiredSignature` or `twoStepVerification` with `updateParty`, call `listSigningMethods` — eID availability varies per account; never assume.\n6. **Preflight.** `checkDocumentReadiness`; fix blockers, surface warnings to the user.\n7. **Send.** Confirm recipients and expiration with the user, then `sendDocument`. If the user lacks permission to send without approval, use `submitForApproval` with the approver emails instead.\n\n## Validation\n\nSuccess = `sendDocument` (or `submitForApproval`) succeeds and the document shows PENDING (or PENDING_APPROVAL). Always end by showing the document link.\n"
}