[pmwoz]

Stacked on #67, which pins the T3 contract that adds freshSession. Merge #67 first.

The Automations item in skills/poteto-mode/references/t3-adapter.md now says where scheduled runs go:

• A run that only reads and replies, such as benny's triage, uses bindToCurrentThread: false and freshSession: true. The first run makes one thread in a new worktree, and later runs post there in a fresh session.
• A run that changes code or opens a PR, such as benny's reproduce automation, uses only bindToCurrentThread: false. A one-thread task reuses its thread's worktree across runs, so each such run needs its own thread and a fresh worktree from the default branch.
• With neither set, T3 binds the task to the thread that created it and every run continues that conversation. The adapter did not say this before, so automations defaulted to it.

This follows T3's schedule_task handler at 2756da4 (OrchestratorMcpService.ts): freshSession maps to thread mode fresh_session, an unbound task has threadId: null until its first run, and an unbound task's workspace is a worktree from the default branch with startFromOrigin: true.

Bumps the version to 0.13.7.

Checks

bun run check, bun test tools (39 pass), and bun run typecheck pass.