Ship

1. Confirm the branch and diff exactly match the reviewed scope.
2. Re-run the required checks from docs/development/quality-gates.md.
3. Verify that public contracts and generated files are pushed. Merge each companion change into the default branch of its repository (for example fallow-docs main). A pushed feature branch is not enough: the release then must merge it.
4. Create signed conventional commits only.
5. Merge through the repository's current protected-main workflow.
6. Monitor the merged commit until required CI completes. Before you retry a failed job, confirm that the branch contains the current base (git merge-base --is-ancestor origin/main HEAD). A second identical failure is a defect, not a flake: diagnose it instead of a third retry.
7. Inspect the merged tree for conflict markers and generated drift.
8. Return every touched checkout to a clean, synchronized state.

Do not call work complete while required merged-commit workflows are still running.