ACI-034: Namespace Archaeology

Thesis

A codebase's rename history records when its team understood the domain well enough to name it, and a misplaced name gathers callers fast, so rename on purpose and early. A rename is cheap in the tree and expensive wherever something keys on the name: before renaming, ask what reconciles by it, and where anything does, give the content a durable id it carries, enforced at the boundary and stamped by the system. Make a new field required through a time-boxed dual path whose lock is committed in advance.