fix(openworlds): add aasimar lineage to RACES (Closes #375)

[100yenadmin]

TL;DR

Adds aasimar as a first-class lineage in RACES (CHA +2, WIS +1 per 5e canon Protector tradition), retroactively validating Dame Aylin's existing PORTRAIT_GALLERY entry (race: "aasimar"). Closes the race-tag drift the --ui-gate gallery_per_race probe (PR #386) flags as unknownRaces: ["aasimar"].

Closes / addresses

• Closes fix(openworlds): Dame Aylin tagged race:'aasimar' is not a valid RACES key (PORTRAIT_GALLERY filter never matches) #375 (Trivial — Dame Aylin tagged with invalid RACES key)
• Pairs with PR feat(qa): ui_gate_probe — gallery_per_race ≥ 1 check (Addresses #382) #386 (gallery_per_race ≥ 1 gate that detects this class of drift)
• Surfaced during Loop 10 verification of PR fix(openworlds): create — #277 #281 #315 #369

What this lands

One additive entry at viewer/openworlds/screen-create.jsx:866:

aasimar: {
  name: "Aasimar",
  size: "Medium",
  life: "160 years",
  glyph: "aasimar",
  body: "Touched by something brighter once. Bears a heritage older than empires, and the unsettling habit of catching candle-light at the wrong angles. Born to the Upper Planes' echo; walks the world unsure whether to atone or to lead.",
  bonus: { cha: 2, wis: 1 },
},

Why option (1), not option (2)

#375 offered two paths:

1. Add aasimar to RACES (lineage-positive)
2. Re-tag Dame Aylin → human (drift-patching)

Picked (1). Aasimar IS a canonical 5e lineage (PHB-adjacent, Volo's Guide) AND a canonical BG3 lore lineage (planetouched). Re-tagging Aylin would patch the drift but cost real CRPG-canon fidelity. Players coming from D&D Beyond / Kingmaker / BG3 will expect Aasimar on a character-creation screen.

5e canon mapping

Field	Value	Rationale
Size	Medium	Volo's Guide
Life	~160 years	"live longer than humans"
ASI	CHA +2, WIS +1	Protector tradition (most common in BG3 lore, closest fit for the existing flat-RACES bonus style)

Subraces (Protector / Scourge / Fallen) and full trait set (Celestial Resistance, Healing Hands, Light cantrip) deferred — same pattern as the other 11 races, which don't yet expose subraces or full trait sets either.

Smoke test (post-fix, regex from #386 against patched file)

Counts per race (after this PR):
   human        4
   halfling     0  ← still empty (#379 — next PR with empty-state)
   dwarf        0  ← still empty
   elf          2
   half         2
   tiefling     1
   dragonborn   0  ← still empty
   drow         1
   githyanki    1
   gnome        0  ← still empty
   half-orc     0  ← still empty
   aasimar      1  ← Dame Aylin now reachable ✓
Unknown race tags: []  ← drift CLOSED ✓

Acceptance criteria (per #375)

• ☑ Option (1) chosen: aasimar added to RACES with proper ability bonuses (CHA +2, WIS +1)
• ☑ Closest lore fit (Protector Aasimar tradition)
• ☑ Lore-line body copy matches existing prose style (mythopoetic, present-tense, character-not-encyclopedia)
• ☑ Dame Aylin's PORTRAIT_GALLERY entry now validates (verified via regex smoke)
• ☑ --ui-gate gallery_per_race unknownRaces set is now empty (verified)

Out of scope (intentionally)

• Empty galleries for dwarf / halfling / gnome / dragonborn / half-orc — separate fix(openworlds): portrait gallery empty for 5 of 11 races (dwarf, halfling, gnome, dragonborn, half-orc) #379 fix coming next with empty-state fallback
• Full subrace handling — feat(openworlds): create — subrace handling in race + portrait selection (#315 AC5) #377
• Aasimar racial trait set beyond ability bonuses — deferred until the other 11 races get full trait sets too (consistency)
• Updating CREATE_RACE_IDS in qa/ui_gate_probe.js — that lives on PR feat(qa): ui_gate_probe — gallery_per_race ≥ 1 check (Addresses #382) #386 (unmerged); will rebase feat(qa): ui_gate_probe — gallery_per_race ≥ 1 check (Addresses #382) #386 to include 'aasimar' once this lands

Collision audit

• viewer/openworlds/screen-create.jsx last touched on main by PR fix(openworlds): create — #277 #281 #315 #369 (fix(openworlds): create — #277 #281 #315). Adding a single RACES entry at the end of the table doesn't conflict with any open PR's surface.
• Main agent's open fix(dm,viewer): cold-open delivers a real 2nd-person opening scene, not the setup brief (Addresses #357) #388 is fix(dm,viewer): cold-open delivers a real 2nd-person opening — DM/cold-open territory, zero overlap.
• This PR is additive: removes nothing, modifies no existing entry.

DO NOT MERGE yet

Per owner direction. Ready for review.

Summary by CodeRabbit

New Features

• Added Aasimar as a playable race option in character creation with +2 Charisma and +1 Wisdom stat bonuses.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0af8b8d6-8de6-43e0-a63d-bdbf575d2ad8

📥 Commits

Reviewing files that changed from the base of the PR and between bb1870d and 9fd1ab2.

📒 Files selected for processing (1)

• viewer/openworlds/screen-create.jsx

---

📝 Walkthrough

Walkthrough

The PR adds the aasimar race to the RACES data structure in the character creation screen, including display metadata (name, size, lifespan, glyph, flavor text) and ability bonuses (Charisma +2, Wisdom +1). This resolves the data inconsistency where Dame Aylin in the portrait gallery was tagged with a race key that did not exist in the playable races table.

Changes

Aasimar race definition

Layer / File(s)	Summary
Aasimar race entry viewer/openworlds/screen-create.jsx	RACES is extended with an aasimar key containing name, size (Medium), lifespan (160 years), portrait glyph, flavor text, and ability bonuses (Charisma +2, Wisdom +1) matching 5e canon.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

• electricsheephq/WorldOS#375: This PR directly addresses the missing aasimar race key, making Dame Aylin's portrait entry reachable through the character creation race filter.

Possibly related PRs

• electricsheephq/WorldOS#369: Both PRs extend the RACES table in viewer/openworlds/screen-create.jsx with additional playable race definitions.

Poem

🌟 A winged celestial joins the fold,
Charisma shines and wisdom's gold—
Dame Aylin now can truly be
Selected by our hero's decree!
🐰 ~CodeRabbit

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: adding aasimar lineage to RACES and closing issue #375. It is specific, directly related to the changeset, and helps developers understand the primary objective.
Description check	✅ Passed	The description is comprehensive and well-structured. It includes a summary of changes, detailed rationale for the chosen approach (option 1), mapping to 5e canon, acceptance criteria verification, and out-of-scope items. Both required CLA sections are missing but the substantive content exceeds template expectations.
Linked Issues check	✅ Passed	The PR fully addresses issue #375 requirements: adds aasimar to RACES with correct fields (name, size, life, glyph, body) and ability bonuses (cha: +2, wis: +1), provides 5e canon rationale, includes smoke-test validation, and verifies Dame Aylin is now reachable. All acceptance criteria from the linked issue are met.
Out of Scope Changes check	✅ Passed	The PR is purely additive—a single RACES entry addition with no modifications to existing entries or unrelated changes. All explicitly out-of-scope items (empty galleries, subraces, full trait sets, qa/ui_gate_probe.js updates) are correctly deferred to other PRs (#379, #377, #386), demonstrating good scope discipline.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[100yenadmin]

Superseded by #653 — a fresh re-implementation off current main with a RED→GREEN regression guard (this stale branch was 4–8 days behind). Closing the stale PR.