docs: plan derived versioning + auto-generated changelog + plugin distribution#121
Merged
Conversation
…tribution Consolidates the maintainer's interview decisions into a gated design/plan for itd-73 (impact-derived versioning) + itd-67's changelog-generation and distribution slices, fed by shipped intent/issue records. Changelog prose is host-delegated (agent-generated, never human-written); version is derived from impact (pre-1.0 breaking->minor); generation runs at the reviewed launch ship, so ADR-37 is preserved and auto-release.yml is untouched. itd-66 (deep render/parity/smoke) is deferred as a follow-up. Five gated phases (P0-P4), each detector-first with a STOP condition. Assisted-by: Claude:claude-opus-4-8
A maintainer grilling walked the full design tree and resolved every open fork, plus caught three errors in the draft: - shipped-set is a git tree-diff (ls-tree tag vs HEAD), not a log walk — immune to squash/rebase and rename detection (dissolves the Phase 1 STOP); - prose is faithful-by-construction via a completeness bijection (agent cites each record id; Go verifies the id set); the agent judges the Keep-a-Changelog section, impact is version-only; - the derived version is release-payload-only (dev tree stays version-absent per ADR-19); seed is 0.3.0 (corrects a 0.1.0 error); - surface-break taxonomy pinned; preview is deterministic-only; clean-cutover migration (one final manual roll, then derived from the next cut); - there is no abcd:CHANGELOG agent — Phase 3 authors a new composer agent modelled on press-release-composer, ingested via --changelog-json. Assisted-by: Claude:claude-opus-4-8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A gated design/plan for the derived-version + auto-generated-changelog + plugin-distribution programme (itd-73 + itd-67 changelog/distribution slices; itd-66 deferred). Consolidates a maintainer interview + a full design-tree grilling.
What it decides
impact(pre-1.0 breaking->minor); generation runs at the reviewedlaunch ship, so ADR-37 is preserved and auto-release.yml is untouched (zero workflow changes).Grilling outcomes (authoritative, top of the doc)
impactis version-only.impactrequired on intents, optional-default-fixon issues; ~5 historical intents back-filled once.abcd:CHANGELOGagent exists — Phase 3 authors a new composer agent (press-release-composer pattern), ingested via--changelog-jsonlike disembark.Phasing
P0 plan the intents + record itd-66 deferral · P1 impact field + lint + version derivation · P2 surface guardrail · P3 generation + preview · P4 manifest version + install + light smoke. Each detector-first, own PR, with a STOP condition.
Not yet built — this is the design for sign-off. An implementation prompt accompanies it.
Assisted-by: Claude:claude-opus-4-8