Update to Lucia

{
  "description": "Use when Lucia must create or resume a durable client engagement, import selected inputs, and prepare or start a client-bound workflow through the Studio Archive component shared with Vera.",
  "included_files": [],
  "name": "studio-archive",
  "skill_md_contents": "---\nname: studio-archive\ndescription: Use when Lucia must create or resume a durable client engagement, import selected inputs, and prepare or start a client-bound workflow through the Studio Archive component shared with Vera.\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# Archivio dello studio\n\nAfter substantive use of this workflow, read and follow the `Plugin Improvement Feedback` section in `../lucia/SKILL.md`.\n\nResolve `../../modules/studio-archive` from this skill directory when it\nexists; otherwise resolve `../../../studio-archive` in the repository. Read\nthat module's `skills/studio-archive/SKILL.md` completely and follow it.\nTreat the resolved module root as the plugin working directory for every\ncommand. Do not paraphrase, shorten, fork, or replace the component workflow.\n\nUse the plain Studio Archive tools under `lucia`. Prepare only the workflows\ndeclared in Lucia’s `components.json`: `prompt-optimizer`,\n`deep-research-validator`, and `apertura-pratica`. The shared component guide\nalso describes other products: use its client, engagement, file, search,\nsnapshot, and run lifecycle instructions for Lucia. Journal sampling, invoice\nchecks, and verification of Vera’s selective reporting receipts are outside\nLucia’s Archive. Preserve the literal shared `Vera/` ledger paths.\n\nFor CLI fallback, use Lucia’s `scripts/lucia_studio_archive.py` at the product\nroot with the same arguments as the component guide. It applies Lucia’s workflow\nlist and retains the same client, engagement, receipts and lifecycle.\n\nLucia's public experience and deliverables are in Italian.\n"
}