feat: make changesets self-describing - #40
Merged
Conversation
## Summary - Stamp changeset commit messages and PR bodies with durable metadata - Rehydrate chain topology from live git refs and supplied GitHub records - Render chain status without plan or state files - Cover fresh-clone reconstruction, rebase preservation, and ambiguity failures ## Why - Make materialized and published changesets independently reconstructable - Establish a disjoint module seam for the consolidated CLI to consume
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.
TL;DR
Makes materialized and published changesets reconstructable from commit trailers, PR metadata, and live git/GitHub evidence without local plan or state files.
Summary
Changeset-Slug,Changeset-Index, andChangeset-Sourcetrailer stamping throughgit interpret-trailers..carve-changesets/, trailer survival through rebase propagation, and missing/conflicting evidence failures.Scope boundary
cli.py, invokegh, port create-chain extraction, removestate.json, rebuild merge/propagate, or change plan authoring.skills/prepare-changesets/remains frozen and untouched.Validation
just format— pass.just lint-py— pass.just lint-md— pass.just test-carve-changesets— pass (12 tests).just test— pass (191 tests).git diff --check— pass.skills-ref validate— pass for every complete skill other thancarve-changesets.review-code-change— clean ate88bf87e9cb1a4e04bdf8b051ce8ca0f0dcb96e6versusac5408716958ba5417aaa537305d6a93573f2edb; one non-gating defer preserves Derive carve-changesets chain state from live git instead of a state.json cache #32's live-invariant work.The epic grants a pre-packaging exception for the exact repository-wide
just lintfailureMissing required file: SKILL.mdunderskills/carve-changesets. Issue #35 owns that future file. Python lint, Markdown lint, all complete-skill validations, focused tests, and the full repository suite pass; no other local or remote gate is waived.Tickets
Fixes #31