@trim21/personal-pi-extensions 0.1.554 → 0.1.556

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trim21/personal-pi-extensions",
-  "version": "0.1.554",
+  "version": "0.1.556",
   "type": "module",
   "description": "Custom pi coding-agent extensions: bwrap sandbox, workspace guard, opencode edit, and more",
   "keywords": [

package/src/aft/guidelines.md

@@ -0,0 +1,3 @@
+### AFT 工具
+
+调查代码库时先用 AFT 工具（aft_outline / aft_zoom / aft_callgraph / aft_search）摸清结构、查看符号、追踪调用关系，再退回 grep 或整文件读取——它们成本更低，也是为此专门构建的。

package/src/aft/tools.ts

@@ -41,6 +41,14 @@ const SEARCH_PROMPT = readFileSync(
   fileURLToPath(new URL("search.md", import.meta.url)),
   "utf8",
 ).trim();
+/**
+ * 四个工具共用的使用准则，挂在结构入口 aft_outline 上注入一次：pi 的
+ * promptGuidelines 是 per-tool 的，而这条讲的是整个 AFT 工具集的分工。
+ */
+const AFT_GUIDELINES = readFileSync(
+  fileURLToPath(new URL("guidelines.md", import.meta.url)),
+  "utf8",
+).trim();
 
 export interface AftToolContext {
   cwd: string;
@@ -124,7 +132,7 @@ export function registerOutlineTool(pi: ExtensionAPI, ctx: AftToolContext): void
       "target 为目录时默认返回扁平文件树（语言、顶层符号数、字节大小）；传 files: false 可改回符号大纲。",
     ].join("\n"),
     promptSnippet: "Output structural outline of a file/directory",
-    promptGuidelines: [OUTLINE_PROMPT],
+    promptGuidelines: [OUTLINE_PROMPT, AFT_GUIDELINES],
     parameters: OutlineParams,
     async execute(_id, params, signal, _onUpdate, extCtx) {
       const target = coerceTargetParam(params.target);

package/src/bwrap/runtime.ts

@@ -260,8 +260,8 @@ function notifyMode(
   ctx.ui.notify(labels[mode], "info");
 }
 
-/** 沙箱默认写边界：根只读、工作区可写、.git 只读。不展开用户配置的额外可写路径。 */
-const SANDBOX_WRITE_RULES = "/ is read-only, ./ is writable, ./.git/ is read-only";
+/** 沙箱默认写边界：根只读、工作区与 /tmp 可写、.git 只读。不展开用户配置的额外可写路径。 */
+const SANDBOX_WRITE_RULES = "/ is read-only, /tmp/ and ./ are writable, ./.git/ is read-only";
 
 /** 网络层级：关 / 只放行白名单 / 完全放开（白名单域名本身不列出，对判断失败无用）。 */
 function describeNetwork(resolved: ResolvedBwrap): string {

package/src/system-prompt/prompt.md

@@ -17,7 +17,6 @@ In addition to the tools above, you may have access to other custom tools depend
 
 ## Doing tasks
 
-- When investigating a codebase, first use the AFT tools (aft_outline / aft_zoom / aft_callgraph / aft_search) to map the structure, inspect named symbols, and trace call relationships before falling back to grep or full-file reads — they are cheaper and purpose-built for this.
 - The user will primarily request you to perform software engineering tasks. These may include solving bugs, adding new functionality, refactoring code, explaining code, and more. When given an unclear or generic instruction, consider it in the context of these software engineering tasks and the current working directory. For example, if the user asks you to change "methodName" to snake case, do not reply with just "method_name", instead find the method in the code and modify the code.
 - You are highly capable and often allow users to complete ambitious tasks that would otherwise be too complex or take too long. You should defer to user judgement about whether a task is too large to attempt.
 - For exploratory questions ("what could we do about X?", "how should we approach this?", "what do you think?"), respond in 2-3 sentences with a recommendation and the main tradeoff. Present it as something the user can redirect, not a decided plan. Don't implement until the user agrees.