Implement programmer agent system and consolidate agent infrastructure

Programmer Agent System:
- Add programmer-orchestrator (Opus) for workflow coordination
- Add code-planner (Sonnet) for design and planning
- Add code-implementer (Sonnet) for writing code
- Add code-reviewer (Sonnet) for quality review
- Add /programmer command and project registration skill
- Add state files for preferences and project context

Agent Infrastructure:
- Add master-orchestrator and linux-sysadmin agents
- Restructure skills to use SKILL.md subdirectory format
- Convert workflows from markdown to YAML format
- Add commands for k8s and sysadmin domains
- Add shared state files (model-policy, autonomy-levels, system-instructions)
- Add PA memory system (decisions, preferences, projects, facts)

Cleanup:
- Remove deprecated markdown skills and workflows
- Remove crontab example (moved to workflows)

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

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

automation/README.md

@@ -0,0 +1,74 @@
+# Claude Automation
+
+Scheduled automation for Claude agent workflows using systemd user timers.
+
+## Active Timers
+
+| Timer | Schedule | Purpose |
+|-------|----------|---------|
+| `k8s-agent-health-check.timer` | Every 6 hours | Comprehensive cluster health check |
+| `k8s-agent-daily-summary.timer` | Daily at 8am | Lightweight cluster status digest |
+| `claude-log-rotation.timer` | Weekly (Sunday midnight) | Clean up old log files |
+| `restic-backup.timer` | Hourly | Backup automation |
+| `omarchy-battery-monitor.timer` | Every 30 seconds | Battery status monitoring |
+
+## Commands
+
+```bash
+# List all timers with next run time
+systemctl --user list-timers
+
+# Check timer status
+systemctl --user status k8s-agent-health-check.timer
+
+# Manually trigger a workflow
+systemctl --user start k8s-agent-health-check
+
+# View logs
+journalctl --user -u k8s-agent-health-check
+
+# View recent logs with follow
+journalctl --user -u k8s-agent-health-check -f
+
+# Check for failed services
+systemctl --user --failed
+```
+
+## Timer Locations
+
+All timers and services are in: `~/.config/systemd/user/`
+
+## Workflows
+
+Workflows are in: `~/.claude/workflows/`
+
+- `health/cluster-health-check.yaml` - Full health check (6-hourly)
+- `health/cluster-daily-summary.yaml` - Quick status digest (daily)
+
+## Scheduler
+
+The `scheduler.sh` script wraps Claude CLI invocations:
+
+```bash
+./scheduler.sh <workflow-name>
+./scheduler.sh cluster-health-check
+./scheduler.sh cluster-daily-summary
+```
+
+## Logs
+
+- Workflow logs: `~/.claude/logs/workflows/`
+- Journal logs: `journalctl --user -u <service-name>`
+
+## Maintenance
+
+```bash
+# Reload after editing timer/service files
+systemctl --user daemon-reload
+
+# Enable a new timer
+systemctl --user enable --now <timer-name>.timer
+
+# Disable a timer
+systemctl --user disable --now <timer-name>.timer
+```

automation/crontab.example

@@ -1,18 +0,0 @@
-# K8s Agent Scheduled Workflows
-# Install with: crontab /home/will/.claude/automation/crontab.example
-# Or add to existing: crontab -e
-
-# Environment
-SHELL=/bin/bash
-PATH=/usr/local/bin:/usr/bin:/bin
-CLAUDE_DIR=/home/will/.claude
-DASHBOARD_URL=http://k8s-agent-dashboard-k8s-agent.taildb3494.ts.net
-
-# Cluster health check - every 6 hours
-0 */6 * * * /home/will/.claude/automation/scheduler.sh cluster-health-check >> /home/will/.claude/logs/cron.log 2>&1
-
-# Daily cluster summary - 8am
-0 8 * * * /home/will/.claude/automation/scheduler.sh cluster-health-check >> /home/will/.claude/logs/cron.log 2>&1
-
-# Log rotation - weekly on Sunday at midnight
-0 0 * * 0 find /home/will/.claude/logs -name "*.log" -mtime +7 -delete