xjxandgd-ops
0b5c7b8149
Agent guidance previously ranked existing implementation and tests ahead
of documented contracts without distinguishing observed behavior from
intended requirements. The root guidance and bilingual documentation
index now make that distinction and require investigating whether a
disagreement comes from a defect, stale documentation, or an unresolved
requirement. Existing product, delivery, and release constraints remain
intact.
Validation: the scoped local pre-push checks passed, including source
syntax and local Markdown links; the changelog-fragment policy also
passed.
## Development claim / 开发声明
- Domain: `release-control-plane`
- Claim: `engineering-speedup`
- Base commit: `d2040c4922d4b021eedc4cd0eae953537c28d0fb`
- Release preparation: `no`
- Focused validation:
- `python3 script/tests/test_validation_tooling.py`
- `./script/validate_build_scripts_safety.sh --static-only`
<!-- apc-engineering-coordination-v1
{"claim_overlap_rejections":4,"merge_tree_conflicts":0,"schema_version":"apc.engineering-coordination.v1","task_created_at":"2026-09-09T02:21:17Z","train_conflict_resolutions":0}
-->
Co-authored-by: gd-ops <gd-ops@xmfunny.com>
Unreleased changelog fragments / 未发布变更片段
Every direct, task, and train development PR records each user-visible change as a globally unique <id>.json fragment here. Ordinary development leaves root CHANGELOG.md untouched. Only an explicit release-preparation branch may freeze and consume the fragments. See changelog and integration for commands and macOS release for the version/tag/Release contract. / 所有 direct、task 与 train 开发 PR 均在此以全局唯一的 <id>.json 记录用户可见变化，普通开发不修改根 CHANGELOG.md。仅显式发布准备分支可冻结并汇总片段；命令和版本、tag、Release 契约见上述文档。
{
"schema_version": "apc.changelog-fragment.v1",
"kind": "Changed",
"scope": "overlay",
"summary_en": "Desktop bubbles keep the newest Agent reply.",
"summary_zh": "桌面气泡保留最新的 Agent 回复。"
}