docs: finalize v0.1.0 documentation with framework leak detection

Updates across all documentation files:

CHANGELOG.md:
- Add Framework Leak Detection as implemented feature in v0.1.0
- Update test count: 159 → 194 tests across 7 files
- Update examples count: 36 → 38 files (29 good + 9 bad)
- Remove framework leak from future releases

README.md:
- Add Framework Leak Detection section in Features
- Document supported frameworks: HTTP, ORM/DB, External services
- Include examples of Express, Prisma, TypeORM, etc.
- Emphasize domain boundary protection

ROADMAP.md:
- Move Framework Leak Detection from v0.2.0 to v0.1.0
- Update v0.1.0 metrics: 194 tests, 38 examples
- Renumber future versions (Entity Exposure now v0.2.0)
- Maintain proper version sequence through v1.0.0

CLAUDE.md:
- Update project description with framework leak detection
- Add to Key features list (5 features total)
- Update Guardian capabilities overview

TODO.md:
- Update current tasks and priorities

All documentation now accurately reflects v0.1.0 release with 5 core features:
1. Hardcode Detection
2. Circular Dependency Detection
3. Naming Convention Enforcement
4. Architecture Violations
5. Framework Leak Detection

packages/guardian/README.md

@@ -34,6 +34,14 @@ Code quality guardian for vibe coders and enterprise teams - because AI writes f
 - Smart exclusions for base classes
 - Helpful fix suggestions
 
+🔌 **Framework Leak Detection**
+- Detects framework-specific imports in domain layer
+- Identifies HTTP frameworks (Express, Fastify, Koa, Hapi, NestJS)
+- Catches ORM/Database leaks (Prisma, TypeORM, Sequelize, Mongoose, Drizzle)
+- Detects external service dependencies (AWS SDK, Firebase, Stripe, Twilio)
+- Maintains clean domain boundaries
+- Prevents infrastructure coupling in business logic
+
 🏗️ **Clean Architecture Enforcement**
 - Built with DDD principles
 - Layered architecture (Domain, Application, Infrastructure)