<!-- sid:90c3b059-fc0e-4cf0-ba39-63be64d3f9c1 ws:magitek-ops pn:2 layer:L2-FTS+L3 type:initial ms:25346 -->
[Syncrovanis v0.2.2] onboarding | L2-FTS+L3 via KB-FTS5+copilot-cli | magitek-ops | domener: claude/agents/solo-reportmaker claude/agents/solo-dev-full-reportmaker claude/agents/solo-light-reportmaker ops/monitoring | 25346ms
Layers: L0:miss|L1:miss|L2:hit|L3:hit(copilot-cli)

**[Guardrail] solo-reportmaker: NO SUDO ACCESS - READ THIS FIRST!** _/home/heine/.claude/agents/solo-reportmaker.md_
**⚠️ CRITICAL: Du har IKKE sudo-tilgang. ALDRI prøv sudo-kommandoer!**

```
❌ FORBUDT (kaster vekk tokens - fungerer ALDRI):
- sudo anything (unntatt: sudo systemctl restart puppeteer-server)
- chown
- chmod (systemfiler)
- apt-get / apt install
- systemctl / service (unntatt: puppeteer-server)
- mkdir /var/... (utenfor prosjektmappen)
- Any command requiring root privileges

🔧 SPESIALTILFELLE - Puppeteer restart (DU KAN):
✅ sudo systemctl restart puppeteer-server  (fungerer!)
✅ POST...
**[Guardrail] solo-reportmaker: Critical Documentation (All Roles)** _/home/heine/.claude/agents/solo-reportmaker.md_
1. **[docs/llm/00-ONBOARDING.md](docs/llm/00-ONBOARDING.md)** ← **READ THIS FIRST!**
   - 14 CRITICAL RULES (production environment, git workflow, migrations, etc.)
   - Architecture quick reference
   - Parallel LLM sessions awareness

2. **[docs/llm/04A-CRITICAL-GOTCHAS.md](docs/llm/04A-CRITICAL-GOTCHAS.md)**
   - Top 4 silent failure patterns

3. **[docs/llm/02-KODEBASE-KART.md](docs/llm/02-KODEBASE-KART.md)**
   - File locations and structure

---
**[Guardrail] solo-reportmaker: TOP 5 CRITICAL MISTAKES (DON'T DO THESE!)** _/home/heine/.claude/agents/solo-reportmaker.md_
1. **`sudo` kommandoer** ← ❌ FUNGERER ALDRI! Sløser tokens!
   - ⚠️ Du har IKKE sudo-tilgang i dette miljøet
   - ⚠️ Hver sudo-feil = bortkastet API-kall + token-sløsing
   - ✅ Be brukeren kjøre privilegerte kommandoer manuelt
   - ✅ Finn alternative løsninger som ikke krever root

2. **`git add .`** ← ❌ NEVER! Stages other LLM's work
   - ✅ Use: `git add file1 file2` (specific files only)

3. **`git stash`** ← ❌ NEVER without checking! Stashes OTHER agents' work too!
   - ✅ First: `git status`...
**[Workflow] solo-reportmaker: Bug Detection → Delegate Suggestion (PROAKTIV)** _/home/heine/.claude/agents/solo-reportmaker.md_
**Når bruker-prompt inneholder bug/feil-signaler, STOPP og foreslå delegering FØR du starter!**
**[Guardrail] solo-dev-full-reportmaker: Smart Agent Selection (NEW v2.6 - Cost Optimization)** _/home/heine/.claude/agents/solo-dev-full-reportmaker.md_
**📢 ALLTID VERBOSE (BLOCKING) OUTPUT!**
Agenter skal ALDRI kjøres med `run_in_background: true`.
Kjør agenter synkront (blocking) slik at full verbose output vises i sanntid.

**CRITICAL:** Before spawning agents, analyze complexity → select optimal agent.

| Type | Agent | Cost | Criteria |
|------|-------|------|----------|
| Simple | generic-light | 1x | <50 LOC, 1-2 files, add/fix |
| Moderate | generic-fast-thinking | 4x | 50-200 LOC, 2-5 files, needs analysis |
| Complex |...
**[Guardrail] solo-dev-full-reportmaker: 7. COORDINATION FOLDER STRUCTURE** _/home/heine/.claude/agents/solo-dev-full-reportmaker.md_
**CRITICAL: coordination/ root must stay clean!**

```
✅ ALWAYS use correct subdirectory:

coordination/
├── handoffs/              ← HANDOFF-{NNN}-{YYMMDD}-{desc}.md
├── masterplans/           ← active/MP-*/ + completed/YYYY/MM-mnd-ukeNN/MP-*/
├── experts/
│   └── handoffs/          ← Knowledge handoffs (bug-crusher etc.)
├── tasks/                 ← TASK-*.md
├── audits/                ← AUDIT-*, ANALYSE-*, GAP-ANALYSIS-*.md
├── task-completion/       ← COMPLETION-*.md
├──...
**[Workflow] solo-dev-full-reportmaker: Developer Full Mode** _/home/heine/.claude/agents/solo-dev-full-reportmaker.md_
**Kode på main med orchestrator-koordinering.**
**[Workflow] solo-dev-full-reportmaker: Bug Detection → Delegate Suggestion (PROAKTIV)** _/home/heine/.claude/agents/solo-dev-full-reportmaker.md_
**Når bruker-prompt inneholder bug/feil-signaler, STOPP og foreslå delegering FØR du starter!**
**[Workflow] solo-dev-full-reportmaker: Trigger-ord (sjekk HVER bruker-prompt)** _/home/heine/.claude/agents/solo-dev-full-reportmaker.md_
| Kategori | Nøkkelord |
|----------|-----------|
| **Direkte** | bug, feil, error, exception, crash, broken, ødelagt, virker ikke, fungerer ikke, feiler |
| **Symptomer** | blank side, 500, 404, null, undefined, timeout, spinner, feil data, viser feil, tom, mangler |
| **Debugging** | hvorfor, undersøk, finn ut, debug, trace, reproduser, merkelig, rart, uventet |
**[Guardrail] solo-light-reportmaker: 7. COORDINATION FOLDER STRUCTURE** _/home/heine/.claude/agents/solo-light-reportmaker.md_
**CRITICAL: coordination/ root must stay clean!**

```
✅ ALWAYS use correct subdirectory:

coordination/
├── handoffs/              ← HANDOFF-{NNN}-{YYMMDD}-{desc}.md
├── masterplans/           ← active/MP-*/ + completed/YYYY/MM-mnd-ukeNN/MP-*/
├── experts/
│   └── handoffs/          ← Knowledge handoffs (bug-crusher etc.)
├── tasks/                 ← TASK-*.md
├── audits/                ← AUDIT-*, ANALYSE-*, GAP-ANALYSIS-*.md
├── task-completion/       ← COMPLETION-*.md
├──...
**[Workflow] solo-light-reportmaker: SOLO Light Mode** _/home/heine/.claude/agents/solo-light-reportmaker.md_
**Lean modus for parallelle solo-sesjoner på main branch.**
**[Workflow] solo-light-reportmaker: Bug Detection → Delegate Suggestion (PROAKTIV)** _/home/heine/.claude/agents/solo-light-reportmaker.md_
**Når bruker-prompt inneholder bug/feil-signaler, STOPP og foreslå delegering FØR du starter!**
**[Workflow] solo-light-reportmaker: Trigger-ord (sjekk HVER bruker-prompt)** _/home/heine/.claude/agents/solo-light-reportmaker.md_
| Kategori | Nøkkelord |
|----------|-----------|
| **Direkte** | bug, feil, error, exception, crash, broken, ødelagt, virker ikke, fungerer ikke, feiler |
| **Symptomer** | blank side, 500, 404, null, undefined, timeout, spinner, feil data, viser feil, tom, mangler |
| **Debugging** | hvorfor, undersøk, finn ut, debug, trace, reproduser, merkelig, rart, uventet |
**[Workflow] solo-light-reportmaker: Når triggeret → Vis dette FØRST** _/home/heine/.claude/agents/solo-light-reportmaker.md_
```
🐛 Dette høres ut som debugging/feilsøking.

Dev-agenter er optimalisert for å BYGGE, ikke DIAGNOSTISERE.
Bug-crusher (Opus+Extended Thinking) er designet for:
  → Root cause analysis (5x "Hvorfor?")
  → Data flow tracing gjennom hele stacken
  → Systematisk hypotese-eliminering

Alternativer:
1. /bug-crusher → Dyp debugging med extended thinking (anbefalt for ukjent årsak)
2. /solo-bug-light → Troubleshooter mode med smart agent selection (lettere)
3. Fortsett her → Hvis det er en...
**Gotchas section** _coordination/experts/operations/magitek-server-ops/shared/CURRENT-monitoring-ha.md_
MONITORING-01: Split-Horizon Monitoring DNS
- Symptom: `monitoring*.magitek.no` works on one network but returns `ERR_SSL_UNRECOGNIZED_NAME` on another.
- Cause: both public CNAMEs target `px10.magitek.no`; hjemme-LAN resolution lands on NPM hjemme `192.168.86.16`, while public traffic lands on NPM kontoret.
- Fix: keep matching proxy hosts and valid certs for both FQDNs on both NPM instances.

MO
**Perspectives** _coordination/explore/EX-0002-260303-wordpress-multi-site-management/EXPLORE.md_
#### Perspective 1: MainWP Free -- The Pragmatic Choice

**Approach:** Install MainWP Dashboard on a dedicated WordPress instance. Install MainWP Child on each managed site. Use the 21+ free extensions for backup, security, monitoring, and reporting.

**Pros:**
- Covers ALL five requirements out of the box
- Zero cost
- 12 years of active development, large community
- Unlimited sites
- Self-hoste

MCP: proxmox-hjemme, proxmox-pmox2, proxmox-pmox10, proxmox-pmox15, proxmox-px1, proxmox-px3, docker, serena, context7, dam-sqlite