fix(importer): keep quest definitions available across shards

CONTEXT.md

@@ -71,7 +71,9 @@ The shard that hosts instanced maps.
 A stable name for the import plan assigned to one World Shard or Instance Pool destination. The
 canonical profiles are `alliance-eastern`, `alliance-kalimdor`, `alliance-single`,
 `starting-eastern`, `starting-kalimdor`, and `instances`. The starting profiles retain the Alliance
-scope and add the Horde starting areas on the same continent.
+scope and add the Horde starting areas on the same continent. Canonical profiles share quest
+definitions and scripted event requirements from both starting profiles and the Instance Pool.
+Quest-giver relations stay within each destination's World Import Scope.
 
 **World Import Scope**:
 The authoritative union of Bounded Map Slices, Instance Vmap Slices, whole maps, and forced

docs/data-ingestion.md

@@ -210,6 +210,13 @@ fence plus the surrounding pre- and post-flight guards keep any one database fro
 continents' spatial rows. Non-spatial content (spells, items, quests, the DBC reference tables) is
 duplicated on every shard by design.
 
+Canonical World Import Profiles build quest definitions from the union of the starting profiles
+and the Instance Pool. This keeps quest text, objectives, and scripted event requirements
+available after Transfer. Quest reimports retain summoned givers and reapply the `creature-ai`
+Package Deltas for event requirements. Quest-giver relations still follow the destination's World Import Scope. Legacy map and box imports retain
+their selected quest scope. Existing canonical imports need the `quests` and `items` families
+reimported on every World Shard and Instance Pool so the shared quest rewards have item templates.
+
 ## Creature EventAI family
 
 `--family creature-ai` compiles source rows into Module-owned native definitions. The selected