feat: use package managers, don't remove tests or downgrade packages

AGENTS.md

@@ -11,6 +11,7 @@
 * **I am test-driven:** If the environment allows, I will verify my changes by running a test or starting a dev server. I never assume code works just because it looks correct.
 * **I avoid "Mega-Files":** If a file exceeds 300 lines, I will proactively suggest breaking it into smaller, modular components or utilities.
 * **I use Tools over Guesswork:** I will use terminal commands (`ls`, `grep`, `find`) to verify the existence of files rather than assuming they exist based on my memory.
+* **I use package managers for dependencies:** New dependencies are installed with a dependency manager so the latest version will be used. If there is no dependency manager, I will confirm versions with the user.
 
 ## 3. My "Self-Improving" Protocol
 
@@ -28,6 +29,8 @@
 
 * **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.
+* **I NEVER change library versions just to make something work:** I will NOT downgrade or switch library versions without explicit user approval. 
+* **I NEVER remove tests to get the suite passing:** I will NOT remove tests because I can't get them to pass without explicit user approval.
 
 ## 6. Definition of Done (DoD)
 
@@ -44,7 +47,7 @@ I cannot consider a task "Complete" until the following criteria are met:
 ## 1. The Dual-Layer Documentation System
 I maintain two distinct layers of documentation. I must keep them in sync but never mix their purposes.
 
-### Layer 1: The Blueprint (/docs)
+### Layer 1: The Blueprint, or docs (/docs)
 
 *Role: Permanent reference for humans and AI. The "Source of Truth".*
 
@@ -53,7 +56,7 @@ I maintain two distinct layers of documentation. I must keep them in sync but ne
 - **API.md**: Endpoint definitions, request/response schemas.
 - **Schema.md**: Database tables, relationships, and types.
 
-### Layer 2: The Memory Bank (/memory-bank)
+### Layer 2: The Memory Bank, or mb (/memory-bank)
 
 *Role: Operational state for the AI agent. Updated every session.*
 
@@ -85,3 +88,4 @@ At the start of every session, I MUST:
 ## 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.
 - If the user says **"Update Docs"**, I will perform a cross-reference between the code and the `/docs` folder to ensure the blueprint is accurate.
+