Add generationStatus and match3d/runtime fixes

Introduce persistent generationStatus to work summaries (puzzle & match3d) and propagate generation recovery rules across docs and frontend/backends so "generating" is restored from server-side work summary rather than ephemeral front-end notices. Update API server image/asset handling (improve match3d material sheet green/alpha decontamination and promote generatedItemAssets background fields) and add runtime improvements: alpha-based hotspot hit-testing, tray insertion/three-match animation behavior, and session re-read on client-side VectorEngine timeouts/lock-screen interruptions. Many docs, tests and related frontend modules updated/added to reflect these contract and behavior changes.

src/services/miniGameDraftGenerationProgress.test.ts

@@ -99,6 +99,22 @@ describe('miniGameDraftGenerationProgress', () => {
     );
   });
 
+  test('finished draft generation keeps elapsed time pinned to completion time', () => {
+    const state: MiniGameDraftGenerationState = {
+      kind: 'puzzle',
+      phase: 'failed',
+      startedAtMs: 1_000,
+      finishedAtMs: 151_000,
+      completedAssetCount: 0,
+      totalAssetCount: 0,
+      error: 'VectorEngine 图片编辑请求超时',
+    };
+
+    const progress = buildMiniGameDraftGenerationProgress(state, 500_000);
+
+    expect(progress?.elapsedMs).toBe(150_000);
+  });
+
   test('big fish draft generation exposes multiple draft steps', () => {
     const state: MiniGameDraftGenerationState = {
       kind: 'big-fish',