primethink-cli 1.3.2__tar.gz → 1.3.4__tar.gz

{primethink_cli-1.3.2/primethink_cli.egg-info → primethink_cli-1.3.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: primethink-cli
-Version: 1.3.2
+Version: 1.3.4
 Summary: PrimeThink CLI - A powerful tool for interacting with PrimeThink AI API
 Author-email: PrimeThink <support@primethink.ai>
 License-Expression: MIT
@@ -71,6 +71,8 @@ pt chat send --agent AGENT_ID --message "your message"
 | `pt install-skill` | Install the bundled CLI agent skill for Claude Code and compatible agents |
 | `pt install-developer-skill` | Install the complete public PrimeThink developer skill, including nested resources |
 | `pt live-app new` | Scaffold a React or HTML Live App from a GitHub template catalog |
+| `pt live-app publish` | Create/update a Live App task and sync its flat artifact |
+| `pt live-app test` | Sync a Live App into a new or existing chat |
 | `pt profile add` | Configure an API token for a profile |
 | `pt profile use` | Switch the active profile |
 | `pt profile list` | List configured profiles |
@@ -80,6 +82,7 @@ pt chat send --agent AGENT_ID --message "your message"
 | `pt chat create` | Create a new chat |
 | `pt chat rename` | Rename a chat |
 | `pt chat goal` | Update a chat's goal |
+| `pt chat type` | Switch a chat between `live-app` and `chat` mode |
 | `pt chat messages` | List a chat's messages (cursor-paginated) |
 | `pt chat archive` / `pt chat unarchive` | Archive / unarchive a chat |
 | `pt chat delete` | Delete a chat (asks for confirmation; `--yes` to skip) |
@@ -108,7 +111,9 @@ pt chat send --agent AGENT_ID --message "your message"
 | `pt task get` | Fetch a task's details as JSON |
 | `pt task delete` | Delete a task (asks for confirmation; `--yes` to skip) |
 | `pt task duplicate` | Duplicate a task |
-| `pt task publish` / `pt task unpublish` | Make a task public / private |
+| `pt task set-public` / `pt task set-private` | Make a task public / private |
+| `pt task publish` | Create/update a task from a project directory |
+| `pt task test` | Sync a task goal into a new or existing chat |
 | `pt task export` | Export a task's portable config as JSON (for `pt task import`) |
 | `pt task import` | Create a new task from an exported JSON file (deploy across environments with `--profile`) |
 | `pt task create-version` | Snapshot a task's current state as a named version |
@@ -121,6 +126,8 @@ pt chat send --agent AGENT_ID --message "your message"
 
 Every command that calls the API also accepts `--profile` (use a specific profile for one request) and `--api-url`/`-u` (override the API URL for one request). See the [full CLI reference](docs/cli-reference.md) for every option and example.
 
+`--help` works in either position: `pt chat send --help`, `pt chat --help send`, and `pt --help chat send` all print the same page.
+
 > **Tip:** `-p` is the short flag for `--profile` in the `pt task`, `pt agent`, and `pt search` groups, `pt image generate`, and `pt whoami`, but in the `pt chat` and `pt collection` groups there is no `-p` for profile — there `-p` means `--path` (a directory inside the chat/collection) on the file commands. Use the long form `--profile` when in doubt.
 
 ## Configuration
@@ -287,13 +294,23 @@ pt task upload-image 99 ./cover.png
 pt task export 99 --output tasks/briefing.json
 pt task import tasks/briefing.json --profile production
 
+# Publish a conventional task project (GOAL.md required); pass an ID to update
+pt task publish ./tasks/briefing --virtual-assistant-id 7
+pt task publish ./tasks/briefing --task-id 99 --virtual-assistant-id 7
+
+# Make the resulting task public/private, or test its goal in a chat
+pt task set-public 99
+pt task set-private 99
+pt task test ./tasks/briefing
+pt task test ./tasks/briefing --chat-id EXISTING_CHAT_ID
+
 # Generate an image with AI
 pt image generate --prompt "A lighthouse at dawn" --output lighthouse.png
 ```
 
-## Live App Scaffolding
+## Live App Workflows
 
-Create a new Live App project without configuring an API profile:
+Scaffold a new Live App project without configuring an API profile:
 
 ```bash
 # Default: React + Tailwind + Flowbite
@@ -309,13 +326,33 @@ pt live-app new ./my-live-app \
   --ref v2.0.0
 ```
 
-The destination must not already exist. Flowbite requires Tailwind. The command downloads a public GitHub repository and selects a template from `live-app-templates/manifest.json`; it never runs `npm install` or any generated code. Read the generated `README.md` for preview, build, and deployment instructions.
+The destination must not already exist. Flowbite requires Tailwind. The command downloads a public GitHub repository and selects a template from `live-app-templates/manifest.json`; it never runs `npm install` or generated code.
+
+After building, publish the Live App as a task or synchronize it directly into a test chat. Artifact discovery checks `dist/`, then `app/`, then the project root; use `--app-dir` to override it. The artifact must contain `index.html` (or `canvas.html`, deployed as `index.html`) and should be flat.
+
+```bash
+# Create a Live App task; add --task-id 123 to update it
+pt live-app publish ./my-live-app --virtual-assistant-id 7
+pt live-app publish ./my-live-app --task-id 123 --virtual-assistant-id 7
+
+# Create a temporary test chat, or update an existing chat in place
+pt live-app test ./my-live-app
+pt live-app test ./my-live-app --chat-id EXISTING_CHAT_ID
+
+# Change any chat's renderer explicitly
+pt chat type EXISTING_CHAT_ID live-app
+pt chat type EXISTING_CHAT_ID chat
+```
+
+Project metadata follows the reference-script conventions: `.name.config`, `.description.config`, `GOAL.md`, and optional `INITIAL_PROMPT.md`; `.image.png` is uploaded when publishing a Live App. Existing same-named app documents receive a new `Production` version, while identical content is reported as unchanged.
+
+Automated Live App UI testing is no longer a `pt` command. It now lives in the `primethink-developer` skill as a deterministic, plan-driven workflow: the skill authors a reviewable `tests/test_plan.yaml`, runs it with a bundled Playwright runner (no LLM in the execution loop), reads the structured results, and heals failing selectors before re-running. Install it with `pt install-developer-skill`.
 
 ## MCP Server
 
 The same code that powers the `pt` CLI can run as an [MCP](https://modelcontextprotocol.io)
-server, exposing every API command as a tool that MCP clients (Claude Code,
-Claude Desktop, and others) can call directly — no shelling out to `pt`.
+server, exposing the core PrimeThink API management operations as tools for MCP clients (Claude Code,
+Claude Desktop, and others) to call directly — no shelling out to `pt`. Local scaffolding and project publish/test orchestration remain CLI workflows.
 
 The MCP SDK is an optional dependency, so CLI-only installs stay lean:
 
@@ -342,8 +379,8 @@ example (Claude Desktop / Claude Code `mcpServers` config):
 
 Without `PRIMETHINK_TOKEN` in the client config, the server falls back to your
 configured active profile (`~/.primethink/config.json`); individual tools also
-accept optional `profile` and `api_url` arguments. Every CLI command has a tool
-equivalent — messaging, chats, collections, tasks, agents, semantic search, and
+accept optional `profile` and `api_url` arguments. Core API management operations have tool
+equivalents — messaging, chats, collections, tasks, agents, semantic search, and
 image generation. See the [CLI reference](docs/cli-reference.md#mcp-server-pt-mcp)
 for the full tool list.
 

{primethink_cli-1.3.2 → primethink_cli-1.3.4}/README.md

@@ -37,6 +37,8 @@ pt chat send --agent AGENT_ID --message "your message"
 | `pt install-skill` | Install the bundled CLI agent skill for Claude Code and compatible agents |
 | `pt install-developer-skill` | Install the complete public PrimeThink developer skill, including nested resources |
 | `pt live-app new` | Scaffold a React or HTML Live App from a GitHub template catalog |
+| `pt live-app publish` | Create/update a Live App task and sync its flat artifact |
+| `pt live-app test` | Sync a Live App into a new or existing chat |
 | `pt profile add` | Configure an API token for a profile |
 | `pt profile use` | Switch the active profile |
 | `pt profile list` | List configured profiles |
@@ -46,6 +48,7 @@ pt chat send --agent AGENT_ID --message "your message"
 | `pt chat create` | Create a new chat |
 | `pt chat rename` | Rename a chat |
 | `pt chat goal` | Update a chat's goal |
+| `pt chat type` | Switch a chat between `live-app` and `chat` mode |
 | `pt chat messages` | List a chat's messages (cursor-paginated) |
 | `pt chat archive` / `pt chat unarchive` | Archive / unarchive a chat |
 | `pt chat delete` | Delete a chat (asks for confirmation; `--yes` to skip) |
@@ -74,7 +77,9 @@ pt chat send --agent AGENT_ID --message "your message"
 | `pt task get` | Fetch a task's details as JSON |
 | `pt task delete` | Delete a task (asks for confirmation; `--yes` to skip) |
 | `pt task duplicate` | Duplicate a task |
-| `pt task publish` / `pt task unpublish` | Make a task public / private |
+| `pt task set-public` / `pt task set-private` | Make a task public / private |
+| `pt task publish` | Create/update a task from a project directory |
+| `pt task test` | Sync a task goal into a new or existing chat |
 | `pt task export` | Export a task's portable config as JSON (for `pt task import`) |
 | `pt task import` | Create a new task from an exported JSON file (deploy across environments with `--profile`) |
 | `pt task create-version` | Snapshot a task's current state as a named version |
@@ -87,6 +92,8 @@ pt chat send --agent AGENT_ID --message "your message"
 
 Every command that calls the API also accepts `--profile` (use a specific profile for one request) and `--api-url`/`-u` (override the API URL for one request). See the [full CLI reference](docs/cli-reference.md) for every option and example.
 
+`--help` works in either position: `pt chat send --help`, `pt chat --help send`, and `pt --help chat send` all print the same page.
+
 > **Tip:** `-p` is the short flag for `--profile` in the `pt task`, `pt agent`, and `pt search` groups, `pt image generate`, and `pt whoami`, but in the `pt chat` and `pt collection` groups there is no `-p` for profile — there `-p` means `--path` (a directory inside the chat/collection) on the file commands. Use the long form `--profile` when in doubt.
 
 ## Configuration
@@ -253,13 +260,23 @@ pt task upload-image 99 ./cover.png
 pt task export 99 --output tasks/briefing.json
 pt task import tasks/briefing.json --profile production
 
+# Publish a conventional task project (GOAL.md required); pass an ID to update
+pt task publish ./tasks/briefing --virtual-assistant-id 7
+pt task publish ./tasks/briefing --task-id 99 --virtual-assistant-id 7
+
+# Make the resulting task public/private, or test its goal in a chat
+pt task set-public 99
+pt task set-private 99
+pt task test ./tasks/briefing
+pt task test ./tasks/briefing --chat-id EXISTING_CHAT_ID
+
 # Generate an image with AI
 pt image generate --prompt "A lighthouse at dawn" --output lighthouse.png
 ```
 
-## Live App Scaffolding
+## Live App Workflows
 
-Create a new Live App project without configuring an API profile:
+Scaffold a new Live App project without configuring an API profile:
 
 ```bash
 # Default: React + Tailwind + Flowbite
@@ -275,13 +292,33 @@ pt live-app new ./my-live-app \
   --ref v2.0.0
 ```
 
-The destination must not already exist. Flowbite requires Tailwind. The command downloads a public GitHub repository and selects a template from `live-app-templates/manifest.json`; it never runs `npm install` or any generated code. Read the generated `README.md` for preview, build, and deployment instructions.
+The destination must not already exist. Flowbite requires Tailwind. The command downloads a public GitHub repository and selects a template from `live-app-templates/manifest.json`; it never runs `npm install` or generated code.
+
+After building, publish the Live App as a task or synchronize it directly into a test chat. Artifact discovery checks `dist/`, then `app/`, then the project root; use `--app-dir` to override it. The artifact must contain `index.html` (or `canvas.html`, deployed as `index.html`) and should be flat.
+
+```bash
+# Create a Live App task; add --task-id 123 to update it
+pt live-app publish ./my-live-app --virtual-assistant-id 7
+pt live-app publish ./my-live-app --task-id 123 --virtual-assistant-id 7
+
+# Create a temporary test chat, or update an existing chat in place
+pt live-app test ./my-live-app
+pt live-app test ./my-live-app --chat-id EXISTING_CHAT_ID
+
+# Change any chat's renderer explicitly
+pt chat type EXISTING_CHAT_ID live-app
+pt chat type EXISTING_CHAT_ID chat
+```
+
+Project metadata follows the reference-script conventions: `.name.config`, `.description.config`, `GOAL.md`, and optional `INITIAL_PROMPT.md`; `.image.png` is uploaded when publishing a Live App. Existing same-named app documents receive a new `Production` version, while identical content is reported as unchanged.
+
+Automated Live App UI testing is no longer a `pt` command. It now lives in the `primethink-developer` skill as a deterministic, plan-driven workflow: the skill authors a reviewable `tests/test_plan.yaml`, runs it with a bundled Playwright runner (no LLM in the execution loop), reads the structured results, and heals failing selectors before re-running. Install it with `pt install-developer-skill`.
 
 ## MCP Server
 
 The same code that powers the `pt` CLI can run as an [MCP](https://modelcontextprotocol.io)
-server, exposing every API command as a tool that MCP clients (Claude Code,
-Claude Desktop, and others) can call directly — no shelling out to `pt`.
+server, exposing the core PrimeThink API management operations as tools for MCP clients (Claude Code,
+Claude Desktop, and others) to call directly — no shelling out to `pt`. Local scaffolding and project publish/test orchestration remain CLI workflows.
 
 The MCP SDK is an optional dependency, so CLI-only installs stay lean:
 
@@ -308,8 +345,8 @@ example (Claude Desktop / Claude Code `mcpServers` config):
 
 Without `PRIMETHINK_TOKEN` in the client config, the server falls back to your
 configured active profile (`~/.primethink/config.json`); individual tools also
-accept optional `profile` and `api_url` arguments. Every CLI command has a tool
-equivalent — messaging, chats, collections, tasks, agents, semantic search, and
+accept optional `profile` and `api_url` arguments. Core API management operations have tool
+equivalents — messaging, chats, collections, tasks, agents, semantic search, and
 image generation. See the [CLI reference](docs/cli-reference.md#mcp-server-pt-mcp)
 for the full tool list.
 

{primethink_cli-1.3.2 → primethink_cli-1.3.4}/SPECS.md

@@ -41,6 +41,7 @@ To obtain an API key, go to `Settings > API Keys` in the PrimeThink app and gene
 | `pt chat create` | `POST /api/v1/chats` |
 | `pt chat rename` | `PUT /api/v1/chats/{chat_id}/name` |
 | `pt chat goal` | `PUT /api/v1/chats/{chat_id}/goal` |
+| `pt chat type` | `PUT /api/v1/chats/{chat_id}/page_type?page_type=html\|chat` |
 | `pt chat messages` | `GET /api/v1/chats/{chat_id}/messages` |
 | `pt chat archive` / `unarchive` | `POST /api/v1/chats/{chat_id}/archive/{true\|false}` |
 | `pt chat delete` | `DELETE /api/v1/chats/{chat_id}` |
@@ -63,7 +64,11 @@ To obtain an API key, go to `Settings > API Keys` in the PrimeThink app and gene
 | `pt task get` | `GET /api/v1/tasks/{task_id}` |
 | `pt task delete` | `DELETE /api/v1/tasks/{task_id}` |
 | `pt task duplicate` | `POST /api/v1/tasks/{task_id}/duplicate` |
-| `pt task publish` / `unpublish` | `PATCH /api/v1/tasks/{task_id}/public-status?task_type=public\|private` |
+| `pt task set-public` / `set-private` | `PATCH /api/v1/tasks/{task_id}/public-status?task_type=public\|private` |
+| `pt task publish` | `POST /api/v1/tasks/` or `PATCH /api/v1/tasks/{task_id}` |
+| `pt task test` | `POST /api/v1/chats` (new only), `PUT /api/v1/chats/{chat_id}/page_type` (existing only), `PUT /api/v1/chats/{chat_id}/goal` |
+| `pt live-app publish` | task create/update + task version + task directory/document/version endpoints |
+| `pt live-app test` | chat create/page-type/goal + chat directory/document/version endpoints |
 | `pt task export` | `GET /api/v1/tasks/{task_id}` (portable fields filtered client-side) |
 | `pt task import` | `POST /api/v1/tasks/` |
 | `pt task create-version` | `POST /api/v1/tasks/{task_id}/versions` |
@@ -493,8 +498,8 @@ pt task duplicate TASK_ID
 
 **CLI Commands** (the CLI exposes the public/private pair; use `pt task update --type` for the rest):
 ```bash
-pt task publish TASK_ID     # task_type=public
-pt task unpublish TASK_ID   # task_type=private
+pt task set-public TASK_ID    # task_type=public
+pt task set-private TASK_ID   # task_type=private
 ```
 
 ---

{primethink_cli-1.3.2 → primethink_cli-1.3.4}/USER_GUIDE.md

@@ -73,7 +73,7 @@ pt version
 
 You should see output like:
 ```
-PrimeThink CLI v1.1.0
+PrimeThink CLI v1.3.3
 ```
 
 ## Getting Started
@@ -689,22 +689,30 @@ pt task update 99 --description "Updated description"
 pt task update 99 --schedule-nl "every Friday at 17:00"
 ```
 
-### Duplicate, publish, or delete a task
+### Duplicate, publish, test, change visibility, or delete a task
 
 ```bash
 # Clone a task (prints the new task's JSON, including its id)
 pt task duplicate 99
 
+# Publish a conventional task project; GOAL.md is required
+pt task publish ./tasks/briefing --virtual-assistant-id 7
+pt task publish ./tasks/briefing --task-id 99 --virtual-assistant-id 7
+
+# Sync the project goal into a new temporary chat or an existing chat
+pt task test ./tasks/briefing
+pt task test ./tasks/briefing --chat-id CHAT_UUID
+
 # Toggle a task's visibility (its type) between public and private
-pt task publish 99
-pt task unpublish 99
+pt task set-public 99
+pt task set-private 99
 
 # Delete a task — prompts for confirmation unless you pass --yes
 pt task delete 99
 pt task delete 99 --yes
 ```
 
-For type changes other than public/private (e.g. `group` or `catalog`), use `pt task update 99 --type group`.
+A project directory can override its folder name with `.name.config`, its description with `.description.config`, and its initial prompt with `INITIAL_PROMPT.md`. For type changes other than public/private (e.g. `group` or `catalog`), use `pt task update 99 --type group`.
 
 ### Version a task
 
@@ -786,13 +794,36 @@ pt live-app new ./company-app \
 
 The URL must be a public HTTPS GitHub repository. A custom catalog defines its variants in `live-app-templates/manifest.json`; see the [CLI Reference](docs/cli-reference.md#pt-live-app-new) for the schema. Downloads and extracted files are size-limited and validated, and extraction is atomic.
 
+### Publish and test a Live App
+
+After building, the CLI discovers a flat artifact in `dist/`, then `app/`, then the project root. Override discovery with `--app-dir`. The artifact must contain `index.html` or `canvas.html` (deployed as `index.html`).
+
+```bash
+# Create or update the reusable Live App task
+pt live-app publish ./my-live-app --virtual-assistant-id 7
+pt live-app publish ./my-live-app --task-id 42 --virtual-assistant-id 7
+
+# Iterate in a new temporary chat or update one chat in place
+pt live-app test ./my-live-app
+pt live-app test ./my-live-app --chat-id CHAT_UUID --open
+
+# Explicitly switch any existing chat's renderer
+pt chat type CHAT_UUID live-app
+pt chat type CHAT_UUID chat
+```
+
+The commands read `.name.config`, `.description.config`, and optional `GOAL.md`; publish also uploads `.image.png` when present. Same-named app documents are updated as new `Production` versions, preserving their IDs and relative links.
+
+Automated UI testing of a Live App is not part of the CLI. It is a deterministic, plan-driven workflow provided by the `primethink-developer` skill (`pt install-developer-skill`): the skill captures the running app's accessibility snapshot, authors a reviewable `tests/test_plan.yaml`, runs it with a bundled Playwright runner without an LLM in the execution loop, reads the structured results, and heals failing selectors before re-running.
+
 ## MCP Server
 
-Everything the CLI can do, PrimeThink can also expose over the [Model Context
+Core API management operations can also be exposed over the [Model Context
 Protocol (MCP)](https://modelcontextprotocol.io) — the same code, running as a
 server that AI assistants talk to directly. Instead of an assistant shelling out
 to `pt`, it calls typed tools like `send_message`, `list_chats`, `create_task`,
-and `search_documents`.
+and `search_documents`. Local scaffolding and project publish/test orchestration
+remain CLI workflows.
 
 ### When to use it
 
@@ -834,9 +865,10 @@ overrides.
 
 A few things to know:
 
-- Every CLI command has a tool equivalent (messaging, chats, collections, tasks,
-  agents, semantic search, images). Field-heavy tools like `create_task` expose
-  common fields plus an `extra_fields` object for anything else.
+- Core API management operations have tool equivalents (messaging, chats, collections, tasks,
+  agents, semantic search, images). Local scaffolding and project publish/test orchestration
+  remain CLI workflows. Field-heavy tools like `create_task` expose common fields plus an
+  `extra_fields` object for anything else.
 - File and sync tools read and write on the machine where the server runs — your
   own machine, for a locally launched server.
 - Unlike the CLI, delete tools don't prompt for confirmation; your MCP client is
@@ -1333,6 +1365,15 @@ pt task create --help
 pt chat sync-to --help
 ```
 
+`--help` also works *before* the command it describes — the CLI resolves the rest
+of the command path, so `pt --help chat send` and `pt chat --help send` print the
+same page as `pt chat send --help`:
+
+```bash
+pt --help chat send
+pt chat --help send
+```
+
 ### Documentation
 
 - [README](README.md) - Quick start guide

{primethink_cli-1.3.2 → primethink_cli-1.3.4}/docs/cli-reference.md

@@ -1,6 +1,6 @@
 # PrimeThink CLI — Command Reference
 
-Complete reference for every command in the PrimeThink CLI (`pt`), version 1.2.0.
+Complete reference for every command in the PrimeThink CLI (`pt`), version 1.3.3.
 
 Commands are organized into noun groups: `profile`, `live-app`, `chat`, `collection`, `agent`, `task`, `search`, and `image`.
 
@@ -15,6 +15,8 @@ Commands are organized into noun groups: `profile`, `live-app`, `chat`, `collect
   - [`pt install-developer-skill`](#pt-install-developer-skill)
 - [Live Apps: `pt live-app`](#live-apps-pt-live-app)
   - [`pt live-app new`](#pt-live-app-new)
+  - [`pt live-app publish`](#pt-live-app-publish)
+  - [`pt live-app test`](#pt-live-app-test)
 - [Profiles: `pt profile`](#profiles-pt-profile)
   - [`pt profile add`](#pt-profile-add)
   - [`pt profile use`](#pt-profile-use)
@@ -26,6 +28,7 @@ Commands are organized into noun groups: `profile`, `live-app`, `chat`, `collect
   - [`pt chat create`](#pt-chat-create)
   - [`pt chat rename`](#pt-chat-rename)
   - [`pt chat goal`](#pt-chat-goal)
+  - [`pt chat type`](#pt-chat-type)
   - [`pt chat messages`](#pt-chat-messages)
   - [`pt chat archive`](#pt-chat-archive)
   - [`pt chat unarchive`](#pt-chat-unarchive)
@@ -58,8 +61,10 @@ Commands are organized into noun groups: `profile`, `live-app`, `chat`, `collect
   - [`pt task get`](#pt-task-get)
   - [`pt task delete`](#pt-task-delete)
   - [`pt task duplicate`](#pt-task-duplicate)
+  - [`pt task set-public`](#pt-task-set-public)
+  - [`pt task set-private`](#pt-task-set-private)
   - [`pt task publish`](#pt-task-publish)
-  - [`pt task unpublish`](#pt-task-unpublish)
+  - [`pt task test`](#pt-task-test)
   - [`pt task export`](#pt-task-export)
   - [`pt task import`](#pt-task-import)
   - [`pt task create-version`](#pt-task-create-version)
@@ -94,6 +99,23 @@ Every command that calls the API accepts these two options:
 > `--path` (a directory inside the chat/collection) on the file commands. When in doubt,
 > use the long forms.
 
+### Getting help
+
+`--help` can be written before or after the command it describes — the CLI resolves
+the whole command path that follows the flag, so these three are equivalent:
+
+```bash
+pt chat send --help
+pt chat --help send
+pt --help chat send
+```
+
+A leading `--help` never errors: it descends as far as the path is recognized, so
+`pt --help chat nope` describes `pt chat`, and `pt --help nope` describes `pt`. A
+*trailing* `--help` keeps Click's own behavior, where the command path has to
+resolve before the flag is reached — `pt chat nope --help` is still a
+`No such command 'nope'` error.
+
 ### Output
 
 - Commands that call the API print the JSON response, pretty-printed with 2-space indentation, to stdout. This makes output easy to pipe into `jq` or redirect to a file.
@@ -132,7 +154,7 @@ Display the CLI version.
 
 ```bash
 pt version
-# PrimeThink CLI v1.2.0
+# PrimeThink CLI v1.3.3
 ```
 
 ### `pt whoami`
@@ -150,7 +172,7 @@ pt whoami --profile production
 
 ### `pt mcp`
 
-Run PrimeThink as an [MCP](https://modelcontextprotocol.io) server over stdio, exposing every API command as a tool that MCP clients can call. See [MCP Server (`pt mcp`)](#mcp-server-pt-mcp) for the full tool list and client configuration.
+Run PrimeThink as an [MCP](https://modelcontextprotocol.io) server over stdio, exposing core API management operations as tools that MCP clients can call. See [MCP Server (`pt mcp`)](#mcp-server-pt-mcp) for the full tool list and client configuration.
 
 ```bash
 pt mcp
@@ -227,7 +249,7 @@ pt install-developer-skill --force --ref <TAG_OR_COMMIT>
 
 ## Live Apps: `pt live-app`
 
-Create a local PrimeThink Live App project from a public GitHub template catalog. This group is local-only and does not require an API token or profile. The command downloads files but does not execute generated code or run a package manager.
+Create, publish, synchronize, and test PrimeThink Live Apps. `pt live-app new` is local-only and does not require an API token; the publishing and chat-test commands use the normal profile connection options.
 
 ### `pt live-app new`
 
@@ -297,6 +319,59 @@ A custom repository provides `live-app-templates/manifest.json` at its root. Eac
 
 Each requested combination must match exactly one entry. For compatibility, repositories without a manifest can use the default catalog's conventional directory names, but new catalogs should always include the manifest.
 
+### `pt live-app publish`
+
+Create a new private Live App task from a project directory, or update one when `--task-id` is supplied. The command reads project metadata, creates a `Production` task version, and synchronizes the flat app artifact into the task's `@app` folder.
+
+```bash
+pt live-app publish DIRECTORY --virtual-assistant-id ID [OPTIONS]
+```
+
+| Option | Default | Description |
+|---|---|---|
+| `--task-id ID` | create | Update this task instead of creating one |
+| `--virtual-assistant-id ID` | required | Agent assigned to the task |
+| `--app-dir DIRECTORY` | auto | Flat artifact directory; otherwise checks `dist/`, `app/`, then project root |
+| `--version-name NAME` | `Production` | Name used for the task version and document versions |
+| `--profile`, `--api-url` | active profile | Connection selection |
+
+The artifact requires `index.html`, or `canvas.html` (uploaded as `index.html`). Files are uploaded at the top level. A same-named remote document receives a new version, preserving its ID and relative references; an identical version is reported as unchanged. If `DIRECTORY/.image.png` exists, it is uploaded as the task image.
+
+```bash
+pt live-app publish ./decision-board --virtual-assistant-id 7
+pt live-app publish ./decision-board --task-id 42 --virtual-assistant-id 7
+```
+
+### `pt live-app test`
+
+Synchronize a Live App into a newly created temporary chat, or update an explicit existing chat in place. The command sets the chat page type to HTML, applies `GOAL.md` when present, and versions/uploads the app files under `@app`.
+
+```bash
+pt live-app test DIRECTORY [OPTIONS]
+```
+
+| Option | Default | Description |
+|---|---|---|
+| `--chat-id CHAT_ID` | create | Reuse this existing chat |
+| `--workspace-id ID` | unset | Workspace for a newly created chat |
+| `--temporary` / `--permanent` | temporary | Lifetime of a newly created chat |
+| `--app-dir DIRECTORY` | auto | Override flat artifact discovery |
+| `--version-name NAME` | `Production` | Document version name |
+| `--open` | off | Open the resulting chat in a browser |
+| `--web-url URL` | derived from API URL | Web URL used for output/opening (defaults to the active profile's API host, mapping `api.` → `app.`) |
+
+```bash
+pt live-app test ./decision-board
+pt live-app test ./decision-board --chat-id CHAT_UUID --open
+```
+
+> **UI testing moved out of the CLI.** Automated Live App UI testing is now a
+> deterministic, plan-driven workflow owned by the `primethink-developer` skill
+> rather than a `pt` subcommand — the skill authors a reviewable
+> `tests/test_plan.yaml`, runs it with a bundled Playwright runner (no LLM in the
+> execution loop), and heals failing selectors. See the skill's UI-testing guide.
+> This removes the CLI's `kiro-cli` dependency.
+
 ---
 
 ## Profiles: `pt profile`
@@ -475,6 +550,17 @@ pt chat goal 123 --goal "Track the Q3 launch checklist"
 pt chat goal 123 --goal-file ./goal.md
 ```
 
+### `pt chat type`
+
+Switch a chat between the Live App renderer and the normal chat view. `live-app` maps to API page type `html`; `chat` maps to API page type `chat`.
+
+```bash
+pt chat type CHAT_ID (live-app|chat) [--profile NAME] [--api-url URL]
+
+pt chat type 123 live-app
+pt chat type 123 chat
+```
+
 ### `pt chat messages`
 
 List messages in a chat. With no options, the server returns the latest page (25 messages). Pagination is cursor-based on message IDs, not page numbers.
@@ -998,20 +1084,56 @@ pt task duplicate TASK_ID [--profile NAME] [--api-url URL]
 pt task duplicate 99 | jq '.id'
 ```
 
+### `pt task set-public`
+
+Make a task public via the task public-status endpoint.
+
+```bash
+pt task set-public TASK_ID [--profile NAME] [--api-url URL]
+```
+
+### `pt task set-private`
+
+Make a task private via the task public-status endpoint. For other task types (`group`, `system`, `catalog`), use `pt task update TASK_ID --type TYPE`.
+
+```bash
+pt task set-private TASK_ID [--profile NAME] [--api-url URL]
+```
+
 ### `pt task publish`
 
-Make a task public — sets its type to `public` via the task public-status endpoint.
+Create a private task from a conventional project directory, or synchronize the metadata into an existing task when `--task-id` is passed.
+
+```bash
+pt task publish DIRECTORY --virtual-assistant-id ID [--task-id ID] [--profile NAME] [--api-url URL]
+```
+
+`GOAL.md` is required and must not be empty. The task name defaults to the directory name and can be overridden by `.name.config`; the description defaults to the name and can be overridden by `.description.config`; optional `INITIAL_PROMPT.md` supplies the initial prompt. Creation uses the same conservative defaults as the reference workflow (private, published, standard chat, optional features disabled). Updating synchronizes name, description, goal, initial prompt, and virtual assistant without replacing unrelated server fields.
 
 ```bash
-pt task publish TASK_ID [--profile NAME] [--api-url URL]
+pt task publish ./tasks/morning-briefing --virtual-assistant-id 7
+pt task publish ./tasks/morning-briefing --task-id 99 --virtual-assistant-id 7
 ```
 
-### `pt task unpublish`
+### `pt task test`
+
+Apply a task project's required `GOAL.md` to a newly created chat or an explicit existing chat. Existing chats are switched to normal chat mode.
 
-Make a task private — sets its type to `private` via the task public-status endpoint. For other type changes (`group`, `system`, `catalog`), use `pt task update TASK_ID --type TYPE`.
+```bash
+pt task test DIRECTORY [OPTIONS]
+```
+
+| Option | Default | Description |
+|---|---|---|
+| `--chat-id CHAT_ID` | create | Reuse this existing chat |
+| `--workspace-id ID` | unset | Workspace for a newly created chat |
+| `--temporary` / `--permanent` | temporary | Lifetime of a newly created chat |
+| `--open` | off | Open the resulting chat in a browser |
+| `--web-url URL` | derived from API URL | Web URL used for output/opening (defaults to the active profile's API host, mapping `api.` → `app.`) |
 
 ```bash
-pt task unpublish TASK_ID [--profile NAME] [--api-url URL]
+pt task test ./tasks/morning-briefing
+pt task test ./tasks/morning-briefing --chat-id CHAT_UUID --permanent
 ```
 
 ### `pt task export`
@@ -1233,7 +1355,7 @@ Point an MCP client's server config at `pt mcp`:
 
 ### Tools
 
-Every API command has a tool equivalent. Names are snake_case (e.g. the CLI's `pt chat send` → the `send_message` tool, `pt chat list` → `list_chats`):
+Core API management commands have tool equivalents; local scaffolding and the project publish/test orchestration commands remain CLI workflows. Tool names are snake_case (e.g. the CLI's `pt chat send` → the `send_message` tool, `pt chat list` → `list_chats`):
 
 | Group | Tools |
 |---|---|