openplanr 3.4.0 → 3.6.0

package/lib/host-packages/claude/openplanr/skills/design-review/references/utilities.md

@@ -1,26 +1,71 @@
-# Bundled design utilities
+# Design utilities
 
-Run the linked design helper from the skill entrypoint relative to the skill's
-directory. It contains deterministic operations and all required assets. It needs
-Node.js 22.13 or later, with no provider credentials. Local design work needs no global
-CLI. Sharing a design for company review runs in the `openplanr` CLI, which holds the
-owner keys. Only `fonts fetch` downloads anything, and only when run; nothing is
-fetched when a design opens.
-Use `--help` to inspect the installed command interface before writing documents
-or invoking operations; the installed contract is authoritative.
+Design operations run in the `openplanr` CLI. They are deterministic, need Node.js
+22.13 or later and no provider credentials. Only `fonts fetch` downloads anything,
+and only when run; nothing is fetched when a design opens. Use `--help` on a
+command to inspect the installed interface before writing documents or invoking
+operations; the installed contract is authoritative.
+
+## Check the design runtime
+
+Run this once, before consultation, and check whether the host's artifact tool
+offers a design quickstart or a Design artifact type:
 
 ```sh
-node scripts/design.mjs inspect <design-document.json> --json
-node scripts/design.mjs validate <design-document.json> --json
-node scripts/design.mjs render <design-document.json> --json
-node scripts/design.mjs open <design-document.json> --view canvas --no-open --json
-node scripts/design.mjs feedback <design-document.json> --action inspect --json
-node scripts/design.mjs view-context <design-document.json> --json
-node scripts/design.mjs studio <design-document.json> --action status --json
-node scripts/design.mjs studio <design-document.json> --action stop --json
-node scripts/design.mjs fonts fetch --family "<Name>:<weights>" [--family ...] --dest <design>/source/assets/fonts --json
+openplanr design capabilities --json
 ```
 
+These skills need design contract 1. Treat a successful
+`openplanr design capabilities --json` as proof the runtime is ready. Never locate
+or import the OpenPlanr workflow package, inspect `node_modules`, or call internal
+runtime modules. Use the `openplanr` on `PATH`; never search for another one or
+for bundled design scripts. A failed probe means the matching stop below.
+
+| Probe result | Runtime | Next action |
+|---|---|---|
+| `ok: true` and `supported.min` ≤ 1 ≤ `supported.max` | Ready | Use the commands below. |
+| `openplanr` not found | Stop 1: no CLI | `npm install -g openplanr` |
+| `unknown command 'design'`, `E_DESIGN_RUNTIME_UNSUPPORTED`, or a `supported` range without 1 | Stop 2: CLI too old | `npm install -g openplanr@latest` |
+| `ok: false` with `E_DESIGN_RUNTIME_MISSING` and `pipeline: null` | Stop 3: CLI without its workflow package | `npm install -g openplanr`, run without `--omit=optional` |
+
+A design on the hosted canvas needs no CLI. At a stop, consultation and
+authoring still happen: author `design-document.json`, its sources and
+`design-spec.md`, mark them **unverified**, and say that no studio was rendered or
+checked. End with every next action that applies, each one the user can run: the
+stop's command, and the host action below. On Claude Code without a Design
+artifact type, that is the command and the canvas actions. Then ask the user to
+run the skill again.
+
+| Host | Notes |
+|---|---|
+| Claude Code | Design builds on the hosted canvas when the artifact tool offers a Design type. When it does not, also name the canvas actions: sign in with `/login` on a claude.ai Pro, Max, Ultra, Team or Enterprise plan; or, when artifacts are turned off, re-enable them in `/config`. An API key or gateway token means no claude.ai login: name `/login` with a claude.ai plan, or the CLI. On Bedrock, Google Cloud or Foundry, or in an organisation with CMEK, HIPAA or Zero Data Retention, the canvas is unavailable and the CLI is the path. |
+| Codex | The stop's command. `openplanr setup` installs the workflow package beside the skills, but `PATH` can resolve a different `openplanr`; `which openplanr` shows the one that runs. Codex's default `workspace-write` sandbox stops the studio: `design open` fails with `listen EPERM`. Tell the user to run `openplanr design open <design-document.json>` in their own terminal, or to restart Codex with `-c sandbox_workspace_write.network_access=true -c 'sandbox_workspace_write.writable_roots=["<absolute path of ~/.planr>"]'` (use `PLANR_HOME` instead when it is set). That setting also lets commands reach the network. |
+| Cursor | The stop's command. `openplanr setup` installs the workflow package beside the skills, but `PATH` can resolve a different `openplanr`; `which openplanr` shows the one that runs. |
+| ChatGPT | Without a local shell, take stop 1: deliver the unverified sources and specification, and name `npm install -g openplanr` for a coding agent with a shell. |
+
+## Commands
+
+Run these from the project directory. Paths resolve against it.
+
+```sh
+openplanr design inspect <design-document.json> --json
+openplanr design validate <design-document.json> --json
+openplanr design render <design-document.json> --json
+openplanr design open <design-document.json> --view canvas --no-open --json
+openplanr design view-context <design-document.json> --json
+openplanr design verify <design-document.json> --report <browser-report.json> --json
+openplanr design export <design-document.json> --view canvas --format html --output <path> --json
+openplanr design studio status <design-document.json> --json
+openplanr design studio stop <design-document.json> --json
+openplanr design fonts fetch --family "<Name>:<weights>" [--family ...] --dest <design>/source/assets/fonts --json
+openplanr artifact feedback <design-document.json> --action inspect --json
+```
+
+`render` reads the specification at the path in [handoff.md](handoff.md), so write
+`design-spec.md` before the first render. The CLI prints `<path>` in place of
+absolute paths, so an `ENOENT` names no file: check that `design-spec.md` and
+every source the document names exist before suspecting the CLI.
+
 `fonts fetch` snapshots at most two OFL or Apache families, three weights each, as
 Latin `woff2` files with their license files and a local `fonts.css`. It needs network
 access; ask the user to approve that one command. A host that allowlists domains needs
@@ -30,9 +75,9 @@ access; ask the user to approve that one command. A host that allowlists domains
 [design-system.md](design-system.md) for the fallback.
 
 Use `--view prototype` or `--view walkthrough` to select the initial presentation.
-When an `openplanr` CLI is available, prefer its public `openplanr artifact` route for
-opening the document; otherwise use this bundled script. Both compose the same
-design and artifact runtime, preserving feedback and view behavior.
+`design open` keeps the studio running until it is stopped, so run it in the
+background. `openplanr artifact open <design-document.json>` opens the same studio,
+preserving feedback and view behavior.
 
 `view-context` returns validated live viewer data, or `{ viewContext: null, reason }`
 when unavailable or stale. Use `--request-time <ISO-timestamp>` to reject context
@@ -51,12 +96,12 @@ Opening a completed design reuses its healthy local service and returns a short
 Studio; a service hosting several designs offers a selection page. Keep the
 returned URL instead of constructing one from export paths.
 
-Use `studio --action status` to find the healthy service for this design. Its
+Use `design studio status` to find the healthy service for this design. Its
 `status: running` reports service availability; `browserStatus` reports observed
 preview loading separately, and `verification` reports actual saved checks.
 Startup alone does not mean a design is ready or verified.
 
-Use `studio --action stop` to authenticate the exact owned live instance and drain
+Use `design studio stop` to authenticate the exact owned live instance and drain
 pending saves; it does not signal a process by PID. `status: stopping` means
 shutdown was accepted. Run status again to confirm it stopped. Feedback, ratings
 and arrangement remain in their canonical stores and survive reopening.
@@ -65,7 +110,7 @@ A healthy service with different settings, an older runtime, or an unvalidated
 session must be stopped before reopening. When its launcher record is missing,
 stop can recover the sole authenticated owner for this design. If several owned
 services remain, inspect status and choose one explicitly with
-`studio <design-document.json> --action stop --instance-id <id>`. An instance from
+`openplanr design studio stop <design-document.json> --instance-id <id>`. An instance from
 another project or state directory is rejected. Hosted shares continue independently.
 
 ## Import downloaded feedback
@@ -73,7 +118,7 @@ another project or state directory is rejected. Hosted shares continue independe
 Explicitly reconcile downloaded feedback with the canonical local ledger:
 
 ```sh
-node scripts/design.mjs feedback <design-document.json> --action import --input <downloaded-review.json> --revision <current-render-revision> --json
+openplanr artifact feedback <design-document.json> --action import --input <downloaded-review.json> --revision <current-render-revision> --json
 ```
 
 Read `feedback --action inspect` first and pass its current `revision` internally;
@@ -110,16 +155,11 @@ The design remains accessible when the local machine is offline. Owner authority
 saves automatically in a protected user-level file outside the project; recovery
 export is optional. Only copy the reviewer token through the explicit Share controls.
 
-Sharing needs the OpenPlanr CLI (`npm install -g openplanr`). The bundled utility's
-`share`, `publish`, `sync` and `manage` commands, the studio's Share dialog, and handoff
-decisions on a shared design all run `openplanr artifact` for the network step, so the
-helper itself reads no owner keys. `share` creates or retries a review, `publish` sends
-an explicitly requested new revision to the existing URL, and `sync` retrieves
-authenticated feedback. You can also run the CLI directly: `openplanr artifact share`,
-`publish`, `sync`, `status`, `manage`, `feedback` and `handoff`. Without the CLI,
-sharing commands stop with `E_DESIGN_SHARE_CLI_REQUIRED`, and feedback inspection
-still works but reports that sync was skipped. A helper and CLI with different sharing
-formats refuse with `E_DESIGN_SHARE_RUNTIME_MISMATCH`; update whichever is older.
+Sharing runs in the `openplanr` CLI, which holds the owner keys:
+`openplanr artifact share`, `publish`, `sync`, `status`, `manage`, `feedback` and
+`handoff`, and the studio's Share dialog. `share` creates or retries a review,
+`publish` sends an explicitly requested new revision to the existing URL, and
+`sync` retrieves authenticated feedback.
 
 Retention is until the owner revokes or deletes the review, while the service is
 maintained. The owner can pause comments and rotate access tokens. Rotation blocks
@@ -129,9 +169,9 @@ saved operation and use its retry path. Report service unavailability explicitly
 
 ## Team review and handoff
 
-`openplanr artifact handoff <design-document.json>` and the bundled
-`node scripts/design.mjs handoff <design-document.json>` prepare or refresh a
-factual review handoff. Use `--json` for structured results and consult `--help`
+`openplanr artifact handoff <design-document.json>` prepares or refreshes a
+factual review handoff, and `openplanr design handoff <design-document.json>`
+inspects it. Use `--json` for structured results and consult `--help`
 for inspection, update and approval actions. Follow [team-review.md](team-review.md)
 for active-agent refinement and owner approval. These deterministic operations do
 not call a provider, publish a design or start Plan/Ship.

package/lib/host-packages/claude/openplanr/skills/investigate/SKILL.md

@@ -28,9 +28,8 @@ Prove the regression test with [fail-first](references/fail-first.md).
 
 Report other defects you notice as [findings](references/findings.md), and never
 fix them in this change unless they block the requested fix. The established cause
-is never a finding. The packaged [backlog helper](scripts/backlog-item.mjs) lists
-and files backlog items when no CLI is installed; resolve it relative to this
-`SKILL.md`.
+is never a finding. [Backlog filing](references/backlog-filing.md) lists and files
+backlog items with your own file tools.
 
 ## Return
 

package/lib/host-packages/claude/openplanr/skills/investigate/references/backlog-filing.md

@@ -0,0 +1,102 @@
+# Backlog filing
+
+List and file backlog items with your own file tools. If `openplanr` is already on
+`PATH`, you may instead send each item as one JSON object on stdin to
+`openplanr --project-dir <repository-root> backlog add --data - --json`.
+
+## Where items live
+
+1. Read `.planr/config.json` at the repository root. If it is missing or is not
+   valid JSON, stop and report that the project has no OpenPlanr configuration.
+2. The backlog folder is `<outputPaths.agile>/backlog`, with `outputPaths.agile`
+   defaulting to `.planr`. The ID prefix is `idPrefix.backlog`, default `BL`.
+3. Issued IDs are empty marker files in `<backlog folder>/.issued-ids/`.
+
+## List open items
+
+List the files named `<PREFIX>-NNN-<slug>.md` in the backlog folder and read each
+frontmatter's `id`, `title` and `status`. An item is open unless its `status` is
+`closed` or `done`; a missing `status` counts as open.
+
+## Take an ID
+
+Do this immediately before writing each item, never earlier in the run:
+
+1. List the backlog folder and `.issued-ids/` again; create `.issued-ids/` if it is
+   missing.
+2. Find the highest `<PREFIX>-NNN` number among the file names in both. The new
+   number is that plus 1, or 1 when there is none, padded to at least 3 digits
+   (`BL-007`, `BL-1000`).
+3. Claim it by creating the empty file `.issued-ids/<ID>`. In a POSIX shell use a
+   no-clobber create, `(set -C; : > '<backlog folder>/.issued-ids/<ID>')`, or
+   elsewhere any create that fails when the file already exists, and treat a
+   failure as the ID being taken.
+4. If the marker already existed or any `<ID>-*.md` file exists, take the next
+   number and repeat step 3.
+
+Never overwrite or edit an existing backlog file or marker. A marker outlives its
+item, so the ID of a deleted item is never issued again.
+
+## Write the item
+
+Name the file `<ID>-<slug>.md` in the backlog folder. The slug is the title in
+lowercase with every character other than ASCII letters, digits, `_`, `-` and
+whitespace removed, runs of whitespace, `_` and `-` turned into one `-`, and
+leading or trailing `-` removed. When it is longer than 80 characters, cut it at 80, then back to the last
+`-`.
+
+The frontmatter needs every field below. Scalar values are double-quoted JSON strings;
+arrays use the flow form shown in the example:
+
+- `id`: the claimed ID.
+- `title`: one line.
+- `priority`: `critical`, `high`, `medium` or `low`.
+- `tags`: a list of quoted strings, `[]` when there are none.
+- `status`: `"open"`.
+- `created` and `updated`: today's date as `YYYY-MM-DD`.
+- `when`: `next-unit:<ref>`, `sprint:<SPRINT-NNN or next>`, `trigger:<event>`, or
+  `declined:<reason>`. Use a PR number, task ID, backlog ID, or branch for `<ref>`.
+  Never store `now`; it is a triage outcome. Trigger forms include
+  `date:YYYY-MM-DD`, `closed:<BL-NNN>`, `merged:#<PR>`, `merged:<branch>`, and
+  `release:<pkg>@<semver>`; other non-empty event text is allowed.
+- `files`: a list of quoted repo-relative paths, such as `["src/routes/import.ts"]`.
+  Omit line numbers, absolute paths and `..` segments. Use distinct paths from
+  the evidence, or `[]` when there are none.
+
+Older items may omit `when` and `files`. When listing them, derive files from
+body evidence such as `src/routes/import.ts:41` only if `files` is absent.
+
+The body is `# <ID>: <title>`, then `## Tags` with one `- <tag>` line per tag
+(omitted when there are none), then the description. A description that starts
+with its own `##` sections stands as written; otherwise it goes under
+`## Description`. End with a `---` line and the close line.
+
+```markdown
+---
+id: "BL-007"
+title: "Import endpoint has no rate limit"
+priority: "medium"
+tags: ["security", "api"]
+status: "open"
+created: "2026-11-08"
+updated: "2026-11-08"
+when: "next-unit:#612"
+files: ["src/routes/import.ts"]
+---
+
+# BL-007: Import endpoint has no rate limit
+
+## Tags
+
+- security
+- api
+
+## Problem
+
+`/import` accepts unlimited requests (`src/routes/import.ts:41`).
+
+---
+_Close when done: `openplanr backlog update BL-007 --status closed`_
+```
+
+Report the ID and the repo-relative path of each filed item.

package/lib/host-packages/claude/openplanr/skills/investigate/references/findings.md

@@ -31,9 +31,8 @@ Merge duplicates within the run. Sort by severity, highest first, and number fro
 
 ## Check what is already tracked
 
-Before showing findings, list open backlog items with the backlog helper
-linked from SKILL.md, resolved relative to that file: `node <helper> list
---project <repository-root> --open`. A finding about the same problem as an open item,
+Before showing findings, list open backlog items as
+[backlog filing](backlog-filing.md) describes. A finding about the same problem as an open item,
 normally the same evidence file and an equivalent title, is `tracked`. Never file
 it again and never edit the existing item.
 
@@ -52,26 +51,19 @@ rule that applies. File only what it allows.
    example a print or exec mode), another skill or a delegate runner started this
    run, or the user said not to ask. Read `findings.unattended` in
    `.planr/config.json`. Only `file` files every untracked finding. With
-   `report`, or no setting, do not run `add` at all: mark the findings `reported`.
+   `report`, or no setting, do not file at all: mark the findings `reported`.
 
 Never ask per finding, never ask mid-run, and never file or drop a finding
 silently.
 
 ## File
 
-Send each item as one JSON object (`title`, `priority`, `tags`, `description`)
-on stdin. Never pass `acceptanceCriteria`.
+File each item from its `title`, `priority`, `tags` and `description` as
+[backlog filing](backlog-filing.md) describes. Never add acceptance criteria.
+When the `openplanr` command files it and the result says
+`templateOverrideIgnored`, say the default format was used.
 
-- When an `openplanr` CLI resolves (the project's `node_modules/.bin`, then
-  `PATH`; never `npx`): `openplanr --project-dir <repository-root> backlog add
-  --data - --json`.
-- Otherwise: `node <helper> add --project <repository-root> --data -`. Its
-  result can carry `cliHint`; end the result with that line, word for word,
-  once. Install only if the user says yes then, by running exactly the command in
-  the line. If the result says `templateOverrideIgnored`, say the default format
-  was used.
-
-If filing fails, report the command and its error, and leave the finding
+If filing fails, report the step and its error, and leave the finding
 `reported`.
 
 ## Report

package/lib/host-packages/claude/openplanr/skills/operate/SKILL.md

@@ -6,9 +6,7 @@ license: MIT
 
 # OpenPlanr Operate
 
-Run one useful operating review, not a ceremony. Build shared context once, fan out the five
-executive advisors, use the Challenger to test material claims, and let the Chair synthesize the
-result. Return a clean board report with decisions, actions, risks, gaps, and any real issues.
+Run one useful operating review, not a ceremony. By default one agent applies all seven lenses in one pass and writes one report with decisions, actions, risks, gaps, and any real issues.
 
 ## Scope the review
 
@@ -20,58 +18,69 @@ Infer these values from the request and repository when they are clear:
 - **Roster** — all seven lenses unless the user selects fewer.
 
 Use the current repository, current snapshot, periodic review, and all seven lenses as sensible
-defaults. When ownership is useful, a recommendation may suggest a person, a role, or
-`unassigned`.
+defaults. A recommendation may suggest a person, a role, or `unassigned`.
 
 Ask only when an unresolved choice would materially change the sources inspected or the decision
 being answered. Use the host's native structured-question UI when available, offering a
 recommended choice and short alternatives. Otherwise ask one concise chat question at a time.
 Never present the scope fields as a prose questionnaire.
 
-Preserve the user's wording in `cycle.md`, followed by the effective scope used by the lenses.
-Do not claim a trend from a current snapshot; describe current state and name any missing baseline.
+Record the user's wording and the effective scope in the report's Scope section. Do not claim a
+trend from a current snapshot; describe current state and name any missing baseline.
 
-## Create the cycle workspace
+## Choose the mode
 
-Use a short subject slug and today's ISO date. Choose the first unused path;
-when the base path exists, append `-02`, `-03`, and so on. Reuse an existing
-cycle only when the user explicitly asks to resume it and its recorded scope
-matches. Never overwrite a prior cycle implicitly.
+Default: this agent applies the lenses itself. Use subagents only when the user names a roster or
+asks for independent reviewers; then follow Fan out.
 
-```text
-.planr/operate/<date>-<slug>/
-  cycle.md
-  brief.md
-  <selected-lens-notes>.md
-  board-report.md
-```
+Where the report goes: with no `.planr/` in the repository, answer in chat, or write one file where
+the repository already keeps such documents. With `.planr/`, write `board-report.md` in a cycle
+directory (below). `cycle.md`, `brief.md` and per-lens notes only when subagents run or the user asks to persist the cycle; a persisted cycle without fan-out writes `cycle.md` and `brief.md` with the contents defined under Fan out.
+
+## Read the sources
+
+Read the files the request names, plus `AGENTS.md` and `CLAUDE.md` when tracked, in one batch.
+Expand only for a missing contract, a dependency or a contradiction, and stop when each claim has
+evidence or a named gap. Keep observations separate from interpretation.
+
+## Apply the lenses
+
+Work through each selected lens in one pass:
 
-`cycle.md` records the effective scope, roster, repository revision when relevant, and the outcome
-of each lens. An advisor lens run on its own creates the same layout with a one-lens roster and an
-unsynthesized `board-report.md`, so every review the dashboard lists has one shape.
-If the directory is ignored by Git, continue locally and mention that in the report; do not ask the
-user to change ignore rules. Report an exact filesystem error only when the cycle workspace cannot be
-created or written.
+| Lens | Focus |
+|---|---|
+| CEO | strategy and finance: direction, runway, margin, cost of delay |
+| CTO | technology and delivery risk: architecture, reliability, security, execution risk |
+| CPO | product and activation: customer value, activation, prioritization, adoption |
+| CMO | growth and market: acquisition, positioning, demand, retention, measurement |
+| COO | operations and customer health: process, support, incidents, capacity |
+| Challenger | for each material claim: the strongest alternative, the downside, and the confidence |
+| Chair | the decision queue and action plan, from the findings above |
 
-## Build shared context once
+Name each Review coverage row `CEO`, `CTO`, `CPO`, `CMO`, `COO`, `Challenger` or `Chair`; the dashboard matches on those names.
 
-Write `brief.md` as a compact orientation aid, not a conclusion. Include:
+Every recommendation cites a source: a project path, command output, or a named gap. Do not
+fabricate a lens with no evidence; record it as `no material finding` or `unavailable` in review
+coverage with the smallest next action. Then assemble the report below.
 
-- effective subject, window, requested decision, and roster;
-- current revision and working-tree state when relevant;
-- the requested range and a short change summary when the review is historical;
-- paths to relevant planning, product, customer, financial, operational, delivery, architecture,
-  incident, and metric sources;
-- important context that was searched for but not found.
+## Cycle directory
 
-Open enough of the repository to make these pointers useful. Keep observations separate from
-interpretation so every lens can reach its own conclusion. The brief is a starting point; lenses
-may inspect other relevant project sources.
+Use a short subject slug and today's ISO date: `.planr/operate/<date>-<slug>/`. Choose the first
+unused path; when the base path exists, append `-02`, `-03`, and so on. Reuse an existing cycle
+only when the user explicitly asks to resume it and its recorded scope matches. Never overwrite a
+prior cycle implicitly. If the directory is ignored by Git, continue locally and mention that in the
+report; do not ask the user to change ignore rules. Report an exact filesystem error only when the
+directory cannot be created or written.
 
-## Run the selected lenses (seven by default)
+## Fan out
+
+When the user names a roster or asks for independent reviewers, create the cycle directory with
+`cycle.md` (effective scope, roster, revision when relevant, outcome of each lens) and `brief.md`
+(scope, revision, source paths, context searched for but not found), then one note per selected lens. An advisor lens run on its own creates the same layout with a one-lens
+roster and an unsynthesized `board-report.md`.
 
 Dispatch only the selected independent advisors, in parallel when subagents are
-available:
+available, giving each the brief path, its output path and the effective scope:
 
 | Lens | Skill | Output |
 |---|---|---|
@@ -81,21 +90,17 @@ available:
 | Growth and market | `planr-cmo-review` | `cmo.md` |
 | Operations and customer health | `planr-coo-review` | `coo.md` |
 
-Give each selected advisor the brief path, its output path, and the effective
-scope. Do not invoke or create note files for advisor lenses omitted by the
-roster. After the selected advisor work finishes:
+Do not create note files for omitted lenses. After the advisor work finishes:
 
-1. If Challenger is selected, run `planr-challenger-review` over the available
-   advisor notes to surface only material exceptions, alternatives, and downside.
-2. If Chair is selected, run `planr-chair-review` over the available selected
-   notes to produce the decision queue and action plan.
-3. If Challenger or Chair is omitted, record `omitted by scope` in review
-   coverage. Assemble the board report from the available selected notes without
-   inventing the omitted lens; when Chair is absent, clearly label the result as
-   an unsynthesized lens summary rather than a Chair recommendation.
+1. If Challenger is selected, run `planr-challenger-review` over the available advisor notes to
+   surface only material exceptions, alternatives, and downside.
+2. If Chair is selected, run `planr-chair-review` over the available notes to produce the decision
+   queue and action plan.
+3. If Challenger or Chair is omitted, record `omitted by scope` in review coverage and label the
+   result an unsynthesized lens summary, not a Chair recommendation.
 
-Missing or malformed lens output is an issue, not a reason to fabricate that lens or discard all
-other useful work. Record the problem, its effect on confidence, and the smallest next action.
+Missing or malformed lens output is an issue, not a reason to fabricate that lens or discard the
+other work. Record the problem, its effect on confidence, and the smallest next action.
 
 ## Assemble `board-report.md`
 
@@ -144,47 +149,31 @@ Use these sections in this order:
 ## Review coverage
 | Lens | Outcome | Note | Informed |
 |---|---|---|---|
-| ... | reported / no material finding / unavailable / omitted by scope | `file.md` or `—` | D1 / watch / none |
+| CEO | reported / no material finding / unavailable / omitted by scope | `file.md` or `—` | D1 / watch / none |
 
 ## Issues
 - **I1 — <problem>:** <impact and practical next action>
 <or `None.`>
 ```
 
-When Chair is selected, copy decisions and actions from `chair.md`; do not create a new executive
-opinion during assembly. When Chair is omitted, summarize only the available selected notes,
-label the report as an unsynthesized lens summary, and use `No decision-ready proposal was
-established.` plus `No proposed actions.` unless those notes already state a directly supported
-proposal. Never present that result as Chair synthesis. Keep at most five decisions, seven actions,
-and five decision-changing gaps. When no decision is ready, say so plainly and retain the strongest
-watch items and the context needed to improve the next review.
-
-## Optional quality check
+In fan out with Chair, copy decisions and actions from `chair.md` without adding a new executive
+opinion. Without Chair, summarize only the available notes, label the report an unsynthesized lens
+summary, and use `No decision-ready proposal was established.` plus `No proposed actions.` unless
+those notes already state a supported proposal. Keep at most five decisions, seven actions, and five
+decision-changing gaps. When no decision is ready, say so and keep the strongest watch items.
 
-The packaged [note validator](scripts/validate-note.mjs) can identify missing sections, fields, or limits:
+## Quality check
 
-```sh
-node "<skill-root>/scripts/validate-note.mjs" "<absolute-advisor-output>" --profile advisor --contract-version 2.0.0
-node "<skill-root>/scripts/validate-note.mjs" "<absolute-challenger-output>" --profile challenger --contract-version 2.0.0
-node "<skill-root>/scripts/validate-note.mjs" "<absolute-chair-output>" --profile chair --contract-version 2.0.0
-node "<skill-root>/scripts/validate-note.mjs" "<absolute-board-report-path>" --profile board-report --contract-version 2.0.0
-```
-
-Use their diagnostics as editing help. Include unresolved structural problems under `Issues` with
-their impact and next action while preserving the useful parts of the report.
+Before returning, check the report (and any lens note) against [the note checklist](references/note-checklist.md), which runs the CLI's `validate-note` when `command -v openplanr` succeeds and is the check otherwise. Put unresolved structural problems under `Issues` with their impact and next action.
 
 ## Return
 
-Lead with the grounded overall signal and most consequential decision or missing
-evidence. Link `board-report.md`, summarize decision/action counts and the review
-coverage actually completed, and name any unavailable or unsynthesized lens.
-Keep the full decision queue, source inventories and diagnostic output in their
-existing artifacts. Include unresolved issues with their impact and next action,
-omitting empty chat sections. Preserve the durable report contract; different
-summary wording never requires another review or corrective run.
-
-When the OpenPlanr dashboard is running, the operating cycle is browsable at
-`#/operate/cycles/<id>`, the completed review index at `#/operate/cycles`, and the latest
-completed review at `#/operate/today`. The standalone dashboard presents these local reports
-read-only and refreshes them automatically. Inbox, actions, evidence, outcomes, recovery, and
-all mutations require an actor-bound governed Operate session.
+Lead with the grounded overall signal and most consequential decision or missing evidence.
+Link `board-report.md` when one was written, summarize decision and action counts and the review
+coverage completed, and name any unavailable or unsynthesized lens. Follow
+[the shared return rules](references/return-contract.md).
+
+When the OpenPlanr dashboard is running, the cycle is browsable at `#/operate/cycles/<id>`, the
+review index at `#/operate/cycles`, and the latest review at `#/operate/today`, read-only.
+Inbox, actions, evidence, outcomes, recovery, and all mutations require an actor-bound governed
+Operate session.