No forwarding headers when moving code between components

When moving headers from one library to another, delete the original file and update every #include across the codebase to point to the new location. Do not create forwarding headers, re-exports, or any backwards-compatibility workarounds.

Why: Forwarding headers add unnecessary indirection and file bloat. User considers them a workaround, not a proper fix.

How to apply: After moving a header: grep for all includes of the old path, update them in-place, delete the old file.