umb

.claude/settings.local.json

@@ -17,7 +17,8 @@
       "mcp__memory__create_relations",
       "mcp__memory__add_observations",
       "Bash(mkdir:*)",
-      "Bash(mv:*)"
+      "Bash(mv:*)",
+      "mcp__memory__read_graph"
     ],
     "deny": []
   },

memory-bank/decisionLog.md

@@ -23,5 +23,22 @@ This file records architectural and implementation decisions using a list format
 **Rationale**: Professional repository needs structured issue/PR workflows for contributors
 **Implementation Details**: 4 YAML issue templates + markdown PR template with validation requirements
 
+**GitHub Workflow Decision**: Create automated Docker build and push workflow
+**Rationale**: Automate CI/CD pipeline for consistent Docker image deployment to GHCR
+**Implementation Details**: .github/workflows/build_and_publish_docker.yml with push trigger on main branch, GHCR authentication using secrets.GITHUB_TOKEN, dual tagging (latest + commit SHA)
+
+**Dependencies Management**: Use Poetry for Python dependency management
+**Rationale**: Deterministic builds with poetry.lock, single source of truth in pyproject.toml
+**Implementation Details**: Existing pyproject.toml configuration, Poetry-based dependency tracking
+
+**Code Quality Tools**: Black for formatting, Ruff for linting
+**Rationale**: Consistent code style and quality across project
+**Implementation Details**: Configuration in pyproject.toml, integration with pre-commit hooks and CI
+
+**Branching Strategy**: Simplified GitFlow with feature branches
+**Rationale**: Clean main branch representing production, structured development workflow
+**Implementation Details**: feature/* branches → main via Pull Requests
+
 ---
 2025-01-11 22:47:00 - Initial creation with key decisions from session
+2025-01-11 22:50:00 - Added GitHub workflow, Poetry, code quality, and branching decisions from Memory MCP history

memory-bank/progress.md

@@ -24,6 +24,9 @@ This file tracks the project's progress using a task list format.
 
 ## Next Steps
 
+- **PRIORITY**: Create GitHub workflow file (.github/workflows/build_and_publish_docker.yml)
+- Create GitHub issue templates (bug_report.md, feature_request.md) 
+- Create GitHub pull request template (pull_request_template.md)
 - Consider creating remaining documentation files:
   - docs/architecture/overview.md
   - docs/api/tools/ documentation for individual Gemini tools

memory-bank/systemPatterns.md

@@ -12,6 +12,8 @@ It is optional, but recommended to be updated as the project evolves.
 - **Configuration Management**: Centralized config.py with environment variable handling
 - **Utility Organization**: Shared utilities in `utils/` for file operations, git, tokens
 - **Testing Strategy**: Comprehensive test suite with both unit tests and live integration tests
+- **Dependency Management**: Poetry with pyproject.toml as single source of truth
+- **Code Quality**: Black for formatting, Ruff for linting, pre-commit hooks integration
 
 ## Architectural Patterns
 
@@ -19,6 +21,8 @@ It is optional, but recommended to be updated as the project evolves.
 - **Memory Management**: Dual approach - file-based Memory Bank + Memory MCP entities
 - **Documentation-Driven Development**: All code changes require corresponding documentation
 - **Collaboration Framework**: Structured Claude-Gemini interaction patterns with tool selection matrix
+- **CI/CD Pipeline**: GitHub Actions with automated Docker build and GHCR publishing
+- **Branching Strategy**: Simplified GitFlow - feature/* → main via Pull Requests
 
 ## Testing Patterns