Update to JUNE

{
  "name": "june-maintain-casework",
  "description": "Create and update ordinary case-management records in JUNE safely. Use when a user asks to create or modify a case, contact, case participant, note, deadline, appointment, or document metadata. Use the dedicated facts skill for Case Facts or Document Facts.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 436
    }
  ],
  "skill_md_contents": "---\nname: june-maintain-casework\ndescription: Create and update ordinary case-management records in JUNE safely. Use when a user asks to create or modify a case, contact, case participant, note, deadline, appointment, or document metadata. Use the dedicated facts skill for Case Facts or Document Facts.\n---\n\n# Maintain JUNE casework\n\nResolve the target and required identifiers before changing data. Use JUNE's current record as the source of truth.\n\n## Prepare the change\n\n1. Identify the authenticated user and relevant permissions with `whoami` or `get_user_permissions` when authorization is material.\n2. Resolve the case with `get_case_by_reference` or another read tool. Never infer a case ID.\n3. Read the current target record before updating it.\n4. Resolve controlled values instead of inventing IDs:\n   - mandates: `list_mandates`\n   - roles, deadline types, appointment types, document types, and other reference values: `get_value_list`\n   - contacts: `search_contacts`, then `get_contact` for the selected match\n5. If multiple targets or values remain plausible, ask the user to choose.\n\n## Apply the requested operation\n\nUse the narrowest matching tool:\n\n- new records: `create_case`, `create_contact`, `add_case_participant`, `create_note`, `create_deadline`, or `create_appointment`\n- existing records: `update_case`, `update_document`, or `update_appointment`\n\nFor `add_case_participant`, select an existing contact or create one first, resolve the exact role with `get_value_list(\"Roles\")`, and never confuse contact ID with participant ID.\n\nUse `$june-manage-facts` for `update_casefact`, `create_document_facts`, or `update_document_facts`; those operations require their own schemas and version rules.\n\nBefore a destructive-hint update, summarize the exact target and replacement values and obtain explicit confirmation unless the user's latest instruction already states that exact target and change. Do not silently overwrite existing values. Never broaden a requested change to adjacent fields or records.\n\nCreate operations may produce duplicates. Do not retry a successful or ambiguous write automatically; read the record back first.\n\n## Report the result\n\nState what changed, identify the case and affected record, and include returned IDs or deep links. If the tool returns an error or an ambiguous outcome, preserve the current state and explain the next safe check.\n"
}