@dataworks-technology/cli 1.6.0 → 1.7.0

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
     {
       "name": "dataworks",
       "source": "./plugins/dataworks",
-      "description": "Query Dataworks athlete metrics using the authenticated local CLI session"
+      "description": "Query Dataworks athlete metrics and operate the Dataworks platform using the authenticated local CLI session."
     }
   ]
 }

package/README.md

@@ -339,7 +339,7 @@ Files under `src/generated/`, `src/commands/data/`, and `docs/commands/` are gen
 
 Canonical metric names are generated the same way. [`scripts/generate-metrics.ts`](./scripts/generate-metrics.ts) reads `metricConfig` from the private `@dataworks/sdk` devDependency and emits `src/generated/metrics.ts` and the catalogue block in the `query-dataworks-metrics` skill. To add a metric, change the SDK — not the generated files, and not the alias layer in `src/lib/metric-names.ts`.
 
-The daily SDK maintenance workflow checks for new `@dataworks-technology/data` and `@dataworks/sdk` versions. Deterministic generation runs first; if compatibility work is required, a constrained LiteLLM maintenance agent prepares a draft pull request for human review.
+The daily SDK maintenance workflow checks for new `@dataworks-technology/data` and `@dataworks/sdk` versions. Deterministic generation runs first; if compatibility work is required, a constrained LiteLLM maintenance agent repairs it. The repository workflow verifies the exact update with full CI, merges successful updates automatically, and starts a CLI release. Failed repairs remain draft PRs for human review.
 
 See [architecture](./docs/architecture.md), [contributing](./docs/contributing.md), [automated SDK maintenance](./docs/maintenance.md), [security](./docs/security.md), and [releasing](./docs/releasing.md) for details.
 
@@ -350,11 +350,11 @@ See [architecture](./docs/architecture.md), [contributing](./docs/contributing.m
 | Trigger                           | Workflow       | Description                                                                                                                 |
 | --------------------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------- |
 | Pull request or push to `main`    | `ci.yml`       | Verifies generation, formatting, types, tests, builds, and packaging on the labelled self-hosted runner with Node 22 and 24 |
-| Daily schedule or manual dispatch | `sdk-sync.yml` | Updates the Data SDK and opens or refreshes a draft maintenance PR                                                          |
+| Daily schedule or manual dispatch | `sdk-sync.yml` | Updates SDKs, verifies and automatically merges successful maintenance PRs                                                  |
 | Manual dispatch                   | `uat-e2e.yml`  | Authenticates against UAT and reads the public Data manifest                                                                |
-| Push to `main`                    | `release.yml`  | Runs release-please on the self-hosted runner, then publishes with npm provenance from the required GitHub-hosted runner    |
+| Push to `main` or manual dispatch | `release.yml`  | Runs release-please on the self-hosted runner, then publishes with npm trusted publishing and notifies Slack                |
 
-Automated SDK update pull requests remain drafts until a human reviews and marks them ready.
+Successful SDK maintenance and release-please PRs are verified and merged automatically. Failed SDK repairs remain draft PRs for human review. Successful npm publication notifies Slack through `SLACK_WEBHOOK_URL`.
 
 ---
 
@@ -374,7 +374,7 @@ Automated SDK update pull requests remain drafts until a human reviews and marks
 - Depends on **Dataworks-Data** for the public GraphQL schema and `@dataworks-technology/data` package
 - Uses the same public contract that generates the Data SDK Docusaurus reference
 - Authenticates against the UAT or Live Cognito and Data Engine endpoints at runtime
-- New SDK versions are consumed through reviewed automated pull requests rather than manual schema copying
+- New SDK versions are consumed through verified automated pull requests rather than manual schema copying
 
 ---
 

package/oclif.manifest.json

@@ -11719,5 +11719,5 @@
       ]
     }
   },
-  "version": "1.6.0"
+  "version": "1.7.0"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dataworks-technology/cli",
-  "version": "1.6.0",
+  "version": "1.7.0",
   "description": "The official command-line interface for the Dataworks Data Engine",
   "type": "module",
   "license": "MIT",
@@ -22,7 +22,6 @@
     "dist",
     "plugins",
     "schema",
-    "skills",
     "oclif.manifest.json",
     "README.md",
     "LICENSE"

package/plugins/dataworks/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "dataworks",
-  "version": "1.6.0",
-  "description": "Query athlete metrics from Dataworks using the authenticated local CLI session.",
+  "version": "1.7.0",
+  "description": "Query Dataworks athlete metrics and operate the Dataworks platform using the authenticated local CLI session.",
   "author": { "name": "Dataworks Technology" },
   "homepage": "https://github.com/Dataworks-Technology/Dataworks-CLI",
   "repository": "https://github.com/Dataworks-Technology/Dataworks-CLI",

package/plugins/dataworks/.codex-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "dataworks",
-  "version": "1.6.0",
-  "description": "Query athlete metrics from Dataworks using the authenticated local CLI session.",
+  "version": "1.7.0",
+  "description": "Query Dataworks athlete metrics and operate the Dataworks platform using the authenticated local CLI session.",
   "author": { "name": "Dataworks Technology", "url": "https://dataworks.live/" },
   "homepage": "https://github.com/Dataworks-Technology/Dataworks-CLI",
   "repository": "https://github.com/Dataworks-Technology/Dataworks-CLI",
@@ -12,7 +12,7 @@
   "interface": {
     "displayName": "Dataworks",
     "shortDescription": "Query athlete metrics safely",
-    "longDescription": "Resolve athletes and return normalized GPS, heart-rate, and other Dataworks metric values through one read-only tool.",
+    "longDescription": "Resolve athletes and events, return normalized metric values and server-side aggregates through read-only tools, and drive the full Dataworks CLI for everything else.",
     "developerName": "Dataworks Technology",
     "category": "Data",
     "capabilities": ["Read"],

package/{skills → plugins/dataworks/skills}/dataworks-cli/SKILL.md

@@ -5,11 +5,16 @@ description: Route operational requests to inspect, query, create, update, delet
 
 # Dataworks CLI
 
-Use `dw` as the operational interface for Dataworks actions. When the
-`query_metrics` tool is available, use it for historical athlete metric requests;
-it is the read-only, CLI-authenticated interface over Data Explorer. Do not call a
-Dataworks HTTP or GraphQL endpoint directly, or use an SDK instead, when the CLI
-or this tool can perform the action.
+Use `dw` as the operational interface for Dataworks actions. Do not call a
+Dataworks HTTP or GraphQL endpoint directly, or use an SDK, when the CLI or the
+Dataworks MCP tools can perform the action.
+
+The MCP tools, when available, own a narrow slice: `query_metrics` for historical
+metric values and aggregates, and `list_athletes` / `list_events` for resolving
+the IDs those queries need. Everything else is the CLI's job — full entity
+records, teams, datasets, participants, ingestion, subscriptions, and every
+create, update or delete. Use the CLI for those directly; it is not a fallback
+for when a tool fails.
 
 If a request needs `query_metrics` but the tool is unavailable, tell the user to
 run `dw agents install` once, then start a new Codex thread or run
@@ -23,7 +28,9 @@ the restarted or reloaded agent exposes the tool.
 2. Run `dw commands --json` to discover the installed command contract.
 3. Run `dw <command> --help` before constructing the exact call.
 4. Prefer the narrowest matching command:
-   - Historical athlete metrics: `query_metrics` when available
+   - Historical metric values or aggregates: `query_metrics` when available
+   - An athlete or event ID for such a query: `list_athletes` / `list_events`
+   - A full athlete, event, dataset or participant record: `dw data ...`
    - Data Engine entities: `dw data ...`
    - Authentication and session state: `dw auth ...`
    - Tenant discovery and persistence: `dw tenant list` and `dw tenant select ...`

package/plugins/dataworks/skills/query-dataworks-metrics/SKILL.md

@@ -11,6 +11,17 @@ Three read-only tools use the current authenticated `dw` session and tenant:
 - `list_athletes` — find an athlete ID, or confirm someone is not in this tenant.
 - `list_events` — find an event ID for a race, by name.
 
+These cover historical metrics and the IDs needed to ask for them, and nothing
+else. They are deliberately narrow: `list_athletes` returns only an ID, a name
+and an external ID. For anything beyond that — an athlete's full record, teams,
+datasets, participants, events as entities, ingestion, live subscriptions, or any
+create, update or delete — use the `dw` CLI, which covers the whole Data Engine
+API. See the `dataworks-cli` skill, and run `dw commands --json` to discover the
+exact command rather than exploring with `dw help`.
+
+Reach for the CLI as readily as these tools; it is the same authenticated
+session, not a fallback.
+
 If `query_metrics` is unavailable, tell the user to run `dw agents install`
 once in their terminal, then start a new Codex thread or run `/reload-plugins`
 in Claude Code. Do not substitute raw GraphQL or guess that setup succeeded.
@@ -104,8 +115,10 @@ environment, tenant, canonical metric, order, and returned count. GPS rows inclu
 decoded `position.latitude` and `position.longitude`; heart-rate values are
 numeric with unit `bpm` when the source value is valid.
 
-Every error carries a `recovery` field. Follow it rather than improvising, and
-never fall back to raw GraphQL or `dw data ...` to work around a failure.
+Every error carries a `recovery` field. Follow it rather than improvising. Do not
+reach for raw GraphQL to work around a metric failure — but the `dw` CLI is a
+first-class route for anything these tools do not cover, and the `dataworks-cli`
+skill explains how to drive it.
 
 - `ATHLETE_AMBIGUOUS` — present the candidates and ask the user to choose.
 - `ATHLETE_NOT_FOUND` — the athlete is not in this tenant. Do not retry with