frappe-builder 1.1.0-dev.18 → 1.1.0-dev.19

package/.frappe-builder/po-approval/implementation-artifacts/sprint-status.yaml

@@ -2,13 +2,13 @@ feature_id: po-approval
 feature_name: "PO Approval"
 mode: full
 phase: testing
-updated_at: 2026-03-28T11:05:52.239Z
+updated_at: 2026-03-28T11:15:20.689Z
 
 components:
   - id: final-comp
     sort_order: 0
     status: complete
-    completed_at: 2026-03-28T11:05:52.239Z
+    completed_at: 2026-03-28T11:15:20.689Z
 
 progress:
   done: 1

package/AGENTS.md

@@ -11,6 +11,21 @@ You are Frappe-Nexus, the primary orchestrator for frappe-builder — a Frappe/E
 - Surface state clearly: active project, feature, phase, progress — never work silently
 - Run quality gates before marking any feature complete
 
+## Context Window Protection (MANDATORY)
+
+**Always use context-mode MCP tools.** Raw tool output floods the context window and degrades performance. This is non-negotiable.
+
+| Instead of… | Use… |
+|---|---|
+| Reading a file to analyse it | `ctx_execute_file(path, ...)` |
+| Running bash commands with long output | `ctx_execute(language: "shell", code: "...")` |
+| Searching the codebase | `ctx_batch_execute(commands, queries)` or `ctx_search(queries)` |
+| Fetching a URL | `ctx_fetch_and_index(url)` then `ctx_search(...)` |
+
+**Only use direct Read/Bash when you are about to Edit the file** — the Edit tool needs file content in context. All other reads must go through context-mode.
+
+After every `ctx_batch_execute` or `ctx_execute`, summarise findings in 3–5 bullet points. Never dump raw output into your response.
+
 ## Constraints
 - Never auto-pilot: every significant action must be visible to the developer
 - Always prefer Frappe built-ins over custom solutions

package/extensions/frappe-session.ts

@@ -238,7 +238,9 @@ export function buildStateInjection(ctx: SessionContext): string {
     `Phase: ${ctx.phase}`,
     `Progress: ${progress}`,
     `Last action: ${ctx.lastTool ?? "none"}`,
-    "======================================"
+    "======================================",
+    "CONTEXT WINDOW RULE: Use ctx_execute_file / ctx_execute / ctx_batch_execute / ctx_search for ALL",
+    "reads and searches. Only use Read directly when you are about to Edit that file.",
   );
   return lines.join("\n");
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "frappe-builder",
-  "version": "1.1.0-dev.18",
+  "version": "1.1.0-dev.19",
   "description": "Frappe-native AI co-pilot for building and customising Frappe/ERPNext applications",
   "type": "module",
   "bin": {

package/tools/context-sandbox.ts

@@ -1,9 +1,14 @@
 /**
- * Context-mode sandbox routing for Frappe tool output.
+ * Output truncation guard for Frappe tool output.
  *
- * Context-mode MCP tools are accessible to the LLM session but not callable
- * directly from extension code. Until an HTTP endpoint is discoverable,
- * routeThroughContextMode applies the 8K truncation fallback.
+ * Context-mode MCP tools (ctx_execute, ctx_search, etc.) are only callable by
+ * the LLM agent — NOT from Node.js extension code. There is no HTTP endpoint
+ * to route to from here.
+ *
+ * This module is a last-resort truncation guard for bench_execute and
+ * frappe_query outputs that would otherwise flood the context window.
+ * The agent is instructed via AGENTS.md to use ctx_execute / ctx_batch_execute
+ * proactively instead of relying on this fallback.
  *
  * NFR17: truncation is NEVER silent — warning is always prepended.
  */
@@ -11,12 +16,11 @@
 const CHAR_LIMIT = 8192 * 4; // ~8K tokens at 4 chars/token
 
 /**
- * Routes raw tool output through the context-mode sandbox.
- * Falls back to 8K truncation with a visible warning if sandbox unavailable.
+ * Applies the 8K truncation guard to raw tool output.
+ * Named routeThroughContextMode for API compatibility with existing callers.
  * Never throws.
  */
 export async function routeThroughContextMode(raw: string): Promise<string> {
-  // TODO: wire to context-mode MCP HTTP endpoint when discoverable from extension code
   return applyTruncationFallback(raw);
 }