[Docs] Add production hotfix path to release workflow

[roomote-roomote]

​Opened on behalf of @mrubens. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

Related issue

Internal maintainer workflow documentation based on the completed production hotfix sequence in #1840 and #1841.

Why this PR exists

• A maintainer explicitly invited this PR in the linked issue or discussion
• I am a maintainer / this is internal Roomote work

The existing $changeset-release-pr skill already owns Roomote's versioning, changelog, and promotion rules. Adding the emergency procedure there keeps one canonical release workflow while avoiding a competing invocation with duplicated safeguards.

What changed

Extends $changeset-release-pr with a clearly separated emergency direct-to-main hotfix path while preserving its normal develop release workflow as the default.

The hotfix path covers complete fix and prerequisite selection from latest main, exact scope and relevant live checks, repository-owned patch changeset consumption, focused and pre-push validation, merge-commit delivery to main, a two-file develop sync that preserves pending changesets, strict tag/image/GitHub Release ordering, and rollback safeguards. It explicitly refreshes both remote-tracking branch refs before creating the production branch, preventing stale origin/main state from passing the safety check.

This is documentation-only agent guidance with no runtime product behavior change.

How it was tested

• pnpm test:release-scripts (16 passed)
• pnpm --filter @roomote/worker exec vitest run src/workspace/__tests__/repo-local-skills.test.ts (4 passed)
• consolidated skill frontmatter, normal-path, and hotfix-contract assertions
• explicit hotfix fetch refspecs verified with git fetch --dry-run
• git diff --check
• node scripts/pre-push-checks.mjs (oxlint, residual ESLint, fast typechecks, and knip)
• focused completion review found no material gaps

Checklist

• The PR title follows the repo convention: [Fix], [Feat], [Improve], [Refactor], [Docs], or [Chore] followed by a user-facing description
• This PR is small and scoped to one change
• pnpm lint and pnpm check-types pass locally
• I added tests or included a clear manual validation note above
• I removed secrets, tokens, private keys, and customer data from code, logs, and screenshots
• If this change should appear in the changelog, I ran pnpm changeset (not applicable to repository-only workflow documentation)

[roomote-community]

No code issues found. See task

• .agents/skills/changeset-release-pr/SKILL.md:293 refreshes only FETCH_HEAD, so a stale origin/main can be released.

_{Reviewed 3eeabe5}

[roomote-roomote]

Resolved the outstanding stale remote-tracking ref issue in 3eeabe5c: the hotfix preflight now refreshes explicit main and develop tracking refs before branching. Release-script tests and the full pre-push gate pass.