[aramprice]

Completed: all eight repositories now have protected default branch main. Native renames preserved the tips and every unrelated branch/tag object; protections, integrations, workflow state, existing PR heads and fresh-clone defaults were verified. All eight tracking issues are closed as completed.

All affected deployed Git source checks and the isolated public-source check/get probe succeeded. Live configuration changed only the remaining Git branch selectors; version/infrastructure state and every original pipeline/job pause setting were preserved. Published BOSH documentation links and the BPM edit mapping were verified.

Documentation/comment-only follow-ups can merge independently. The review links and original cutover plan below are retained for reference.

Repository	Preparation PR	Tracking issue
bosh-aws-light-stemcell-builder	cloudfoundry/bosh-aws-light-stemcell-builder#66	cloudfoundry/bosh-aws-light-stemcell-builder#67
bosh-azure-cpi-release	cloudfoundry/bosh-azure-cpi-release#778	cloudfoundry/bosh-azure-cpi-release#779
bosh-dns-release	cloudfoundry/bosh-dns-release#182	cloudfoundry/bosh-dns-release#183
bosh-google-cpi-release	cloudfoundry/bosh-google-cpi-release#402	cloudfoundry/bosh-google-cpi-release#403
bosh-utils	cloudfoundry/bosh-utils#160	cloudfoundry/bosh-utils#161
bosh-vsphere-cpi-release	cloudfoundry/bosh-vsphere-cpi-release#476	cloudfoundry/bosh-vsphere-cpi-release#477
bpm-release	cloudfoundry/bpm-release#237	cloudfoundry/bpm-release#238
docs-bosh	cloudfoundry/docs-bosh#937	cloudfoundry/docs-bosh#938

Documentation/comment follow-ups:

• Update source comments for the main branch rename bosh-linux-stemcell-builder#787 — bosh-aws-light-stemcell-builder
• Update source comments for the main branch rename nginx-buildpack#441 — bosh-dns-release
• Update documentation for the main branch rename bosh-gcscli#57 — bosh-google-cpi-release
• Update documentation for the main branch rename docs-cf-admin#286 — bosh-google-cpi-release
• Update documentation for the main branch rename bosh#2837 — bosh-utils
• Update source comments for the main branch rename haproxy-boshrelease#997 — bpm-release
• Update documentation for the main branch rename exemplar-backup-and-restore-release#8 — bpm-release
• Update source comments for the main branch rename bosh-gdc-cpi-release#18 — docs-bosh

The docs-bosh preparation PR also contains the Azure, Google, vSphere and BPM documentation links. The follow-ups change only links; they do not gate the operational cutovers.

Cutover sequence:

1. Merge source preparation before renaming each repository with pinned Git sources. Keep deployed branch selectors unchanged until main exists.
2. For bosh-utils, merge into develop and let the current CI promote the tested preparation to the existing default branch. Verify promotion before renaming; retain develop and release-semver.
3. Pause/drain repository and counter writers, capture refs/protections/pipeline state, then natively rename master to main. Reconfigure existing consumers, verify actual checks/fetches and preserve version/infrastructure state before restoring original pause settings.
4. Coordinate docs-bosh publication after Azure, Google, vSphere and BPM have main. Its deployed source already follows the default branch, so its preparation PR may remain open through the native rename and retarget to main before merging.
5. Verify protected default main, unchanged tips and unrelated refs/tags, PR retargeting, workflow/integration settings and fresh-clone defaults for all eight. Mark this PR ready only after those results are recorded in the linked repository issues.

Validation: generator comparison changes only the eight selected default_branch values and their protection selectors from ^master$ to ^main$. All other generated configuration is unchanged; git diff --check passes.

Peribolos synchronization is asynchronous and individual runs may be canceled by later merges. No particular run is a checklist gate; an eventual successful synchronization containing the merged configuration remains required before org configuration is fully applied.