docs(code): add progress tracking instructions to plan.devin

Add detailed instructions for documenting reasoning processes in `<THOUGHT>` tags, including progress tracking symbols (`✓`, `!`, `*`) for tasks and sub-tasks. Also, update Kotlin files to improve file handling and UI feedback.

Author: phodal

core/src/main/kotlin/cc/unitmesh/devti/sketch/ui/code/CodeHighlightSketch.kt

@@ -342,9 +342,9 @@ private fun CodeHighlightSketch.processWriteCommand(currentText: String) {
             val file = ScratchRootType.getInstance()
                 .createScratchFile(project, newFileName, language, currentText)
 
-            if (file == null) {
-                return@addActionListener
-            }
+            this.text = "Written to $newFileName"
+
+            if (file == null) return@addActionListener
 
             val psiFile = PsiManager.getInstance(project).findFile(file)!!
 

core/src/main/resources/genius/en/code/plan.devin

@@ -58,6 +58,10 @@ Here is the rule you should follow:
 If `<user.question>` directly contradicts any of these steps, follow the instructions from `<user.question>`
 first. Be thorough in your thinking process, so it's okay if it is lengthy.
 
+For each step, document your reasoning process inside `<THOUGHT>` tags. Include the following information, enclosed within XML tags:
+
+1. `<PLAN>`: An updated plan incorporating the outcomes from the previous step. Mark progress by adding `✓` after each task in the plan that was fully completed before this step during the **current session**. Use the symbol `!` for tasks that have a latest status as failed, and use `*` for tasks that are currently in progress. If there are sub-tasks, mark their progress statuses as well. Ensure all progress statuses are marked accurately and appropriately reflect the hierarchical relationships of statuses between tasks and sub-tasks. For example, if all sub-tasks are completed, the parent task should also be marked as completed.
+
 For example:
 
 <THOUGHT>

core/src/main/resources/genius/zh/code/plan.devin

@@ -58,11 +58,16 @@ Here is the rule you should follow:
 If `<user.question>` directly contradicts any of these steps, follow the instructions from `<user.question>`
 first. Be thorough in your thinking process, so it's okay if it is lengthy.
 
+For each step, document your reasoning process inside `<THOUGHT>` tags. Include the following information, enclosed within XML tags:
+
+1. `<PLAN>`: An updated plan incorporating the outcomes from the previous step. Mark progress by adding `✓` after each task in the plan that was fully completed before this step during the **current session**. Use the symbol `!` for tasks that have a latest status as failed, and use `*` for tasks that are currently in progress. If there are sub-tasks, mark their progress statuses as well. Ensure all progress statuses are marked accurately and appropriately reflect the hierarchical relationships of statuses between tasks and sub-tasks. For example, if all sub-tasks are completed, the parent task should also be marked as completed.
+
+
 For example:
 
 <THOUGHT>
 <PLAN>
-Some plan
+1.
 </PLAN>
 </THOUGHT>
 

exts/devins-lang/src/main/kotlin/cc/unitmesh/devti/language/compiler/exec/WriteInsCommand.kt

@@ -37,7 +37,7 @@ class WriteInsCommand(val myProject: Project, val argument: String, val content:
             return writeToFile(filepath, projectDir)
         }
 
-        val psiFile = PsiManager.getInstance(myProject).findFile(virtualFile)
+        val psiFile = runReadAction { PsiManager.getInstance(myProject).findFile(virtualFile) }
             ?: return "$DEVINS_ERROR: File not found: $argument"
 
         var output: String? = null