#21223: elliott commit

## 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> This PR introduces a rebrand from OpenClaw to Athena and adds Cortex integration tooling. The changes include a new `athena.mjs` CLI entry point, Cortex MCP tool discovery plugin, extensive UI theming updates (Sonance brand colors), and migration of configuration paths from `.openclaw` to `.athena`. **Key Issues:** - Package name/version resolution mismatch: `package.json` name is still `openclaw` but `CORE_PACKAGE_NAME` changed to `athena`, breaking version lookup logic - Repository URLs in `package.json` point to Dana-Innovations/Athena but package name remains `openclaw` - Breaking changes to config paths (`.openclaw` → `.athena`, `openclaw.json` → `athena.json`) without migration documentation - Cortex tools plugin hardcodes `athena.json` path without legacy fallback, will fail for existing installations - Brand-specific MCP config (sonance-brand-mcp) added to public repository **PR Description:** Completely unfilled - all sections are blank templates, making it impossible to understand intent, test plan, or security implications. <h3>Confidence Score: 1/5</h3> - This PR has critical breaking changes and will fail for existing users due to config path mismatches and package name inconsistencies - Multiple logical errors that break core functionality: version resolution will fail due to package name mismatch, existing installations will lose config access due to path changes without migration, and the cortex-tools plugin won't work for users who haven't migrated yet. The completely empty PR description violates repository guidelines requiring detailed change documentation. - Pay close attention to `package.json`, `src/version.ts`, `src/config/paths.ts`, and `extensions/cortex-tools/src/agent-sync.ts` - these contain the critical breaking changes _{Last reviewed commit: cf5b771} <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->