chore: update agents file, have the agent update the memory-bank

AGENTS.md

@@ -29,6 +29,14 @@
 * **I am honest about failures:** If a tool call fails or I am confused by a requirement, I will stop immediately and ask for clarification rather than "hallucinating" a fix.
 * **I check the logs:** If a terminal command fails, I will read the error output carefully and explain the root cause before attempting a second fix.
 
+## 6. Definition of Done (DoD)
+
+I cannot consider a task "Complete" until the following criteria are met:
+* **Code:** The implementation meets all requirements and follows project patterns.
+* **Quality:** Tests pass and no new linting errors are introduced.
+* **Documentation:** The Memory Bank (`/memory-bank`) is updated to reflect the new state.
+* **Verification:** The user has confirmed the changes work as expected in their environment.
+
 ---
 
 # Project Management & Context Rules
@@ -67,11 +75,12 @@ At the start of every session, I MUST:
 - I only perform tasks listed in `memory-bank/progress.md` or as requested by the user.
 - If I discover a new pattern or make a technical decision (e.g., "we use absolute imports"), I must immediately update `systemPatterns.md`.
 
-### Phase C: Task Completion
+### Phase C: Task Completion (The "DoD" Check)
-Before calling `attempt_completion`, I MUST:
+
-1. Update `memory-bank/activeContext.md` with a summary of changes.
+**CRITICAL:** I MUST NOT call `attempt_completion` until the following documentation steps are finished:
-2. Update `memory-bank/progress.md` by checking off completed items.
+1. **Sync Memory Bank:** Update `memory-bank/activeContext.md` with the latest decisions/changes and `memory-bank/progress.md` with completed milestones.
-3. **If and only if** the changes affect the long-term blueprint, update the corresponding file in `/docs` (e.g., updating `API.md` after adding a route).
+2. **Update Blueprint:** If architectural changes were made, update the corresponding files in `/docs`.
+3. **Final Verification:** Ask the user to verify the feature. Only after their confirmation and the doc updates can I use `attempt_completion`.
 
 ## 3. Automation Commands
 - If the user says **"Initialize Memory Bank"**, I will create the directory and scaffold all 5 files based on the current project state.

memory-bank/activeContext.md

@@ -1,19 +1,16 @@
 # Active Context
 
 ## Current Status
-- Initializing the project environment.
+- Project completed and deployed to Firebase.
-- Documentation phase (Memory Bank & Blueprint).
+- Stable maintenance mode.
 
 ## Recent Changes
-- Created `memory-bank/projectBrief.md`.
+- Updated `AGENTS.md` to include a "Definition of Done" and strict "Phase C" documentation requirements.
-- Created `memory-bank/productContext.md`.
+- Linked documentation updates explicitly to the `attempt_completion` tool in the protocol.
-- Implemented unit conversion on toggle in `src/main.ts`.
+- Synchronized Memory Bank to reflect completed project state.
-- Extracted `convertUnits` utility and added tests.
 
 ## Current Focus
-- Completing Memory Bank initialization.
+- Monitoring for bugs and preparing for future enhancements.
-- Drafting PRD and Architecture.
-- Setting up the Vite/TypeScript/Tailwind environment.
 
 ## Active Decisions
 - **Dark Mode Implementation**: Adopted a Dracula Midnight theme (`#21222c` background) as the primary interface style. Added custom Dracula color palette to `tailwind.config.js`.

memory-bank/progress.md

@@ -17,3 +17,5 @@
 - [x] Implement `index.html` UI
 - [x] Implement `src/main.ts` glue code
 - [x] Verify build output
+- [x] Update `AGENTS.md` with strict documentation rules
+- [x] Synchronize Memory Bank status

memory-bank/systemPatterns.md

@@ -20,11 +20,10 @@
   - `style.css`: Tailwind entry point.
 - `docs/`: Permanent documentation (PRD, Architecture).
 - `memory-bank/`: AI operational context.
-- `tests/`: Unit tests.
+- `src/calculator.test.ts`: Unit tests.
 
 ## Calculation Constants (Defaults)
 - Grid Width/Depth: 42mm
 - Grid Height Unit: 7mm
 - Base Thickness: 4.8mm (typical baseplate height above surface)
 - Bin Lip/Bottom: 0.7mm (typical clearance/thickness to account for in vertical units)
-  - *Note: These defaults will be refined during implementation based on official specs.*