[jinxiao]

Issue

Closes #23

Summary

A component-only fix previously left the repository with different module versions, and selecting all modules did not guarantee they matched. New preparations now always include the full maintained cohort and choose one shared version from all accumulated component/repository notes and reserved tags. A Logger-only fix advances every maintained component together and synchronizes internal requirements, sums and workspace mappings automatically.

The root version Release groups actual changes by component/repository and provides the full version table. It remains a draft until every component consumer and Release succeeds, then is finalized last and marked Latest for stable releases. Independent Go module/import paths and required prefixed tags remain intact. Remove component selection from Actions and replace the Release issue form with a shared-version field.

Testing

• 21 isolated automation regressions passed with real Git/Go metadata, including Logger-only cohort patching, aggregate feature increments, reserved nested tags, divergent published baselines, rollback, native PR activation and legacy plan recovery.
• 37 offline release regressions passed with pinned GoReleaser OSS v2.18.2, including partial/mixed plan rejection, stale internal requirement rejection, unified notes, failure/resume ordering, and real CLI root/component/prerelease draft/finalization and stable-root Latest requests against a local GitHub fixture.
• 18 contribution/form regressions passed.
• actionlint v1.7.12 and git diff --check passed.
• Native required PR policy, module/Lambda and strict documentation checks run before merge.

Risks and compatibility

Every future release includes all maintained modules, including those with no feature changes. tools/modules.json records release_version and schema-2 plans enforce the cohort and aligned internal requirements. Old schema-1 plans remain recoverable only against pre-policy metadata at their original immutable commits. Development modules and the frozen tracer/xray adapter remain excluded. No third-party dependencies, module paths or Go APIs change. Existing v0.1.0 tags, notes and publication evidence are preserved. This feature PR does not prepare or publish a new version.

Release notes

• repository | feature | Release all maintained components at one shared version with a grouped project changelog and automatic dependency alignment.

Checklist

• The issue records the scope and acceptance criteria
• Tests and documentation match the change, or I explained why they are not applicable
• I kept CGO disabled and did not run cloud AWS tests without authorization
• I excluded credentials, personal configuration, and generated build artifacts