Frontend: Station Bot verification and guild identity administration

[GitAddRemote]

User Story

As a guild owner or guild admin, I need Station-Bot verification and guild identity administration represented as a small set of focused configuration tickets so implementation can ship in narrow, testable slices instead of one large form story.

Definition of Done

• Verification enablement and effective-state controls are delivered in User Story: Station Bot verification enablement and effective-state controls #246
• Verification role-name configuration is delivered in User Story: Station Bot verification role-name configuration #247
• Organization-member role mapping is delivered in User Story: Station Bot organization-member role mapping #248
• This umbrella issue remains a parent/checklist only and does not duplicate child implementation scope

Acceptance Criteria

• The verification domain is fully represented by child issues User Story: Station Bot verification enablement and effective-state controls #246, User Story: Station Bot verification role-name configuration #247, and User Story: Station Bot organization-member role mapping #248
• Each child issue can be completed independently without reopening scope in this umbrella
• Cross-cutting dependencies stay anchored to Tech Story: Station-Bot administration backend contract, sync model, and secure config persistence #232, Frontend: Station Bot administration shell with guild selector, feature overview, and health status #233, and Tech Story: Station-Bot administration authorization, org-to-guild mapping, and hidden navigation #242

Technical Elaboration

This issue now exists only to track the verification/identity configuration domain at a higher level. The direct implementation work is split by configuration surface:

• User Story: Station Bot verification enablement and effective-state controls #246 verification enablement and effective-state controls
• User Story: Station Bot verification role-name configuration #247 verified, temporary-member, and applicant role-name configuration
• User Story: Station Bot organization-member role mapping #248 organization-member role mapping and validation

Design Elaboration

The verification experience should still feel cohesive in the final product, but delivery should happen in smaller units so validation, copy, and Discord-side side effects can be reviewed independently.

---

Parent Epic: #231
Child Issues: #246, #247, #248
Depends on: #232, #233, #242