fix: restore accidentally deleted coderipple directory

- Restored entire coderipple/ directory from HEAD~1
- Includes all source code, tests, examples, and documentation
- Preserves CI/CD pipeline fixes from previous commit
- 66 files restored including core multi-agent system

Author: robertoallende

coderipple/IMPORT_GUIDELINES.md

@@ -0,0 +1,183 @@
+# CodeRipple Import Guidelines
+
+This document establishes the standard import patterns for the CodeRipple project to ensure consistency across development environments and CI/CD pipelines.
+
+## Standard Import Patterns
+
+### ✅ Correct Import Patterns
+
+All CodeRipple modules should be imported using the package prefix:
+
+```python
+# Core agents
+from coderipple.orchestrator_agent import orchestrator_agent
+from coderipple.tourist_guide_agent import tourist_guide_agent
+from coderipple.building_inspector_agent import building_inspector_agent
+from coderipple.historian_agent import historian_agent
+
+# Core tools
+from coderipple.webhook_parser import GitHubWebhookParser, WebhookEvent
+from coderipple.git_analysis_tool import analyze_git_diff
+from coderipple.config import get_config
+
+# Content generation and validation
+from coderipple.content_generation_tools import generate_content
+from coderipple.bedrock_integration_tools import enhance_content_with_bedrock
+from coderipple.content_validation_tools import validate_content_quality
+
+# Analysis tools
+from coderipple.source_code_analysis_tool import analyze_source_code
+from coderipple.existing_content_discovery_tool import discover_existing_content
+
+# Advanced features
+from coderipple.agent_context_flow import coordinate_agents
+from coderipple.real_diff_integration_tools import integrate_diff_analysis
+```
+
+### ❌ Incorrect Import Patterns
+
+**Do NOT use these patterns:**
+
+```python
+# ❌ Direct module imports (will fail in CI/CD)
+from webhook_parser import GitHubWebhookParser
+from git_analysis_tool import analyze_git_diff
+from tourist_guide_agent import tourist_guide_agent
+
+# ❌ src.module imports (legacy pattern)
+from src.webhook_parser import GitHubWebhookParser
+from src.git_analysis_tool import analyze_git_diff
+
+# ❌ sys.path manipulation (not needed with proper package structure)
+import sys
+import os
+sys.path.insert(0, os.path.join(os.path.dirname(__file__), '..', 'src'))
+```
+
+## Package Structure
+
+CodeRipple follows standard Python package structure:
+
+```
+coderipple/
+├── src/
+│   └── coderipple/
+│       ├── __init__.py
+│       ├── orchestrator_agent.py
+│       ├── tourist_guide_agent.py
+│       ├── building_inspector_agent.py
+│       ├── historian_agent.py
+│       ├── webhook_parser.py
+│       ├── git_analysis_tool.py
+│       ├── config.py
+│       └── ... (other modules)
+├── tests/
+│   ├── test_*.py (all test files)
+│   └── test_import_diagnostics.py (diagnostic framework)
+└── examples/
+    └── *.py (example files)
+```
+
+## Environment Compatibility
+
+These import patterns work consistently across:
+
+- **Local Development**: macOS, Linux, Windows
+- **CI/CD Pipelines**: GitHub Actions, GitLab CI, etc.
+- **AWS Lambda**: Production deployment environment
+- **Docker Containers**: Containerized deployments
+
+## Diagnostic Tools
+
+### Import Diagnostics Test
+
+Run the comprehensive import diagnostic test to validate your environment:
+
+```bash
+cd coderipple
+python3 tests/test_import_diagnostics_standalone.py
+```
+
+This test provides:
+- Environment analysis (Python version, paths, package installation)
+- Available modules discovery
+- Import validation with specific error reporting
+- Actionable recommendations for fixing issues
+
+### Pytest Integration
+
+For pytest-based testing:
+
+```bash
+cd coderipple
+pytest tests/test_import_diagnostics.py -v
+```
+
+## Troubleshooting
+
+### Common Issues and Solutions
+
+**Issue**: `ModuleNotFoundError: No module named 'module_name'`
+**Solution**: Use `from coderipple.module_name import ...` instead of `from module_name import ...`
+
+**Issue**: `ModuleNotFoundError: No module named 'src.module_name'`
+**Solution**: Replace `from src.module_name import ...` with `from coderipple.module_name import ...`
+
+**Issue**: Imports work locally but fail in CI/CD
+**Solution**: Ensure you're using the `coderipple.` prefix for all CodeRipple modules
+
+**Issue**: `ModuleNotFoundError: No module named 'coderipple'`
+**Solution**: Install the CodeRipple package: `cd coderipple && pip install -e .`
+
+### Environment Validation
+
+Check your environment setup:
+
+```python
+import sys
+import coderipple
+
+print(f"Python version: {sys.version}")
+print(f"CodeRipple installed: {coderipple.__file__}")
+print(f"CodeRipple version: {coderipple.__version__}")
+```
+
+## Development Workflow
+
+### Before Committing Code
+
+1. **Run import diagnostics**: `python3 tests/test_import_diagnostics_standalone.py`
+2. **Verify test imports**: `python3 -c "from tests.test_your_module import *"`
+3. **Check example imports**: `python3 -c "from examples.your_example import *"`
+4. **Run full test suite**: `pytest tests/ -v`
+
+### Code Review Checklist
+
+- [ ] All imports use `from coderipple.module_name import ...` pattern
+- [ ] No `sys.path.insert()` statements in test or example files
+- [ ] No `from src.module_name import ...` patterns
+- [ ] No direct module imports without `coderipple.` prefix
+- [ ] Import diagnostic test passes
+
+## CI/CD Integration
+
+The import diagnostic framework is integrated into the CI/CD pipeline to catch import issues before deployment:
+
+```yaml
+# GitHub Actions example
+- name: Run Import Diagnostics
+  run: |
+    cd coderipple
+    python3 tests/test_import_diagnostics_standalone.py
+```
+
+## Future Enhancements
+
+- **Import Linting**: Consider adding flake8 or pylint rules to enforce import patterns
+- **Pre-commit Hooks**: Automatically validate imports before commits
+- **IDE Integration**: Configure IDEs to suggest correct import patterns
+
+---
+
+**Last Updated**: Unit 14.2 Implementation (June 2025)
+**Maintained By**: CodeRipple Development Team

coderipple/README.md

@@ -0,0 +1,58 @@
+# coderipple Documentation Hub
+
+*Auto-generated documentation hub maintained by CodeRipple Tourist Guide Agent*  
+*Last updated: 2025-06-26 23:41:17*
+
+---
+
+Welcome to the coderipple documentation! This hub provides access to all automatically maintained documentation organized by a **layered documentation structure** - three layers that handle different depths of understanding.
+
+## Documentation Layers
+
+### 🎯 User Documentation (How to ENGAGE)
+*Start here if you want to use or contribute to coderipple*
+
+*No user documentation available yet*
+
+### 🏗️ System Documentation (What it IS)
+*Current system architecture, capabilities, and technical specifications*
+
+- **[architecture.md](coderipple/system/architecture.md)**: System Architecture
+  *Updated: 2025-06-26 23:41:17*
+
+### 📚 Decision Documentation (Why it BECAME this way)
+*Historical context, architectural decisions, and evolution story*
+
+- **[architecture_decisions.md](coderipple/decisions/architecture_decisions.md)**: Architectural Decision Records
+  *Updated: 2025-06-26 23:41:17*
+
+---
+
+## Quick Navigation
+
+- **[Repository](https://github.com/robertoallende/coderipple)** - Source code and issues
+- **Documentation Status**: 2 files across 2 layers
+- **Framework**: [Layered Documentation Structure](https://github.com/robertoallende/coderipple#documentation-layers)
+
+## About This Documentation
+
+This documentation is automatically maintained by **CodeRipple**, a multi-agent system that updates documentation based on code changes. Each layer serves a different purpose:
+
+- **User docs** help you discover, learn, and use the system
+- **System docs** explain what currently exists and how it works  
+- **Decision docs** preserve why things were built this way
+
+*Documentation automatically updates when code changes. If you notice gaps or issues, please [create an issue](https://github.com/robertoallende/coderipple/issues).*
+
+## System Status
+
+- ✅ **Step 1**: GitHub webhook payload parsing  
+- ✅ **Step 2**: Git analysis tool framework
+- ✅ **Step 3**: Multi-agent system (Tourist Guide, Building Inspector, Historian)
+- ✅ **Step 4A-F**: Complete enhanced documentation generation (README, intelligent content, context flow, Bedrock integration, validation, real diff)
+- ✅ **Step 5A-D**: Advanced agent capabilities (source analysis, content discovery, update logic, context-rich generation)
+- ✅ **Step 6**: Tourist Guide enhancement (bootstrap, user documentation structure)
+- ✅ **Step 7**: Configuration management & directory structure
+- 📅 **Step 8**: AWS infrastructure deployment (Lambda, API Gateway, Terraform)
+
+*Generated by CodeRipple Tourist Guide Agent on 2025-06-26 23:41:17*