fix(lite-plan): correct executionContext.planObject.tasks type documentation

Issue found by Gemini analysis:
- executionContext.planObject.tasks was incorrectly documented as string[]
- Actual runtime structure is array of structured task objects (7 fields)
- This caused documentation mismatch between lite-plan and lite-execute

Fix:
- Update executionContext definition to show full task object structure
- Add comment clarifying it's an array of structured objects (7 fields each)
- Aligns with actual implementation and lite-execute consumption logic

Impact: Documentation only (no code changes, runtime behavior was already correct)

.claude/commands/workflow/lite-plan.md

@@ -100,10 +100,24 @@ Context passed to lite-execute via --in-memory (Phase 5):
 
 ```javascript
 {
-  planObject: {                        // See planObject structure above
+  planObject: {                        // Complete planObject structure (see above)
     summary: string,
     approach: string,
-    tasks: string[],
+    tasks: [                           // Array of structured task objects (7 fields each)
+      {
+        title: string,
+        file: string,
+        action: string,
+        description: string,
+        implementation: string[],
+        reference: {
+          pattern: string,
+          files: string[],
+          examples: string
+        },
+        acceptance: string[]
+      }
+    ],
     estimated_time: string,
     recommended_execution: string,
     complexity: string