xjxandgd-ops
72c66a67fb
## Summary
- restore release-preparation context on `main` pushes only when typed
validation scope reports an exact `CHANGELOG.md` change
- make primary cold launch converge on the shared control-center
presenter and retain fronting until the SwiftUI window is registered
- add control-plane, lifecycle, and race-regression coverage for both
release blockers
## Validation
- `python3 script/tests/test_validation_tooling.py` (53 passed)
- `python3 script/development_domains.py validate`
- `./script/validate_build_scripts_safety.sh --static-only`
- `./script/validate_app_lifecycle_contract.sh` (12/12 passed)
- `./script/validate_swift_tests.sh --scope all` (745 passed)
- `./script/validate_pre_push.sh`
- `./script/changelog_fragments.py policy --base-ref origin/main
--release-preparation true`
## Release note
This amends the still-unpublished v0.4.3 release preparation. The exact
merged `main` commit will receive the mandatory host UI acceptance
before release dispatch.
## Development claim / 开发声明
- Domain: `release-control-plane`
- Claim: `control-plane`
- Base commit: `7c57bbdb16b24074df16dd64ec51d3fc28782a7f`
- Release preparation: `yes`
- Focused validation:
- `python3 script/tests/test_validation_tooling.py`
- `./script/validate_build_scripts_safety.sh --static-only`
<!-- apc-engineering-coordination-v1
{"claim_overlap_rejections":0,"merge_tree_conflicts":0,"schema_version":"apc.engineering-coordination.v1","task_created_at":"2026-08-12T16:56:32Z","train_conflict_resolutions":0}
-->
---------
Co-authored-by: gd-ops <gd-ops@xmfunny.com>
Project Documentation / 项目文档
README.md and README.zh-CN.md are the product entrypoints. This directory contains the durable technical contracts used by maintainers and Agents. / 根目录 README 面向用户；本目录只保存维护者与 Agent 需要长期维护的技术契约。
Source order / 信息优先级
- Current user request / 当前用户要求
- Implementation, typed schemas, manifests, and tests / 实现、类型化 schema、manifest 与测试
- The owning document below / 下表中负责该主题的文档
- Public README / 面向用户的 README
When prose disagrees with code, investigate the implementation and update the single owning document. / 文档与实现冲突时，应核对实现并更新唯一负责该主题的文档。
Documents / 文档
| Document / 文档 | Owns / 负责内容 |
|---|---|
| System architecture | Components, ownership, product boundaries, and main flows / 组件、所有权、产品边界与主流程 |
| Runtime and IPC | Processes, startup, replacement, transport, updates, and diagnostics / 进程、启动、替换、通信、更新与诊断 |
| Data model | Storage, typed projections, identity, revisions, retention, and versioned contracts / 存储、类型化投影、身份、revision、保留与版本契约 |
| Agent connectors | Host adapters, event mapping, routing, managed operations, and privacy / Agent 适配、事件映射、路由、受管操作与隐私 |
.petpack V3 |
Portable package format and producer conformance / 可移植宠物包格式与制作合规要求 |
| Validation profiles | What each validation layer proves / 各验证层能够证明什么 |
| Parallel development | Direct/train PR lanes, Agent ownership, auto-merge, and protected delivery / direct/train PR 通道、Agent 所有权、自动合并与受保护交付 |
| macOS release | Official GitHub Release procedure and installation contract / 正式 GitHub Release 流程与安装合同 |
| CHANGELOG | Versioned user-visible changes / 按版本记录的用户可见变化 |
Maintenance / 维护
- Keep one durable document per topic; link to code or schemas instead of copying them. / 每个主题只保留一份长期文档，优先链接源码或 schema。
- Describe current behavior and invariants only. Plans, audits, progress logs, screenshots, and command output belong in issues, commits, PRs, CI, or Release notes. / 只描述当前行为与不变量；计划、审计、进度、截图和命令输出进入 issue、commit、PR、CI 或 Release notes。
- Put user-visible changes in
[Unreleased]; do not commit diagnostics, user data, credentials, build output, or temporary assets as documentation. / 用户可见变化写入[Unreleased]；不要把诊断、用户数据、凭据、构建产物或临时素材作为文档提交。