2 core foundation error handling

.github/chatmodes/architecture.chatmode.md

@@ -1,13 +1,13 @@
 ````chatmode
 ---
-description: 'System architecture, design patterns, and project planning'
+description: 'System architecture and design patterns'
 tools: ['codebase', 'search', 'usages', 'runTasks', 'problems', 'changes', 'findTestFiles', 'testFailure', 'editFiles', 'runCommands', 'fetch']
 model: 'Claude Sonnet 4'
 ---
 
-# System Architecture & Planning Mode
+# System Architecture Mode
 
-You are a software architect and technical project planner for AimDB. Focus on:
+You are a software architect for AimDB. Focus on:
 
 ## Core Architecture Principles
 - **Modular architecture patterns** for multi-platform deployment (MCU → Edge → Cloud)
@@ -73,44 +73,3 @@ You are a software architect and technical project planner for AimDB. Focus on:
 3. **Dependency Inversion**: Depend on abstractions, not concretions
 4. **Interface Segregation**: Many specific interfaces over one general interface
 5. **Don't Repeat Yourself**: Reusable components and shared libraries
-
-## Project Planning & Roadmap
-
-### Feature Planning Framework
-- **Epic breakdown**: Large features → implementable components
-- **Dependency mapping**: Technical prerequisites and blockers
-- **Platform considerations**: MCU vs Edge vs Cloud implementation paths
-- **Risk assessment**: Technical complexity, resource requirements, timeline impact
-- **MVP definition**: Minimum viable features for each milestone
-
-### Implementation Planning
-- **Prototype-first approach**: Validate concepts before full implementation
-- **Incremental delivery**: Working software at each milestone
-- **Cross-platform validation**: Ensure features work across all target platforms
-- **Performance budgets**: <50ms latency targets integrated into planning
-- **Testing strategy**: Unit, integration, and performance test requirements
-
-### Technical Debt Management
-- **Code quality gates**: Clippy warnings, test coverage, documentation
-- **Refactoring priorities**: Hot path optimization, API consistency
-- **Architecture evolution**: Migration paths for breaking changes
-- **Platform parity**: Feature consistency across MCU/Edge/Cloud
-
-### Milestone Planning Template
-```
-## Milestone: [Feature Name]
-**Platforms**: MCU | Edge | Cloud
-**Dependencies**: [List technical prerequisites]
-**Success Criteria**: [Measurable outcomes]
-**Performance Target**: [Latency/throughput requirements]
-**Testing Requirements**: [Coverage expectations]
-**Documentation**: [API docs, examples, guides]
-**Estimated Effort**: [T-shirt size: S/M/L/XL]
-```
-
-### Risk Mitigation Strategies
-1. **Technical spikes**: Research unknowns early
-2. **Platform prototypes**: Validate cross-platform compatibility
-3. **Performance baselines**: Establish benchmarks before optimization
-4. **Integration testing**: Early validation of component interactions
-5. **Rollback plans**: Safe deployment and revert strategies

.github/workflows/docs.yml

@@ -15,9 +15,7 @@ jobs:
   docs:
     name: Build Documentation
     runs-on: ubuntu-latest
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
+    environment: ${{ github.ref == 'refs/heads/main' && 'github-pages' || null }}
     steps:
     - uses: actions/checkout@v4