Update app.py

app.py

@@ -562,7 +562,7 @@ If you find any "Code-Blocks" then,
    
 3. **Pseudo‑code formatting**:
    - Represent each block or nested block on its own line.
-   - Indent nested blocks by 4 spaces under their parent (`forever`, `if`, etc.).
+   - **Indent nested blocks by 4 spaces under their parent (`forever`, `if`, etc.).This is a critical requirement.**
    - No comments or explanatory text—just the block sequence.
    - a natural language breakdown of each step taken after the event, formatted as a multi-line string representing pseudo-code. Ensure clarity and granularity—each described action should map closely to a Scratch block or tight sequence. 
 
@@ -573,71 +573,57 @@ If you find any "Code-Blocks" then,
 
 5. **Examples for reference**:  
 **Correct** pattern for a simple start script:
-   ```
-   when green flag clicked
-   switch backdrop to [blue sky v]
-   set [score v] to (0)
-   show variable [score v]
-   broadcast [Game Start v]
-   end
-   ```
+    ```
+    when green flag clicked
+        switch backdrop to [blue sky v]
+        set [score v] to (0)
+        show variable [score v]
+        broadcast [Game Start v]
+    end
+    ```
 **Correct** pattern for updating the high score variable handling:
-   ```
-   when I receive [Game Over v]
-   if <((score)) > (([High Score v]))> then
-   set [High Score v] to ([score v])
-   end
-   switch backdrop to [Game Over v]
-   end
-   ```
+    ```
+    when I receive [Game Over v]
+        if <((score)) > (([High Score v]))> then
+            set [High Score v] to ([score v])
+        end
+        switch backdrop to [Game Over v]
+    end
+    ```
 **Correct** pattern for level up and increase difficulty use:
-   ```
-   when I receive [Level Up v]
-   change [level v] by (1)
-   set [ballSpeed v] to ((([ballSpeed v]) * (1.1)))
-   end
-   ```
+    ```
+    when I receive [Level Up v]
+        change [level v] by (1)
+        set [ballSpeed v] to ((([ballSpeed v]) * (1.1)))
+    end
+    ```
 **Correct** pattern for jumping mechanics use:
-   ```
-   when [space v] key pressed
-   if <((y position)) = (-100)> then
-   repeat (5)
-   change y by (100)
-   wait (0.1) seconds
-   change y by (-100)
-   wait (0.1) seconds
-   end
-   end
-   end
-   ```
-**Correct** pattern for continuos moving objects use:
-   ```
-   when green flag clicked
-   go to x: (240) y: (-100)
-   set [speed v] to (-5)
-   show variable [speed v]
-   forever
-   change x by ([speed v])
-   if <((x position)) < (-240)> then
-   go to x: (240) y: (-100) 
-   end
-   end
-   end
-   ```
+    ```
+    when [space v] key pressed
+        if <((y position)) = (-100)> then
+            repeat (5)
+                change y by (100)
+                wait (0.1) seconds
+                change y by (-100)
+                wait (0.1) seconds
+            end
+        end
+    end
+    ```
 **Correct** pattern for continuos moving objects use:
-   ```
-   when green flag clicked
-   go to x: (240) y: (-100)
-   set [speed v] to (-5)
-   show variable [speed v]
-   forever
-   change x by ([speed v])
-   if <((x position)) < (-240)> then
-   go to x: (240) y: (-100) 
-   end
-   end
-   end
-   ```
+    ```
+    when green flag clicked
+        go to x: (240) y: (-100)
+        set [speed v] to (-5)
+        show variable [speed v]
+        forever
+            change x by ([speed v])
+            if <((x position)) < (-240)> then
+                go to x: (240) y: (-100) 
+            end
+        end
+    end
+    ```
 6. **Donot** add any explaination of logic or comments to justify or explain just put the logic content in the json.
 7. **Output**:  
     Return **only** a JSON object, using double quotes everywhere: