[Improve] Sharpen Triage GitHub Issues plan and clarification comments

[roomote-roomote]

Opened on behalf of Matt Rubens. Follow up by mentioning @roomote-roomote, in the web UI, or in Discord.

Related issue

N/A — follow-up polish after #557.

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

What changed

Updated Triage GitHub Issues comment templates:

• Clearer clarifying-question and proposed-plan shapes
• Less exact gh CLI ceremony
• Mentions use the deployment-configured GitHub App slug via resolveConfiguredGitHubAppSlug() / getGitHubAppMention() instead of hard-coded @roomote

How it was tested

• Unit test for slug injection in buildIssueFixerFixPrompt
• Typecheck + pre-push green

Checklist

• The PR title follows the repo convention
• This PR is small and scoped to one change
• pnpm lint and pnpm check-types pass locally
• Added a focused unit test for the mention injection
• I removed secrets, tokens, private keys, and customer data
• If this change should appear in the changelog, I ran pnpm changeset

[roomote-roomote]

No code issues found. See task

• packages/cloud-agents/src/server/issue-fixer-prompt.ts:97 and :109: The templates hard-code @roomote, but GitHub mention routing matches the deployment's configured app slug. This deployment uses @roomote-roomote, so replies following either template will not trigger the implementation task; inject the configured app mention instead.

_{Reviewed 2b59337}