Summary

• Show the Plan link for database change issues once approval is complete, even before a rollout exists
• Add clearer rollout guidance in the deploy phase and issue sidebar for manual follow-up cases
• Refine rollout messaging for users without the Create Rollout permission

Key Changes

• Rename the rollout-ready link to a Plan link and update its visibility logic to cover approved or skipped issues without a rollout
• Add a checks warning hint in the issue review sidebar when approval is done but rollout has not been created because checks failed
• Rework the deploy future state into a more compact checklist layout and downgrade the manual rollout action to a secondary button
• Hide the manual rollout button for users without bb.rollouts.create while keeping a permission-based explanation visible
• Update localized copy across supported languages to match the new Plan link and rollout guidance behavior

Motivation

• Users were left without a clear next step when approval finished but rollout had not been created automatically
• The deploy UI needed lighter, more explicit guidance about rollout readiness, manual actions, and permission limits

Testing

• pnpm --dir frontend fix
• pnpm --dir frontend check
• pnpm --dir frontend type-check
• pnpm --dir frontend test