Project sessions hide terminal reasons for startup and turn failures

## Describe the bug

A coordinated local worktree project session can surface only a generic `error` or `idle` state to its parent when startup, the first kickoff turn, or a later active turn fails. The metadata does not explain the cause or say whether the intact session can be resumed, so the parent may abandon recoverable work or replace an empty session without preserving the diagnostic cause.

## Affected version

`1.0.71-2`

## Steps to reproduce the behavior

### Startup or first-turn failure

1. Create a fresh local worktree project session with a valid autopilot kickoff.
2. Let branch and worktree creation succeed, but have the session reach terminal `error` before producing a diff.
3. Read the parent-facing session metadata. It shows a real branch and worktree path with zero changed files, but exposes neither a structured terminal reason nor a last error.
4. Send a simple follow-up message asking the session to report its error. The session immediately reaches `error` again without returning a cross-session explanation.

Verified reproduction metadata:

```text
session_id: 3b50dbcd-3543-43a3-ac03-d78e648cf1f4
state: error
changed_files: 0
terminal_reason: not exposed
last_error: not exposed
```

A sibling session created at the same time from the same base branch ran normally, so this signature was not a general failure of that base branch. The safe recovery was to archive the empty session and recreate it, which discarded the diagnostic cause.

### Later active-turn failure

1. Start a coordinated project session with a long task that performs substantial review and validation work.
2. Let the turn reach its context limit after it has committed work but before it reports completion, or send a new parent message while a resumed turn is active.
3. Observe the parent-facing session status and metadata.
4. Inspect the child directly and confirm its worktree and commit are intact and that the actual cause was context exhaustion or interruption.

The parent receives a generic failure state without the actionable cause. In one reproduction, transient model `408` errors also appeared around the interrupted turn, further obscuring the primary cause.

## Expected behavior

Parent-facing project-session metadata and tool responses should preserve a safe, structured reason for failures during startup, the first kickoff turn, and later active turns. They should also make the recovery path explicit instead of requiring the parent to infer whether to resume or replace the session.

## Acceptance criteria

- Startup, first-turn, and kickoff failures for local worktree sessions expose a structured terminal reason or last error through parent-facing session metadata.
- The create or kickoff caller receives a useful failure response instead of learning only from a later bare `error` state.
- Sending a message to a terminally errored session returns a structured cannot-wake reason instead of silently ending in `error` again.
- Metadata states whether the intact worktree and session are resumable or whether replacement is required.

## Additional context

- macOS / Apple Silicon
- In the later-turn reproductions, the committed code was not corrupted or lost.
- A fresh session could recover an intact commit, but that workaround consumes a new worktree and requires manual diagnosis.
- Please route this to the app or orchestration owner if the status translation is outside the CLI process.

首先跟踪 CLI 进程中的本地 worktree project-session 流程，包括面向 parent 的会话元数据、工具响应，以及 create 或 kickoff caller。检查启动、首次 turn、后续 turn 和 terminal-session 失败是如何转换的，然后验证结构化原因、cannot-wake 响应以及 resumable-versus-replacement 状态是否按规范公开。

由索引模型根据 Issue 内容生成。