feat(web): Landing page — Features section (deploy, state, tools, security)

[duyetbot]

Goal

Landing page features section that explains what OMA does — not just "what it is" but "what you can do with it."

Features to highlight

🚀 Deploy Everywhere

Run agents on Cloudflare Workers (edge), your own Kubernetes cluster, a Docker host, or a random VM. Agents follow the workload, not the other way around.

graph LR
    A[Agent] --> B{OMA Platform}
    B --> C[Cloudflare]
    B --> D[Kubernetes]
    B --> E[Docker]
    B --> F[Bare Metal]

Loading

💾 Managed State

Sessions survive crashes, restarts, and deploys. The event log (SQLite + Durable Objects) means you never lose context. Agent resumes exactly where it left off.

🔧 Tool Ecosystem

• 8 built-in tools (bash, read, write, edit, web_search, web_fetch, glob, grep)
• MCP server support (Linear, GitHub, Slack, or any SSE MCP server)
• Custom tools with JSON Schema validation
• Multi-agent delegation (call_agents_parallel)

🔒 Security Built-in

• Credentials never enter the sandbox (outbound proxy injection)
• Encrypted vaults (AES-256-GCM)
• Per-tenant isolation
• Granular RBAC

📊 Observability

• Session streaming (SSE)
• Token usage tracking
• Session replay from event log
• Outcome evaluation framework

Visual layout

4-column card grid at desktop, 2-column tablet, single-column mobile.
Each card has: icon, title, 2-sentence description, "Learn more →" link.

Acceptance

• Each feature is understandable in one glance
• Links go to corresponding docs pages
• Mermaid diagrams render in the Astro site

[duyet]

Shipped: features section (Everything You Need / Why OMA / API compatibility) lives on /features; the landing page keeps a compact overview + explore cards (PR #283). Closing.