@blockrun/franklin 3.15.75 → 3.15.77

package/dist/agent/context.js

@@ -27,6 +27,7 @@ When a user asks for a current price, today's news, or any live-world state, **c
 
 # System
 - All text you output outside of tool use is displayed to the user. Use markdown for formatting.
+- **Markdown tables**: use plain ASCII pipe \`|\` for every column separator, not the box-drawing \`│\` (U+2502). Mixing \`│\` data rows with \`|\` separator rows produces a broken table that no renderer parses correctly. Same rule for the separator: use \`---\`, not \`━━━\` or other Unicode dashes. If you can't draw a clean table in plain ASCII, emit a bullet list instead.
 - Tools are your hands. You MUST use tools to take action — do not describe what you would do without doing it. Never end your turn with a promise of future action — execute it now. Every response should either (a) contain tool calls that make progress, or (b) deliver a final result to the user.
 - You can call multiple tools in a single response. If you intend to call multiple tools and there are no dependencies between them, make ALL independent tool calls in parallel. This is critical for performance. However, if tool calls depend on previous results, run them sequentially — do NOT use placeholders or guess dependent values.
 

package/dist/agent/llm.d.ts

@@ -52,6 +52,23 @@ export interface LLMClientOptions {
     chain: Chain;
     debug?: boolean;
 }
+/**
+ * Replace Unicode box-drawing characters with their ASCII equivalents.
+ *
+ * Models occasionally emit U+2502 (`│`) and U+2500 (`─`) in markdown tables
+ * — sometimes mixed with ASCII `|` / `-` in the same table. No markdown
+ * renderer parses the mix, and the "table" displays as run-on text. Verified
+ * 2026-05-06 in a real session: opus-4.7 emitted a CRCL fundamentals table
+ * with `│` data rows and `|` separator, ignoring the system-prompt nudge
+ * added in 3.15.76. The unconditional swap fixes the rendering at the
+ * streaming boundary so every downstream surface (user terminal, conversation
+ * history, audit log) gets the corrected version.
+ *
+ * Trade: the rare case where a user genuinely wants box-drawing in output
+ * (e.g. asking what U+2502 looks like) loses fidelity. Acceptable — that
+ * case has no real-world frequency, the broken-tables case has weekly.
+ */
+export declare function sanitizeTableUnicode(s: string): string;
 /**
  * Extract the most human-readable message from an error body.
  * Some gateways wrap provider errors multiple times, e.g.

package/dist/agent/llm.js

@@ -28,6 +28,27 @@ function parseTimeoutEnv(name) {
     const parsed = raw ? Number.parseInt(raw, 10) : NaN;
     return Number.isFinite(parsed) && parsed >= 0 ? parsed : null;
 }
+/**
+ * Replace Unicode box-drawing characters with their ASCII equivalents.
+ *
+ * Models occasionally emit U+2502 (`│`) and U+2500 (`─`) in markdown tables
+ * — sometimes mixed with ASCII `|` / `-` in the same table. No markdown
+ * renderer parses the mix, and the "table" displays as run-on text. Verified
+ * 2026-05-06 in a real session: opus-4.7 emitted a CRCL fundamentals table
+ * with `│` data rows and `|` separator, ignoring the system-prompt nudge
+ * added in 3.15.76. The unconditional swap fixes the rendering at the
+ * streaming boundary so every downstream surface (user terminal, conversation
+ * history, audit log) gets the corrected version.
+ *
+ * Trade: the rare case where a user genuinely wants box-drawing in output
+ * (e.g. asking what U+2502 looks like) loses fidelity. Acceptable — that
+ * case has no real-world frequency, the broken-tables case has weekly.
+ */
+export function sanitizeTableUnicode(s) {
+    if (!s)
+        return s;
+    return s.replace(/│/g, '|').replace(/─/g, '-');
+}
 function getModelRequestTimeoutMs() {
     // 180s budget for *time-to-headers* (the gateway flushes SSE headers only
     // once the upstream model emits its first token). Reasoning-class models
@@ -545,6 +566,15 @@ export class ModelClient {
         const appendText = (text) => {
             if (!text)
                 return;
+            // Sanitize Unicode box-drawing chars to ASCII pipe/dash. 3.15.76's
+            // system-prompt nudge asked models not to emit U+2502 / U+2500 in
+            // tables — opus-4.7 ignored it 2026-05-06, shipped a CRCL analysis
+            // table where data rows used `│` and the separator used `|`. No
+            // markdown renderer parses that mix; the table displayed as run-on
+            // text. Normalize at the streaming boundary so the user, the model
+            // history (next turn the model sees its own corrected output), and
+            // the audit log all match.
+            text = sanitizeTableUnicode(text);
             currentText += text;
             if (textEmission.mode === 'undecided') {
                 const trimmed = currentText.trimStart();

package/dist/stats/audit.js

@@ -105,6 +105,12 @@ export function readAudit() {
         return [];
     }
 }
+/**
+ * Regex: SCREAMING-CASE bracketed label like `[SYSTEM NOTE]`,
+ * `[FRANKLIN HARNESS PREFETCH]`, `[GROUNDING CHECK FAILED]`. Used to detect
+ * harness-injected text that masks the real user prompt in audit forensics.
+ */
+const SYNTHETIC_LABEL = /\[[A-Z][A-Z _-]+\]/;
 /** Pull the last user message from a Dialogue history, flatten, and strip newlines. */
 export function extractLastUserPrompt(history) {
     for (let i = history.length - 1; i >= 0; i--) {
@@ -122,9 +128,19 @@ export function extractLastUserPrompt(history) {
         // "[FRANKLIN HARNESS PREFETCH] CRCL price..." and 18 showed
         // "[GROUNDING CHECK FAILED] ..." instead of the user's actual question.
         // Skip any message whose first non-whitespace block is a SCREAMING-CASE
-        // bracketed label and keep walking back to the real user turn.
-        if (/^\[[A-Z][A-Z _-]+\]/.test(cleaned))
+        // bracketed label.
+        if (new RegExp('^' + SYNTHETIC_LABEL.source).test(cleaned))
             continue;
+        // 3.15.76: also strip TRAILING synthetic labels. Newer post-response
+        // evaluators append `[SYSTEM NOTE] The user is correcting you. Your
+        // previous response was wrong...` to the user's real text within the
+        // SAME message — so the message doesn't start with the bracket but the
+        // audit field still ends up half-real, half-synthetic. The bracket is
+        // preceded by whitespace + at least one real character, so trim from
+        // the first such occurrence.
+        const trailing = cleaned.match(new RegExp('^(.+?)\\s' + SYNTHETIC_LABEL.source));
+        if (trailing && trailing[1].trim())
+            return trailing[1].trim();
         return cleaned;
     }
     return undefined;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@blockrun/franklin",
-  "version": "3.15.75",
+  "version": "3.15.77",
   "description": "Franklin — The AI agent with a wallet. Spends USDC autonomously to get real work done. Pay per action, no subscriptions.",
   "type": "module",
   "exports": {