Use when preparing any kuik release, alphas included, before dispatching the Release workflow, or when asked to write or update the release notes of the next version, for example "write the notes of the next beta" or "prepare the release of 3.0.0".
Use when opening a pull request on kuik, rewriting its description, or answering its automated review; prepares the branch, drafts a short readable description for the user to confirm, and keeps it in step with the branch.
Use before writing, adding or reworking Ginkgo specs in kuik; drafts the It/Entry strings as pending specs, has spec-reviewer check them and shows them with task test-outline before any body is written.
Use when asked to prepare, write or update the acceptance scenarios (or acceptance tests) of a kuik v3 release before its acceptance run, for example "prepare the acceptance scenarios of kuik 3.0.0-alpha.4" or "write the acceptance tests for the next alpha".
Use when adding, changing or fixing e2e specs under test/e2e/ in kuik (the Kind suite run by task test-e2e), or when deciding what a PR should check end to end.
Use when asked to run the acceptance tests of a kuik v3 release (also called a smoke test) on a pre-production or other cluster where kuik is already installed, for example "validate kuik 3.0.0-alpha.3 on preprod", "smoke test the release on our cluster" or…
Write a decision note under notes/ (filter, numbered file, index line)