build(skills): improve release skill conventions

[tylerbutler]

Summary

Improves the fluid-release skill based on lessons from the 2.91.0 release:

• Require all release PRs to be opened as drafts and assigned to the release runner via --draft --assignee @me
• Add a merge freeze announcement step after the release notes PR is created, prompting the user to notify the team in the "Fluid Framework All" Teams channel
• Elevate the ADO blocker check from a passive reminder to a mandatory confirmation gate that blocks progress until the user responds
• Add a pre-merge blocker re-check (GitHub + ADO) between Step 4 and Step 5 to catch late-breaking release blockers
• Document the revert-and-regenerate workflow when a release-blocking PR with a changeset merges after the release notes PR
• Never auto-merge the version bump PR — always merge manually to avoid race conditions with late-landing changesets
• Fix Teams channel name to "Fluid Framework All"

[Copilot]

Pull request overview

Updates the fluid-release skill guidance to make release PR handling and blocker checks more explicit and harder to miss during minor/patch release execution.

Changes:

• Make ADO release-blocker verification an explicit confirmation step (not just a reminder).
• Add a merge-freeze announcement reminder after opening the release notes PR.
• Add a pre-merge blocker re-check step before merging release-prep PRs.
• Document that release PRs should be opened as drafts and assigned to the release runner.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.

File	Description
.claude/skills/fluid-release/references/release-execution.md	Tightens blocker-handling guidance by requiring explicit ADO confirmation before proceeding.
.claude/skills/fluid-release/references/minor-release-prep.md	Adds merge-freeze reminder and a pre-merge blocker re-check section; updates release notes PR instructions for draft/assignee.
.claude/skills/fluid-release/SKILL.md	Makes ADO blocker check mandatory and documents draft+assignee conventions for release PRs.

---

You can also share your feedback on Copilot code review. Take the survey.

[github-actions]

🔗 No broken links found! ✅

Your attention to detail is admirable.

linkcheck output

> fluid-framework-docs-site@0.0.0 ci:check-links /home/runner/work/FluidFramework/FluidFramework/docs
> start-server-and-test "npm run serve -- --no-open" 3000 check-links

1: starting server using command "npm run serve -- --no-open"
and when url "[ 'http://127.0.0.1:3000' ]" is responding with HTTP status code 200
running tests using command "npm run check-links"


> fluid-framework-docs-site@0.0.0 serve
> docusaurus serve --no-open

[SUCCESS] Serving "build" directory at: http://localhost:3000/

> fluid-framework-docs-site@0.0.0 check-links
> linkcheck http://localhost:3000 --skip-file skipped-urls.txt

Crawling...

Stats:
  272202 links
    1863 destination URLs
    2108 URLs ignored
       0 warnings
       0 errors