docs: remove learning objectives, exercises, prerequisites, and time estimates

Author: jfarcand

src/chapter-01-project-architecture.md

@@ -3,12 +3,6 @@
 
 # Chapter 1: Project Architecture & Module Organization
 
-> **Learning Objectives**: Understand the Pierre codebase structure, Rust module system, and how the project is organized for maintainability and scalability.
->
-> **Prerequisites**: Basic Rust syntax, familiarity with `cargo` commands
->
-> **Estimated Time**: 2-3 hours
-
 ---
 
 ## Introduction
@@ -508,12 +502,13 @@ src/
         ├── mod.rs
         └── handlers/
             ├── mod.rs
-            ├── strava_api.rs
+            ├── fitness_api.rs
             ├── intelligence.rs
             ├── goals.rs
             ├── configuration.rs
             ├── sleep_recovery.rs
             ├── nutrition.rs
+            ├── recipes.rs
             └── connections.rs
 ```
 
@@ -522,21 +517,23 @@ src/
 ```rust
 //! MCP tool handlers for all tool categories
 
-pub mod strava_api;
+pub mod fitness_api;
 pub mod intelligence;
 pub mod goals;
 pub mod configuration;
 pub mod sleep_recovery;
 pub mod nutrition;
+pub mod recipes;
 pub mod connections;
 
 // Re-export all handler functions
-pub use strava_api::*;
+pub use fitness_api::*;
 pub use intelligence::*;
 pub use goals::*;
 pub use configuration::*;
 pub use sleep_recovery::*;
 pub use nutrition::*;
+pub use recipes::*;
 pub use connections::*;
 ```
 
@@ -856,40 +853,6 @@ grep -r "pub struct" src/
 
 ---
 
-## Practical Exercises
-
-### Exercise 1: Explore Module Structure
-
-1. Open `src/lib.rs` and count the `pub mod` declarations
-2. For each protocol module (`mcp`, `a2a`, `protocols`), open its `mod.rs`
-3. Draw a mental map of 3-level deep module hierarchy
-
-**Expected output**: Understanding of how modules nest and relate
-
-### Exercise 2: Trace an Import Path
-
-1. Open `src/bin/pierre-mcp-server.rs`
-2. Find the import: `use pierre_mcp_server::mcp::multitenant::MultiTenantMcpServer`
-3. Navigate the path:
-   - `src/lib.rs` → `pub mod mcp;`
-   - `src/mcp/mod.rs` → `pub mod multitenant;`
-   - `src/mcp/multitenant.rs` → `pub struct MultiTenantMcpServer`
-
-**Expected output**: Comfortable navigating nested modules
-
-### Exercise 3: Identify Feature Flags
-
-1. Search `Cargo.toml` for `[features]` section
-2. Find all `#[cfg(feature = "...")]` in `src/database_plugins/factory.rs`
-3. Run build with different features:
-   ```bash
-   cargo build --no-default-features --features postgresql
-   ```
-
-**Expected output**: Understanding conditional compilation
-
----
-
 ## Rust Idioms Summary
 
 | Idiom | Purpose | Example Location |

src/chapter-02-error-handling.md

@@ -3,12 +3,6 @@
 
 # Chapter 2: Error Handling & Type-Safe Errors
 
-> **Learning Objectives**: Master structured error handling in Rust using `thiserror`, understand why Pierre eliminates `anyhow!()` from production code, and learn error propagation patterns.
->
-> **Prerequisites**: Chapter 1, basic understanding of `Result<T, E>` and `Option<T>`
->
-> **Estimated Time**: 3-4 hours
-
 ---
 
 ## Introduction
@@ -803,110 +797,6 @@ async fn get_user_and_validate(id: &str) -> DatabaseResult<User> {
 
 ---
 
-## Practical Exercises
-
-### Exercise 1: Define a Custom Error Type
-
-Create a configuration error type with `thiserror`:
-
-```rust
-use thiserror::Error;
-
-#[derive(Error, Debug)]
-pub enum ConfigError {
-    // TODO: Add variants for:
-    // - File not found (with path)
-    // - Invalid format (with details)
-    // - Missing required field (with field name)
-    // - Invalid value (with field and value)
-}
-```
-
-**Solution**:
-```rust
-#[derive(Error, Debug)]
-pub enum ConfigError {
-    #[error("Configuration file not found: {path}")]
-    FileNotFound { path: String },
-
-    #[error("Invalid configuration format: {details}")]
-    InvalidFormat { details: String },
-
-    #[error("Missing required field: {field}")]
-    MissingField { field: String },
-
-    #[error("Invalid value for {field}: {value}")]
-    InvalidValue { field: String, value: String },
-}
-```
-
-### Exercise 2: Implement Error Conversion
-
-Add `From<std::io::Error>` for `ConfigError`:
-
-```rust
-impl From<std::io::Error> for ConfigError {
-    fn from(err: std::io::Error) -> Self {
-        // TODO: Convert io::Error to appropriate ConfigError variant
-    }
-}
-```
-
-**Solution**:
-```rust
-impl From<std::io::Error> for ConfigError {
-    fn from(err: std::io::Error) -> Self {
-        match err.kind() {
-            std::io::ErrorKind::NotFound => Self::FileNotFound {
-                path: "unknown".to_string(),  // Could enhance with path tracking
-            },
-            _ => Self::InvalidFormat {
-                details: err.to_string(),
-            },
-        }
-    }
-}
-```
-
-### Exercise 3: Error Propagation Chain
-
-Write a function that reads and parses a JSON config file:
-
-```rust
-async fn load_json_config(path: &str) -> Result<Config, ConfigError> {
-    // TODO:
-    // 1. Read file with tokio::fs::read_to_string (returns io::Error)
-    // 2. Parse JSON with serde_json::from_str (returns serde_json::Error)
-    // 3. Use ? operator for both operations
-    // 4. Implement necessary From conversions
-}
-```
-
-**Solution**:
-```rust
-async fn load_json_config(path: &str) -> Result<Config, ConfigError> {
-    let contents = tokio::fs::read_to_string(path)
-        .await
-        .map_err(|e| match e.kind() {
-            std::io::ErrorKind::NotFound => ConfigError::FileNotFound {
-                path: path.to_string(),
-            },
-            _ => ConfigError::InvalidFormat {
-                details: e.to_string(),
-            },
-        })?;
-
-    let config: Config = serde_json::from_str(&contents)
-        .map_err(|e| ConfigError::InvalidFormat {
-            details: format!("JSON parse error: {}", e),
-        })?;
-
-    Ok(config)
-}
-```
-
----
-
 ## Rust Idioms Summary
 
 | Idiom | Purpose | Example Location |

src/chapter-03-configuration.md

@@ -3,12 +3,6 @@
 
 # Chapter 3: Configuration Management & Environment Variables
 
-> **Learning Objectives**: Master environment-driven configuration in Rust, understand type-safe config patterns, and learn how Pierre implements the algorithm selection system.
->
-> **Prerequisites**: Chapters 1-2, basic understanding of environment variables
->
-> **Estimated Time**: 2-3 hours
-
 ---
 
 ## Introduction
@@ -799,94 +793,6 @@ validated_config.use_in_production();
 
 ---
 
-## Practical Exercises
-
-### Exercise 1: Create a Custom Config Enum
-
-Define a `CacheBackend` enum for cache configuration:
-
-```rust
-#[derive(Debug, Clone, Serialize, Deserialize)]
-pub enum CacheBackend {
-    // TODO: Add variants for:
-    // - Memory (in-process LRU cache)
-    // - Redis (with connection string)
-    // - Disabled (no caching)
-}
-
-impl CacheBackend {
-    pub fn from_env() -> Self {
-        // TODO: Parse from CACHE_BACKEND environment variable
-        // Default to Memory if not set
-    }
-}
-```
-
-**Solution**:
-```rust
-#[derive(Debug, Clone, Serialize, Deserialize)]
-pub enum CacheBackend {
-    Memory,
-    Redis { connection_string: String },
-    Disabled,
-}
-
-impl CacheBackend {
-    pub fn from_env() -> Self {
-        match env::var("CACHE_BACKEND").ok() {
-            Some(s) if s.starts_with("redis://") => Self::Redis {
-                connection_string: s,
-            },
-            Some(s) if s == "disabled" => Self::Disabled,
-            _ => Self::Memory,  // Default
-        }
-    }
-}
-```
-
-### Exercise 2: Add Validation to Config Struct
-
-Implement validation for algorithm configuration:
-
-```rust
-impl AlgorithmConfig {
-    pub fn validate(&self) -> Result<(), ConfigError> {
-        // TODO: Validate that algorithm names are known
-        // Valid TSS algorithms: avg_power, normalized_power, hybrid
-        // Valid MaxHR algorithms: fox, tanaka, nes, gulati
-    }
-}
-```
-
-**Solution**:
-```rust
-impl AlgorithmConfig {
-    pub fn validate(&self) -> Result<(), ConfigError> {
-        // Validate TSS algorithm
-        match self.tss.as_str() {
-            "avg_power" | "normalized_power" | "hybrid" => {}
-            _ => return Err(ConfigError::InvalidValue {
-                field: "tss".to_string(),
-                value: self.tss.clone(),
-            }),
-        }
-
-        // Validate MaxHR algorithm
-        match self.maxhr.as_str() {
-            "fox" | "tanaka" | "nes" | "gulati" => {}
-            _ => return Err(ConfigError::InvalidValue {
-                field: "maxhr".to_string(),
-                value: self.maxhr.clone(),
-            }),
-        }
-
-        Ok(())
-    }
-}
-```
-
----
-
 ## Rust Idioms Summary
 
 | Idiom | Purpose | Example Location |