Align dependency docs with changelog

Co-authored-by: Tuntii <121901995+Tuntii@users.noreply.github.com>

Author: Copilot

docs/PHILOSOPHY.md

@@ -96,7 +96,7 @@ validator = "0.16"
 |-----------|----------------|--------------|
 | HTTP Server | `hyper 1.x` | `hyper 2.x`, `h3` (HTTP/3) |
 | Async Runtime | `tokio` | `smol`, `async-std` (future) |
-| Validation | `validator` | Custom engine (planned for v1.0) |
+| Validation | `rustapi-validate` | Custom engine (available) |
 | Router | `matchit` | Custom radix tree |
 | OpenAPI | `utoipa` | Native implementation |
 
@@ -114,7 +114,6 @@ RustAPI already hides external crates behind internal adapters. To reduce depend
 3. Ship replacements behind feature flags, then flip defaults.
 
 Good candidates for in-house implementations:
-- Validation (`validator`) → native validation engine (already planned).
 - Router (`matchit`) → internal radix tree with RustAPI-specific optimizations.
 - OpenAPI (`utoipa`) → native schema generator to control outputs.
 - TOON format (`toon-format`) → move core format logic into `rustapi-toon`.

docs/README.md

@@ -26,11 +26,11 @@ RustAPI is an ergonomic web framework for Rust, inspired by FastAPI's developer
 
 > *"API surface is ours, engines can change."*
 
-RustAPI provides a stable, ergonomic public API. Internal dependencies (`hyper`, `tokio`, `validator`) are implementation details that can be upgraded without breaking your code.
+RustAPI provides a stable, ergonomic public API. Internal dependencies (e.g., `hyper`, `tokio`, `matchit`) are implementation details that can be upgraded without breaking your code.
 
 ### External Dependency Plan
 
-To reduce external dependency debt (bağımlılık borcu), we prioritize replacing crates with stable specs and small surfaces, while keeping the public API unchanged. Candidate areas for RustAPI-owned implementations are validation, routing, OpenAPI generation, and the TOON format. Foundational runtime and HTTP crates (`tokio`, `hyper`, `tower`) remain external for stability and security.
+To reduce external dependency debt, we prioritize replacing crates with stable specs and small surfaces, while keeping the public API unchanged. Validation already uses the native `rustapi-validate` engine; candidates for further RustAPI-owned implementations are routing, OpenAPI generation, the TOON format, and template rendering. Foundational runtime and HTTP crates (`tokio`, `hyper`, `tower`) remain external for stability and security.
 
 ## Getting Started