/ 
Dist-Conformance-0.004

Changes for version 0.004 - 2026-11-10

  • The update of CriticProfile appends to a profile that is there each policy of the template that it lacks, as the template writes its section, and leaves every line of the profile as it was. It used to leave them for a person, unless replace: true overwrote the profile.
  • New check RefusedIniKeys: an INI file, such as dist.ini, sets no key that the flavor refuses for a plugin, such as user under [GithubMeta]. Unlike DataSchema, its update removes each such line, and nothing else.

Documentation

conformance
Check a repository against its flavor of the standards, and bring it up to date

Modules

Dist::Conformance
Whether the development harness of a repository conforms to its standards, and bringing it up to date
Dist::Conformance::Check
The interface of a check, and what the checks share
Dist::Conformance::Check::ClaudeMd
CLAUDE.md exists and names the skills that it must
Dist::Conformance::Check::ClaudeSettings
.claude/settings.json enables the plugins of the harness
Dist::Conformance::Check::CriticProfile
The perlcritic profile enables or turns off every policy of its template
Dist::Conformance::Check::DataSchema
A JSON, YAML or INI file parses and matches a schema
Dist::Conformance::Check::DistFiles
A distribution has the files that its build needs
Dist::Conformance::Check::GitHooks
The git hooks are tracked, match their templates, and are installed
Dist::Conformance::Check::RefusedIniKeys
An INI file, such as dist.ini, sets no key that the flavor refuses, and the update removes each one
Dist::Conformance::Check::SystemPackages
The system packages that a repository declares in metamerge.yml, validated, and resolved for a host
Dist::Conformance::Check::ToolConfiguration
The configuration files of the tools exist
Dist::Conformance::Check::Workflows
The CI workflows exist
Dist::Conformance::Config
.conformance.yml, which picks the flavor of a repository and its source
Dist::Conformance::Flavor
A named set of checks and their configuration, read from a standards source
Dist::Conformance::Schema
Parse YAML, JSON and INI, and validate the result against a schema
Dist::Conformance::Snapshot
What a check can read of a repository: its paths, their blob SHAs and their contents
Dist::Conformance::Snapshot::Directory
A snapshot of a checkout on this machine, which an update can change
Dist::Conformance::Snapshot::Tree
A snapshot from a tree listing and a callback that fetches one file
Dist::Conformance::Source
Where the standards come from: the flavor files and the templates
Dist::Conformance::Source::Directory
Standards read from a directory on this machine
Dist::Conformance::Source::Git
Standards fetched from a git repository into a cache directory
Dist::Conformance::Update
What an update changed, or would change, in a checkout, and what it left to a person

Other files