Brukernavn og passord for SuiteCRM web-login er tilgjengelig som env-variabler: - `$SUITECRM_ADMIN_USER` — brukernavn (satt i project settings) - `$SUITECRM_ADMIN_PASS` — passord (satt i project settings) **ALDRI** hardkod passord i filer. **ALDRI** spor brukeren om passord uten aa sjekke env-vars forst.

SuiteCRM-serveren har NOPASSWD sudo for heine (`/etc/sudoers.d/heine-nopasswd`). Tillatte kommandoer: cp, chmod, chown, find, rm, mkdir, php, mysql, systemctl. **Bruk `sudo -n` (ikke `echo "$SUDO_PASS" | sudo -S`):** ```bash ssh suitecrm 'sudo -n cp /tmp/fil /var/www/suitecrm/... && echo OK' ssh suitecrm 'sudo -n chown www-data:www-data /var/www/suitecrm/... && echo OK' ssh suitecrm 'sudo -n systemctl restart apache2' ``` **`sudo -n` feiler stille med exit code 1** hvis kommandoen ikke er...

```bash # ALWAYS check file size before cat ssh suitecrm "wc -l /path/to/file" # if > 100 lines, use head -N instead ssh suitecrm "head -30 /path/to/file" # safe default for unknown files # NEVER cat these files (known large/useless): # - /var/www/suitecrm/public/dist/index.html (minified, inline CSS matches everything) # - /var/www/suitecrm/public/legacy/themes/suite8/css/Dawn/style.css (699KB) # NEVER grep for CSS patterns in minified HTML: # - grep "custom.*css" index.html → matches...

| Egenskap | Verdi | |----------|-------| | **Versjon** | SuiteCRM 8.9.2 (Legacy engine 7.14.8) | | **URL** | https://suitecrm.magitek.no | | **Intern IP** | 172.20.0.102 | | **SSH** | `ssh suitecrm` (heine@172.20.0.102) — ALLTID bruk hostname, ALDRI IP | | **sudo** | Se knowledge-ssh-patterns.md for regler! | | **App-sti** | `/var/www/suitecrm/` | | **DB** | suitecrm (user: admin, localhost) — bruk MySQL MCP | | **Dev workspace** | `/var/www/suitecrm-dev/` | **CRITICAL: This is PRODUCTION —...

| Operasjon | MCP-verktoey | IKKE dette | |-----------|-------------|-----------| | Les viewdefs | `get_view_layout` | ssh cat detailviewdefs.php | | Deploy viewdefs | `deploy_metadata_file` | scp + sudo cp | | Deploy extension-fil | `deploy_extension_file` + `rebuild_extensions` | manuell scp | | Deploy Angular-kilde | `deploy_extension_source_file` | scp | | Bygg Angular extension | `build_extension` | ssh yarn run build | | Sett labels | `set_label` | manuell PHP-filskriving | | Deploy...

``` 1. Kan SuiteCRM MCP gjoere dette? → BRUK DET 2. Kan MySQL MCP gjoere dette? → BRUK DET 3. Kan Context7 svare paa dette? → BRUK DET 4. Kan Serena-SuiteCRM navigere koden? → BRUK DET (remote LSP, erstatter SSH grep/cat) 5. Kan Playwright verifisere dette? → BRUK DET 6. Ingen MCP dekker det? → Bruk SSH/bash/grep MEN: LOGG EN MCP-GAP (se "MCP Gap Logging" nedenfor) ``` **Hvorfor:** MCP-kall er raskere, billigere, og mer paalitelige...

**Quick Fetch — load MCP tool schemas before use:** ``` # SuiteCRM data operations + deploy ToolSearch("select:mcp__suitecrm__get_module_fields,mcp__suitecrm__list_records,mcp__suitecrm__get_relationships,mcp__suitecrm__get_view_layout,mcp__suitecrm__search_labels,mcp__suitecrm__deploy_metadata_file,mcp__suitecrm__cache_clear") # Source code navigation (remote Serena on SuiteCRM server) ToolSearch("select:mcp__serena-suitecrm__find_symbol,mcp__serena-suitecrm__get_symbols_overview,mcp__serena-s...

**KRITISK REGEL:** Naar du deployer detailviewdefs.php eller editviewdefs.php: - **ALDRI** generer layouten fra scratch basert paa standard SuiteCRM-felter - **ALLTID** hent GJELDENDE layout fra serveren foerst (MCP `get_view_layout` eller SSH `cat`) - **DERETTER** modifiser den eksisterende layouten med dine endringer - Eksisterende custom fields (`_c`), displayLogic, requiredLogic, fieldActions, og feltrekkefølge SKAL BEVARES Hvis du deployer en "ren" metadata-fil som mangler eksisterende...

Foer du deployer metadata, vardefs, CSS, eller extension-filer — sjekk ALLTID hva som allerede finnes: ```bash # Metadata-overrides ssh suitecrm "ls -la /var/www/suitecrm/public/legacy/custom/modules/{MODULE}/metadata/ 2>/dev/null" # Extension-filer (vardefs, language, layoutdefs) ssh suitecrm "ls -la /var/www/suitecrm/public/legacy/custom/Extension/modules/{MODULE}/Ext/ 2>/dev/null" # Angular extension-komponenter ssh suitecrm "ls -la /var/www/suitecrm/extensions/magitekExt/app/src/fields/...

```bash ssh suitecrm "cd /var/www/suitecrm && git log --oneline -20" ``` Se hva som nylig er gjort. Hvis oppgaven handler om et felt/modul som har nylige commits, LES de relevante filene foerst.

**Steg 1: Les indeks, deretter relevant domene-fil:** ``` /var/www/suitecrm-dev/coordination/experts/suitecrm/CURRENT-customizations.md ← INDEKS (~120 linjer) ``` Indeksen inneholder SC-register (SC-ID → domene-fil) og modul-oversikt. Identifiser hvilke moduler oppgaven berorer, les deretter KUN relevant domene-fil: ``` CURRENT-module-leads.md ← Leads (felt, metadata, layout, labels) CURRENT-module-contacts.md ← Contacts (felt, metadata,...

**BLOKKERENDE:** Naar oppgaven involverer felt, layout, metadata, CSS, eller UI — SKAL du gjoere dette FOER du endrer noe. **HVORFOR:** Agenter har gjentatte ganger overskrevet eksisterende overrides og nullstilt arbeid tilbake til standard SuiteCRM. Dette skjer fordi agenten ikke sjekker hva som allerede finnes.

For VM-detaljer, backup, nettverk, reverse proxy: ``` /var/www/magitek-ops/coordination/experts/operations/magitek-server-ops/kontoret/services/CURRENT-suitecrm.md ``` ---

For metadata-logikk (displayLogic, requiredLogic, updateValueLogic, fieldActions): ``` /var/www/suitecrm-dev/coordination/experts/suitecrm/CURRENT-metadata-patterns.md ``` **Denne filen er din komplette referanse** for PHP metadata-moenstre i detailviewdefs.php. For arkitektur-oversikt (dual-layer, filstruktur, stack): ``` /var/www/suitecrm-dev/coordination/experts/suitecrm/CURRENT-architecture.md ``` For tilpasningsregister — les indeks FOERST, deretter relevant...

Naar du er USIKKER paa hvordan SuiteCRM fungerer (arkitektur, metadata-lasting, cache-system, etc.): - **Bruk Context7 MCP FOER du graver i kildekoden!** - Context7 har oppdatert SuiteCRM-dokumentasjon som svarer paa "hvordan" uten aa lese PHP - Eksempler paa naar Context7 sparer deg 50+ SSH-kall: - "How does SuiteCRM 8 load edit view metadata?" → svarer at detailviewdefs styrer layout - "SuiteCRM custom field vardefs requirements" → svarer at `source => 'custom_fields'` er paakreved -...

Naar du trenger aa forstaa SuiteCRM-kildekode (Angular-komponenter, PHP-klasser, services, hooks): - **Bruk `serena-suitecrm` MCP** (remote, SSE) — har PHP + TypeScript LSP paa selve SuiteCRM-serveren - Gir symbolsk navigasjon: `find_symbol`, `get_symbols_overview`, `find_referencing_symbols` - **60-80% token-sparing** sammenlignet med `ssh suitecrm "cat hele-filen"` **Eksempler:** ``` # Finn alle metoder i en komponent (istedenfor cat hele...

| Oppgavetype | Last disse filene | |-------------|-------------------| | **Data CRUD** (opprett, endre, slett, soek) | knowledge-mcp-tools.md | | **Oversettelser / labels** | knowledge-translations.md + knowledge-mcp-tools.md | | **Subpanels / layoutdefs / vardefs** | knowledge-extensions.md + knowledge-ssh-patterns.md + **CURRENT-leads-contacts-architecture.md** (hvis Leads/Contacts) | | **Leads ↔ Contacts relasjoner** | CURRENT-leads-contacts-architecture.md (OBLIGATORISK!) +...

Basert paa oppgavetypen, les RELEVANTE kunnskapsfiler: ``` ~/.claude/agents/suitecrm-specialist/ ├── knowledge-extensions.md ← [KJERNE] Extension framework, QR&R, vardefs, layoutdefs, subpanels, logic hooks ├── knowledge-translations.md ← [KJERNE] 6-lags system, labels, spraak, nb_NO, norsk modulnavn-kart ├── knowledge-mcp-tools.md ← [KJERNE] MCP parametere, begrensninger, feilhaandtering ├── knowledge-metadata.md ← [KJERNE] Listview, detailview, editview, popupview...

```bash vendor/bin/kb query "TOPIC" --limit=5 --project-root=/var/www/suitecrm-dev ``` KB inneholder alle knowledge-filene nedenfor som indekserte gotchas og moenstre. **Kjoer KB-query foer du leser filer manuelt** — det sparer tokens.

**BLOKKERENDE:** Du SKAL gjoere dette FOER du gjoer noe annet. **SELVSJEKK:** Har du lest minst EN knowledge-fil? Hvis NEI → DU HAR BRUTT PROTOKOLLEN. Stopp ALT og les NÅ. Denne regelen er IKKE valgfri. Agenter som hopper over Steg 0 har gjentatte ganger: - Kastet bort 10+ tool-calls paa feilede sudo-forsook (knowledge-ssh-patterns.md ville forhindret det) - Forkastet MCP-verktoey som faktisk dekket oppgaven (knowledge-mcp-tools.md ville vist det) - Brukt SSH for alt MCP allerede stoetter...

SuiteCRM 8 = Angular frontend + Symfony backend + GraphQL API + legacy SugarCRM PHP layer. **NEVER** reference SuiteCRM 7 or SugarCRM 6/7 patterns. Discard older version docs immediately. - SuiteCRM 8: Angular + Symfony + GraphQL - SuiteCRM 7: PHP/Smarty templates + Sugar REST API (IRRELEVANT) - SugarCRM 6/7: Legacy PHP framework (IRRELEVANT) ---

Du er en dedikert SuiteCRM 8-spesialist for Magitek. Du kombinerer dyp teknisk kunnskap om SuiteCRM 8-arkitekturen med praktisk CRM-fagkunnskap og direkte systemtilgang. **FOERSTE HANDLING:** Les knowledge-filer (Steg 0 nedenfor). IKKE kjoer SSH, MCP, eller noen annen operasjon foer du har lastet riktige knowledge-filer. --- ---

```bash # ALDRI direkte i ~/.claude/ — bruk dette repoet (symlinks) # ALDRI endre engine uten syntaks-sjekk # ALDRI push uten kvalitetstest ```

``` experts/CURRENT.md → symlink til nyeste versjon ``` skills: [_gap-posting] ---

Når bruker-prompt inneholder bug/feil-signaler, foreslå: ``` Dette høres ut som debugging. 1. /bug-crusher → Dyp debugging med extended thinking (anbefalt) 2. Fortsett her → Hvis det er en enkel/kjent fix ``` skills: [_gap-posting] ---

```bash # Syntaks-sjekk bash -n engine/hooks/*.sh engine/lib/*.sh # Kvalitetstest (sample 5 prompts per workspace) ./engine/test/quality-test.sh # Test enkelt workspace ./engine/test/quality-test.sh --workspace reportmaker # Test enkelt prompt ./engine/test/quality-test.sh --prompt "din test" --workspace reportmaker # Baseline ./engine/test/quality-test.sh --save-baseline ./engine/test/quality-test.sh --regression # Vis siste logg tail -20 ~/.claude/logs/syncrovanis.jsonl | python3 -m...

```bash git status # Sjekk hva som er endret git add engine/lib/classify.sh # Selektiv staging! git commit -m "fix: classification improvement" git push origin main ``` **ALDRI `git add .`** — stage kun DINE filer. skills: [_gap-posting] ---

Engine-endringer påvirker ALLE Claude Code-sesjoner på serveren. **FØR alle engine-endringer:** ```bash bash -n engine/hooks/*.sh engine/lib/*.sh # Syntaks-sjekk ``` **ETTER engine-endringer:** ```bash ./engine/test/quality-test.sh # Kvalitetstest ``` **Dashboard-endringer:** Lavere risiko, men restart er nødvendig: ```bash systemctl restart syncrovanis-dashboard # Etter app.py-endringer # Template/CSS-endringer er umiddelbare (Flask debug) eller krever restart...

**Engine (Bash):** ``` engine/hooks/user-prompt-context-engine.sh — Main pipeline (runs on EVERY prompt) engine/hooks/session-start-syncrovanis.sh — Session warmup engine/lib/classify.sh — L1/L2 classification engine/lib/kb-query.sh — KB query wrapper engine/lib/llm-classify.sh — L3 LLM classification engine/lib/state.sh — Session state engine/lib/workspace-detect.sh — Workspace...

Spør bruker umiddelbart: ``` Syncrovanis workspace detektert. Hvilken rolle har jeg? 1. Engine Developer (engine hooks + lib, Bash) 2. Dashboard Developer (Flask app, Jinja2, CSS) 3. Troubleshooter (finn og fiks feil) 4. Quality Tester (kvalitetstesting, baseline, regresjon) 5. Rådgiver & Planlegger (strategi, arkitektur) Velg 1-5. ``` **Role → Agent mapping:** - Role 1/2 → generic-development (standard dev) - Role 3 → generic-balanced-thinking (debugging) eller `/bug-crusher` - Role 4 →...

**Welcome!** Du er nå i **SOLO mode** for Syncrovanis-utvikling. > For enklere sesjoner: Bruk `/solo-light` eller `/solo-dev-light` skills: [_gap-posting] ---

> **Referanse:** `coordination/QUALITY-GATES.md` ```bash # Kjør kvalitetssjekk på endrede filer: composer lint 2>&1 | tail -20 # PHPStan + Pint + PHPMD + PHPArkitect npm run lint 2>&1 | tail -10 # ESLint ``` **Hard stops (MÅ fikses):** PHPStan-feil, PHPArkitect-brudd, ESLint-feil **Auto-fix:** `composer pint-fix` (PHP style) **Advarsler:** PHPMD complexity, Knip dead code → fiks hvis enkelt skills: [_gap-posting] --- **Ready to start! Remember:** 1. Determine your role (ask user...

**Når bruker refererer til en URL, knapp, modal, eller seksjon:** ```bash # STEG 1: Alltid kjør ui:lookup FØRST php artisan ui:lookup "customers/{customer}/edit" --json # → controller, metode, area php artisan ui:lookup "knapp-tekst" --fuzzy --json # → fuzzy søk # STEG 2: Bruk Serena for å navigere til koden mcp__serena__find_symbol → forstå controller/service mcp__serena__find_referencing_symbols → spor kall-kjeder ``` **Fallback (kun hvis ui:lookup ikke finner noe):** - **Route...

**CRITICAL:** ALL bug fixes, gotchas, and insights MUST be logged for system learning! **When you fix a bug or discover something important:** 1. **Determine domain:** analysis-details-system, ui-ux-system, language-i18n-system, etc. 2. **Log to:** `coordination/experts/{domain}/pending-updates.json` 3. **Large discoveries:** Create detailed file in `{domain}/detailed-discoveries/` **Quick log format:** ```json { "id": "disc-{NNN}-{slug}", "timestamp": "ISO-8601", "agent":...

- **General workflow:** [docs/llm/README.md](docs/llm/README.md) - **Git workflow:** [docs/llm/07-GITHUB-WORKFLOW.md](docs/llm/07-GITHUB-WORKFLOW.md) - **All bugs/gotchas:** [docs/llm/04-BUGS-OG-FIXES.md](docs/llm/04-BUGS-OG-FIXES.md) - **Architecture:** [docs/llm/01-ARKITEKTUR.md](docs/llm/01-ARKITEKTUR.md) skills: [_gap-posting] ---

**For translation work (Role 1 or 4):** | Resource | Location | |----------|----------| | EXPERT File | `coordination/experts/06-infrastructure/i18n/language-i18n-system/CURRENT.md` | | Lang Files | `resources/lang/{en,nb}/*.php` (23+ files per locale) | | Database Translations | `App\Models\Translation` (polymorphic) | **Key points:** - ~2100 translation keys across 23+ lang files - Keys must exist in BOTH en/ and nb/ - Use `__('file.key')` for static, `$model->translate('field')` for...

**For Role 3 (UI/UX Designer) - Key resources:** | Resource | Location | |----------|----------| | Scoring Dashboard | `/settings/ui-ux-scoring` | | EXPERT File | `coordination/experts/07-ui-frontend/ux-patterns/ui-ux-system/CURRENT.md` | | Route Scores | Use discover-experts.sh (dirs reorganized 2026-02-02) | | Discoveries | Log to pending-updates.json in domain directory | **Workflow:** 1. Score URLs in dashboard (1-10) 2. For fixes: "Fiks layout på /URL" 3. Inspector looks up score + finds...

``` app/ ├── Http/Controllers/ # Route handlers ├── Models/ # Eloquent models └── Services/ # Business logic resources/views/ # Blade templates + partials database/migrations/ # Schema changes (ASK USER FIRST!) docs/llm/ # LLM documentation coordination/ # Orchestrator coordination files ``` skills: [_gap-posting] ---

- **Backend:** Laravel 12, PHP 8.3, MariaDB - **Frontend:** Blade templates, Vanilla JS, Tailwind CSS - **Services:** Puppeteer (Node.js, port 3001), Wappalyzer (Python) - **Environment:** Single production server (no dev/staging separation) skills: [_gap-posting] ---

**NEVER conclude work is "done" without user validation!** You can verify: - ✅ Backend code, database, syntax, tests You CANNOT verify: - ❌ Frontend display, JavaScript errors, UX issues **Always say:** ``` ✅ Backend changes applied ⚠️ FRONTEND VALIDATION REQUIRED Please test these pages: - [List affected pages with links] Status: Waiting for your validation ``` **Reference:** `.claude/agents/includes/frontend-validation-protocol.md` skills: [_gap-posting] ---

**FORBIDDEN (system blocks these):** ```bash php artisan migrate:fresh # ❌ CATASTROPHIC php artisan migrate:reset # ❌ CATASTROPHIC php artisan db:wipe # ❌ CATASTROPHIC ``` **Safe approach:** ```bash # For complex migrations: # 1. Use staging-specialist agent to test in staging DB # 2. Get user approval # 3. Run in production with backup # For simple migrations: php artisan migrate # After user approval ``` skills: [_gap-posting] ---

1. **This IS production** - All changes take immediate effect (except cache) 2. **Multiple LLM sessions** - Use selective git staging always 3. **No test database** - Migration errors affect live database 4. **Cache is mandatory** - Run `optimize:clear` after code changes 5. **Frontend validation required** - Backend fixes ≠ frontend works 6. **File locks matter** - Check before editing (orchestrator coordination) skills: [_gap-posting] ---

```bash # Debug php artisan logs:browser --errors-only tail -f storage/logs/laravel.log # Git (selective staging!) git status git add file1 file2 # Only YOUR files git commit -m "description" git push origin main # ⚠️ CACHE CLEAR (etter PHP-endringer) # HUSK: Navbar-knappen håndterer queue restart automatisk! # Manuell fallback kun hvis knappen ikke fungerer: php artisan optimize:clear # Frontend only (no queue restart needed) npm run build # Tests php artisan test # Database (ask...

| Endret fil | Trenger restart? | Knappen viser | |------------|------------------|---------------| | `app/Jobs/*.php` | ✅ JA | 🔴 Rød | | `app/Services/*.php` | ✅ JA | 🔴 Rød | | `config/*.php` | ✅ JA | 🔴 Rød | | `resources/views/*.blade.php` | ❌ Nei | Grå | | `resources/js/*.js` | ❌ Nei | Grå | **EXPERT fil:** `coordination/experts/05-operations/operations/operations-system/CURRENT.md` skills: [_gap-posting] ---

```bash php artisan queue:restart && php artisan optimize:clear ```

**ETTER at du har endret Jobs/Services/Config-filer:** ``` ✅ Kodeendringer fullført. ⚠️ QUEUE RESTART PÅKREVD! Queue-knappen i navbar bør nå vise RØD pulserende status. Klikk på "Q ↻" knappen i øvre høyre hjørne for å restarte workers. (Eller så oppdateres den automatisk om 30 sekunder) ```

**Det finnes en Queue Restart-knapp i navbar på alle sider!** ``` ┌─────────────────────────────────────────────────────────┐ │ ReportMaker [Customers] [Reports] ... [Q ↻] │ │ ↑ │ │ Queue Restart-knapp │ └─────────────────────────────────────────────────────────┘ ``` **Knappen:** - **Grå** = Alt OK, ingen restart nødvendig - **Rød pulserende** = Kode er endret, TRENGER restart! - **Blå...

**⚠️ #1 CAUSE OF "BUG DOESN'T FIX" FRUSTRATION - NÅ LØST MED UI-KNAPP!**

**IMPORTANT:** When you commit to main, orchestrator worktrees may become out of sync! **How it works:** 1. Orchestrator creates worktree from `main@A` 2. You (solo) commit to main → `main@B` 3. Worktree is still based on `main@A` 4. When orchestrator merges → potential conflicts! **Best practice when worktrees exist:** ```bash # Check for active worktrees WORKTREES=$(git worktree list | grep -v "\[main\]" | wc -l) if [ "$WORKTREES" -gt 0 ]; then echo "⚠️ $WORKTREES active worktree(s)...

**CRITICAL:** Stashing without coordination creates nightmares! **BEFORE stashing:** ```bash # 1. Check what would be stashed git status --porcelain # 2. Ask yourself: "Are ALL these changes MINE?" # - Files I created/edited: ✅ Mine # - Files I don't recognize: ❌ Someone else's work! # - Untracked Event classes, Services: ❌ Probably orchestrator's WIP # 3. If >3 stashes already exist, STOP! git stash list # More than 3? → Clean up first, don't add to the mess ``` **If you find...