<!--
  UASK Engineering Hub template · definition-of-done 0.2.0 · item process.definition-of-done · playbook quality.quality-release (R1) · CC BY 4.0
  This is the copy form of the checklist `process.definition-of-done`, which is the one home of these lines; the number at the end of each
  line is its rule there (tests/check_repo.py checks that every rule appears). Copy to the project as DEFINITION-OF-DONE.md (or a section
  of CONTRIBUTING.md) and cut it down: keep only checks the project really performs, add lines of your own, remove none that applies at
  your tier. Change it only through a reviewed pull request. Delete these comments in the copy.
-->

# Definition of Done — [project]

Version: 0.2.0 · Owner: [name] · Last changed: [YYYY-MM-DD]

A work package is done when every line below that applies to it is true. A line that does not apply is marked "n/a" in the pull request
with a reason. "Done" means verified: a commit hash and the output of the checks, otherwise the package is reported as "not verified".

## Every package

- [ ] The Done criterion of the brief is met and the evidence is in the pull request (test, command output, screenshot). (R1)
- [ ] The gate script is green locally and in CI, and it is the same script: `<gate command, for example bash tests/run.sh>`. (R2)
- [ ] The checks were seen to fail before the change and to pass after it; a fixed defect has a regression test. (R3)
- [ ] Verified by someone who did not build it (a person or a second session), who re-ran the checks; at the lightweight tier the builder checked it
      against this list and said so. (R4)
- [ ] The files changed are those the brief allows; any other is explained. (R5)
- [ ] The pull request title and commits follow Conventional Commits; breaking changes are marked. (R6)
- [ ] Documentation is updated: user docs, README, and an ADR if an architectural decision was made; `CHANGELOG.md` has a line under `Unreleased`
      if users will notice. (R7)
- [ ] No secrets, no debug leftovers, no new warnings; new dependencies have a compatible licence, are maintained and have no known exploited vulnerability. (R8)
- [ ] Anything that is the owner's to decide is listed under "Owner decisions needed", not merged as decided. (R9)
- [ ] The package's line is in the project log: id, branch, commit, verdict, time against the estimate. (R10)

## A change to stored data or a live system

- [ ] A backup proved by restore exists and is recorded with the change; the rollback was tried or its steps are listed. (R11)

## This project only

<!-- Add the checks specific to the product, for example:
     - accessibility check of changed pages;
     - a database migration has a tested down step or a documented restore;
     - translations updated for every changed string;
     - tested on the oldest and newest supported host version. -->

- [ ] [project-specific check] (R12)
