@wrangled/cli 0.3.5 → 0.3.6

package/dist/guide.js

@@ -9,12 +9,12 @@ export const guide = `# ${brand.name} CLI
 
 ## Setup
 
-1. Check the login: \`${cli} whoami\`. It prints the workspace name, slug, and id.
+1. Check the login: \`${cli} whoami\`. It prints the workspace name, slug, and id, and whether the key has library access.
 2. If it exits with code 3, you are not logged in. Ask the user to run \`${cli} login\` in their own terminal. It prompts for the key without showing it. Never ask for the key in chat and never put it on a command line, where it lands in shell history and logs. In CI, the key comes from the \`${envPrefix}_API_KEY\` environment variable.
 
 ## Start with the data guide
 
-Run \`${cli} guide\` first. It says, in plain words, what this workspace has. It starts with the settled facts: rows to leave out of the numbers, known gaps in the data, last month's normal numbers and the latest changes, with \`${cli} facts\` for the rest. Then each connected source with when it last synced and how many rows it holds over which dates; the content library's ads, emails, text messages, landing pages, videos and posts and how many videos and recordings have transcripts; and what is missing, such as a source that is not connected, a failing sync, or videos and recordings without a transcript yet.
+Run \`${cli} guide\` first. It says, in plain words, what this workspace has. It starts with the settled facts: rows to leave out of the numbers, known gaps in the data, last month's normal numbers and the latest changes, with \`${cli} facts\` for the rest. Next comes the latest weekly story's headline, with \`${cli} story\` for the whole story. Then each connected source with when it last synced and how many rows it holds over which dates; the content library's ads, emails, text messages, landing pages, videos and posts and how many videos and recordings have transcripts; and what is missing, such as a source that is not connected, a failing sync, or videos and recordings without a transcript yet.
 
 ## Before writing ads: the campaign brief
 
@@ -203,7 +203,7 @@ A scheduled hand's run acts as its skill's agent, the way the Facebook ads agent
 \`\`\`
 ${cli} login                        validate a key (prompted, piped, or ${envPrefix}_API_KEY) and save it
 ${cli} logout                       delete saved credentials
-${cli} whoami                       show the current workspace
+${cli} whoami                       show the current workspace and library access
 ${cli} guide                        what this workspace's data holds, how fresh it is, and what is missing: read it first
 ${cli} brief [--from <date>] [--to <date>] [--channel <channel>] [--campaign <id>] [--top <n>]   the offer, voice, best and worst ads, pages, results and audience: start here before writing ads
 ${cli} warehouse schema [--summary] [--table <name> ...] [--search <words>]   list tables and columns; --summary for one row per table

package/dist/main.js

@@ -51,7 +51,7 @@ const commands = {
             if (options.format === "json")
                 return printJson(me);
             const { name, slug, id } = me.workspace;
-            console.log(renderTable(["workspace", "slug", "id"], [{ workspace: name, slug, id }]));
+            console.log(renderTable(["workspace", "slug", "id", "library access"], [{ workspace: name, slug, id, "library access": me.knowledge ? "on" : "off" }]));
         },
     },
     "warehouse schema": {

package/dist/playbooks.js

@@ -99,6 +99,14 @@ ${cli} facts --format json
 
 Treat confirmed facts as true. Confirmed \`baseline\` facts are the normal numbers to compare against. \`watch\` facts are what an earlier run asked to re-check (one past its \`validUntil\` has run its course), \`change\` facts are what changed or was proposed and when, and \`gap\` facts are the data's quirks. A summary that starts "Not yet confirmed:" is a suggestion no person has checked yet: weigh it, but never let it outweigh what a query shows.
 
+Then read the latest weekly story about this client:
+
+\`\`\`sh
+${cli} story --format json
+\`\`\`
+
+It is the newest weekly story of what the data said and why: context to build on and to check, never a fact and never a substitute for a query. Never take a number from it; where this run's numbers disagree with it, this run's numbers win. If its \`story\` is null, there is no story yet: carry on.
+
 ## 2. Check that the data is fresh
 
 \`\`\`sh
@@ -404,6 +412,14 @@ ${cli} facts --format json
 
 Treat confirmed facts as true. Confirmed \`baseline\` facts are the normal numbers to compare against. \`watch\` facts are what an earlier run asked to re-check (one past its \`validUntil\` has run its course), \`change\` facts are what changed or was proposed and when, and \`gap\` facts are the data's quirks. A summary that starts "Not yet confirmed:" is a suggestion no person has checked yet: weigh it, but never let it outweigh what a query shows.
 
+Then read the latest weekly story about this client:
+
+\`\`\`sh
+${cli} story --format json
+\`\`\`
+
+It is the newest weekly story of what the data said and why: context to build on and to check, never a fact and never a substitute for a query. Never take a number from it; where this run's numbers disagree with it, this run's numbers win. If its \`story\` is null, there is no story yet: carry on.
+
 Then read how people decided:
 
 \`\`\`sh

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wrangled/cli",
-  "version": "0.3.5",
+  "version": "0.3.6",
   "description": "Command-line access to your marketing data warehouse, for people and coding agents",
   "type": "module",
   "bin": {