Update extension version and refine default instructions for commit messages and edit formats

Author: robertpiosik

packages/vscode/package.json

@@ -2,7 +2,7 @@
   "name": "gemini-coder",
   "displayName": "Code Web Chat",
   "description": "Superfast AI coding (CWC)",
-  "version": "1.626.0",
+  "version": "1.627.0",
   "scripts": {
     "build": "npx vsce package --no-dependencies",
     "vscode:prepublish": "rimraf out && npm run compile",
@@ -536,7 +536,7 @@
           "type": "string",
           "scope": "resource",
           "description": "Style and conventions (e.g. Conventional Commits, gitmoji) for generated commit messages.",
-          "default": "Write a brief and precise summary for the changes, limited to a single sentence if possible and nothing else. Use an imperative tone to ensure clarity and focus on the primary change or purpose."
+          "default": "Write a brief and precise summary for the changes, limited to a single sentence, if possible and nothing else. Use an imperative tone to ensure clarity and focus on the primary change or purpose."
         },
         "codeWebChat.commitMessageAutoAcceptAfter": {
           "type": "number",
@@ -578,8 +578,8 @@
           "scope": "resource",
           "description": "Style of generated code blocks in \"Edit context\" mode.",
           "default": {
-            "whole": "Whenever showing a new or updated file, provide brief explanation, then print path in a markdown heading (e.g. ### File: `src/index.ts`), followed by a markdown code block with full contents—as I have a disability which means I can't type and need to be able to just copy and paste.",
-            "truncated": "Whenever showing a new or updated file, provide brief explanation, then print path in a markdown heading (e.g. ### File: `src/index.ts`), followed by a markdown code block with truncated contents—as a space saving measure (unchanged parts should be hidden behind ellipsis comments, e.g. \"// ...\").",
+            "whole": "Whenever showing a new or updated file, provide brief explanation, then print path in a markdown heading (e.g. ### New file `src/index.ts`, ### Updated file: `src/index.ts`), followed by a markdown code block with full contents—as I have a disability which means I can't type and need to be able to just copy and paste.",
+            "truncated": "Whenever showing a new or updated file, provide brief explanation, then print path in a markdown heading (e.g. ### New file: `src/index.ts`, ### Updated file: `src/index.ts`), followed by a markdown code block with truncated contents—as a space saving measure unchanged parts should be hidden behind ellipsis comments, e.g. \"// ...\".",
             "diff": "Whenever showing a new or updated file, provide brief explanation and print the Unified Diff within a markdown code block. Example: \nThe count variable has been incremented.\n```diff\n--- a/file.py\n+++ b/file.py\n@@ -2,1 +2,1 @@\n-count = 10\n+count = 20\n```"
           },
           "properties": {