#22612: Claude/hive landing page c tqx s

## Summary Describe the problem and fix in 2–5 bullets: - Problem: - Why it matters: - What changed: - What did NOT change (scope boundary): ## Change Type (select all) - [ ] Bug fix - [ ] Feature - [ ] Refactor - [ ] Docs - [ ] Security hardening - [ ] Chore/infra ## Scope (select all touched areas) - [ ] Gateway / orchestration - [ ] Skills / tool execution - [ ] Auth / tokens - [ ] Memory / storage - [ ] Integrations - [ ] API / contracts - [ ] UI / DX - [ ] CI/CD / infra ## Linked Issue/PR - Closes # - Related # ## User-visible / Behavior Changes List user-visible changes (including defaults/config). If none, write `None`. ## Security Impact (required) - New permissions/capabilities? (`Yes/No`) - Secrets/tokens handling changed? (`Yes/No`) - New/changed network calls? (`Yes/No`) - Command/tool execution surface changed? (`Yes/No`) - Data access scope changed? (`Yes/No`) - If any `Yes`, explain risk + mitigation: ## Repro + Verification ### Environment - OS: - Runtime/container: - Model/provider: - Integration/channel (if any): - Relevant config (redacted): ### Steps 1. 2. 3. ### Expected - ### Actual - ## Evidence Attach at least one: - [ ] Failing test/log before + passing after - [ ] Trace/log snippets - [ ] Screenshot/recording - [ ] Perf numbers (if relevant) ## Human Verification (required) What you personally verified (not just CI), and how: - Verified scenarios: - Edge cases checked: - What you did **not** verify: ## Compatibility / Migration - Backward compatible? (`Yes/No`) - Config/env changes? (`Yes/No`) - Migration needed? (`Yes/No`) - If yes, exact upgrade steps: ## Failure Recovery (if this breaks) - How to disable/revert this change quickly: - Files/config to restore: - Known bad symptoms reviewers should watch for: ## Risks and Mitigations List only real risks for this PR. Add/remove entries as needed. If none, write `None`. - Risk: - Mitigation: <!-- greptile_comment --> <h3>Greptile Summary</h3> Added a standalone Next.js landing page for "The Hive" - a proposed queen-centric swarm infrastructure concept for OpenClaw. The landing page is completely self-contained in the `hive-landing/` directory with no impact on the main OpenClaw codebase. **Key additions:** - Complete Next.js 15 app with React 19, TypeScript, and Tailwind CSS 4 - Three.js powered 3D honeycomb background animation using `@react-three/fiber` - Multiple landing page sections: Hero, Architecture, Security, Biology, Roadmap, CTA, Footer - ASCII art visualizations for technical concepts (Queen hierarchy, firewall architecture) - Responsive design with terminal-style UI elements - Static export configuration (`output: "export"`) for easy deployment **Technical notes:** - Uses client-side rendering for Three.js components with proper SSR disabling - Implements scroll-triggered animations and effects - All dependencies are properly scoped to the landing page subdirectory - No integration with main OpenClaw build system or dependencies <h3>Confidence Score: 4/5</h3> - Safe to merge with minor fix - isolated landing page with no impact on core codebase - The PR adds a completely self-contained Next.js landing page in a separate directory with its own dependencies. The code is well-structured with proper TypeScript typing, client-side rendering guards for Three.js, and follows modern React patterns. Only one issue found: placeholder GitHub URL that needs updating. No security concerns, no impact on existing functionality, and the static export configuration is appropriate for a landing page. - hive-landing/src/app/components/navbar.tsx needs GitHub URL updated _{Last reviewed commit: 5eecfda} <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->