@openengio/cli 0.27.0 → 0.27.1

package/bin/public/openeng.js

@@ -10956,7 +10956,7 @@ var CLI_OPTIONS = {
 };
 
 // packages/cli/src/cli-version.ts
-var PATCH_VERSION = 0;
+var PATCH_VERSION = 1;
 var CLI_VERSION = `0.${PROTOCOL_VERSION}.${PATCH_VERSION}`;
 
 // packages/cli/src/environment.ts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openengio/cli",
-  "version": "0.27.0",
+  "version": "0.27.1",
   "license": "Apache-2.0",
   "type": "module",
   "engines": {

package/skill/demo/SKILL.md

@@ -7,12 +7,21 @@ description: Use when a person new to OpenEngineering wants a hands-on tour, or
 
 ## 1. Offer three paths
 
+At every decision in sections 1–3 (path, workflow, next story or step), use your harness's
+multiple-choice question tool if your tool set has one; otherwise ask as a short numbered list.
+Make the first option the happy path: a named next step the person can select to move forward
+without more typing. Offer two or three other real options, never filler. Say once, early, that
+they can always skip a question or type their own answer. Ask every question a step needs together,
+in one multiple-choice call where your tool allows several, so the person answers them in one go;
+run routine commands without permission questions. Each stop point
+asks its own question; an offered option never replaces the person's required words.
+
 After sign-in, when the person has no task of their own, offer once:
 
-- **Seed demo**: create a project, run `openeng demo seed --project <id>`, then follow the
-  [Quickstart](https://docs.openeng.io/get-started/quickstart/) together.
 - **Free-form tour** (the main path): build a small example around their work and explore its
   capabilities together in the app.
+- **Seed demo**: create a project, run `openeng demo seed --project <id>`, then follow the
+  [Quickstart](https://docs.openeng.io/get-started/quickstart/) together.
 - **Something else**: follow the task the person names. They may decline the tour.
 
 Before the tour starts, load every capability below into your own native task or plan tool,
@@ -74,7 +83,6 @@ Ask what the person designs or manages and where the work gets hard. Offer a fit
 or use their own vocabulary. Agree a small story with a visible result. Create a demo organisation
 with `openeng org create` unless asked to use an existing one; say which data is invented.
 Ask before touching existing data, inviting anyone, connecting Onshape or registering an app.
-Ask at most two questions at a time; do not turn routine commands into permission questions.
 
 Whenever the tour designs types, read `openeng skill new-use-case` and follow every stop point
 in order: show the person the work and wait for agreement at each one. Do not skip a stop point