From 773bee619127c0211f7dab61af85469ef84f18d7 Mon Sep 17 00:00:00 2001
From: orchestrator <orchestrator@cubecraftlabs.com>
Date: Sat, 26 Sep 2026 16:51:03 +0000
Subject: [PATCH] release: advance version to 0.9.2 and add the 0.9.2 release
 notes

---
 RELEASE_NOTES.md                          | 33 +++++++++++++++++++++++
 custom_components/nestquest/manifest.json |  2 +-
 pyproject.toml                            |  2 +-
 uv.lock                                   |  2 +-
 4 files changed, 36 insertions(+), 3 deletions(-)

diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index 40c0b79..e2fbf34 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -1,5 +1,38 @@
 # NestQuest Release Notes
 
+## Version 0.9.2 — 2026-09-26
+
+### Scope
+
+Patch release carrying the admin "Delete task" capability onto `main`.
+
+- **Delete a task in the admin PWA:** the definition edit sheet gains an
+  admin-only Delete action with hybrid semantics (D-017, owner decision "delete
+  if there's no history, retire/deactivate if there is"). If the definition has
+  **no completion history**, it is hard-deleted together with its instances,
+  assignees, windows and its schedule rule (when unreferenced), all in one
+  transaction under the connection lock. If it has **any completion history** (a
+  completion or an un-completion), nothing is deleted: it is retired by
+  deactivation instead, preserving the definition, rule, assignees, windows and
+  all history, with future uncompleted instances cleared as with any
+  deactivation. (PR #262.)
+- **API:** `DELETE /api/v1/admin/quest-definitions/{id}` lives on the admin plane
+  (`require_admin`; a non-admin is refused and an unknown id is 404). The response
+  reports `deleted`/`retired` and carries the retired definition (`null` when
+  deleted). The kids' panel gains no control, and `QuestDefinitionsDao` now has
+  exactly one, history-guarded, delete method.
+
+### Upgrade note
+
+The database schema is unchanged at version **9**; no migration or backup step is
+needed beyond the 0.8.0 note. No runtime dependency is added.
+
+### Requirements
+
+Home Assistant 2024.6.0 or newer. Install through HACS from the
+`Maniacs-Mansion/NestQuest` GitHub mirror (kept current by the Gitea push
+mirror).
+
 ## Version 0.9.1 — 2026-09-26
 
 ### Scope
diff --git a/custom_components/nestquest/manifest.json b/custom_components/nestquest/manifest.json
index e5d2485..7f61e54 100644
--- a/custom_components/nestquest/manifest.json
+++ b/custom_components/nestquest/manifest.json
@@ -15,5 +15,5 @@
   "iot_class": "local_polling",
   "issue_tracker": "https://github.com/Maniacs-Mansion/NestQuest/issues",
   "requirements": [],
-  "version": "0.9.1"
+  "version": "0.9.2"
 }
diff --git a/pyproject.toml b/pyproject.toml
index 7699773..a5e8476 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -1,6 +1,6 @@
 [project]
 name = "nestquest"
-version = "0.9.1"
+version = "0.9.2"
 description = "NestQuest Home Assistant Integration"
 readme = "README.md"
 requires-python = ">=3.11"
diff --git a/uv.lock b/uv.lock
index 5d63707..2c3f8ec 100644
--- a/uv.lock
+++ b/uv.lock
@@ -373,7 +373,7 @@ wheels = [
 
 [[package]]
 name = "nestquest"
-version = "0.9.1"
+version = "0.9.2"
 source = { virtual = "." }
 
 [package.dev-dependencies]