🎨 style(markdown): format all markdown files with prettier

- 使用 prettier 格式化所有 markdown 文件
- prose-wrap: always, print-width: 80
- 保持代码块和表格格式
- 提升可读性和一致性

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

codex/skills/root-cause-tracing/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: root-cause-tracing
-description: "Root cause analysis (RCA) and tracing failures back to the original trigger across layers. Triggers: root cause, RCA, tracing, 回溯, 根因, 追溯, 为什么会发生."
+description:
+  "Root cause analysis (RCA) and tracing failures back to the original trigger
+  across layers. Triggers: root cause, RCA, tracing, 回溯, 根因, 追溯,
+  为什么会发生."
 ---
 
 # Root Cause Tracing（根因溯源 / RCA）
@@ -21,22 +24,18 @@ description: "Root cause analysis (RCA) and tracing failures back to the origina
 ## Procedure（default）
 
 1. **Frame the Failure**
-
    - Define expected vs actual behavior
    - Identify the earliest known bad signal
 
 2. **Trace Backwards**
-
    - Walk back through layers: surface error → caller → upstream trigger
    - Look for the first point where invariants were violated
 
 3. **Find the Trigger**
-
    - What input/state/sequence causes it?
    - What changed around that area (code/config/deps/data)?
 
 4. **Fix at the Right Layer**
-
    - Prefer root-cause fix + defense-in-depth guardrails
    - Add regression test or a deterministic repro harness