chore(release): promote dev to main

[seakee]

Summary

Promote the verified integration branch dev to the protected stable branch main. This carries the release-flow documentation and the stable aggregate CI gate introduced by PRs #469 and #470.

Scope

• Frontend panel
• Manager Server
• CPA panel mode
• Full Docker mode
• Native packages / release
• Docs / Wiki
• CI / build / tooling

Changes

• Publish the required release/<version> → dev → main → tag release-promotion process.
• Use the stable Required checks aggregate gate so path-skipped CI jobs satisfy the protected-branch policy deterministically.
• Promote only the same repository's current dev branch into main.

User Impact

No product runtime behavior changes. Maintainers and community contributors now have a consistent PR target and a reliable protected-branch gate for docs-only and scoped changes.

Compatibility / Runtime Notes

• CPA panel mode: N/A.
• Manager Server mode: N/A.
• Full Docker / native packages: No runtime, packaging, or release asset changes; this promotion governs the release process and CI gate.

Data / Security Notes

No credentials, runtime configuration, database data, or release secrets are changed. The existing same-repository dev → main source restriction remains enforced.

Risk / Rollback

Risk level: Low

Rollback notes:

Revert this promotion through a new protected dev → main PR if the branch model or aggregate-gate policy needs to change.

Verification

• Type check
• Lint
• Tests
• Build
• Manual UI check
• Docs/link check
• Not applicable, docs-only

Commands / evidence:

PR #469: Scope, PR Template, and Required checks succeeded.
dev commit 00c26e0: Scope and Required checks succeeded; path-scoped build jobs skipped as designed.

Screenshots / Recordings

N/A — documentation and CI policy only.

Docs

• README / README_CN updated for user-visible capabilities
• Matching docs manual and navigation updated
• Demo fixtures, screenshots, and deep links reviewed
• Release notes needed
• Not needed — this promotion documents and enforces the release workflow; no product release is created.

Docs decision:

docs/release.md is the canonical release-process reference. No tag or GitHub Release is included in this PR.

Related

Refs #469
Refs #470