feat(babydegen-ui): integrate Basius agent (Base chain)

[mohandast52]

Integrates the Basius agent (Base chain) into babydegen-ui — the third chain-clone alongside Modius (Mode) and Optimus (Optimism): same agent code, different deployment chain.

aero.mp4

[github-actions]

📦 Bundle sizes

App	Total	js	css	png
agentsfun-ui	1844.6 KB (+37.9 KB, +2.1%)	1001.2 KB	0.0 KB	825.8 KB
babydegen-ui	4028.1 KB (+110.8 KB, +2.8%)	1583.2 KB	0.0 KB	2437.3 KB
predict-ui	5255.4 KB (+37.9 KB, +0.7%)	1828.0 KB	0.0 KB	3409.9 KB

Compared against the latest successful main run, not this PR's merge-base — deltas may conflate this PR's change with intervening main commits. Warns at ±10% per-app delta; non-blocking. Sudden bundle growth is a malware canary.

[Tanya-atatakai]

✅ Approve — Basius (Base chain) integration

Correct, complete, and consistent. Verified locally: tsc --noEmit passes (CI runs no typecheck/build), all per-agent switches are updated with no missed call sites, deleted logos are unreferenced, and every new asset path resolves.

What's done well

• Completeness — every per-agent branch found and updated (agentMap, colors, theme, palette, mockChat, mockPortfolio); no two-way switch left behind.
• Both AgentType copies + LOGO_MAP updated (util-constants-and-types and ui-chat/types.ts) — the exact trap CLAUDE.md warns about.
• Asset wiring correct — base-network.png (donut plugin), aero.png (mockAgentAsset → 'AERO' → token avatar), aerodrome.png (PROTOCOL maps) all resolve.
• Genuine fix bundled in — COLOR.black → COLOR.buttonText makes button-text color agent-specific (white on Optimus red / Basius blue, dark on Modius lime), defined for all three variants.
• Coverage gate respected — new module-load branches land in files already excluded from coverage; agentMap.ts (not excluded) got a new basius test keeping all three branches covered.
• Docs + release workflow tag→env mapping updated in lockstep.

Suggestions (non-blocking)

1. Scaling smell — the N-way if (=== 'modius') … if (=== 'basius') … return optimus ladder is now repeated across ~6 files. Since this is the second clone, consider a single source-of-truth record keyed by AgentType (Record<AgentType, {...}>) so a new chain is one object entry and omissions become compile errors. Fine to defer.
2. Out-of-scope deletions — public/logos/{modius,optimus}.png removed as unused (confirmed unreferenced, harmless); just noting it rides along in a feature PR.

Risk: low — pure additive config for a new enum value; existing paths unchanged apart from the deliberate button-text fix.

[rajat2502]

Reviewed end-to-end: agentMap contract changes ripple correctly (network/token logo paths, both SelectedProtocol maps, ui-chat's duplicated AgentType + LOGO_MAP all updated), no security-relevant surface, mocks/tests unaffected. Two non-blocking nits: public/logos/basius-chat.png appears unreferenced (chat logo is bundled from libs/ui-chat/src/assets/), and the jest.config coverage-exclusion comments for colors.ts/theme.ts/palette.ts now understate those files (they branch on agentType since this PR).