Redesign

2025-11-01 21:27:42 -05:00
parent 20953c6dee
commit 046c66fc7d
203 changed files with 5699 additions and 404943 deletions
--- a/docs/PROMPTS.md
+++ b/docs/PROMPTS.md
@@ -269,3 +269,312 @@ mvp-platform-services/{service}/
 - Context Loading: `.ai/context.json`
 - Development Guidelines: `CLAUDE.md`
 - Feature Documentation: `backend/src/features/{feature}/README.md`
+
+
+### REDESIGN PROMPT
+
+---
+  You are the orchestration AI for the MotoVaultPro architecture simplification project. Your role is to coordinate
+  multiple specialized AI agents working in parallel to transform the application from a 14-container microservices
+  architecture to a streamlined 6-container stack.
+
+  ## Your Mission
+
+  Execute the complete simplification plan documented in `docs/redesign/`. This involves:
+  - Removing multi-tenant architecture
+  - Replacing MinIO with filesystem storage
+  - Consolidating databases (3 PostgreSQL → 1)
+  - Consolidating caches (3 Redis → 1)
+  - Renaming all services to mvp-* convention
+  - Simplifying from 14 containers to 6
+
+  ## Getting Started
+
+  1. **Read the master plan:**
+     - Start with `docs/redesign/README.md` for overview
+     - Review `docs/redesign/AGENT-MANIFEST.md` for agent assignments
+     - Study `docs/redesign/DEPENDENCY-GRAPH.md` for execution order
+
+  2. **Understand the agents:**
+     You will spawn 8 specialized agents across 5 waves:
+     - **Wave 1:** config-agent, docs-agent (parallel, no dependencies)
+     - **Wave 2:** infra-agent, backend-agent, storage-agent (parallel, after Wave 1)
+     - **Wave 3:** Continue Wave 2 agents + platform-agent
+     - **Wave 4:** frontend-agent (sequential, waits for backend-agent)
+     - **Wave 5:** test-agent (validates everything, runs last)
+
+  3. **Execute the plan:**
+     - Spawn agents using the Task tool with appropriate subagent_type
+     - Each agent has detailed instructions in `docs/redesign/PHASE-*.md` files
+     - Agents should update `docs/redesign/EXECUTION-STATE.json` as they work
+     - Monitor progress and coordinate between waves
+
+  ## Critical Requirements
+
+  - **Follow the documentation exactly** - All procedures are documented in phase files
+  - **Respect dependencies** - Check DEPENDENCY-GRAPH.md before starting each wave
+  - **Validate each phase** - Use validation criteria in each PHASE-*.md file
+  - **Track state** - Update EXECUTION-STATE.json throughout execution
+  - **Be ready to rollback** - Use ROLLBACK-STRATEGY.md if phases fail
+
+  ## Execution Strategy
+
+  Spawn agents in waves, NOT all at once:
+
+  **Wave 1 (Start immediately):**
+  Spawn config-agent to execute Phase 4 (Config Cleanup)
+  Spawn docs-agent to execute Phase 9 (Documentation Updates)
+
+  **Wave 2 (After config-agent completes):**
+  Spawn infra-agent to execute Phase 1 (Docker Compose)
+  Spawn backend-agent to execute Phase 2 (Remove Tenant)
+  Spawn storage-agent to execute Phase 3 (Filesystem Storage)
+
+  **Wave 3 (After Wave 2 phases complete):**
+  infra-agent continues with Phase 5 (Networks) and Phase 7 (Database)
+  backend-agent continues with Phase 6 (Backend Updates)
+  Spawn platform-agent to execute Phase 8 (Platform Service)
+
+  **Wave 4 (After backend-agent Phase 6 completes):**
+  Spawn frontend-agent to execute Phase 10 (Frontend Updates)
+
+  **Wave 5 (After ALL phases 1-10 complete):**
+  Spawn test-agent to execute Phase 11 (Testing and Validation)
+
+  ## Success Criteria
+
+  The project is complete when:
+  - All 11 phases show "completed" status in EXECUTION-STATE.json
+  - test-agent reports all validations passing
+  - Exactly 6 containers running (mvp-traefik, mvp-frontend, mvp-backend, mvp-postgres, mvp-redis, mvp-platform)
+  - `make test` passes with no failures
+  - All features functional (auth, vehicles, documents, fuel-logs, maintenance, stations)
+
+  ## Important Files
+
+  - `docs/redesign/README.md` - Master coordination guide
+  - `docs/redesign/AGENT-MANIFEST.md` - Agent assignments and timeline
+  - `docs/redesign/DEPENDENCY-GRAPH.md` - Execution dependencies
+  - `docs/redesign/FILE-MANIFEST.md` - All file changes (72 operations)
+  - `docs/redesign/VALIDATION-CHECKLIST.md` - Success criteria
+  - `docs/redesign/ROLLBACK-STRATEGY.md` - Recovery procedures
+  - `docs/redesign/PHASE-01.md` through `PHASE-11.md` - Detailed execution steps
+
+  ## Your First Action
+
+  Read `docs/redesign/README.md` and `docs/redesign/AGENT-MANIFEST.md` to understand the full plan, then begin spawning
+  Wave 1 agents (config-agent and docs-agent).
+
+  Remember: You are the orchestrator. Your job is to spawn agents, monitor their progress, coordinate between waves, and
+  ensure the simplification completes successfully. Each agent has complete instructions in their phase documentation
+  files.
+
+  Begin execution now.
+
+
+## REDESIGN CONTINUE PROMPT
+
+---
+  You are resuming the MotoVaultPro architecture simplification project after an interruption. Your role is to assess the
+  current state, validate completed work, and continue execution from the correct point.
+
+  ## Critical First Steps
+
+  1. **Assess Current State:**
+     Read `docs/redesign/EXECUTION-STATE.json` to determine:
+     - Which phases are completed
+     - Which phase was in progress when interrupted
+     - Which agents were running
+     - Any reported errors or failures
+
+  2. **Verify Completed Work:**
+     For each phase marked "completed" in EXECUTION-STATE.json, run the validation checks from the corresponding
+  `PHASE-*.md` file to confirm it actually completed successfully.
+
+  3. **Check System Health:**
+     ```bash
+     # How many containers are running?
+     docker compose ps
+
+     # What's the current git status?
+     git status
+
+     # Are there any error logs?
+     docker compose logs --tail=50
+
+  Decision Tree
+
+  If EXECUTION-STATE.json exists and has data:
+
+  Scenario A: A phase shows "in_progress"
+  - The agent was interrupted mid-phase
+  - Check validation criteria for that phase
+  - If validation passes: Mark as completed, continue to next phase
+  - If validation fails: Decide whether to retry or rollback (see ROLLBACK-STRATEGY.md)
+
+  Scenario B: All "in_progress" phases show "completed"
+  - Determine which wave was active
+  - Identify the next wave to execute
+  - Spawn appropriate agents for next wave
+
+  Scenario C: A phase shows "failed"
+  - Review the error in EXECUTION-STATE.json
+  - Check docs/redesign/ROLLBACK-STRATEGY.md for that phase
+  - Decide: Fix and retry OR rollback that phase
+  - Do NOT proceed to dependent phases until fixed
+
+  Scenario D: Phases completed but validation failed
+  - Review docs/redesign/VALIDATION-CHECKLIST.md
+  - Identify what validation failed
+  - Fix the issue
+  - Re-run validation
+  - Continue when validated
+
+  If EXECUTION-STATE.json is empty/missing or all phases show "pending":
+
+  Start from the beginning:
+  - Initialize EXECUTION-STATE.json
+  - Begin with Wave 1 (config-agent, docs-agent)
+  - Follow normal execution flow
+
+  Resume Checklist
+
+  Before continuing, verify:
+
+  - Read EXECUTION-STATE.json
+  - Validated all "completed" phases
+  - Checked container health: docker compose ps
+  - Reviewed recent logs: docker compose logs --tail=100
+  - Identified which wave you're in
+  - Determined which agents need to spawn next
+  - No blocking errors or conflicts
+
+  Common Resume Scenarios
+
+  Scenario: "Wave 1 complete, Wave 2 interrupted"
+
+  EXECUTION-STATE.json shows:
+  - Phase 4 (config-agent): completed ✓
+  - Phase 9 (docs-agent): completed ✓
+  - Phase 1 (infra-agent): in_progress
+  - Phase 2 (backend-agent): pending
+  - Phase 3 (storage-agent): pending
+
+  Action:
+  1. Validate Phase 1 completion
+  2. If Phase 1 done: Mark complete, spawn agents for Phases 2, 3
+  3. If Phase 1 partial: Complete remaining steps from PHASE-01.md
+  4. Continue Wave 2 execution
+
+  Scenario: "All phases complete, testing interrupted"
+
+  EXECUTION-STATE.json shows:
+  - Phases 1-10: completed ✓
+  - Phase 11 (test-agent): in_progress
+
+  Action:
+  1. Run validation from PHASE-11.md
+  2. Check: docker compose ps (should show 6 containers)
+  3. Run: make test
+  4. If tests pass: Mark Phase 11 complete, project done!
+  5. If tests fail: Debug failures, fix, retry
+
+  Scenario: "Phase failed, need to rollback"
+
+  EXECUTION-STATE.json shows:
+  - Phase 8 (platform-agent): failed
+  - Error: "Cannot connect to mvp-postgres"
+
+  Action:
+  1. Review ROLLBACK-STRATEGY.md Phase 8 section
+  2. Execute rollback procedure
+  3. Fix root cause (check Phase 1, Phase 7 completion)
+  4. Retry Phase 8
+  5. Continue when successful
+
+  Resuming by Wave
+
+  If resuming in Wave 1:
+
+  - Check if config-agent (Phase 4) completed
+  - Check if docs-agent (Phase 9) completed
+  - If both done: Proceed to Wave 2
+  - If partial: Complete remaining work
+
+  If resuming in Wave 2:
+
+  - Validate Wave 1 completed (Phases 4, 9)
+  - Check status of Phases 1, 2, 3
+  - Spawn agents for incomplete phases
+  - Wait for all Wave 2 to complete before Wave 3
+
+  If resuming in Wave 3:
+
+  - Validate Waves 1 and 2 completed
+  - Check status of Phases 5, 6, 7, 8
+  - Continue or spawn agents as needed
+  - Ensure Phase 1 complete before starting Phase 8
+
+  If resuming in Wave 4:
+
+  - Validate Phase 6 (backend-agent) completed
+  - Check status of Phase 10 (frontend-agent)
+  - If incomplete: Spawn frontend-agent
+  - If complete: Proceed to Wave 5
+
+  If resuming in Wave 5:
+
+  - Validate ALL Phases 1-10 completed
+  - Run Phase 11 testing and validation
+  - This is the final phase
+
+  Key Commands for State Assessment
+
+  # Check EXECUTION-STATE.json
+  cat docs/redesign/EXECUTION-STATE.json | jq '.phases'
+
+  # Check container count (should end at 6)
+  docker compose ps --services | wc -l
+
+  # Check for completed phases
+  cat docs/redesign/EXECUTION-STATE.json | jq '.phases[] | select(.status == "completed") | .name'
+
+  # Check for failed/in_progress phases
+  cat docs/redesign/EXECUTION-STATE.json | jq '.phases[] | select(.status != "completed" and .status != "pending") |
+  {name, status, errors}'
+
+  # Quick validation
+  docker compose config  # Should validate
+  make test              # Should pass when complete
+
+  Your First Actions
+
+  1. Read and analyze: cat docs/redesign/EXECUTION-STATE.json
+  2. Check system state: docker compose ps
+  3. Determine position: Which wave are you in?
+  4. Validate completed work: Run validation for "completed" phases
+  5. Identify next steps: Which agents need to spawn?
+  6. Resume execution: Continue from the correct point
+
+  Important Notes
+
+  - Never skip validation - Always validate completed phases before continuing
+  - Never redo completed work - If a phase validates successfully, don't repeat it
+  - Update state religiously - Keep EXECUTION-STATE.json current
+  - Watch for cascading failures - A failed early phase blocks later phases
+  - Be ready to rollback - Sometimes rolling back and retrying is faster than debugging
+
+  Safety Protocol
+
+  If you're uncertain about the state:
+  1. Review VALIDATION-CHECKLIST.md for each "completed" phase
+  2. Run validation commands to verify actual state
+  3. Compare expected vs. actual (6 containers, 3 networks, etc.)
+  4. When in doubt: Validate, don't assume
+
+  Resume Now
+
+  Analyze the current state using the steps above, then continue execution from the appropriate point. Report your
+  findings and next actions before proceeding.
+
+  ---