openplanr 2.2641.0 → 2.2641.2

package/docs/CLI.md

@@ -1,7 +1,7 @@
-# planr CLI reference
+# openplanr CLI reference
 
-> Every command and flag of the `planr` CLI.
-> Package: `openplanr` | Binary: `planr` (aliases: `openplanr`, `opr`)
+> Every command and flag of the `openplanr` CLI.
+> Package: `openplanr` | Binary: `openplanr` (alias: `opr`)
 
 ---
 
@@ -11,7 +11,7 @@
 npm install -g openplanr
 
 # Verify
-planr --version
+openplanr --version
 ```
 
 ---
@@ -22,11 +22,11 @@ The CLI auto-detects non-TTY environments (CI, coding agents) and skips interact
 
 ```bash
 # Explicit flag
-planr epic create --title "My App" --yes
-planr task create --story US-001 --title "Implement approved story" --yes
+openplanr epic create --title "My App" --yes
+openplanr task create --story US-001 --title "Implement approved story" --yes
 
 # Auto-detected (no TTY)
-echo "" | planr epic create --title "My App"
+echo "" | openplanr epic create --title "My App"
 ```
 
 **Behavior in non-interactive mode:**
@@ -54,12 +54,12 @@ These options apply to **all** commands:
 
 ## Commands
 
-### `planr company`
+### `openplanr company`
 
 The company route connects an explicitly configured workspace to selected local artifacts. Existing encrypted token shares remain separate. Sign in through the browser and choose the organization in the identity provider's consent screen:
 
 ```bash
-planr company login
+openplanr company login
 ```
 
 The normal customer flow needs no service URL or output flag. For a remote or
@@ -67,17 +67,17 @@ headless session, print the authorization URL instead of launching it:
 
 ```bash
 # Print the browser URL instead of launching it; open it on this same computer
-planr company login --no-open --timeout 300
+openplanr company login --no-open --timeout 300
 ```
 
 Successful sign-in and sign-out show a short confirmation. To switch accounts,
-run `planr company logout` before signing in again. Recovery and cleanup warnings
+run `openplanr company logout` before signing in again. Recovery and cleanup warnings
 remain visible. Structured output with status details and error codes is available
 for automation:
 
 ```bash
-planr company login --json
-planr company logout --json
+openplanr company login --json
+openplanr company logout --json
 ```
 
 Hosted commands use `https://api.openplanr.dev` by default. `--api-url <origin>` is an advanced override for local development, staging, and self-hosted testing; customers do not need to copy a service URL.
@@ -91,28 +91,28 @@ Logout revokes saved refresh and access tokens before removing their local refer
 Publication selects one repository-relative JSON, Markdown, SVG or HTML file, up to 1 MiB. An authored `openplanr-design-document` selected with `--kind design` packages the complete design: its declared screens, frames, variants, and supported local assets. The entire packaged revision must fit within the same 1 MiB limit. Single HTML/SVG designs remain supported.
 
 ```bash
-planr company preview .planr/designs/checkout/design-document.json \
+openplanr company preview .planr/designs/checkout/design-document.json \
   --kind design --title "Checkout experience" \
   --project <project-id>
-planr company publish <preview-id> --json
+openplanr company publish <preview-id> --json
 ```
 
 Review the exact selected files, content and publication size before publishing. `--json` includes the complete content for inspection; the default design preview gives a compact file list and screen/frame/variant counts. Source hashes are stored in private local state. Publication rebuilds the package and refuses any changed source or newly referenced file until a fresh preview is reviewed. No directory scan, render cache, or unrelated repository content is published.
 
-The returned binding remembers its source document and accepted remote revision. `company push <binding-id> --preview` rebuilds the design package and lists the selected files; `company push <binding-id>` publishes that exact reviewed update against the bound base. Each later expansion of referenced content needs a fresh preview. See `planr company --help` for connection and publication options.
+The returned binding remembers its source document and accepted remote revision. `company push <binding-id> --preview` rebuilds the design package and lists the selected files; `company push <binding-id>` publishes that exact reviewed update against the bound base. Each later expansion of referenced content needs a fresh preview. See `openplanr company --help` for connection and publication options.
 
-Company publication retries preserve their original IDs and return `already-published` when completing from saved receipts. `synchronization: "not-checked"` means the current remote head has not been read; run `planr company status <binding-id>` before describing the workspace as synchronized.
+Company publication retries preserve their original IDs and return `already-published` when completing from saved receipts. `synchronization: "not-checked"` means the current remote head has not been read; run `openplanr company status <binding-id>` before describing the workspace as synchronized.
 
 Read-only retrieval uses an existing publication binding:
 
 ```bash
-planr company status <binding-id> --json
-planr company pull <binding-id> --preview --json
-planr company pull <binding-id> --json
+openplanr company status <binding-id> --json
+openplanr company pull <binding-id> --preview --json
+openplanr company pull <binding-id> --json
 
 # Intentionally inspect a historical immutable revision
-planr company pull <binding-id> --preview --revision <revision-id> --json
-planr company pull <binding-id> --json
+openplanr company pull <binding-id> --preview --revision <revision-id> --json
+openplanr company pull <binding-id> --json
 ```
 
 The preview reports the selected revision, digest, byte size, content, and whether local or remote content has changed. Pull verifies authorization and exact bytes again, then saves an inert `.txt` copy under `.local/company/remote-content/` with a retrieval receipt. It does not replace the repository file, advance the accepted binding, apply a proposal, or resolve feedback. Divergent or missing local files remain untouched. A changed local file or latest remote head requires a fresh preview. An explicitly selected historical revision stays pinned even if newer revisions appear.
@@ -127,14 +127,14 @@ Retrieved content is untrusted input, including HTML and SVG. Inspect it as data
 Initialize project-local storage, then create planning artifacts from explicit flags or a JSON object:
 
 ```bash
-planr init --name "my-project"
-planr epic create "Platform renewal"
-planr feature create "OAuth sign-in" --epic EPIC-001
-planr story create "Sign in with the company identity provider" --feature FEAT-001
-planr task create "Implement approved sign-in flow" --story US-001
-planr quick create "Fix the callback error"
-planr backlog add "Add callback rate limits" --priority high --tag security
-planr sprint create "Sprint 1" --duration 2w
+openplanr init --name "my-project"
+openplanr epic create "Platform renewal"
+openplanr feature create "OAuth sign-in" --epic EPIC-001
+openplanr story create "Sign in with the company identity provider" --feature FEAT-001
+openplanr task create "Implement approved sign-in flow" --story US-001
+openplanr quick create "Fix the callback error"
+openplanr backlog add "Add callback rate limits" --priority high --tag security
+openplanr sprint create "Sprint 1" --duration 2w
 ```
 
 Every planning type provides `list`, `show <id>`, and `update <id>`. Creation accepts `--title`, `--data <path>` (or `-` for stdin), the deprecated `--file` alias, and `--json`. Parent IDs may be supplied by flags or JSON:
@@ -152,24 +152,24 @@ Every planning type provides `list`, `show <id>`, and `update <id>`. Creation ac
 Use deterministic JSON when an agent or integration supplies complete fields:
 
 ```bash
-planr epic create --data epic.json --json
-planr feature create --data feature.json --json
-planr task create --data - --json < task.json
+openplanr epic create --data epic.json --json
+openplanr feature create --data feature.json --json
+openplanr task create --data - --json < task.json
 ```
 
-`planr update <ids...>` supports bulk status changes. `--all-done` and `--all-pending` also update canonical task checkboxes for task and quick-task artifacts. Use each command's `--help` output for its exact options.
+`openplanr update <ids...>` supports bulk status changes. `--all-done` and `--all-pending` also update canonical task checkboxes for task and quick-task artifacts. Use each command's `--help` output for its exact options.
 
-### `planr sprint` refinement
+### `openplanr sprint` refinement
 
 The `planr:sprint` skill judges every open item and selects a sprint; these commands store what it decides. Sprint statuses are `planned`, `active` and `closed`.
 
 ```bash
-planr sprint create --data sprint.json --json            # name, releaseCut, capacityDays, optional batches
-planr sprint refinement SPRINT-004 --data refinement.json # validate, store, fill the sprint body
-planr sprint diff SPRINT-003 SPRINT-004                   # what moved between two runs
-planr sprint apply SPRINT-004 --dry-run                   # preview the status write-back
-planr sprint apply SPRINT-004 --yes --commit              # write it as one commit
-planr sprint close SPRINT-004                             # record leftovers for the next run
+openplanr sprint create --data sprint.json --json            # name, releaseCut, capacityDays, optional batches
+openplanr sprint refinement SPRINT-004 --data refinement.json # validate, store, fill the sprint body
+openplanr sprint diff SPRINT-003 SPRINT-004                   # what moved between two runs
+openplanr sprint apply SPRINT-004 --dry-run                   # preview the status write-back
+openplanr sprint apply SPRINT-004 --yes --commit              # write it as one commit
+openplanr sprint close SPRINT-004                             # record leftovers for the next run
 ```
 
 | Command | Behaviour |
@@ -179,34 +179,34 @@ planr sprint close SPRINT-004                             # record leftovers for
 | `apply <id>` | Writes each item's `targetStatus` and `targetPriority` (backlog only) and the `blockedBy` note of blocked items to the artifacts. Statuses must belong to the type's vocabulary unless `--force`. Needs `--yes` (or `--dry-run`); with `--commit` the touched files are committed as `chore(planr): refine backlog for <id>`. |
 | `close <id>` | Sets `status: closed` and `closedAt`, and records `leftovers[]` (unchecked or unfinished `taskIds`) in `refinement.json` for the next run. |
 
-Every command accepts `--json`. Failures use bounded codes such as `E_SPRINT_NOT_FOUND`, `E_SPRINT_REFINEMENT_INVALID` (with `$`-rooted diagnostics), `E_SPRINT_REFINEMENT_MISSING`, `E_SPRINT_APPLY_CONFIRMATION_REQUIRED`, `E_SPRINT_APPLY_STATUS_INVALID`, `E_SPRINT_CLOSED` and `E_SPRINT_ALREADY_CLOSED`. `planr status` lists the active sprint first with its release cut and checkbox progress, and `planr status --json` exposes it as `sprint`.
+Every command accepts `--json`. Failures use bounded codes such as `E_SPRINT_NOT_FOUND`, `E_SPRINT_REFINEMENT_INVALID` (with `$`-rooted diagnostics), `E_SPRINT_REFINEMENT_MISSING`, `E_SPRINT_APPLY_CONFIRMATION_REQUIRED`, `E_SPRINT_APPLY_STATUS_INVALID`, `E_SPRINT_CLOSED` and `E_SPRINT_ALREADY_CLOSED`. `openplanr status` lists the active sprint first with its release cut and checkbox progress, and `openplanr status --json` exposes it as `sprint`.
 
 
-### `planr spec`
+### `openplanr spec`
 
 Spec-driven planning mode — third posture alongside agile + QT, designed for **planning *for* AI coding agents**. Each spec is a self-contained directory at `.planr/specs/SPEC-NNN-{slug}/` containing the spec doc, decomposed User Stories, decomposed Tasks, and any UI design assets. The artifact schema mirrors the [planr-pipeline](https://github.com/openplanr/OpenPlanr/tree/main/packages/pipeline) canonical protocol schemas under `schemas/v1.0.0/` — file Create/Modify/Preserve lists, Type=UI|Tech, agent assignment, DoD with build/test commands. The two products use one artifact contract; no conversion adapter ever.
 
 The generated artifact contract and command examples in this section are the
 packaged source of truth for spec-driven mode.
 
-#### `planr spec init`
+#### `openplanr spec init`
 
 Activate spec-driven mode in the current project. Creates `.planr/specs/`. Adds `spec: SPEC` to `idPrefix` if missing. Idempotent.
 
 ```bash
-planr spec init
+openplanr spec init
 ```
 
 ---
 
-#### `planr spec create`
+#### `openplanr spec create`
 
 Create a new spec — a self-contained directory with `stories/`, `tasks/`, `design/` subfolders.
 
 ```bash
-planr spec create "Auth flow"
-planr spec create --title "Auth flow" --slug auth --priority P0 --milestone v1.0
-planr spec create "User Onboarding" --po @AsemDevs
+openplanr spec create "Auth flow"
+openplanr spec create --title "Auth flow" --slug auth --priority P0 --milestone v1.0
+openplanr spec create "User Onboarding" --po @AsemDevs
 ```
 
 | Option              | Description                                            | Required     |
@@ -222,12 +222,12 @@ planr spec create "User Onboarding" --po @AsemDevs
 
 ---
 
-#### `planr spec shape`
+#### `openplanr spec shape`
 
 Interactive 4-question authoring of a spec's body. Walks the PO through Context, Functional Requirements, Business Rules, and Acceptance Criteria. Optionally captures Out-of-Scope items and Decomposition Notes. Updates `status: pending → shaping`.
 
 ```bash
-planr spec shape SPEC-001
+openplanr spec shape SPEC-001
 ```
 
 **Refused in `--no-interactive` mode** — this command is interactive by design (it asks 4 sequential questions).
@@ -243,14 +243,14 @@ planr spec shape SPEC-001
 
 ---
 
-#### `planr spec sync`
+#### `openplanr spec sync`
 
 Validate spec integrity and auto-fix safe inconsistencies. Use after manual edits, interrupted work, or when in doubt.
 
 ```bash
-planr spec sync                       # scan all specs
-planr spec sync SPEC-001              # scope to one spec
-planr spec sync --dry-run             # report findings without writing fixes
+openplanr spec sync                       # scan all specs
+openplanr spec sync SPEC-001              # scope to one spec
+openplanr spec sync --dry-run             # report findings without writing fixes
 ```
 
 | Option        | Description                                          | Required |
@@ -266,66 +266,66 @@ planr spec sync --dry-run             # report findings without writing fixes
 
 ---
 
-#### `planr spec list`
+#### `openplanr spec list`
 
 List all specs with title, status, and decomposition counts.
 
 ```bash
-planr spec list
+openplanr spec list
 ```
 
 ---
 
-#### `planr spec show`
+#### `openplanr spec show`
 
 Print a spec's metadata, body summary, and the full US/Task decomposition tree.
 
 ```bash
-planr spec show SPEC-001
+openplanr spec show SPEC-001
 ```
 
 ---
 
-#### `planr spec status`
+#### `openplanr spec status`
 
 Decomposition state. Without args: aggregate report across all specs. With a spec ID: focused view.
 
 ```bash
-planr spec status                # aggregate
-planr spec status SPEC-001       # focused
+openplanr spec status                # aggregate
+openplanr spec status SPEC-001       # focused
 ```
 
 ---
 
-#### `planr spec destroy`
+#### `openplanr spec destroy`
 
 Remove a spec entirely. Because each spec is a self-contained directory, this is a single `rm -rf`. Prompts for confirmation (use `--yes` to skip).
 
 ```bash
-planr spec destroy SPEC-001
-planr spec destroy SPEC-001 --yes
+openplanr spec destroy SPEC-001
+openplanr spec destroy SPEC-001 --yes
 ```
 
 ---
 
-#### `planr spec attach-design`
+#### `openplanr spec attach-design`
 
 Copy PNG mockup files into the spec's `design/` subdirectory and update
 `ui_files` frontmatter on the SPEC. The `planr:plan` host skill reads these
 inputs while it builds the reviewed implementation plan.
 
 ```bash
-planr spec attach-design SPEC-001 --files login.png signup.png
+openplanr spec attach-design SPEC-001 --files login.png signup.png
 ```
 
 ---
 
-#### `planr spec promote`
+#### `openplanr spec promote`
 
 Validate that a spec is ready for handoff to `planr-pipeline` (has stories, tasks, non-trivial body) and print the next-step pipeline command. Updates SPEC frontmatter `status: ready-for-pipeline`.
 
 ```bash
-planr spec promote SPEC-001
+openplanr spec promote SPEC-001
 ```
 
 After promotion, run from any configured runtime:
@@ -337,24 +337,24 @@ $planr:plan       # Codex
 
 ---
 
-### `planr template list`
+### `openplanr template list`
 
 List all available task templates (built-in and custom).
 
 ```bash
-planr template list
+openplanr template list
 ```
 
 Shows template name, description, task count, and whether it's built-in or custom.
 
 ---
 
-### `planr template show`
+### `openplanr template show`
 
 Preview a template's contents and variables.
 
 ```bash
-planr template show rest-endpoint
+openplanr template show rest-endpoint
 ```
 
 | Argument | Description   | Required |
@@ -363,13 +363,13 @@ planr template show rest-endpoint
 
 ---
 
-### `planr template use`
+### `openplanr template use`
 
 Generate a task list from a template with variable substitution.
 
 ```bash
-planr template use rest-endpoint --title "User Profile API"
-planr template use react-component --title "Dashboard Widget"
+openplanr template use rest-endpoint --title "User Profile API"
+openplanr template use react-component --title "Dashboard Widget"
 ```
 
 | Argument/Option   | Description                       | Required |
@@ -393,12 +393,12 @@ Template variables (e.g., `{{entityName}}`, `{{componentName}}`) are prompted in
 
 ---
 
-### `planr template save`
+### `openplanr template save`
 
 Save an existing task list as a reusable custom template.
 
 ```bash
-planr template save TASK-001 --name my-pattern
+openplanr template save TASK-001 --name my-pattern
 ```
 
 | Argument/Option | Description                      | Required |
@@ -410,12 +410,12 @@ planr template save TASK-001 --name my-pattern
 
 ---
 
-### `planr template delete`
+### `openplanr template delete`
 
 Remove a custom template.
 
 ```bash
-planr template delete my-pattern
+openplanr template delete my-pattern
 ```
 
 | Argument | Description   | Required |
@@ -426,12 +426,12 @@ Prompts for confirmation before deleting. Only custom templates can be deleted.
 
 ---
 
-### `planr checklist show`
+### `openplanr checklist show`
 
 Display the agile development checklist.
 
 ```bash
-planr checklist show
+openplanr checklist show
 ```
 
 Shows the full 5-phase checklist:
@@ -444,34 +444,34 @@ Shows the full 5-phase checklist:
 
 ---
 
-### `planr checklist toggle`
+### `openplanr checklist toggle`
 
 Interactively toggle checklist items. Presents a multi-select prompt where you can check/uncheck items, then writes changes back to the file with a progress summary.
 
 ```bash
-planr checklist toggle
+openplanr checklist toggle
 ```
 
 ---
 
-### `planr checklist reset`
+### `openplanr checklist reset`
 
 Reset the checklist back to its initial state.
 
 ```bash
-planr checklist reset
+openplanr checklist reset
 ```
 
 ---
 
-### `planr init`
+### `openplanr init`
 
-Initialize deterministic project storage in `.planr/`. Runtime installation belongs to `planr setup`.
+Initialize deterministic project storage in `.planr/`. Runtime installation belongs to `openplanr setup`.
 
 ```bash
-planr init
-planr init --name my-project
-planr init --force
+openplanr init
+openplanr init --name my-project
+openplanr init --force
 ```
 
 | Option | Description |
@@ -481,18 +481,18 @@ planr init --force
 
 ---
 
-### `planr setup`, `planr runtime`, and `planr doctor`
+### `openplanr setup`, `openplanr runtime`, and `openplanr doctor`
 
 ```bash
-planr setup
-planr setup --runtime auto --scope user --yes
-planr setup --dry-run
-planr setup --minimal
-planr runtime detect
-planr runtime install codex --scope user
-planr runtime update claude --scope user
-planr runtime rollback
-planr doctor --strict
+openplanr setup
+openplanr setup --runtime auto --scope user --yes
+openplanr setup --dry-run
+openplanr setup --minimal
+openplanr runtime detect
+openplanr runtime install codex --scope user
+openplanr runtime update claude --scope user
+openplanr runtime rollback
+openplanr doctor --strict
 ```
 
 Interactive setup guides coding-agent and scope selection. It installs the OpenPlanr skills bundled with the CLI. User scope is
@@ -508,7 +508,7 @@ operations. After confirmation, setup registers the generated local marketplace
 (`openplanr-local`) that ships inside the installed `openplanr` package and
 installs or updates `planr@openplanr-local` from it, so the plugin always matches
 this CLI. Setup never reads `openplanr/marketplace` for versions.
-`planr doctor` checks the installed plugin's version and stable manifest identity
+`openplanr doctor` checks the installed plugin's version and stable manifest identity
 without mutating Claude Code, and warns about older `openplanr@…` and
 `planr-pipeline@…` plugins. `doctor --fix` preserves saved scopes and discovery
 mode while previewing owned-file, managed native plugin and stale-daemon repairs.
@@ -527,7 +527,7 @@ Use one Claude Code channel per machine; see
 Use the corresponding `planr:*` skills through the installed runtime adapter.
 Semantic workflows are not duplicated as utility CLI commands.
 
-### `planr operate`
+### `openplanr operate`
 
 The public Operate namespace supports two distinct products. The installed
 `$planr-operate` skill runs a guidance-first local seven-lens review with no
@@ -535,7 +535,7 @@ named-owner, receipt, evidence-ledger, or blocking-validation prerequisite.
 Its optional note checker reports bounded structural diagnostics:
 
 ```bash
-planr operate validate-note <note.md> --profile advisor|challenger|chair|board-report --contract-version 2.0.0 --json
+openplanr operate validate-note <note.md> --profile advisor|challenger|chair|board-report --contract-version 2.0.0 --json
 ```
 
 Diagnostics are editing help. Missing or malformed lens output remains a
@@ -543,20 +543,20 @@ visible issue with its impact and next action; it does not discard other useful
 findings or force a correction loop. `--contract-version auto` is the default;
 it detects declared or structurally identifiable v1 and v2 Markdown notes.
 
-The other `planr operate` commands expose the durable Protocol 2.0 stateful
+The other `openplanr operate` commands expose the durable Protocol 2.0 stateful
 runtime. For that interface, first discover the installed domains. The command
 returns canonical `domainId`/`domainVersion` pairs and registered roles without
 opening project runtime storage:
 
 ```bash
-planr operate domains --json
+openplanr operate domains --json
 ```
 
 Pass one exact returned identity to Cycle start. Do not substitute the protocol
 version for the domain version.
 
 ```bash
-planr operate start \
+openplanr operate start \
   --scope <scopeId> \
   --domain <domainId> \
   --domain-version <domainVersion> \
@@ -569,9 +569,9 @@ Codex full setup installs every canonical, manifest-owned `planr-*` skill in the
 The durable runtime's issued executors use this file-based packet protocol only:
 
 ```bash
-planr operate assignment prepare <assignmentId> --actor <agentId> --runtime codex --json
-planr operate assignment validate <packetId> --content-file <resultPath|-> --json
-planr operate assignment submit <packetId> --content-file <resultPath|-> --json
+openplanr operate assignment prepare <assignmentId> --actor <agentId> --runtime codex --json
+openplanr operate assignment validate <packetId> --content-file <resultPath|-> --json
+openplanr operate assignment submit <packetId> --content-file <resultPath|-> --json
 ```
 
 `prepare` claims idempotently and returns the exact packet paths. `validate`
@@ -584,45 +584,45 @@ Useful read-only and recovery surfaces:
 
 | Command | Purpose |
 | --- | --- |
-| `planr operate cycle <cycleId> --actor <humanActorId> --json` | Read the exact owner-bound Cycle experience |
-| `planr operate dashboard <cycleId> --actor <humanActorId>` | Open the loopback dashboard |
-| `planr operate recovery storage-status --json` | Inspect neutral storage and migration status |
-| `planr operate assignment recover --json` | Clear only runtime-confirmed abandoned packets |
+| `openplanr operate cycle <cycleId> --actor <humanActorId> --json` | Read the exact owner-bound Cycle experience |
+| `openplanr operate dashboard <cycleId> --actor <humanActorId>` | Open the loopback dashboard |
+| `openplanr operate recovery storage-status --json` | Inspect neutral storage and migration status |
+| `openplanr operate assignment recover --json` | Clear only runtime-confirmed abandoned packets |
 
 Failures from packet commands are bounded in both human and `--json` output;
 machine output contains `ok`, `code`, and `problem` without stack traces or host
-paths. For setup or command parity failures, run `planr doctor --strict --json`.
-Use `planr upgrade status`, then `planr upgrade apply` when doctor reports an
+paths. For setup or command parity failures, run `openplanr doctor --strict --json`.
+Use `openplanr upgrade status`, then `openplanr upgrade apply` when doctor reports an
 incompatible installed CLI. `upgrade apply` prints the new version, up to five
 highlights per release (`--notes full` prints every entry), and the command that
 updates each installed coding agent. The published compatible set is read from the npm
 registry's `latest` CLI document (its version and the exact `planr-pipeline` it
 bundles); `OPENPLANR_ECOSYSTEM_SOURCE` points the check at another URL or file.
 
-### `planr artifact`
+### `openplanr artifact`
 
 Open, share, import, and export native diagrams, designs, and HTML reviews:
 
 ```bash
-planr artifact <file>
-planr artifact open <file> [--title <title>] [--root <asset-root>] [--theme auto|light|dark] [--presentation auto|document|canvas] [--port <port>] [--no-open] [--json]
-planr artifact share <file> [--title <title>] [--root <asset-root>] [--presentation auto|document|canvas] [--snapshot] [--short] [--ttl 1d|7d|30d] [--secret-output <private-file>] [--no-open] [--json] [--yes]
-planr artifact publish <diagram-manifest|diagram-bundle|design-document> [--yes] [--json]
-planr artifact sync <diagram-manifest|diagram-bundle|design-document> [--json]
-planr artifact import --secret-input <private-file|-> [--output <path>] [--allow-stale] [--json] [--yes]
-planr artifact export <session-id> [--format json|markdown] [--output <path>]
+openplanr artifact <file>
+openplanr artifact open <file> [--title <title>] [--root <asset-root>] [--theme auto|light|dark] [--presentation auto|document|canvas] [--port <port>] [--no-open] [--json]
+openplanr artifact share <file> [--title <title>] [--root <asset-root>] [--presentation auto|document|canvas] [--snapshot] [--short] [--ttl 1d|7d|30d] [--secret-output <private-file>] [--no-open] [--json] [--yes]
+openplanr artifact publish <diagram-manifest|diagram-bundle|design-document> [--yes] [--json]
+openplanr artifact sync <diagram-manifest|diagram-bundle|design-document> [--json]
+openplanr artifact import --secret-input <private-file|-> [--output <path>] [--allow-stale] [--json] [--yes]
+openplanr artifact export <session-id> [--format json|markdown] [--output <path>]
 ```
 
 Diagram manifests and authoring bundles share directly to one permanent native
 review per stable `/diagram/<id>` link, with a separate reviewer access token.
 The local studio's **Share diagram** dialog copies the link and token separately.
-Owner credentials stay privately outside the repository. Publish revisions
+Owner keys stay privately outside the repository. Publish revisions
 explicitly; `sync` imports revision-bound feedback without changing the diagram.
 Native diagram sharing does not accept `--snapshot`, `--short`, or `--ttl`;
 export HTML first to choose the generic snapshot transport.
 
 When `--root` is omitted, the artifact file's directory is the asset root. This
-makes `planr artifact share /absolute/path/to/artifact.html` work without
+makes `openplanr artifact share /absolute/path/to/artifact.html` work without
 changing directories or supplying a redundant root. Supported public HTTPS
 dependencies are bundled into the immutable artifact automatically; runtime
 network access remains blocked in the review sandbox.
@@ -650,17 +650,17 @@ invisible opaque-origin Blob sandbox; it is not standalone website publishing.
 
 ---
 
-### `planr rules generate`
+### `openplanr rules generate`
 
 Generate AI agent rule files for Cursor, Claude Code, and/or Codex. Two flags: **`--target`** (which runtime) and **`--scope`** (which workflow — agile or pipeline).
 
 ```bash
-planr rules generate                                       # all targets, agile scope (default)
-planr rules generate --target cursor                       # cursor only, agile scope
-planr rules generate --target cursor --scope pipeline      # cursor pipeline rules (Cursor adapter for planr-pipeline)
-planr rules generate --target codex --scope pipeline       # AGENTS.md with pipeline orchestration section
-planr rules generate --target all --scope all              # everything for everyone
-planr rules generate --dry-run                             # preview without writing
+openplanr rules generate                                       # all targets, agile scope (default)
+openplanr rules generate --target cursor                       # cursor only, agile scope
+openplanr rules generate --target cursor --scope pipeline      # cursor pipeline rules (Cursor adapter for planr-pipeline)
+openplanr rules generate --target codex --scope pipeline       # AGENTS.md with pipeline orchestration section
+openplanr rules generate --target all --scope all              # everything for everyone
+openplanr rules generate --dry-run                             # preview without writing
 ```
 
 | Option              | Description                                       | Default |
@@ -682,7 +682,7 @@ planr rules generate --dry-run                             # preview without wri
 | `claude` × `agile`      | `CLAUDE.md` (agile context-gathering protocol)                                                                |
 | `claude` × `pipeline`   | `CLAUDE.md` with the pipeline block and the `## OpenPlanr capabilities` skill map                          |
 | `codex` × `agile`       | `AGENTS.md` (agile context)                                                                                   |
-| `codex` × `pipeline`    | `AGENTS.md` project policy with the `## OpenPlanr capabilities` skill map; `planr setup` installs the skills |
+| `codex` × `pipeline`    | `AGENTS.md` project policy with the `## OpenPlanr capabilities` skill map; `openplanr setup` installs the skills |
 | `* × all`               | Both scopes side-by-side                                                                                      |
 
 **Cross-runtime support:** v1.0 artifacts plus v1.1 capability contracts run on
@@ -691,13 +691,13 @@ Cursor uses Composer handoff with sequential fallback.
 
 ---
 
-### `planr sync`
+### `openplanr sync`
 
 Validate and repair cross-references across all artifacts.
 
 ```bash
-planr sync                          # fix broken cross-references
-planr sync --dry-run                # preview changes without writing
+openplanr sync                          # fix broken cross-references
+openplanr sync --dry-run                # preview changes without writing
 ```
 
 With the pipeline scope, `CLAUDE.md` and `AGENTS.md` also receive a generated
@@ -720,13 +720,13 @@ Handles both story-level and feature-level task relationships.
 
 ---
 
-### `planr status`
+### `openplanr status`
 
 Show project planning progress with tree view, completion metrics, and color-coded progress.
 
 ```bash
-planr status
-planr status --all
+openplanr status
+openplanr status --all
 ```
 
 | Option  | Description                       | Default                                  |
@@ -743,13 +743,13 @@ planr status --all
 
 ---
 
-### `planr graph`
+### `openplanr graph`
 
 Emit the OpenPlanr artifact graph. `--json` is the stable machine-readable
 contract consumed by `planr-pipeline` dashboard and ecosystem conformance.
 
 ```bash
-planr graph --json
+openplanr graph --json
 ```
 
 | Option   | Description                         | Default |
@@ -760,23 +760,23 @@ The JSON output follows `planr-pipeline/schemas/v1.0.0/graph.schema.json`.
 
 ---
 
-### `planr config show`
+### `openplanr config show`
 
 Display the current deterministic project configuration.
 
 ```bash
-planr config show
+openplanr config show
 ```
 
 ---
 
-### `planr config set-agent`
+### `openplanr config set-agent`
 
 Set the default coding agent for task implementation guidance.
 
 ```bash
-planr config set-agent                   # interactive prompt
-planr config set-agent cursor            # set directly
+openplanr config set-agent                   # interactive prompt
+openplanr config set-agent cursor            # set directly
 ```
 
 | Argument  | Description                    | Required     |
@@ -785,25 +785,25 @@ planr config set-agent cursor            # set directly
 
 ---
 
-### `planr linear init`
+### `openplanr linear init`
 
 Authenticate to [Linear](https://linear.app) with a personal access token, then allow one, several, or all accessible teams. When several teams are enabled, choose the default used by commands that omit `--team`. OpenPlanr saves the allowed `linear.teams` plus the backward-compatible default `linear.teamId` and `linear.teamKey` in `.planr/config.json`. The token is stored via the credentials service (or the `PLANR_LINEAR_TOKEN` environment variable) and is never written into `config.json`.
 
 ```bash
-planr linear init
+openplanr linear init
 ```
 
-`planr linear push <artifact> --team <id-or-key>` targets any team selected during init. A push always targets one team; OpenPlanr does not duplicate an artifact across every team because each artifact has one authoritative Linear linkage.
+`openplanr linear push <artifact> --team <id-or-key>` targets any team selected during init. A push always targets one team; OpenPlanr does not duplicate an artifact across every team because each artifact has one authoritative Linear linkage.
 
-### `planr linear sync`
+### `openplanr linear sync`
 
-**Two steps in one command:** (1) **bidirectional workflow status sync** for every Feature, Story, Quick task, and Backlog item with a `linearIssueId` — three-way merge between local frontmatter, Linear's workflow state, and a stored baseline; (2) run **task checklist** sync (`TASK-*.md` ↔ Linear) for all task files that share a `linearIssueId` (see `planr linear tasklist-sync`). Use `--verbose` to log per-artifact work.
+**Two steps in one command:** (1) **bidirectional workflow status sync** for every Feature, Story, Quick task, and Backlog item with a `linearIssueId` — three-way merge between local frontmatter, Linear's workflow state, and a stored baseline; (2) run **task checklist** sync (`TASK-*.md` ↔ Linear) for all task files that share a `linearIssueId` (see `openplanr linear tasklist-sync`). Use `--verbose` to log per-artifact work.
 
 ```bash
-planr linear sync
-planr linear sync --dry-run
-planr linear sync --on-conflict linear
-planr --verbose linear sync
+openplanr linear sync
+openplanr linear sync --dry-run
+openplanr linear sync --on-conflict linear
+openplanr --verbose linear sync
 ```
 
 | Option | Description |
@@ -823,7 +823,7 @@ Each artifact's status decision considers three values: `local` (current frontma
 | Both diverged from `base` (or `base` missing and they disagree) | **Conflict** → resolve per `--on-conflict`. |
 | Backlog local is `promoted` | Never overwritten (`promoted` is local-only and implies a target pointer Linear can't know about). |
 
-`planr quick update --status <v>` and `planr backlog update --status <v>` automatically clear `linearStatusReconciled` so the next sync sees a local change and pushes it up.
+`openplanr quick update --status <v>` and `openplanr backlog update --status <v>` automatically clear `linearStatusReconciled` so the next sync sees a local change and pushes it up.
 
 **Status sync coverage**
 
@@ -834,7 +834,7 @@ Each artifact's status decision considers three values: `local` (current frontma
 | backlog (`BL-`) | `open` · `closed` · `promoted` | ✅ (never auto-overwrites `promoted`) |
 | task (`TASK-`) | `pending` · `in-progress` · `done` (per-file) | ✅ push (aggregated to merged TaskList issue); pull deferred — see below |
 
-**TASK aggregation on push.** A single Linear TaskList issue aggregates every `TASK-NNN.md` file under one feature (one issue, multiple checkbox lists merged). `planr linear push` resolves a single workflow stateId for that issue using the rule:
+**TASK aggregation on push.** A single Linear TaskList issue aggregates every `TASK-NNN.md` file under one feature (one issue, multiple checkbox lists merged). `openplanr linear push` resolves a single workflow stateId for that issue using the rule:
 
 | Local task-file statuses | Linear TaskList state |
 |---|---|
@@ -843,9 +843,9 @@ Each artifact's status decision considers three values: `local` (current frontma
 | Mix of `done` + `pending` (no in-progress) | In Progress (`started`) — work has begun |
 | All `pending` | Todo (`unstarted`) |
 
-The `--all-done` flag on `planr task update` (see above) is the recommended path: flipping every checkbox in a task file to `[x]` and setting `status: done` makes the next `planr linear push FEAT-XXX` move the merged TaskList issue to Done.
+The `--all-done` flag on `openplanr task update` (see above) is the recommended path: flipping every checkbox in a task file to `[x]` and setting `status: done` makes the next `openplanr linear push FEAT-XXX` move the merged TaskList issue to Done.
 
-**Pull-side TASK propagation** (Linear → all task files under feature) is tracked separately — partial-disagreement guards aren't trivial. `planr linear tasklist-sync` continues to handle per-checkbox sync as today.
+**Pull-side TASK propagation** (Linear → all task files under feature) is tracked separately — partial-disagreement guards aren't trivial. `openplanr linear tasklist-sync` continues to handle per-checkbox sync as today.
 
 **Baseline frontmatter fields** (written by sync, optional; missing = no prior sync):
 
@@ -856,7 +856,7 @@ The `--all-done` flag on `planr task update` (see above) is the recommended path
 
 **Estimate sync**
 
-`planr linear push` also writes an artifact's reviewed `estimatedPoints` or `storyPoints` to Linear's native Issue estimation field, per the team's configured scale:
+`openplanr linear push` also writes an artifact's reviewed `estimatedPoints` or `storyPoints` to Linear's native Issue estimation field, per the team's configured scale:
 
 | Team scale | Behavior |
 |---|---|
@@ -868,11 +868,11 @@ The `--all-done` flag on `planr task update` (see above) is the recommended path
 
 Applies to FEAT / US / QT / BL pushes. TASK is intentionally out of scope — one Linear TaskList issue aggregates multiple local `TASK-*.md` files (same rationale as the TASK status deferral), so estimate aggregation rules are tracked as a follow-up.
 
-The team scale is auto-detected per push run and cached. Set a reviewed `estimatedPoints: <n>` in the artifact frontmatter, then `planr linear push` sends it.
+The team scale is auto-detected per push run and cached. Set a reviewed `estimatedPoints: <n>` in the artifact frontmatter, then `openplanr linear push` sends it.
 
 **Status-name aliases (push side):** values like `completed`, `cancelled`, `canceled`, and `todo` on a QT/feature/story are transparently treated as `done`/`pending` so hand-edited frontmatter using Linear's native vocabulary still works.
 
-**Zero-config auto-derive:** on every push run, `planr linear push` fetches the team's workflow states once and auto-derives a status→stateId map from Linear's canonical state **types** (`backlog` / `unstarted` / `started` / `completed` / `canceled`). You don't need to configure anything for basic status sync to work — the first `pending`/`open` state of each canonical type becomes the default. Configure `linear.pushStateIds` only when you want non-default routing (e.g., push `done` to "Released" instead of the first `completed` state).
+**Zero-config auto-derive:** on every push run, `openplanr linear push` fetches the team's workflow states once and auto-derives a status→stateId map from Linear's canonical state **types** (`backlog` / `unstarted` / `started` / `completed` / `canceled`). You don't need to configure anything for basic status sync to work — the first `pending`/`open` state of each canonical type becomes the default. Configure `linear.pushStateIds` only when you want non-default routing (e.g., push `done` to "Released" instead of the first `completed` state).
 
 **Config:** `linear.statusMap` — keys are Linear state names (e.g. `"Code Review"`), values are one of `pending`, `in-progress`, `done` for tasks/stories/features/QT, or one of `open`, `closed`, `promoted` for BL. `linear.pushStateIds` — local status → Linear workflow state UUID; takes precedence over the auto-derived defaults. For backlog, use `open`/`closed`/`promoted` keys directly (BL has no implicit coercion to the task vocabulary).
 
@@ -893,33 +893,33 @@ The team scale is auto-detected per push run and cached. Set a reviewed `estimat
 }
 ```
 
-### `planr linear status`
+### `openplanr linear status`
 
 **Local only** — no Linear API. Prints a text table: OpenPlanr id, Linear identifier, URL, last-known `status` (or em dash for epics), and a note for malformed or stale `linearIssueId` values (e.g. a workflow state uuid mistaken for an issue id).
 
 ```bash
-planr linear status
-planr linear status --scope EPIC-001
+openplanr linear status
+openplanr linear status --scope EPIC-001
 ```
 
-### `planr linear push`
+### `openplanr linear push`
 
-Create or update Linear entities for any planning artifact, at the smallest scope the id implies. Accepts any supported prefix — `EPIC-`, `FEAT-`, `US-`, `TASK-`, `QT-`, `BL-` — and writes `linearProject*` / `linearIssue*` / `linearMilestoneId` / `linearLabelId` / `linearProjectMilestoneId` / `linearLabelIds` / `linearTaskChecklistSyncedAt` back to artifact frontmatter. Requires `planr linear init` and a team id in config.
+Create or update Linear entities for any planning artifact, at the smallest scope the id implies. Accepts any supported prefix — `EPIC-`, `FEAT-`, `US-`, `TASK-`, `QT-`, `BL-` — and writes `linearProject*` / `linearIssue*` / `linearMilestoneId` / `linearLabelId` / `linearProjectMilestoneId` / `linearLabelIds` / `linearTaskChecklistSyncedAt` back to artifact frontmatter. Requires `openplanr linear init` and a team id in config.
 
 ```bash
-planr linear push EPIC-001                              # full subtree: project + features + stories + tasklists + linked QT/BL
-planr linear push FEAT-015                              # just one feature + its stories + its tasklist
-planr linear push US-054                                # just one story
-planr linear push TASK-015                              # just one tasklist sub-issue
-planr linear push QT-007                                # standalone quick task (or epic-linked if QT has epicId)
-planr linear push BL-001                                # backlog item (auto `backlog` label)
-planr linear push EPIC-001 --dry-run                    # local preview only; no Linear API calls
-planr linear push EPIC-001 --update-only                # only update existing linked entities
-planr linear push FEAT-015 --push-parents               # if the parent epic isn't pushed yet, push it first (upward attachment only)
-planr linear push FEAT-015 --no-cascade                 # push only this feature — skip its stories and tasklist
-planr linear push EPIC-001 --no-cascade                 # push only the epic project — no features
-planr linear push TASK-004 --push-parents               # push parent feature (no sibling stories) + this tasklist
-planr linear push EPIC-001 --as milestone-of:<projectId># first-time mapping strategy override
+openplanr linear push EPIC-001                              # full subtree: project + features + stories + tasklists + linked QT/BL
+openplanr linear push FEAT-015                              # just one feature + its stories + its tasklist
+openplanr linear push US-054                                # just one story
+openplanr linear push TASK-015                              # just one tasklist sub-issue
+openplanr linear push QT-007                                # standalone quick task (or epic-linked if QT has epicId)
+openplanr linear push BL-001                                # backlog item (auto `backlog` label)
+openplanr linear push EPIC-001 --dry-run                    # local preview only; no Linear API calls
+openplanr linear push EPIC-001 --update-only                # only update existing linked entities
+openplanr linear push FEAT-015 --push-parents               # if the parent epic isn't pushed yet, push it first (upward attachment only)
+openplanr linear push FEAT-015 --no-cascade                 # push only this feature — skip its stories and tasklist
+openplanr linear push EPIC-001 --no-cascade                 # push only the epic project — no features
+openplanr linear push TASK-004 --push-parents               # push parent feature (no sibling stories) + this tasklist
+openplanr linear push EPIC-001 --as milestone-of:<projectId># first-time mapping strategy override
 ```
 
 | Argument / option           | Description                                                                                                                                    | Required |
@@ -967,21 +967,21 @@ Quick tasks and backlog items push as top-level issues in a user-chosen standalo
 
 **Epic-linked QT / BL**
 
-A QT or BL file with `epicId: "EPIC-XXX"` (or legacy `parentEpic`) in frontmatter is pulled into that epic's Linear container instead of the standalone project. `planr linear push EPIC-XXX` cascades to every linked QT/BL. Unlinked ones stay in the standalone project. `planr quick create --epic` and `planr backlog add --epic` set the link at creation time.
+A QT or BL file with `epicId: "EPIC-XXX"` (or legacy `parentEpic`) in frontmatter is pulled into that epic's Linear container instead of the standalone project. `openplanr linear push EPIC-XXX` cascades to every linked QT/BL. Unlinked ones stay in the standalone project. `openplanr quick create --epic` and `openplanr backlog add --epic` set the link at creation time.
 
-**Mapping:** Epic → Linear project (or milestone / label — see strategies above); feature → top-level issue; story → sub-issue of the feature issue; per-feature merged task list → sub-issue; linked QT/BL → top-level issue in the epic's container. Optional `linear.pushStateIds` maps `pending` / `in-progress` / `done` to Linear workflow **state id** (uuid). Optional `linear.defaultProjectLead` is the Linear user id for project `leadId`. See `planr linear sync` for pulling status **from** Linear into frontmatter.
+**Mapping:** Epic → Linear project (or milestone / label — see strategies above); feature → top-level issue; story → sub-issue of the feature issue; per-feature merged task list → sub-issue; linked QT/BL → top-level issue in the epic's container. Optional `linear.pushStateIds` maps `pending` / `in-progress` / `done` to Linear workflow **state id** (uuid). Optional `linear.defaultProjectLead` is the Linear user id for project `leadId`. See `openplanr linear sync` for pulling status **from** Linear into frontmatter.
 
 **Idempotency:** Re-running the command updates the same project and issues when Linear ids are already stored in frontmatter. No duplicate creates.
 
 **Resilience:** A malformed artifact file (unparseable frontmatter, missing title, broken YAML) is skipped with a clear warning and the rest of the push proceeds — one broken file no longer aborts the whole run.
 
-### `planr linear tasklist-sync`
+### `openplanr linear tasklist-sync`
 
 Bidirectionally sync **checkbox** state between local `TASK-*.md` files and the corresponding Linear **TaskList** issues (`linearIssueId` in frontmatter). OpenPlanr reuses a single Linear issue for multiple task files in the same feature by using `## TASK-...` sections; a single file maps to the whole description. A three-way merge uses `linearChecklistReconciled` in each task’s frontmatter as the last known agreement; on divergence you can be prompted, or set `--on-conflict local` or `--on-conflict linear` (e.g. in CI).
 
 ```bash
-planr linear tasklist-sync
-planr linear tasklist-sync --on-conflict linear
+openplanr linear tasklist-sync
+openplanr linear tasklist-sync --on-conflict linear
 ```
 
 | Argument / option        | Description | Required |
@@ -990,14 +990,14 @@ planr linear tasklist-sync --on-conflict linear
 
 ---
 
-### `planr github push`
+### `openplanr github push`
 
 Push planning artifacts to GitHub Issues. Requires `gh` CLI to be installed and authenticated (`gh auth login`).
 
 ```bash
-planr github push EPIC-001              # push a single artifact
-planr github push --epic EPIC-001       # push all artifacts under an epic
-planr github push --all                 # push all artifacts
+openplanr github push EPIC-001              # push a single artifact
+openplanr github push --epic EPIC-001       # push all artifacts under an epic
+openplanr github push --all                 # push all artifacts
 ```
 
 | Argument/Option   | Description                         | Required                                    |
@@ -1016,15 +1016,15 @@ planr github push --all                 # push all artifacts
 
 ---
 
-### `planr github sync`
+### `openplanr github sync`
 
 Bi-directional status sync between local artifacts and GitHub Issues.
 
 ```bash
-planr github sync                       # interactive conflict resolution (both directions)
-planr github sync --direction pull      # GitHub → local (update local status from issue state)
-planr github sync --direction push      # local → GitHub (update issue state from local status)
-planr github sync --direction both      # both with interactive conflict resolution (default)
+openplanr github sync                       # interactive conflict resolution (both directions)
+openplanr github sync --direction pull      # GitHub → local (update local status from issue state)
+openplanr github sync --direction push      # local → GitHub (update issue state from local status)
+openplanr github sync --direction both      # both with interactive conflict resolution (default)
 ```
 
 | Option              | Description               | Default |
@@ -1033,40 +1033,40 @@ planr github sync --direction both      # both with interactive conflict resolut
 
 **Status mapping:**
 
-- GitHub `open` → local `in-progress` / `draft`
-- GitHub `closed` → local `done` / `accepted`
-- Local `done` → closes the GitHub issue
-- Conflicts (both changed) → interactive prompt to choose which side wins
+- An issue is closed when its item is `done` and open for every other status.
+- `--direction pull`: a closed issue marks its item `done`, and an open issue for a `done` item
+  marks it `in-progress`. Other statuses stay as they are.
+- `--direction push`: a `done` item closes its issue; any other status reopens it.
+- `--direction both`: asks which side wins for each item whose status and issue state disagree.
 
 ---
 
-### `planr github status`
+### `openplanr github status`
 
 Show sync status of all linked artifacts.
 
 ```bash
-planr github status
+openplanr github status
 ```
 
 Displays a table of all artifacts that have a `githubIssue` field, showing local status vs GitHub issue state and whether they are in sync.
 
 ---
 
-### `planr report`
+### `openplanr report`
 
 Generate a stakeholder report from `.planr/` artifacts and (optionally) recent
 GitHub activity. The commands below define the packaged reporting surface.
 
 ```bash
-planr report weekly                                   # markdown to .planr/reports/
-planr report sprint --sprint SPRINT-001               # sprint summary for one sprint
-planr report executive --format html                  # HTML wrapper around the markdown
-planr report weekly --stdout                          # print to stdout, no file
-planr report weekly --no-github                       # skip the gh API calls
-planr report weekly --lint                            # run the quality linter on the output
-planr report weekly --strict-evidence                 # fail if bullet claims lack URLs or #issue refs
-planr report weekly --push slack --dry-run            # show what would be posted to Slack
-planr report sprint --push github                     # archive as a planr:report GitHub issue
+openplanr report weekly                                   # markdown to .planr/reports/
+openplanr report sprint --sprint SPRINT-001               # sprint summary for one sprint
+openplanr report executive --format html                  # HTML wrapper around the markdown
+openplanr report weekly --stdout                          # print to stdout, no file
+openplanr report weekly --no-github                       # skip the gh API calls
+openplanr report weekly --lint                            # run the quality linter on the output
+openplanr report weekly --strict-evidence                 # fail if bullet claims lack URLs or #issue refs
+openplanr report sprint --push github                     # archive as a planr:report GitHub issue
 ```
 
 | Option                | Description                                                                              | Default            |
@@ -1080,8 +1080,8 @@ planr report sprint --push github                     # archive as a planr:repor
 | `--stdout`            | Print markdown to stdout instead of writing a file                                       | `false`            |
 | `--lint`              | Run the report quality linter on the generated markdown                                  | `false`            |
 | `--strict-evidence`   | Fail if substantive bullets under `##` (except **Evidence**) lack URLs or `#NNN` refs; skips full-line `_placeholder_` bullets | `false`            |
-| `--push <targets>`    | Comma-separated channels: `github`, `slack`                                              | None               |
-| `--dry-run`           | With `--push`, show actions without sending (Slack dry-run works without a webhook)      | `false`            |
+| `--push <targets>`    | Comma-separated channels: `github`                                                       | None               |
+| `--dry-run`           | With `--push`, show actions without sending                                              | `false`            |
 
 **Output files:** `.planr/reports/<YYYY-MM-DD>-<reportType>-report.md` (and `.html` when `--format html`, same basename). Example: `2026-04-19-weekly-report.md`.
 
@@ -1097,25 +1097,21 @@ planr report sprint --push github                     # archive as a planr:repor
       "Compliance": "SOC2 controls verified weekly."
     }
   },
-  "templateOverrides": "./reports-overrides",
-  "distribution": {
-    "slackWebhookUrl": "https://hooks.slack.com/services/...",
-    "slackChannel": "#eng-updates"
-  }
+  "templateOverrides": "./reports-overrides"
 }
 ```
 
-`slackChannel` is reserved for future use; Incoming Webhooks target the channel encoded in the webhook URL. All blocks are optional; the command works against a freshly initialized project.
+All blocks are optional; the command works against a freshly initialized project.
 
 ---
 
-### `planr report-linter`
+### `openplanr report-linter`
 
-Lint an existing stakeholder markdown file (or stdin) against the same rules `planr report --lint` runs.
+Lint an existing stakeholder markdown file (or stdin) against the same rules `openplanr report --lint` runs.
 
 ```bash
-planr report-linter ./drafts/weekly.md --type weekly
-cat drafts/sprint.md | planr report-linter --type sprint
+openplanr report-linter ./drafts/weekly.md --type weekly
+cat drafts/sprint.md | openplanr report-linter --type sprint
 ```
 
 | Option         | Description                                                                          | Default    |
@@ -1145,14 +1141,14 @@ Each `pattern` is a case-insensitive regular expression. A pattern that does not
 
 ---
 
-### `planr context`
+### `openplanr context`
 
 Print the report context pack — artifacts, sprint state, GitHub signals, and the flat evidence index — as JSON for piping into other tools.
 
 ```bash
-planr context --report-type weekly
-planr context --report-type sprint --sprint SPRINT-001 --days 14
-planr context --report-type weekly | jq '.evidence | length'
+openplanr context --report-type weekly
+openplanr context --report-type sprint --sprint SPRINT-001 --days 14
+openplanr context --report-type weekly | jq '.evidence | length'
 ```
 
 | Option                 | Description                                                                  | Default    |
@@ -1166,16 +1162,16 @@ The JSON payload is written to stdout; a one-line summary (`context: <n> evidenc
 
 ---
 
-### `planr voice standup`
+### `openplanr voice standup`
 
 Convert a transcript file (or stdin) into structured standup markdown using a heuristic Yesterday / Today / Blockers parser. Live microphone capture and bundled speech-to-text are intentionally **not** part of v1 — pair this with any STT or OS dictation tool that produces text.
 
 ```bash
-planr voice standup --file standups/2026-04-19.txt
-planr voice standup --file t.txt --lint
-planr voice standup --file t.txt --append-story US-029
-planr voice standup --file t.txt --edit          # interactive: open $EDITOR before saving
-planr voice standup --file t.txt --reload-file   # interactive: re-read file after editing externally
+openplanr voice standup --file standups/2026-04-19.txt
+openplanr voice standup --file t.txt --lint
+openplanr voice standup --file t.txt --append-story US-029
+openplanr voice standup --file t.txt --edit          # interactive: open $EDITOR before saving
+openplanr voice standup --file t.txt --reload-file   # interactive: re-read file after editing externally
 ```
 
 | Option                       | Description                                                                                  | Default       |
@@ -1191,16 +1187,16 @@ Per-segment audio replay is reserved (`TranscriptSegment.audioOffsetMs` exists i
 
 ---
 
-### `planr export`
+### `openplanr export`
 
 Generate a consolidated planning report in markdown, JSON, or HTML format.
 
 ```bash
-planr export                                    # markdown report in current directory
-planr export --format html                      # self-contained HTML report
-planr export --format json                      # machine-readable JSON
-planr export --format html --scope EPIC-001     # only artifacts under one epic
-planr export --output ./reports                 # custom output directory
+openplanr export                                    # markdown report in current directory
+openplanr export --format html                      # self-contained HTML report
+openplanr export --format json                      # machine-readable JSON
+openplanr export --format html --scope EPIC-001     # only artifacts under one epic
+openplanr export --output ./reports                 # custom output directory
 ```
 
 | Option              | Description                                  | Default                 |
@@ -1223,29 +1219,29 @@ planr export --output ./reports                 # custom output directory
 Use the CLI to maintain deterministic repository artifacts; invoke host skills for semantic planning and implementation:
 
 ```text
-planr init
-  └─ planr epic create "Platform renewal"
-       └─ planr feature create "OAuth sign-in" --epic EPIC-001
-            └─ planr story create "Company sign-in" --feature FEAT-001
-                 └─ planr task create "Implement approved flow" --story US-001
-
-planr backlog add "Investigate callback failures" --priority high
-planr backlog list
-planr backlog update BL-001 --status closed
-
-planr sprint create "Sprint 1" --duration 2w
-planr sprint list
-planr sprint show SPRINT-001
-planr sprint refinement SPRINT-001 --data refinement.json
-planr sprint apply SPRINT-001 --yes --commit
-planr sprint close SPRINT-001
-
-planr sync
-planr status
-planr rules generate
-planr github push --all
-planr github sync
-planr export --format html
+openplanr init
+  └─ openplanr epic create "Platform renewal"
+       └─ openplanr feature create "OAuth sign-in" --epic EPIC-001
+            └─ openplanr story create "Company sign-in" --feature FEAT-001
+                 └─ openplanr task create "Implement approved flow" --story US-001
+
+openplanr backlog add "Investigate callback failures" --priority high
+openplanr backlog list
+openplanr backlog update BL-001 --status closed
+
+openplanr sprint create "Sprint 1" --duration 2w
+openplanr sprint list
+openplanr sprint show SPRINT-001
+openplanr sprint refinement SPRINT-001 --data refinement.json
+openplanr sprint apply SPRINT-001 --yes --commit
+openplanr sprint close SPRINT-001
+
+openplanr sync
+openplanr status
+openplanr rules generate
+openplanr github push --all
+openplanr github sync
+openplanr export --format html
 ```
 
 For semantic decomposition, invoke the installed `planr:plan` skill. After reviewing the plan, invoke `planr:ship` separately.