Constraint: L0 must stay free of GameFramework/Unity parsing concerns after the 2026-05-12 boundary correction
Rejected: Keep prior L0/L1 file classifications | would continue to misroute parser and IDataRow work
Confidence: high
Scope-risk: narrow
Directive: Treat historical IDataRow-based Domain entries as transition state until they are moved to L1
Tested: Recounted TODO summary figures and cross-checked the updated boundary notes against current repository state
Not-tested: No code changes or runtime validation involved
- Add BinaryReaderExtension with Vector2/3/4, Quaternion, Color, Rect types
- Implement ParseDataRow(byte[]) in TagRow and RarityTagBudgetRow
- Update CLAUDE.md with GameFramework module table and improved architecture docs
- Remove unnecessary InternalsVisibleTo and L1 wrapper classes
Co-Authored-By: Claude <noreply@anthropic.com>
- Mark TagRow/RarityTagBudgetRow as implemented
- Mark TagGenerationRuleRegistry/RarityTagBudgetRuleRegistry as migrated
- Add new architecture note for L0/L1 IDataRow separation
- Add wave 3 modification record section
- Update dependency chain and priority sections
Co-Authored-By: Claude <noreply@anthropic.com>
- Add TagRow and RarityTagBudgetRow implementing GameFramework IDataRow
- Migrate TagGenerationRule and RarityTagBudgetRule to Domain layer
- Migrate TagGenerationRuleRegistry and RarityTagBudgetRuleRegistry
to use IEnumerable<TagRow> instead of DRTag
This establishes the foundation for DR migration: L0 now has pure C#
IDataRow implementations while L1 will provide DataRowBase wrappers.
Co-Authored-By: Claude <noreply@anthropic.com>
Basil
SepComet
SepComet