Add comprehensive MkDocs documentation structure with GitHub Pages support

[devin-ai-integration]

Add comprehensive MkDocs documentation structure with GitHub Pages support

Summary

This PR creates a complete MkDocs documentation website for the Talos project, organizing all existing documentation into a comprehensive, user-friendly structure. The documentation is built using the Material theme and includes 23 new files covering getting started guides, architecture explanations, CLI references, development guidelines, project philosophy, and detailed API documentation.

Key Changes:

• Complete docs/ directory structure with 6 main sections: Getting Started, Architecture, CLI Reference, Development, Philosophy, and API Reference
• MkDocs configuration (mkdocs.yml) with Material theme, search, code highlighting, and navigation
• GitHub Actions workflow (.github/workflows/docs.yml) for automated GitHub Pages deployment
• Consolidated content from existing files (README.md, AGENTS.md, PERFORMANCE_ANALYSIS.md, CLI_GITHUB_COMMANDS.md, etc.) into organized sections
• Comprehensive API reference for core, services, and tools layers with code examples
• Development guides including contributing guidelines, code style, testing practices, and performance optimization

The documentation structure follows modern practices seen in projects like Quix Streams and provides a complete foundation for GitHub Pages hosting.

Review & Testing Checklist for Human

⚠️ CRITICAL: This PR contains extensive content that needs verification against the actual codebase.

• Verify API documentation accuracy - Check that all API references, class definitions, method signatures, and code examples in docs/api/ match the actual implementation in src/talos/
• Test MkDocs functionality - Run mkdocs build and mkdocs serve locally to ensure the site builds and renders correctly with proper navigation
• Test GitHub Actions workflow - Verify the workflow in .github/workflows/docs.yml deploys successfully to GitHub Pages (may need to enable Pages in repo settings)
• Review content organization - Verify the navigation structure and content organization meets project needs and user expectations
• Validate all links - Check that all internal links, references, and navigation paths work correctly throughout the documentation

Recommended Test Plan:

1. Clone the branch and run mkdocs build --strict to verify build succeeds without warnings
2. Run mkdocs serve and navigate through all sections to check for broken links or formatting issues
3. Cross-reference API documentation in docs/api/ against actual source code in src/talos/
4. Test the GitHub Actions workflow by merging to main and verifying Pages deployment
5. Review the overall documentation structure against the original Quix Streams example for style consistency

---

Diagram

%%{ init : { "theme" : "default" }}%%
graph TD
    Root["talos/"]:::context
    MkDocsConfig["mkdocs.yml"]:::major-edit
    DocsDir["docs/"]:::major-edit
    WorkflowFile[".github/workflows/docs.yml"]:::major-edit
    
    DocsDir --> GetStarted["docs/getting-started/"]:::major-edit
    DocsDir --> Architecture["docs/architecture/"]:::major-edit
    DocsDir --> CLI["docs/cli/"]:::major-edit
    DocsDir --> Development["docs/development/"]:::major-edit
    DocsDir --> Philosophy["docs/philosophy/"]:::major-edit
    DocsDir --> API["docs/api/"]:::major-edit
    
    GetStarted --> Overview["overview.md"]:::major-edit
    GetStarted --> Install["installation.md"]:::major-edit
    GetStarted --> Quick["quickstart.md"]:::major-edit
    
    API --> CoreAPI["core.md"]:::major-edit
    API --> ServicesAPI["services.md"]:::major-edit
    API --> ToolsAPI["tools.md"]:::major-edit
    
    Development --> Contributing["contributing.md"]:::major-edit
    Development --> CodeStyle["code-style.md"]:::major-edit
    Development --> Testing["testing.md"]:::major-edit
    
    ExistingFiles["README.md<br/>AGENTS.md<br/>PERFORMANCE_ANALYSIS.md"]:::context
    ExistingFiles -.->|"content extracted"| DocsDir
    
    MkDocsConfig -.->|"configures"| DocsDir
    WorkflowFile -.->|"deploys"| DocsDir
    
    subgraph Legend
        L1["Major Edit"]:::major-edit
        L2["Minor Edit"]:::minor-edit  
        L3["Context/No Edit"]:::context
    end

    classDef major-edit fill:#90EE90
    classDef minor-edit fill:#87CEEB
    classDef context fill:#FFFFFF

Loading

Notes

Content Sources: Documentation content was derived from existing files including README.md, AGENTS.md, PERFORMANCE_ANALYSIS.md, CLI_GITHUB_COMMANDS.md, src/talos/cli/README.md, and talos_prompt.md. Some content was interpreted and expanded based on these sources, which creates a risk that the API documentation may not perfectly match the actual implementation.

Testing Status: Successfully tested mkdocs build (builds in 1.63 seconds), but mkdocs serve testing was limited due to port conflicts in the development environment. The GitHub Actions workflow has not been tested in the actual GitHub environment yet.

GitHub Pages Setup: The workflow assumes GitHub Pages is enabled for the repository. The repository owner may need to enable Pages in the repository settings and configure it to deploy from GitHub Actions.

---

Link to Devin run: https://app.devin.ai/sessions/d79e030c16e2450c9b21b6260f1a1cfa
Requested by: @talos-agent

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring