Restore GitHub Pages with Redis Agent Memory landing page

[abrookins]

Summary

• restore the GitHub Pages deployment with a new one-page MkDocs build
• direct visitors to the supported Redis Agent Memory product and official documentation
• keep the original open-source server documentation unpublished and link to its Markdown source on GitHub

The landing page uses a separate MkDocs configuration and source directory. This prevents the legacy V0/docs/ content from entering the published artifact.

How Has This Been Tested?

• pre-commit run --all-files
• strict MkDocs build with mkdocs build --config-file mkdocs.pages.yml --clean --strict
• verified every external landing-page link returns HTTP 200
• previewed the generated page through the local MkDocs server

Linked Items

None.

Breaking Changes

None.

---

Note

Low Risk
Documentation and CI-only changes; no application runtime, auth, or data paths affected.

Overview
Restores GitHub Pages with a dedicated one-page MkDocs site instead of publishing legacy V0/docs/.

A new .github/workflows/docs.yml workflow builds on push/PR when V0/landing/**, V0/mkdocs.pages.yml, or the workflow file change; on main it uploads V0/site and deploys via GitHub Pages (pages / id-token permissions, mkdocs-material, strict mkdocs build).

V0/mkdocs.pages.yml points docs_dir at landing and sets the published URL to https://redis.github.io/agent-memory-server/, isolating the artifact from open-source server docs.

V0/landing/index.md is the public landing: product positioning, links to official Redis Agent Memory / Iris docs, and a section that routes OSS users to GitHub source and V0/docs Markdown rather than hosting that tree on Pages.

^{Reviewed by Cursor Bugbot for commit 8c09e4f. Bugbot is set up for automated code reviews on this repo. Configure here.}