docs: reconcile Common Changelog release history

[jamesreimer]

Outcome and authority

Implement the settled Issue #14 contract and its current-main amendment. Issue closure on merge: none. Issue #14 remains open for Planning's exact-candidate review, independent review, and later publication disposition.

Add supported repository release history through v0.2.0 and retain future summaries in PR descriptions. No next version or standing Unreleased section is created. This candidate does not execute Agent Workflows #17 or repo-template #53.

• Base: d358c22438b80053a37cf173c1f652952fb35e2a (verified local HEAD and fetched canonical main before implementation).
• Candidate: 5362ef7
• Upstream: repo-template v1.3.0, commit 1d4d26a784f6450dd1d9d4221e4dc068a5e0b687, annotated tag object 861b4083467cca05c5cb276b69cb545fa5dab68d, published 2026-09-29T00:02:33Z. Independently read the tag ref, annotated object and target, and release timestamp through GitHub API. The earlier Stage 1 commit is not the reconciliation target.

Surface comparison and adaptations

Read all six corresponding upstream files directly at the exact release commit and compared their applicable responsibilities against the downstream base and candidate. This is a scoped Common Changelog reconciliation, not a claim of repository-wide byte identity.

Changed file	Correspondence and local adaptation
CHANGELOG.md	Adopt Common Changelog format, group order, imperative entries, commit/PR references, and release links. Replace upstream history with five independently verified local releases. Initial release uses a brief notice.
CONTRIBUTING.md	Adapt upstream PR-summary retention, final-candidate review, release curation, no-Unreleased rule, and backfill disclosure. Explicitly preserve canonical role/handoff/workflow, source-pin, project-evidence, and publication-authorization responsibilities.
.github/pull_request_template.md	Adopt lightweight summary-or-not-notable prompt; add a link to the local canonical GitHub issue-closure guidance, usable from copied PR text.
MAINTAINING.md	Adapt upstream reviewed preparation before candidate selection, whole-delta and carried-forward summary checks, version/date/link checks, and actual UTC publishedAt verification. Preserve local pre-1.0 version rules, exact-candidate qualification, annotated-tag correspondence, and explicit human publication authority.
AGENTS.md	Add only Common Changelog format routing to contribution/release owners; preserve existing project authority and source routing.
README.md	Add local release-history discovery and responsibility routing. Upstream new-repository bootstrap/reset instructions are inapplicable to this existing library.

Common Changelog governs format only. The changelog does not replace GOVERNING-SOURCES.md, canonical reusable artifacts, instantiated handoffs, exact source pins, Git/PR/Issue history, GitHub Releases, or authorization evidence. No governing-source pin, role, handoff, workflow, validator, dependency, runtime, CI configuration, or license changes in this candidate.

Pre-1.0 semantics remain: compatible additions and incompatible changes use MINOR; compatible fixes/clarifications use PATCH; the existing v1.0 evidence gate remains intact. Backfill does not relabel historical patches as semantic workflow changes or claim stable 1.0 maturity. Consumers select revisions deliberately, preserve local adaptations under their own authority, and update copies/instances explicitly. A repository release does not adopt consumer standards, advance consumer pins, transfer roles, or grant execution/publication authority.

Historical evidence

For each section, read its GitHub Release body and actual UTC publishedAt, verify local annotated tag object and peeled commit against git ls-remote --tags origin, inspect release trees/deltas and supporting merged PR evidence. All five tags are annotated. Exact identities and timestamps follow.

Release	UTC publishedAt	Annotated tag object	Peeled release commit
v0.1.0	2026-09-23T06:00:49Z	b774d1756b799a9191725a6beb30f964580c9ad6	4f716ece97bd5a5ffe56facf1e42f449e28bfa45
v0.1.1	2026-09-23T20:31:08Z	f0f39f408b0305b15b5376ae0b8c4011f8fd326e	1072f198cf64cc94f295931d0f3233ef6cb5c2fe
v0.1.2	2026-09-23T20:43:40Z	97649c1dcfb7185b1f3899da762f737879d33e3e	e7f11b4bf684223c071511dac7689da22346b49a
v0.1.3	2026-09-24T02:03:42Z	cba28939e6da06aae787c876c8f28128637a69f3	512c3fcda4b74a3639a0b51058a2c96433d7156d
v0.2.0	2026-09-28T06:01:01Z	82869b1e65dac11c5fdf2ea5833c00e3ae86954e	d288d778685de43aab306f4609773c460acbef32

• v0.1.0: release notes, release tree, initial implementation PR #1 and repository readiness PR #3 support four roles, five handoffs, reviewed-change, authority/evidence separation and qualification support. Use an initial-release notice without inventing a prior delta.
• v0.1.1: full v0.1.0...v0.1.1 diff and PR #5 touch maintenance/title and the then-existing provenance record only. No canonical workflow or source-pin change.
• v0.1.2: full v0.1.1...v0.1.2 diff and PR #7 support updated five source references, repo-template v1.2.1 correspondence and stale release wording correction. PR evidence records byte-identical normative source text and unchanged edition 1.0; this task does not re-audit historical source qualification independently.
• v0.1.3: release diff, canonical source registry and artifact substitutions, and PR #9 support PROVENANCE-to-GOVERNING-SOURCES responsibility correction and anchor migration. Pins remain at df73ad31cdbb15210ad9670d669d3c567a79a1d3; workflow requirement force is unchanged. Historical consumers referencing old paths need deliberate reference updates.
• v0.2.0: full v0.1.3...v0.2.0 diff and PR #10/PR #12 support latest-release discovery, role continuity, ready-to-use transfer, final-success validation, exact source verification, PRI and expanded publication evidence. PRI is added at debd50926ea45c371a7b10237ef9aba1b3b04304, edition 1.0; existing five pins remain unchanged. Release notes characterize these as compatible pre-1.0 additions; integrations tied to handoff table labels require review and were not tested.

No unsupported historical point identified. Backfill is explicitly retrospective. #15/PR #16 belongs after v0.2.0; the current-base diff confirms its three canonical publication surfaces, and it is retained below rather than assigned a release.

Carried-forward next-release summary — #15

Add GitHub issue-closure safety across PR closing relationships, controlling commit messages, and final landing messages; resolve canonical full issue identities, verify final host state, bind merge correspondence to the exact head, and verify resulting issue states after merge while preserving lifecycle and host-neutrality semantics.

Evidence: Issue #15, PR #16, published commit d358c22. PR #16 is not edited. Future release preparation owns curation through the new procedure; this summary is durably retained here.

Proposed next-release summary — #14

Add Common Changelog release history with supported retrospective backfill through v0.2.0, retain notable-change summaries in PR descriptions, and integrate reviewed release preparation with UTC publication-date verification while preserving pre-1.0 and consumer-authority boundaries.

Evidence: Issue #14, this PR and exact candidate above. Repository maintenance and documentation only; no reusable workflow semantics or governing-source pins change.

Validation and host correspondence

• Full .venv/bin/pre-commit run --all-files --show-diff-on-failure: PASS on final staged candidate, including Markdown authoring and link regression suites, local links, Ruff, actionlint, artifact validator and tests. Expected no-files skip for broken symlinks only.
• python3 scripts/validate_local.py: PASS; python3 -m unittest discover -s tests: PASS, five tests.
• git diff --check and git diff --cached --check: PASS; npm audit: zero vulnerabilities. Node v24.18.1.
• Final staged tree is committed without further content changes. No validator mutation or new policy exception: root filenames are unrestricted, local artifact checks cover roles/handoffs/workflows, and no generated structure inventory exists. Additional positive/injected-defect policy tests are inapplicable; existing regression suites remain active.
• Independently read effective main rules: ruleset 23862052 requires Repository validation from integration 15368, strict up-to-date checks, squash PRs, resolved review conversations, and blocks deletion/non-fast-forward updates. No host mutation. The unchanged workflow checks out github.event.pull_request.head.sha || github.sha and runs for every PR. Broader host reconfiguration is inapplicable to this documentation-only reconciliation.
• Hosted validation: final SUCCESS on exact candidate 5362ef73106d1f5e68f48d685b82226bf4e7302b: run 36674964784, Repository validation job. Run head SHA and checkout log both resolve the exact candidate; required-check readback reports pass.
• Closure readback: PR docs: reconcile Common Changelog release history #18 closingIssuesReferences is empty; Issue reconcile Common Changelog baseline from repo-template #14 is OPEN. The PR description and sole candidate commit subject/body contain no issue-closing command targeting a real issue. PR head and base match the identities above; worktree is clean. Recheck after any description/head/relationship or landing-message change before publication.

Mechanical checks do not establish historical interpretation or source-force correctness; manual implementor comparison is separate from required independent review. External links are skipped by the local link checker; release, PR, tag and upstream references used here were read directly. No live publication/date-mismatch experiment or consumer integration test was performed.

Material consequence dispositions

• Handled here: historical context and source-pin distinctions, retrospective disclosure, contribution-time evidence retention, carried-forward prevent accidental GitHub issue-closing keywords in handoff prose #15 summary, reconcile Common Changelog baseline from repo-template #14's own summary, release curation and publication-date evidence/correction in existing work records, deliberate consumer updates, safe issue prompting.
• Inapplicable: naming-policy exception, structure inventory, validator extension/tests, tag-only completion procedure, automatic downstream adoption, host/settings changes, source-pin advancement, reusable role/runtime redesign, sibling repository changes. Existing release mechanics use annotated tags plus GitHub Releases.
• Durably owned by existing work: Planning's exact-candidate assessment, required independent review and later authorized publication remain with Issue #14 and this PR. The separate reusable consequence-disposition rule remains owned by Issue #17, which this task does not implement. No new unowned material consequence identified.

Return to Planning / Primary Author

Act as Planning / Primary Author under the settled Issue #14 contract and amendments. Review the exact candidate against the base above and this evidence, then arrange the required independent review without mutating the candidate. Assess supported release backfill, upstream correspondence, pre-1.0 and source/consumer boundaries, carried-forward summaries, UTC date handling and issue safety. Return material findings to authorized Implementation for correction and requalification. Completion of this handoff is an exact-candidate assessment and independent-review disposition in the existing Issue #14/PR record; issue completion and publication require their actual later authority.

This Implementation return stops at one open validated PR. No merge, release, tag, issue closure, or unrelated merged-PR edits were performed. Publication must establish its actual landing message and repeat the complete canonical issue-closure gate immediately before any later authorized merge; present readback is candidate evidence only.