Testing

CLAUDE.md

@@ -277,14 +277,52 @@ Agent (calculations + thresholds) → Status → Dashboard (display only) → Ta
 - [x] Fixed CPU load parsing for comma decimal separator locale (", " split)
 - [x] Fixed CPU temperature to prioritize x86_pkg_temp over generic thermal zones
 - [x] Fixed C-state collection to discover all available states (including C10)
+- [x] **Dashboard improvements and maintenance mode (2025-10-13)**
+- [x] Host auto-discovery with predefined CMTEC infrastructure hosts (cmbox, labbox, simonbox, steambox, srv01)
+- [x] Host navigation limited to connected hosts only (no disconnected host cycling)
+- [x] Storage widget restructured: Name/Temp/Wear/Usage columns with SMART details as descriptions
+- [x] Agent-provided descriptions for Storage widget (agent is source of truth for formatting)
+- [x] Maintenance mode implementation: /tmp/cm-maintenance file suppresses notifications
+- [x] NixOS borgbackup integration with automatic maintenance mode during backups
+- [x] System widget simplified to single row with C-states as description lines
+- [x] CPU load thresholds updated to production values (9.0/10.0)
 
 **Production Configuration:**
-- CPU load thresholds: Warning ≥ 5.0, Critical ≥ 8.0
+- CPU load thresholds: Warning ≥ 9.0, Critical ≥ 10.0
 - CPU temperature thresholds: Warning ≥ 100°C, Critical ≥ 100°C (effectively disabled)
 - Memory usage thresholds: Warning ≥ 80%, Critical ≥ 95%
 - Connection timeout: 15 seconds (agents send data every 5 seconds)
 - Email rate limiting: 30 minutes (set to 0 for testing)
 
+### Maintenance Mode
+
+**Purpose:**
+- Suppress email notifications during planned maintenance or backups
+- Prevents false alerts when services are intentionally stopped
+
+**Implementation:**
+- Agent checks for `/tmp/cm-maintenance` file before sending notifications
+- File presence suppresses all email notifications while continuing monitoring
+- Dashboard continues to show real status, only notifications are blocked
+
+**Usage:**
+```bash
+# Enable maintenance mode
+touch /tmp/cm-maintenance
+
+# Run maintenance tasks (backups, service restarts, etc.)
+systemctl stop service
+# ... maintenance work ...
+systemctl start service
+
+# Disable maintenance mode  
+rm /tmp/cm-maintenance
+```
+
+**NixOS Integration:**
+- Borgbackup script automatically creates/removes maintenance file
+- Automatic cleanup via trap ensures maintenance mode doesn't stick
+
 ### Development Guidelines
 
 **When Adding New Metrics:**
@@ -306,4 +344,23 @@ NEVER write that you have "successfully implemented" something or generate exten
 
 NEVER implement code without first getting explicit user agreement on the approach. Always ask for confirmation before proceeding with implementation.
 
-NEVER mention Claude or automation in commit messages. Keep commit messages focused on the technical changes only.
+## Commit Message Guidelines
+
+**NEVER mention:**
+- Claude or any AI assistant names
+- Automation or AI-generated content
+- Any reference to automated code generation
+
+**ALWAYS:**
+- Focus purely on technical changes and their purpose
+- Use standard software development commit message format
+- Describe what was changed and why, not how it was created
+- Write from the perspective of a human developer
+
+**Examples:**
+- ❌ "Generated with Claude Code" 
+- ❌ "AI-assisted implementation"
+- ❌ "Automated refactoring"
+- ✅ "Implement maintenance mode for backup operations"
+- ✅ "Restructure storage widget with improved layout"
+- ✅ "Update CPU thresholds to production values"