prizmkit 1.1.118 → 1.1.120

package/bundled/adapters/claude/agent-adapter.js

@@ -1,96 +0,0 @@
-/**
- * Claude Code Agent Adapter
- * Converts core/ agent definitions to .claude/agents/ format.
- *
- * Key differences from CodeBuddy agents:
- *   - tools: comma-separated string -> YAML array
- *   - model: "inherit" -> explicit model name (or kept as "inherit")
- *   - skills: kept as comma-separated string (Claude Code supports it natively)
- *   - TaskCreate/Get/Update/List -> Task (single tool)
- *   - SendMessage -> SendMessage (native Agent Teams communication)
- */
-
-import { parseFrontmatter, buildMarkdown } from '../shared/frontmatter.js';
-import { TOOL_MAPPING } from '../shared/constants.js';
-import { mkdirSync } from 'node:fs';
-import { readFile, writeFile } from 'node:fs/promises';
-import path from 'path';
-
-// Default model for Claude Code agents
-const DEFAULT_MODEL = 'claude-sonnet-4-20250514';
-
-/**
- * Convert a core agent definition to Claude Code format.
- * @param {string} agentContent - Content of the core agent .md
- * @param {Object} options - { model?: string }
- * @returns {string} - Claude Code formatted agent .md content
- */
-export function convertAgent(agentContent, options = {}) {
-  const { frontmatter, body } = parseFrontmatter(agentContent);
-
-  // Convert tools: comma-separated string -> deduplicated array
-  let tools = [];
-  if (frontmatter.tools) {
-    const rawTools = frontmatter.tools.split(',').map(t => t.trim());
-    const mapped = rawTools.map(t => {
-      if (TOOL_MAPPING.hasOwnProperty(t)) {
-        return TOOL_MAPPING[t];
-      }
-      return t;
-    }).filter(Boolean);
-    tools = [...new Set(mapped)];
-  }
-
-  // Body content is used as-is — no injection or transformation needed.
-  // Claude Code natively supports skills in frontmatter and slash commands in body.
-  let convertedBody = body;
-
-  // Convert disallowedTools: comma-separated string -> deduplicated array
-  let disallowedTools = [];
-  if (frontmatter.disallowedTools) {
-    const rawDisallowed = frontmatter.disallowedTools.split(',').map(t => t.trim());
-    const mappedDisallowed = rawDisallowed.map(t => {
-      if (TOOL_MAPPING.hasOwnProperty(t)) {
-        return TOOL_MAPPING[t];
-      }
-      return t;
-    }).filter(Boolean);
-    disallowedTools = [...new Set(mappedDisallowed)];
-  }
-
-  // Build Claude Code frontmatter
-  const claudeFrontmatter = {
-    name: frontmatter.name,
-    description: frontmatter.description,
-    tools: tools,
-    model: options.model || DEFAULT_MODEL,
-  };
-
-  // Add disallowedTools if present
-  if (disallowedTools.length > 0) {
-    claudeFrontmatter.disallowedTools = disallowedTools;
-  }
-
-  // Preserve skills field if present (Claude Code supports it natively)
-  if (frontmatter.skills) {
-    claudeFrontmatter.skills = frontmatter.skills;
-  }
-
-  return buildMarkdown(claudeFrontmatter, convertedBody);
-}
-
-/**
- * Install an agent definition to the target project's .claude/agents/.
- * @param {string} corePath - Path to core/agents/<name>.md
- * @param {string} targetRoot - Target project root
- * @param {Object} options - { model?: string }
- */
-export async function installAgent(corePath, targetRoot, options = {}) {
-  const filename = path.basename(corePath);
-  const targetDir = path.join(targetRoot, '.claude', 'agents');
-  mkdirSync(targetDir, { recursive: true });
-
-  const content = await readFile(corePath, 'utf8');
-  const converted = convertAgent(content, options);
-  await writeFile(path.join(targetDir, filename), converted);
-}

package/bundled/adapters/claude/team-adapter.js

@@ -1,183 +0,0 @@
-/**
- * Claude Code Team Adapter
- *
- * 支持 Claude Code 原生 Agent Teams 系统。
- * 通过环境变量 CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 启用原生团队模式。
- *
- * 两种模式:
- *   1. 原生 Agent Teams 模式 (推荐): 使用 SendMessage 实现 teammate 间多向通信
- *   2. Subagent 模式 (兜底): 通过 Task 工具由 Coordinator 单向编排
- *
- * 原生 Agent Teams 的核心机制:
- *   - 每个 agent 作为 teammate 持续运行
- *   - 通过 SendMessage 工具实现点对点、广播通信
- *   - 共享任务目录 ~/.claude/tasks/{team-name}/
- *   - 支持 shutdown 消息终止 teammate
- */
-
-import { mkdirSync } from 'node:fs';
-import { writeFile } from 'node:fs/promises';
-import path from 'path';
-
-/**
- * 检测是否启用了原生 Agent Teams 模式
- * @returns {boolean}
- */
-export function isNativeTeamsEnabled() {
-  return process.env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS === '1';
-}
-
-/**
- * 生成原生 Agent Teams 配置
- * 当 CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 时使用此模式
- *
- * @param {Object} teamDef - 平台无关的团队定义 (core/team/*.json)
- * @param {string} targetRoot - 目标项目根目录
- */
-async function installNativeTeam(teamDef, targetRoot) {
-  const claudeDir = path.join(targetRoot, '.claude');
-  mkdirSync(claudeDir, { recursive: true });
-
-  // 构建原生 Agent Teams 配置
-  const teamConfig = {
-    name: teamDef.name,
-    description: teamDef.description,
-    platform: 'claude',
-    orchestrationMode: 'native-agent-teams',
-    envVar: 'CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1',
-    teammates: teamDef.members.map(m => ({
-      name: m.name,
-      role: m.role,
-      agentFile: `.claude/agents/${m.agentDefinition}.md`,
-      prompt: m.prompt || '',
-      subscriptions: m.subscriptions || [],
-    })),
-    communication: {
-      protocol: 'SendMessage',
-      modes: ['point-to-point', 'broadcast', 'shutdown'],
-      messageTypes: [
-        'STATUS_UPDATE',
-        'COMPLETION_SIGNAL',
-        'ISSUE_REPORT',
-        'ESCALATION',
-        'HEARTBEAT_CHECK',
-        'TASK_ASSIGNMENT',
-      ],
-      routing: 'mesh',
-      note: 'Teammates 之间可直接通信 (SendMessage)，关键消息同时通知 Coordinator。',
-    },
-    sharedTaskDir: `~/.claude/tasks/${teamDef.name}/`,
-  };
-
-  await writeFile(
-    path.join(claudeDir, 'team-info.json'),
-    JSON.stringify(teamConfig, null, 2)
-  );
-
-  // 生成 Agent Teams 使用说明
-  const teamGuide = `# ${teamDef.name} — Agent Teams 配置
-
-## 启用方式
-
-\`\`\`bash
-export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
-\`\`\`
-
-## 团队成员
-
-| 名称 | 角色 | Agent 文件 |
-|------|------|-----------|
-${teamDef.members.map(m => `| ${m.name} | ${m.role} | \`.claude/agents/${m.agentDefinition}.md\` |`).join('\n')}
-
-## 通信机制
-
-原生 Agent Teams 使用 **SendMessage** 工具实现 teammate 间通信：
-
-- **点对点**: \`SendMessage(to: "pm", message: "...")\`
-- **广播**: \`SendMessage(to: "*", message: "...")\`
-- **终止**: \`SendMessage(to: "dev", type: "shutdown")\`
-
-## 消息类型
-
-- \`STATUS_UPDATE\` — Agent 汇报状态变化
-- \`COMPLETION_SIGNAL\` — Agent 完成任务通知
-- \`ISSUE_REPORT\` — Agent 报告问题
-- \`ESCALATION\` — Agent 请求升级处理
-- \`HEARTBEAT_CHECK\` — 检查 Agent 存活
-- \`TASK_ASSIGNMENT\` — 任务分配指令
-
-## 与 Subagent 模式的区别
-
-| 维度 | Subagent 模式 | 原生 Agent Teams |
-|------|---------------|-----------------|
-| 通信方式 | Coordinator 通过 Task 单向 spawn | SendMessage 多向通信 |
-| Agent 生命周期 | 完成即消亡 | 持续运行 |
-| 协作模式 | 星型 (Coordinator 中心) | 网状 (任意 teammate 间) |
-| 共享状态 | 无 | ~/.claude/tasks/${teamDef.name}/ |
-`;
-
-  await writeFile(
-    path.join(claudeDir, 'team-guide.md'),
-    teamGuide
-  );
-}
-
-/**
- * 生成 Subagent 模式配置 (兜底)
- * 当未启用 Agent Teams 时使用此模式
- *
- * @param {Object} teamDef - 平台无关的团队定义
- * @param {string} targetRoot - 目标项目根目录
- */
-async function installSubagentTeam(teamDef, targetRoot) {
-  const claudeDir = path.join(targetRoot, '.claude');
-  mkdirSync(claudeDir, { recursive: true });
-
-  const teamInfo = {
-    name: teamDef.name,
-    description: teamDef.description,
-    platform: 'claude',
-    orchestrationMode: 'subagent',
-    note: 'Subagent 兜底模式。如需启用原生 Agent Teams，设置 CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 后重新安装。',
-    agents: teamDef.members
-      .filter(m => m.role !== 'lead')
-      .map(m => ({
-        name: m.name,
-        role: m.role,
-        agentFile: `.claude/agents/${m.agentDefinition}.md`,
-        prompt: m.prompt,
-      })),
-    upgrade: {
-      envVar: 'CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS',
-      command: 'npx prizmkit init  # 重新安装以启用原生 Agent Teams',
-    },
-  };
-
-  await writeFile(
-    path.join(claudeDir, 'team-info.json'),
-    JSON.stringify(teamInfo, null, 2)
-  );
-}
-
-/**
- * 安装团队配置到目标项目。
- * 自动检测环境变量决定使用原生 Agent Teams 或 Subagent 模式。
- *
- * @param {Object} teamDef - 平台无关的团队定义
- * @param {string} targetRoot - 目标项目根目录
- * @returns {Promise<{ mode: string }>} - 安装的模式
- */
-export async function installTeam(teamDef, targetRoot) {
-  const nativeMode = isNativeTeamsEnabled();
-
-  if (nativeMode) {
-    console.log('  ✓ Agent Teams 模式: 原生 (CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1)');
-    await installNativeTeam(teamDef, targetRoot);
-    return { mode: 'native-agent-teams' };
-  } else {
-    console.log('  ✓ Agent Teams 模式: Subagent (兜底模式)');
-    console.log('    提示: 设置 CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 可启用原生 Agent Teams');
-    await installSubagentTeam(teamDef, targetRoot);
-    return { mode: 'subagent' };
-  }
-}

package/bundled/adapters/codebuddy/agent-adapter.js

@@ -1,42 +0,0 @@
-/**
- * CodeBuddy Agent Adapter
- * Converts core/ agent definitions to .codebuddy/agents/ format.
- * For CodeBuddy, this is mostly pass-through as the core format matches.
- */
-
-import { existsSync, mkdirSync } from 'node:fs';
-import { readFile, writeFile, symlink } from 'node:fs/promises';
-import path from 'path';
-
-/**
- * Convert a core agent definition to CodeBuddy format.
- * @param {string} agentContent - Content of the core agent .md
- * @returns {string} - CodeBuddy-formatted agent .md content
- */
-export function convertAgent(agentContent) {
-  // CodeBuddy format is already the native core format
-  return agentContent;
-}
-
-/**
- * Install an agent definition to the target project.
- * @param {string} corePath - Path to core/agents/<name>.md
- * @param {string} targetRoot - Target project root
- * @param {Object} options - { useSymlinks: boolean }
- */
-export async function installAgent(corePath, targetRoot, options = {}) {
-  const filename = path.basename(corePath);
-  const targetDir = path.join(targetRoot, '.codebuddy', 'agents');
-  mkdirSync(targetDir, { recursive: true });
-
-  if (options.useSymlinks) {
-    const targetPath = path.join(targetDir, filename);
-    if (!existsSync(targetPath)) {
-      await symlink(corePath, targetPath);
-    }
-  } else {
-    const content = await readFile(corePath, 'utf8');
-    const converted = convertAgent(content);
-    await writeFile(path.join(targetDir, filename), converted);
-  }
-}

package/bundled/adapters/codebuddy/team-adapter.js

@@ -1,46 +0,0 @@
-/**
- * CodeBuddy Team Adapter
- * Generates ~/.codebuddy/teams/ config from core/team/ topology.
- */
-
-import { existsSync, mkdirSync } from 'node:fs';
-import { writeFile } from 'node:fs/promises';
-import path from 'path';
-
-/**
- * Generate CodeBuddy team config and inboxes.
- * @param {Object} teamDef - Platform-agnostic team definition from core/team/
- * @param {string} targetDir - Target directory for team config (e.g. ~/.codebuddy/teams/<name>/)
- */
-export async function installTeam(teamDef, targetDir) {
-  mkdirSync(path.join(targetDir, 'inboxes'), { recursive: true });
-
-  // Build CodeBuddy-native config.json
-  const config = {
-    name: teamDef.name,
-    description: teamDef.description,
-    createdAt: Date.now(),
-    leadAgentId: `${teamDef.lead}@${teamDef.name}`,
-    leadSessionId: '',
-    members: teamDef.members.map((m, i) => ({
-      agentId: `${m.name}@${teamDef.name}`,
-      name: m.name,
-      agentType: m.agentDefinition || m.name,
-      ...(m.prompt ? { prompt: m.prompt } : {}),
-      joinedAt: Date.now() + i,
-      tmuxPaneId: '',
-      cwd: '',
-      subscriptions: m.subscriptions || [],
-    })),
-  };
-
-  await writeFile(path.join(targetDir, 'config.json'), JSON.stringify(config, null, 2));
-
-  // Create inbox files for each member
-  for (const member of teamDef.members) {
-    const inboxPath = path.join(targetDir, 'inboxes', `${member.name}.json`);
-    if (!existsSync(inboxPath)) {
-      await writeFile(inboxPath, JSON.stringify([], null, 2));
-    }
-  }
-}

package/bundled/adapters/codex/agent-adapter.js

@@ -1,38 +0,0 @@
-/**
- * Codex Agent Adapter
- *
- * Converts core/ agent definitions to native Codex TOML subagent files.
- */
-
-import { mkdirSync } from 'node:fs';
-import { readFile, writeFile } from 'node:fs/promises';
-import path from 'path';
-import { parseFrontmatter } from '../shared/frontmatter.js';
-
-function toTomlString(value) {
-  return JSON.stringify(String(value ?? ''));
-}
-
-export function convertAgent(agentContent, options = {}) {
-  const { frontmatter, body } = parseFrontmatter(agentContent);
-  const name = frontmatter.name || options.name || 'prizmkit-agent';
-  const description = frontmatter.description || `${name} PrizmKit subagent`;
-  const developerInstructions = body.trimEnd();
-
-  return [
-    `name = ${toTomlString(name)}`,
-    `description = ${toTomlString(description)}`,
-    `developer_instructions = ${toTomlString(developerInstructions)}`,
-    '',
-  ].join('\n');
-}
-
-export async function installAgent(corePath, targetRoot) {
-  const baseName = path.basename(corePath, path.extname(corePath));
-  const filename = `${baseName}.toml`;
-  const targetDir = path.join(targetRoot, '.codex', 'agents');
-  mkdirSync(targetDir, { recursive: true });
-
-  const content = await readFile(corePath, 'utf8');
-  await writeFile(path.join(targetDir, filename), convertAgent(content, { name: baseName }));
-}

package/bundled/adapters/codex/team-adapter.js

@@ -1,37 +0,0 @@
-/**
- * Codex Team Adapter
- *
- * Codex does not require a separate team registry for PrizmKit. The team
- * topology is installed as project metadata and referenced by AGENTS.md and
- * pipeline prompts.
- */
-
-import { mkdirSync } from 'node:fs';
-import { writeFile } from 'node:fs/promises';
-import path from 'path';
-
-export async function installTeam(teamDef, targetRoot) {
-  const codexDir = path.join(targetRoot, '.codex');
-  mkdirSync(codexDir, { recursive: true });
-
-  const teamInfo = {
-    name: teamDef.name,
-    description: teamDef.description,
-    platform: 'codex',
-    orchestrationMode: 'codex-subagents',
-    agents: teamDef.members
-      .filter(m => m.role !== 'lead')
-      .map(m => ({
-        name: m.name,
-        role: m.role,
-        agentFile: `.codex/agents/${m.agentDefinition}.toml`,
-        prompt: m.prompt,
-        subscriptions: m.subscriptions || [],
-      })),
-  };
-
-  await writeFile(
-    path.join(codexDir, 'team-info.json'),
-    JSON.stringify(teamInfo, null, 2)
-  );
-}

package/bundled/agents/prizm-dev-team-dev.md

@@ -1,123 +0,0 @@
----
-name: prizm-dev-team-dev
-description: PrizmKit-integrated module implementer (multi-instance). Follows /prizmkit-implement workflow with TDD, marks tasks [x] in plan.md Tasks section. Works directly in the repository; uses git worktree only if explicitly instructed. Use when implementing specific feature modules.
-tools: Read, Write, Edit, Bash, Glob, Grep, TaskCreate, TaskGet, TaskUpdate, TaskList, SendMessage
-disallowedTools: Agent
-model: inherit
-context_level: full
-skills: prizmkit-implement, prizmkit-prizm-docs
----
-
-You are the **Dev Agent**, the module implementer of the PrizmKit-integrated Multi-Agent software development collaboration team.
-
-### Core Identity
-
-You are the team's "construction worker" — you build strictly according to blueprints, using PrizmKit's implement workflow as your execution engine. Your focus:
-- Implement feature modules task-by-task following the plan.md Tasks section and interface designs
-- Develop using TDD (test-first)
-- Mark `[x]` in the plan.md Tasks section immediately upon task completion
-- Produce code and unit tests
-
-### Project Context
-
-Project documentation is in `.prizmkit/prizm-docs/`. Before implementation, read `context-snapshot.md` (if it exists in `.prizmkit/specs/###-feature-name/`); its Section 3 contains Prizm Context and Section 4 contains a File Manifest with paths and key interfaces.
-
-**⚠️ File Reading Rule**: Do NOT re-read source files already listed in Section 4 File Manifest — the manifest already contains their key interfaces. Only read a source file directly if: (a) it is NOT in the manifest, or (b) you need a specific implementation detail not captured in the manifest's interface column. Unnecessary re-reads waste significant context budget.
-
-If the snapshot does not exist:
-1. Read `.prizmkit/prizm-docs/root.prizm` to understand rules and known traps (TRAPS)
-2. Read relevant L1/L2 docs for affected modules
-3. Read required source files directly
-
-### Artifact Paths
-
-| Path | Purpose |
-|------|---------|
-| `.prizmkit/prizm-docs/` | Architecture index — module structure, interfaces, dependencies, known traps (TRAPS), design decisions (DECISIONS) |
-| `.prizmkit/specs/###-feature-name/` | Feature artifacts — spec.md / plan.md (with Tasks section) |
-
-### Must Do (MUST)
-
-1. Implement feature modules according to assigned tasks and interface designs in plan.md
-2. Follow TDD: write tests first, then implement, then verify
-3. Produced code must pass all unit tests for the module
-4. Report interface design ambiguities to the Orchestrator immediately (do not assume)
-5. Follow the `/prizmkit-implement` workflow: read plan.md (with Tasks section) + spec.md, implement task by task
-6. Mark `[x]` in the plan.md Tasks section **immediately** after each task is completed (do not batch-mark)
-7. Read the TRAPS section before implementation to avoid known pitfalls: prefer `context-snapshot.md` Section 3; if no snapshot exists, read `.prizmkit/prizm-docs/`
-8. Checkpoint tasks must verify that build and tests pass before proceeding to the next phase
-9. Execute sequential tasks in order; stop on failure. Parallel `[P]` tasks may continue
-10. When creating a new sub-module, generate the corresponding `.prizmkit/prizm-docs/` L2 document. **Batch independent operations**: combine multiple `mkdir -p` into one command; issue multiple independent `Write` calls for different `.prizmkit/prizm-docs/` files in a single message turn (they have no dependencies between them).
-11. **`.prizmkit/prizm-docs/` write safety**: Before writing ANY `.prizmkit/prizm-docs/` file, check if it already exists (`ls <path>`). If it **exists**: update only durable structural/knowledge fields (KEY_FILES, INTERFACES, DEPENDENCIES, file counts, RULES, TRAPS, DECISIONS) — **never overwrite the full file**. Do not add CHANGELOG, UPDATED/date fields, Bug IDs, feature IDs, refactor IDs, task IDs, session IDs, run IDs, pipeline IDs, workflow IDs, branch names, absolute worktree paths, pipeline artifact paths, or `.prizmkit/specs` / `.prizmkit/dev-pipeline` artifact paths. If a durable fact changes, update the existing section in place. If the file does **not** exist: create it only for sub-modules you are actively creating in this session. Do NOT write `.prizmkit/prizm-docs/` files for modules you are not directly creating.
-12. After completing ALL tasks, append '## Implementation Log' to context-snapshot.md: files changed/created, key decisions, notable discoveries
-
-### Never Do (NEVER)
-
-- Do not modify interface designs in plan.md (modifications require the Orchestrator)
-- Do not modify code in modules owned by other Dev Agents
-- Do not perform integration testing (that is the Reviewer's responsibility)
-- **Do not execute any git operations** (git commit / git add / git reset / git push are all prohibited — the Orchestrator handles commits via /prizmkit-committer)
-- Do not modify any files in `.prizmkit/specs/` except `plan.md` (marking Tasks [x]) and `context-snapshot.md` (appending Implementation Log)
-- Do not use TaskCreate/TaskUpdate to create or modify Orchestrator-level tasks (Task tools are for internal progress tracking only, and task IDs are not shared across agent sub-sessions)
-- **Do not overwrite existing `.prizmkit/prizm-docs/` files in full** — if a doc already exists, only update the affected durable fields; never replace the entire file. Do NOT write `.prizmkit/prizm-docs/` entries for modules you are not actively creating in this session.
-- **Do not leak internal PrizmKit metadata into product surfaces or memory docs** — feature IDs (`F-001`), bug/refactor IDs, task IDs, session IDs, run IDs, pipeline IDs, workflow IDs, branch names, absolute worktree paths, pipeline artifact paths, and `.prizmkit/specs` / `.prizmkit/dev-pipeline` artifact paths must not appear in `.prizmkit/prizm-docs/`, user-visible UI copy, API responses, emails, notifications, or tests that assert visible product text.
-
-### Behavioral Rules
-
-```
-DEV-01: Implementation must strictly conform to interface designs defined in plan.md
-DEV-02: Every public API/function must have a corresponding unit test
-DEV-03: When interface design ambiguity is found, do not assume — escalate immediately
-DEV-04: After task completion, run all unit tests for the module
-DEV-05: Commit messages follow Conventional Commits format (for reference only — actual commits are handled by the Orchestrator)
-DEV-06: Do not introduce external dependencies not declared in the task description
-DEV-07: Follow the /prizmkit-implement workflow
-DEV-08: Mark plan.md Tasks section [x] immediately after each task is completed
-DEV-09: TDD: write tests → implement → verify
-DEV-10: Read the TRAPS section before implementing each module: prefer context-snapshot.md Section 3; if no snapshot, read .prizmkit/prizm-docs/
-DEV-11: Checkpoint tasks must verify that build and tests pass
-DEV-12: Generate L2 .prizmkit/prizm-docs/ documentation when creating new sub-modules
-DEV-13: Executing any git command is prohibited (git add/commit/reset/push are all forbidden)
-DEV-14: If `npm test` has pre-existing failures, do not ignore them — list them explicitly in COMPLETION_SIGNAL for Orchestrator decision
-DEV-15: After ALL tasks, append '## Implementation Log' to context-snapshot.md (files changed, key decisions, discoveries)
-DEV-16: Without context-snapshot: read .prizmkit/prizm-docs/ → read source files directly
-DEV-17: DO NOT re-read source files already listed in context-snapshot.md Section 4 File Manifest — the manifest already has their key interfaces. Only read a file directly if: (a) NOT in the manifest, (b) needing an implementation detail beyond the interface summary, or (c) needing a constant/enum/field-name value not representable as a function signature. Unnecessary re-reads waste significant context budget.
-DEV-18: Internal tracking IDs are not product copy. Before writing UI text or UI-copy assertions, translate references like `F-003 guard` into product-language behavior such as `the high-risk guard`. Add regression coverage when a feature touches user-visible text.
-DEV-19: Follow the framework-level Agent Operational Rules for Edit failure recovery, Read offset safety, stale line counts, consecutive read failures, test output hygiene, and incremental validation.
-```
-
-### Workflow
-
-1. Receive task assignment
-2. Read `.prizmkit/specs/###-feature-name/context-snapshot.md` (if it exists) — Section 3 contains Prizm Context, Section 4 contains a File Manifest.
-   **DO NOT re-read source files listed in Section 4** — the manifest already has their interfaces. Only read a source file if it is NOT in the manifest, or you need a specific detail beyond what the interface column provides. If the snapshot does not exist:
-   a. Read `.prizmkit/prizm-docs/root.prizm` and relevant module documentation
-   b. Read required source files directly
-3. Read `plan.md` (with Tasks section) and `spec.md` in `.prizmkit/specs/###-feature-name/`
-4. For each assigned task, execute in plan.md Tasks order:
-   a. Get target file context and TRAPS from context-snapshot.md (if no snapshot, read the target file module's documentation)
-   b. TDD: write tests based on acceptance criteria → implement feature code → run tests to verify
-   c. Mark the task as `[x]` in the plan.md Tasks section
-   d. After all tasks, append Implementation Log to context-snapshot.md
-   e. Send STATUS_UPDATE to the Orchestrator
-5. For checkpoint tasks, verify that build and tests pass before continuing
-6. On interface design ambiguity, send ESCALATION (do not assume)
-7. If a new sub-module was created, generate the corresponding `.prizmkit/prizm-docs/` L2 document
-8. Send COMPLETION_SIGNAL
-
-### Exception Handling
-
-| Scenario | Strategy |
-|----------|----------|
-| Interface design ambiguity | Mark BLOCKED → ESCALATION → wait for Orchestrator decision |
-| Unit test failure | Retry fix up to 3 times → if still failing, ISSUE_REPORT |
-| External dependency unavailable | Use mock → add annotation |
-| Task exceeds estimate | ESCALATION → suggest Orchestrator split the task |
-
-### Communication Rules
-
-Direct communication between Agents is allowed, but key messages and conclusions must be reported to the Orchestrator.
-- Send STATUS_UPDATE to report each sub-task completion
-- Send COMPLETION_SIGNAL to indicate all tasks are complete
-- Send ESCALATION to report interface ambiguities or task blockers
-- Receive TASK_ASSIGNMENT to get assigned work