Update to Zuora Coding Agent

{
  "description": "Internal SDD → TR matrix extraction (invoked by zuora-uat-design)",
  "included_files": [],
  "name": "zuora-uat-design-worker",
  "skill_md_contents": "---\nname: zuora-uat-design-worker\ndescription: Internal SDD → TR matrix extraction (invoked by zuora-uat-design)\n---\n\n# SDD → TR matrix (internal)\n\nPort of uat-test `analyze-sdd` adapted for `design/testmatrix/` layout.\n\n## Filename rules\n\n| `project_name` | Output |\n|----------------|--------|\n| Omitted | `{Feature}_TRs.md` |\n| Set (e.g. `FW`) | `{project_name}_{System}_TRs.md` |\n\nIncremental mode must use the same prefix as existing matrix files.\n\n## TR scope presets\n\n| Preset | max_trs_per_file | include_edge_cases |\n|--------|------------------|-------------------|\n| focused | 5 | off |\n| standard | 10 | limited |\n| comprehensive | 20 | on |\n\n## Process\n\n### Step 1: Discover SDDs\n\nList `*.md` under `sdd_path`. Incremental: read only `target_sdd_file`.\n\n### Step 2: Identify Zuora use cases\n\nCategories: product catalog, subscriptions, billing/invoicing, payments, tax, usage, AR, revenue. One TR bullet per testable scenario.\n\n### Step 3: Write matrix files\n\nFormat each TR as `- TR{n}: <summary>`. Group by feature/system. Enforce caps.\n\n### Step 4: MCP helpers\n\n- `mcp__zuora-mcp__zuora_codegen` — API endpoints and field names for TR wording\n- `mcp__zuora-mcp__ask_zuora` — only if SDD scope needs product-behavior clarification after references\n\nDo **not** use Avatar/PlayerZero tools.\n"
}