PR: #743: feat(agents): rename matter agent Mira → Vani in counsel-visible copy [Story-3084] by @ankitmaheshwari-com

View PR →

Files changed

7 file(s), +65 / -62 lines

Path	Role	+	-
messages/en.json	Config	+24	-24
messages/hi.json	Config	+24	-24
public/agent-avatars/{mira-matter-expert.png => vani-matter-expert.png}	Source	bin	bin
src/components/matter-detail/brief/frame-summary-history.tsx	Component	+2	-2
src/components/matter-detail/ccb/mira-descriptor.ts	Component	+11	-8
src/components/settings/security/account-security-page.test.tsx	Component	+2	-2
tests/unit/channels-page.test.tsx	Test	+2	-2

Story-3084: Rename Mira to Vani in the app agent panel

A lawyer met Vani on WhatsApp but Mira in the app — same agent, two names. Companion to Chore-3076 (WhatsApp copy) and required because a competing legal-AI product ships as "MIRA" in the same Indian market. Every counsel-visible string in the app now reads Vani (English) and वाणी (Hindi). The Hindi is the idiomatic word for speech/voice, carrying the name's meaning rather than a transliteration of "Vani".

Counsel-visible strings changed. Machine identity — the AgentCore runtime name, rail-session keys, the i18n namespace — did not.

What changed

Surface	Change
Matter agent panel (`Mira` namespace)	Name, `ccb.askMira`/placeholders/aria labels, the working line, proposed and failed titles, and the empty-state title/composer now say Vani / वाणी in both locales.
Settings → Channels & remote-logout copy	The WhatsApp connect/disconnect copy, enrollment steps, refusal summary, and the log-out-everywhere consequence copy that named the agent now say Vani / वाणी. Leaving these as "Mira" would have re-created the exact two-names-one-product bug this Story kills.
Doc-passage attribution & notes author	The `mira` passage-answer author/anchor and the section-note `agentAuthor` now render as Vani / वाणी.
Avatar asset	`mira-matter-expert.png` → `vani-matter-expert.png`. The image bytes are unchanged (pure rename); no new face shipped. The two references (`MIRA_AVATAR_SRC` value and the Brief gutter `<img>`) point at the new path.

What deliberately did NOT change

MIRA_KEY = "mira" — machine key for rail-session scoping, logs, and the AgentCore runtime name. Never shown. Renaming it would move an AgentCore runtime.
The Mira i18n namespace key and the askMira key — identifiers, not copy. Only their values changed. Renaming the keys would churn every call site for zero user benefit.
Const/hook identifiers (MIRA_AVATAR_SRC, MIRA_ACCENT, useMiraDescriptor) and machine-facing helper/file names (getMiraConverseRailConnection, mira-rail, etc.).

Automated proof

Every counsel string across both locale files was flipped; a grep proves no counsel-visible "Mira"/"मीरा" remains (only the identifier keys do).
Unit tests asserting the rendered copy were updated to Vani: account-security remote-logout toasts and the Channels disconnect/enrollment copy.
pnpm lint (0 errors), pnpm test (Vani assertions green), pnpm build all pass.

Acceptance boundary

Locale files and unit tests prove the rendered contract in both languages. The only residual "Mira" literal is a generated src/gen/ OpenAPI schema description (machine-facing, never rendered, HR-22 — do not hand-edit). Machine identity strings are intentionally retained.