ghcp-sp-95-branch-protection

Author: edburns

80-java-monorepo-add-01-remove-before-merge/20260515-prompts.md

@@ -123,3 +123,23 @@ Note: only this one workflow (`java-publish.yml`) needs the bypass. All other Ja
 The code in `copilot-sdk-java-00` has been updated. In particular there have been changes to the workflows there. I am aware we have copied over at least one workflow in the process of performing Phase 0 work according to the plan.
 
 Examine the recent workflow changes in `copilot-sdk-java-00` and make the corresponding Java changes to keep the `copilot-sdk-00` side up to date.
+
+## ghcp-sp-95-branch-protection
+
+Consider this text from the plan.
+
+```markdown
+- [⌛ ] **Confirm branch protection** — will new required status checks be accepted? See https://github.com/github/copilot-sdk-partners/issues/95 .
+```
+
+Use the `gh` CLI to look at this comment on the issue: https://github.com/github/copilot-sdk-partners/issues/95#issuecomment-4462156144
+
+The last statement in that comment is this:
+
+> Steve requested I look into the cost of doing the trade-off item 4 and if the cost is deemed too high, we can do it after GA.
+
+It is now time to do this investigation. I suspect what Steve was told by his agent isn't quite the full story. I suspect plenty of projects still use `maven-release-plugin`, but do want to follow current best practices. 
+
+One aspect that I want to be clear on: this SDK is much smaller than Quarkus or Spring. Is there evidence to support the assertion that projects of this size still do use `maven-release-plugin` even in 2026-05? Or, is it the case that even small projects have abandoned in favor of other options.
+
+Finally, what about the use of the `central-publishing-maven-plugin`? Does that need to be considered in this branch protection conversation?