fix: resolve Blizzard roster class names and skip unusable members

[Erilla]

shurkle reached the sweep this time — cap reserved 300, fingerprintDurationMs=1155, 2 requests used — and then failed upstream_schema_changed.

Verified against the live Blizzard API (credentials injected by railway run, never printed):

member.character keys: faction, id, key, level, name, playable_class, playable_race, realm
playable_class keys: id, key          ← no "name"
members missing playable_class.name: 393 of 393

The guild roster does not carry class names; they come from the static playable-class index. normalizedRosterCharacter required playable_class.name, so every member became null, members.every(m => m !== null) rejected the roster, and the sweep raised non-retryable schema_drift. No guilded root could ever have been swept.

The unit test passed because its fixture invented playable_class: { name: "Mage" }. That fixture is now the real shape, { id: 8 }, and the test asserts the name is resolved.

• Class names are resolved once per process from /data/wow/playable-class/index (namespace=static-<region>), accounted through the same observer, so it is one extra request per sweep, not per member. An inline playable_class.name is still accepted if Blizzard ever sends one.
• A member the key space cannot represent is now skipped rather than fatal — the same treatment Raider.IO claimed characters already get, whose test comment warns that "one out-of-scope claimed character could turn every search for that player into a permanent schema-drift failure". The roster path repeated exactly that mistake.
• A missing members array remains structural drift.

Both roster tests were red with blizzard_schema_drift before the change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Qh8Zb2HnaxebWrRLUMoAiv