NEVER write passwords in masterplan files, CONTEXT.md, tasks, or any file that gets committed to git. ---

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) ---

Structured implementation of SuiteCRM masterplans with remote deploy, progress tracking, and completion reports. --- ---

``` ✅ All tasks implemented (or partial with reason) ✅ Review-fixes incorporated (K-XXX) ✅ Acceptance criteria verified ✅ Script syntax checked (bash -n / python3 check) ✅ Selective commits (per task, with MP-reference) ✅ Completion report saved ✅ Discoveries logged (if relevant) ✅ Git push confirmed 📊 NEXT: /audit-masterplan ``` --- **Ready.** Provide masterplan file (MP-number or filename) to start.

``` ❌ Improvise beyond masterplan - follow the plan! ❌ Skip review-fixes - incorporate K-XXX! ❌ Forget TodoWrite - track ALL tasks! ❌ Batch commits - commit per task! ❌ Say "done" without completion report! ❌ Use git add . (selective staging!) ❌ Run destructive remote commands without approval ❌ Assume PHP/Laravel commands work here (they don't) ``` ---

```bash ./coordination/scripts/fix-permissions.sh 2>/dev/null || true git add coordination/masterplans/active/MP-{NNNN}-{YYMMDD}-{feature}/COMPLETION.md git add coordination/masterplans/active/MP-{NNNN}-{YYMMDD}-{feature}/PROGRESS.md git commit -m "completion: MP-{NNNN} {feature} implementation report" git push origin main ``` ---

**Save:** ``` coordination/masterplans/active/MP-{NNNN}-{YYMMDD}-{feature}/COMPLETION.md ``` Include: Task status table, review fixes incorporated, acceptance criteria, files changed/created, discoveries logged, next steps.

**After all tasks, go through EACH acceptance criterion:** ``` Acceptance criteria from MP-{NNNN}: - [ ] Criterion 1 → Verified: {how} - [ ] Criterion 2 → Verified: {how} - [ ] Criterion 3 → ⚠️ Requires remote access → user must verify ``` **Ops-specific verification:** ```bash # Script syntax check bash -n {script.sh} # Expert file symlink check file coordination/experts/{domain}/CURRENT.md # Coordination file valid JSON python3 -c "import json; json.load(open('{file}.json'))" # Git...

**When user provides "Resume: MP-{NNNN}-HANDOFF.md":** ``` 1. Check for PROGRESS.md first (fastest path) 2. If PROGRESS.md exists: read it (< 40 lines), skip to remaining tasks 3. If no PROGRESS.md: read HANDOFF.md instead 4. Read MASTERPLAN.md (Level 1: Task Index) — ~50-80 lines 5. Read CONTEXT.md (Level 2: Shared Context) — ~80-150 lines 6. For next task: Read tasks/TASK-{NNN}.md ``` **CRITICAL: Resume should use < 5% of context before work starts!** ---

**When user requests "handoff" or context is low:** **Write immediately:** ``` coordination/masterplans/active/MP-{NNNN}-{YYMMDD}-{feature}/HANDOFF.md ``` Format: Completed tasks (commit hash + 1 line), resume task, key context (max 5-8 bullets), remaining tasks. Keep < 80 lines. **Then show user:** ``` --- HANDOFF READY Paste this in new chat: /implement-masterplan Resume: coordination/masterplans/active/MP-{NNNN}-{YYMMDD}-{feature}/HANDOFF.md --- ``` ---

A) **Revert commit:** `git revert {hash}` — undo scope creep, re-implement correctly B) **Accept pre-emption:** Mark affected future tasks as DONE in PROGRESS.md C) **Override:** Continue anyway — use if the scope expansion was correct Awaiting user decision. ``` 2. **Update PROGRESS.md:** Set Scope column to `L2-BLOCK` for this task 3. **STOP implementation.** Do NOT proceed to the next task. 4. **Report to user:** Show the SCOPE-BLOCK.md content and ask which option to take. ---

{list with L2's MISSING_JUDGEMENT}

{list with L2's EXTRA_JUDGEMENT}

**Runs automatically after step 9 (commit), before step 12 (PROGRESS.md update).** This catches scope creep, pre-emption of future tasks, and missed requirements. #### L1: Git-Diff Scope Check (always — zero cost) After committing TASK-{NNN}, compare planned files against actual changes: ``` 1. EXTRACT planned files from TASK-{NNN}.md: Read the task file's ## Files section. Two formats exist: Format A (newer): ## Files - **Create:** `path/to/file.py` (~N lines, description) ...

**Next task:** TASK-{NNN} **Expert file:** {path if loaded} **Review fixes remaining:** {K-XXX list or "none"} ``` **Rules:** Write after EVERY completed task, overwrite each time, keep < 50 lines. Scope values: MATCH, WARN, ANOMALY, L2-PASS, L2-BLOCK, SKIP, - (not done). **⚠️ IMPORTANT: Implement what the plan says - DO NOT improvise!** **Commit format:** ```bash git commit -m "$(cat <<'EOF' feat(MP-{NNNN}): TASK-{NNN} - {short title} - {change 1} - {change 2} - Review fix K-{NNN}...

| Task | Title | Status | Commit | Scope | |------|-------|--------|--------|-------| | TASK-001 | {title} | DONE | {short hash} | MATCH | | TASK-002 | {title} | IN_PROGRESS | - | - |

**File:** `coordination/masterplans/active/MP-{NNNN}-{YYMMDD}-{feature}/PROGRESS.md` ```markdown # Progress: MP-{NNNN} **Updated:** {ISO timestamp} **Agent:** implement-masterplan-ops

**For EACH task in masterplan:** ``` 1. MARK as in_progress in TodoWrite 2. Read this task's file: {MP directory}/tasks/TASK-NNN.md 3. Check dependencies (are previous tasks complete?) 4. CHECK if any files already have uncommitted changes (others' work?) 5. Implement according to masterplan specifications 6. Incorporate any review-fixes (K-XXX) for this task 7. Syntax check (if scripts): bash -n {script} or python3 -c "import ast; ast.parse(open('{file}').read())" 8. Selective commit: git add...

Auto-generate TodoWrite from masterplan's tasks + acceptance criteria. ---

**Parse masterplan's execution mode:** #### SOLO SEQUENTIAL (standard) ✅ → Implement all tasks in sequence in this chat #### SOLO PARALLEL → Ask user: "Which tasks should THIS chat handle?" #### ORCHESTRATED → Redirect with clear message: ``` 🚨 This masterplan requires ORCHESTRATED execution with worktrees. Run /orchestrate instead. ``` → STOP ---

**Identify affected domains from masterplan:** ```bash ./coordination/scripts/discover-experts.sh --list 2>/dev/null || ls coordination/experts/ ``` **Read relevant CURRENT.md expert file(s):** ``` coordination/experts/{category}/{domain}/CURRENT.md ``` ---

```bash ls coordination/masterplans/active/MP-{NNNN}-*/REVIEW*.md 2>/dev/null ``` **IF review exists:** → Incorporate ALL critical findings (K-XXX) into implementation → Incorporate warnings (A-XXX) where possible → Log incorporated fixes in completion report **IF review NOT found:** ``` ⚠️ No review found for MP-{NNNN}. Recommendation: Run /review-masterplan first for quality assurance. Do you want to continue without review, or review first? ``` ---

**WAIT for user to provide masterplan file. DO NOT search or list masterplans yourself!** User will provide filename or MP-number. When you have it, locate the MP directory: ```bash ls coordination/masterplans/active/MP-{NNNN}-*/ ``` #### App Masterplan Detection (MANDATORY after reading CONTEXT.md) **After reading the masterplan, check the Deployment Target in CONTEXT.md.** If the deployment target is `/var/www/{something}/` where `{something}` is NOT `magitek-ops`: ``` ⚠️ APP MASTERPLAN...

``` ✅ Completion reports → coordination/masterplans/active/ ❌ NEVER write files directly to coordination/ root ``` ---

``` ❌ Destructive remote commands without explicit user approval ✅ Read-only checks: qm list, pct list, ping, df -h, systemctl status ```

``` Changed shell script → chmod +x {script} Changed coordination/ → git add + commit + push Changed expert files → git add + commit + push SSH to remote server → verify with read-only command first ```

```bash # BEFORE stash: git status --porcelain - are ALL changes MINE? # ❌ NEVER stash without checking # ✅ git stash push -m "implement-mp: {MP-number} - {date}" ```

```bash git add file1 file2 # ✅ Only YOUR files git add . # ❌ NEVER! Stages others' work! ```

``` ⚠️ FACTS: - Hjemme (192.168.86.x) = PRODUCTION (live websites, Nextcloud, storage) - Kontoret (172.20.0.x) = primarily development - Multiple LLM sessions may work SIMULTANEOUSLY ❌ NEVER: qm destroy, pct destroy, zfs destroy, rm -rf on remote servers ✅ ALLOWED: Config changes, script creation, expert file updates, coordination files ``` ---

This is **magitek-ops** — an infrastructure operations workspace, NOT an application. **What exists here:** - Bash scripts, coordination files, expert knowledge files - SSH operations, Proxmox management, networking config - Markdown documentation, YAML, JSON coordination files **What does NOT exist here:** - No PHP/Laravel/artisan commands - No npm/Vite/frontend build - No Blade templates or CSS frameworks - No queue workers - No application database **Infrastructure server context:** - SSH...