🧹 chore(ci): promote dev integration governance

[seakee]

Summary

Promote the tested dev integration branch to stable main. This first promotion establishes the permanent rule that all later main changes must originate from the same repository's dev branch.

Scope

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

Changes

• Promote the tested dev integration commit containing dev-targeted CI and PR-template validation.
• Add the main-promotion source gate to stable main.
• Publish the contributor workflow that directs community PRs to dev.

User Impact

Users retain main as the stable default branch. Contributors gain a documented dev integration target and direct PRs to main will be rejected after this promotion.

Compatibility / Runtime Notes

• CPA panel mode: N/A.
• Manager Server mode: N/A.
• Full Docker / native packages: N/A.

Data / Security Notes

No runtime configuration, credentials, database data, or request data changes. The source gate has read-only permissions and verifies the exact repository and branch identity.

Risk / Rollback

Risk level: Low

Rollback notes:

Revert the governance commits and remove the corresponding branch-protection rules if the branch model must be withdrawn.

Verification

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

Commands / evidence:

PR #467: all 9 checks passed
dev push CI: https://github.com/seakee/CPA-Manager-Plus/actions/runs/30679820341 (success)
npm run test  # 133 files, 1361 tests passed
git diff --check

Screenshots / Recordings

N/A — CI and contributor documentation 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 — CONTRIBUTING.md is the canonical contribution guide; product documentation and release notes are unaffected.

Docs decision:

The change governs repository integration and does not change a user-facing product capability.

Related

Refs #467