@thallylabs/cli 0.8.14 → 0.8.16

package/README.md

@@ -5,30 +5,35 @@ One tool, one mental model. You author **content + config**; the framework
 
 ## The model
 
-A Thally project is just three things you own:
+You own the portable content and configuration surfaces:
 
-- `src/content/` — your MDX pages
-- `docs.json` — navigation, theme, and config
+- `src/content/` — MDX pages
+- `docs.json` — navigation, theme, and product configuration
+- `src/data/site.ts` — site identity, links, and brand defaults
+- `src/mdx/custom-components.tsx` — customer MDX components
 - `snippets/` — reusable MDX
+- `public/` and `openapi.yaml` — public assets and API specifications
 
-Everything under `src/app/` is framework plumbing managed by Thally. You should
-never need to edit it. The `thally` commands wrap the framework so the runtime
-stays invisible.
+Framework-owned paths are recorded in `starter-release.json` and managed by
+Thally. `src/app/` is framework plumbing, but it is not the complete ownership
+contract. The `thally` commands keep the runtime invisible while preserving
+customer-owned paths during upgrades.
 
 ## Commands
 
-| Command | What it does |
-| --- | --- |
-| `thally init [dir]` | Scaffold a new Thally project |
-| `thally dev` | Run the docs site locally (agent endpoints live) |
-| `thally build` | Build the production site |
-| `thally start` | Serve the built production site |
-| `thally deploy [--prod]` | Build and deploy to a live URL, print agent endpoints |
-| `thally check [--agents] [--fix]` | Lint content + Agent Readiness Score |
-| `thally new <page-id> [--title]` | Create a page and register it in `docs.json` |
-| `thally migrate <github-or-docs-url> [dir]` | Migrate a docs repository or public docs site |
-| `thally translate --locale <code>` | Translate content into a locale |
-| `thally mcp` | Start the Model Context Protocol server (stdio) |
+| Command                                     | What it does                                                   |
+| ------------------------------------------- | -------------------------------------------------------------- |
+| `thally init [dir]`                         | Scaffold a new Thally project                                  |
+| `thally dev`                                | Run the docs site locally (agent endpoints live)               |
+| `thally build`                              | Build the production site                                      |
+| `thally start`                              | Serve the built production site                                |
+| `thally deploy [--prod]`                    | Build and deploy to a live URL, print agent endpoints          |
+| `thally check [--agents] [--fix]`           | Lint content + Agent Readiness Score                           |
+| `thally new <page-id> [--title]`            | Create a page and register it in `docs.json`                   |
+| `thally migrate <github-or-docs-url> [dir]` | Migrate a docs repository or public docs site                  |
+| `thally translate --locale <code>`          | Translate content into a locale                                |
+| `thally starter update [--apply]`           | Plan or explicitly apply an immutable three-way runtime update |
+| `thally mcp`                                | Start the Model Context Protocol server (stdio)                |
 
 `thally migrate` asks which platform currently hosts the docs and dispatches to
 the Mintlify or Docusaurus adapter. Non-interactive callers can pass
@@ -36,13 +41,19 @@ the Mintlify or Docusaurus adapter. Non-interactive callers can pass
 
 Run `thally` with no arguments for the full help.
 
+`thally starter update` is a dry run by default. It compares the previously
+recorded scaffold, the promoted target scaffold, and the current project. It
+automatically updates unchanged framework-owned files, preserves user-owned
+paths, and reports manual-review conflicts before `--apply` writes anything.
+
 ## How it works
 
 - **Framework commands** (`dev`, `build`, `start`, `deploy`) prefer the
   project's npm scripts and fall back to invoking the framework directly — so
   the framework is an implementation detail, not part of your surface.
 - **Authoring commands** (`init`, `migrate`, `translate`) delegate to
-  `create-thally-docs`; `mcp` starts `@thallylabs/mcp`. All capabilities are reachable through
-  the single `thally` binary.
+  `create-thally-docs`; `starter update` uses the same immutable scaffold
+  catalog and ownership-aware updater; `mcp` starts `@thallylabs/mcp`. All
+  capabilities are reachable through the single `thally` binary.
 - **`check --agents`** runs content lint plus the Agent Readiness Score, with a
   CI-friendly non-zero exit code when the score is below the threshold.

package/dist/index.js

@@ -53,7 +53,7 @@ function helpText() {
   lines.push("  thally \u2014 keep customer-facing knowledge in sync with product changes");
   lines.push("");
   lines.push("  Connect product evidence, prepare reviewable updates, and publish one trusted source.");
-  lines.push("  You author content/, docs.json, and snippets/.");
+  lines.push("  You author src/content/, docs.json, site.ts, custom MDX, snippets/, and public assets.");
   lines.push("  The framework (Next.js) is a hidden runtime \u2014 you never touch src/app/.");
   lines.push("");
   lines.push("  Usage: thally <command> [options]");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thallylabs/cli",
-  "version": "0.8.14",
+  "version": "0.8.16",
   "description": "The Thally CLI for authoring knowledge surfaces, tracing product changes, and keeping documentation checked.",
   "type": "module",
   "engines": {
@@ -24,8 +24,8 @@
   },
   "dependencies": {
     "@anthropic-ai/sdk": "^0.78.0",
-    "@thallylabs/mcp": "0.10.14",
-    "create-thally-docs": "0.10.13"
+    "@thallylabs/mcp": "0.10.16",
+    "create-thally-docs": "0.10.15"
   },
   "devDependencies": {
     "@thallylabs/agent": "*",