@remits/remits-cli 0.1.79 → 0.1.80

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remits/remits-cli",
-  "version": "0.1.79",
+  "version": "0.1.80",
   "description": "Local CLI for auth, component sync, and live test execution against Remits",
   "license": "MIT",
   "private": false,

package/skills/remits-cli/SKILL.md

@@ -217,7 +217,7 @@ Use `mcp_support_ticket` to manage lifecycle:
 - `update_status` — move to `in_progress` or `pending_review`
 - `complete` — resolve the ticket with a summary of what was done
 - `release` — unassign if you cannot continue
-- Always call `mcp_support_ticket` with the ticket's owning `accountId`.
+- **Pulling a ticket by number is enough — you do NOT need to know its account first.** The `ticketId` IS the ticket's globally-unique anchor id, and `mcp_support_ticket` resolves the owning account from it for every action that operates on an existing ticket (`read`, `accept`, `update_status`, `complete`, `release`, `record_progress`, `add_artifact`, `get_attachment`). So when a user says "pull ticket 19463", just call `read` with `{ "action": "read", "ticketId": "19463" }` from any authenticated **prod** session (the ticket lives in prod data) — omit `accountId` entirely. The response returns the resolved `accountId`/`accountName` (and `implementationAccountId` when set); use those for any follow-up work. **Only `create` requires an explicit `accountId`** (a brand-new ticket has no anchor to resolve from). If a bare `ticketId` returns "Support ticket not found", double-check you are in `--data-mode prod`, then fall back to passing an explicit `accountId`.
 - If a ticket is part of the request, manage the lifecycle proactively. Do not wait for the human user to remind you to read, accept, update, complete, or release it.
 
 Ticket-routing context:
@@ -1109,9 +1109,9 @@ Create and manage the full lifecycle of account-relative `support_tickets`.
 
 | Parameter | Required | Description |
 |-----------|----------|-------------|
-| `accountId` | yes | The account that owns the support ticket |
+| `accountId` | conditional | The account that owns the support ticket. **Required only for `create`.** For every other action it is optional — the tool resolves the owning account from `ticketId` (the ticket's anchor id) and returns it. Pass it only to override/disambiguate. |
 | `action` | yes | `create`, `read`, `accept`, `update_status`, `complete`, `release`, `record_progress`, `add_artifact`, or `get_attachment` |
-| `ticketId` | conditional | Required for every action **except** `create` (which returns the new ticket ID) |
+| `ticketId` | conditional | Required for every action **except** `create` (which returns the new ticket ID). Alone it is sufficient to resolve the ticket and its owning account. |
 | `subject` | conditional | Short title. Required for `create`. |
 | `type` | conditional | Required for `create`: `enhancement`, `defect`, `question`, `task`, or `incident` |
 | `priority` | no | `low`/`medium`/`high`/`critical` for `create` (default `medium`) |