Update LazyCodex web copy

[alpoxdev]

Summary

• Refresh landing copy to match the current README positioning: OmO agent harness for Codex, project memory, parallel agents, and verified completion
• Update docs copy that still described LazyCodex as a Hephaestus-only light port
• Update the -loop syntax and GitHub stars fallback, and note the web package is on Next.js 16

Validation

• pnpm exec node ./scripts/generate-docs-content.mjs
• pnpm lint
• pnpm type-check
• pnpm build
• pnpm test:e2e -- e2e/landing.spec.ts e2e/docs.spec.ts e2e/responsive.spec.ts (expanded to full suite): 59 passed, including Lighthouse mobile/desktop 100/100/100/100
• Local HTTP smoke on http://127.0.0.1:3020/ and /docs confirmed refreshed copy and 2.4k stars fallback

---

Summary by cubic

Refreshes the website and docs to position LazyCodex as the OmO agent harness for Codex with project memory, parallel agents, and verified completion. Also updates command docs, the GitHub stars fallback, and README to reflect current behavior (including Next.js 16).

• Refactors
  • Rewrote landing and docs to cover agent roles beyond Hephaestus, delegation/orchestration, team mode, and durable boulder state.
  • Updated site copy, pillars, and skills list; highlights diagnostics, MCP tools, and project memory via lazycodex-ai.
  • Documented $ulw-loop option: --completion-promise=TEXT; raised FALLBACK_GITHUB_STARS to 2,375.
  • README now notes packages/web on Next.js 16.

^{Written for commit c233b60. Summary will update on new commits.}

[github-actions]

Thanks for the PR! Changes to LazyCodex land through oh-my-openagent — could you open this against omo-codex over there instead? PRs in this repository can't be merged.

If you're working with a coding agent, prompt it like this:

I opened #109 ("Update LazyCodex web copy") against code-yeongyu/lazycodex, but changes there land through code-yeongyu/oh-my-openagent, where the Codex implementation lives under packages/omo-codex. Read my original PR, then open an equivalent PR against code-yeongyu/oh-my-openagent. In the new PR body, link the original PR (#109), explain that it was first opened against lazycodex, and describe in detail what that PR changed and why.