@liangjie559567/ultrapower 7.6.0 → 7.7.0

package/docs/guides/mcp-server-usage.md

@@ -70,8 +70,8 @@ Edit `~/.claude/claude_desktop_config.json`:
 After configuration, restart Claude Desktop. The MCP server tools should appear in the tool list:
 
 ```
-mcp__plugin_ultrapower_t__ultrapower:lsp_hover
-mcp__plugin_ultrapower_t__ultrapower:lsp_goto_definition
+mcp__plugin_ultrapower_t__lsp_hover
+mcp__plugin_ultrapower_t__lsp_goto_definition
 mcp__plugin_ultrapower_t__ultrapower:ast_grep_search
 ... (64 tools total - each tool has both new and legacy names)
 ```
@@ -121,12 +121,12 @@ Restart Cursor. Check the MCP panel to confirm the server is connected and all 3
 
 Get type information at cursor position:
 ```
-Use mcp__plugin_ultrapower_t__ultrapower:lsp_hover with file and position
+Use mcp__plugin_ultrapower_t__lsp_hover with file and position
 ```
 
 Find all references to a symbol:
 ```
-Use mcp__plugin_ultrapower_t__ultrapower:lsp_find_references to locate usage
+Use mcp__plugin_ultrapower_t__lsp_find_references to locate usage
 ```
 
 ### AST Tools

package/docs/guides/tool-name-migration.md

@@ -17,29 +17,29 @@ Starting from v5.6.0, all ultrapower tools use the `ultrapower:` prefix instead
 
 ### LSP Tools
 
-* `lsp_hover` → `ultrapower:lsp_hover`
+* `ultrapower:lsp_hover` → `ultrapower:lsp_hover`
 
-* `lsp_goto_definition` → `ultrapower:lsp_goto_definition`
+* `ultrapower:lsp_goto_definition` → `ultrapower:lsp_goto_definition`
 
-* `lsp_find_references` → `ultrapower:lsp_find_references`
+* `ultrapower:lsp_find_references` → `ultrapower:lsp_find_references`
 
-* `lsp_document_symbols` → `ultrapower:lsp_document_symbols`
+* `ultrapower:lsp_document_symbols` → `ultrapower:lsp_document_symbols`
 
-* `lsp_workspace_symbols` → `ultrapower:lsp_workspace_symbols`
+* `ultrapower:lsp_workspace_symbols` → `ultrapower:lsp_workspace_symbols`
 
-* `lsp_diagnostics` → `ultrapower:lsp_diagnostics`
+* `ultrapower:lsp_diagnostics` → `ultrapower:lsp_diagnostics`
 
-* `lsp_diagnostics_directory` → `ultrapower:lsp_diagnostics_directory`
+* `ultrapower:lsp_diagnostics_directory` → `ultrapower:lsp_diagnostics_directory`
 
-* `lsp_servers` → `ultrapower:lsp_servers`
+* `ultrapower:lsp_servers` → `ultrapower:lsp_servers`
 
-* `lsp_prepare_rename` → `ultrapower:lsp_prepare_rename`
+* `ultrapower:lsp_prepare_rename` → `ultrapower:lsp_prepare_rename`
 
-* `lsp_rename` → `ultrapower:lsp_rename`
+* `ultrapower:lsp_rename` → `ultrapower:lsp_rename`
 
-* `lsp_code_actions` → `ultrapower:lsp_code_actions`
+* `ultrapower:lsp_code_actions` → `ultrapower:lsp_code_actions`
 
-* `lsp_code_action_resolve` → `ultrapower:lsp_code_action_resolve`
+* `ultrapower:lsp_code_action_resolve` → `ultrapower:lsp_code_action_resolve`
 
 ### State Tools
 

package/docs/mcp/configuration.md

@@ -91,7 +91,7 @@ Location: `.claude/mcp.json` (workspace)
       "args": ["bridge/mcp-server.cjs"],
       "disabled": false,
       "autoApprove": [
-        "lsp_hover",
+        "ultrapower:lsp_hover",
         "state_read",
         "notepad_read"
       ]
@@ -137,8 +137,8 @@ Edit `src/mcp/timeout.ts`:
 
 ```typescript
 export const TOOL_TIMEOUTS: Record<string, number> = {
-  lsp_hover: 30000,
-  lsp_diagnostics: 60000,
+  ultrapower:lsp_hover: 30000,
+  ultrapower:lsp_diagnostics: 60000,
   ast_grep_search: 60000,
   ask_codex: 300000,
   ask_gemini: 300000
@@ -160,8 +160,8 @@ Skip permission prompts for trusted tools:
   "mcpServers": {
     "ultrapower": {
       "autoApprove": [
-        "lsp_hover",
-        "lsp_goto_definition",
+        "ultrapower:lsp_hover",
+        "ultrapower:lsp_goto_definition",
         "state_read",
         "notepad_read",
         "project_memory_read"

package/docs/mcp/performance.md

@@ -6,9 +6,9 @@
 
 | Tool | Cold Start | Warm | Notes |
 | ------ | ----------- | ------ | ------- |
-| `lsp_hover` | 150ms | 20ms | LSP server cached |
-| `lsp_diagnostics` | 300ms | 50ms | File-level |
-| `lsp_diagnostics_directory` | 2s | 500ms | Directory scan |
+| `ultrapower:lsp_hover` | 150ms | 20ms | LSP server cached |
+| `ultrapower:lsp_diagnostics` | 300ms | 50ms | File-level |
+| `ultrapower:lsp_diagnostics_directory` | 2s | 500ms | Directory scan |
 | `ast_grep_search` | 100ms | 30ms | Pattern complexity varies |
 | `state_read` | 10ms | 5ms | JSON parse |
 | `notepad_read` | 15ms | 8ms | Markdown parse |
@@ -137,8 +137,8 @@ await mcp__plugin_ultrapower_t__lsp_diagnostics_directory({
 
 Output includes timing:
 ```
-[debug] lsp_hover started
-[debug] lsp_hover completed in 23ms
+[debug] ultrapower:lsp_hover started
+[debug] ultrapower:lsp_hover completed in 23ms
 ```
 
 ### Measure Tool Calls

package/docs/mcp-compatibility-matrix.md

@@ -47,7 +47,7 @@ All community MCP server tools use the format: `mcp__servername__toolname`
 
 Internal OMC tools do not use namespace prefixes:
 
-* `lsp_*` - Language Server Protocol tools
+* `ultrapower:lsp_*` - Language Server Protocol tools
 
 * `ast_grep_*` - AST manipulation tools
 

package/docs/partials/agent-tiers.md

@@ -116,18 +116,18 @@ Task(subagent_type="ultrapower:explore",
 
 | 工具 | 类别 | 用途 | 是否分配给 Agent？ |
 | ------ | ---------- | --------- | --------------------- |
-| `lsp_hover` | LSP | 获取代码位置的类型信息和文档 | 否（orchestrator 直接使用） |
-| `lsp_goto_definition` | LSP | 跳转到符号定义处 | 否（orchestrator 直接使用） |
-| `lsp_find_references` | LSP | 查找符号在代码库中的所有用法 | 是（仅 `explore`） |
-| `lsp_document_symbols` | LSP | 获取文件中所有符号的概览 | 是 |
-| `lsp_workspace_symbols` | LSP | 按名称在工作区中搜索符号 | 是 |
-| `lsp_diagnostics` | LSP | 获取文件的错误、警告和提示 | 是 |
-| `lsp_diagnostics_directory` | LSP | 项目级类型检查（tsc --noEmit 或 LSP） | 是 |
-| `lsp_prepare_rename` | LSP | 检查符号是否可以重命名 | 否（orchestrator 直接使用） |
-| `lsp_rename` | LSP | 在整个项目中重命名符号 | 否（orchestrator 直接使用） |
-| `lsp_code_actions` | LSP | 获取可用的重构和快速修复 | 否（orchestrator 直接使用） |
-| `lsp_code_action_resolve` | LSP | 获取代码操作的完整编辑详情 | 否（orchestrator 直接使用） |
-| `lsp_servers` | LSP | 列出可用的语言服务器及安装状态 | 否（orchestrator 直接使用） |
+| `ultrapower:lsp_hover` | LSP | 获取代码位置的类型信息和文档 | 否（orchestrator 直接使用） |
+| `ultrapower:lsp_goto_definition` | LSP | 跳转到符号定义处 | 否（orchestrator 直接使用） |
+| `ultrapower:lsp_find_references` | LSP | 查找符号在代码库中的所有用法 | 是（仅 `explore`） |
+| `ultrapower:lsp_document_symbols` | LSP | 获取文件中所有符号的概览 | 是 |
+| `ultrapower:lsp_workspace_symbols` | LSP | 按名称在工作区中搜索符号 | 是 |
+| `ultrapower:lsp_diagnostics` | LSP | 获取文件的错误、警告和提示 | 是 |
+| `ultrapower:lsp_diagnostics_directory` | LSP | 项目级类型检查（tsc --noEmit 或 LSP） | 是 |
+| `ultrapower:lsp_prepare_rename` | LSP | 检查符号是否可以重命名 | 否（orchestrator 直接使用） |
+| `ultrapower:lsp_rename` | LSP | 在整个项目中重命名符号 | 否（orchestrator 直接使用） |
+| `ultrapower:lsp_code_actions` | LSP | 获取可用的重构和快速修复 | 否（orchestrator 直接使用） |
+| `ultrapower:lsp_code_action_resolve` | LSP | 获取代码操作的完整编辑详情 | 否（orchestrator 直接使用） |
+| `ultrapower:lsp_servers` | LSP | 列出可用的语言服务器及安装状态 | 否（orchestrator 直接使用） |
 | `ast_grep_search` | AST | 基于 AST 的模式化结构代码搜索 | 是 |
 | `ast_grep_replace` | AST | 基于模式的结构化代码转换 | 是 |
 | `python_repl` | Data | 用于数据分析和计算的持久化 Python REPL | 是 |
@@ -154,30 +154,30 @@ Task(subagent_type="ultrapower:explore",
 
 | 工具 | 直接使用时机 |
 | ------ | --------------------- |
-| `lsp_hover` | 对话中快速查询类型 |
-| `lsp_goto_definition` | 分析过程中导航到符号定义 |
-| `lsp_prepare_rename` | 在决定方案前检查重命名可行性 |
-| `lsp_rename` | 安全重命名操作（返回编辑预览，不自动应用） |
-| `lsp_code_actions` | 发现可用的重构操作 |
-| `lsp_code_action_resolve` | 获取特定代码操作的详情 |
-| `lsp_servers` | 检查语言服务器可用性 |
+| `ultrapower:lsp_hover` | 对话中快速查询类型 |
+| `ultrapower:lsp_goto_definition` | 分析过程中导航到符号定义 |
+| `ultrapower:lsp_prepare_rename` | 在决定方案前检查重命名可行性 |
+| `ultrapower:lsp_rename` | 安全重命名操作（返回编辑预览，不自动应用） |
+| `ultrapower:lsp_code_actions` | 发现可用的重构操作 |
+| `ultrapower:lsp_code_action_resolve` | 获取特定代码操作的详情 |
+| `ultrapower:lsp_servers` | 检查语言服务器可用性 |
 
 对于需要实现的复杂重命名或重构任务，委派给 `executor`（使用 `model="opus"`），它可以使用 `ast_grep_replace` 进行结构化转换。
 
 ### 工具选择指南
 
-* **需要文件符号概览或工作区搜索？** 通过 `explore` 使用 `lsp_document_symbols`/`lsp_workspace_symbols`
+* **需要文件符号概览或工作区搜索？** 通过 `explore` 使用 `ultrapower:lsp_document_symbols`/`ultrapower:lsp_workspace_symbols`
 
-* **需要查找符号的所有用法？** 通过 `explore` 使用 `lsp_find_references`
+* **需要查找符号的所有用法？** 通过 `explore` 使用 `ultrapower:lsp_find_references`
 
 * **需要结构化代码模式？**（如"查找所有匹配 X 形状的函数"）通过 `explore`、`architect` 或 `code-reviewer` 使用 `ast_grep_search`
 
 * **需要结构化代码转换？** 通过 `executor`（使用 `model="opus"`）使用 `ast_grep_replace`
 
-* **需要全项目类型检查？** 通过 `architect`、`executor` 或 `build-fixer` 使用 `lsp_diagnostics_directory`
+* **需要全项目类型检查？** 通过 `architect`、`executor` 或 `build-fixer` 使用 `ultrapower:lsp_diagnostics_directory`
 
-* **需要单文件错误检查？** 通过多个 agent 使用 `lsp_diagnostics`（参见矩阵）
+* **需要单文件错误检查？** 通过多个 agent 使用 `ultrapower:lsp_diagnostics`（参见矩阵）
 
 * **需要数据分析/计算？** 通过 `scientist` 使用 `python_repl`
 
-* **需要快速类型信息或定义查询？** 直接使用 `lsp_hover`/`lsp_goto_definition`（orchestrator 直接工具）
+* **需要快速类型信息或定义查询？** 直接使用 `ultrapower:lsp_hover`/`ultrapower:lsp_goto_definition`（orchestrator 直接工具）

package/docs/partials/features.md

@@ -59,7 +59,7 @@
 
 ## 目录诊断工具
 
-通过 `lsp_diagnostics_directory` 工具进行项目级类型检查。
+通过 `ultrapower:lsp_diagnostics_directory` 工具进行项目级类型检查。
 
 **策略：**
 

package/docs/partials/verification-tiers.md

@@ -6,7 +6,7 @@
 
 | 层级 | 标准 | Agent | 模型 | 所需证据 |
 | ------ | ---------- | ------- | ------- | ------------------- |
-| **LIGHT** | <5 个文件，<100 行，完整测试覆盖 | architect-low | haiku | lsp_diagnostics 无错误 |
+| **LIGHT** | <5 个文件，<100 行，完整测试覆盖 | architect-low | haiku | ultrapower:lsp_diagnostics 无错误 |
 | **STANDARD** | 默认（非 LIGHT 或 THOROUGH） | architect-medium | sonnet | diagnostics + 构建通过 |
 | **THOROUGH** | >20 个文件，或架构/安全变更 | architect | opus | 完整审查 + 所有测试 |
 
@@ -94,7 +94,7 @@ ELSE:
 | 声明 | 所需证据 |
 | ------- | ------------------- |
 | "已修复" | 显示现在通过的测试 |
-| "已实现" | lsp_diagnostics 无错误 + 构建通过 |
+| "已实现" | ultrapower:lsp_diagnostics 无错误 + 构建通过 |
 | "已重构" | 所有测试仍然通过 |
 | "已调试" | 定位到 file:line 的根本原因 |
 

package/docs/plans/2026-02-24-superpowers-ultrapower-integration-design.md

@@ -113,7 +113,7 @@ brainstorming 触发时的强制流程：
   verification-before-completion → [验证通过]
 
 阶段5b: 构建验证（新增）
-  build-fixer → lsp_diagnostics_directory → [零错误]
+  build-fixer → ultrapower:lsp_diagnostics_directory → [零错误]
 
 阶段6: 部署测试
   qa-tester → ultraqa循环 → [全部通过]
@@ -282,7 +282,7 @@ brainstorming 触发时的强制流程：
 
 | Agent | 关键节点 | 主推 | 备选 | 推荐理由 |
 | --- | --- | --- | --- | --- |
-| `build-fixer` agent | lsp_diagnostics 零错误后 | `qa-tester` agent | `requesting-code-review` | 构建通过进入部署测试 |
+| `build-fixer` agent | ultrapower:lsp_diagnostics 零错误后 | `qa-tester` agent | `requesting-code-review` | 构建通过进入部署测试 |
 
 ### 阶段6：部署测试
 

package/docs/plans/2026-03-02-docs-comprehensive-update.md

@@ -311,18 +311,18 @@ Total: **35 tools** exposed via `mcp__plugin_ultrapower_t__` prefix.
 ### LSP Tools (12)
 
 ```
-lsp_hover                  — Type info and docs at position
-lsp_goto_definition        — Jump to definition
-lsp_find_references        — Find all usages
-lsp_document_symbols       — File outline
-lsp_workspace_symbols      — Cross-workspace symbol search
-lsp_diagnostics            — Per-file errors/warnings
-lsp_diagnostics_directory  — Project-level type check
-lsp_servers                — List available language servers
-lsp_prepare_rename         — Check if rename is valid
-lsp_rename                 — Preview multi-file rename
-lsp_code_actions           — Available refactors/fixes
-lsp_code_action_resolve    — Get action details
+ultrapower:lsp_hover                  — Type info and docs at position
+ultrapower:lsp_goto_definition        — Jump to definition
+ultrapower:lsp_find_references        — Find all usages
+ultrapower:lsp_document_symbols       — File outline
+ultrapower:lsp_workspace_symbols      — Cross-workspace symbol search
+ultrapower:lsp_diagnostics            — Per-file errors/warnings
+ultrapower:lsp_diagnostics_directory  — Project-level type check
+ultrapower:lsp_servers                — List available language servers
+ultrapower:lsp_prepare_rename         — Check if rename is valid
+ultrapower:lsp_rename                 — Preview multi-file rename
+ultrapower:lsp_code_actions           — Available refactors/fixes
+ultrapower:lsp_code_action_resolve    — Get action details
 ```
 
 Supported languages: TypeScript, Python, Rust, Go, C/C++, Java, JSON, HTML, CSS, YAML
@@ -860,17 +860,17 @@ Directives are the highest-priority memory: they survive context compression and
 
 ### LSP Tools (12)
 
-Require a running language server. Use `lsp_servers()` to check availability.
+Require a running language server. Use `ultrapower:lsp_servers()` to check availability.
 
 ```typescript
 // Type info at cursor position
-lsp_hover({ file: "src/hooks/bridge.ts", line: 42, character: 15 })
+ultrapower:lsp_hover({ file: "src/hooks/bridge.ts", line: 42, character: 15 })
 
 // Find all usages
-lsp_find_references({ file: "src/lib/validateMode.ts", symbol: "assertValidMode" })
+ultrapower:lsp_find_references({ file: "src/lib/validateMode.ts", symbol: "assertValidMode" })
 
 // Project-wide diagnostics
-lsp_diagnostics_directory({ directory: "src/", includeWarnings: false })
+ultrapower:lsp_diagnostics_directory({ directory: "src/", includeWarnings: false })
 ```
 
 ### AST Tools (2)

package/docs/plans/2026-03-05-mcp-adoption-atomic-tasks.md

@@ -162,11 +162,11 @@ npm install --save-dev @types/node
 
 **步骤：**
 1. 创建 `src/mcp/adapters/lsp-adapter.ts`
-2. 转换 lsp_hover, lsp_goto_definition, lsp_find_references
-3. 转换 lsp_document_symbols, lsp_workspace_symbols
-4. 转换 lsp_diagnostics, lsp_diagnostics_directory
-5. 转换 lsp_servers, lsp_prepare_rename, lsp_rename
-6. 转换 lsp_code_actions, lsp_code_action_resolve
+2. 转换 ultrapower:lsp_hover, ultrapower:lsp_goto_definition, ultrapower:lsp_find_references
+3. 转换 ultrapower:lsp_document_symbols, ultrapower:lsp_workspace_symbols
+4. 转换 ultrapower:lsp_diagnostics, ultrapower:lsp_diagnostics_directory
+5. 转换 ultrapower:lsp_servers, ultrapower:lsp_prepare_rename, ultrapower:lsp_rename
+6. 转换 ultrapower:lsp_code_actions, ultrapower:lsp_code_action_resolve
 
 **验收：**
 
@@ -380,7 +380,7 @@ npm install --save-dev @types/node
 1. 创建 `src/mcp/tool-resolver.ts`
 2. 实现 `resolveTool(name: string)` 函数
 3. 支持带前缀：`mcp__plugin_ultrapower_t__lsp_hover`
-4. 支持不带前缀：`lsp_hover`
+4. 支持不带前缀：`ultrapower:lsp_hover`
 5. 支持命名空间：`ultrapower:lsp_hover`
 
 **验收：**
@@ -530,8 +530,8 @@ npm install --save-dev @types/node
 **依赖：** 1.4.1
 
 **步骤：**
-1. 测试 `lsp_hover` 调用
-2. 测试 `lsp_diagnostics` 调用
+1. 测试 `ultrapower:lsp_hover` 调用
+2. 测试 `ultrapower:lsp_diagnostics` 调用
 3. 验证参数传递正确
 4. 验证返回结果格式
 
@@ -581,7 +581,7 @@ npm install --save-dev @types/node
 **步骤：**
 1. 使用旧前缀调用工具：`mcp__plugin_ultrapower_t__lsp_hover`
 2. 使用新前缀调用工具：`ultrapower:lsp_hover`
-3. 使用无前缀调用工具：`lsp_hover`
+3. 使用无前缀调用工具：`ultrapower:lsp_hover`
 4. 验证三种方式都能成功
 
 **验收：**

package/docs/plans/2026-03-16-tech-debt-fixes.md

@@ -0,0 +1,222 @@
+# Technical Debt Fixes Implementation Plan
+
+> **For Claude:** REQUIRED SUB-SKILL: Use ultrapower:executing-plans to implement this plan task-by-task.
+
+**Goal:** Fix 4 identified technical debt items from architecture assessment (TD-1 to TD-4)
+
+**Architecture:** Prioritize P0 test stability, then address P1 deprecation warnings and platform compatibility, finally unify atomic write protection
+
+**Tech Stack:** TypeScript, Vitest, Node.js fs module, cross-platform file operations
+
+---
+
+## Task 1: Fix P0 Test Timeout Issues (TD-1)
+
+**Priority:** P0 - Blocking CI pipeline
+
+**Files:**
+- Modify: `src/features/__tests__/mcp-integration.test.ts:9`
+- Modify: `src/features/mcp-autodiscovery/__tests__/performance.test.ts:7`
+
+**Step 1: Increase timeout for MCP integration tests**
+
+```typescript
+// src/features/__tests__/mcp-integration.test.ts
+beforeAll(async () => {
+  contextManager = new UnifiedContextManager();
+  await contextManager.initialize();
+}, 30000); // Increase from 10000 to 30000ms
+```
+
+**Step 2: Increase timeout for performance tests**
+
+```typescript
+// src/features/mcp-autodiscovery/__tests__/performance.test.ts
+beforeAll(async () => {
+  // Setup code
+}, 30000); // Increase from 10000 to 30000ms
+```
+
+**Step 3: Run tests to verify fixes**
+
+Run: `npm test -- mcp-integration.test.ts performance.test.ts`
+Expected: All tests pass without timeout
+
+**Step 4: Commit**
+
+```bash
+git add src/features/__tests__/mcp-integration.test.ts src/features/mcp-autodiscovery/__tests__/performance.test.ts
+git commit -m "fix(test): increase timeout for MCP integration tests to 30s
+
+Resolves TD-1: Test timeout issues blocking CI pipeline"
+```
+
+---
+
+## Task 2: Remove LSP Tool Deprecation Warnings (TD-2)
+
+**Priority:** P1 - User experience and maintenance
+
+**Files:**
+- Modify: `src/tools/lsp-tools.ts`
+- Modify: `docs/REFERENCE.md`
+- Modify: `README.md`
+
+**Step 1: Update all documentation to use new naming**
+
+Search and replace in documentation:
+- `ultrapower:lsp_diagnostics` → `ultrapower:lsp_diagnostics`
+- `ultrapower:lsp_hover` → `ultrapower:lsp_hover`
+- (repeat for all 12 LSP tools)
+
+**Step 2: Add deprecation timeline to CHANGELOG**
+
+```markdown
+## [Unreleased]
+
+### Deprecated
+- Old LSP tool naming (without `ultrapower:` prefix) will be removed in v8.0.0
+- Users should migrate to new naming: `ultrapower:lsp_*`
+```
+
+**Step 3: Verify no old naming in docs**
+
+Run: `grep -r "ultrapower:lsp_diagnostics" docs/ README.md`
+Expected: No matches (all should use `ultrapower:lsp_diagnostics`)
+
+**Step 4: Commit**
+
+```bash
+git add docs/ README.md CHANGELOG.md
+git commit -m "docs: migrate LSP tool naming to ultrapower: prefix
+
+Resolves TD-2: Prepare for v8.0.0 deprecation removal"
+```
+
+---
+
+## Task 3: Add Windows Platform Compatibility Tests (TD-3)
+
+**Priority:** P1 - Platform compatibility
+
+**Files:**
+- Create: `tests/platform/windows-atomic-write.test.ts`
+- Modify: `src/lib/atomic-write.ts`
+
+**Step 1: Create Windows-specific test file**
+
+```typescript
+// tests/platform/windows-atomic-write.test.ts
+import { describe, it, expect } from 'vitest';
+import { atomicWriteJsonSyncWithRetry } from '../../src/lib/atomic-write';
+import { existsSync, readFileSync } from 'node:fs';
+import { join } from 'node:path';
+
+describe.skipIf(process.platform !== 'win32')('Windows atomic write', () => {
+  it('should handle locked files gracefully', async () => {
+    const testPath = join(process.cwd(), '.test-windows-lock.json');
+    const data = { test: 'value' };
+
+    // Write should succeed even if file is temporarily locked
+    atomicWriteJsonSyncWithRetry(testPath, data);
+
+    expect(existsSync(testPath)).toBe(true);
+    const content = JSON.parse(readFileSync(testPath, 'utf-8'));
+    expect(content).toEqual(data);
+  });
+});
+```
+
+**Step 2: Run Windows tests**
+
+Run: `npm test -- windows-atomic-write.test.ts`
+Expected: Tests pass on Windows, skipped on other platforms
+
+**Step 3: Document platform differences**
+
+Add to `docs/standards/runtime-protection.md`:
+
+```markdown
+### Windows Platform Notes
+
+- `renameSync` is not atomic when target file is locked
+- Directory-level `fsync` silently fails
+- Use `maxRetries` parameter in `atomicWriteJsonSyncWithRetry` for robustness
+```
+
+**Step 4: Commit**
+
+```bash
+git add tests/platform/windows-atomic-write.test.ts docs/standards/runtime-protection.md
+git commit -m "test(platform): add Windows atomic write compatibility tests
+
+Resolves TD-3: Windows platform compatibility validation"
+```
+
+---
+
+## Task 4: Unify Atomic Write Protection (TD-4)
+
+**Priority:** P2 - Consistency and safety
+
+**Files:**
+- Modify: `src/hooks/subagent-tracker/index.ts`
+
+**Step 1: Replace immediate write with atomic write**
+
+```typescript
+// src/hooks/subagent-tracker/index.ts
+import { atomicWriteJsonSyncWithRetry } from '../../lib/atomic-write';
+
+// Replace this:
+// writeFileSync(statePath, JSON.stringify(state, null, 2), "utf-8");
+
+// With this:
+atomicWriteJsonSyncWithRetry(statePath, state);
+```
+
+**Step 2: Remove writeTrackingStateImmediate function**
+
+Remove the `writeTrackingStateImmediate()` function entirely, replace all calls with `atomicWriteJsonSyncWithRetry`.
+
+**Step 3: Run tests to verify no regressions**
+
+Run: `npm test -- subagent-tracker`
+Expected: All tests pass
+
+**Step 4: Update difference documentation**
+
+Remove D-07 from `docs/standards/runtime-protection.md` (no longer a difference).
+
+**Step 5: Commit**
+
+```bash
+git add src/hooks/subagent-tracker/index.ts docs/standards/runtime-protection.md
+git commit -m "refactor(hooks): unify atomic write protection in subagent-tracker
+
+Resolves TD-4: Remove immediate write bypass, use atomic write consistently"
+```
+
+---
+
+## Verification Checklist
+
+After completing all tasks:
+
+- [ ] All tests pass: `npm test`
+- [ ] No TypeScript errors: `npm run build`
+- [ ] No lint errors: `npm run lint`
+- [ ] CI pipeline passes on GitHub Actions
+- [ ] Documentation updated for all changes
+- [ ] CHANGELOG.md includes all fixes
+
+---
+
+## Estimated Timeline
+
+- Task 1 (P0): 30 minutes
+- Task 2 (P1): 1 hour
+- Task 3 (P1): 2 hours
+- Task 4 (P2): 1 hour
+
+**Total:** ~4.5 hours