[Human] Create the org team petry-projects/solution-architect (closed, notifications off, 0 members) #1633

Story

As a org owner / maintainer session,
I want create the org team that backs the persona's mention handle, with the correct privacy/notification settings and no members,
so that @petry-projects/solution-architect resolves as a mentionable, non-paging routing target so the persona can be summoned without notifying a real account.

Acceptance Criteria

1. The org team petry-projects/solution-architect exists with privacy: closed (secret teams are unmentionable) and notification_setting: notifications_disabled (routes a webhook, not a page).
2. The team has 0 members — the auto-added creator is removed — so a mention notifies no human.
3. The team slug equals the persona id (solution-architect) so the shared router resolves a mention by stripping the org prefix.

Tasks / Subtasks

• Create the petry-projects/solution-architect org team with privacy: closed and notifications disabled. (AC: test issue from agent #1)
• Remove the auto-added creator so membership is 0. (AC: Go-live improvements for PR review agent #2)
• Confirm the slug is exactly solution-architect. (AC: Add @claude delegation, auto-merge, and rebase handling #3)

Dev Notes

• Creating org teams is an org mutation OUTSIDE dev-lead's PR flow — same treatment as qa-lead's team and Epic: Onboard the bmad-bgreat-suite ops personas (sre-lead, devops-lead, security-lead) #1304's T. This is a human/session step; hands_off.
• Why closed + notifications-disabled + 0 members: '@solution-architect' bare would be a real GitHub account owned by a stranger; the org TEAM handle petry-projects/solution-architect is the routing target. Closed (not secret) so it is mentionable; notifications disabled so a mention routes a webhook rather than paging anyone; 0 members so no human is notified. Mirrors personas/security-lead/README.md §'How it is addressed'.
• This unblocks the live smoke test in V. It has no code dependency on S1/S2 and can be done in parallel, but V needs both this and S2.

Project Structure Notes

No repository change — an org-level GitHub mutation. Tracked as a story so the epic DAG captures the dependency (V depends on it), but hands_off so it is never auto-released to dev-lead.

References

• personas/security-lead/README.md#how-it-is-addressed (closed team, notifications off)
• petry-projects/.github standards/persona-standards.md §4.1
• Discussion Architectural integrity in the agentic delivery model — what enforces our standards, and where does the Solution Architect fit? #1360 §7 T

Story prepared by the BMAD Scrum Master (Bob) for epic #1627. Status: ready-for-dev.