Skip to content

test(fixture): adr-migrate summary names kind, verb, capability, basis #612

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aaronsb merged 1 commit into from
Sep 28, 2026
Merged

test(fixture): adr-migrate summary names kind, verb, capability, basis #612

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion tests/fixtures/docker/scenarios/adr-migrate/prompt.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
This repository's decision records now follow the adr/v1 contract declared in docs/architecture/adr.yaml (the ADR way and `docs/scripts/adr` describe it). Migrate two records to v1: ADR-179 (removing the pre-1.0 migrator) and ADR-186 (the live integration fixture). Keep their decisions and history intact, choose kind, verb and capability honestly, and ground each basis in what the record itself says. Do not invent operator statements. Convert them with `docs/scripts/adr import scan` on the two files, resolve each import sheet's open items, then `docs/scripts/adr import apply`. Run `docs/scripts/adr lint` on the two files until it reports 0 errors; the warning that an imported record has no `## Summary` yet is expected (ADR-306 §4). Then summarize what you chose and why.
This repository's decision records now follow the adr/v1 contract declared in docs/architecture/adr.yaml (the ADR way and `docs/scripts/adr` describe it). Migrate two records to v1: ADR-179 (removing the pre-1.0 migrator) and ADR-186 (the live integration fixture). Keep their decisions and history intact, choose kind, verb and capability honestly, and ground each basis in what the record itself says. Do not invent operator statements. Convert them with `docs/scripts/adr import scan` on the two files, resolve each import sheet's open items, then `docs/scripts/adr import apply`. Run `docs/scripts/adr lint` on the two files until it reports 0 errors; the warning that an imported record has no `## Summary` yet is expected (ADR-306 §4). Then summarize, for each record, the kind, verb, capability and basis you chose and why.
Loading