Update to Lucia

{
  "description": "Use when Lucia must refresh an existing law-firm website or create a first informational website from verified lawyer or firm materials, with responsive implementation, exact browser review, a reviewable preview, mechanical validation, and approval-bound publication. Applies the shared website workflow through Lucia's lawyer-specific confidentiality and professional-information profile.",
  "included_files": [
    {
      "relative_path": "references/lucia-lawyer-profile.md",
      "size_in_bytes": 4531
    }
  ],
  "name": "presenza-digitale-studio",
  "skill_md_contents": "---\nname: presenza-digitale-studio\ndescription: Use when Lucia must refresh an existing law-firm website or create a first informational website from verified lawyer or firm materials, with responsive implementation, exact browser review, a reviewable preview, mechanical validation, and approval-bound publication. Applies the shared website workflow through Lucia's lawyer-specific confidentiality and professional-information profile.\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# Presenza digitale dello studio\n\nAfter substantive use of this workflow, read and follow the `Plugin Improvement\nFeedback` section in `../lucia/SKILL.md`.\n\nRead `references/lucia-lawyer-profile.md` completely. Its lawyer-specific\ncontract takes precedence over profession-specific references to Vera or a\ncommercialista in the shared component, but it does not weaken or replace the\ncomponent's evidence, implementation, responsive review, destination approval,\npackage binding, or publication gates.\n\nResolve `../../modules/presenza-digitale-studio` from this skill directory when\nit exists; otherwise resolve `../../../presenza-digitale-studio` in the\nrepository. Read that module's\n`skills/presenza-digitale-studio/SKILL.md` completely and follow it. Treat the\nresolved module root as the plugin working directory for every command,\nrequirement, script, schema, reference, and asset. Do not copy or fork the\nshared website machinery inside Lucia.\n\nThe canonical schema currently names an assistant-originated studio convention\n`vera_default_proposal`. Preserve that opaque internal provenance value so the\nshared scripts and schemas remain byte-identical, but label it as a Lucia\nproposal in every user-facing review. Lucia's public experience and\ndeliverables are in Italian by default; language does not determine\njurisdiction, professional rules, or publication requirements.\n"
}