Upstream — this project and its template
How this works
This project started from a template, and the template keeps changing. It publishes each change as a numbered entry in its
CHANGELOG.md, read wheretemplate:points. This file is this project's side of that. The steps areCONTRIBUTING.md→ The upgrade kind.
template-entry:in the frontmatter is the marker: the last changelog entry this project reviewed. Entries above it are waiting, and taking them is an upgrade. A fresh copy ships with it set to the template's latest entry.Adapted or declined records every entry this project took in changed, or did not take, and why, so a decline is never argued twice. An entry adopted as written needs no line. Each line reads
- **Entry 3 · declined.** Why.Outbox holds what this project found that the template should fix, one line each (what was found, where, who found it and when, what is owed, the shape a
## Raisedentry takes) plus an ID never reused:- **U1 · What was found.** Where · who found it, YYYY-MM-DD · what the template owes.Whoever maintains the template reads it here; where they cannot, paste the entry into an issue on the template's repository. Only this project writes here, and it clears an entry when it judges a changelog entry has fixed it, or when the template declines it.
Adapted or declined
(none yet)
Outbox
(empty)