[Fix] PR remains blocked after Roomote findings are resolved

[roomote-roomote]

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

What changed

• Keep automated PR findings on inline comments and the canonical summary instead of submitting request_changes reviews.
• Expose GitHub review IDs and states through the provider-neutral PR discussion read surface.
• Forward review IDs through the worker MCP boundary and support provider-neutral review dismissal backed by GitHub.
• Fetch the target GitHub review before dismissal and require both CHANGES_REQUESTED state and a normalized managed Roomote author identity.
• Dismiss stale Roomote-authored change requests after a clean sync review, while rejecting human, unrelated-bot, and non-change-request reviews.

Why this change was made

Automated change-request reviews could leave a pull request blocked after all findings were addressed. The dismissal path also needed to enforce its ownership guarantee at the provider boundary rather than trusting a caller-supplied review ID.

Impact

Clean sync reviews can clear stale Roomote-owned change requests without risking dismissal of reviews from humans or unrelated bots. Unsupported providers continue to report review dismissal as an honest capability gap.

[roomote-community]

No new code issues found. See task

• packages/sdk/src/server/lib/pull-requests/source-control-pull-request-writes.ts:762 Restrict review dismissal to Roomote-owned CHANGES_REQUESTED reviews before forwarding the request to GitHub.
• apps/worker/src/mcp/roomote-mcp-server/index.ts:848 Forward reviewId when invoking handleManageSourceControl so review dismissal can succeed.

_{Reviewed dbf2b62}

[roomote-roomote]

Fixed and pushed in dbf2b62.

• GitHub now fetches and validates the target review before dismissal, allowing only managed Roomote authors in CHANGES_REQUESTED state.
• Human, unrelated-bot, and non-change-request reviews are rejected before the dismissal API call.
• reviewId is forwarded through the registered worker MCP tool so the validated dismissal path is reachable.
• Focused SDK and worker tests, typechecks, formatting, lint, and the full pre-push suite pass.
• Both addressed review threads are resolved.