openplanr 2.0.0 → 2.1.0

package/dist/templates/rules/shared/capability-map.md.hbs

@@ -0,0 +1,23 @@
+## OpenPlanr capabilities
+
+Every skill below is model-invoked: reach for it as soon as a request matches,
+without waiting to be asked by name. When no single skill clearly fits, start
+with `{{prefix}}openplanr`, which routes to the best one. PLAN and SHIP stay
+separate user-invoked workflows.
+{{#each families}}
+
+### {{{this.title}}}
+
+{{#each this.skills}}
+- `{{@root.prefix}}{{this.name}}` — {{{this.lead}}} Use when: {{{this.useWhen}}}.{{#if this.notFor}} Not for: {{{this.notFor}}}.{{/if}}
+{{/each}}
+{{/each}}
+{{#if agents}}
+
+### Delegated agents
+
+The Ship workflow dispatches these subagents itself; do not start them by hand.
+{{#each agents}}
+- `{{this.id}}` — {{{this.summary}}}
+{{/each}}
+{{/if}}

package/docs/CLI.md

@@ -59,9 +59,21 @@ These options apply to **all** commands:
 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 --json
+planr company login
+```
+
+The normal customer flow needs no service URL or output flag. For a remote or
+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 --json
+planr company login --no-open --timeout 300
+```
+
+Structured output is available for automation:
+
+```bash
+planr company login --json
 planr company logout --json
 ```
 
@@ -541,7 +553,9 @@ 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
-incompatible installed CLI.
+incompatible installed CLI. 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`
 
@@ -634,6 +648,12 @@ planr sync                          # fix broken cross-references
 planr sync --dry-run                # preview changes without writing
 ```
 
+With the pipeline scope, `CLAUDE.md` and `AGENTS.md` also receive a generated
+`## OpenPlanr capabilities` section listing every skill (with its triggers) and,
+for Claude Code, the delegated agents, read from the shipped capability map.
+Start with `/planr:openplanr` (`$planr:openplanr` in Codex) when the right
+skill is unclear.
+
 | Option      | Description                                  | Default |
 | ----------- | -------------------------------------------- | ------- |
 | `--dry-run` | Show what would change without writing files | `false` |

package/lib/host-packages/adapter-registry.json

@@ -2,7 +2,7 @@
   "kind": "host-native-adapter-registry",
   "schemaVersion": "1.0.0",
   "protocolVersion": "1.8.0",
-  "pipelineVersion": "0.45.0",
+  "pipelineVersion": "0.45.1",
   "pluginVersion": "0.1.0",
   "adapters": [
     {

package/lib/host-packages/capability-map.json

@@ -0,0 +1,494 @@
+{
+  "kind": "openplanr-capability-map",
+  "schemaVersion": "1.0.0",
+  "pluginVersion": "0.1.0",
+  "families": [
+    {
+      "id": "planning",
+      "title": "Plan and specify"
+    },
+    {
+      "id": "implementation",
+      "title": "Implement"
+    },
+    {
+      "id": "quality",
+      "title": "Review and QA"
+    },
+    {
+      "id": "design",
+      "title": "Design"
+    },
+    {
+      "id": "diagram",
+      "title": "Diagrams"
+    },
+    {
+      "id": "artifact",
+      "title": "Artifact reviews"
+    },
+    {
+      "id": "release",
+      "title": "Land and release"
+    },
+    {
+      "id": "diagnostics",
+      "title": "Setup and diagnostics"
+    },
+    {
+      "id": "planning-tools",
+      "title": "Status, routing and sync"
+    },
+    {
+      "id": "operate",
+      "title": "Operate"
+    },
+    {
+      "id": "operate-advisor",
+      "title": "Operate advisors"
+    },
+    {
+      "id": "operate-synthesis",
+      "title": "Operate synthesis"
+    }
+  ],
+  "skills": [
+    {
+      "id": "planr-artifact",
+      "name": "artifact",
+      "family": "artifact",
+      "description": "Open, share, import, or export an OpenPlanr HTML artifact review. Use when feedback must move between a local artifact and its review board.",
+      "useWhen": [
+        "Open or share an HTML artifact review",
+        "Import artifact feedback and export the reviewed artifact"
+      ],
+      "notFor": [
+        "Review source code changes",
+        "Create a product interface design"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-browser-qa",
+      "name": "browser-qa",
+      "family": "quality",
+      "description": "Run practical browser-backed QA against real routes, forms, viewports, accessibility, console, and network behavior. Use for UI, authentication, session, navigation, or browser-network changes.",
+      "useWhen": [
+        "Test this page or application in a real browser",
+        "Check routes, forms, mobile viewports, accessibility, console, and network behavior"
+      ],
+      "notFor": [
+        "Run backend unit tests only",
+        "Review a plan without exercising a browser"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-ceo-review",
+      "name": "ceo-review",
+      "family": "operate-advisor",
+      "description": "Produce a grounded strategy and finance review for an Operate cycle. Use when direction, runway, margin, investment, or cost of delay needs a CEO lens.",
+      "useWhen": [
+        "Run a CEO strategy and finance review",
+        "Assess direction, runway, margin, investment, or cost of delay"
+      ],
+      "notFor": [
+        "Review implementation details",
+        "Assess only product usability"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-chair-review",
+      "name": "chair-review",
+      "family": "operate-synthesis",
+      "description": "Synthesize an Operate cycle into a prioritized decision queue and action plan. Use after specialist reviews when leadership needs one coherent brief.",
+      "useWhen": [
+        "Synthesize executive reviews into a decision queue",
+        "Turn operating-review findings into prioritized decisions and actions"
+      ],
+      "notFor": [
+        "Produce an independent specialist review",
+        "Implement the recommended actions"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-challenger-review",
+      "name": "challenger-review",
+      "family": "operate-synthesis",
+      "description": "Challenge an Operate cycle's claims, alternatives, downside, and confidence. Use when assumptions or executive consensus need an independent stress test.",
+      "useWhen": [
+        "Challenge operating-review assumptions and downside",
+        "Test material claims, alternatives, confidence, and dissent"
+      ],
+      "notFor": [
+        "Summarize reviews without challenging them",
+        "Implement a proposed decision"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-cmo-review",
+      "name": "cmo-review",
+      "family": "operate-advisor",
+      "description": "Produce a grounded market and growth review for an Operate cycle. Use when acquisition, positioning, demand, retention, or missing measurement needs a CMO lens.",
+      "useWhen": [
+        "Run a market and growth review",
+        "Assess acquisition, positioning, demand, channels, or growth measurement"
+      ],
+      "notFor": [
+        "Review backend architecture",
+        "Assess internal delivery mechanics only"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-coo-review",
+      "name": "coo-review",
+      "family": "operate-advisor",
+      "description": "Produce a grounded operations and customer-health review for an Operate cycle. Use when readiness, service delivery, capacity, or customer health needs a COO lens.",
+      "useWhen": [
+        "Run an operations and customer-health review",
+        "Assess readiness, support, reliability, process, or customer operations"
+      ],
+      "notFor": [
+        "Review company strategy only",
+        "Design a product interface"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-cpo-review",
+      "name": "cpo-review",
+      "family": "operate-advisor",
+      "description": "Produce a grounded product and activation review for an Operate cycle. Use when customer value, activation, prioritization, or adoption needs a CPO lens.",
+      "useWhen": [
+        "Run a product and activation review",
+        "Assess customer value, adoption, activation, retention, or product outcomes"
+      ],
+      "notFor": [
+        "Review infrastructure only",
+        "Assess financial runway only"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-cto-review",
+      "name": "cto-review",
+      "family": "operate-advisor",
+      "description": "Produce a grounded technology and delivery-risk review for an Operate cycle. Use when architecture, reliability, security, or execution risk needs a CTO lens.",
+      "useWhen": [
+        "Run a technology and delivery-risk review",
+        "Assess architecture, security, reliability, technical debt, or delivery risk"
+      ],
+      "notFor": [
+        "Review marketing channels",
+        "Assess financial runway only"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-dashboard",
+      "name": "dashboard",
+      "family": "planning-tools",
+      "description": "Start or inspect the loopback-only OpenPlanr planning dashboard. Use when the user wants to view local planning or Operate state in the browser.",
+      "useWhen": [
+        "Open or inspect the local OpenPlanr dashboard",
+        "Show planning and Operate workspaces visually"
+      ],
+      "notFor": [
+        "Return a short text delivery status",
+        "Create a product dashboard design"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-design",
+      "name": "design",
+      "family": "design",
+      "description": "Design a polished product interface through adaptive consultation, a shared canvas/prototype/walkthrough studio, and an implementation-ready specification. Use for a new design or an existing interface that needs a coherent direction.",
+      "useWhen": [
+        "Create an initial product design direction",
+        "Start the OpenPlanr design workflow for a feature"
+      ],
+      "notFor": [
+        "Review an existing completed design",
+        "Explore several competing design variants"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-design-loop",
+      "name": "design-loop",
+      "family": "design",
+      "description": "Compare three materially different product design directions in a live review studio, collect pins and ratings, and develop the selected direction. Use for visual alternatives, comparison or a remix.",
+      "useWhen": [
+        "Explore multiple design directions or variants",
+        "Iterate a design using pinned board feedback"
+      ],
+      "notFor": [
+        "Create only one initial design",
+        "Review an existing design without generating variants"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-design-review",
+      "name": "design-review",
+      "family": "design",
+      "description": "Review and revise an existing product design using stable board pins and scoped browser-verified changes. Use for focused improvements while preserving unrelated screens and feedback.",
+      "useWhen": [
+        "Review or critique an existing OpenPlanr design",
+        "Apply pinned feedback to affected design regions"
+      ],
+      "notFor": [
+        "Create an initial design from scratch",
+        "Implement backend code"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-diagram",
+      "name": "diagram",
+      "family": "diagram",
+      "description": "Create, inspect, verify, or rerender professional offline diagrams. Use for architecture, process, sequence, data, state, or relationship visuals from intent or source.",
+      "useWhen": [
+        "Create a professional diagram from English intent or Mermaid",
+        "Inspect, verify, preview, or rerender an OpenPlanr diagram set"
+      ],
+      "notFor": [
+        "Create a product interface design",
+        "Open a generic artifact that is not a diagram"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-doctor",
+      "name": "doctor",
+      "family": "diagnostics",
+      "description": "Diagnose OpenPlanr CLI, pipeline, runtime-adapter, installation, and lock health. Use when setup, discovery, versions, generated assets, or runtime behavior seems wrong.",
+      "useWhen": [
+        "Diagnose OpenPlanr installation, runtime, adapter, version, or lock health",
+        "Check why planr setup or upgrade is unhealthy"
+      ],
+      "notFor": [
+        "Diagnose an application bug",
+        "Implement a feature"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-investigate",
+      "name": "investigate",
+      "family": "diagnostics",
+      "description": "Diagnose a bug, regression, error, or unexplained behavior and optionally implement a bounded fix. Use for root-cause investigation, not planned feature delivery.",
+      "useWhen": [
+        "Investigate a bug, regression, error, or unexplained behavior",
+        "Reproduce a defect, establish its root cause, or apply a bounded fix",
+        "Investigate why this fails"
+      ],
+      "notFor": [
+        "Plan a new feature",
+        "Run a broad product review"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-land",
+      "name": "land",
+      "family": "release",
+      "description": "Assess release readiness and prepare or inspect an OpenPlanr landing sequence. Use after implementation and checks are complete, before merge, publication, or deployment.",
+      "useWhen": [
+        "Prepare or inspect a landing and release plan",
+        "Check whether reviewed work is ready to land without deploying it"
+      ],
+      "notFor": [
+        "Build a new application feature",
+        "Deploy or publish immediately"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-openplanr",
+      "name": "openplanr",
+      "family": "planning-tools",
+      "description": "Route a planning, specification, delivery, design, review, diagram, release, or operating request to the best OpenPlanr skill. Use when the right skill is unclear or the request spans several.",
+      "useWhen": [
+        "Choose which OpenPlanr skill should handle a request",
+        "Route a mixed or unclear planning, delivery, design, or operating request"
+      ],
+      "notFor": [
+        "Perform the routed work itself",
+        "Answer a question unrelated to OpenPlanr workflows"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-operate",
+      "name": "operate",
+      "family": "operate",
+      "description": "Run a focused operating review across seven executive lenses and produce a decision and action brief. Use for periodic product or company-level leadership review.",
+      "useWhen": [
+        "Run an executive operating review across product, technology, growth, operations, and strategy",
+        "Produce a decision and action brief for the product or company"
+      ],
+      "notFor": [
+        "Review only a code diff",
+        "Implement the resulting actions"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-plan",
+      "name": "plan",
+      "family": "planning",
+      "description": "Turn a Protocol-compatible specification or product intent into schema-compatible OpenPlanr stories and implementation tasks. Use for planning and decomposition, not implementation.",
+      "useWhen": [
+        "Decompose a specification into user stories and implementation tasks",
+        "Create an implementation plan from product intent"
+      ],
+      "notFor": [
+        "Implement the plan",
+        "Review an already written plan"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-plan-review",
+      "name": "plan-review",
+      "family": "planning",
+      "description": "Review an OpenPlanr plan for product, engineering, design, and developer-experience problems. Use after planning and before implementation to improve the plan.",
+      "useWhen": [
+        "Review an implementation plan for product, engineering, design, and developer-experience problems",
+        "Challenge a plan before implementation"
+      ],
+      "notFor": [
+        "Implement the plan",
+        "Write a new specification from vague intent"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-release",
+      "name": "release",
+      "family": "release",
+      "description": "Choose and maintain a product's versioning scheme, classify shipped changes, and write user-facing changelogs or release notes. Use for SemVer or CalVer decisions, version bumps, release cadence, and preparing a versioned release after landing.",
+      "useWhen": [
+        "Choose the next SemVer or CalVer version and write user-facing release notes",
+        "Set up or maintain a changelog, versioning scheme, and release cadence"
+      ],
+      "notFor": [
+        "Check whether unmerged work is ready to land without choosing a version",
+        "Implement product code before release preparation"
+      ],
+      "deferTo": [
+        "planr-land",
+        "planr-ship"
+      ]
+    },
+    {
+      "id": "planr-ship",
+      "name": "ship",
+      "family": "implementation",
+      "description": "Implement an OpenPlanr plan, specification, task, or clearly stated request end to end in the current repository. Use when the user asks to build, implement, fix, finish, or ship local work.",
+      "useWhen": [
+        "Implement a plan, specification, task, fix, or clearly stated local request",
+        "Build and verify the requested repository change",
+        "Ship this",
+        "Ship task",
+        "Implement this task"
+      ],
+      "notFor": [
+        "Only plan the work",
+        "Prepare a release without changing code"
+      ],
+      "deferTo": [
+        "planr-land"
+      ]
+    },
+    {
+      "id": "planr-spec",
+      "name": "spec",
+      "family": "planning",
+      "description": "Shape vague product or engineering intent into a clear, measurable Protocol-compatible specification grounded in the current repository. Use when requirements need clarification before planning or implementation.",
+      "useWhen": [
+        "Turn vague product or engineering intent into a precise specification",
+        "Clarify requirements and acceptance criteria before planning"
+      ],
+      "notFor": [
+        "Implement an existing specification",
+        "Return project status"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-status",
+      "name": "status",
+      "family": "planning-tools",
+      "description": "Inspect project delivery or one feature's pipeline status without changing state. Use when the user asks what is done, pending, blocked, or next.",
+      "useWhen": [
+        "Report current OpenPlanr delivery status or outstanding work",
+        "Show progress for one feature or the whole project"
+      ],
+      "notFor": [
+        "Open the visual dashboard",
+        "Modify planning state"
+      ],
+      "deferTo": []
+    },
+    {
+      "id": "planr-sync",
+      "name": "sync",
+      "family": "planning-tools",
+      "description": "Audit OpenPlanr planning artifacts for graph and protocol drift. Use when statuses, references, schemas, or generated planning views may be inconsistent.",
+      "useWhen": [
+        "Audit planning artifacts for graph, schema, or protocol drift",
+        "Check whether stories, tasks, and generated planning state are synchronized"
+      ],
+      "notFor": [
+        "Synchronize external cloud data",
+        "Implement feature code"
+      ],
+      "deferTo": []
+    }
+  ],
+  "agents": [
+    {
+      "id": "planr-backend",
+      "description": "Use this agent when implementing a Tech task from the task file (Type=Tech — task-2.md, or sole task-1.md when no PNG). Services, controllers, DTOs, DB queries — backend only; never touches UI. For Step 0.2 entity scaffolding from schema.json use entity-scaffold-agent instead."
+    },
+    {
+      "id": "planr-database",
+      "description": "Use this agent when scanning a live database schema. READ-ONLY introspection that produces output/db/schema.json from PostgreSQL, MySQL, MSSQL, SQLite, or MongoDB."
+    },
+    {
+      "id": "planr-designer",
+      "description": "Use this agent when PNG mockups for a feature need to be analyzed into a structured design specification. Vision-based extraction of colors, typography, components, and layout into a 10-section design-spec.md."
+    },
+    {
+      "id": "planr-devops",
+      "description": "Use this agent when generating infrastructure config (docker-compose.yml, Dockerfiles, .env.example, CI workflow stubs) from the projects stack. Generates files only — never deploys, never pushes images, never calls cloud APIs."
+    },
+    {
+      "id": "planr-documentation",
+      "description": "Use this agent when creating or updating human-readable product and engineering documentation from the request, repository, planning context, and implemented behavior. Cross-references intent and code, flags material drift, and never generates application code."
+    },
+    {
+      "id": "planr-entity-scaffold",
+      "description": "Step 0.2 only — generate ORM entity / DbContext (or equivalent) scaffolding from output/db/schema.json into output/src/. Not for `/ship` Tech tasks; use backend-agent for those."
+    },
+    {
+      "id": "planr-frontend",
+      "description": "Use this agent when implementing a UI task (Type=UI, task-1.md). Generates production-grade React/Next.js/Vue components, pages, and styles in src/features/{name}/. Frontend code only — never touches services, controllers, DTOs, or DB."
+    },
+    {
+      "id": "planr-qa",
+      "description": "Review a scoped implementation without editing it and return concise, evidence-based, actionable findings focused on acceptance, security, and correctness."
+    },
+    {
+      "id": "planr-specification",
+      "description": "Decompose a functional specification into schema-compatible User Stories and tasks after loading the active stack, design, database, and repository context. Writes planning artifacts only."
+    }
+  ]
+}

package/lib/host-packages/claude/openplanr/.openplanr-content.json

@@ -3,7 +3,7 @@
   "schemaVersion": "1.0.0",
   "protocolVersion": "1.8.0",
   "host": "claude-code",
-  "skillCount": 25,
+  "skillCount": 26,
   "roleCount": 9,
   "files": [
     {
@@ -156,7 +156,7 @@
     },
     {
       "path": "skills/artifact/references/company-review.md",
-      "digest": "sha256:168066d3539dab064adeaaf0e4187df8b779d53476be17283b4a62d4bb136257"
+      "digest": "sha256:b31bb74501fd24ae388294a4ccf2b9161b128f0288b2fb03c99a762595e0eaba"
     },
     {
       "path": "skills/artifact/references/design-sharing.md",
@@ -464,7 +464,7 @@
     },
     {
       "path": "skills/design-loop/scripts/runtime/packages/protocol/package.json",
-      "digest": "sha256:b4b9cdd63c56723fa0c64cae1ce50776bf1f221d56e345672803974e70781567"
+      "digest": "sha256:9a11f3b5e52bb2bd3f2310a9cbc1276b62b1b08e401279769228d5bfd8567995"
     },
     {
       "path": "skills/design-loop/scripts/runtime/packages/protocol/registry/artifact-theme.json",
@@ -632,7 +632,7 @@
     },
     {
       "path": "skills/design-review/scripts/runtime/packages/protocol/package.json",
-      "digest": "sha256:b4b9cdd63c56723fa0c64cae1ce50776bf1f221d56e345672803974e70781567"
+      "digest": "sha256:9a11f3b5e52bb2bd3f2310a9cbc1276b62b1b08e401279769228d5bfd8567995"
     },
     {
       "path": "skills/design-review/scripts/runtime/packages/protocol/registry/artifact-theme.json",
@@ -800,7 +800,7 @@
     },
     {
       "path": "skills/design/scripts/runtime/packages/protocol/package.json",
-      "digest": "sha256:b4b9cdd63c56723fa0c64cae1ce50776bf1f221d56e345672803974e70781567"
+      "digest": "sha256:9a11f3b5e52bb2bd3f2310a9cbc1276b62b1b08e401279769228d5bfd8567995"
     },
     {
       "path": "skills/design/scripts/runtime/packages/protocol/registry/artifact-theme.json",
@@ -922,6 +922,14 @@
       "path": "skills/land/SKILL.md",
       "digest": "sha256:04d2deb6b7d4c161f94580f7b6481c51ca60b55afe6f5d510fd640d57f569c2d"
     },
+    {
+      "path": "skills/openplanr/openplanr.skill.json",
+      "digest": "sha256:f14e20b843f7f51688ded299fbeb773eab1d244429e7baaaff5a14713bde72be"
+    },
+    {
+      "path": "skills/openplanr/SKILL.md",
+      "digest": "sha256:0796e0cce4d8fdf6f5b8cca86ef7c96fd02150493b609d08e74bb78045fcb2dd"
+    },
     {
       "path": "skills/operate/openplanr.skill.json",
       "digest": "sha256:daa8c7683675c88996da7803dee168d9e880aad880870d650e34035cd89f1dd7"
@@ -1020,7 +1028,7 @@
     },
     {
       "path": "skills/plan/scripts/runtime/packages/protocol/package.json",
-      "digest": "sha256:b4b9cdd63c56723fa0c64cae1ce50776bf1f221d56e345672803974e70781567"
+      "digest": "sha256:9a11f3b5e52bb2bd3f2310a9cbc1276b62b1b08e401279769228d5bfd8567995"
     },
     {
       "path": "skills/plan/scripts/runtime/packages/protocol/registry/artifact-theme.json",
@@ -1175,5 +1183,5 @@
       "digest": "sha256:53698324b62f43b672ce8fe1654c526c96fb202e313442f09c6fc1e72268677e"
     }
   ],
-  "contentDigest": "sha256:90664ea5cd984084c6b5e9ffdff5dcd6a1c3e7243eb87aa8ef82f0ad4100766f"
+  "contentDigest": "sha256:558c63f719ffa2fda80259fca6f072a0f51afab5e9b4a2c1dd931374bfe3ae61"
 }

package/lib/host-packages/claude/openplanr/skills/artifact/references/company-review.md

@@ -3,7 +3,7 @@
 Use this route only for an explicitly configured company workspace. Existing `planr artifact share/publish/sync` token shares keep their separate encryption and authorization model. Never silently import a token share into company storage.
 
 1. Read `planr company --help`. If this command is absent, report the actual installed CLI path/version and required local build; do not search the disk for runtime internals or silently install a public release.
-2. Start browser sign-in with `planr company login --json`; use `--no-open` to display its authorization URL and open it on the same computer. The hosted CLI uses `https://api.openplanr.dev` by default; `--api-url <origin>` is an advanced development, staging, or self-hosted override. The company service must advertise a configured public OAuth client. Choose the organization in the issuer's consent screen. The CLI stores renewable credentials in the OS keychain, or discloses its existing encrypted local-file fallback. Never print tokens, place them in arguments/URLs, or ask for them in chat. Tokens renew automatically; revoked access still fails closed. `company connect --token-stdin` and `PLANR_COMPANY_TOKEN` remain explicit developer fallbacks without automatic renewal.
+2. Start browser sign-in with `planr company login`; use `--no-open` to display its authorization URL and open it on the same computer. Add `--json` only when an automated caller needs the structured completion receipt. The hosted CLI uses `https://api.openplanr.dev` by default; `--api-url <origin>` is an advanced development, staging, or self-hosted override. The company service must advertise a configured public OAuth client. Choose the organization in the issuer's consent screen. The CLI stores renewable credentials in the OS keychain, or discloses its existing encrypted local-file fallback. Never print tokens, place them in arguments/URLs, or ask for them in chat. Tokens renew automatically; revoked access still fails closed. `company connect --token-stdin` and `PLANR_COMPANY_TOKEN` remain explicit developer fallbacks without automatic renewal.
 3. List authorized projects with `planr company projects --json`. Actor and organization come from the verified token; identifiers in a request never establish permission.
 4. For a user-requested publication, `planr company preview <repository-relative-file> --project <id> --kind diagram|design|plan|document --json` records the exact selected file, bytes, size and digest. Show the publication scope. `planr company publish <preview-id> --json` explicitly publishes that preview. Content becomes accessible to the managed company service; source code and unselected files stay local. No hidden recursive upload.
 5. Inspect synchronization with `planr company status <binding-id> --json`. Update the same artifact using `planr company push <binding-id> --preview --json`, review the changed scope/content, then `planr company push <binding-id> --json`. Conflicts are comparisons to resolve, not permission to force overwrite.

package/lib/host-packages/claude/openplanr/skills/design/scripts/runtime/packages/protocol/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openplanr/protocol",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "type": "module",
   "description": "Canonical OpenPlanr schemas, registries, typed errors, and portable contract validation",
   "license": "MIT",