Context
The English Project Status page includes a Current Status bullet for the frozen support boundary that links to docs/en/stabilization-support-matrix.md, but the Chinese Project Status Current Status list does not mirror that entry. The Chinese page links the support matrix later, yet the top status summary is the page most likely to be scanned during beta/release checks.
This is a small public-doc consistency gap independent from the current whiteboard PR stack and PR #261.
Scope
- Add the Chinese Current Status bullet that mirrors the English frozen support boundary entry.
- Add focused docs-test coverage proving both EN/ZH Project Status pages expose the support boundary in the Current Status section.
- Keep the change limited to public docs/tests.
Acceptance Criteria
docs/zh-CN/project-status.md Current Status includes a stable support-boundary link to ./stabilization-support-matrix.md.
- Focused tests fail without the Chinese Current Status entry and pass after the fix.
- Existing stabilization support docs tests remain green.
git diff --check passes.
Out of scope
No runtime behavior changes, no public API changes, no release checklist rewrite, no version/package change, no whiteboard roadmap work, no PR-stack merge or admin bypass, and no broad support-claim expansion.
Context
The English Project Status page includes a Current Status bullet for the frozen support boundary that links to
docs/en/stabilization-support-matrix.md, but the Chinese Project Status Current Status list does not mirror that entry. The Chinese page links the support matrix later, yet the top status summary is the page most likely to be scanned during beta/release checks.This is a small public-doc consistency gap independent from the current whiteboard PR stack and PR #261.
Scope
Acceptance Criteria
docs/zh-CN/project-status.mdCurrent Status includes a stable support-boundary link to./stabilization-support-matrix.md.git diff --checkpasses.Out of scope
No runtime behavior changes, no public API changes, no release checklist rewrite, no version/package change, no whiteboard roadmap work, no PR-stack merge or admin bypass, and no broad support-claim expansion.