升级本机 Trellis 至 0.6.12（upgrade-trellis-0-6-12）

.codex/agents/trellis-check.toml

@@ -17,9 +17,11 @@ CRITICAL — Recursion guard (read first):
 You are the Trellis reviewer agent.
 
 Trellis Context Loading Protocol:
-- Look for the `<!-- trellis-hook-injected -->` marker in your input above.
-- If the marker is present, the native `SubagentStart` hook has already loaded the role-specific task artifacts and spec context. Proceed directly with the check work.
-- If the marker is absent, 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.
+- First look for `Full hook output saved to: <path>` in your input above. If present, the visible `SubagentStart` output was truncated; read the referenced file before doing check work.
+- If the referenced file cannot be read, use the active-task fallback below.
+- If there is no saved-output notice and the `<!-- trellis-hook-injected -->` marker is present, the hook loaded the complete role-specific task artifacts and spec context.
+- 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.
 

.codex/agents/trellis-implement.toml

@@ -17,9 +17,11 @@ CRITICAL — Recursion guard (read first):
 You are the Trellis implementer agent.
 
 Trellis Context Loading Protocol:
-- Look for the `<!-- trellis-hook-injected -->` marker in your input above.
-- If the marker is present, the native `SubagentStart` hook has already loaded the role-specific task artifacts and spec context. Proceed directly with the implementation work.
-- If the marker is absent, find `Active task: <path>` in your dispatch prompt. Read `<path>/implement.jsonl`, each file listed there, `<path>/prd.md`, `<path>/design.md` if present, and `<path>/implement.md` if present before doing the work. If the dispatch prompt has no active-task path, ask the main session; do not guess or use another session's task.
+- First look for `Full hook output saved to: <path>` in your input above. If present, the visible `SubagentStart` output was truncated; read the referenced file before doing implementation work.
+- If the referenced file cannot be read, use the active-task fallback below.
+- If there is no saved-output notice and the `<!-- trellis-hook-injected -->` marker is present, the hook loaded the complete role-specific task artifacts and spec context.
+- 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>/implement.jsonl`, each file listed there, `<path>/prd.md`, `<path>/design.md` if present, and `<path>/implement.md` if present before doing the work. If the dispatch prompt has no active-task path, ask the main session; do not guess or use another session's task.
 
 Rules:
 - Read before write. Follow `.trellis/spec/` guidance relevant to the task.

.codex/agents/trellis-research.toml

@@ -15,12 +15,17 @@ through the chat reply is a failure.
 
 ## Trellis Context Loading Protocol
 
-Look for the `<!-- trellis-hook-injected -->` marker in your input above.
-
-- If the marker is present, the native `SubagentStart` hook has supplied the
-  `Active task: <path>` header and research-only context. Use that task path.
-- If the marker is absent, find `Active task: <path>` in your dispatch prompt.
-  If it is absent too, ask the main session for the path; do not run
+- First look for `Full hook output saved to: <path>` in your input above. If
+  present, the visible `SubagentStart` output was truncated; read the referenced
+  file before doing research work.
+- If the referenced file cannot be read, use the active-task fallback below.
+- If there is no saved-output notice and the
+  `<!-- trellis-hook-injected -->` marker is present, the hook supplied the
+  complete `Active task: <path>` header and research-only context.
+- 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. If it
+  is absent too, ask the main session for the path; do not run
   `task.py current`, guess, or use another session's task.
 - Do not load `implement.jsonl` or `check.jsonl`; research is role-isolated.
 

.codex/hooks/inject-subagent-context.py

@@ -32,6 +32,14 @@ import sys
 from pathlib import Path
 from typing import Any
 
+# Hook hosts send UTF-8 JSON regardless of the process locale.
+_stdin_reconfigure = getattr(sys.stdin, "reconfigure", None)
+if callable(_stdin_reconfigure):
+    try:
+        _stdin_reconfigure(encoding="utf-8", errors="replace")
+    except (OSError, ValueError):
+        pass
+
 # IMPORTANT: Force stdout to use UTF-8 on Windows
 # This fixes UnicodeEncodeError when outputting non-ASCII characters
 if sys.platform.startswith("win"):