Update AGENTS.md with improved commit message handling guidelines

- Specify that COMMIT_EDITMSG should be created or updated.
- Encourage editing the existing file to maintain context across multiple steps.

Signed-off: junie@lucy.xalior.com

AGENTS.md

@@ -147,9 +147,9 @@ Comment what the code does, not what the agent has done. The documentation's pur
 - git branching:
   - Do not create new branches
 - git commits:
-  - Create COMMIT_EDITMSG file, await any user edits, then commit using that 
-    commit note, and then delete the COMMIT_EDITMSG file. Remember to keep
-    the first line as the subject <50char
+  - Create or update COMMIT_EDITMSG file, await any user edits, then commit
+    using that commit note, and then delete the COMMIT_EDITMSG file. 
+    Remember to keep the first line as the subject <50char
 - git commit messages:
   - Use imperative mood (e.g., "Add feature X", "Fix bug Y").
   - Include relevant issue numbers if applicable.
@@ -165,8 +165,9 @@ Comment what the code does, not what the agent has done. The documentation's pur
 - deploy workflow:
   - `bin/deploy.sh` refuses to run with uncommitted or untracked files at the repo root.
 - testing:
-  - Do not restart the dev-server, use the already running one.
-  - use tsc -noEmit to check for type errors, build breaks the dev-server.
+  - **DO NOT** not restart the dev-server, use the already running one.
+  - Use tsc -noEmit to check for type errors
+  - **DO NOT** 'build' the application, Next.js build breaks the dev-server.
   
 ### References