merging-to-main

To merge a feature branch into main safely, you enforce a test-suite gate and CI-watched execution. This ensures coordinator hook tests and project tests pass first, blocking the PR merge on any failures to prevent broken releases.

An acceptance oracle gate validates a branch merge against a plan's bindable acceptance criteria table before testing. It runs an authoritative check to ensure planned requirements are met, removing uncertainty when promoting work to main.

Automate release notes and PR body creation for a GitHub merge by drafting a ship verdict and structured notes during promotion. This optionally updates CHANGELOG.md and appends a demo path for user-visible merges.

Yes, you can override test gating to merge a hotfix into main using an approved hotfix escape hatch. This allows merging despite test failures when urgent release promotion is required and justified.

To verify a safe branch cleanup after merging a PR via gh, run post-merge safety checks. This confirms your intended edits still exist in main and validates that the branch cleanup removed the merged feature branch securely.