@rubytech/taskmaster 1.13.1 → 1.13.2

package/dist/build-info.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.13.1",
-  "commit": "d92801f174160fea1fbe6d2d8cfef7df8238a4ae",
-  "builtAt": "2026-03-03T14:12:45.492Z"
+  "version": "1.13.2",
+  "commit": "88d6bba938408c30d11292a357207ac4013341e1",
+  "builtAt": "2026-03-03T16:52:03.788Z"
 }

package/dist/entry.js

@@ -1,7 +1,33 @@
 #!/usr/bin/env node
 import { spawn } from "node:child_process";
+import { mkdirSync, appendFileSync } from "node:fs";
 import path from "node:path";
 import process from "node:process";
+/**
+ * Write a crash message to /tmp/taskmaster/crash.log so startup failures
+ * are visible even when systemd journal is unavailable (e.g. on the Pi).
+ */
+function writeCrashLog(label, error) {
+    try {
+        const msg = error instanceof Error ? (error.stack ?? error.message) : String(error);
+        const dir = "/tmp/taskmaster";
+        mkdirSync(dir, { recursive: true });
+        appendFileSync(path.join(dir, "crash.log"), `[${new Date().toISOString()}] ${label}: ${msg}\n`);
+    }
+    catch {
+        // Best-effort — nothing we can do if /tmp is unwritable.
+    }
+}
+process.on("uncaughtException", (err) => {
+    writeCrashLog("uncaughtException", err);
+    console.error("[taskmaster] uncaughtException:", err);
+    process.exit(1);
+});
+process.on("unhandledRejection", (reason) => {
+    writeCrashLog("unhandledRejection", reason);
+    console.error("[taskmaster] unhandledRejection:", reason);
+    process.exit(1);
+});
 import { applyCliProfileEnv, parseCliProfileArgs } from "./cli/profile.js";
 import { isTruthyEnvValue } from "./infra/env.js";
 import { installProcessWarningFilter } from "./infra/warnings.js";
@@ -54,6 +80,7 @@ function ensureExperimentalWarningSuppressed() {
         process.exit(code ?? 1);
     });
     child.once("error", (error) => {
+        writeCrashLog("Failed to respawn CLI", error);
         console.error("[taskmaster] Failed to respawn CLI:", error instanceof Error ? (error.stack ?? error.message) : error);
         process.exit(1);
     });
@@ -134,6 +161,7 @@ if (!ensureExperimentalWarningSuppressed()) {
     import("./cli/run-main.js")
         .then(({ runCli }) => runCli(process.argv))
         .catch((error) => {
+        writeCrashLog("Failed to start CLI", error);
         console.error("[taskmaster] Failed to start CLI:", error instanceof Error ? (error.stack ?? error.message) : error);
         process.exitCode = 1;
     });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/taskmaster",
-  "version": "1.13.1",
+  "version": "1.13.2",
   "description": "AI-powered business assistant for small businesses",
   "publishConfig": {
     "access": "public"

package/templates/zanzi-taxi/agents/admin/AGENTS.md

@@ -23,9 +23,11 @@ Before doing anything else:
 ## Operational Focus Areas
 
 ### Bookings
+- Booking records live at `bookings/{job-id}.md` in memory. Each tracks: route, fare, driver, status, timestamps, and ratings.
 - Summarise recent booking activity: confirmed, completed, cancelled, no-shows
 - Flag bookings where the driver didn't show or the tourist complained
 - Track conversion patterns: how many enquiries become bookings
+- Review reminder compliance: did drivers confirm when reminded? Identify drivers who frequently miss reminders.
 
 ### Drivers
 - Monitor driver ratings across all five dimensions (cleanliness, politeness, safety, knowledge, punctuality)

package/templates/zanzi-taxi/agents/public/AGENTS.md

@@ -30,7 +30,9 @@ When a tourist requests a ride:
 4. **Present offers** — show the tourist up to 3 competing offers: fare, driver rating, vehicle type, estimated journey time. No driver personal details at this stage.
 5. **Confirm booking** — when the tourist chooses, send a Stripe payment link for the booking fee.
 6. **Post-payment** — once payment clears, send: driver name, phone number, vehicle details, plate number, and the pickup PIN. Explain how PIN verification works.
-7. **Follow up** — after the estimated journey completion time, prompt for feedback and collect ratings.
+7. **Driver reminders** — for advance bookings, send tiered reminders (evening-before, 2-hour, 30-minute). Escalate immediately if a driver doesn't confirm.
+8. **Record the booking** — write a structured record to `bookings/{job-id}.md` on confirmation. Update at each lifecycle event (reminder, pickup, completion, rating).
+9. **Follow up** — after the estimated journey completion time, prompt for feedback and collect ratings.
 
 See the zanzi-taxi skill references for detailed behaviour at each phase.
 

package/templates/zanzi-taxi/skills/zanzi-taxi/SKILL.md

@@ -37,3 +37,5 @@ This skill applies whenever a tourist:
 - **Job ID on every driver message.** Prepend `[BGL-XXXX]` to every message sent to a driver.
 - **Confirm before acting.** Always get explicit tourist confirmation before booking. Never auto-confirm.
 - **Knowledge base is truth.** If the knowledge base doesn't cover a route or destination, say so.
+- **Remind drivers before pickup.** Advance bookings get tiered reminders (evening-before, 2-hour, 30-minute). Escalate if no confirmation.
+- **Record every booking.** Write a structured record to `bookings/{job-id}.md` on confirmation. Update at every lifecycle event.

package/templates/zanzi-taxi/skills/zanzi-taxi/references/ride-matching.md

@@ -63,6 +63,42 @@ Confirm the driver has received:
 - Fare confirmed
 - QR code (encodes the tourist's PIN)
 
+## Phase 6: Driver Pickup Reminders
+
+For advance bookings (pickup time is more than 1 hour from confirmation):
+
+1. **Evening before** — If the pickup is the next day, message the driver the evening before: `[BGL-XXXX] Reminder: pickup tomorrow at [time], [location]. Passenger: [name], [passengers] pax. Please confirm you're available.`
+2. **2 hours before** — Message the driver: `[BGL-XXXX] Pickup in 2 hours at [location]. Passenger: [name]. Please confirm.`
+3. **30 minutes before** — Final reminder: `[BGL-XXXX] Pickup in 30 minutes at [location]. Passenger [name] is expecting you.`
+
+If the driver does not confirm the evening-before or 2-hour reminder, escalate:
+- Attempt to reach the driver again
+- If no response, begin sourcing a replacement driver immediately
+- Notify the tourist only when you have a confirmed replacement or have exhausted options — don't create anxiety prematurely
+
+For same-day bookings with less than 2 hours lead time, send a single confirmation reminder 15 minutes before pickup.
+
+Also message the tourist at the 2-hour mark for advance bookings: "Your ride is confirmed for [time]. [Driver name] will be at [location]." This reassures them without requiring action.
+
+## Phase 7: Booking Record
+
+Every confirmed booking must be recorded in memory for audit. Store:
+
+- **Job ID** (e.g. `BGL-0042`)
+- **Tourist** — WhatsApp ID, name if given, number of passengers
+- **Route** — pickup location, destination
+- **Pickup datetime** — agreed date and time
+- **Driver** — name, WhatsApp number, vehicle, plate
+- **Fare** — negotiated amount, booking fee amount, Stripe payment ID
+- **PIN** — the 4-digit pickup code
+- **Status** — one of: `confirmed`, `reminded`, `picked_up`, `completed`, `cancelled`, `no_show`
+- **Timestamps** — when each status transition occurred
+- **Rating** — post-ride ratings (added after Phase 7 feedback)
+
+Write the booking record to memory at `bookings/{job-id}.md` on confirmation. Update the record at each lifecycle event (reminder sent, pickup, completion, rating). This creates a complete audit trail per booking.
+
+The admin agent uses these records for operational oversight — booking summaries, driver reliability tracking, and dispute resolution.
+
 ## Edge Cases
 
 **Tourist wants to cancel after payment:** Explain the booking fee is non-refundable (commitment device for both sides). Offer to reschedule at no extra charge.