Creation Verification: Test All Archetype Paths

[Jasrags]

Summary

Systematically test all 5 SR5 archetype paths through the character creation sheet to verify budget constraints, data completeness, and finalization work correctly.

Parent Issue

• Creation Sheet Verification & Polish #95 Creation Sheet Verification & Polish

Prerequisites

• ✅ Phase 1 Data Verification complete ([Tracking] v0.9 Creation Verification #96) - all catalog data verified against CRB

Archetype Test Matrix

1. Mundane Character

• Priority A: Resources (450,000¥)
• Priority B: Attributes (16 points)
• Priority C: Skills (28/2)
• Priority D: Metatype (Human, 3 special attribute points)
• Priority E: Magic (None)
• Verify: No magic path selection shown
• Verify: Edge can be raised to 6 with special attribute points
• Verify: Gear purchasing with high resources works

2. Magician (Full Magician)

• Priority A: Magic (Magic 6, 10 spells, 2 skills at 5)
• Priority B: Attributes (20 points)
• Priority C: Skills (28/2)
• Priority D: Metatype (Elf, 0 special attribute points)
• Priority E: Resources (6,000¥)
• Verify: Tradition selection appears
• Verify: 10 spells can be selected
• Verify: 2 free magical skills at rating 5
• Verify: Magic attribute starts at 6

3. Technomancer

• Priority A: Magic (Resonance 6, 5 complex forms, 2 skills at 5)
• Priority B: Attributes (20 points)
• Priority C: Skills (28/2)
• Priority D: Metatype (Human, 3 special attribute points)
• Priority E: Resources (6,000¥)
• Verify: Stream selection appears (not tradition)
• Verify: 5 complex forms can be selected
• Verify: Resonance attribute starts at 6
• Verify: Sprites section available

4. Adept

• Priority A: Magic (Magic 6, 1 active skill at 4)
• Priority B: Attributes (20 points)
• Priority C: Skills (28/2)
• Priority D: Metatype (Ork, 0 special attribute points)
• Priority E: Resources (6,000¥)
• Verify: Adept powers card appears
• Verify: Power points = Magic rating
• Verify: No spell selection (adepts don't cast)
• Verify: 1 free active skill at rating 4

5. Mystic Adept

• Priority A: Magic (Magic 6, 4 spells, 1 skill at 4)
• Priority B: Attributes (20 points)
• Priority C: Skills (28/2)
• Priority D: Metatype (Human, 3 special attribute points)
• Priority E: Resources (6,000¥)
• Verify: Both spells AND adept powers cards appear
• Verify: Power points allocation UI works
• Verify: 4 spells can be selected
• Verify: Tradition selection appears

Budget Constraint Verification

For each archetype path, verify:

Attribute Points

• Cannot spend more points than allocated by priority
• Cannot raise attribute above racial maximum
• Cannot raise attribute above 6 at creation (augmented max rule)
• Special attributes (Edge/Magic/Resonance) use separate pool

Skill Points

• Skill points and skill group points tracked separately
• Cannot raise skill above 6 at creation
• Skill groups must be purchased as groups (no splitting)
• Free skills from priority applied correctly
• Specializations cost 1 skill point OR 7 karma

Karma

• Starting karma = 25
• Positive qualities cost karma
• Negative qualities give karma (max 25 from negatives)
• Karma can convert to nuyen (2,000¥ per karma)
• Cannot go negative on karma

Nuyen

• Starting nuyen from Resources priority
• Gear availability ≤ 12 at creation
• Cannot spend more than available
• Lifestyle requires at least 1 month prepaid

Essence

• Starts at 6.0
• Cyberware/bioware reduces essence
• Cannot go below 0.01
• Magic rating capped at current Essence (rounded down)

Finalization Checks

• Character cannot be finalized with validation errors
• All required fields populated (name, metatype)
• At least 1 contact selected
• Budgets are within limits
• Draft status changes to "active" on finalize
• Character appears in character list after finalization

Test Environment

• Browser: Chrome, Firefox, Safari
• Viewport: Desktop (1920x1080), Tablet (1024x768), Mobile (375x812)
• Dev server: pnpm dev

Acceptance Criteria

• All 5 archetype paths complete creation successfully
• Budget constraints enforced at all stages
• Validation errors prevent finalization when rules violated
• Character data persists correctly through finalization
• No console errors during creation flow