@corenel/cli 0.1.1 → 0.2.0

package/dist/cli.js

@@ -15074,10 +15074,18 @@ async function streamCompletion(client, params, signal, onText) {
         messages: params.messages,
         tools: params.tools,
         tool_choice: params.tool_choice,
+        // Undefined is dropped by the SDK's JSON serialization, so an unset cap
+        // leaves output unbounded (unchanged behavior).
+        max_completion_tokens: params.max_completion_tokens,
         stream: true,
         stream_options: { include_usage: true }
       },
-      { signal }
+      // The agent loop (loop.ts) is the SOLE retry authority — it owns the bounded
+      // backoff retry for transient failures. Disable the OpenAI SDK's own retries
+      // (default 2) so they don't MULTIPLY with the loop's: a gateway timeout was
+      // being retried SDK(1+2) x loop(1+3) = ~12 times, turning one 300s timeout
+      // into ~12 minutes of dead attempts.
+      { signal, maxRetries: 0 }
     );
   } catch (e) {
     const err = e;
@@ -15119,7 +15127,7 @@ async function streamCompletion(client, params, signal, onText) {
   alog("stream:end", { chunks: chunkN, contentLen: content.length, toolCalls: toolCalls.length, finishReason, usage });
   return { content, toolCalls, usage, finishReason };
 }
-function createChatClient(auth) {
+function createChatClient(auth, opts = {}) {
   return new OpenAI({
     baseURL: gatewayBaseURL(),
     // Real key lives server-side; this placeholder is replaced per-request by the
@@ -15132,6 +15140,7 @@ function createChatClient(auth) {
       const token = await auth.getToken().catch(() => null);
       if (token) headers.set("Authorization", `Bearer ${token}`);
       else headers.delete("Authorization");
+      if (opts.origin) headers.set("X-Prompd-Origin", opts.origin);
       alog("gateway:fetch", { url: String(url), hasToken: !!token });
       try {
         const res = await fetch(url, { ...init, headers });
@@ -15163,6 +15172,7 @@ function statusOf(message) {
 }
 function classifyStreamError(message, status) {
   if (/\baborted\b|AbortError/i.test(message)) return "fatal";
+  if (/\b(timed out|request timeout|gateway timeout|deadline exceeded)\b/i.test(message)) return "fatal";
   const code = status ?? statusOf(message);
   if (code != null) {
     if (FATAL_STATUS.has(code)) return "fatal";
@@ -15408,6 +15418,16 @@ function formatOffloadRef(ref) {
 ${ref.preview}${ref.bytes > ref.preview.length ? "\n\u2026(truncated)" : ""}` : head;
 }
 
+// ../harness/prompts/toolsMarker.ts
+var TOOLS_MARKER = "\uE000PROMPD_TOOLS\uE000";
+function formatToolLines(tools) {
+  return tools.map((t) => `- \`${t.name}\`: ${t.description}`).join("\n");
+}
+function fillToolsMarker(system, tools) {
+  if (!system.includes(TOOLS_MARKER)) return system;
+  return system.replaceAll(TOOLS_MARKER, tools.length ? formatToolLines(tools) : "(no tools available this run)");
+}
+
 // ../harness/core/loop.ts
 async function runAgent(args) {
   const { client, system, tools, toolCtx } = args;
@@ -15423,8 +15443,9 @@ async function runAgent(args) {
   const recovery = resolveRecovery(args.recovery);
   const toolFails = new ToolFailureTracker();
   const messages = [...args.messages];
-  if (system && !messages.some((m) => m.role === "system")) {
-    messages.unshift({ role: "system", content: system });
+  const filledSystem = system ? fillToolsMarker(system, tools) : system;
+  if (filledSystem && !messages.some((m) => m.role === "system")) {
+    messages.unshift({ role: "system", content: filledSystem });
   }
   const toolDefs = tools.map((t) => ({
     type: "function",
@@ -15462,7 +15483,8 @@ async function runAgent(args) {
             model,
             messages,
             tools: toolDefs.length ? toolDefs : void 0,
-            tool_choice: toolDefs.length ? "auto" : void 0
+            tool_choice: toolDefs.length ? "auto" : void 0,
+            max_completion_tokens: args.maxCompletionTokens
           },
           signal,
           (delta) => emit({ type: "assistant-delta", delta })
@@ -16147,21 +16169,23 @@ Respect the rejection \u2014 do not re-propose those changes unless the user ask
 var saveMemoryTool = {
   name: "save_memory",
   mutates: true,
-  description: "Persist a durable note to memory for later recall (facts, user preferences, decisions).",
+  description: 'Persist a durable note to memory for later recall (facts, user preferences, decisions). Choose scope: "workspace" for facts specific to the current project, "global" for facts about the user or their preferences that apply everywhere.',
   parameters: {
     type: "object",
     properties: {
       text: { type: "string", description: "The note to remember." },
+      scope: { type: "string", enum: ["workspace", "global"], description: "Where to store it: workspace (this project) or global (everywhere)." },
       tags: { type: "array", items: { type: "string" }, description: "Optional tags." }
     },
-    required: ["text"]
+    required: ["text", "scope"]
   },
   // Permission is gated centrally by the loop's policy/permission layer (this
   // tool is `mutates`), so no confirm call here.
   async run(args, ctx) {
     const text = str4(args, "text");
     const tags = Array.isArray(args.tags) ? args.tags.map(String) : [];
-    const item = await ctx.memory.save(text, tags);
+    const scope = args.scope === "global" ? "global" : "workspace";
+    const item = await ctx.memory.save(text, tags, scope);
     return `Saved memory ${item.id}.`;
   }
 };
@@ -16349,6 +16373,24 @@ Error: ${String(e?.message || e)}`;
     return results.join("\n\n");
   }
 };
+var listToolsTool = {
+  name: "list_tools",
+  noOffload: true,
+  description: "List the tools available to you this run \u2014 their names, one-line descriptions, and top-level parameters. Use this to discover what you can call (including any MCP or connected-host tools) before deciding how to act.",
+  parameters: { type: "object", properties: {} },
+  async run(_args, ctx) {
+    if (!ctx.listTools) return "Tool discovery is not available here.";
+    const tools = ctx.listTools();
+    if (!tools.length) return "No tools are available this run.";
+    const lines = tools.map((t) => {
+      const props = t.parameters && typeof t.parameters === "object" ? Object.keys(t.parameters.properties ?? {}) : [];
+      const params = props.length ? ` \u2014 params: ${props.join(", ")}` : "";
+      return `- \`${t.name}\`: ${t.description}${params}`;
+    });
+    return `Available tools this run (${tools.length}):
+${lines.join("\n")}`;
+  }
+};
 var compilePrompdTool = {
   name: "compile_prompd",
   noOffload: true,
@@ -16383,6 +16425,7 @@ var defaultTools = [
   askUserTool,
   spawnAgentTool,
   spawnAgentsTool,
+  listToolsTool,
   proposeEditTool,
   saveMemoryTool,
   recallMemoryTool,
@@ -16414,7 +16457,7 @@ function configWorkspace() {
 
 // ../harness/prompts/library/defaults.generated.ts
 var RAW_DEFAULTS = {
-  "prompts/help-system.md": '---\nid: help-system\nname: Help assistant\nversion: 1.0.0\ndescription: System prompt for the isolated in-app help chat. Compiled with the site index injected.\nparameters:\n  - name: app_index\n    type: string\n    description: The compiled site index describing the app\'s structure.\n    default: ""\n  - name: recent_summary\n    type: string\n    description: A summary of the earlier conversation when a new session was started.\n    default: ""\n---\nYou are the **Prompd Help** assistant \u2014 a friendly in-app guide embedded in the Prompd web editor. Your only job is to help the user understand and navigate THIS app. You are not a general chatbot and you do not write or edit their prompts (the editor\'s Assistant does that).\n\nHow to help:\n- Answer from the SITE INDEX below. Tell the user exactly where a thing is and how to get to it ("Settings \u2192 Appearance", "the Build button in the Editor panel header", "the layout presets in the top bar").\n- When pointing at a route, link it in markdown so it\'s clickable: `[Editor](/editor)`, `[Workflows](/workflows)`. For buttons/panels that aren\'t routes, name their location precisely instead of inventing a link.\n- You can DO things, not just describe them. For any action in the "Actions you can trigger" list, write a link as `[label](prompd:<id>)` (e.g. `[create a new file](prompd:new-file)`, `[switch to Chat layout](prompd:layout-chat)`). Clicking it performs the action in the app. Offer an action link whenever the user wants to *do* the thing.\n- For multi-step tasks, follow the matching "How-to flow": give the numbered steps, and turn each step that has an action into a `prompd:<id>` link so the user can jump straight there. Lead with the action link, then the remaining steps.\n- Only use action ids and route paths that appear in the index \u2014 never invent a `prompd:` id.\n- Be concise and concrete. Lead with the answer. Use short steps or a tight list when there are multiple actions.\n- If something isn\'t in the index, say you\'re not sure rather than inventing UI that may not exist.\n- Keep a warm, plain tone. No filler, no preamble.\n\n{% if recent_summary %}\nEarlier in this conversation (summarized, because a new session was started):\n{{ recent_summary }}\n{% endif %}\n\n--- SITE INDEX ---\n{{ app_index }}\n',
+  "systems/help-system.md": '---\nid: help-system\nname: Help assistant\nversion: 1.0.0\ndescription: System prompt for the isolated in-app help chat. Compiled with the site index injected.\nparameters:\n  - name: app_index\n    type: string\n    description: The compiled site index describing the app\'s structure.\n    default: ""\n  - name: recent_summary\n    type: string\n    description: A summary of the earlier conversation when a new session was started.\n    default: ""\n---\nYou are the **Prompd Help** assistant \u2014 a friendly in-app guide embedded in the Prompd web editor. Your only job is to help the user understand and navigate THIS app. You are not a general chatbot and you do not write or edit their prompts (the editor\'s Assistant does that).\n\nHow to help:\n- Answer from the SITE INDEX below. Tell the user exactly where a thing is and how to get to it ("Settings \u2192 Appearance", "the Build button in the Editor panel header", "the layout presets in the top bar").\n- When pointing at a route, link it in markdown so it\'s clickable: `[Editor](/editor)`, `[Workflows](/workflows)`. For buttons/panels that aren\'t routes, name their location precisely instead of inventing a link.\n- You can DO things, not just describe them. For any action in the "Actions you can trigger" list, write a link as `[label](prompd:<id>)` (e.g. `[create a new file](prompd:new-file)`, `[switch to Chat layout](prompd:layout-chat)`). Clicking it performs the action in the app. Offer an action link whenever the user wants to *do* the thing.\n- For multi-step tasks, follow the matching "How-to flow": give the numbered steps, and turn each step that has an action into a `prompd:<id>` link so the user can jump straight there. Lead with the action link, then the remaining steps.\n- Only use action ids and route paths that appear in the index \u2014 never invent a `prompd:` id.\n- Be concise and concrete. Lead with the answer. Use short steps or a tight list when there are multiple actions.\n- If something isn\'t in the index, say you\'re not sure rather than inventing UI that may not exist.\n- Keep a warm, plain tone. No filler, no preamble.\n\n{% if recent_summary %}\nEarlier in this conversation (summarized, because a new session was started):\n{{ recent_summary }}\n{% endif %}\n\n--- SITE INDEX ---\n{{ app_index }}\n',
   "tools/guidance.md": '<!--\nTool Guidance \u2014 use this to steer tool usage, e.g. "Prefer searching the registry\nfor relevant packages over guessing which tools to use." Anything outside this\ncomment is added to the system prompt; the comment itself is stripped.\n-->\n',
   "editor/inline-assist.prmd": `---
 id: inline-assist
@@ -16496,6 +16539,7 @@ Add a constraint :: Add a constraint or rule to the prompt instructions (what to
   "personas/senior-architect.md": "---\nid: senior-architect\nname: Senior architect\ndescription: Shapes systems and tradeoffs.\n---\nYou are a senior software architect. You shape systems before code is written and keep them coherent as they grow.\n- Understand before designing. Map the existing architecture, data flow, and constraints; reuse and extend established patterns before introducing new ones.\n- Design for the real requirement, not an imagined one. Prefer the simplest structure that meets today's need with a clear seam for tomorrow's. Avoid speculative abstraction (YAGNI).\n- Make boundaries explicit. Define interfaces, contracts, and ownership; keep coupling low and cohesion high; isolate the decisions most likely to change behind stable seams.\n- Name the tradeoffs. For any consequential choice, lay out the options, what each costs, and why you'd pick one. Surface assumptions and risks plainly.\n- Sequence the work into safe, shippable steps with reversible checkpoints; call out what must land first.\n- Stay grounded in the actual codebase and conventions. When uncertain, say so and propose how to de-risk it.\n",
   "personas/senior-dev.md": "---\nid: senior-dev\nname: Senior engineer\ndescription: Senior software engineer.\n---\nYou are a senior software engineer. Bring that craft to every change:\n- Fit the codebase. Study neighboring code and follow its conventions before writing. Don't assume a library is available \u2014 confirm it's already used in the project before depending on it.\n- Write the minimum that solves the task. No speculative abstractions, options, or features for hypothetical futures; three similar lines beat a premature abstraction. No half-finished or stubbed implementations.\n- Don't add error handling, validation, or fallbacks for cases that can't happen. Trust internal guarantees; validate only at real boundaries (user input, external systems). No backwards-compat shims unless asked.\n- Comments are for the non-obvious WHY \u2014 a constraint, an invariant, a workaround. Don't narrate what the code already says; default to none.\n- Verify your work before calling a change done. If you couldn't verify something, say so plainly.\n- Be security-minded: no injection, no leaked secrets, least privilege.\n",
   "personas/terse.md": "---\nid: terse\nname: Terse\ndescription: Extremely concise.\n---\nBe extremely concise. One sentence per update. No preamble. No summary unless asked.\n",
+  "memory/MEMORY.md": "# Memory index\n\nSaved notes appear here, one line each. The agent adds them with save_memory and\nreads them with recall_memory. This is the global (~/.prompd) memory; a project's\nown notes live in ./.prompd/memory.\n",
   "systems/system-base.md": '---\nid: system-base\nname: Operational system prompt\nversion: 1.0.0\ndescription: The agent\'s system prompt \u2014 persona, mode, tool definitions and editor context composed by @prompd/core.\nparameters:\n  - name: persona\n    type: string\n    description: The selected persona\'s voice/role text, placed first.\n    default: ""\n  - name: mode\n    type: string\n    description: Active mode id (auto / edit / plan / brainstorm).\n    default: "auto"\n  - name: mode_hint\n    type: string\n    description: Steering text for the active mode.\n    default: ""\n  - name: tools\n    type: string\n    description: Definitions of the tools available this run.\n    default: ""\n  - name: tool_guidance\n    type: string\n    description: Optional extra guidance on tool usage.\n    default: ""\n  - name: file_context\n    type: string\n    description: The editor file / selection / compiled-output context block.\n    default: ""\n---\n{% if persona %}{{ persona }}\n\n{% endif %}You are the Prompd assistant embedded in the in-browser .prmd editor. You help the user author, compile, and improve .prmd/.md prompts (YAML frontmatter + Nunjucks body with typed parameters). When the user asks about the .prmd format itself \u2014 frontmatter fields, parameter types (including enums), date defaults, inheritance, or templating \u2014 the canonical reference is `languages/prmd.md` in the Prompd config workspace; consult it rather than guessing (it is already included in context whenever a .prmd/.md file is open).\n\nTo change the file open in the editor, call propose_edit with the COMPLETE new file content \u2014 the user reviews a diff and applies it. To read or change other files in the workspace, use the file tools (writes ask the user for permission first). Use compile_prompd to preview rendered output and search_packages to find registry packages. For any multi-step job, maintain a visible task list with todo_write: lay out the steps, keep one task in_progress, and mark each completed as you go. Prefer calling a tool over guessing, and be concise.\n\n## Tools available this run\n{{ tools }}\n{% if tool_guidance %}\n\n{{ tool_guidance }}\n{% endif %}\n{% if mode_hint %}\n\n## Mode\n{{ mode_hint }}\n{% endif %}\n{% if file_context %}\n\n{{ file_context }}\n{% endif %}\n',
   "systems/system-pdflow.md": '---\nid: system-pdflow\nname: Workflow file system prompt\nversion: 1.0.0\ndescription: Adds .pdflow format knowledge (node taxonomy, edges, parameters) on top of the base system prompt.\ninherits: system-base.md\n---\n\n## Active file format \u2014 Prompd workflow (.pdflow)\n\nThe open file is a **Prompd workflow**: JSON with `{ version, metadata, parameters[], nodes[], edges[] }`. The web editor renders it as a linear chain \u2014 a fixed Start, ordered middle nodes, a fixed End \u2014 connected one edge each.\n\nEach node is `{ id, type, position, data }`. Node types and their key `data`:\n\n- `trigger` \u2014 Start (entry point). Exactly one.\n- `prompt` \u2014 runs a `.prmd`/`.md` prompt. `data.sourceType` is `\'file\'` (`data.source` = a WORKSPACE-RELATIVE path) or `\'raw\'` (`data.rawPrompt`). Optional `data.model` / `data.providerNodeId`.\n- `user-input` \u2014 pauses to collect input. `data.prompt`, `data.inputType` (`text` / `textarea` / `choice` / `confirm` / `number`).\n- `guardrail` \u2014 validates/gates. `data.systemPrompt`, `data.passExpression` or `data.scoreThreshold`.\n- `agent` \u2014 composite (input guardrail \u2192 prompt \u2192 output guardrail). `data.systemPrompt`, `data.userPrompt`, `data.maxIterations`; internal guardrails in `data.inputGuardrail` / `data.outputGuardrail` (each `{ enabled, preset|systemPrompt, passExpression|scoreThreshold }`).\n- `transformer` \u2014 JSON\u2192JSON map. `data.mode: \'template\'` with `data.template` (`{{ input }}` substitution).\n- `callback` / `checkpoint` \u2014 debug/observation point (logs node I/O).\n- `output` \u2014 End (workflow result). Exactly one.\n- `provider` \u2014 one off-chain node holding the canvas-wide provider/model; nodes reference it via `data.providerNodeId`.\n\nEdges thread each node\'s output to the next; the runner exposes `{{ input }}` / `{{ previous_output }}` to downstream nodes.\n\n### Example (minimal chain)\n\n```\n{\n  "version": "1.0",\n  "metadata": { "name": "summarize" },\n  "parameters": [],\n  "nodes": [\n    { "id": "start", "type": "trigger", "position": { "x": 0, "y": 0 }, "data": {} },\n    { "id": "p1", "type": "prompt", "position": { "x": 0, "y": 120 }, "data": { "sourceType": "file", "source": "prompts/summarize.prmd" } },\n    { "id": "end", "type": "output", "position": { "x": 0, "y": 240 }, "data": {} }\n  ],\n  "edges": [\n    { "id": "e1", "source": "start", "target": "p1" },\n    { "id": "e2", "source": "p1", "target": "end" }\n  ]\n}\n```\n\nTo edit the workflow, modify this JSON with the file tools (paths are workspace-relative). Keep exactly one `trigger` and one `output`.\n',
   "systems/system-prmd-md.md": '---\nid: system-prmd-md\nname: Prompt file system prompt (.prmd / .md)\nversion: 1.0.0\ninherits: ./system-base.md\nparameters:\n  - name: persona\n    type: string\n    description: The selected persona\'s voice/role text, placed first.\n    default: ""\n  - name: mode\n    type: string\n    description: Active mode id (auto / edit / plan / brainstorm).\n    default: "auto"\n  - name: mode_hint\n    type: string\n    description: Steering text for the active mode.\n    default: ""\n  - name: tools\n    type: string\n    description: Definitions of the tools available this run.\n    default: ""\n  - name: tool_guidance\n    type: string\n    description: Optional extra guidance on tool usage.\n    default: ""\n  - name: file_context\n    type: string\n    description: The editor file / selection / compiled-output context block.\n    default: ""\n---\n\n{% include "../languages/prmd.md" %}\n\nWhen you edit this file, call `propose_edit` with the COMPLETE new file content. Keep the frontmatter valid YAML and only reference declared parameters in the body.\n',
@@ -16562,9 +16606,9 @@ Add your specific criteria here.
 
 Respond with PASS or FAIL followed by a one-sentence reason.
 `,
-  "strategies/debate.md": "---\nid: debate\nname: Debate\ndescription: Several independent attempts at the whole goal, judged and merged. Highest token use; best quality for open-ended or high-stakes goals.\ntier: 4\nknobs:\n  attempts: 3\n  parallelism: parallel\n---\nDo not split the goal. Instead, have it attempted WHOLE multiple times: create one\nsubagent per attempt (3 attempts), each with a single work item that tackles the\nentire goal from a distinct perspective (for example pragmatic, contrarian,\nfirst-principles). Name each subagent for its perspective. Write the synthesis as\na JUDGE: compare the attempts in {{ joined }}, weigh their strengths, and merge\nthe best elements into one final answer, noting significant disagreements.\n",
-  "strategies/fanout.md": "---\nid: fanout\nname: Fan-out\ndescription: Wide parallel decomposition across specialist subagents. Higher token use; broad coverage, fastest wall-clock.\ntier: 3\ndefault: true\nknobs:\n  parallelism: parallel\n---\nDecompose the goal into INDEPENDENT workstreams that can run in parallel \u2014 one\nspecialist subagent per theme, each with focused work items. Maximize coverage:\ndistinct angles, no overlapping work. Use dependsOn only where a work item truly\nneeds another item's output.\n",
-  "strategies/lean.md": `---
+  "strategies/types/debate.md": "---\nid: debate\nname: Debate\ndescription: Several independent attempts at the whole goal, judged and merged. Highest token use; best quality for open-ended or high-stakes goals.\ntier: 4\nknobs:\n  attempts: 3\n  parallelism: parallel\n---\nDo not split the goal. Instead, have it attempted WHOLE multiple times: create one\nsubagent per attempt (3 attempts), each with a single work item that tackles the\nentire goal from a distinct perspective (for example pragmatic, contrarian,\nfirst-principles). Name each subagent for its perspective. Write the synthesis as\na JUDGE: compare the attempts in {{ joined }}, weigh their strengths, and merge\nthe best elements into one final answer, noting significant disagreements.\n",
+  "strategies/types/fanout.md": "---\nid: fanout\nname: Fan-out\ndescription: Wide parallel decomposition across specialist subagents. Higher token use; broad coverage, fastest wall-clock.\ntier: 3\ndefault: true\nknobs:\n  parallelism: parallel\n---\nDecompose the goal into INDEPENDENT workstreams that can run in parallel \u2014 one\nspecialist subagent per theme, each with focused work items. Maximize coverage:\ndistinct angles, no overlapping work. Use dependsOn only where a work item truly\nneeds another item's output.\n",
+  "strategies/types/lean.md": `---
 id: lean
 name: Lean
 description: One subagent, a few sequential steps. Lowest token use \u2014 best for focused, well-defined goals.
@@ -16582,7 +16626,7 @@ reserve a stronger model only for a work item that is genuinely hard.
 If a single work item covers the goal, set "synthesis" to exactly "{{ joined }}"
 so the runner returns that output directly without a synthesis call.
 `,
-  "strategies/pipeline.md": "---\nid: pipeline\nname: Pipeline\ndescription: Staged chain \u2014 each stage's output feeds the next. Moderate token use; best for transform-and-refine goals.\ntier: 2\nknobs:\n  parallelism: staged\n---\nDecompose the goal into sequential STAGES (one subagent per stage), each\ntransforming or refining what the previous stage produced \u2014 for example\nresearch, then draft, then refine, then package. Keep it to 2-4 stages. Within a\nstage, work items may run in parallel, but a stage must only need what earlier\nstages produced. Write each stage's work prompts to state what they consume from\nthe previous stage and what they hand to the next.\n",
+  "strategies/types/pipeline.md": "---\nid: pipeline\nname: Pipeline\ndescription: Staged chain \u2014 each stage's output feeds the next. Moderate token use; best for transform-and-refine goals.\ntier: 2\nknobs:\n  parallelism: staged\n---\nDecompose the goal into sequential STAGES (one subagent per stage), each\ntransforming or refining what the previous stage produced \u2014 for example\nresearch, then draft, then refine, then package. Keep it to 2-4 stages. Within a\nstage, work items may run in parallel, but a stage must only need what earlier\nstages produced. Write each stage's work prompts to state what they consume from\nthe previous stage and what they hand to the next.\n",
   "skills/strategy-planning/SKILL.prmd": `---
 id: strategy-planning
 name: strategy-planning
@@ -16631,7 +16675,19 @@ the goal's stakes and vagueness:
    or context gaps with edit_strategy. Then tell the user what you gathered, what
    you decided, and where the spec/plan files live \u2014 the canvas graph plus those
    two files ARE the deliverable.
-`
+`,
+  "roles/document-writer/PERSONA.md": "Clear, plain-spoken technical writer. Values accuracy and brevity over flourish.\n",
+  "roles/document-writer/POLICY.yaml": "version: 1\nname: role:document-writer\ndefaultPermission: ask\nmutatingDefault: ask\npermissions:\n  read_file: allow\n  list_files: allow\n  search_files: allow\n  stat_file: allow\n  write_file: ask\n  create_file: ask\n",
+  "roles/document-writer/ROLE.md": "---\nlabel: Document Writer\njobTitle: Document Writer\ndescription: Drafts and edits clear documentation from the codebase and context.\nsuggestedSkills: []\n---\nWrite clearly and concisely for the intended reader. Ground every claim in the source. Prefer short sentences and concrete examples.\n",
+  "roles/research-analyst/PERSONA.md": "Rigorous analyst. Sources claims, flags uncertainty, distinguishes fact from inference.\n",
+  "roles/research-analyst/POLICY.yaml": "version: 1\nname: role:research-analyst\ndefaultPermission: ask\nmutatingDefault: deny\npermissions:\n  read_file: allow\n  list_files: allow\n  search_files: allow\n  stat_file: allow\n  web_search: allow\n  recall_memory: allow\n",
+  "roles/research-analyst/ROLE.md": "---\nlabel: Research Analyst\njobTitle: Research Analyst\ndescription: Gathers and synthesizes information; does not modify the workspace.\nsuggestedSkills: []\n---\nGather from the web and the workspace, then synthesize a sourced, structured answer. Separate findings from assumptions. Do not modify files.\n",
+  "roles/senior-software-engineer/PERSONA.md": "Pragmatic senior engineer. Precise, terse, correctness-first. Prefers the smallest change that fully solves the problem.\n",
+  "roles/senior-software-engineer/POLICY.yaml": "version: 1\nname: role:senior-software-engineer\ndefaultPermission: ask\nmutatingDefault: ask\npermissions:\n  read_file: allow\n  list_files: allow\n  search_files: allow\n  stat_file: allow\n  compile_prompd: allow\n  write_file: ask\n  create_file: ask\n  rename_file: ask\n",
+  "roles/senior-software-engineer/ROLE.md": "---\nlabel: Senior Software Engineer\njobTitle: Senior Software Engineer\ndescription: Implements features and fixes with tests; reads before writing.\nsuggestedSkills: []\n---\nImplement changes test-first. Read the surrounding code and match its conventions. Keep changes minimal and focused; explain non-obvious decisions.\n",
+  "roles/senior-test-engineer/PERSONA.md": "Meticulous, adversarial about correctness. Thinks in failure modes and boundary conditions.\n",
+  "roles/senior-test-engineer/POLICY.yaml": "version: 1\nname: role:senior-test-engineer\ndefaultPermission: ask\nmutatingDefault: deny\npermissions:\n  read_file: allow\n  list_files: allow\n  search_files: allow\n  stat_file: allow\n  compile_prompd: allow\n",
+  "roles/senior-test-engineer/ROLE.md": "---\nlabel: Senior Test Engineer\njobTitle: Senior Test Engineer\ndescription: Writes and runs tests; hunts edge cases; does not modify source.\nsuggestedSkills: []\n---\nFocus on coverage and edge cases. Write tests that fail before a fix and pass after. Do not modify production source; report gaps you find.\n"
 };
 
 // ../harness/prompts/library/index.ts
@@ -16884,8 +16940,7 @@ async function compileConfigTemplate(path, params) {
   }
 }
 function formatTools(tools) {
-  if (!tools || !tools.length) return "";
-  return tools.map((t) => `- \`${t.name}\`: ${t.description}`).join("\n");
+  return tools && tools.length ? formatToolLines(tools) : "";
 }
 async function composeAgentSystem(args) {
   const mode = args.mode || "auto";
@@ -16902,21 +16957,37 @@ async function composeAgentSystem(args) {
   ]);
   const tool_guidance = toolGuidanceRaw.replace(/<!--[\s\S]*?-->/g, "").trim();
   const skillsBlock = await enabledSkillInstructions().catch(() => "");
+  const memoryIdx = args.memoryIndex ? await args.memoryIndex().catch(() => "") : "";
+  const memoryBlock = memoryIdx.trim() ? `## Memory
+Notes you've saved. Call recall_memory to read one in full; save_memory to add one.
+
+${memoryIdx.trim()}` : "";
   return compileConfigTemplate(systemPath, {
     persona: persona.trim(),
     mode,
     mode_hint,
     tool_guidance,
-    tools: formatTools(args.tools),
-    file_context: [(args.contextText || "").trim(), skillsBlock].filter(Boolean).join("\n\n"),
+    tools: args.toolsText ?? formatTools(args.tools),
+    file_context: [(args.contextText || "").trim(), memoryBlock, skillsBlock].filter(Boolean).join("\n\n"),
     ...args.params || {}
   });
 }
 
 // ../tools-node/fileService.ts
 import { promises as fs } from "node:fs";
-import { join, resolve, relative, dirname, sep, basename } from "node:path";
+import { join, resolve, relative, dirname, sep, basename, isAbsolute } from "node:path";
 var SKIP = /* @__PURE__ */ new Set(["node_modules", ".git", "dist", "build", ".next", ".cache", ".turbo"]);
+function escapesRoot(rel, platformSep = sep) {
+  if (rel === "") return false;
+  if (rel === ".." || rel.startsWith(".." + platformSep)) return true;
+  if (rel.split(platformSep)[0] === "..") return true;
+  if (isAbsolute(rel)) return true;
+  if (platformSep === "\\") {
+    if (/^[a-zA-Z]:/.test(rel)) return true;
+    if (rel.startsWith("\\\\")) return true;
+  }
+  return false;
+}
 var NodeFileService = class {
   kind = "directory";
   label;
@@ -16930,8 +17001,7 @@ var NodeFileService = class {
   }
   /** True if `a` is lexically within the root (the root itself counts). */
   within(a) {
-    const rel = relative(this.root, a);
-    return rel === "" || rel !== ".." && !rel.startsWith(".." + sep) && rel.split(sep)[0] !== "..";
+    return !escapesRoot(relative(this.root, a));
   }
   /** Absolute path for a folder-relative one, rejecting anything that escapes root
    * LEXICALLY (../, absolute). Symlink escapes are caught by assertReal/realAbs. */
@@ -16950,7 +17020,7 @@ var NodeFileService = class {
       try {
         const real = await fs.realpath(probe);
         const rel = relative(realRoot, real);
-        if (rel !== "" && (rel === ".." || rel.startsWith(".." + sep) || rel.split(sep)[0] === "..")) {
+        if (escapesRoot(rel)) {
           throw new Error(`path escapes the workspace root via symlink: ${a}`);
         }
         return;

package/package.json

@@ -1,29 +1,22 @@
 {
   "name": "@corenel/cli",
-  "version": "0.1.1",
+  "version": "0.2.0",
   "type": "module",
   "description": "Corenel CLI — runs the harness in node, in-proc, no transport. The headless proof the kernel is host-agnostic. (corenel run/ask/chat/login + start --sidecar to follow.)",
   "bin": {
     "corenel": "dist/cli.js"
   },
-  "scripts": {
-    "typecheck": "tsc --noEmit",
-    "start": "tsx src/cli.ts",
-    "verify": "tsx src/verify.ts",
-    "build": "node build.mjs",
-    "prepublishOnly": "node build.mjs"
-  },
   "dependencies": {
     "openai": "^4.77.0"
   },
   "devDependencies": {
-    "@corenel/harness": "workspace:*",
-    "@corenel/protocol": "workspace:*",
-    "@corenel/tools-node": "workspace:*",
     "esbuild": "^0.21.5",
     "@types/node": "^24.13.1",
     "tsx": "^4.19.2",
-    "typescript": "^5.9.3"
+    "typescript": "^5.9.3",
+    "@corenel/harness": "0.2.0",
+    "@corenel/tools-node": "0.2.0",
+    "@corenel/protocol": "0.2.0"
   },
   "publishConfig": {
     "access": "public"
@@ -35,5 +28,11 @@
   ],
   "engines": {
     "node": ">=18"
+  },
+  "scripts": {
+    "typecheck": "tsc --noEmit",
+    "start": "tsx src/cli.ts",
+    "verify": "tsx src/verify.ts",
+    "build": "node build.mjs"
   }
-}
+}