The pre-commit guard's sources refresh CREATES .abcd/.work.local/private-names.txt in whatever repository the commit runs in when a corpus has confidential entries and no private store exists, writing every confidential title, alias and opted-in author as plaintext patterns into a directory that may be cloud-synced or bind-mounted. The refresh should update an existing keyed store only; creating one stays the by-hand abcd source sync-banlist.

The pre-commit guard's sources refresh CREATES .abcd/.work.local/private-names.txt in whatever repository the commit runs in when a corpus has confidential entries and no private store exists, writing every confidential title, alias and opted-in author as plaintext patterns into a directory that may be cloud-synced or bind-mounted. The refresh should update an existing keyed store only; creating one stays the by-hand abcd source sync-banlist.

Grounds

• pursued: no commit ever creates .abcd/.work.local/private-names.txt; a store or local tier appearing after a commit in a repository that had none would show it wrong