@tenderprompt/cli 0.1.10 → 0.1.12

package/README.md

@@ -36,8 +36,8 @@ session:
 - inspect artifact-scoped analytics without SQL or platform credentials
 - run server-validated chart specs and export aggregate rows
 - generate starter analytics suggestions
-- create saved analytics dashboards and charts, with `--dry-run` available for
-  write previews
+- create, list, update, and delete saved analytics dashboards and charts, with
+  `--dry-run` available for write previews
 
 The CLI is deterministic by design: every workflow has a non-interactive flag
 path, supports `--json` where automation needs structured output, and avoids
@@ -88,6 +88,15 @@ TTL values are intentionally bounded:
 Use `--profile publish` only when the token should be allowed to publish.
 Publish still requires explicit confirmation with `--confirm publish`.
 
+Credential precedence is explicit-first:
+
+1. `--token`
+2. `--profile <name>`
+3. `TENDER_API_TOKEN`
+4. saved default profile
+
+`--base-url` overrides the base URL for whichever credential source is used.
+
 ## Git Transport
 
 Tender source movement uses Git:
@@ -159,6 +168,8 @@ tender app analytics export query artifact_123 --spec chart.json --format csv
 tender app analytics suggestions artifact_123 --range 30d --json
 
 tender app analytics charts templates --json
+
+tender app analytics properties list artifact_123 --json
 ```
 
 Safe write previews:
@@ -166,22 +177,54 @@ Safe write previews:
 ```bash
 tender app analytics dashboards artifact_123 --create "Agent dashboard" --dry-run --json
 
+tender app analytics properties activate artifact_123 \
+  --event signup_started \
+  --property plan \
+  --type dimension \
+  --dry-run \
+  --json
+
 tender app analytics charts create artifact_123 \
   --dashboard analytics_dashboard_123 \
   --title "Signup funnel" \
   --spec funnel.json \
   --dry-run \
   --json
+
+tender app analytics charts update artifact_123 \
+  --chart analytics_chart_123 \
+  --title "Signup funnel" \
+  --spec funnel.json \
+  --dry-run \
+  --json
+
+tender app analytics charts delete artifact_123 \
+  --chart analytics_chart_123 \
+  --dry-run \
+  --json
 ```
 
 Real saved-dashboard writes use the same commands without `--dry-run`.
+List charts before update/delete so the target chart id and current spec are
+explicit:
+
+```bash
+tender app analytics charts list artifact_123 --dashboard analytics_dashboard_123 --json
+```
 
 Agents should combine `capabilities --include-catalog` with local source-code
 inspection. For example, inspect where the app calls
 `__TP_ANALYTICS.invoke(...)`, propose a chart spec, validate it with
 `analytics query`, and only then create a saved chart.
 Use `charts templates --json` for reusable chart shapes; adapt any placeholders
-to observed events, paths, or promoted property keys before querying or saving.
+to observed events, paths, or queryable property keys before querying or saving.
+Property group-bys and property metrics need the custom event property to be
+available for dashboard queries; `charts create` and `charts update` activate
+missing properties automatically when the spec includes an `event_name = ...`
+filter. `analytics query` is read-only, so use
+`properties activate` first when trying an ad hoc property query. When a
+query fails for a missing dashboard-query property, the CLI prints the exact
+activation commands to run and does not perform that write automatically.
 
 ## Safety Model
 
@@ -195,6 +238,8 @@ to observed events, paths, or promoted property keys before querying or saving.
   remote URLs.
 - Analytics commands use tenant/artifact-scoped API routes. They do not expose
   raw query credentials or raw SQL.
+- Dashboard-query property activation is an explicit analytics write and remains
+  tenant/artifact-scoped.
 - Raw analytics event export is intentionally not available; exports are bounded
   catalog metadata or validated aggregate query rows.