Use the public project name consistently while retaining compatibility identifiers and existing download names. Publish the contribution, architecture and translation contracts with their enforcement limits. Synchronize the bilingual unreleased changelog and release notes.
1.4 KiB
1.4 KiB
Result / 用户结果
What changes for users? Link the relevant issue; do not claim unfinished work.
Design / 设计边界
- Responsibility and affected modules:
- Why this belongs here; interfaces that remain unchanged:
- Dependency, data-format, threading, or lifetime changes (ADR if applicable):
- Compatibility and migration/fallback behavior:
Evidence / 验证依据
- Commands and actual results (include unrun checks):
- Regression tests: what fails before the fix?
- UI changes: screenshots, long translations, keyboard access, DPI checks:
- Hot-path changes: allocation/work/load measurements, where applicable:
Required Review / 必须确认
- I followed
CONTRIBUTING.md,docs/architecture.md, anddocs/project-constraints.md. - I split responsibilities, not arbitrary line ranges; no duplicate behavior authority was added.
python3 scripts/check_architecture.py --base <PR-base-commit>passes; budgets were not inflated to fit the change.- Tests cover success and failure; platform/feature coverage limitations are stated.
- New messages use typed i18n IDs and matching placeholders; untranslated content has an explicit fallback.
- Governance changes include a counterexample, corrected contract, tests, and a maintainer-reviewed decision.
Checkboxes explain the review; they do not replace CI or maintainer approval.