@c4t4/heyamigo 0.7.3 → 0.7.5

package/dist/queue/async-tasks.js

@@ -70,7 +70,7 @@ export function reloadAsyncSystemPrompt() {
 }
 function buildPrompt(task) {
     const lines = [
-        `You are running a BACKGROUND TASK for the owner. The chat already got your ack reply. Your only job now is to do the work and output the final message to send them.`,
+        `You are a BACKGROUND WORKER doing a delayed chat reply. The chat already got an ack ("on it, will report back"). Now you do the work, and your output IS the follow-up chat reply — the full answer the owner is waiting for.`,
         ``,
         `TASK:`,
         task.description,
@@ -80,15 +80,32 @@ function buildPrompt(task) {
         ``,
         `Sender: ${task.senderName ?? task.senderNumber}`,
         ``,
-        `RULES:`,
-        `- Stay fully in character (personality file). This is not customer service.`,
-        `- Do the real work. Use tools (browser, etc.) as needed.`,
-        `- When done, output ONLY the message to send the user. No preamble, no "here's what I found:" framing unless that's the message itself.`,
-        `- Do NOT emit any [DIGEST:...], [JOURNAL:...], [ASYNC:...], or other markers. This is the final output.`,
-        `- Start the message with a short reference to what you were working on so the user knows which task this is about (e.g. "About the TikTok scrape: ..."). They may have asked for multiple things.`,
-        `- If the task is impossible or the tools failed, say so honestly and briefly. Don't fabricate.`,
+        `HOW TO OUTPUT:`,
+        `- Write the full answer as a natural chat reply. Same voice, same style as the main chat Claude. What the owner would have gotten if you'd answered inline, just delayed.`,
+        `- Open with a short "about the X you asked about..." reference so the owner knows which task this is (they may have asked for several). One sentence, then the content.`,
+        `- Concrete findings, no filler. Numbers, names, dates. If you found 10 creators, list them — don't say "multiple creators".`,
+        `- If the task failed or hit a wall (login wall, empty page, bot-detection, timeout), say so honestly and briefly. Don't fabricate.`,
         ``,
-        `Output the final user-facing message now.`,
+        `OPTIONAL MARKERS (at the END of your output, same pattern as main chat):`,
+        `- [JOURNAL:<slug> — <one-line finding>] for any finding that belongs in an active journal. These run IN ADDITION to your chat reply — they file structured entries in journals/<slug>/entries.jsonl for future reference, dedup, and cross-session memory. Use existing slugs only (check [Journals: active] in your preamble). ONE marker per finding.`,
+        `- [JOURNAL-NEW:<slug> — <one-line purpose>] if the task clearly deserves a new journal that doesn't exist yet. Conservative — only when the topic is a recurring tracking surface, not a one-off.`,
+        `- [DIGEST: <one-line reason>] if you learned something durable about the owner or chat that should update the profile/brief.`,
+        ``,
+        `CONSTRAINTS:`,
+        `- Do NOT emit [ASYNC:...]. No recursive delegation.`,
+        `- Markers are bonus persistence, not a substitute for the chat reply. Always write the chat reply first.`,
+        `- Stay fully in character (personality).`,
+        ``,
+        `EXAMPLE for an IG scrape of rivoara_official (with journal tracking):`,
+        `About the @rivoara_official check: bio is "Premium shower filter for HT aftercare". Last 3 posts: day-5 routine walkthrough, filter-science deep dive, Turkey clinic partnership announcement. Grid is clean, ~200 followers. Pattern: aftercare positioning is the lead, product is secondary.`,
+        ``,
+        `[JOURNAL:rivoara-spy — IG bio: "Premium shower filter for HT aftercare"]`,
+        `[JOURNAL:rivoara-spy — IG recent posts: day-5 routine, filter science, Turkey clinic partnership]`,
+        ``,
+        `EXAMPLE for a failure:`,
+        `About the @rivoara_official check: Instagram threw a login wall after the first navigation. Can't read the bio or posts without auth. The VNC Chrome session looks expired — worth re-logging.`,
+        ``,
+        `Do the work now. Write the reply. Markers optional at the end.`,
     ];
     return lines.join('\n');
 }
@@ -161,24 +178,100 @@ async function runTask(task) {
         });
         return;
     }
-    // Strip any accidental trailing markers Claude emitted despite instructions.
-    // Import lazily to avoid an import cycle (digest-flag already stands alone,
-    // but being explicit here keeps this module independent).
+    // Parse markers from the worker's output and route them through the same
+    // handlers the main chat uses. The async worker's job is to emit findings
+    // as markers; clean pre-marker text is only sent to chat when short (a
+    // failure explanation or tight ack) or when no markers fired at all.
     const { extractFlags } = await import('../memory/digest-flag.js');
-    const { clean } = extractFlags(output);
-    if (!clean.trim()) {
-        logger.warn({ id: task.id, jid: task.jid }, 'async task produced empty output after flag strip');
-        return;
+    const { clean, digest, journals, journalCreates } = extractFlags(output);
+    // Journal creates run first so an entry flagged in the same output against
+    // a new slug lands correctly.
+    const { appendEntry, createJournal, getJournal, isValidSlug } = await import('../memory/journals.js');
+    for (const op of journalCreates) {
+        if (!isValidSlug(op.slug)) {
+            logger.warn({ op, id: task.id }, 'async JOURNAL-NEW: invalid slug, dropped');
+            continue;
+        }
+        if (getJournal(op.slug))
+            continue;
+        try {
+            createJournal({
+                slug: op.slug,
+                name: titleCaseSlug(op.slug),
+                purpose: op.purpose,
+            });
+            logger.info({ slug: op.slug, id: task.id }, 'journal created via async marker');
+        }
+        catch (err) {
+            logger.error({ err, op, id: task.id }, 'async JOURNAL-NEW failed');
+        }
+    }
+    let appendedCount = 0;
+    for (const j of journals) {
+        const ok = appendEntry(j.slug, {
+            source: 'async',
+            jid: task.jid,
+            senderNumber: task.senderNumber,
+            note: j.note,
+        });
+        if (ok)
+            appendedCount++;
+        else {
+            logger.warn({ slug: j.slug, id: task.id }, 'async JOURNAL marker pointed at unknown slug, dropped');
+        }
     }
-    const sent = await initiate({ jid: task.jid, text: clean });
+    if (digest) {
+        const { scheduleDigest } = await import('../memory/scheduler.js');
+        scheduleDigest({
+            jid: task.jid,
+            number: task.senderNumber,
+            reason: digest,
+        });
+    }
+    // The clean (marker-stripped) text IS the chat reply. Always send it when
+    // present. Markers fired in parallel above are bonus persistence —
+    // journal entries, digests, new journal creation — not a substitute for
+    // the chat reply.
+    const chatText = clean.trim();
+    const anyMarkerFired = appendedCount > 0 || journalCreates.length > 0 || digest !== null;
+    if (chatText.length > 0) {
+        await initiate({ jid: task.jid, text: chatText });
+    }
+    else if (anyMarkerFired) {
+        // Worker emitted only markers, no chat text. That's contract-breaking
+        // (chat reply is the primary output) but recoverable — send a short
+        // completion note so the owner isn't left with silence.
+        const bits = [];
+        if (appendedCount > 0) {
+            bits.push(`${appendedCount} journal ${appendedCount === 1 ? 'entry' : 'entries'}`);
+        }
+        if (journalCreates.length > 0) {
+            bits.push(`${journalCreates.length} journal${journalCreates.length === 1 ? '' : 's'} created`);
+        }
+        if (digest)
+            bits.push('digest scheduled');
+        await initiate({
+            jid: task.jid,
+            text: `Done. ${bits.join(', ')}.`,
+        });
+    }
+    // Else: no chat text AND no markers — worker produced nothing. Log only.
     logger.info({
         id: task.id,
         jid: task.jid,
-        sent,
         elapsed: elapsedLog(),
-        chars: clean.length,
+        appended: appendedCount,
+        createdJournals: journalCreates.length,
+        digestFired: !!digest,
+        chatSent: chatText.length,
     }, 'async task completed');
 }
+function titleCaseSlug(slug) {
+    return slug
+        .split('-')
+        .map((p) => (p ? p[0].toUpperCase() + p.slice(1) : p))
+        .join(' ');
+}
 function truncate(s, n) {
     return s.length > n ? s.slice(0, n - 1) + '…' : s;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4t4/heyamigo",
-  "version": "0.7.3",
+  "version": "0.7.5",
   "description": "WhatsApp AI bot powered by Claude with long-term memory, browser control, and role-based access",
   "type": "module",
   "main": "dist/index.js",