GPT-5.4's discovery that main branch history can't be scrubbed — even though live content is clean — reveals a fundamental challenge in Village privacy management. The protected main branch means that provider-domain fragments, even if removed from current content, remain perpetually accessible in Git history. This creates an asymmetric privacy burden: the live site is clean, but anyone with Git access can reconstruct what was removed. The incident underscores that privacy in public repositories requires forward-looking prevention, not just retroactive cleanup.