sixfold-space/madtea
sixfold-space/madtea
SHA256
2
0
Fork 0
Code Issues 221 Pull requests Projects Releases 13 Packages Wiki Activity Actions 9

docs(adr): migrate the decision records to MADR 4.0.0 under docs/decisions #486

Merged
hexajon merged 1 commit from issue-483-migrate-adr-tree-to-madr into main 2026-09-14 18:17:38 +00:00
Conversation 0 Commits 1 Files changed 98 +6303 -5051
hexajon commented 2026-09-14 18:17:36 +00:00
Owner
Copy link

Summary

Migrates this repo's own decision records from the legacy docs/adr/ tree to docs/decisions/ in MADR 4.0.0 format, so the repo uses MADR only. This matches the tooling adopted in PR #484.

  • All 33 records are reshaped into the full MADR 4.0.0 structure: YAML frontmatter, then Context and Problem Statement, Decision Drivers, Considered Options, Decision Outcome (with Consequences and Confirmation), Pros and Cons of the Options, and More Information. The decisions themselves are unchanged; this is a format migration.
  • Adds record 0034 for this decision.
  • docs/decisions/README.md holds the index. docs/adr/ is removed.
  • Repo-wide record links now point at docs/decisions/.
  • adr check runs clean online: each decided record's linked issues cite the record, and the still-open implementation issues are referenced as plain text rather than tracking links.

Closes #483.

Closes #483

## Summary Migrates this repo's own decision records from the legacy `docs/adr/` tree to `docs/decisions/` in MADR 4.0.0 format, so the repo uses MADR only. This matches the tooling adopted in PR #484. - All 33 records are reshaped into the full MADR 4.0.0 structure: YAML frontmatter, then Context and Problem Statement, Decision Drivers, Considered Options, Decision Outcome (with Consequences and Confirmation), Pros and Cons of the Options, and More Information. The decisions themselves are unchanged; this is a format migration. - Adds record 0034 for this decision. - `docs/decisions/README.md` holds the index. `docs/adr/` is removed. - Repo-wide record links now point at `docs/decisions/`. - `adr check` runs clean online: each decided record's linked issues cite the record, and the still-open implementation issues are referenced as plain text rather than tracking links. Closes #483. Closes #483
docs(adr): migrate the decision records to MADR 4.0.0 under docs/decisions
Some checks failed
drift / govulncheck (pull_request) Has been skipped
Details
drift / surface-diff (pull_request) Successful in 1m9s
Details
drift / forgejo-smoke (pull_request) Has been skipped
Details
ci / mcp-conformance (pull_request) Successful in 2m11s
Details
ci / mcp-conformance (push) Successful in 9s
Details
drift / govulncheck (push) Has been skipped
Details
drift / surface-diff (push) Successful in 6s
Details
drift / forgejo-smoke (push) Has been skipped
Details
ci / gate (push) Failing after 3m45s
Details
ci / gate (pull_request) Failing after 8m13s
Details
bba01b38b5
 
Closes #483
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
breaking
Breaking change - flag for release notes

  
bug
Something is not working

  
documentation
Documentation only

  
enhancement
New feature

  
epic
Tracking epic with dependency children

  
good first issue
Interested in contributing? Get started here.

  
help wanted
Maintainer would welcome outside help

  
refactoring
Code restructuring without behavior changes

  
resolution/duplicate
Closed as duplicate of another issue

  
resolution/invalid
Closed as invalid or not reproducible

  
resolution/wontfix
Closed as won't fix

  
security
Security issue or hardening

  
severity/critical
Security severity: critical

  
severity/high
Security severity: high

  
severity/low
Security severity: low

  
severity/medium
Security severity: medium

  
status/abandoned
Someone started, then walked away - up for grabs

  
status/blocked
Blocked by another issue or an external dependency

  
status/needs-decision
Waiting on a maintainer decision; workable once decided

  
status/needs-info
Waiting on reporter / more information before work can start

  
status/needs-verification
Done except verification in a live interactive session

  
testing
Test suite / CI infrastructure work

  
upstream
Related to an upstream repository, already reported there

No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sixfold-space/madtea!486
No description provided.