Changes for version 0.006 - 2026-11-17
- The update of GitHooks installs each hook where git runs it from, as git rev-parse --git-path hooks says, so it honors core.hooksPath. Before, it always wrote into the hooks directory of the common git directory, which git does not read when core.hooksPath is set. So with a core.hooksPath of the tracked directory, such as git-hooks, the update installed a copy that nothing ran, and reported the install again whenever another worktree had installed different bytes. Now it finds the hooks installed where they are tracked. A checkout whose .git git cannot read is now an error of git, not a checkout without hooks.
Documentation
Check a repository against its flavor of the standards, and bring it up to date
Modules
Whether the development harness of a repository conforms to its standards, and bringing it up to date
The interface of a check, and what the checks share
CLAUDE.md exists and names the skills that it must
.claude/settings.json enables the plugins of the harness
The perlcritic profile enables or turns off every policy of its template, and no retired one
A JSON, YAML or INI file parses and matches a schema
A distribution has the files that its build needs
The git hooks are tracked, match their templates, and are installed
An INI file, such as dist.ini, sets no key that the flavor refuses, and the update removes each one
The system packages that a repository declares in metamerge.yml, validated, and resolved for a host
The configuration files of the tools exist
The CI workflows exist
.conformance.yml, which picks the flavor of a repository and its source
A named set of checks and their configuration, read from a standards source
Parse YAML, JSON and INI, and validate the result against a schema
What a check can read of a repository: its paths, their blob SHAs and their contents
A snapshot of a checkout on this machine, which an update can change
A snapshot from a tree listing and a callback that fetches one file
Where the standards come from: the flavor files and the templates
Standards read from a directory on this machine
Standards fetched from a git repository into a cache directory
What an update changed, or would change, in a checkout, and what it left to a person