@letterstory/cli 0.148.1 → 0.148.3

package/README.md

@@ -1,7 +1,7 @@
 # `@letterstory/cli`
 
-Spin up and manage Letterstory **phantom blogs** from your terminal. The CLI is a thin
-client over the Letterstory MCP endpoint (`POST /api/mcp`) — it wraps the same tool
+Spin up and manage Letter **phantom blogs** from your terminal. The CLI is a thin
+client over the Letter MCP endpoint (`POST /api/mcp`) — it wraps the same tool
 manifest an agent sees, so it never drifts from the API.
 
 ## Install
@@ -79,7 +79,7 @@ refresh automatically. Run `letterstory logout` to revoke the session and forget
 
 **Or use a static API key** (for CI/automation, or when you want scoped-down access):
 
-You need a Letterstory API key (starts with `ls_`; legacy `lb_` keys still work) with the `phantom:read` and
+You need a Letter API key (starts with `ls_`; legacy `lb_` keys still work) with the `phantom:read` and
 `phantom:write` capabilities — mint one in the app under **Settings → API keys**
 (<https://app.letterstory.com/settings?tab=api-keys>).
 Add `phantom:domain` too if you plan to buy custom domains.
@@ -96,7 +96,7 @@ Run `letterstory whoami` (alias `status`) any time to confirm which key/url (or
 resolved and see your company profile. Run `letterstory config` to see the resolved url and
 credential source without making a network call.
 
-## Phantomstory — a collection Letterstory hosts as an independent publication
+## Phantomstory — a collection Letter hosts as an independent publication
 
 A phantom is a site we host that renders one of your collections; it never carries your
 company's name. Phantoms are metered in SITES live at once (`phantom balance`), not posts.
@@ -129,7 +129,7 @@ letterstory phantom delete <phantom-id> --yes
 Pass `--no-wait` to return immediately and poll later with `phantom get`, `--no-configure`
 for a bare site, or `--dry-run` to see the plan without provisioning anything.
 
-Publishing to the site is a **collection run** on its collection (below). Letterstory's own
+Publishing to the site is a **collection run** on its collection (below). Letter's own
 launch recipe from a client domain — positioning inferred, a masthead proposed, the first
 posts seeded — is `phantom-onboard` (see "Propose, then onboard a phantom").
 
@@ -603,7 +603,7 @@ letterstory arena role set reviewsite.com --role context
 letterstory arena role set rival.com --role company --company "Rival" --rival
 letterstory arena role reset rival.com                 # hand it back to research
 
-# Arenas are callable endpoints with one-file defaults (the org's default arena is "Letterstory"):
+# Arenas are callable endpoints with one-file defaults (the org's default arena is "Letter"):
 letterstory arena list
 letterstory arena endpoint create --name "Docs research" --defaults '{"depth":"barebones"}'
 letterstory arena endpoint config <arena-id> [--file cfg.json]
@@ -913,7 +913,7 @@ app; `letterstory mail connections` shows what is connected.
 
 ## Anything else
 
-Every Letterstory tool is reachable, not just the ones with a dedicated command group:
+Every Letter tool is reachable, not just the ones with a dedicated command group:
 
 ```bash
 letterstory whoami                                 # or: status — verify your key + who it's for

package/lib/cli.mjs

@@ -1,4 +1,4 @@
-// Argument parsing, help, and command routing for the Letterstory CLI. `run(argv)`
+// Argument parsing, help, and command routing for the Letter CLI. `run(argv)`
 // is the single entry the bin and the tests both call; it returns an exit code and
 // never throws for user-facing problems (those become a printed CliError + code 1).
 
@@ -53,6 +53,7 @@ import {
 	cmdAdmin,
 	cmdFeedback,
 	cmdRepo,
+	cmdBuild,
 	cmdSite,
 	cmdEvals,
 	cmdOfferings,
@@ -65,13 +66,18 @@ import {
 
 // Matches cli/package.json; publish-cli.yml rewrites both to the published version.
 // Matches cli/package.json; publish-cli.yml rewrites both to the published version.
-export const VERSION = "0.148.1";
+export const VERSION = "0.148.3";
 
 // Flags that never take a value. Listing them explicitly means `deploy get --json <id>`
 // can't accidentally swallow the id as --json's value. Every `type: "bool"` flag (and its
 // `negate` spelling) in a command's ARGS map must be listed; boolean-flags.test.ts enforces it.
 export const BOOLEAN_FLAGS = new Set([
+	// build: repeat an open build's ask; post its progress in the org's Slack channel.
+	"again",
+	"notify-slack",
 	"remap",
+	// site observations: each kind noticed, not the observations (keys_only).
+	"keys",
 	// login: one-link device sign-in instead of the loopback browser flow.
 	"device",
 	"json",
@@ -361,7 +367,7 @@ function buildHelp(bin) {
 	const heading =
 		bin === "phantom"
 			? "👻 phantom — deploy and manage Phantomstory blogs from your terminal"
-			: "letterstory — spin up and manage Letterstory phantom blogs from your terminal";
+			: "letterstory — spin up and manage Letter phantom blogs from your terminal";
 	return `${heading}
 
 Usage:
@@ -406,7 +412,7 @@ Collections (the content engine as a primitive — one door, 'collection run'):
   collection links <id> [--refresh]                    Internal-link refresh: on/off, posts due (--refresh runs the next batch now)
   collection delete <id> --yes
 
-Phantomstory (a collection Letterstory hosts as an independent publication):
+Phantomstory (a collection Letter hosts as an independent publication):
   phantom list                                         Your phantoms (metered in SITES live at once)
   phantom new --name <n> [--description <t>] [--theme <t>] [--collection <id>] [--customer-ref <r>]
               [--no-configure] [--config '<json>'] [--client-domain <d>] [--dry-run] [--no-wait]
@@ -767,7 +773,7 @@ What does this org still need? (the router — reads only, decides nothing):
                                                        Planner, CMS, phantom) with its status:
                                                        done / running / ready / blocked, and what
                                                        a blocked step is waiting on.
-  ${bin === "phantom" ? "onboard" : "phantom-onboard"} next                         The first ready step Letterstory recommends,
+  ${bin === "phantom" ? "onboard" : "phantom-onboard"} next                         The first ready step Letter recommends,
                                                        as the exact command to run next. Optional
                                                        steps are listed, never chosen.
 
@@ -830,7 +836,7 @@ Admin (STAFF key — --staff-key / LETTERSTORY_STAFF_API_KEY; acts before an org
                                                        the queries behind the answer. Needs the
                                                        fleet:query capability on the staff key.
   admin recipes list [--enabled-only] | show <id|name> | vocab [--json]
-                                                       Plan recipes: Letterstory's one global library behind
+                                                       Plan recipes: Letter's one global library behind
                                                        every account's Plan (/superadmin/plan-recipes). vocab
                                                        says what a recipe can say (fields, goals, company
                                                        types, primitives). Needs recipes:read.
@@ -1148,7 +1154,7 @@ no endpoint, no run. Applied on phantom create --composition '{"key":"..."}'):
   compositions resolve <composition-key>                Preview what create_phantom would
                                                        merge in — read-only, costs nothing.
 
-Shredder (diversify content produced outside Letterstory; structure preserved):
+Shredder (diversify content produced outside Letter; structure preserved):
   shredder list                                        Your shredder endpoints + run counts
   shredder create --name <n>                           New endpoint (returns a callable public id)
   shredder delete <endpoint-id> --yes
@@ -1353,7 +1359,7 @@ Mail:
   mail postal-address "<address>"                      Set the org's CAN-SPAM mailing address (email footers)
   mail vercel-key set (--token <t> | --token-file <path|->) [--team <team_id>]
                                                        Buy and own mail domains on your Vercel account / team
-  mail vercel-key remove --yes                         Future purchases go back to Letterstory's account
+  mail vercel-key remove --yes                         Future purchases go back to Letter's account
   mail registrant --first-name <f> --last-name <l> --email <e> --phone "(415) 555-1234"
            --address <a> [--address2 <a>] --city <c> --state <s> --zip <z> --country "United States" [--company <c>]
                                                        WHOIS registrant for purchases on your Vercel key
@@ -1378,6 +1384,17 @@ Insights:
                                                        Page access: who's reading your phantom sites
   insights activity [--phantom <uuid>] [--limit <n>]   What hit your phantom sites in the last 7 days, newest first
 
+Build (a change to your site, or launching what isn't code; the Build box's own door):
+  build <words…> [--prompt <text>] [--site <host>] [--subject <host/path>]... [--action build|build_pr|build_merge|slack|linear]
+             [--attach <path>]... [--attach-url <name>=<https url>]... [--attach-ref <path>]... [--attach-url-ref <name>=<https url>]...
+             [--harness claude-code|letterpress-1] [--notify-slack] [--again]
+                                                       Build from your words: "add a pricing page" opens a preview or PR;
+                                                       "launch a phantom for us", "set up mailers" or "onboard my blog" is
+                                                       done by Build itself (a phantom site buys its own domain), and the
+                                                       build reads Done with no PR to merge. --again repeats an open build's ask
+  build talk <words…> [--conversation <id>|--build <id>] [--site <host>] [--harness claude-code|letterpress-1]
+                                                       One turn of a conversation with Build (questions, follow-ups on a build)
+
 The Site (one model of your whole marketing site, keyed by host and path):
   site list                                            Mapped hosts, and hosts you already have elsewhere
   site map <host> [--sitemap <url>] [--max-pages <n>] [--no-audit] [--relation owned|watched]
@@ -1388,7 +1405,7 @@ The Site (one model of your whole marketing site, keyed by host and path):
   site tree <host> [path] [--depth <n>] [--unfold] [--since <iso>]
                                                        The tree one folder at a time; --since adds +N/-N per folder
   site page <host> <path>                              One page: facts, bindings, raw URLs, open items
-  site observations <host> [path] [--state open|dismissed|resolved] [--tone risk|warn|info] [--key <k>] [--since <iso>] [--min-reach <0..1>]
+  site observations <host> [path] [--state open|dismissed|resolved] [--tone risk|warn|info] [--key <k>] [--since <iso>] [--min-reach <0..1>] [--keys]
   site observe <host> [path] [--max-pages <n>]         Jev pass: meta accuracy, title, outdated
   site dismiss <host> <observation-id> --reason <why> [--kind not_relevant|already_handled|wrong|later] [--decision dismiss|reopen]
   site families <host> [path] [--state suggested|tracked|dismissed]
@@ -1405,8 +1422,8 @@ The Site (one model of your whole marketing site, keyed by host and path):
   site watch-competitors [domain] [--limit <n>]        Map competitors' sitemaps (the next few unmapped, or one now)
   site highlight <domain> [--off]                      Highlight a competitor; its changes lead the top changes
 
-Repo changes (Claude Code edits your repo in a sandbox; the Letterstory GitHub App opens a PR):
-  repo repos                                           Repos the Letterstory GitHub App can reach
+Repo changes (Claude Code edits your repo in a sandbox; the Letter GitHub App opens a PR):
+  repo repos                                           Repos the Letter GitHub App can reach
   repo branches --repo owner/name                      Branches a change can start from (default first)
   repo prs [--repo owner/name]                         Every open PR (whoever opened it), longest-idle first
   repo suggestions                                     Fixes found and not acted on yet, and how to start each
@@ -1587,6 +1604,7 @@ const CLIENT_COMMANDS = {
 	mailers: cmdMailers,
 	feedback: cmdFeedback,
 	repo: cmdRepo,
+	build: cmdBuild,
 	site: cmdSite,
 	evals: cmdEvals,
 	visits: cmdVisits,

package/lib/client.mjs

@@ -1,4 +1,4 @@
-// The Letterstory CLI's transport: a thin JSON-RPC client over the MCP endpoint
+// The Letter CLI's transport: a thin JSON-RPC client over the MCP endpoint
 // (POST /api/mcp), plus config resolution. The CLI wraps the same tool manifest an
 // agent sees, so it stays in sync with the server by construction — there is no
 // second copy of the surface here, only ergonomic wrappers around tools/call.

package/lib/commands/admin.mjs

@@ -5097,7 +5097,7 @@ function recipeFromFlags(flags) {
 }
 
 /**
- * `admin recipes …` — the Plan recipes page (/superadmin/plan-recipes) for an agent: Letterstory's
+ * `admin recipes …` — the Plan recipes page (/superadmin/plan-recipes) for an agent: Letter's
  * one global library of recipes behind every account's Plan. The loop for building it out is
  * `vocab` (what a recipe can say) → `export --out recipes.json` → edit → `import recipes.json
  * --dry-run` → `import recipes.json`. Reads need recipes:read on the staff key, writes
@@ -5207,7 +5207,7 @@ const LAGO = "/api/superadmin/billing/lago";
 const LAGO_USAGE = `Usage: admin billing lago <command>
   catalog [--apply] [--include-drafts]   what the plan catalog would change in Lago; --apply makes it so
   provision <org-id> --plan starter [--ratio 4] [--why "…" above 4x] [--complimentary 20000] [--stripe-customer cus_…] [--start 2026-11-02T00:00:00Z] [--review 2027-05-01]
-  reconcile [--org <org-id>]             Lago's tokens this period against what we rated and forwarded
+  reconcile [--org <org-id>]             Lago's tokens this period and last invoice against what we forwarded
   forward                                forward billable usage to Lago now (the cron's pass)
   payments [--org <org-id>] [--open]     failed payments and what the retry loop did about each
   payments retry <lago-invoice-id>       charge one failed invoice again now
@@ -5266,7 +5266,10 @@ async function cmdAdminBilling(ctx) {
 		case "reconcile": {
 			const params = new URLSearchParams(compact({ orgId: flagStr(flags.org) }));
 			const result = await staffRequest(ctx, "GET", `${LAGO}/reconcile${params.size ? `?${params}` : ""}`);
-			ok(ctx, result.ok ? "Lago agrees with us." : "Lago and we disagree: see the orgs below.");
+			ok(
+				ctx,
+				result.summary ?? (result.ok ? "Lago agrees with us." : "Lago and we disagree: see the orgs below.")
+			);
 			printResult(io, flags, result);
 			return result.ok ? 0 : 1;
 		}
@@ -5274,7 +5277,9 @@ async function cmdAdminBilling(ctx) {
 			const result = await staffPost(ctx, `${LAGO}/forward`, {});
 			ok(
 				ctx,
-				`Sent ${result.sent}, already there ${result.duplicates}, held ${result.held}, refused ${result.refused}.`
+				`Sent ${result.sent}, already there ${result.duplicates}, held ${result.held}, refused ${result.refused}` +
+					`${result.swept ? `, ${result.swept} found behind the cursor` : ""}` +
+					`${result.late ? `, ${result.late} for a closed period (billed only if its invoice was not out yet)` : ""}.`
 			);
 			printResult(io, flags, result);
 			return 0;

package/lib/commands/auth.mjs

@@ -18,7 +18,7 @@ export async function cmdLogin(ctx) {
 	if (key) {
 		if (!key.startsWith("ls_") && !key.startsWith("lb_")) {
 			io.error(
-				"Warning: Letterstory API keys usually start with 'ls_' (legacy keys start with 'lb_'). Saving anyway."
+				"Warning: Letter API keys usually start with 'ls_' (legacy keys start with 'lb_'). Saving anyway."
 			);
 		}
 		const saved = { key, ...(flagStr(flags.url) ? { url } : {}) };

package/lib/commands/build.mjs

@@ -0,0 +1,99 @@
+// `build` — Build from words, the way the Build box and the letterpress terminal do it
+// (src/lib/growth-builds/start-build.ts). What the words name is done: a change to the site
+// becomes a preview or a pull request, and launching phantom sites or mailers, or onboarding the
+// main blog, is carried out by Build itself with nothing to merge.
+//   build <words…>          → start_build         (--prompt for a long ask; --again to repeat one)
+//   build talk <words…>     → send_build_message  (--conversation <id> | --build <id> to continue)
+
+import { CliError } from "../client.mjs";
+import { argsFromFlags, flagList, flagStr, ok, printResult, refuseUnknownFlags } from "./shared.mjs";
+import { attachmentUrls, uploadAttachments } from "./repo.mjs";
+
+const ARGS = {
+	start_build: {
+		// The words after `build`, or --prompt for a longer ask.
+		prompt: { value: (flags, positionals) => flagStr(flags.prompt) ?? (positionals.join(" ").trim() || undefined) },
+		domain: "site",
+		// --subject host/path (repeatable): the pages it is about.
+		subjects: { flag: "subject", type: "list" },
+		// --attach <path> (uploaded first) and --attach-url <name>=<https url>, both repeatable;
+		// -ref ones are context the agent reads, never put in the repo.
+		files: { value: (_flags, _positionals, extra) => (extra.files?.length ? extra.files : undefined) },
+		delivery: { flag: "action", enum: ["build", "build_pr", "build_merge", "slack", "linear"] },
+		notify_slack: { flag: "notify-slack", type: "bool" },
+		harness: { flag: "harness", enum: ["claude-code", "letterpress-1"] },
+		again: { flag: "again", type: "bool" },
+	},
+	send_build_message: {
+		message: {
+			value: (flags, positionals) => flagStr(flags.message) ?? (positionals.join(" ").trim() || undefined),
+		},
+		conversation_id: "conversation",
+		build_id: "build",
+		domain: "site",
+		subjects: { flag: "subject", type: "list" },
+		files: { value: (_flags, _positionals, extra) => (extra.files?.length ? extra.files : undefined) },
+		harness: { flag: "harness", enum: ["claude-code", "letterpress-1"] },
+	},
+};
+
+const FILE_FLAGS = ["attach", "attach-url", "attach-ref", "attach-url-ref"];
+
+/** The files named by --attach / --attach-url (and their -ref forms), uploaded first. */
+async function attachedFiles(ctx) {
+	const { flags } = ctx;
+	const place = flagList(flags.attach);
+	const uploaded = await uploadAttachments(ctx, [...place, ...flagList(flags["attach-ref"])]);
+	return [
+		...uploaded.map((f, i) => (i < place.length ? f : { ...f, reference: true })),
+		...attachmentUrls(flagList(flags["attach-url"])),
+		...attachmentUrls(flagList(flags["attach-url-ref"])).map((f) => ({ ...f, reference: true })),
+	];
+}
+
+export async function cmdBuild(ctx) {
+	if (ctx.positionals[0] === "talk") return buildTalk({ ...ctx, positionals: ctx.positionals.slice(1) });
+	return buildStart(ctx);
+}
+
+async function buildStart(ctx) {
+	const { client, flags, io } = ctx;
+	refuseUnknownFlags(ctx, {}, [
+		"prompt",
+		"site",
+		"subject",
+		"action",
+		"notify-slack",
+		"harness",
+		"again",
+		...FILE_FLAGS,
+	]);
+	const files = await attachedFiles(ctx);
+	const args = argsFromFlags(ARGS.start_build, flags, ctx.positionals, { files });
+	if (!args.prompt) throw new CliError('Say what to build: letterstory build "launch a phantom for us"');
+	const result = await client.callTool("start_build", args);
+	printResult(io, flags, result, (r) => {
+		if (r.status !== "started") return r.message ?? r.status;
+		const steps = (r.build?.steps ?? []).map((s) => `  ${s.status}  ${s.title}${s.note ? `: ${s.note}` : ""}`);
+		return [`Started: ${r.build.title}  (${r.build.id})`, ...steps].join("\n");
+	});
+	if (result.status !== "started" && !flags.json) ok(ctx, "Nothing was started.");
+	return 0;
+}
+
+async function buildTalk(ctx) {
+	const { client, flags, io } = ctx;
+	refuseUnknownFlags(ctx, {}, ["message", "conversation", "build", "site", "subject", "harness", ...FILE_FLAGS]);
+	const files = await attachedFiles(ctx);
+	const args = argsFromFlags(ARGS.send_build_message, flags, ctx.positionals, { files });
+	if (!args.message) throw new CliError('Say something: letterstory build talk "make the hero darker"');
+	const result = await client.callTool("send_build_message", args);
+	printResult(io, flags, result, (r) =>
+		[r.reply, ...(r.questions ?? []).map((q) => `? ${q.question}`), r.build ? `Build: ${r.build.id}` : null]
+			.filter(Boolean)
+			.join("\n")
+	);
+	return 0;
+}
+
+export { ARGS };

package/lib/commands/collection.mjs

@@ -2,7 +2,7 @@
 //
 // A collection is a publication with a one-file configuration that produces and publishes
 // posts on a cadence; `collection run` produces ONE post on it (sourced, written, gated,
-// published, and — when Letterstory hosts the site — rebuilt). Runs are 20–60 minutes, so
+// published, and — when Letter hosts the site — rebuilt). Runs are 20–60 minutes, so
 // `collection run` submits and then follows the run unless you tell it not to
 // (`--no-wait`); `collection run-status` picks it up later. A direct run spends the
 // collection's weekly cadence budget (its posts_per_week); the planner's own slots are the

package/lib/commands/feedback.mjs

@@ -1,4 +1,4 @@
-// `feedback` — submit product feedback about Letterstory itself: a bug, something
+// `feedback` — submit product feedback about Letter itself: a bug, something
 // missing, something unclear, a feature request, or praise. One subcommand, one tool
 // (submit_feedback) — there is no read/list surface yet, staff triage this table directly.
 

package/lib/commands/mcp.mjs

@@ -1,4 +1,4 @@
-// `mcp` — print ready-to-paste configuration for wiring the Letterstory MCP server
+// `mcp` — print ready-to-paste configuration for wiring the Letter MCP server
 // into an agent (Claude Code, Claude Desktop, Cursor, …). Same endpoint/auth header
 // the CLI itself uses (see client.mjs's `mcpEndpoint` / `x-integrations-key`), just
 // packaged for copy-paste instead of for this process's own requests.
@@ -30,7 +30,7 @@ export function cmdMcp(ctx) {
 
 	const masked = config.key ? `${config.key.slice(0, 6)}…${config.key.slice(-4)}` : undefined;
 
-	io.log(`Letterstory MCP`);
+	io.log(`Letter MCP`);
 	io.log(`  endpoint:  ${endpoint}`);
 	io.log(`  transport: streamable-http`);
 	io.log(`  auth:      ${header}: ${masked ?? "(no key found — run `" + ctx.bin + " login` first)"}`);

package/lib/commands/onboard.mjs

@@ -760,7 +760,7 @@ async function cmdOnboardNext(ctx) {
 	return 0;
 }
 
-// `onboard primitives [<domain>]` — what Letterstory would stand up for this company: one
+// `onboard primitives [<domain>]` — what Letter would stand up for this company: one
 // read of propose_primitive_plan, printed item by item with the org-config record each one
 // stands for. Nothing runs; the plan is applied with `org apply`.
 // A first read crawls the site; `pending` means one is already in flight, so wait and ask.

package/lib/commands/outbound.mjs

@@ -810,7 +810,7 @@ export async function cmdMail(ctx) {
 			if (action === "remove") {
 				if (!inner.flags.yes) {
 					ctx.io.error(
-						`Removing the key sends future purchases back to Letterstory's account and drops the registrant contact. Re-run with --yes to confirm: ${ctx.bin} mail vercel-key remove --yes`
+						`Removing the key sends future purchases back to Letter's account and drops the registrant contact. Re-run with --yes to confirm: ${ctx.bin} mail vercel-key remove --yes`
 					);
 					return 1;
 				}

package/lib/commands/phantom.mjs

@@ -1,4 +1,4 @@
-// `phantom` — Phantomstory: a collection Letterstory hosts as an independent publication.
+// `phantom` — Phantomstory: a collection Letter hosts as an independent publication.
 //
 // Hosting only: the site, its identity and theme, its domain, its rebuilds, its balance.
 // Publishing a post to it is `collection run --collection <its collection_id>`; its

package/lib/commands/repo.mjs

@@ -1,5 +1,5 @@
 // `repo` — changes to the org's own repos, made by Claude Code in a sandbox and opened as a
-// pull request by the Letterstory GitHub App (src/lib/repo-changes). One subcommand per tool:
+// pull request by the Letter GitHub App (src/lib/repo-changes). One subcommand per tool:
 //   repo start   → start_repo_change     repo status → get_repo_change
 //   repo activity → get_repo_change_activity (what the sandbox is doing; --follow polls)
 //   repo list    → list_repo_changes     repo cancel → cancel_repo_change
@@ -347,7 +347,7 @@ export async function cmdRepo(ctx) {
 }
 
 /** `--attach-url name=https://…` → `{ name, url }`. */
-function attachmentUrls(specs) {
+export function attachmentUrls(specs) {
 	return specs.map((spec) => {
 		const at = spec.indexOf("=");
 		if (at < 1) throw new CliError(`--attach-url must be name=https://… (got ${spec})`);
@@ -356,7 +356,7 @@ function attachmentUrls(specs) {
 }
 
 /** Reserve an upload per --attach file, PUT the bytes, and return `{ name, upload_path }` for each. */
-async function uploadAttachments(ctx, paths) {
+export async function uploadAttachments(ctx, paths) {
 	if (!paths.length) return [];
 	const names = paths.map((p) =>
 		basename(p)
@@ -711,7 +711,7 @@ async function repoRepos(ctx) {
 	return 0;
 }
 
-/** `repo prs [--repo owner/name]`: every open PR, longest-idle first, and which Letterstory opened. */
+/** `repo prs [--repo owner/name]`: every open PR, longest-idle first, and which Letter opened. */
 async function repoPrs(ctx) {
 	const { client, flags, io } = ctx;
 	refuseUnknownFlags(ctx, {}, ["repo"]);
@@ -722,7 +722,7 @@ async function repoPrs(ctx) {
 			: r.pullRequests
 					.map(
 						(p) =>
-							`${p.repo}#${p.number}  ${p.title}  (${p.daysSinceUpdate}d idle${p.draft ? ", draft" : ""}${p.letterRun ? `, Letterstory run ${p.letterRun.status}` : ""})\n  ${p.url}`
+							`${p.repo}#${p.number}  ${p.title}  (${p.daysSinceUpdate}d idle${p.draft ? ", draft" : ""}${p.letterRun ? `, Letter run ${p.letterRun.status}` : ""})\n  ${p.url}`
 					)
 					.join("\n")
 	);

package/lib/commands/shredder.mjs

@@ -1,4 +1,4 @@
-// `shredder` — create shredder endpoints and run content produced OUTSIDE Letterstory
+// `shredder` — create shredder endpoints and run content produced OUTSIDE Letter
 // through the cross-provider shredder. A shred rewrites each sentence across multiple
 // LLM providers to diversify, leaving structure (headings, lists, tables) untouched, and
 // logs every call to telemetry against the org's shred balance.

package/lib/commands/sim.mjs

@@ -6,7 +6,7 @@
 //   letterstory sim create --name "Attio API" --spec-url https://api.attio.com/openapi/api
 //   letterstory sim show <id>
 //   letterstory sim rule <id> /v2/webhooks sink --note "never call real endpoints"
-//   letterstory sim create --name "Letterstory" --tools-file tools.json --tool-route "/api/integrations/tools/{name}"
+//   letterstory sim create --name "Letter" --tools-file tools.json --tool-route "/api/integrations/tools/{name}"
 //   letterstory sim key <id> --agent our-ci --goal "nightly integration test"
 //   letterstory sim seed <id> --prompt "a 3-person content team with two blogs" --activate
 //   letterstory sim seed <id> --use <seed-id|none>

package/lib/commands/site.mjs

@@ -133,6 +133,7 @@ const ARGS = {
 		since: "since",
 		min_reach: { flag: "min-reach", type: "num" },
 		limit: { flag: "limit", type: "num" },
+		keys_only: { flag: "keys", type: "bool" },
 	},
 	observe_site: {
 		host: { positional: 0, required: true, label: "host" },

package/lib/commands.mjs

@@ -44,6 +44,7 @@ export * from "./commands/targets.mjs";
 export * from "./commands/admin.mjs";
 export * from "./commands/feedback.mjs";
 export * from "./commands/repo.mjs";
+export * from "./commands/build.mjs";
 export * from "./commands/site.mjs";
 export * from "./commands/evals.mjs";
 export * from "./commands/visits.mjs";

package/lib/oauth.mjs

@@ -1,5 +1,5 @@
 // Browser-based OAuth 2.1 login (RFC 8252 loopback redirect + PKCE) for the
-// Letterstory CLI. This talks to the app's own /api/oauth/* endpoints — see
+// Letter CLI. This talks to the app's own /api/oauth/* endpoints — see
 // src/lib/oauth/core.ts on the server side for the matching implementation.
 
 import { randomBytes, createHash } from "node:crypto";
@@ -38,12 +38,12 @@ function openBrowser(url) {
 	}
 }
 
-const CALLBACK_HTML_OK = `<!doctype html><html><head><title>Letterstory CLI</title></head>
+const CALLBACK_HTML_OK = `<!doctype html><html><head><title>Letter CLI</title></head>
 <body style="font-family: system-ui, sans-serif; max-width: 28rem; margin: 4rem auto; text-align: center;">
 <h2>You're signed in.</h2><p>You can close this tab and return to your terminal.</p>
 </body></html>`;
 
-const CALLBACK_HTML_ERROR = `<!doctype html><html><head><title>Letterstory CLI</title></head>
+const CALLBACK_HTML_ERROR = `<!doctype html><html><head><title>Letter CLI</title></head>
 <body style="font-family: system-ui, sans-serif; max-width: 28rem; margin: 4rem auto; text-align: center;">
 <h2>Sign-in failed.</h2><p>Return to your terminal for details.</p>
 </body></html>`;

package/package.json

@@ -1,10 +1,10 @@
 {
 	"name": "@letterstory/cli",
-	"version": "0.148.1",
-	"description": "Spin up and manage Letterstory phantom blogs from your terminal.",
+	"version": "0.148.3",
+	"description": "Spin up and manage Letter phantom blogs from your terminal.",
 	"type": "module",
 	"license": "UNLICENSED",
-	"author": "Letterstory",
+	"author": "Letter",
 	"homepage": "https://github.com/letterstory/letterstory/tree/main/cli#readme",
 	"repository": {
 		"type": "git",