@togglhq/cli 1.5.26 → 1.5.28

package/build/program.js

@@ -1,2 +1,2 @@
-import { t as createProgram } from "./program-B03iyxXV.js";
+import { t as createProgram } from "./program-CwW_34U6.js";
 export { createProgram };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@togglhq/cli",
-  "version": "1.5.26",
+  "version": "1.5.28",
   "description": "Toggl CLI for Toggl 2.0 API operations.",
   "license": "UNLICENSED",
   "type": "module",
@@ -26,7 +26,9 @@
   "files": [
     "build/**/*.js",
     "build/**/*.d.ts",
-    "skills/**",
+    "skills/*/SKILL.md",
+    "skills/*/reference/**",
+    "skills/*/workflows/**",
     "README.md",
     "LICENSE"
   ],
@@ -57,6 +59,6 @@
     "@types/node": "22.19.11",
     "tsdown": "0.21.8",
     "typescript": "5.9.3",
-    "vitest": "3.2.4"
+    "vitest": "3.2.7"
   }
 }

package/skills/toggl-cli/reference/auth-environments-workspaces.md

@@ -31,7 +31,7 @@ If the account has multiple workspaces, pass the workspace explicitly:
 toggl auth --workspace-id <workspace-id>
 ```
 
-When `--profile` is omitted, the CLI saves the account under an account-based profile name such as `hazem-12345` and makes it active. Use an explicit profile name only when the user asks for a specific name:
+When `--profile` is omitted, the CLI saves the account under an account-based profile name such as `user-12345` and makes it active. Use an explicit profile name only when the user asks for a specific name:
 
 ```bash
 toggl auth --profile <name>

package/skills/toggl-cli/reference/command-contract.md

@@ -11,9 +11,9 @@ toggl [global flags] <group> … <subcommand> [flags]
 Put global flags before the first group:
 
 ```bash
-toggl --json tasks list --project-id 436195
-toggl --profile hazem-12345 projects list
-toggl --workspace-id 356965 tasks list --project-id 436195
+toggl --json tasks list --project-id 123456
+toggl --profile user-12345 projects list
+toggl --workspace-id 789012 tasks list --project-id 123456
 ```
 
 **Organization and shared data** use multi-segment paths (no top-level `org` command):
@@ -36,7 +36,7 @@ Core resources and actions:
 | `statuses`     | `list`                                                                              |
 | `users`        | `list`                                                                              |
 
-Operations marked **`hidden: true`** in `@toggl/operations` (notably generated **calendar** and **scheduler** endpoints today) are skipped by `visibleOperations()` and do not register CLI/MCP commands.
+Some low-level endpoints are omitted from the CLI and MCP.
 
 Bulk mutations use a nested command: **`toggl <resource> bulk <verb>`** (for example `toggl tasks bulk patch`). MCP entity tools still use hyphenated `action` values such as `bulk-patch` — only the CLI path uses the nested form.
 
@@ -54,7 +54,7 @@ Bulk mutations use a nested command: **`toggl <resource> bulk <verb>`** (for exa
 Successful responses go to stdout as JSON. Use `--json` for compact single-line JSON that is easy to parse:
 
 ```bash
-toggl --json tasks list --project-id 436195
+toggl --json tasks list --project-id 123456
 ```
 
 Without `--json`, successful output is still JSON, but pretty-printed.
@@ -67,7 +67,7 @@ Prefer scalar flags for simple calls. Input field names map to kebab-case flags:
 
 ```bash
 toggl --json tasks get --task-id 12345
-toggl --json tasks list --project-id 436195 --status-id 243956
+toggl --json tasks list --project-id 123456 --status-id 111222
 toggl --json time-entries list --date-from 2026-04-01 --date-to 2026-04-07
 ```
 
@@ -75,15 +75,15 @@ For `update` commands, payload fields use `--payload-<field>`:
 
 ```bash
 toggl --json tasks update --task-id 12345 --payload-name "New task name"
-toggl --json tasks update --task-id 12345 --payload-status-id 270002
-toggl --json projects update --project-id 436195 --payload-name "Renamed project"
+toggl --json tasks update --task-id 12345 --payload-status-id 456789
+toggl --json projects update --project-id 123456 --payload-name "Renamed project"
 ```
 
 Use `--data` for a full JSON body:
 
 ```bash
-toggl --json tasks create --data '{"name":"Write release notes","project_id":436195}'
-toggl --json tasks update --data '{"task_id":12345,"payload":{"status_id":270002}}'
+toggl --json tasks create --data '{"name":"Write release notes","project_id":123456}'
+toggl --json tasks update --data '{"task_id":12345,"payload":{"status_id":456789}}'
 ```
 
 Use `--data -` when shell quoting is fragile:
@@ -101,7 +101,7 @@ toggl --json tasks create --data-file ./new-task.json
 Bulk endpoints expect JSON via `--data` or `--data-file` (arrays for patch-style bulk; objects with `ids` or `task_ids` for deletes/archives). Examples:
 
 ```bash
-toggl --json tasks bulk patch --dry-run --data '[{"id":111,"status_id":270002},{"id":222,"status_id":270002}]'
+toggl --json tasks bulk patch --dry-run --data '[{"id":111,"status_id":456789},{"id":222,"status_id":456789}]'
 toggl --json projects bulk patch --data-file ./project-updates.json
 toggl --json time-blocks bulk create --data '{"time_blocks":[{"task_id":12345,"start":"2026-04-01T09:00:00Z","duration":60}]}'
 toggl --json time-entries bulk patch --data '[{"id":9001,"description":"Updated"}]'
@@ -117,17 +117,17 @@ toggl --json tasks bulk delete --data '{"ids":[111,222]}' --yes
 Use `--dry-run` to validate resolved input without making an API call:
 
 ```bash
-toggl tasks update --task-id 12345 --payload-status-id 270002 --dry-run
+toggl tasks update --task-id 12345 --payload-status-id 456789 --dry-run
 ```
 
 Delete commands require `--yes`. Never add `--yes` unless the user clearly requested the destructive delete:
 
 ```bash
 toggl --json tasks delete --task-id 12345 --yes
-toggl --json projects delete --project-id 436195 --yes
+toggl --json projects delete --project-id 123456 --yes
 toggl --json time-blocks delete --task-id 12345 --time-block-id 67890 --yes
 toggl --json tasks bulk delete --data '{"ids":[111,222]}' --yes
-toggl --json projects bulk delete --data '{"ids":[436195,436196]}' --yes
+toggl --json projects bulk delete --data '{"ids":[123456,123457]}' --yes
 toggl --json time-blocks bulk delete --data '{"ids":[101,102]}' --yes
 ```
 

package/skills/toggl-cli/reference/projects.md

@@ -19,7 +19,7 @@ toggl --json projects get --project-id <project-id>
 Create a project:
 
 ```bash
-toggl --json projects create --data '{"name":"Q3 Planning","workspace_id":356965}'
+toggl --json projects create --data '{"name":"Q3 Planning","workspace_id":789012}'
 ```
 
 Rename a project:
@@ -45,7 +45,7 @@ toggl --json projects list
 When creating tasks, pass the resolved project ID to `tasks create`:
 
 ```bash
-toggl --json tasks create --data '{"name":"Task name","project_id":436195}'
+toggl --json tasks create --data '{"name":"Task name","project_id":123456}'
 ```
 
 Project deletion is destructive. Confirm the exact project ID and name before using `--yes`.

package/skills/toggl-cli/reference/tasks.md

@@ -20,7 +20,7 @@ toggl --json tasks get --task-id <task-id>
 Create a task:
 
 ```bash
-toggl --json tasks create --data '{"name":"Follow up with design","project_id":436195}'
+toggl --json tasks create --data '{"name":"Follow up with design","project_id":123456}'
 ```
 
 Update a task with scalar payload flags:
@@ -33,7 +33,7 @@ toggl --json tasks update --task-id <task-id> --payload-status-id <status-id>
 Update a task with a JSON payload:
 
 ```bash
-toggl --json tasks update --data '{"task_id":12345,"payload":{"name":"Updated name","status_id":270002}}'
+toggl --json tasks update --data '{"task_id":12345,"payload":{"name":"Updated name","status_id":456789}}'
 ```
 
 Delete a task only after explicit user confirmation:

package/skills/toggl-cli/reference/troubleshooting.md

@@ -86,7 +86,7 @@ toggl --json tasks delete --task-id <task-id> --yes
 For API response schema warnings, rerun with debug enabled:
 
 ```bash
-TOGGL_DEBUG=1 toggl --json tasks list --project-id 436195
+TOGGL_DEBUG=1 toggl --json tasks list --project-id 123456
 ```
 
 ## Unknown Command Shape

package/skills/toggl-cli/workflows/common-workflows.md

@@ -36,7 +36,7 @@ If multiple resources match a user-provided name, ask before mutating.
 
 ```bash
 toggl --json projects list
-toggl --json tasks create --data '{"name":"Write release notes","project_id":436195}'
+toggl --json tasks create --data '{"name":"Write release notes","project_id":123456}'
 ```
 
 ## Move a Task to a Status

package/skills/toggl-cli/INTERNAL.md

@@ -1,62 +0,0 @@
-# Internal Toggl CLI Workflows
-
-Install `@toggl/cli-internal` from **GitHub Packages** for internal builds that include staging and MS environment helpers (`toggl-internal` bin).
-
-Configure `~/.npmrc` with a GitHub Packages token (`read:packages`) and Toggl org access:
-
-```
-@toggl:registry=https://npm.pkg.github.com/
-//npm.pkg.github.com/:_authToken=<GH_NPM_TOKEN>
-```
-
-```bash
-npm install -g @toggl/cli-internal
-```
-
-## Environments
-
-Use production by default. Use these flags only when a Toggl engineer asks for staging or a named MS environment.
-
-Authenticate against staging:
-
-```bash
-toggl-internal auth --staging
-toggl-internal --json profile list
-toggl-internal --json workspace list
-```
-
-Authenticate against a named MS environment:
-
-```bash
-toggl-internal auth --ms <name>
-toggl-internal --json profile list
-toggl-internal --json workspace list
-```
-
-Generated non-production profiles keep the environment prefix, for example `staging-hazem-12345` or `ms-foo-hazem-12345`.
-
-## Environment Variables
-
-The internal build also recognizes shorthand environment variables:
-
-```bash
-ENV=staging toggl-internal auth
-MS=<name> toggl-internal auth
-```
-
-Explicit URL overrides still take precedence:
-
-```bash
-TOGGL_FOCUS_API_URL=<url> TOGGL_ACCOUNTS_API_URL=<url> toggl-internal auth
-```
-
-## Troubleshooting
-
-When data appears missing in an internal environment, verify profile and workspace before assuming the resource does not exist:
-
-```bash
-toggl-internal --json profile list
-toggl-internal --json profile current
-toggl-internal --json workspace list --refresh
-toggl-internal --json workspace switch <workspace-id>
-```