feat: add opt-in real nickname controls

[Sisyphbaous-DT-Project]

在群聊场景中，当前用户识别信息里的 nickname 通常来自群昵称或群名片。这个值更适合作为群内展示名，但它可能被频繁修改，也可能和用户真实昵称不一致。对依赖用户识别、长期上下文或个性化回复的场景来说，模型只能看到群昵称会影响身份信息的一致性。

本次改动增加两个默认关闭的真实昵称相关开关，让部署者可以按需选择“追加真实昵称”或“仅使用真实昵称”。未启用新开关时，现有行为保持不变。

同时，本次改动将用户和群组身份信息整理为结构化 JSON 元数据，并对昵称、真实昵称、群名等外部输入做基础清洗，减少控制字符、零宽字符和伪造标签边界对提示词结构的干扰。

Modifications / 改动点

• 新增 provider_settings.real_nickname_display 开关，开启后在支持的平台上向模型额外提供用户真实昵称。
• 新增 provider_settings.real_nickname_only 开关，开启后模型只看到真实昵称；当真实昵称不可用或清洗后为空时，回退到原昵称。
• 将用户身份信息和群组信息改为 JSON 风格元数据，减少自然语言拼接带来的歧义，例如 User metadata: {"user_id":"...","nickname":"..."}。
• 对昵称、真实昵称和群名进行元数据清洗，包括控制字符、零宽字符、尖括号边界和长度限制。
• 补充 WebUI 配置项、三种语言的配置文案，以及条件配置项出现/消失时的轻量过渡动画。
• 补充单元测试，覆盖默认行为、真实昵称追加、仅真实昵称模式、缺失回退、清洗、去重和对象形态 raw_message 读取。

• This is NOT a breaking change. / 这不是一个破坏性变更。

Screenshots or Test Results / 运行截图或测试结果

已执行以下验证：

PYTHONPATH=. pytest -s tests/unit/test_astr_main_agent.py -q
99 passed, 1 warning

npm run typecheck
vue-tsc --noEmit

python -m json.tool dashboard/src/i18n/locales/zh-CN/features/config-metadata.json >/dev/null
python -m json.tool dashboard/src/i18n/locales/en-US/features/config-metadata.json >/dev/null
python -m json.tool dashboard/src/i18n/locales/ru-RU/features/config-metadata.json >/dev/null

git diff --check

本地手动验证：

• 启动 AstrBot 后端和本地 WebUI 后，访问 http://localhost:3000/#/config#normal。
• 开启“用户识别”后，“追加用户真实昵称”配置项按条件出现。
• 开启“追加用户真实昵称”后，“仅使用真实昵称”配置项按条件出现，并带有过渡动画。
• 保存配置后，后端可读取新增配置项并按预期生成用户元数据。

Checklist / 检查清单

• 如果 PR 中有新加入的功能，已经通过 Issue / 邮件等方式和作者讨论过。
• 我的更改经过了测试，并已在上方提供了验证步骤和测试结果。
• 我确保没有引入新依赖库。
• 我的更改没有引入恶意代码。

Summary by Sourcery

Add configurable support for exposing users’ real nicknames and structured metadata in system reminders, along with UI and test updates.

New Features:

• Introduce optional provider settings to append and optionally prefer real user nicknames in identifier metadata.
• Expose group and user identity as structured JSON-style metadata in system reminders instead of plain text.

Enhancements:

• Sanitize user and group metadata values to strip control/zero-width characters, normalize whitespace and brackets, and cap length before injecting into prompts.
• Add animated transitions for conditionally shown object-type configuration items in the Web UI, respecting reduced-motion preferences.

Tests:

• Extend main agent tests to cover real nickname display/only modes, fallbacks, metadata sanitization, de-duplication, and object-shaped raw message handling.

[gemini-code-assist]

Code Review

This pull request introduces features to append and display a user's real nickname in system reminders, along with robust metadata sanitization and formatting. Key changes include adding helper functions to clean metadata values (removing control characters, zero-width characters, and escaping HTML-like tags), updating the configuration schema and localized strings, and wrapping configuration items in the dashboard with a TransitionGroup for smoother UI transitions. Unit tests were also added to verify the new metadata processing and fallback behaviors. Feedback on the changes highlights a potential layout issue in the dashboard transition styles: hardcoding max-height to 180px in the TransitionGroup styles can cause items taller than 180px to be clipped or experience sudden height jumps during transitions. It is recommended to remove the max-height transition and only animate opacity and transform to ensure compatibility with varying item heights.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[sourcery-ai]

Hey - I've left some high level feedback:

• In _append_system_reminders, real-nickname de-duplication currently compares real_nickname (unsanitized) against sanitized_user_nickname; if you want to ensure zero-width/control-character differences don’t cause redundant metadata, consider sanitizing real_nickname before the equality check and reuse that sanitized value in _format_metadata.
• In AstrBotConfigV4.vue, createSelectorModel(itemKey).value is called multiple times per item (including inside v-ifs and v-for), which can lead to unnecessary recomputation; you could cache the model per item (e.g., via a computed or local variable inside the loop) to avoid repeated calls.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In `_append_system_reminders`, real-nickname de-duplication currently compares `real_nickname` (unsanitized) against `sanitized_user_nickname`; if you want to ensure zero-width/control-character differences don’t cause redundant metadata, consider sanitizing `real_nickname` before the equality check and reuse that sanitized value in `_format_metadata`.
- In `AstrBotConfigV4.vue`, `createSelectorModel(itemKey).value` is called multiple times per item (including inside `v-if`s and `v-for`), which can lead to unnecessary recomputation; you could cache the model per item (e.g., via a computed or local variable inside the loop) to avoid repeated calls.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Sisyphbaous-DT-Project]

关于 Sourcery 的两点建议，已逐项确认：

• _append_system_reminders 中的 real_nickname 在参与去重比较前已经通过 _sanitize_optional_metadata_value() 清洗，因此这里不是未清洗值和清洗值比较的问题；相关逻辑保持不变。
• createSelectorModel(itemKey).value 的重复调用属于现有通用配置渲染器的模板写法，当前场景开销很小。为避免扩大本 PR 范围，暂不在这个改动里重构该部分。

补充：关于 Gemini 对 max-height 过渡的建议，后续实测发现移除该过渡会导致条件配置项关闭时直接消失，缺少折叠收起动画。因此已在 5c4fa2a 中撤销 caa2c64，恢复原有折叠高度过渡。当前 PR 暂不扩大为动态高度动画重构；如果后续需要兼容更高配置项，可以在单独改动中设计更完整的动态高度过渡方案。

已重新执行 npm run typecheck 与 git diff --check。