@tenderprompt/cli 0.1.25 → 0.1.27

package/README.md

@@ -39,6 +39,8 @@ session:
 - inspect artifact-scoped analytics without SQL or platform credentials
 - inspect artifact-scoped app database tables, schema, and bounded read-only
   query output
+- create private app admin dashboard, resource, view, and widget definitions
+  from structured app database specs
 - share app setup between Tender accounts without copying customer data,
   analytics history, app database rows, secrets, or release history
 - run server-validated chart specs and export aggregate rows
@@ -156,6 +158,11 @@ tender app db tables artifact_123 --env published --json
 tender app db schema artifact_123 --env published --table votes --json
 tender app db query artifact_123 --env published --sql "select * from votes limit 20" --json
 tender app db query artifact_123 --env published --sql "select * from votes order by created_at" --limit 50 --offset 50 --json
+tender app db dashboards artifact_123 --create "App admin" --default-env published --dry-run --json
+tender app db resources suggest artifact_123 --env published --json
+tender app db dashboards render artifact_123 --dashboard app_db_dashboard_123 --env published --json
+tender app db resources create artifact_123 --dashboard app_db_dashboard_123 --spec resource.json --dry-run --json
+tender app db widgets create artifact_123 --dashboard app_db_dashboard_123 --title "Total signups" --spec widget.json --dry-run --json
 ```
 
 ## Shared app setup
@@ -340,6 +347,26 @@ Client and server limits include a 100 KB statement cap and at most 100 bound
 parameters. The server enforces the final policy, row limits, response limits,
 artifact scope, and audit logging.
 
+Private app admin dashboards are definition-only in the CLI. Use the same
+artifact-scoped `db-read` profile to save dashboards, table-backed resources,
+saved views, and widgets; raw app rows stay in the generated app database.
+Logged-in users can open saved dashboards at `/#/workspace/<artifact-id>/admin`.
+
+```bash
+tender app db resources suggest artifact_123 --profile db --env published --json
+tender app db dashboards artifact_123 --profile db --create "Coffee Matcher Admin" --default-env published --json
+tender app db resources create artifact_123 --profile db --dashboard app_db_dashboard_123 --spec resource.json --view recent.json --json
+tender app db widgets create artifact_123 --profile db --dashboard app_db_dashboard_123 --title "Votes by choice" --spec widget.json --json
+tender app db dashboards render artifact_123 --profile db --dashboard app_db_dashboard_123 --env published --json
+```
+
+Suggested app database resources may include `dateRange: { "source":
+"dashboard", "column": "created_at" }` so saved admin dashboards behave like a
+Grafana dashboard: one top-level date range applies to charts and tables by
+default, while resource filters stay available for local drill-downs. Use
+`dateRange: { "source": "off" }` or a fixed override only for panels that should
+not follow the dashboard date range.
+
 ## Safety Model
 
 - Local agents run in the user's environment, not in Tender.