Remove superseded fork accounting and harden migrations

[iam-brain]

Question

Only after sufficient flagged real-world validation, remove superseded fork-specific aggregation in a dedicated PR and make the lineage ledger authoritative. Preserve parsed-document cache compatibility where safe, invalidate incompatible accounting schemas, prevent legacy and lineage totals from mixing, retain permanent family-level containment, and document emergency rollback or migration behavior.