updating plan and prompt files

documentation/PROMPT.md

@@ -18,15 +18,13 @@ You are responsible for implementing the remaining "Emacs DNA" features and solv
 
 OPERATIONAL RULES (STRICT)
 
-1. The "State File" Protocol (CRITICAL)
+1. The "Project Plan" Protocol (CRITICAL)
 
-You must maintain a file in the repo documentation folder named DEV_STATE.md.
+You must maintain the documentation/PLAN.md file as the single source of truth for the project's state.
 
-Read-First: Before every task, read this file to understand the architecture and current focus.
+Read-First: Before every task, read documentation/PLAN.md to understand the architecture, current focus, and detailed plan.
 
-Write-Always: After every code change, update this file to reflect progress.
-
-Structure: Keep sections for Architecture, Current Module, File Manifest, and Todo/Done lists.
+Write-Always: After every significant code change or completion of a subtask, update documentation/PLAN.md to reflect progress, new findings, or changes to the plan. Ensure the "Current Focus" and "Current State Summary (Completed Features)" sections are always accurate and detailed.
 
 2. Git Discipline
 
@@ -44,15 +42,16 @@ Lua Bindings: When adding C++ features (like KillRing), immediately expose them
 
 Memory Safety: Use std::shared_ptr and std::weak_ptr for the Buffer/Window hierarchy. Watch out for GTK/sigc++ lifetime issues (e.g., the recent double-free on exit).
 
+Good Practices: Adhere to established coding standards, naming conventions, and architectural patterns observed in the existing codebase. Prioritize clean, maintainable, and testable code.
+
 INTERACTION LOOP
 
 Analyze: specific files needed.
 
-Plan: implementation strategy.
+Plan: implementation strategy, incorporating details from documentation/PLAN.md.
 
 Execute: Generate code.
 
-Update State: Generate new DEV_STATE.md content.
-
-Commit: Generate shell commands.
+Update Plan: Generate new documentation/PLAN.md content to reflect progress.
 
+Commit: Generate shell commands.