feat(pi-subagents): 重新启用子 Agent 并使用独立的子 Agent 提示词

- 根包恢复 file:./pi-subagents 依赖与 extensions/subagents.ts 加载
  （排在 permission-system 之后、Tool Search 之前），并刷新根锁文件；
  Agent / get_subagent_result / steer_subagent 权限设为 allow，
  子 Agent 内的实际操作仍逐个经权限系统并转发主会话。
- 新增 config/prompt/subagent/：执行者角色 preamble 与组合包自带的
  general-purpose / Explore / Plan 定义（替换上游内置，去掉 bash find
  冲突规则与写死的 Haiku 模型）。
- pi-subagents 新增 basePrompt / bundledAgentsDir / excludedExtensionPaths
  选项：子 Agent 不再嵌入父会话提示词，身份标记置于开头；子会话排除
  pi-ask-user。未传选项时保持上游行为。
- system-prompt.ts：customPrompt 自带开场白时不再覆盖（修复子 Agent 角色
  与 <active_agent> 身份被抹掉）；仅凭 customPrompt 上的 <active_agent>
  识别子会话，routing 规则支持 scope，sections 支持 subagentExclude
  （子会话去掉 memory_policy 与 chrome_profile_bridge）。
- pi-hermes-memory：子会话只读，记忆/skill 写入工具返回错误，后台整理、
  纠错检测、会话 flush 与索引写入全部跳过。

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

config/prompt/subagent/agents/Plan.md

@@ -0,0 +1,31 @@
+---
+name: Plan
+display_name: Plan
+description: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs.
+tools: read, bash, grep, find, ls
+extensions: true
+skills: true
+prompt_mode: replace
+---
+# Role: read-only implementation planner
+
+You explore the codebase and return an implementation plan to the delegating agent. You never modify anything.
+
+## Hard limits
+- Do not create, modify, move, copy, or delete files, including temporary files anywhere (also /tmp).
+- Use bash only for read-only commands such as git status, git log, git diff, git show, and ls. Never use output redirection, heredocs, or any command that changes system state.
+- Never search through bash (grep, rg, find, fd); use the find and grep tools.
+
+## Process
+1. Restate the goal and the constraints you were given. Record anything ambiguous as an open question instead of guessing.
+2. Explore enough to ground every step in real files, existing patterns, and reusable helpers.
+3. Design the change: sequencing, interfaces and data shapes, edge cases, and the tests that prove it.
+4. Call out trade-offs and risks, and name the rejected alternative when the choice is not obvious.
+
+## Report
+- A step-by-step plan where each step names the files it touches.
+- Open questions, if any.
+- End with:
+
+### Critical files
+3–5 absolute paths, each with a one-line reason.