feat: migrate to unified documentation structure

[eoln]

Summary

This PR migrates the documentation from package-specific structure to a unified monorepo documentation site, solving pre-commit hook issues and improving maintainability.

Changes

🏗️ Infrastructure

• Created root-level MkDocs configuration for entire monorepo
• Moved eol-rag-context docs to unified structure at docs/packages/
• Added root-level pre-commit hooks for documentation validation
• Moved validate_docs.py script to root scripts/ directory

📚 Documentation

• Created comprehensive landing page for EOL Framework
• Added package overview with roadmap for future packages
• Created getting-started guides (installation, quickstart, configuration)
• Added placeholder pages for planned packages (eol-core, eol-cli, eol-sdk)

✅ Fixes

• Pre-commit hooks now work correctly from root directory
• Documentation validation runs from any location
• Paths are consistent across the monorepo

Benefits

• Single documentation site for entire framework
• Better navigation between packages with unified structure
• Pre-commit hooks work from any directory
• Easier maintenance with single MkDocs config
• Scalable structure for adding new packages

Testing

• Documentation builds successfully: mkdocs build --strict
• Documentation serves locally: mkdocs serve
• Pre-commit hooks pass from root directory
• All internal links work correctly

Screenshots

The documentation structure now looks like:

eol/
├── mkdocs.yml              # Root-level config
├── docs/                   # All documentation
│   ├── packages/          # Package-specific docs
│   │   ├── eol-rag-context/
│   │   ├── eol-core/
│   │   └── eol-cli/
│   ├── getting-started/   # Unified guides
│   └── architecture/      # System docs
└── scripts/
    └── validate_docs.py   # Single validator

Next Steps

After merging this PR:

1. Deploy to GitHub Pages with mkdocs gh-deploy
2. Update CI/CD workflows to use new structure
3. Remove old package-level MkDocs configs

🤖 Generated with Claude Code