ci: separate PR validation from main deployment

[RyanLee-Dev]

Pull requests currently repeat their checks after merging, and mixed website/documentation changes can build the site in two workflows. Make PR validation and main deployment separate GitHub Actions responsibilities.

• Run the required core-check gate for PRs, manual full checks and release qualification. Main already requires an up-to-date PR with a successful check; merging no longer starts another core test suite.
• Validate website and published documentation changes in core-check only. Keep main website publication and manual deployment, including Pages configuration and Git history.
• Trigger the existing post-merge review once for a merged PR and read its existing checks and logs. Checkout only the immutable merged commit, with explicit read permissions for check/status data.
• Select lint for actionlint configuration changes, and run only hygiene for a verified empty diff. Keep GitHub concurrency, dependency caches, failed-job reruns and within-release artifact transfer.

Releases retain the full exact-ref gate. Direct pushes/admin bypasses do not establish PR CI success. No repository protection settings are changed.

Validation: 46 CI planner/metrics tests, documentation and naming checks, actionlint 1.7.12 and git diff --check passed locally. Independent review passed. Hosted CI is pending for the updated branch.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
openagentcore	🟢 Ready	View Preview	Oct 1, 2026, 11:25 AM

💡 Tip: Enable Automations to automatically generate PRs for you.