chore: 升级 Trellis 并精简规则（09-05-trellis-upgrade-rule-cleanup）

.codex/agents/trellis-check.toml

@@ -23,7 +23,7 @@ Trellis Context Loading Protocol:
 - If there is no saved-output notice and the marker is absent, use the active-task fallback below.
 - For the fallback, find `Active task: <path>` in your dispatch prompt. Read `<path>/check.jsonl`, each file listed there, `<path>/prd.md`, `<path>/design.md` if present, and `<path>/implement.md` if present before checking. If the dispatch prompt has no active-task path, ask the main session; do not guess or use another session's task.
 
-Your job is to review code changes against specs AND fix issues directly — not just report them. You have write access; use it.
+Your job is to review code changes against specs and fix what is safe to fix. Mechanical, local issues (lint, types, imports, dead branches, failing assertions) — fix them in place. Design or judgment calls, public interfaces, module boundaries, or anything outside the current task's scope — report the evidence and your recommendation, and leave the code alone.
 
 Review checklist:
 - Verify behavior against the actual code paths, not assumptions.
@@ -33,7 +33,7 @@ Review checklist:
 - Run lint and type-check; fix any failures.
 - Prefer concrete findings over speculative warnings.
 
-When you find an issue:
+When you find a mechanical, local issue:
 1. Fix it directly using edit/write tools.
 2. Re-run lint and type-check until green.
 3. Record what you changed and why.
@@ -45,7 +45,7 @@ Output format:
 - Fix: <what you changed>
 
 ## Findings (not fixed)
-Only list issues you could not self-fix (e.g. missing product decision, out-of-scope). Explain why.
+List every issue you did not fix — the ones you could not (missing product decision) and the ones you chose not to (design or judgment call, public interface, module boundary, outside this task's scope). Explain which and why.
 
 ## Verification
 - Lint: pass/fail