Propagate spec rename and privacy-policy decisions through code comments, registries, and tests

A privacy backfill plan was renamed and updated with confirmed policy decisions, but dependent code comments, validation registries, and unit expectations still referenced the old spec path and an old exemption for staff-authored notes. This created documentation drift and a risk that backfill tooling would preserve a text column that policy now requires scanning.