Update to Vera

{
  "description": "Use when Vera must refresh an existing professional-studio website or create a first informational website from verified studio materials, with responsive implementation, reviewable preview, validation, and approval-bound publication.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 289
    }
  ],
  "name": "presenza-digitale-studio",
  "skill_md_contents": "---\nname: presenza-digitale-studio\ndescription: Use when Vera must refresh an existing professional-studio website or create a first informational website from verified studio materials, with responsive implementation, reviewable preview, validation, and approval-bound publication.\n---\n\n<!-- VERA_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`../vera/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<!-- VERA_OPENAI_ONBOARDING_END -->\n\n# Presenza digitale dello studio\n\nAfter substantive use of this workflow, read and follow the `Plugin Improvement Feedback` section in `../vera/SKILL.md`.\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 all commands,\nrequirements, scripts, schemas, references and visual assets.\n"
}