[Phase 4] Role-adaptive tutorial content with a safe default #337

Story

As a first-time TalkTerm user with a stated role,
I want have the tutorial's brainstorm topic and examples match the role I gave during setup,
so that the exercise feels relevant to my actual work so the artifact I leave with is something I might genuinely use.

Acceptance Criteria

1. The tutorial reads the user's role from the profile captured during setup (Epic 2).
2. Step-4's brainstorm topic (and any role-flavored examples in earlier steps) are selected from a small set of role-appropriate variants.
3. When the role is missing, unknown, or unmapped, the tutorial falls back to a sensible generic variant and never errors or blocks.
4. The set of role variants is defined in one place so a new role can be added without touching the step engine or step control flow.

Tasks / Subtasks

• Read the stated role from the profile written during setup (Epic 2). (AC: Install BMad Method v6.2.0 with Claude Code integration #1)
• Define a role->content-variant mapping (brainstorm topic + any role-flavored examples) in a single content table. (AC: Add brainstorming session: TalkTerm concept review and revision #2, Bump actions/create-github-app-token from 1 to 3 #4)
• Select the variant at tutorial start and feed it into the step content from story 3. (AC: Add brainstorming session: TalkTerm concept review and revision #2)
• Add a generic default variant used when role is missing/unknown/unmapped. (AC: chore: add Dependabot with auto-merge via GitHub App #3)

Dev Notes

• This story only selects CONTENT; it must not add branching to the step engine (story 2) or fork the step definitions (story 3). Selection happens once at tutorial start and parameterizes the existing steps.
• The exact place the role is stored and its enumerated values depend on Epic 2 setup (open question); code against a single accessor so the source can be adjusted without touching the mapping.
• The default variant is load-bearing for the non-technical audience whose role may be blank on first run — it must be a complete, shippable experience, not a degraded stub.
• Testing: table-drive the mapping (known roles -> expected variant; missing/unknown -> default) as a pure function independent of the UI.

Project Structure Notes

Adds a role->variant content table and a one-shot selection at tutorial start; no engine or step-flow changes.

References

• Ideas Discussion 💡 Guided Interactive Onboarding: Avatar-Led Learn-by-Doing First Session #245 — Summary (tutorial adapts based on the user's stated role)
• TalkTerm PRD — Journey 1 (role-driven first workflow)
• TalkTerm Epic 2 — setup captures the user's role

Likely target surface

• role accessor from profile
• role->content-variant table
• one-shot variant selection at tutorial start

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