march-cli 0.1.30 → 0.1.32

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "march-cli",
-  "version": "0.1.30",
+  "version": "0.1.32",
   "description": "March CLI — terminal-native coding agent with context reconstruction",
   "type": "module",
   "main": "./src/main.mjs",

package/src/cli/tui/markdown-renderer.mjs

@@ -113,9 +113,9 @@ function renderTable(token, lines, width) {
   shrinkColumns(widths, Math.max(1, width - borderWidth - paddingWidth));
 
   lines.push(formatTableBorder(widths, "┌", "┬", "┐"));
-  lines.push(formatTableRow(cells[0], widths, true));
+  lines.push(...formatTableRow(cells[0], widths, true));
   lines.push(formatTableBorder(widths, "├", "┼", "┤"));
-  for (const row of cells.slice(1)) lines.push(formatTableRow(row, widths, false));
+  for (const row of cells.slice(1)) lines.push(...formatTableRow(row, widths, false));
   lines.push(formatTableBorder(widths, "└", "┴", "┘"));
 }
 
@@ -200,12 +200,18 @@ function plainInline(tokens) {
 }
 
 function formatTableRow(row, widths, header) {
-  const cells = widths.map((width, i) => {
-    const text = truncateCell(row[i] ?? "", width);
-    const padded = text + " ".repeat(Math.max(0, width - visibleWidth(text)));
-    return ` ${header ? bold(padded) : padded} `;
-  });
-  return `${brightBlack("│")}${cells.join(brightBlack("│"))}${brightBlack("│")}`;
+  const wrappedCells = widths.map((width, i) => wrapTableCell(row[i] ?? "", width));
+  const height = Math.max(...wrappedCells.map((cell) => cell.length));
+  const visualRows = [];
+  for (let lineIndex = 0; lineIndex < height; lineIndex += 1) {
+    const cells = widths.map((width, i) => {
+      const text = wrappedCells[i][lineIndex] ?? "";
+      const padded = text + " ".repeat(Math.max(0, width - visibleWidth(text)));
+      return ` ${header ? bold(padded) : padded} `;
+    });
+    visualRows.push(`${brightBlack("│")}${cells.join(brightBlack("│"))}${brightBlack("│")}`);
+  }
+  return visualRows;
 }
 
 function formatTableBorder(widths, left, join, right) {
@@ -218,22 +224,30 @@ function shrinkColumns(widths, maxTotal) {
     widths[index] -= 1;
   }
 }
-
-function truncateCell(text, width) {
-  const chars = [];
-  const sourceChars = Array.from(text);
-  let used = 0;
-  for (const ch of sourceChars) {
-    const w = visibleWidth(ch);
-    if (used + w > width) break;
-    chars.push(ch);
-    used += w;
-  }
-  if (chars.length < sourceChars.length && width > 1) {
-    while (chars.length && used + 1 > width) used -= visibleWidth(chars.pop());
-    return `${chars.join("")}…`;
+function wrapTableCell(text, width) {
+  const lines = [];
+  let current = "";
+  let currentWidth = 0;
+  for (const ch of String(text ?? "")) {
+    if (ch === "\n") {
+      lines.push(current);
+      current = "";
+      currentWidth = 0;
+      continue;
+    }
+    const charWidth = visibleWidth(ch);
+    if (currentWidth + charWidth > width && currentWidth > 0) {
+      lines.push(current.trimEnd());
+      current = "";
+      currentWidth = 0;
+      if (/\s/.test(ch)) continue;
+    }
+    if (!current && /\s/.test(ch)) continue;
+    current += ch;
+    currentWidth += charWidth;
   }
-  return chars.join("");
+  lines.push(current);
+  return lines;
 }
 
 function renderPlainMarkdownFallback(markdown, width) {

package/src/context/system-core/base.md

@@ -5,6 +5,7 @@ The user primarily asks for software engineering work: fixing bugs, adding behav
 
 <communication_contract>
 - Be concise and direct. Match the response shape to the task; simple questions get simple answers.
+- Keep responses honest, restrained, and professional. Do not flatter, praise performatively, exaggerate approval, or default to agreeing with the user.
 - Assume users may not see tool calls. Before the first tool call, say in one sentence what you are about to do. While working, give brief updates when you find something important, change direction, or hit a blocker.
 - For multi-step work, checkpoint after meaningful milestones: what changed, what was verified, and what remains.
 - Don't narrate hidden reasoning. State decisions, results, and relevant next steps.
@@ -18,6 +19,7 @@ The user primarily asks for software engineering work: fixing bugs, adding behav
 - Distinguish the proposed solution from the underlying problem; restate the problem before accepting the solution when the user brings a design or implementation idea.
 - Surface assumptions and ambiguity before acting. If intent, constraints, or code organization are unclear, ask or state the uncertainty instead of guessing.
 - Challenge weak, over-engineered, or mis-scoped proposals directly and offer 1-2 concrete alternatives.
+- If the user is mistaken, the logic is unclear, or information is insufficient, say so plainly with a brief reason, then offer facts, analysis, or actionable next steps.
 - Ask one focused question at a time; when useful, provide 2-4 distinct options rather than open-ended questionnaires.
 - Keep context use bounded. If the task is sprawling or the conversation is losing state, summarize and restart the plan instead of pushing forward blindly.
 - Do not force discussion when the request is already clear; summarize the decision and move toward the appropriate next step.
@@ -95,8 +97,10 @@ The user primarily asks for software engineering work: fixing bugs, adding behav
 - A recall hint's description may record key operational constraints, including when the full memory must be opened; factor those constraints into relevance before acting.
 - If a recall hint may help the current task, use memory_open(id) to read the full memory before relying on it. Ignore hints that are clearly unrelated or too low-value for the task.
 - Use memory_search(query) for full-text search across all memories.
-- To edit an existing memory, use memory_open(id) to get its path, then edit_file with mode="patch" for targeted edits.
-- Use memory_save() to create memories or update whole fields. Before creating a new memory, first search/open related memories and merge updates into an existing memory when they share the same topic, project, or decision thread; prefer modifying the existing memory file over creating a scattered new one. Tags are the primary retrieval key for future recall. Prefer lowercase kebab-case tags like 'march-cli', 'tooling', 'permissions'.
+- To edit an existing memory's body, use memory_open(id) to get its path, then edit_file with mode="patch" for targeted edits.
+- Memory identity is the `id`; local Markdown filenames are id-based storage paths and do not carry title meaning. The user-visible recall/list title comes from frontmatter `name`, not from the filename.
+- When renaming or re-describing an existing memory, update the memory metadata fields (`name`, `description`, `tags`) as metadata, not only the Markdown body heading. Already-injected recall hints in the current prompt may remain stale until the next recall.
+- Use memory_save() to create memories or update whole metadata fields on an existing memory. Before creating a new memory, first search/open related memories and merge updates into an existing memory when they share the same topic, project, or decision thread; prefer modifying the existing memory file over creating a scattered new one. Tags are the primary retrieval key for future recall. Prefer lowercase-kebab-case tags like 'march-cli', 'tooling', 'permissions'.
 - When learning multiple related external workflows or skills, maintain memory as an evolving domain library: start with the specific source name when only one item exists, then rename and rewrite the memory title/description as the scope grows; merge new related learnings into the same memory, preserving each source's unique traits while distilling reusable principles.
 - Distinguish "migrating a Skill to memory" from "learning a Skill": migration preserves the complete Skill folder under memory_root/skills/ and creates a memory entry as its index; that memory should describe what the Skill is for and reference the copied Skill folder path so future recall knows how to use it. Learning only reads and internalizes the Skill's methods, scenarios, and principles into ordinary memory without copying source files. Infer the action from the user's wording, and ask when ambiguous.
 - Unlike recall blocks, this system-core center is always visible in every model call. Only update the center for instructions that must always be followed; use memory for contextual, project-specific, or recall-dependent knowledge.

package/src/memory/markdown/markdown-format.mjs

@@ -55,15 +55,6 @@ export function generateMemoryId() {
   return `mem_${randomUUID().replace(/-/g, "").slice(0, 16)}`;
 }
 
-export function slugify(value) {
-  return String(value ?? "memory")
-    .trim()
-    .toLowerCase()
-    .replace(/[^a-z0-9\u4e00-\u9fff]+/g, "-")
-    .replace(/^-+|-+$/g, "")
-    .slice(0, 80) || "memory";
-}
-
 export function walkMarkdownFiles(root) {
   const out = [];
   if (!existsSync(root)) return out;

package/src/memory/markdown-store.mjs

@@ -8,7 +8,6 @@ import {
   normalizeText,
   parseMemoryMarkdown,
   quoteFtsTerm,
-  slugify,
   walkMarkdownFiles,
 } from "./markdown/markdown-format.mjs";
 import { scoreEntry, toHint } from "./markdown/markdown-recall.mjs";
@@ -176,7 +175,7 @@ export class MarkdownMemoryStore {
     if (!nextDescription) throw new Error("description is required");
     if (!existing && body == null) throw new Error("body is required");
     const nextBody = body ?? (existing ? parseMemoryMarkdown(readFileSync(existing.path, "utf8")).body : "");
-    const nextPath = existing?.path ?? this.#newMemoryPath(now, nextName);
+    const nextPath = existing?.path ?? this.#newMemoryPath(now, nextId);
     mkdirSync(dirname(nextPath), { recursive: true });
     const content = formatMemoryMarkdown({
       frontmatter: {
@@ -248,11 +247,11 @@ export class MarkdownMemoryStore {
     }
   }
 
-  #newMemoryPath(isoDate, name) {
+  #newMemoryPath(isoDate, id) {
     const date = isoDate.slice(0, 10);
     const [year, month, day] = date.split("-");
     const week = `week${Math.ceil(Number(day) / 7)}`;
-    return join(this.root, year, month, week, `${date}-${slugify(name)}.md`);
+    return join(this.root, year, month, week, `${date}-${id}.md`);
   }
 
   #resolveMemoryPath(raw) {

package/src/memory/markdown-tools.mjs

@@ -70,7 +70,7 @@ export function createMarkdownMemoryTools(store, { remoteSources = [] } = {}) {
       name: "memory_save",
       label: "Memory Save",
       description:
-        "Create a Markdown memory or update whole fields on an existing memory. For targeted edits to an existing memory body or frontmatter, use memory_open to get the path, then edit_file. Before creating a new memory, merge related updates into an existing memory when they share the same topic or decision thread. New memories require name, description, body, and at least one tag because recall hints only use tags. When updating by id, omitted fields keep their existing values; passing tags replaces the full tag list.",
+        "Create a Markdown memory or update whole fields on an existing memory. Local memory filenames are id-based storage paths; frontmatter name is the user-visible title. For targeted edits to an existing memory body or frontmatter, use memory_open to get the path, then edit_file. Before creating a new memory, merge related updates into an existing memory when they share the same topic or decision thread. New memories require name, description, body, and at least one tag because recall hints only use tags. When updating by id, omitted fields keep their existing values; passing tags replaces the full tag list.",
       parameters: Type.Object({
         id: Type.Optional(Type.String({ description: "Existing memory id to update. Omit to create a new memory." })),
         name: Type.Optional(Type.String({ description: "Memory name. Required when creating." })),