Update to Lucia

{
  "description": "Review a selected collection of legal documents against common questions, with one row per document and evidence-backed cells, coverage gaps and an Excel review table. Use for structured document review or due diligence across files.",
  "included_files": [
    {
      "relative_path": "references/colonne-italiane.md",
      "size_in_bytes": 1923
    },
    {
      "relative_path": "references/upstream/LICENSE",
      "size_in_bytes": 1061
    },
    {
      "relative_path": "references/upstream/PROVENANCE.json",
      "size_in_bytes": 1304
    },
    {
      "relative_path": "references/upstream/commercial-columns.yaml",
      "size_in_bytes": 4826
    },
    {
      "relative_path": "references/upstream/nda-columns.yaml",
      "size_in_bytes": 3344
    }
  ],
  "name": "revisione-documentale",
  "skill_md_contents": "---\nname: revisione-documentale\ndescription: Review a selected collection of legal documents against common questions, with one row per document and evidence-backed cells, coverage gaps and an Excel review table. Use for structured document review or due diligence across files.\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# Revisione documentale\n\nRead `../revisione-contratti/references/document-workflow.md` and\n`../revisione-contratti/references/prassi-italiana.md` before execution.\nAll helpers run on selected files; no upload to Mike, Dario, Mparanza or a separate\nmodel service. The host model performs the legal reading in the conversation.\n\nAgree the decision and select useful columns from the brief and the documents.\nUse `references/colonne-italiane.md` to select questions for Italian practice.\nChoose them semantically; remove irrelevant questions and add case-specific ones.\nRecord a different relationship, law or formation history in each affected document\ncell when reviewing a mixed portfolio. Upstream YAML snapshots are attribution and\nhistory, not the column definitions to execute. Never fill a missing contract value\nwith a speculative estimate; a requested calculation needs inputs and assumptions.\n\nCreate one source per document and keep amendments and annexes separately\nidentifiable. Explain relationships in the review rather than merging contradictory\ntexts. Process bounded batches, persist review progress and inspect every selected\ndocument. Read long documents in chunks; never silently clip to a character limit.\nTrack actual anchors read in `coverage`. An unreadable or unfinished row remains\nvisible and cannot become “not stated”.\n\nFor each cell separate extracted term, exact quotation, interpretation and action.\nDo not infer agreement-wide silence from a search miss. Read definitions, exceptions\nand applicable schedules before deciding what a term means. Reconcile apparent\ninconsistencies across documents; retain unresolved conflicts explicitly.\n\nRender the common evidence report and Excel table. Summarize exceptional terms,\nmissing information and decisions for the lawyer, without hiding unreviewed rows.\nThe output is a review workpaper, not completed due diligence or legal clearance.\nNo files are sent, filed or changed by this workflow.\n\nUpstream pin and licence: `references/upstream/PROVENANCE.json` and `LICENSE`.\n"
}