Skip to content

feat: 个性化动态称谓、持续信任积累与控制台优化(0.7.0) - #59

Merged
timeance merged 3 commits into
mainfrom
feat/personalized-titles
Nov 10, 2026
Merged

timeance merged 3 commits into
mainfrom
feat/personalized-titles

Conversation

@timeance

@timeance timeance commented Nov 10, 2026 •

Copy link
Copy Markdown
Owner

本次更新让称谓能体现 Bot 的人格,为持续可靠的行为补充信任奖励,并改善管理页面的状态显示。版本更新为 0.7.0。

  • 个性化动态称谓:开启后,根据完整人格和三维关系自由生成称谓,支持亲近却戒备、熟悉但疏远等状态。模型默认跟随复核模型,固定词典仍是默认选项。
  • 按关系变化刷新:任一维度跨过 5 分边界后检查刷新,最短间隔 12 小时,每 Bot 每日最多 30 次模型调用。生成结果会校验并保存,查榜无需等待生成;失败时沿用仍适用的称谓或显示固定词典。
  • 持续尊重边界可积累信任:14 天内至少有 3 件独立、可核验的行为,奖励基础 +1 T,每 5 天最多一次。Galgame 沿用正向倍率,奖励为 +2 T;重复表述、道歉和承诺本身不加分。
  • 管理页面更容易读懂:状态列标出正在衰减的 F、A、T,颜色与数值列一致;「个性化功能」集中放置回复参考与动态称谓,设置说明同步精简。
  • 固定词典调整:优化部分初识与混合关系的用词,保留「泛泛之交」「谨慎的相识」等原词,新增「疏远而戒备的熟人」,共 76 个称谓。
  • 补充使用说明与截图:保留上一版 README 的结构、图解、命令和功能介绍,修正过时说明,加入浅色/深色总览和浅色成员详情截图。截图来自实际页面,全部使用合成演示数据。

新安装默认在回复中体现关系;已有明确关闭的选择继续保留。升级保留关系分数和历史流水,自动兼容旧称谓设置。备份和回退方法见仓库中的 docs/MAINTENANCE_UPGRADE.md。

功能验证已通过:Python 1784 项、Node 100 项,以及 AstrBot 4.28.0 / 4.29.4 的十组框架检查;Python 另有 1 项跳过。本次文档修订另行检查版本、链接、公开内容和格式。真实群聊、线上升级与联网模型的表达效果仍需实际使用验证,完整记录见 docs/ACCEPTANCE.md。

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-10T16:37:36.957453Z d112e9a New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d112e9aad9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread storage/sqlite_backend.py
Comment on lines +2363 to +2365
for group, user, reward in {
(group, user, reward) for group, user, _, reward in affected if reward
}:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Reverse non-boundary trust rewards when their sources are revoked

When a promise_kept, verified_correction, or repair_action event references a persisted boundary anchor, revoking that anchor invalidates the dependent evidence but leaves its trust reward intact. These events never populate consumed_by, so filtering the reversal set to nonempty reward values excludes their own scored logs. I reproduced this through _snapshot(), verify_trust_evidence(), and FavorService.undo_log(): a dependent promise_kept awards +0.5 T, and undoing its source leaves that +0.5 T despite both evidence rows becoming invalidated. Include the scored dependent events themselves in the reversal set, while deduplicating boundary batch rewards, so revoked evidence cannot continue contributing trust.

AGENTS.md reference: AGENTS.md:L13-L13

Useful? React with 👍 / 👎.

@timeance
timeance merged commit 9cf0078 into main Nov 10, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant