Update to Vera

{
  "name": "new-client",
  "description": "Use when a studio starts work on a new client: prepare files, identify missing evidence, and build a source-bound setup covering identity, engagement, privacy, AML, and monitoring.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 289
    }
  ],
  "skill_md_contents": "---\nname: new-client\ndescription: \"Use when a studio starts work on a new client: prepare files, identify missing evidence, and build a source-bound setup covering identity, engagement, privacy, AML, and monitoring.\"\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# New Client\n\nFor a Geneva (CH-GE) mandate, read `../vera/references/localization/geneva.md` first and use this existing function’s Geneva adaptation in its resolved component skill. Language alone never selects jurisdiction.\n\n\nAfter substantive use of this workflow, read and follow the `Plugin Improvement Feedback` section in `../vera/SKILL.md`.\n\nFor substantive AML investigation or a later AML reassessment, use\n`vera:aml-review` with the same client's selected evidence and reviewed setup;\ndo not repeat the whole onboarding intake.\n\nThis is Vera's sole new-client workflow. Do not route users to separate\ndocument-preparation or professional-setup workflows.\n\nResolve the workflow root as `../../modules/new-client` when installed or\n`../../../new-client` in repository source. Resolve its subordinate file\npreparation engine as `../../modules/client-file-preparation` when installed or\n`../../../client-file-preparation` in repository source.\n\nRead that module's `skills/new-client/SKILL.md` completely. When incoming\ndocuments need preparation, also read the engine's\n`skills/client-file-preparation/SKILL.md` completely and execute that as phase\none. Both MCP toolsets belong to this workflow:\n\n- `validate_client_file_preparation_review`,\n  `render_client_file_preparation_review`,\n  `save_client_file_preparation_decisions`, and\n  `apply_client_file_preparation_decisions` review phase one;\n- `validate_new_client_review`, `render_new_client_review`,\n  `save_new_client_decisions`, and `apply_new_client_decisions` review the\n  professional-setup phases.\n\nTreat the relevant resolved module root as the plugin working directory for each\ncommand. Present every phase and artifact to the user under **New Client**.\n\nPhase one accepts `italy`, `geneva`, `zurich`, `uk`, or `mixed`; its review,\nmemo, client request, inventory, extraction report, and fiscal summary follow\n`it`, `en`, `fr`, `de`, or `es`. Low-level machine records retain stable field and\nstatus codes. The current professional setup country pack is Italy only.\nPromote a reviewed phase-one run with the\nresolved `new-client` module's\n`scripts/promote_client_file_preparation.py`; the command verifies the sealed\nmanifest and every listed output, inherits the phase-one language, and must\nreject non-Italian or mixed runs rather than implying another country pack.\n\nReal client data may enter the current model context when useful for the professional\nwork. Do not add a per-case model-use authority or minimisation declaration\nthat Vera cannot verify. Keep credentials, cookies, tokens, session URLs, and\nraw local paths outside the review payload.\n\nFor phase one, when `model_handoff.json` exists, both Codex and Cowork use it\nand every declared page as their default context. Use only the item kinds\nlisted for the current phase. Keep `review_payload.json` as the local MCP/UI\ncontract; do not use its broader draft previews as ordinary synthesis context.\nExact local identifiers remain available in professional artifacts and may be\nloaded when the work requires them. The generic `CLIENT-001` reference applies\nonly to phase-one email drafting; it is not blanket anonymization.\n\nWhen host MCP tools are unavailable, use each resolved module's persistent\nloopback workbench instead of treating chat text as saved decisions. From an\ninstalled/package module root, run:\n\n```bash\npython scripts/review_server.py <phase-output-directory>\n```\n\nFrom either component root in repository source, run:\n\n```bash\npython ../../scripts/serve_review_workbench.py <phase-output-directory> --plugin-dir .\n```\n\nThe packaged workbench invokes the same validate/render/save/apply contract.\nIf it cannot run, the review may continue in Markdown for inspection only;\nleave its JSON decisions pending and say they were not applied.\n"
}