feat: Add MCP server stubs, development docs, and Docker updates

- Add MCP server skeleton implementations for all 7 planned servers
  (llm-gateway, knowledge-base, git, issues, filesystem, code-analysis, cicd)
- Add comprehensive DEVELOPMENT.md with setup and usage instructions
- Add BACKLOG.md with detailed phase planning
- Update docker-compose.dev.yml with Redis and Celery workers
- Update CLAUDE.md with Syndarix-specific context

Addresses issues #16, #20, #21

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CLAUDE.md

@@ -53,7 +53,95 @@ docs/
 ```
 
 ### Current Phase
-**Architecture Spikes** - Validating key decisions before implementation.
+**Backlog Population** - Creating detailed issues for Phase 0-1 implementation.
+
+---
+
+## Development Workflow & Standards
+
+**CRITICAL: These rules are mandatory for all development work.**
+
+### 1. Issue-Driven Development
+
+**Every piece of work MUST have an issue in the Gitea tracker first.**
+
+- Issue tracker: https://gitea.pragmazest.com/cardosofelipe/syndarix/issues
+- Create detailed, well-scoped issues before starting work
+- Structure issues to enable parallel work by multiple agents
+- Reference issues in commits and PRs
+
+### 2. Git Hygiene
+
+**Branch naming convention:** `feature/123-description`
+
+- Every issue gets its own feature branch
+- No direct commits to `main` or `dev`
+- Keep branches focused and small
+- Delete branches after merge
+
+**Workflow:**
+```
+main (production-ready)
+  └── dev (integration branch)
+        └── feature/123-description (issue branch)
+```
+
+### 3. Testing Requirements
+
+**All code must be tested. No exceptions.**
+
+- **TDD preferred**: Write tests first when possible
+- **Test after**: If not TDD, write tests immediately after testable code
+- **Coverage types**: Unit, integration, functional, E2E as appropriate
+- **Minimum coverage**: Aim for >90% on new code
+
+### 4. Code Review Process
+
+**Before merging any feature branch, code must pass multi-agent review:**
+
+| Check | Description |
+|-------|-------------|
+| Bug hunting | Logic errors, edge cases, race conditions |
+| Linting | `ruff check` passes with no errors |
+| Typing | `mypy` passes with no errors |
+| Formatting | Code follows style guidelines |
+| Performance | No obvious bottlenecks or N+1 queries |
+| Security | No vulnerabilities (OWASP top 10) |
+| Architecture | Follows established patterns and ADRs |
+
+**Issue is NOT done until review passes with flying colors.**
+
+### 5. QA Before Main
+
+**Before merging `dev` into `main`:**
+
+- Full test suite passes
+- Manual QA verification
+- Performance baseline check
+- Security scan
+- Code must be clean, functional, bug-free, well-architected, and secure
+
+### 6. Implementation Plan Updates
+
+- Keep `docs/architecture/IMPLEMENTATION_ROADMAP.md` updated
+- Mark completed items as work progresses
+- Add new items discovered during implementation
+
+### 7. UI/UX Design Approval
+
+**Frontend tasks involving UI/UX require design approval:**
+
+1. **Design Issue**: Create issue with `design` label
+2. **Prototype**: Build interactive React prototype (navigable demo)
+3. **Review**: User inspects and provides feedback
+4. **Approval**: User approves before implementation begins
+5. **Implementation**: Follow approved design, respecting design system
+
+**Design constraints:**
+- Prototypes: Best effort to match design system (not required)
+- Production code: MUST follow `frontend/docs/design-system/` strictly
+
+---
 
 ### Key Extensions to Add (from PragmaStack base)
 - Celery + Redis for agent job queue