Rename task_* tables to quest_* with legacy-dev migration path (D-007)

Per design/IMPLEMENTATION-ORDER.md 1.1 and decision D-007: the domain
model takes the quest vocabulary pre-release. SCHEMA_V1 now creates
quest_definitions/quest_instances directly; DAO classes, records and
error messages follow (QuestDefinitionsDao, QuestInstancesDao). The
migration runner gains migration 2, an async-callable step that detects
surviving task_* tables on dev machines and ALTER TABLE RENAMES them
inside the migration transaction, with FK clauses rewritten by SQLite.
Migration 1's content rewrite is legal because nothing was ever
shipped; dev databases stamped version 1 ride migration 2 up to 2.

custom_components/nestquest/schema.py

@@ -86,7 +86,7 @@ date range; a single-day override stores the same date in both columns.
 ``is_present`` 0/1 marks the child absent/present for the whole range;
 ``note`` is optional free text.
 
-Task instances: ``task_instances`` deliberately carries NO completion
+Quest instances: ``quest_instances`` deliberately carries NO completion
 status column.  An instance's current state derives from the latest row
 in ``completion_events`` (Feature 08), so materialization (Feature 07)
 can insert instances without knowing anything about completion and the
@@ -103,7 +103,7 @@ stamps one coherent time).
 Uniqueness: the (definition_id, due_date) pair is declared as a
 table-level ``UNIQUE`` constraint rather than a separate ``CREATE
 UNIQUE INDEX`` statement.  SQLite materializes it as an implicit unique
-index (``sqlite_autoindex_task_instances_1``) — the required "unique
+index (``sqlite_autoindex_quest_instances_1``) — the required "unique
 index prevents duplicate instances" — and the constraint form cannot be
 silently dropped the way a standalone index can, so the duplicate door
 stays shut.  Idempotent materialization keys on exactly this pair.  No
@@ -128,7 +128,7 @@ representable — missed is a derived state announced on the HA event bus
 (Feature 10), never an appended event.
 
 ``child_id`` is deliberately denormalized (it is also derivable via
-``task_instances``): history reporting (Feature 13) filters and rates
+``quest_instances``): history reporting (Feature 13) filters and rates
 per child directly against the log, and the log should stay
 self-describing without joins.
 
@@ -219,9 +219,9 @@ SCHEMA_V1_SCHEDULE_RULES_DDL: list[str] = [
     """,
 ]
 
-SCHEMA_V1_TASK_DEFINITIONS_DDL: list[str] = [
+SCHEMA_V1_QUEST_DEFINITIONS_DDL: list[str] = [
     """
-    CREATE TABLE IF NOT EXISTS task_definitions (
+    CREATE TABLE IF NOT EXISTS quest_definitions (
         id INTEGER PRIMARY KEY AUTOINCREMENT,
         title TEXT NOT NULL,
         description TEXT,
@@ -271,11 +271,11 @@ SCHEMA_V1_PRESENCE_OVERRIDES_DDL: list[str] = [
     """,
 ]
 
-SCHEMA_V1_TASK_INSTANCES_DDL: list[str] = [
+SCHEMA_V1_QUEST_INSTANCES_DDL: list[str] = [
     """
-    CREATE TABLE IF NOT EXISTS task_instances (
+    CREATE TABLE IF NOT EXISTS quest_instances (
         id INTEGER PRIMARY KEY AUTOINCREMENT,
-        definition_id INTEGER NOT NULL REFERENCES task_definitions(id),
+        definition_id INTEGER NOT NULL REFERENCES quest_definitions(id),
         child_id INTEGER NOT NULL REFERENCES children(id),
         due_date TEXT NOT NULL,
         due_time TEXT,
@@ -289,7 +289,7 @@ SCHEMA_V1_COMPLETION_EVENTS_DDL: list[str] = [
     """
     CREATE TABLE IF NOT EXISTS completion_events (
         id INTEGER PRIMARY KEY AUTOINCREMENT,
-        instance_id INTEGER NOT NULL REFERENCES task_instances(id),
+        instance_id INTEGER NOT NULL REFERENCES quest_instances(id),
         child_id INTEGER NOT NULL REFERENCES children(id),
         event_type TEXT NOT NULL CHECK (event_type IN ('completed', 'uncompleted')),
         actor_source TEXT NOT NULL CHECK (actor_source IN ('user', 'panel')),
@@ -315,10 +315,10 @@ SCHEMA_V1_STATEMENTS: list[str] = [
     *SCHEMA_V1_CHILDREN_DDL,
     *SCHEMA_V1_ADMIN_USERS_DDL,
     *SCHEMA_V1_SCHEDULE_RULES_DDL,
-    *SCHEMA_V1_TASK_DEFINITIONS_DDL,
+    *SCHEMA_V1_QUEST_DEFINITIONS_DDL,
     *SCHEMA_V1_PRESENCE_SCHEDULES_DDL,
     *SCHEMA_V1_PRESENCE_OVERRIDES_DDL,
-    *SCHEMA_V1_TASK_INSTANCES_DDL,
+    *SCHEMA_V1_QUEST_INSTANCES_DDL,
     *SCHEMA_V1_COMPLETION_EVENTS_DDL,
 ]