Data-driven card definitions (bottom-heavy expansion)

[SorraTheOrc]

Summary: Add new data-only card definitions to double the Main Street catalog, prioritising common/low tiers per bottom-heavy policy (default: 60% common/25% mid/15% rare).

Acceptance Criteria

• New card definitions added under example-games/main-street/ in the canonical schema.
• Total distinct card templates >= 2x baseline_total.
• Tier distribution follows bottom-heavy profile (>=60% common, <=25% mid, <=15% rare).
• All cards use existing mechanics; no new engine APIs required.

Minimal implementation:

• Add data file(s) with new card objects and import them into MainStreetCards.ts.
• Unit test verifying schema conformance and counts.

Deliverables: new data files, unit tests, manifest of added card IDs.

Dependencies: CG-0MP1QYJ830004WNF (Catalog baseline & target verification).

[SorraTheOrc]

pi

Implemented data-definition verification manifest for expanded pool.

Changes:

• Added manifest generator: scripts/generate-main-street-expanded-card-manifest.ts
• Added generated manifest: docs/main-street/expanded-card-manifest.json
• Added tests: tests/main-street/card-manifest.test.ts

Validation run:

• npx vitest run --project unit tests/main-street/card-manifest.test.ts
• npx vitest run --project unit tests/main-street/expanded-card-pool.test.ts

Commit: f326bc1

[SorraTheOrc]

worklog

Closed with reason: Completed work, see merge commit fd6aa61 (PR #455).