@flowapt/flowiq-cli 0.9.5 → 0.9.6

package/README.md

@@ -1845,9 +1845,13 @@ flowiq plans status <plan_id> --to sent --commit
   timestamps instead of the send date (SAST day start) — "what did a client
   submit today", "what has moved since Friday", which `--since` cannot answer.
 - **`show`** prints the plan the way the dialog does: message copy, the
-  second message sent when a button is tapped, buttons with their URLs, the
-  creative (file name + link), audience, template link, the response to the
-  client, internal notes and the notes thread.
+  second message sent when a button is tapped (named by the button's text),
+  buttons with their targets, the creative (file name + link), audience,
+  template link, the response to the client, internal notes and the notes
+  thread. A marketing plan carries 0-10 buttons in any mix WhatsApp allows:
+  `quick_reply`, `url` (up to 2, `→ link`), `phone` (1, `→ call +27…`) and
+  `copy_code` (1, `→ code SPRING20`); each quick reply may have its own
+  follow-up message (`slide2a`, `slide2b`, `slide2c` … by button position).
 - **`status`** is a dry run until `--commit`. `--comment` is the response the
   **client reads**; `--internal` is staff-only. `approved` and `rejected`
   record you as the reviewer; `rejected` requires `--comment`. Every commit is
@@ -1894,6 +1898,12 @@ flowiq test cleanup <organization_id> --confirm      # delete the stress contact
 `--agent <id>` targets a specific (non-active) agent. `test stress cleanup` is
 destructive and requires `--confirm`.
 
+`test clear` (and `--clear` on `send`, and the clear between scenario turns) hides the
+messages (`memory_cutoff`) AND sets aside the agent's remembered tool results
+(`more_data.tool_usage_history`, which the agent reads as TOOL USAGE HISTORY) under
+`more_data.tool_usage_history_cleared`, so a cleared test really starts fresh. Since 0.9.6;
+before that earlier tool results and escalation reasons leaked into "cleared" tests.
+
 ### Guide — `flowiq guide`
 
 Read the bundled docs in the terminal — no digging through node_modules.

package/TEAM-GUIDE.md

@@ -116,6 +116,7 @@ When you see it, run `npm i -g @flowapt/flowiq-cli` — a stale version also mea
 | Agent can't quote ANY price / "I can't pull the live menu" | `flowiq agent config <org_id> --tool product_lookup=true` — name-based fuzzy lookup that works without embeddings or a live OpenAI key (semantic `get_product_info` needs both) |
 | Client wants leads/requests emailed to their team instead of a human escalation | `flowiq agent config <org_id> --tool email_request_tool=true`, then set the recipient list in Agents → Tool Library → Email Request to Team (no CLI path for the addresses yet) |
 | Talk to the live agent safely (no real WhatsApp ever sent) | `flowiq test send <org_id> "hi, do you sell X?"` |
+| Start a test chat from scratch (agent forgets the earlier test messages AND its earlier tool results) | `flowiq test clear <org_id>` (or `flowiq test send <org_id> "…" --clear`) |
 | **Tell the team what shipped** (the FlowIQ team update email) | `flowiq updates draft` → enrich the JSON (screenshots via `flowiq updates asset`, a *For the team* note per headline) → `flowiq updates preview <file> --open` → `flowiq updates send <file> --test` → `flowiq updates send <file> --yes` |
 | Can I use `flowiq updates`? | Yes: `status`, `uncovered`, `draft`, `preview` and `send --test` (a copy to yourself) work for everyone. Only the real `send --yes` to the whole team is Matt's; anyone else gets a 403 there |
 | Which changelog rows has nobody emailed the team about yet? | `flowiq updates status` / `flowiq updates uncovered` — anything left 20h+ goes out automatically at 08:30 SAST as a plain digest |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flowapt/flowiq-cli",
-  "version": "0.9.5",
+  "version": "0.9.6",
   "description": "Command-line tool for FlowIQ staff: round-trip agent prompts, questionnaires, fine-tuning, pin-board tasks, webhooks, templates, agent-updates, chat exports, and live agent testing without ever touching service-role credentials.",
   "type": "module",
   "bin": {

package/src/commands/agent-test.js

@@ -146,7 +146,8 @@ export async function clear(orgId, opts = {}) {
   let resp;
   try { resp = await clearConv(orgId, opts.agent); }
   catch (e) { console.error(`Clear failed: ${e.message}`); process.exit(1); }
-  console.log(`Cleared web conversation for contact ${resp.contact_id} (history hidden via memory_cutoff; onboarding/disclaimer state NOT reset).`);
+  const tools = Number(resp.tools_cleared || 0);
+  console.log(`Cleared web conversation for contact ${resp.contact_id} (history hidden via memory_cutoff; ${tools} remembered tool result(s) set aside in more_data.tool_usage_history_cleared; onboarding/disclaimer state NOT reset).`);
 }
 
 // ---------- phase 2: stress + extract ----------

package/src/commands/plans.js

@@ -182,7 +182,9 @@ export async function show(planId, opts = {}) {
   if (more.slides && typeof more.slides === "object") {
     for (const [key, slide] of Object.entries(more.slides)) {
       if (!slide || typeof slide !== "object") continue;
-      console.log(`\n${key}${slide.triggered_by ? ` (after ${slide.triggered_by})` : ""}`);
+      const idx = /^button_(\d+)$/.exec(slide.triggered_by ?? "")?.[1];
+      const tapped = idx !== undefined && Array.isArray(more.buttons) ? more.buttons[Number(idx)]?.text : null;
+      console.log(`\n${key}${tapped ? ` (sent when "${tapped}" is tapped)` : slide.triggered_by ? ` (after ${slide.triggered_by})` : ""}`);
       if (slide.message) console.log(indent(slide.message));
       if (slide.media_url) console.log(`  media: ${slide.media_url}`);
     }
@@ -191,7 +193,11 @@ export async function show(planId, opts = {}) {
   const buttons = Array.isArray(more.buttons) ? more.buttons : [];
   if (buttons.length) {
     console.log("\nButtons");
-    for (const b of buttons) console.log(`  [${b?.type ?? "?"}] ${b?.text ?? ""}${b?.url ? ` → ${b.url}` : ""}`);
+    // Marketing plans carry 0-10 buttons: quick_reply, url, phone, copy_code (app src/lib/broadcastPlanButtons.ts).
+    for (const b of buttons) {
+      const target = b?.url ? ` → ${b.url}` : b?.phone_number ? ` → call ${b.phone_number}` : b?.code ? ` → code ${b.code}` : "";
+      console.log(`  [${b?.type ?? "?"}] ${b?.text ?? ""}${target}`);
+    }
   }
 
   console.log("\nCreative");