Add a whole-run deadline to CLI execution

docs/cli.md

@@ -64,6 +64,7 @@ Optional flags:
 | `--top-p <float>` | Runtime top-p override. |
 | `--reasoning-effort <value>` | Runtime reasoning-effort override. |
 | `--timeout <duration>` | Runtime timeout override using Go duration syntax. |
+| `--run-timeout <duration>` | Optional whole-run engine deadline using Go duration syntax; zero or omission adds no deadline, negative values are invalid. |
 | `--transient-retries <integer>` | Nonnegative additional transient attempt count for this request; `0` disables additional attempts. |
 
 Deprecated aliases: `--prompt-id` for `--prompt`, and `--profile-id` for
@@ -78,6 +79,13 @@ zero-second override. The timeout layers are defined in the
 [Promptkit outbound integration contract](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/integrations/openai-compatible-chat.md#timeout-and-cancellation).
 With the built-in client, each transient retry gets a fresh generation timeout;
 this flag does not limit the complete run.
+`--run-timeout` keeps subsecond precision and starts immediately before engine
+execution. It bounds preparation, capacity waits, retry waits, generation, and
+repairs where they honor context. Parsing, engine construction, and output
+writes are outside that interval. A failed run whose execution context reaches
+this deadline exits 1 with a safe deadline diagnostic; a completed invalid
+output still exits 2. It does not promise immediate interruption of synchronous
+work.
 Omitting `--transient-retries` inherits the application setting or Promptkit's
 current default of two additional attempts. The flag overrides only this
 request; it does not alter the configured engine. Structural repair generations