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
- 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>
Basil
SepComet
SepComet