@tenderprompt/cli 0.1.24 → 0.1.26

package/README.md

@@ -39,10 +39,13 @@ 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
 - generate starter analytics suggestions
+- print a non-mutating default analytics provisioning plan for generated apps
 - create, list, update, and delete saved analytics dashboards and charts, with
   `--dry-run` available for write previews
 
@@ -79,6 +82,13 @@ For agents, keep the pattern simple:
 6. call `preview`, `publish --dry-run`, then `publish --confirm publish` only
    when the user asked to publish
 
+For replacement work, run `tender app analytics authoring --json` before adding
+or repairing instrumentation. Its agent guidance tells agents to inspect the
+existing shopper surface before source edits, keep operator analytics out of
+shopper UI, and treat default analytics plus saved starter dashboard charts as
+part of generated-app delivery unless the user opts out or there is a concrete
+blocker.
+
 ## Auth
 
 Use the device login flow to mint a local token:
@@ -148,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
@@ -185,6 +200,7 @@ agents:
 
 ```bash
 tender app analytics capabilities artifact_123 --include-catalog --range 30d --json
+tender app analytics provision artifact_123 --from-app --json
 ```
 
 That response tells the agent:
@@ -201,6 +217,8 @@ Common read-only commands:
 ```bash
 tender app analytics summary artifact_123 --range 30d --json
 
+tender app analytics provision artifact_123 --from-app --json
+
 tender app analytics query artifact_123 --spec chart.json --json
 
 tender app analytics query artifact_123 --spec - --json < chart.json
@@ -256,6 +274,10 @@ explicit:
 tender app analytics charts list artifact_123 --dashboard analytics_dashboard_123 --json
 ```
 
+`analytics provision --from-app` is a guided plan in this release, not a hidden
+write. It returns starter chart specs, write-preview commands, write commands,
+blockers, and the chart-list completion proof an external agent should report.
+
 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
@@ -325,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.

package/dist/artifact-memory.js

@@ -100,7 +100,8 @@ function assertUsefulMemoryText(input) {
     if (lineCount > 240 || byteLength(total) > ARTIFACT_MEMORY_ENTRY_MAX_BYTES) {
         throw new Error(`Memory entries are limited to ${ARTIFACT_MEMORY_ENTRY_MAX_BYTES} bytes. Summarize the relevant context instead.\nNext: tender memory handoff --reason "Need Tender support" --summary "Current blocker and what was tried"`);
     }
-    if (lineCount > 40 && !/^summary|support_handoff|reflection$/i.test(input.summary)) {
+    const allowsLongBody = input.kind === 'summary' || input.kind === 'support_handoff' || input.kind === 'reflection';
+    if (lineCount > 40 && !allowsLongBody) {
         throw new Error('Memory entries should be bounded summaries, not raw transcript dumps.\nNext: tender memory add --kind summary --summary "Compact the useful context" --body "Goal, changes, failures, and next step"');
     }
 }
@@ -162,14 +163,14 @@ async function readExistingNote(input) {
     return result.exitCode === 0 ? result.stdout : '';
 }
 export async function appendArtifactMemoryNote(input) {
-    assertUsefulMemoryText(input);
+    const normalizedKind = normalizeArtifactMemoryKind(input.kind);
+    assertUsefulMemoryText({ ...input, kind: normalizedKind.kind });
     const commitSha = input.commitSha ?? (await readArtifactMemoryHead(input));
     const artifactId = input.artifactId ?? (await inferArtifactIdFromRemote(input));
     if (!artifactId) {
         throw new Error('Artifact memory requires an artifact id. Pass --artifact or run inside a checkout with a Tender artifact remote.\nNext: tender app git setup <app-id> --dir .');
     }
     const sessionId = await readArtifactMemorySessionId(input);
-    const normalizedKind = normalizeArtifactMemoryKind(input.kind);
     const redactedSummary = redactArtifactMemoryText(input.summary.trim());
     const redactedBody = input.body?.trim() ? redactArtifactMemoryText(input.body.trim()) : null;
     const warnings = [