octwin-cli 0.9.0 → 0.9.2

package/CHANGELOG.md

@@ -7,6 +7,24 @@ repo root [`CHANGELOG.md`](../../CHANGELOG.md); this file is the CLI-only cut th
 
 ## [Unreleased]
 
+## [0.9.2] - 2026-10-22
+
+### Changed
+- **`SYMBOLS.md` says what each builtin does, beside its signature.** A builtin's row showed only
+  `(str: unknown, n: unknown, ellipsis?: unknown): string`, so `$first_n` read as "the first N items" and an
+  author fed it to a list (aani-dani, 2026-10-20) — it is the first N WORDS. The row is now the signature,
+  then the catalog's one-sentence summary. (`src/lib/kb-symbols.ts`)
+
+## [0.9.1] - 2026-10-22
+
+### Fixed
+- **The starter's `request` flow declares `issue` as `type: enum`.** It said `type: string` with an `enum:`
+  list, which the platform ignores on any type but `enum` — so the AI Agent could pass any text for the
+  issue, and every pack made with `octwin init` copied the mistake (32 of 99 installed versions on staging,
+  2026-10-22). The platform now refuses the next deploy of a flow with that shape
+  (`enum-on-non-enum-type`), so a pack made by 0.9.0's `octwin init` must change that one word first.
+  (`templates/starter/flows/tools/request.flow.yaml`)
+
 ## [0.9.0] - 2026-10-21
 
 ### Changed

package/dist/cli.js

@@ -6373,34 +6373,34 @@ octwin projects rm <slug> [--yes]
 
   --dow is 0-6, 0 = Sunday. \`rules\` is how you find an id to remove, and
   \`--slots\` is how you check what a rule actually produces.`,
-    automation: `octwin automation [coming | happened | why <id> | campaigns | --campaigns] [--json]
-  No args = every RULE of the project — each in the platform's own words (the
-  sentence the console's Outbound → Automatic tab shows), on or paused, its week
-  (sent / not delivered / failed / skipped) and its next time — under the week's
-  numbers and what needs a look. Needs automation:read.
-
-  A pack writes rules in automation.yaml \`rules:\`; its older \`segment\` /
-  \`stale_records\` / \`sla_sweep\` jobs and xrm \`on:\` hooks run as rules too,
-  listed under the key they compile to (\`segment:<job key>\`).
-
-  READ:
-    octwin automation coming   [--range today|tomorrow|week|all] [--entity e] [--q text] [--cursor c]
-                               # every time still to come — a rule's, or a flow's own message
-    octwin automation happened [--chip all|not_delivered|failed|skipped|moves|tasks] [--period 7d|30d] [--cursor c]
-                               # every fire: its final word, and why a message did not go
-    octwin automation why <id> [--kind timer|fire|queued]
-                               # one line: the rule in words, each step, the words sent
-    octwin automation campaigns [--limit n] [--offset n]
-
-  WRITES (automation:write):
-    octwin automation pause|resume <ruleKey>   # paused: its times arm, nothing runs, nothing caught up
-    octwin automation run <ruleKey>            # a rule on a timetable, now
-    octwin automation send <campaignId>        # enqueue a campaign; enqueued != delivered
-
-  <ruleKey> is the key the list prints; the key of the older job in your own
-  automation.yaml finds the rule it runs as. A 403 on a write can be an RBAC grant
-  gap rather than a missing scope: the action is re-checked on automation.rule.
-  (Until 0.9.0 this command listed job rows — since the platform ran every pack's
+    automation: `octwin automation [coming | happened | why <id> | campaigns | --campaigns] [--json]
+  No args = every RULE of the project — each in the platform's own words (the
+  sentence the console's Outbound → Automatic tab shows), on or paused, its week
+  (sent / not delivered / failed / skipped) and its next time — under the week's
+  numbers and what needs a look. Needs automation:read.
+
+  A pack writes rules in automation.yaml \`rules:\`; its older \`segment\` /
+  \`stale_records\` / \`sla_sweep\` jobs and xrm \`on:\` hooks run as rules too,
+  listed under the key they compile to (\`segment:<job key>\`).
+
+  READ:
+    octwin automation coming   [--range today|tomorrow|week|all] [--entity e] [--q text] [--cursor c]
+                               # every time still to come — a rule's, or a flow's own message
+    octwin automation happened [--chip all|not_delivered|failed|skipped|moves|tasks] [--period 7d|30d] [--cursor c]
+                               # every fire: its final word, and why a message did not go
+    octwin automation why <id> [--kind timer|fire|queued]
+                               # one line: the rule in words, each step, the words sent
+    octwin automation campaigns [--limit n] [--offset n]
+
+  WRITES (automation:write):
+    octwin automation pause|resume <ruleKey>   # paused: its times arm, nothing runs, nothing caught up
+    octwin automation run <ruleKey>            # a rule on a timetable, now
+    octwin automation send <campaignId>        # enqueue a campaign; enqueued != delivered
+
+  <ruleKey> is the key the list prints; the key of the older job in your own
+  automation.yaml finds the rule it runs as. A 403 on a write can be an RBAC grant
+  gap rather than a missing scope: the action is re-checked on automation.rule.
+  (Until 0.9.0 this command listed job rows — since the platform ran every pack's
   automation as rules, those were only its own two sweeps.)`,
     integrations: `octwin integrations [--json]
   What the pack DECLARES beside what is actually CONFIGURED, in one view — because a

package/dist/lib/kb-symbols.js

@@ -78,10 +78,15 @@ const EXTRACTORS = {
     },
     builtins(entry, file) {
         const v = obj(entry.value);
-        // `$` is how an author writes it, and how they will grep for it.
+        // `$` is how an author writes it, and how they will grep for it. The line carries the
+        // signature AND what it does: `(str, n): string` alone let an author take `$first_n` for
+        // "the first N items" — it is the first N WORDS (aani-dani, 2026-10-20). Longer clamp than
+        // the other rows, so the sentence survives beside the signature.
+        const sig = str(v?.signature);
+        const what = str(v?.summary) ?? str(entry.summary);
         return [{
                 symbol: `$${entry.name}`, kind: 'builtin', file,
-                summary: line(str(v?.signature) ?? entry.summary),
+                summary: line(sig && what ? `${sig} — ${what}` : sig ?? what, 180),
             }];
     },
     templates(entry, file) {

package/package.json

@@ -1,46 +1,46 @@
-{
-  "name": "octwin-cli",
-  "version": "0.9.0",
-  "description": "Octwin external-pack developer CLI (by CEQUENS) — scaffold, validate, deploy, and check pure-YAML packs on your tenant.",
-  "type": "module",
-  "bin": {
-    "octwin": "dist/index.js"
-  },
-  "files": [
-    "dist",
-    "templates",
-    "README.md",
-    "CHANGELOG.md",
-    "LICENSE"
-  ],
-  "engines": {
-    "node": ">=22"
-  },
-  "scripts": {
-    "build": "tsc -p tsconfig.json",
-    "prepublishOnly": "npm run build"
-  },
-  "dependencies": {
-    "yaml": "^2.6.0"
-  },
-  "devDependencies": {
-    "@types/node": "^22.0.0",
-    "typescript": "^5.7.0"
-  },
-  "publishConfig": {
-    "access": "public"
-  },
-  "keywords": [
-    "octwin",
-    "cequens",
-    "cli",
-    "whatsapp",
-    "chatbot",
-    "pack",
-    "conversational-ai",
-    "yaml"
-  ],
-  "author": "CEQUENS",
-  "homepage": "https://octwin.ai",
-  "license": "MIT"
-}
+{
+  "name": "octwin-cli",
+  "version": "0.9.2",
+  "description": "Octwin external-pack developer CLI (by CEQUENS) — scaffold, validate, deploy, and check pure-YAML packs on your tenant.",
+  "type": "module",
+  "bin": {
+    "octwin": "dist/index.js"
+  },
+  "files": [
+    "dist",
+    "templates",
+    "README.md",
+    "CHANGELOG.md",
+    "LICENSE"
+  ],
+  "engines": {
+    "node": ">=22"
+  },
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "prepublishOnly": "npm run build"
+  },
+  "dependencies": {
+    "yaml": "^2.6.0"
+  },
+  "devDependencies": {
+    "@types/node": "^22.0.0",
+    "typescript": "^5.7.0"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "keywords": [
+    "octwin",
+    "cequens",
+    "cli",
+    "whatsapp",
+    "chatbot",
+    "pack",
+    "conversational-ai",
+    "yaml"
+  ],
+  "author": "CEQUENS",
+  "homepage": "https://octwin.ai",
+  "license": "MIT"
+}

package/templates/starter/flows/tools/request.flow.yaml

@@ -4,7 +4,7 @@ description: Ask for a technician's visit. Call when the customer reports a prob
 
 input:
   area:  { type: string, agent_fillable: false }   # an area record id — only a tapped row sets it
-  issue: { type: string, optional: true, enum: [leak, power, ac, other] }
+  issue: { type: enum, optional: true, enum: [leak, power, ac, other] }
 
 entry:
   - else: true