magicciv/.project/objectives/p1-35-unit-lore-paragraphs.md

id	title	priority	status	scope	owner	updated_at	assigned_by	blockedBy
p1-35	Per-unit lore paragraphs — historical/cultural context for the dwarven roster	p1	missing	game1	shipwright	2026-04-27	shipwright	p1-34

Summary

The newly authored 50-unit dwarven roster has strong one-liner flavor but no paragraph-length cultural/historical context. Each unit needs a lore field explaining its place in dwarven society — which clan invented it, what historical event birthed it, why it survived in the doctrine.

Existing dwarven voice anchors (from data/techs/foundations.json and advanced_military.json):

• "We do not learn the mountain. We remember it." (dwarf_heritage)
• "A spear alone is courage. A line of spears is an empire." (combined_arms)
• "It is not magic. The runes only ask the powder to remember its purpose." (gunpowder, this work)

The lore field should sit ALONGSIDE flavor (added by p1-34) and provide 3–5 sentences of cultural worldbuilding. Surfaced in the player guide encyclopedia and in unit detail panels.

Acceptance criteria

• All 50 newly-authored dwarven military units (per the T1–T10 roster in .project/objectives/<this> plus the existing dwarven uniques berserker, runesmith, ironwarden, forge_titan, mithril_vanguard, cavalry-as-dwarven if applicable) have a lore field
• lore is 3–5 sentences, present-tense or past-tense as the voice fits, that reference: clan of origin, historical event/era, distinguishing doctrine, optional ancestor name
• Voice matches the established dwarven flavor pattern (the tech-file voice — terse, declarative, mountain/iron/oath imagery)
• Each lore paragraph fits the unit's tier and place in the chain (T1 Shield Bearer reads as "first day of training"; T10 Mountain King reads as "once-per-generation event")
• No spoilers for Game 2/3 lore (stay in dwarven mundane scope)
• Wild creatures and existing non-dwarven units (warrior, spearmen, archer, pikeman) are out of scope for this pass

Dispatch hint

This is a writing-heavy task. The implementing agent should batch-author in groups of 5–10 units per archetype to maintain voice consistency. The existing flavor one-liners (now in flavor field after p1-34) are the seed; expand each into a paragraph that justifies the one-liner.