@inetafrica/open-claudia 3.5.68 → 3.5.69

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 3.5.69
+
+3.5.68 plus the card fixes from Sumeet's 17 Oct review of the test cards (Sumeet, 20 Oct 07:43 EAT: "Why don't you just push them out now?"): a bare date did not say what it was, and the board's side-by-side columns are cramped on a phone.
+
+- **Due dates say "Due"** (`bin/cards.js`): `card example due-dates` sets dateLabel "Due" on its rows question, so Kazee Chat draws "Due Tue 20 Oct" (chat-central f20b993, phone 4.6.3, web e25a670).
+- **Status list instead of the board**: new `card example status`, a rows question with To do / Doing / Done chips, each row starting where it is. `card pieces` marks board "old cards only" and points to it; the card coach no longer suggests a board. Old board cards still draw and wake as before.
+
+Tests: `test-card-blocks.js` (the due-dates label, the status example, board marked old cards only).
+
 ## 3.5.68
 
 3.5.67 plus a guard on test runs (Sumeet, 19 Oct 11:47 EAT, card "Mac: stop parallel threads from running it out of memory": "Both: checker rule and safety net"). The Mac froze twice that morning (power button held at 10:51 and 11:09 EAT): parallel conversations' test runs wanted about 26 GB on the 16 GB Mac, 12 of those GB from one helper's `npx jest` with no worker cap. The same morning the Chat Spaces bot pod was OOM-killed twice by `jest --maxWorkers=4` under its 3 Gi limit. The rule in lessons.md never reached helpers; the tool hook does.

package/bin/cards.js

@@ -67,7 +67,7 @@ const EXAMPLES = {
     body: "Tick the ones that are fine. Tap a date to change it.",
     input: {
       fields: [
-        { id: "tasks", type: "rows", label: "Tasks", tick: true, checked: true,
+        { id: "tasks", type: "rows", label: "Tasks", tick: true, checked: true, dateLabel: "Due",
           options: [{ id: "close", label: "Close it" }],
           rows: [
             { id: "clickhouse", label: "ClickHouse public access", detail: "Remove it, or office/VPN only", date: "2026-10-20" },
@@ -83,6 +83,29 @@ const EXAMPLES = {
     },
     policy: { responders: ["<kazeeUserId>"], mode: "first", results: "hidden" },
   },
+  // Where things stand: a list with a status chip per row (Sumeet, 17 Oct:
+  // the board's side-by-side columns are cramped on a phone). Use this, not
+  // a board, to ask where items are.
+  status: {
+    v: 1, kind: "form", kicker: "Spaces · this week", tag: "3 tasks",
+    title: "Where do these stand?",
+    body: "Tap where each one really is, then press Send once.",
+    input: {
+      fields: [
+        { id: "week", type: "rows", label: "This week", tick: false, dates: false,
+          options: [{ id: "todo", label: "To do" }, { id: "doing", label: "Doing" }, { id: "done", label: "Done" }],
+          rows: [
+            { id: "dog-06", label: "Clean iNet's CRM data", detail: "DOG-06 · due 23 Oct", option: "todo" },
+            { id: "dog-14", label: "Stop old Zoho history going out as new", detail: "DOG-14 · due 20 Oct", option: "todo" },
+            { id: "dog-04", label: "Fix the nightly Zoho import", detail: "DOG-04", option: "done" },
+          ] },
+      ],
+      submitLabel: "Send",
+    },
+    policy: { responders: ["<kazeeUserId>"], mode: "first", results: "hidden" },
+  },
+  // Old cards only: phones and the web still draw a board, but a new card
+  // asks where things stand with `status` above.
   board: {
     v: 1, kind: "form", kicker: "Spaces · this week", tag: "3 tasks",
     title: "Where do these stand?",
@@ -161,8 +184,8 @@ const PIECES = [
   { name: "tick", where: "question", use: "one yes/no tick box, a confirmation", example: "checks" },
   { name: "date", where: "question", use: "one date picker, optional min and max", example: "checks" },
   { name: "slots", where: "question", use: "pick meeting times from a day x time grid; busy slots can't be picked", example: "meeting" },
-  { name: "rows", where: "question", use: "a list where each row gets a tick, a date and/or option chips (approve, re-date, close items)", example: "due-dates" },
-  { name: "board", where: "question", use: "move items between columns (to do, doing, done)", example: "board" },
+  { name: "rows", where: "question", use: "a list where each row gets a tick, a date (dateLabel names it: \"Due\") and/or option chips (approve, re-date, close items; To do / Doing / Done)", example: "due-dates, status" },
+  { name: "board", where: "question", use: "old cards only: to ask where things stand use rows with To do / Doing / Done options", example: "status" },
 ];
 
 function piecesText() {
@@ -204,13 +227,13 @@ const CARD_USAGE = `Usage:
   open-claudia card send <spec.json | '{json}' | -> [--wake each|first|none] [--content "plain text"]
   open-claudia card update <messageId> [--close | --open] [--note "text"] [--spec <file|json>]
   open-claudia card show <messageId>
-  open-claudia card example <decision|choice|rating|slider|form|report|due-dates|board|meeting|table|checks>
+  open-claudia card example <decision|choice|rating|slider|form|report|due-dates|status|meeting|table|checks>
   open-claudia card pieces
 Cards are Kazee Chat only. Answers wake this conversation when --wake is each
 (default for a card a few named people answer) or first; polls anyone answers
 default to none. Spec: chat-central CARDS-V1 (v:1, kind, title, input, policy...).
 Pieces (card pieces lists them): blocks text, stats, bars, facts, table; form
-questions choice, rating, text, tick, date, slots, rows, board.`;
+questions choice, rating, text, tick, date, slots, rows (board: old cards only).`;
 
 async function runCard(args) {
   const sub = args.shift();

package/core/card-coach.js

@@ -47,7 +47,7 @@ function detect(text) {
 }
 
 function hintLine(items) {
-  return `Card coach: your last message listed ${items} items for the reader to decide in plain text. One card built from pieces (rows with ticks, dates or options; board; time slots; table) lets them answer with one Send. See open-claudia card pieces.`;
+  return `Card coach: your last message listed ${items} items for the reader to decide in plain text. One card built from pieces (rows with ticks, dates or options such as To do / Doing / Done; time slots; table) lets them answer with one Send. See open-claudia card pieces.`;
 }
 
 function conversationKey({ adapterId, channelId, threadId }) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inetafrica/open-claudia",
-  "version": "3.5.68",
+  "version": "3.5.69",
   "description": "An always-on, provider-agnostic coding-agent harness for Claude Code and OpenAI Codex via chat",
   "main": "bot.js",
   "bin": {

package/test-provider-language.js

@@ -653,7 +653,10 @@ assert.match(pkg.description, /provider-agnostic coding-agent harness/i);
 // 3.5.68 = 3.5.67 + test-run guard (jest/vitest: 2 workers, one run at a time,
 // 40% free memory) in the tool hook, after the Mac froze twice on 19 Oct.
 // Sumeet, 19 Oct 11:47 EAT card: "Both: checker rule and safety net".
-assert.strictEqual(pkg.version, "3.5.68", "release version must remain unchanged without explicit approval");
+// 3.5.69 = 3.5.68 + card fixes from the 17 Oct review: due dates say "Due",
+// a status list (rows with To do / Doing / Done) instead of the board.
+// Sumeet, 20 Oct 07:43 EAT: "Why don't you just push them out now?"
+assert.strictEqual(pkg.version, "3.5.69", "release version must remain unchanged without explicit approval");
 for (const keyword of ["claude", "codex", "coding-agent", "provider-agnostic"]) {
   assert.ok(pkg.keywords.includes(keyword), `package keyword missing: ${keyword}`);
 }