Update to Lucia

{
  "description": "Use when Lucia must open a new client matter or a new matter for an existing client, organize intake evidence, map parties, prepare conflict-search candidates, define engagement scope, surface possible deadlines, assess conditional AML posture, propose a folder plan, and create a lawyer-reviewable opening package.",
  "included_files": [],
  "name": "apertura-pratica",
  "skill_md_contents": "---\nname: apertura-pratica\ndescription: Use when Lucia must open a new client matter or a new matter for an existing client, organize intake evidence, map parties, prepare conflict-search candidates, define engagement scope, surface possible deadlines, assess conditional AML posture, propose a folder plan, and create a lawyer-reviewable opening package.\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<!-- LUCIA_OPENAI_ONBOARDING_BEGIN -->\nOnboarding is optional. Continue ordinary professional work immediately,\nincluding direct specialist invocation, without checking or completing a local\nonboarding profile. Missing, unfinished, inaccessible or corrupt onboarding state,\nor unavailable voice/window controls, must never block ordinary work. Do not\nautomatically start, resume or repeatedly offer onboarding.\nOnly for a user-requested tutorial or a native teaching handoff, read\n`../lucia/references/local-onboarding.md`. A verified paired lesson worker\nexecutes only its bound lesson and token; never bypass tutorial validation.\nTutorial profiles, progress, examples and feedback remain local; never send a\nchange request, stamp a tutorial receipt or call hosted interviews for a tutorial.\nCurrent user requests take precedence over saved preferences.\n<!-- LUCIA_OPENAI_ONBOARDING_END -->\n\n# Fascicolo nuova pratica\n\nAfter substantive use of this workflow, read and follow the `Plugin Improvement Feedback` section in `../lucia/SKILL.md`.\n\nResolve `../../modules/apertura-pratica` from this skill directory when it\nexists; otherwise resolve `../../../apertura-pratica` in the repository. Read\nthat module's `skills/apertura-pratica/SKILL.md` completely and follow it. Treat\nthe resolved module root as the plugin working directory for every command, schema,\nreference, script and review asset.\n\nThis is Lucia's native legal-matter-opening contract. It reuses Studio Archive\nonly for private client, engagement, input and run lifecycle. It does not use\nLegal/Tax Answer Review as its completion gate and does not inherit Vera's\naccounting intake semantics.\n\nBefore finalizing a durable Studio Archive run, follow that component's model-data\nreport contract for the actual model-context evidence and its limits. Build the\nreadable local report through Lucia's `scripts/workflow_usage.py build-report`\nusing this primary task ID; it obtains and links the signed receipt. Show the\nreport with the delivered result. Report creation does not mean that the matter's\nprofessional analysis ran without a model.\n\nFor the multi-item review, call `lucia_matter_open` with the explicitly selected\nabsolute `run_dir`. Use its native local panel instead of launching\n`review_server.py` or a standalone HTML editor. Saving keeps pending decisions\nbound to the current intake and review; it does not apply them or accept the\nengagement. Preserve the component's separate confirmed apply and validation\nsteps. If the panel is unavailable, review the normal documents in chat and\nleave the UI check pending.\n"
}