feat: mandate real-time auto-documentation of project memory updates across all interaction turns

GEMINI.md

@@ -22,8 +22,16 @@ Read these first:
 - `project-knowledge/` is canonical project memory.
 - `agent-memory/` is agent operating memory.
 
-## Gemini-Specific Notes
+## Gemini-Specific Mandatory Loop (Real-Time Auto-Documentation)
 
-- Prefer the shared workspace rules over model improvisation.
-- Before answering current-state questions, inspect the current-work files and latest relevant daily note.
-- If a prompt changes durable project understanding or reusable agent behavior, update the smallest correct canonical file.
+At the end of EVERY conversational turn, you MUST evaluate the interaction as a senior Obsidian documentation expert:
+
+1. **Analyze for Memory Impact:** Did the user's prompt or your subsequent action reveal new technical context, resolve an open question, change an architectural assumption, or shift current priorities?
+2. **Identify Target Canonical Files:** If memory impact is detected, identify WHERE in the `project-knowledge/` directory this information belongs. This is NOT limited to daily logs. It could be:
+   - `01-current/current-work.md` (priority shifts, new blockers)
+   - `02-work-items/*.md` (story updates, bug reproduction steps)
+   - `03-context/` (system architecture, processes, workflows)
+   - `04-people/` (stakeholder involvement)
+   - `06-daily/YYYY-MM-DD.md` (daily findings)
+3. **Proactive Update:** You MUST use your file editing tools (`replace_file_content` / `multi_replace_file_content`) to inject the new context or CORRECT existing stale context in the appropriate files BEFORE concluding your response.
+4. **No Explicit Prompt Needed:** Do not wait for the user to say "document this". Auto-document implicitly. Ensure you do not pollute the workspace with unverified guesses; only document confirmed context or active hypotheses.