fix: harden workflow execution recovery

README.md

@@ -117,6 +117,14 @@ Retry executor resume after clearing an external session conflict.
 agent-workflow retry-execute --run <run-id>
 ```
 
+If a failed Claude launch recorded a session ID that was never created, explicitly bind a known persisted Claude session from the same repository and frozen plan while retrying:
+
+```bash
+agent-workflow retry-execute --run <run-id> --session <claude-session-id>
+```
+
+The override is accepted only for Claude runs. The session JSONL must exist under `~/.claude/projects`, belong to the run repository, and contain the frozen plan title. Baseline, scope, and review-artifact gates still apply, and the old/new session IDs are appended to the workflow audit log.
+
 ### `agent-workflow status`
 
 Display current workflow status.
@@ -202,6 +210,8 @@ Create `agent-workflow.json` in your repository root:
 }
 ```
 
+`timeoutSeconds` is an inactivity timeout, not a total runtime limit. The host resets the timeout whenever the executor emits stdout/stderr progress, so an active task may run longer than the configured window. A continuously silent executor is terminated after the configured number of seconds. Agy receives a 24-hour internal print-mode ceiling while the host inactivity timeout remains the primary stuck-process guard.
+
 - `defaultVcs` - Default VCS kind: `"auto"` (detect), `"git"`, `"svn"`, or `"none"`. Default is `"auto"`.
 
 ## Environment Variables
@@ -213,8 +223,9 @@ The Agy adapter runs its non-interactive implementation sessions with
 `--dangerously-skip-permissions`. This is required because Agy cannot prompt for
 tool approval in `--print` mode. The workflow's frozen scope, Git gates, and
 executor safety prompt remain the authorization boundary. Its internal
-`--print-timeout` is set from the workflow `timeoutSeconds` value so long tasks
-do not fall back to Agy's five-minute default.
+`--print-timeout` is set to a 24-hour internal ceiling so active tasks do not
+fall back to Agy's five-minute default; the workflow inactivity timeout remains
+the primary guard.
 
 ## State Machine