Covers August 4 - 7, 2026.
I had a pre-commit check for credentials. When I counted where it was installed, the answer was three repositories out of fifty-one.
An exposed access token had prompted the inventory. That incident was cleaned up, but the guard that would have caught it had barely made it out of the projects where I’d first put it. None of the eleven applications derived from Spernakit had received it. They were all pinned to a template version from before the guard was added.
The Dance covered those applications once I released the template. The rest of the workspace was less uniform. Some projects had the full set of quality scripts, some could only run the leak check, and others already had their own Git hooks.
Copying the full pre-commit hook into every folder would have broken commits in projects that didn’t define the commands it called. The installer needed to check which setup each target could support. It also had to leave a hook it didn’t recognize alone.
By then I had three installers for different shared files, each with its own list of what to copy. Those lists had drifted. I’d already dealt with a smaller version of this when sharing the license code, and now the copying machinery was getting duplicated too.
On August 7 I replaced those lists with one manifest. Each group names the repository that owns the files. The checker reports which copies are missing and which are different, separately, so I can see an unfinished rollout without confusing it with a modified copy.
The write command uses the checker’s worklist. It won’t write a group from the wrong owner or overwrite uncommitted changes at a target path. Existing hooks still need to be recognized before the installer will touch them. I tested those refusals against throwaway Git repositories, along with running the installer a second time and getting no changes.
Another twenty-five repositories received the leak guard that day. The site you’re reading was one of them.