Document expanded runtime smoke coverage

docs/migration.md

@@ -83,6 +83,22 @@ client runtime on the Linux VPS:
 - `effect`
 - `icon`
 - `property`
+- `terrain`
+- `tree`
+- `zone`
+- `outdoora1`
+- `outdoora2`
+- `outdoorb1`
+- `outdoorc1`
+- `outdoorsnow1`
+- `pc`
+- `pc2`
+- `guild`
+- `npc`
+- `monster2`
+- `sound`
+- `sound_m`
+- `sound2`
 
 Validation method:
 
@@ -100,11 +116,15 @@ Observed result:
 - `app.Create(...)` succeeded
 - client reached `MainStream.SetLoginPhase()`
 
+For the world, audio, and gameplay-adjacent packs in this list, the current
+validation level is startup regression smoke only. Full confidence for those
+packs still requires map-load or in-game coverage.
+
 Recommended next pack groups:
 
 1. remaining startup-adjacent patch packs
-2. world and map content such as outdoor, terrain, tree, and zone
-3. late-load gameplay content such as pc, npc, monster, and sound
+2. remaining late-load gameplay content not covered yet
+3. scenario-based validation for world, actor, and sound packs
 
 ## Risk notes
 

docs/testing.md

@@ -89,6 +89,26 @@ Confirmed `.m2p` smoke tests:
   - `icon.m2p`
   - `property.m2p`
   with all twenty matching legacy `.pck` files removed
+- the same twenty-pack set plus:
+  - `terrain.m2p`
+  - `tree.m2p`
+  - `zone.m2p`
+  - `outdoora1.m2p`
+  - `outdoora2.m2p`
+  - `outdoorb1.m2p`
+  - `outdoorc1.m2p`
+  - `outdoorsnow1.m2p`
+  with all twenty-eight matching legacy `.pck` files removed
+- the same twenty-eight-pack set plus:
+  - `pc.m2p`
+  - `pc2.m2p`
+  - `guild.m2p`
+  - `npc.m2p`
+  - `monster2.m2p`
+  - `sound.m2p`
+  - `sound_m.m2p`
+  - `sound2.m2p`
+  with all thirty-six matching legacy `.pck` files removed
 
 In every confirmed case the client reached the login bootstrap path under Wine
 and completed:
@@ -108,6 +128,12 @@ additional packs such as world, NPC, monster, and late-load gameplay content.
 Those should be validated with map loads or in-game scenario coverage rather
 than startup-only checks.
 
+The world, audio, and gameplay-adjacent packs listed above are therefore
+validated only as
+startup-time regression smoke coverage. They do prove that the additional
+`.m2p` archives do not break bootstrap or early asset resolution, but they do
+not yet prove full map streaming, actor loading, or gameplay correctness.
+
 Current non-fatal runtime issues on the VPS:
 
 - missing `Tahoma` font mapping in the client runtime