[DeusData]

What does this PR do?

Make the MCP server the clear center of Codebase Memory's README and website: persistent code, documentation and infrastructure context for AI coding agents, with 17 MCP tools and native CLI access. Keep the visuals near the top while identifying CBM Lens as the optional open-beta companion, currently v0.0.1. A brief token-use benefit appears near the top; numerical results stay in the evidence section, attributed to the March 2026 preprint and its evaluated workloads.

• Align page, social and structured metadata; distinguish the application from its source repository.
• Add practical workflow and token-use FAQs, explicit screenshot dimensions, a discoverable plain-text facts page, and an accurate sitemap modification date.
• Add Discord badges to the README and website, and invite the OSS community to contact DeusData or the co-developers directly when a conversation works better.
• Reuse the README's architecture, Galaxy and local-chat GIF walkthroughs, with still-image alternatives for reduced-motion preferences and lazy loading below the hero.
• Integrate matching Discord and Star on GitHub controls into the main desktop header. On mobile, keep the brand and primary action together above two balanced community controls.
• Present core MCP capabilities, Smart CI and agent setup before the detailed Lens showcase.

The approach follows Google's AI search guidance and Bing's guidance on clear, evidenced content. Measurements are sourced to the March 2026 preprint. No ranking guarantees or universal savings percentage are introduced.

Validation

• Focused static validation passed: metadata and canonical URL, internal links, image dimensions and assets, reduced-motion image sources, JSON-LD types and references, sitemap, community badges, four-file scope and diff whitespace.
• Browser checks from 320px to 1440px, including both sides of the tablet breakpoint, found no horizontal overflow or overlapping navigation controls.
• Executable website JavaScript is unchanged.
• Full local CI and C/lint suites were not run under the maintainer's explicit documentation-only validation exception. Search indexing and ranking outcomes are not asserted.

Checklist

• Every commit is signed off.
• Relevant documentation and website checks pass.
• Full C test suite — not run under the documentation-only exception.
• C lint — not run under the documentation-only exception.
• No runtime behavior changed; focused validation covers the edited document contracts.