program(releases): track organization-wide semantic release convention rollout

[szmyty]

Outcome

Coordinate the one-PR-at-a-time rollout of the organization release convention without moving ownership away from individual repositories.

Workstream issues

• spec(releases): define the organization-wide semantic release and changelog contract aether#61 — spec(releases): define the organization-wide semantic release and changelog contract
• policy(releases): add the repository release-convention baseline profile hygiene#27 — policy(releases): add the repository release-convention baseline profile
• feat(releases): add Python package distribution to the reusable release profiles relay#46 — feat(releases): add Python package distribution to the reusable release profiles
• feat(releases): publish reusable semantic-release preparation and verification workflows relay#47 — feat(releases): publish reusable semantic-release preparation and verification workflows
• feat(releases): validate semantic release, changelog, and version-source conformance egolint#29 — feat(releases): validate semantic release, changelog, and version-source conformance
• chore(templates): seed the organization release-convention starter surface #19 — chore(templates): seed the organization release-convention starter surface
• feat(releases): observe organization release-convention adoption and drift pace#17 — feat(releases): observe organization release-convention adoption and drift
• ci(releases): pilot the Python package release convention mindgarden#27 — ci(releases): pilot the Python package release convention
• ci(releases): pilot the Rust CLI and binary release convention aniflow#10 — ci(releases): pilot the Rust CLI and binary release convention
• ci(releases): pilot the container-image release convention realm#17 — ci(releases): pilot the container-image release convention
• ci(releases): pilot the React application and static-site release convention egohygiene.io#17 — ci(releases): pilot the React application and static-site release convention
• ci(releases): pilot the publication and multi-component workspace release convention antidote#68 — ci(releases): pilot the publication and multi-component workspace release convention
• ci(releases): adopt the portable shell-tool release convention mantle#26 — ci(releases): adopt the portable shell-tool release convention

Existing release work to reconcile, not duplicate

• ci(release): validate and publish versioned first-party skill releases aether#13
• Harden, document, and release Identity v1.0.0 identity#18
• 🚀 Establish production-grade release and distribution pipeline renderflow#297
• ✨ Finalize publication UX, release automation, and repository readiness reflector#227
• egohygiene/egohygiene#284

Adoption registry

The Pace implementation must inventory every active repository and classify it before mandatory enforcement:

• Foundation and policy: .github, Aether, Hygiene, Relay, Egolint, Pace, Holon, Observatory, Sanctuary.
• Tools and environments: Mantle, Realm, AniFlow, OptiFlow, Beacon, Mindcap, Mindgarden, Flow, Athena, RenderFlow, Identity.
• Products and publications: egohygiene, egohygiene.io, Akashic, Antidote, Reflector, Store, Civics, Filament.
• Private, incubating, and archived repositories use an explicit applicability state; they are never silently excluded.

Rollout order

1. Aether contract; in parallel, Relay feat(reflector): bootstrap organization analysis engine #6 durable reports.
2. Hygiene baseline and Relay profile/mechanics.
3. Egolint validation and .github starter surface.
4. Python, Rust, container, web, publication, and shell pilots.
5. Pace read-only fleet adoption matrix.
6. Repository-owned remediation PRs for every remaining catalog row; only later consider Pace-authored PR proposals.

Program acceptance criteria

• Every active repository has a tracked release-profile decision and root changelog status.
• Every release-capable repository is validated against the same versioned contract.
• Every profile has at least one proven consumer before broad adoption.
• External distribution/deployment state is explicit and never faked by a GitHub tag.
• No release process relies on mutable action refs, force-updated immutable tags, or unreviewed automatic version rewrites.