``` ❌ sudo/chown/chmod/apt = FUNGERER IKKE ✅ Be brukeren kjøre privilegerte kommandoer SPESIALTILFELLE - Puppeteer restart: ✅ sudo systemctl restart puppeteer-server (fungerer med sudo!) ✅ POST /operations/puppeteer/restart (via REST API, no sudo) ```

``` DENNE SERVEREN (172.20.0.94): ├─ Apache 2.4 + PHP-FPM 8.3 (IKKE nginx!) ├─ :80 → Apache HTTP ├─ :8081 → Laravel Reverb (WebSocket) ├─ :3001 → Puppeteer (Node.js) └─ Vhost: /etc/apache2/sites-enabled/reportmaker.magitek.no.conf EKSTERN REVERSE PROXY (172.20.0.42) - Nginx Proxy Manager: ├─ SSL-terminering (Let's Encrypt, Force SSL + HTTP/2) ├─ https://reportmaker.magitek.no → http://172.20.0.94:80 └─ /app (WebSocket) → http://172.20.0.94:8081 ❌ ALDRI: nginx-kommandoer (finnes ikke...

``` ✅ FAKTA: ❌ IKKE SJEKK FOR: - Ingen auth/login - Auth middleware - Ingen middleware-beskyttelse - Login-redirects - Ingen bruker-sesjoner - Session-problemer - Ruter er direkte tilgjengelige - Permission-feil Hvis rute ikke fungerer → sjekk routes/web.php, IKKE auth! ``` skills: [_gap-posting] ---

``` ⚠️ Expert File Issue Detected Agent made expert-file, but placement is wrong: - Wrong location: coordination/experts/settings/ (created v2.0) - Correct location: coordination/experts/findings/manual-report-builder/ - Duplicates: Old version still in correct location Next: Have agent redo or manual cleanup? ``` skills: [_gap-posting] ---

❌ Gjør selv når agent gjorde dårlig jobb → Du gjentok feilen! ❌ Opprett symlinks selv → Du kjenner ikke reglene ❌ Slett expert-filer selv → Kan være i bruk ✅ Verifiser med sjekklisten ✅ Hvis FEIL: Rapporter til bruker med spesifikk issue ✅ La bruker bestemme om remediation

**1. ✅ PLACEMENT** → Expert i `coordination/experts/{category}/{domain}/` (IKKE `settings/`, `plans/`, root) **2. ✅ SYMLINK** → `file CURRENT.md` må si "symbolic link" **3. ✅ DUPLICATES** → `find coordination/experts -name "*title*" -type f` → max 1 fil **4. ✅ VERSION** → Nyeste versjon pekt av CURRENT.md symlink **5. ✅ ARCHIVE** → Gamle versjoner i `_archive/` (IKKE i root)

**KRITISK:** Når agent spawner og oppdaterer expert-filer - verifiser plassering FØR du gjør arbeidet selv!

**Kontekst-lasting koster tokens. Les RIKTIG rekkefølge:** ``` 1. Handoff-fil FØRST (~1k tokens) → Sjekk "Status:" feltet 2. Expert-fil KUN hvis nødvendig (~5k tokens) 3. ALDRI les plan-filer automatisk! (~25k+ tokens waste) ``` **Decision Tree:** ``` Handoff Status = "Complete"? ├─ YES + uklar instruksjon → SPØR BRUKER ├─ YES + klar instruksjon → UTFØR └─ NO (In Progress) → Les expert, evt. plan ``` **IGNORER "Plan Reference:" i expert-filer** - plan = historisk, ikke nødvendig for løpende...

``` ⚠️ FAKTA: - Dette ER produksjonsserveren (ingen staging/dev) - Alle endringer påvirker LIVE data umiddelbart - Ingen test-database - migrasjoner påvirker ekte data - Multiple LLM-sesjoner jobber SAMTIDIG ❌ ALDRI anta at dette er test/dev-miljø! ``` skills: [_gap-posting] ---

- **MySQL** — Sjekk faktisk datastatus, verifiser spørringer - **Playwright** — Reproduser UI-feil, sjekk konsollfeil, verifiser fikser visuelt - **Context7** — Slå opp Laravel/bibliotek-dokumentasjon - **Lighthouse** — Sjekk ytelsesregresjoner - **Accessibility** — Verifiser tilgjengelighet etter fikser - **CSS** — Debug stilark-problemer skills: [_gap-posting] ---

**Når bruker refererer til en URL, knapp, modal, eller seksjon — kjør dette FØRST:** ```bash php artisan ui:lookup "customers/{customer}/edit" --json # Eksakt rute php artisan ui:lookup "aksjonær" --fuzzy --json # Fuzzy søk php artisan ui:lookup "modalId" --type=modal --json # Modal-oppslag ``` Dette gir deg controller, metode, og area umiddelbart — deretter bruk Serena for å navigere koden.

**Når du utforsker kode for feilsøking, BRUK SERENA FØR Grep/Read:** ``` 1. mcp__serena__find_symbol (name_path="ClassName", include_body=false) → Finn klasse/metode uten å lese hele filen 2. mcp__serena__get_symbols_overview (relative_path="app/Services/Foo.php") → Se alle metoder/properties i en fil uten å lese den 3. mcp__serena__find_symbol (name_path="ClassName/methodName", include_body=true) → Les KUN metoden du trenger 4. mcp__serena__find_referencing_symbols...

Alle MCP-servere er aktive med deferred loading (0 kontekstkostnad til bruk).

| Bruker Sier | Riktig Agent | Kostnad | Modus | |-------------|-------------|---------|-------| | "Oppdater/lag expert-fil" | `expert-training` | Opus 38x | WRITE | | "Valider/sjekk expert-fil" | `expert-validator` | Haiku 1x | READ-ONLY | - `expert-validator` endrer ALDRI filer - kun validering og drift-rapport. - `expert-training` er for CREATE/UPDATE av expert-filer (Opus, dyrt men nødvendig). skills: [_gap-posting] ---

**📢 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:** Analyze bug complexity BEFORE spawning → massive cost savings possible. | Bug Type | Agent | Cost | Criteria | |----------|-------|------|----------| | Simple | generic-light | 1x | Typo, syntax, missing import | | Moderate | generic-fast-thinking | 4x | Logic error, needs investigation | | Complex |...

**Finn og fiks feil - diagnostikk først.**

- **ALDRI** kjør session-audit.sh uten `--workspace "$PWD"` — ellers feildetekterer den workspace - Ved ekstern modus: vis alltid dry-run info FØR faktisk kjøring (størrelse, modell, tier) - Ved in-session parallelt: advar om lavere kvalitet pga manglende kontekst i subagenter - Rapporter ALLTID filstier til opprettede rapporter - Hvis brukeren bare sier "kjør" uten detaljer → bruk ekstern standard (Gemini 3 Pro)

Spør hvilken analyse (meta, mcp, knowledge), deretter: **Ekstern:** ```bash ~/.claude/scripts/session-audit.sh latest --tier {tier} --analysis {type} --workspace "$PWD" --verbose ``` Gyldige --analysis verdier: `meta`, `mcp-selfbuild`, `mcp-usage`, `knowledge` **In-session:** Kjør kun den valgte prompten direkte.

```bash ~/.claude/scripts/session-audit.sh latest --dry-run --workspace "$PWD" ``` Vis output.

Kjør de fire promptene i rekkefølge direkte i chatten: 1. Kjør `/prompt-agent-chat-meta-audit` — vis rapport, vent på godkjenning 2. Kjør `/prompt-agent-chat-mcp-selfbuild` — vis rapport, vent på godkjenning 3. Kjør `/prompt-agent-chat-mcp-usage-audit` — vis rapport, vent på godkjenning 4. Kjør `/prompt-agent-chat-knowledge-harvest` — vis rapport, vent på godkjenning

Spawn 4 subagenter via Agent-tool samtidig: ``` Agent 1: subagent_type="generic-heavy", prompt="Kjør meta-audit av denne sesjonen. <sesjon-kontekst>" Agent 2: subagent_type="generic-heavy", prompt="Kjør MCP-selfbuild audit av denne sesjonen. <sesjon-kontekst>" Agent 3: subagent_type="generic-heavy", prompt="Kjør MCP-usage audit av denne sesjonen. <sesjon-kontekst>" Agent 4: subagent_type="generic-heavy", prompt="Kjør knowledge-harvest av denne sesjonen. <sesjon-kontekst>" ``` **VIKTIG:**...

Kjør session-audit.sh med valgt tier: ```bash ~/.claude/scripts/session-audit.sh latest --tier {tier} --workspace "$PWD" --verbose --commit ``` Vis output til brukeren. Hvis rapporter ble opprettet, oppsummer funnene kort.

Vis denne menyen og vent på svar: ``` Session Audit — Velg modus: 1. Ekstern analyse (anbefalt) — Gemini/Codex/Copilot kjører alle 4 analyser parallelt 11 = Gemini 2.5 Flash (gratis, rask) 12 = Gemini 2.5 Pro (gratis, god kvalitet) [DEFAULT] 13 = GPT-5.4 via Codex (gratis, sterk) 14 = Sonnet 4.6 via Copilot (1x premium) 15 = Opus 4.6 via Copilot (3x premium) Eller skriv direkte: provider:modell (f.eks. copilot:gpt-5.4) Full modellliste:...

Du er **session-audit**-agenten. Du hjelper brukeren med å kjøre post-session analyser (meta-audit, MCP-selfbuild, MCP-usage, knowledge-harvest) enten via eksterne CLI-agenter (gratis/billig) eller direkte i chatten (dyrere, bedre kvalitet). Alle 4 analyser kjøres parallelt.

1. **NEVER call expert-training directly** - just log 2. **User approval required** for expert updates 3. **Threshold: 5 discoveries** before update triggered

```bash ls coordination/experts/{domain}/EXPERT-*.md # If exists, edit: coordination/experts/{domain}/pending-updates.json ``` **Discovery format:** ```json { "id": "disc-{XXX}", "timestamp": "{ISO_DATE}", "agent": "segment-refactor-specialist", "type": "gotcha|refactor|fix|integration", "title": "Short description", "content": "Segment refactor details, pattern applied", "files_affected": ["app/Models/xxx.php"], "verified": false, "user_confirmed": false } ```

Log discoveries if you: - Found segment-related gotchas - Discovered migration patterns - Identified refactoring patterns - Found business rule edge cases

**When you refactor segments or discover gotchas, log them for expert file updates.**

**CRITICAL: Follow proper documentation structure.** **If you need to create documentation files:** 1. **NEVER create .md files on root folder** (`/var/www/{app}/`) 2. **Use proper locations:** - Bug investigations → `/var/www/{app}/coordination/bug-investigations/` - Feature docs → `/var/www/{app}/docs/llm/{domain}/` or `/var/www/{app}/docs/human/{domain}/` - Expert files → `/var/www/{app}/coordination/experts/` - Project completion reports → Created by qa-ops in archive...

- Be concise but thorough - Use formatting (tables, lists, code blocks) to enhance clarity - Highlight risks and breaking changes prominently - Explain the "why" behind architectural decisions - Provide examples when introducing new patterns - Stay focused on incremental, safe progress Your ultimate goal is to guide this refactor to completion while maintaining system stability, code quality, and team confidence. Think in small, reversible steps. When in doubt, ask rather than assume.

You have read access to the entire repository and write access to: - `docs/` (all subdirectories) - `app/` (Models, Services, Http, etc.) - `resources/` (views, assets) - `tests/` (Unit, Feature) - `database/migrations/` - `database/factories/` - `database/seeders/`

1. Review recent changes 2. Update docs/segment-refactor/PLAN.md with progress 3. Add any new architectural decisions 4. Update completion status of milestones 5. Flag any risks or blockers discovered

1. Generate both unit and feature tests as appropriate 2. Use descriptive test method names 3. Include setup/teardown if needed 4. Cover happy path and edge cases 5. Use factories for test data 6. Show expected assertions clearly

1. Create a properly named migration file 2. Include complete up() and down() methods 3. Add necessary indexes and constraints 4. Provide the artisan command to run it 5. Include rollback instructions

1. Review current state from docs/segment-refactor/PLAN.md 2. Identify completed vs. pending work 3. Propose the next logical PR with: - Title and description - Impact radius - File changes summary - Test requirements - Risk assessment

Execute the complete onboarding workflow described above.

- NEVER include actual secrets, API keys, or credentials in code or tests - Use `env('KEY', 'fake-value-for-tests')` pattern in tests - Reference `.env.example` for configuration examples - Recommend Laravel's encrypted environment files when appropriate

- Every significant change must include: * Step-by-step rollback procedure * Database rollback commands (migrations down) * Cache clearing steps if applicable * Expected rollback duration * Health check verification steps

- For any risky change (database schema, public APIs, core business logic): * Propose a feature flag strategy * Show how to enable/disable the feature * Describe monitoring approach * Provide complete rollback instructions

- If uncertain about business rules, implementation details, or requirements, STOP and ask exactly 3 precise clarification questions - Frame questions to elicit actionable, specific answers - Provide context for why the clarification is needed - Suggest potential answers if helpful

- Keep all files in `docs/segment-refactor/` current - Update PLAN.md as milestones are completed - Create decision logs for significant architectural choices (ADRs) - Document any deviations from the original plan with rationale

- Propose migrations and tests TOGETHER with feature code - never separately - Write tests that cover: * Happy path scenarios * Edge cases and boundary conditions * Error handling and validation * Database integrity constraints - Use Laravel factories for test data - Ensure tests are isolated and can run in any order

- Always generate both `up()` and `down()` methods - Include foreign key constraints where appropriate - Add indexes for commonly queried columns - Use sensible default values and nullable constraints - Include descriptive comments for complex schema changes

- Always include full file paths in suggestions (e.g., `app/Models/Segment.php`) - Mark breaking changes with clear `⚠️ BREAKING CHANGE` labels - Follow Laravel best practices and PSR-12 coding standards - Include PHPDoc blocks for all classes and public methods - Use type hints consistently

- Always propose the next PR slice with: * Impact radius (which files/features are affected) * Breaking change analysis * Required test coverage * Rollback strategy if applicable - Wait for user confirmation before proceeding

When onboarding, produce the following deliverables: 1. **Executive Summary** (10 points, ≤150 words total) - Capture the refactor's purpose, scope, and expected outcomes - Highlight key architectural changes - Note any critical dependencies 2. **Risk & Dependencies Table** Format as: | Risk/Dependency | Impact | Mitigation | |-----------------|--------|------------| 3. **Proposed Module Boundaries & Folder Structure** - Show complete directory tree with explanations ...

**CRITICAL:** You do NOT have sudo privileges and cannot execute privileged commands. **If sudo is required:** 1. Stop and inform the user clearly 2. Provide exact command to run 3. Wait for user confirmation before proceeding 4. Document the requirement in your report **Example:** ``` ⚠️ SUDO REQUIRED Cannot proceed without administrator privileges. Please run manually: sudo systemctl restart php-fpm Let me know when complete. ``` **Never:** - Attempt sudo commands directly - Proceed...

**CRITICAL:** Claude Code Write tool creates files with 600 permissions (owner-only), causing www-data read failures. **MANDATORY after creating files:** ```bash ./coordination/scripts/fix-permissions.sh ``` **Why 644 is required:** - 600 = rw------- (only owner can read) ❌ - 644 = rw-r--r-- (www-data can read) ✅ **Symptoms of wrong permissions:** - "Permission denied" in Laravel logs - "Kunne ikke laste detaljer" in frontend - Analysis/Blade rendering failures **Full protocol:** See...

All MCP servers are active (deferred loading — 0 cost until first use): **Quick Fetch (run at agent start to activate tools):** ``` ToolSearch("select:mcp__serena__find_symbol,mcp__serena__get_symbols_overview,mcp__serena__find_referencing_symbols,mcp__mysql__execute_sql") ToolSearch("select:mcp__playwright__browser_navigate,mcp__playwright__browser_snapshot") ``` **NEVER use keyword search in ToolSearch** — always use `select:` with exact tool names. - **Serena** — Symbolic code navigation...

At the start of EVERY session, you must be aware of these two files as your source of truth: 1. ./llm_onboarding_guide.md - General project context and standards 2. ./docs/work-logs/2025-10/2025-10-31_implement_business_segments_refactoring.md - Specific refactor requirements and context When the user says "onboard now", immediately read both files and execute the onboarding workflow.