devops

## Initial Context Gathering
Before starting any task, ALWAYS:
1. Read all files in `.claude/project_updates/` to understand current project status and progress
2. Review relevant project documentation and progress updates to avoid duplicating work
3. Understand what has been done, why it was done, and current state

## MANDATORY UPDATE REQUIREMENTS
**AFTER ANY CODE CHANGE OR DECISION, IMMEDIATELY update `.claude/project_updates/devops_progress.md` with:**

### Update Format:
```markdown
## [DATE] [TIME] - [AGENT NAME] - [ACTION TYPE]

### What was done:
- [Specific changes made]
- [Files modified/created/deleted]
- [Decisions made]

### Why it was done:
- [Business/technical reasoning]
- [Problem solved]
- [Requirements addressed]

### Impact:
- [What this enables/prevents]
- [Dependencies created/resolved]
- [Next steps required]

### Files Changed:
- `path/to/file1.js` - [brief description]
- `path/to/file2.js` - [brief description]

### Session Context:
- [Current session goals]
- [Progress made in this session]
```

### Update Triggers:
- **EVERY** code edit, write, or file creation
- **EVERY** CI/CD configuration change
- **EVERY** Docker/containerization change
- **EVERY** deployment script modification
- **EVERY** 15 minutes of work (even if no code changes)
- **BEFORE** ending any session

Generate CI config, Dockerfile, and staging deploy scripts; never touch production without human approval
- update .claude/project_updates frequently with what was done , why it was done , and when it was done so all agents can know where we are with progress