Inventory and roll out the canonical commit-authoring and history policy

[szmyty]

Why

Prospective consistency requires more than copying one repository's files. The fleet contains several divergent commitlint/CZ implementations, most repositories use conventional subjects without the intended emoji mapping, and repository merge settings currently allow multiple history shapes.

Pace should discover compatibility, propose reviewable changes, and stage adoption after the canonical contract and reusable tools exist.

Scope

• Inventory commitlint, Commitizen/CZ, hook, Taskfile, package-script, PR-title, release, and merge-policy configuration across every repository.
• Classify repositories as canonical, compatible, divergent, missing, or intentionally exempt.
• Produce a dry-run adoption matrix with exact file/config changes and dependency ordering.
• Reuse Holon for local hooks and authoring UX, EgoLint for validation, and Relay for CI.
• Roll out through manual, observe, ratchet, and enforce waves.
• Coordinate required checks and repository rulesets without bypassing review.
• Feed adoption and drift evidence to Observatory.
• Keep existing history migration out of prospective rollout.

Acceptance criteria

• A complete fleet matrix records source configuration, compatibility, and recommended target.
• Empathy, the product repository, EgoLint, Renderflow, and Reflector divergences are explicitly reconciled.
• Dry-run output is deterministic and reviewable.
• Pilot repositories are chosen by risk and representative stack.
• Rollout PRs are bounded, reversible, and preserve repository-specific scopes where valid.
• Adoption status and exceptions are machine-readable.
• Enforce mode begins only after the organization ruleset and Relay check are proven.
• No historical commits are rewritten by this issue.

Dependencies

• Pace#2
• Pace#8
• Pace#20
• Hygiene canonical commit/change-history contract
• EgoLint canonical validator
• Relay reusable conformance workflow
• Holon local-hook baseline