fix: Mark memory-intensive doctests as no_run

Mark doctests that cause OOM (SIGKILL) during CI as no_run so they
compile but don't execute. These tests import complex types from
the prodigy crate which requires significant memory at runtime.

Also update zmij dependency to 1.0.7.

Files changed:
- dlq_integration.rs: Mark agent_result_to_dlq_item doctest as no_run
- env_interpolation.rs: Mark all doctests as no_run
- phases/mod.rs: Mark module-level and trait doctests as no_run
- Cargo.lock: Update zmij 1.0.6 -> 1.0.7

Author: iepathos

Cargo.lock

@@ -78,7 +78,11 @@ impl<R: CommandRunner + 'static> ClaudeExecutor for ClaudeExecutorImpl<R> {
         env_vars: HashMap<String, String>,
     ) -> Result<ExecutionResult> {
         // Handle test mode
-        let test_mode = self.test_config.as_ref().map(|c| c.test_mode).unwrap_or(false);
+        let test_mode = self
+            .test_config
+            .as_ref()
+            .map(|c| c.test_mode)
+            .unwrap_or(false);
         if test_mode {
             return self.handle_test_mode_execution(command).await;
         }
@@ -110,7 +114,11 @@ impl<R: CommandRunner + 'static> ClaudeExecutor for ClaudeExecutorImpl<R> {
 
     async fn check_claude_cli(&self) -> Result<bool> {
         // Always return true in test mode
-        let test_mode = self.test_config.as_ref().map(|c| c.test_mode).unwrap_or(false);
+        let test_mode = self
+            .test_config
+            .as_ref()
+            .map(|c| c.test_mode)
+            .unwrap_or(false);
         if test_mode {
             return Ok(true);
         }

src/cook/execution/claude.rs

@@ -46,7 +46,7 @@ use std::collections::HashMap;
 ///
 /// # Example
 ///
-/// ```
+/// ```no_run
 /// use prodigy::cook::execution::mapreduce::dlq_integration::agent_result_to_dlq_item;
 /// use prodigy::cook::execution::mapreduce::agent::types::{AgentResult, AgentStatus};
 /// use serde_json::json;

src/cook/execution/mapreduce/dlq_integration.rs

@@ -17,7 +17,7 @@ use std::collections::HashMap;
 /// - Named variables: `ARG_1`, `ARG_2`, `ARG_3`, etc. (for `${ARG_1}` syntax)
 ///
 /// # Examples
-/// ```
+/// ```no_run
 /// use prodigy::cook::execution::mapreduce::env_interpolation::build_positional_args_context;
 /// let args = vec!["file.txt".to_string(), "output.txt".to_string()];
 /// let context = build_positional_args_context(&args);
@@ -46,7 +46,7 @@ pub fn build_positional_args_context(args: &[String]) -> InterpolationContext {
 /// Interpolate a single environment variable value with positional arguments
 ///
 /// # Examples
-/// ```
+/// ```no_run
 /// use prodigy::cook::execution::mapreduce::env_interpolation::{build_positional_args_context, interpolate_env_value};
 /// use prodigy::cook::execution::interpolation::InterpolationEngine;
 ///
@@ -74,7 +74,7 @@ pub fn interpolate_env_value(
 /// and returns a new map with interpolated values.
 ///
 /// # Examples
-/// ```
+/// ```no_run
 /// use std::collections::HashMap;
 /// use prodigy::cook::execution::mapreduce::env_interpolation::interpolate_workflow_env_with_positional_args;
 ///
@@ -127,7 +127,7 @@ pub fn interpolate_workflow_env_with_positional_args(
 /// This is separate from interpolation - these are raw positional arg values.
 ///
 /// # Examples
-/// ```
+/// ```no_run
 /// use prodigy::cook::execution::mapreduce::env_interpolation::positional_args_as_env_vars;
 ///
 /// let args = vec!["file.txt".to_string(), "output.txt".to_string()];
@@ -152,7 +152,7 @@ pub fn positional_args_as_env_vars(positional_args: &[String]) -> HashMap<String
 /// Convert EnvValue map to plain string map (for MapPhase.workflow_env)
 ///
 /// # Examples
-/// ```
+/// ```no_run
 /// use std::collections::HashMap;
 /// use prodigy::cook::environment::EnvValue;
 /// use prodigy::cook::execution::mapreduce::env_interpolation::env_values_to_plain_map;

src/cook/execution/mapreduce/env_interpolation.rs

@@ -9,7 +9,7 @@
 //! To add a new custom phase type to the MapReduce workflow:
 //!
 //! 1. **Define the Phase Type**: Add a new variant to the `PhaseType` enum:
-//!    ```rust
+//!    ```rust,no_run
 //!    pub enum PhaseType {
 //!        Setup,
 //!        Map,
@@ -19,7 +19,7 @@
 //!    ```
 //!
 //! 2. **Implement PhaseExecutor**: Create a new executor for your phase:
-//!    ```rust
+//!    ```rust,no_run
 //!    # use prodigy::cook::execution::mapreduce::phases::{PhaseExecutor, PhaseContext, PhaseResult, PhaseError, PhaseType};
 //!    # use async_trait::async_trait;
 //!    pub struct PostProcessPhaseExecutor {
@@ -78,7 +78,7 @@
 //!
 //! You can customize phase transitions by implementing `PhaseTransitionHandler`:
 //!
-//! ```rust
+//! ```rust,no_run
 //! # use prodigy::cook::execution::mapreduce::phases::{PhaseTransitionHandler, PhaseType, PhaseContext, PhaseError, PhaseTransition, PhaseResult};
 //! struct CustomTransitionHandler;
 //!
@@ -266,7 +266,7 @@ pub enum PhaseError {
 ///
 /// # Example Implementation
 ///
-/// ```rust
+/// ```rust,no_run
 /// # use prodigy::cook::execution::mapreduce::phases::{PhaseExecutor, PhaseContext, PhaseResult, PhaseError, PhaseType, PhaseMetrics};
 /// # use async_trait::async_trait;
 /// # use serde_json::json;