npm - @rubytech/taskmaster - Versions diffs - 1.17.0 → 1.17.4 - Mend

@rubytech/taskmaster 1.17.0 → 1.17.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (14) hide show

package/dist/agents/workspace-migrations.js +61 -0
package/dist/build-info.json +3 -3
package/dist/config/agent-tools-reconcile.js +58 -0
package/dist/control-ui/assets/{index-Beuhzjy_.js → index-koe4eKhk.js} +4 -4
package/dist/control-ui/assets/index-koe4eKhk.js.map +1 -0
package/dist/control-ui/index.html +1 -1
package/dist/cron/service/timer.js +5 -1
package/dist/gateway/server-methods/apikeys.js +2 -0
package/dist/gateway/server.impl.js +16 -1
package/dist/hooks/bundled/ride-dispatch/handler.js +23 -9
package/package.json +1 -1
package/templates/beagle-zanzibar/agents/admin/AGENTS.md +16 -8
package/templates/beagle-zanzibar/agents/public/AGENTS.md +10 -5
package/dist/control-ui/assets/index-Beuhzjy_.js.map +0 -1

package/dist/control-ui/index.html CHANGED Viewed

@@ -6,7 +6,7 @@
     <title>Taskmaster Control</title>
     <meta name="color-scheme" content="dark light" />
     <link rel="icon" type="image/png" href="./favicon.png" />
-    <script type="module" crossorigin src="./assets/index-Beuhzjy_.js"></script>
+    <script type="module" crossorigin src="./assets/index-koe4eKhk.js"></script>
     <link rel="stylesheet" crossorigin href="./assets/index-XqRo9tNW.css">
   </head>
   <body>

package/dist/cron/service/timer.js CHANGED Viewed

@@ -103,7 +103,11 @@ export async function executeJob(state, job, nowMs, opts) {
         }
         if (job.sessionTarget === "isolated") {
             const prefix = job.isolation?.postToMainPrefix?.trim() || "Cron";
-            const mode = job.isolation?.postToMainMode ?? "summary";
+            const configuredMode = job.isolation?.postToMainMode ?? "summary";
+            // When delivery was skipped (best-effort, no external channel configured),
+            // promote to "full" so the admin sees the actual report in their main chat
+            // instead of a delivery-error summary.
+            const mode = status === "skipped" && outputText ? "full" : configuredMode;
             let body = (summary ?? err ?? status).trim();
             if (mode === "full") {
                 // Prefer full agent output if available; fall back to summary.

package/dist/gateway/server-methods/apikeys.js CHANGED Viewed

@@ -27,6 +27,8 @@ const PROVIDER_CATALOG = [
     { id: "brave", name: "Brave", category: "Web Search" },
     { id: "elevenlabs", name: "ElevenLabs", category: "Voice" },
     { id: "brevo", name: "Brevo", category: "Email" },
+    { id: "stripe", name: "Stripe", category: "Payments" },
+    { id: "stripe_webhook_secret", name: "Stripe Webhook Secret", category: "Payments" },
 ];
 const VALID_PROVIDER_IDS = new Set(PROVIDER_CATALOG.map((p) => p.id));
 export const apikeysHandlers = {

package/dist/gateway/server.impl.js CHANGED Viewed

@@ -10,7 +10,7 @@ import { CONFIG_PATH_TASKMASTER, isNixMode, loadConfig, migrateLegacyConfig, rea
 import { VERSION } from "../version.js";
 import { isDiagnosticsEnabled } from "../infra/diagnostic-events.js";
 import { logAcceptedEnvOption } from "../infra/env.js";
-import { reconcileAgentContactTools, reconcileBeaglePublicTools, reconcileQrGenerateTool, reconcileStaleToolEntries, } from "../config/agent-tools-reconcile.js";
+import { reconcileAgentContactTools, reconcileBeaglePublicTools, reconcileControlPanelTools, reconcileQrGenerateTool, reconcileStaleToolEntries, } from "../config/agent-tools-reconcile.js";
 import { applyPluginAutoEnable } from "../config/plugin-auto-enable.js";
 import { clearAgentRunContext, onAgentEvent } from "../infra/agent-events.js";
 import { onHeartbeatEvent } from "../infra/heartbeat-events.js";
@@ -198,6 +198,21 @@ export async function startGatewayServer(port = 18789, opts = {}) {
             log.warn(`gateway: failed to persist qr_generate tool reconciliation: ${String(err)}`);
         }
     }
+    // Upgrade admin agents from individual control-panel tools to group:control-panel.
+    // Agents set up before the group existed miss tools added to it later (e.g. logs_read).
+    const cpReconcile = reconcileControlPanelTools({ config: configSnapshot.config });
+    if (cpReconcile.changes.length > 0) {
+        try {
+            await writeConfigFile(cpReconcile.config);
+            configSnapshot = await readConfigFileSnapshot();
+            log.info(`gateway: reconciled control-panel tools:\n${cpReconcile.changes
+                .map((entry) => `- ${entry}`)
+                .join("\n")}`);
+        }
+        catch (err) {
+            log.warn(`gateway: failed to persist control-panel tools reconciliation: ${String(err)}`);
+        }
+    }
     // Stamp config with running version on startup so upgrades keep the stamp current.
     const storedVersion = configSnapshot.config.meta?.lastTouchedVersion;
     if (configSnapshot.exists && storedVersion !== VERSION) {

package/dist/hooks/bundled/ride-dispatch/handler.js CHANGED Viewed

@@ -253,12 +253,15 @@ function buildTripRequestInstruction(fields, resolvedAccountId) {
         `4. For each selected driver, update their status to awaiting_response via memory_write\n` +
         `5. Write shared/active-negotiations/{driver-phone}.md with job_id: ${jobId} for each driver\n` +
         `6. Message each driver in Swahili with the route details, pickup time, passengers, and job ID [${jobId}]\n` +
-        `   Use the message tool with accountId: "${accountId}"\n` +
+        `   Use the message tool with channel: "whatsapp", accountId: "${accountId}"\n` +
         `7. Message the tourist at ${touristPhone} confirming you've contacted drivers and are waiting for quotes\n` +
-        `   Use the message tool with accountId: "${accountId}"\n` +
+        `   Use the message tool with channel: "whatsapp", accountId: "${accountId}"\n` +
         `8. When drivers reply with quotes (dispatched to this session), compile the offers\n` +
-        `9. Message the tourist with up to 3 competing offers: fare, driver rating, vehicle type, estimated journey time\n` +
-        `   Do NOT reveal driver name, phone, or plate — those are gated by payment\n`);
+        `9. Message the tourist at ${touristPhone} with up to 3 competing offers: fare, vehicle type, driver rating, estimated journey time\n` +
+        `   Use the message tool with channel: "whatsapp", accountId: "${accountId}"\n` +
+        `   Cross-agent echo will relay the message to the tourist's active session automatically\n` +
+        `   Do NOT reveal driver name, phone, or plate — those are gated by payment\n` +
+        `   NOTE: Do NOT write a dispatch file for the offers — message the tourist directly\n`);
 }
 function buildBookingConfirmInstruction(fields, resolvedAccountId) {
     const jobId = fields.job_id ?? "UNKNOWN";
@@ -278,7 +281,7 @@ function buildBookingConfirmInstruction(fields, resolvedAccountId) {
         `1. Load the stripe skill and generate a Checkout Session for the booking fee\n` +
         `   Set metadata: booking_id="${jobId}", tourist_phone="${touristPhone}"\n` +
         `2. Message the tourist at ${touristPhone} with the payment link and booking terms\n` +
-        `   Use the message tool with accountId: "${accountId}"\n` +
+        `   Use the message tool with channel: "whatsapp", accountId: "${accountId}"\n` +
         `3. Record the booking details in shared/bookings/${jobId}.md via memory_write\n` +
         `4. Clear the active negotiation files for drivers NOT selected (delete their shared/active-negotiations/{phone}.md)\n`);
 }
@@ -293,9 +296,9 @@ function buildPaymentConfirmedInstruction(params) {
         `1. Read the booking record at shared/bookings/${bookingId}.md for driver details\n` +
         `2. Generate the pickup PIN and QR code (see references/pin-qr.md)\n` +
         `3. Message the tourist at ${touristPhone} with: driver name, phone, vehicle details, plate, and pickup PIN\n` +
-        `   Use the message tool with accountId: "${accountId}"\n` +
+        `   Use the message tool with channel: "whatsapp", accountId: "${accountId}"\n` +
         `4. Message the driver with: passenger name, pickup time/location, fare, and QR code URL\n` +
-        `   Use the message tool with accountId: "${accountId}"\n` +
+        `   Use the message tool with channel: "whatsapp", accountId: "${accountId}"\n` +
         `5. Update the booking record status to "confirmed"\n` +
         `6. Clear the active negotiation file for the driver (shared/active-negotiations/{phone}.md)\n`);
 }
@@ -337,6 +340,10 @@ async function handleMemoryAdd(event) {
         return;
     }
     const fields = parseDispatchFile(content);
+    // Normalize: public agents may write tourist_id instead of tourist_phone
+    if (!fields.tourist_phone && fields.tourist_id) {
+        fields.tourist_phone = fields.tourist_id;
+    }
     // Load config (memory:add events don't carry cfg)
     let cfg;
     try {
@@ -427,8 +434,15 @@ async function handleDriverReply(event) {
         `Driver phone: ${senderPhone}\n` +
         `Message: ${text}\n\n` +
         `Process this reply in the context of the ongoing negotiation for ${jobId}.\n` +
-        `If this is a fare quote, note it and compile offers when ready.\n` +
-        `If the driver is declining, update their status and active negotiation index.\n`;
+        `If this is a fare quote:\n` +
+        `  - Record the quote in the driver's memory profile\n` +
+        `  - When all expected quotes are in (or after a reasonable wait), compile the offers\n` +
+        `  - Message the tourist directly using the message tool with the compiled offers\n` +
+        `    The tourist phone is in the earlier trip-request message in this session\n` +
+        `    Use the message tool with channel: "whatsapp", accountId: "${accountId}"\n` +
+        `    Do NOT write a dispatch file — use the message tool to send the offers directly\n` +
+        `    Cross-agent echo will relay it to the tourist's active session automatically\n` +
+        `If the driver is declining, update their status in memory and delete their shared/active-negotiations/{phone-digits}.md file.\n`;
     console.log(`[ride-dispatch] Driver reply from ${senderPhone} for ${jobId}, dispatching to admin agent "${adminAgentId}"`);
     // Fire and forget — suppress is already set, caller will skip processForRoute
     dispatchToAdmin({

package/package.json CHANGED Viewed

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

package/templates/beagle-zanzibar/agents/admin/AGENTS.md CHANGED Viewed

@@ -77,9 +77,12 @@ When you receive `[System: Ride Dispatch — Trip Request]`:
    - Update their status to `awaiting_response` via `memory_write`
    - Write `shared/active-negotiations/{driver-phone-digits}.md` with `job_id`, `driver_name`, and `contacted_at`
 5. Message each driver in Swahili via the `message` tool with route details, pickup time, passengers, and job ID
-6. Message the tourist confirming drivers have been contacted and quotes are being gathered
-7. When driver replies arrive (dispatched as `[System: Ride Dispatch — Driver Reply]`), compile offers
-8. Message the tourist with up to 3 competing offers — fare, rating, vehicle type, journey time. Do NOT reveal driver name, phone, or plate (gated by payment)
+6. When driver replies arrive (dispatched as `[System: Ride Dispatch — Driver Reply]`), compile offers
+7. Message the tourist at `tourist_phone` using the `message` tool with `accountId` from this dispatch
+   - Include up to 3 offers: fare, vehicle type, driver rating, estimated journey time
+   - Do NOT reveal driver name, phone, or plate — those are gated by payment
+   - Cross-agent echo will relay the WhatsApp message to the tourist's active session automatically
+   - Do NOT write a dispatch file for the offers — message directly
 ### Booking Confirmation
@@ -87,18 +90,21 @@ When you receive `[System: Ride Dispatch — Booking Confirmation]`:
 1. Load the `stripe` skill and generate a Checkout Session for the booking fee
    - Set metadata: `booking_id`, `tourist_phone`, `account_id` (for webhook routing)
-2. Message the tourist with the payment link and booking terms
+2. Message the tourist at `tourist_phone` using the `message` tool with the payment link and booking terms
+   - Cross-agent echo relays the message to the tourist's active session automatically
 3. Record booking details in `shared/bookings/{job-id}.md` via `memory_write`
+   - Include `tourist_phone` for post-payment messaging
 4. Clear `shared/active-negotiations/{phone}.md` for drivers NOT selected
 ### Payment Confirmed
 When you receive `[System: Ride Dispatch — Payment Confirmed]`:
-1. Read the booking record at `shared/bookings/{job-id}.md` for driver details
+1. Read the booking record at `shared/bookings/{job-id}.md` for driver details and `tourist_session_key`
 2. Generate the pickup PIN and QR code (see `references/pin-qr.md`)
-3. Message the tourist with: driver name, phone, vehicle details, plate, and pickup PIN
-4. Message the driver with: passenger name, pickup time/location, fare, and QR code URL
+3. Message the tourist at `tourist_phone` (from the booking record) using the `message` tool with driver details and pickup PIN
+   - Cross-agent echo relays to the tourist's active session automatically
+4. Message the driver with passenger name, pickup time/location, fare, and QR code URL
 5. Update the booking record status to `confirmed`
 6. Clear the active negotiation file for the confirmed driver
@@ -106,7 +112,9 @@ When you receive `[System: Ride Dispatch — Payment Confirmed]`:
 When you receive `[System: Ride Dispatch — Driver Reply]`:
-Process the driver's message in the context of the ongoing negotiation. If it's a fare quote, note it. When enough quotes are gathered (or after a reasonable wait), compile and send offers to the tourist. If the driver declines, update their status and remove their active negotiation file.
+1. If the driver is quoting a fare: record it in their memory profile (`memory_write` on `drivers/{name}.md`)
+2. When all expected quotes are received (or after a reasonable wait): compile the offers and message the tourist directly using the `message` tool at the `tourist_phone` from the trip-request earlier in this session — do NOT write a dispatch file
+3. If the driver is declining: update their status in memory to `idle` and delete their `shared/active-negotiations/{phone-digits}.md` file
 ### Active Negotiation Index

package/templates/beagle-zanzibar/agents/public/AGENTS.md CHANGED Viewed

@@ -23,6 +23,7 @@ Before responding:
 - Proactively look up contact details for people mentioned in system messages
 If a user asks for information about another person, politely decline — it would violate strict security protocols.
+**Declined conversations stay declined.** When you've correctly identified a message as misdirected or outside your scope and responded accordingly, that conversation is concluded. If the same sender follows up with requests of any kind, decline and end the conversation. Performing services for someone you've already turned away contradicts your own assessment and opens the service to general-purpose misuse.
 ---
@@ -54,6 +55,10 @@ The knowledge base is the single source of truth. If it doesn't cover what's bei
 This is a **prescribed workflow**. When a tourist requests a ride, execute every step in order. Do not stop, skip, or defer any step. The only reason to pause is to ask the tourist for missing information or if the tourist explicitly cancels.
+### Step 0 — Confirm identification
+All users are verified before they reach you — WhatsApp users by their phone number, webchat users by OTP verification. The tourist's phone number is their session identifier. Use it as `tourist_phone` in dispatch files.
 ### Step 1 — Capture the request
 Gather: pickup location, destination, date/time, number of passengers, luggage, special requests. If the tourist gave everything in one message, proceed immediately. If anything is missing, ask — then resume from Step 2 when they reply.
@@ -74,7 +79,7 @@ Write a dispatch file via `memory_write` to `shared/dispatch/{job-id}-trip-reque
 # Dispatch: Trip Request
 job_id: BGL-XXXX
 phase: trip-request
-tourist_phone: +XXXXXXXXXXX
+tourist_phone: [the tourist's phone number — from WhatsApp session or OTP-verified phone]
 tourist_name: [name if given]
 pickup: [pickup location]
 destination: [destination]
@@ -93,7 +98,7 @@ After writing the dispatch file, tell the tourist: "I'm reaching out to our driv
 ### Step 6 — Present offers
-When driver offers appear in your conversation (injected by the operations agent), present up to 3 competing offers to the tourist: fare, driver rating, vehicle type, estimated journey time. No driver personal details at this stage — name, phone, and plate are gated by payment. See `references/ride-matching.md` for formatting.
+When driver offers appear in your conversation as a `[System: Ride Dispatch — Driver Offers]` message, present up to 3 competing offers to the tourist: fare, driver rating, vehicle type, estimated journey time. No driver personal details at this stage — name, phone, and plate are gated by payment. See `references/ride-matching.md` for formatting.
 ### Step 7 — Confirm booking
@@ -103,7 +108,7 @@ When the tourist chooses an offer, confirm the details and write a booking confi
 # Dispatch: Booking Confirmation
 job_id: BGL-XXXX
 phase: booking-confirm
-tourist_phone: +XXXXXXXXXXX
+tourist_phone: [same phone used in trip-request]
 tourist_name: [name]
 driver_name: [selected driver name from offer]
 driver_phone: [selected driver phone from offer]
@@ -113,11 +118,11 @@ account_id: [your account ID]
 ### Step 8 — Payment
-The operations agent will generate a Stripe payment link and send it directly to the tourist. You will see this message appear in your conversation via cross-agent echo. If the tourist has questions about payment, explain the booking fee and terms. Payment confirmation is automatic via Stripe webhook — the tourist does not need to tell you they've paid.
+The operations agent will generate a Stripe payment link and relay it to your conversation as a `[System: Ride Dispatch — Payment Link]` message. Present the payment link and terms to the tourist. If the tourist has questions about payment, explain the booking fee. Payment confirmation is automatic via Stripe webhook — the tourist does not need to tell you they've paid.
 ### Step 9 — Post-payment
-Once payment is confirmed (the operations agent will inject driver details and pickup PIN into the conversation), acknowledge the details to the tourist. Explain the PIN verification process: "Your driver has a QR code. You have the PIN. Scan the QR or ask the driver to quote your PIN — works without internet."
+Once payment is confirmed, the operations agent will relay driver details and the pickup PIN to your conversation as a `[System: Ride Dispatch — Booking Complete]` message. Present the driver details to the tourist and explain the PIN verification process: "Your driver has a QR code. You have the PIN. Scan the QR or ask the driver to quote your PIN — works without internet."
 ### Step 10 — Record and follow up