Update to Lucia

{
  "description": "Draft from a supplied editable legal template, preserving the original and returning an edited copy with a change register, factual basis and unresolved placeholders for lawyer review. Use when a template exists, not to invent a template or sign a document.",
  "included_files": [
    {
      "relative_path": "references/upstream/LICENSE",
      "size_in_bytes": 1061
    },
    {
      "relative_path": "references/upstream/PROVENANCE.json",
      "size_in_bytes": 1045
    },
    {
      "relative_path": "references/upstream/draft-from-template.md",
      "size_in_bytes": 1272
    }
  ],
  "name": "redazione-da-modello",
  "skill_md_contents": "---\nname: redazione-da-modello\ndescription: Draft from a supplied editable legal template, preserving the original and returning an edited copy with a change register, factual basis and unresolved placeholders for lawyer review. Use when a template exists, not to invent a template or sign a document.\n---\n<!-- MPARANZA_REPORTING_BEGIN -->\n## Task reporting and recovery\n\nFor every substantive user mandate, follow\n`skills/lucia/references/workflow-usage.md` from this installation's root.\nStart one primary task before preparation, using `usage/pipelines.json`; nested\nspecialists, retries and Studio Archive infrastructure reuse that task. Record\nonly the observed whole-task outcome. Discover `lucia_incident_host_link`,\nincluding deferred tools, and verify this run's Computer ID on the server.\nBuild the report input from actual phases even for chat-only drafts; missing\nclient files or a prepared input JSON do not waive reporting. Show the readable\nlocal model-data report under `skills/lucia/references/model-data-report-contract.md`, link its\nactual signed receipt, and ask once for the user's 1–5 stars after delivery.\nOnly user-authored feedback is submitted; tests remain explicitly marked.\nFollow `skills/lucia/references/incident-recovery.md` for automatic technical\nreporting, evidence requests and targeted remedies. Use the HTTPS browser recovery page in that reference if\nlocal execution is unavailable. Never ask the user to relay logs or repeat consent\nfor technical reporting. Recovery requires an observed successful retry of the\noriginal task and inputs, bound to the original report and current remedy.\nTutorials remain local-only and are excluded from task usage and ratings.\n<!-- MPARANZA_REPORTING_END -->\n\n\n# Redazione da modello\n\nRead `../revisione-contratti/references/document-workflow.md` and\n`../revisione-contratti/references/prassi-italiana.md`. The upstream snapshot is\nattribution/history. Use the supplied editable template;\nif none exists, request it. A PDF does not become an editable template merely\nbecause its text can be extracted. Never rebuild a DOCX from extracted text.\n\nEstablish the represented party, transaction, jurisdiction, required changes and\nsupporting facts. Preserve missing information as visible placeholders with an\nopen-questions list. Never invent identities, amounts, dates, authority or law.\nTreat example names and sample provisions in the template as examples, not facts.\nCheck Italian party identifiers, authority and communication details against the\nsupplied evidence. Separate business choices from legal changes. A firm template\nis not evidence that every clause suits this relationship; keep consumer issues,\nspecific approvals and special regimes visible. Do not insert a generic double\nsignature block as a cure for all issues. Do not silently change foreign governing\nlaw or translate common-law remedies into Italian remedies.\nRecord the shared Italian review context and the template/playbook version in\n`review.json`, even when only an edited copy and change register are requested.\nDeliver the context and open legal questions with the draft; exact replacements\ndo not verify their legal basis.\n\nPrepare the template and supporting files in one evidence pack. Read the original\nstructure, schedules and instructions. Create `changes.json` as exact replacements:\n\n```json\n[{\"anchor\":\"word/document.xml#p3\",\"old\":\"[CLIENT]\",\"new\":\"Example S.r.l.\",\"basis\":\"Client name confirmed in the user's instruction\"}]\n```\n\nFor DOCX read `../revisione-contratti/references/word-handoff.md` and use the\nhost's Documents/Word skill for authoring, native revisions/comments and rendering.\nUse tracked edits when showing adaptations for review; prepare a clean copy only\nwhen requested, with the same change register. The local Word bridge verifies\ninline edit results against the original and proposed changes. Do not rebuild a\nsecond Word editor inside Lucia or mistake a helper's success message for proof\nthat every change was applied.\n\nFor TXT/Markdown use `draft --template D001 --changes /absolute/changes.json`.\nThe older local DOCX replacement mode remains a bounded clean-text helper, not\nthe normal Word authoring route or a substitute for native revisions. If the host\ndocument capability is unavailable, return the proposed edits and identify the\nunfinished Word step. Do not silently replace the template's layout or file format.\n\nInspect the resulting file, render it when local rendering is available, and\nverify layout, numbering, definitions, cross-references, annexes and unresolved\nplaceholders. Compare the result with the original and match every intended edit\nto the change register. Do not call the output final or ready to sign; explain\nunverified formatting or facts. Deliver the edited copy, changes with factual\nbasis, open questions and the lawyer's review decisions. Never overwrite, sign,\nsend or file the original. The helper performs no model or network calls.\n\nMIT source and pin: `references/upstream/PROVENANCE.json` and `LICENSE`.\n"
}