```bash # 1. Write locally to /tmp/ # 2. scp /tmp/file suitecrm:/tmp/ # 3. ssh suitecrm 'echo "$SUDO_PASS" | sudo -S cp /tmp/file /target && sudo -S chown www-data:www-data /target' # 4. QR&R: ssh suitecrm 'echo "$SUDO_PASS" | sudo -S -u www-data php /var/www/suitecrm/scripts/rebuild_extensions.php 2>/dev/null' # 5. Git: ssh suitecrm "cd /var/www/suitecrm && git add -A && git commit -m 'description' && git push" ```

**MCP (use first):** suitecrm, context7, playwright **SSH:** `ssh suitecrm "command"` (172.20.0.102) **Expert files:** `coordination/experts/suitecrm/CURRENT-*.md` **Knowledge:** `~/.claude/agents/suitecrm-specialist/knowledge-*.md`

1. **Understand** — Read expert files if needed, check customization registry 2. **Plan briefly** — State what you'll change and why (2-3 sentences, not a masterplan) 3. **Implement** — Write files, deploy to remote, run QR&R/cache:clear 4. **Verify** — Use MCP + SSH to confirm changes work 5. **Document** — Update customization registry with SC-NNNN entry 6. **Commit** — Git commit on both remote server and this workspace

**IKKE** begynn å jobbe basert på window-tittelen eller konteksten alene. **IKKE** les filer, analyser kode, eller kjør verktøy ennå. Your COMPLETE response must be EXACTLY these two lines (no more, no less, no bullet points): Hva skal jeg gjøre? `[Anbefalt: Sonnet | Effort: medium | Thinking: nei]` --- # Solo Dev Light — SuiteCRM Dev Lean development mode for SuiteCRM 8 customization. No orchestrator, no masterplan overhead. For small, well-defined changes (< 5 files, clear scope).

- DO NOT read `~/.claude/agents/review-masterplan.md` — it's for a different workspace - DO NOT re-verify SSH findings already in the explore report or masterplan - DO NOT run parallel SSH calls that depend on each other - DO NOT cat large files (check wc -l first) - DO NOT grep minified HTML for CSS patterns - DO NOT assume QUALITY-GATES.md or fix-permissions.sh exist (they don't in this workspace) - DO NOT use `serena` (local) for SuiteCRM code — use `serena-suitecrm` (remote LSP) - DO NOT...

After saving REVIEW.md: ```bash git add coordination/masterplans/active/MP-{NNNN}-{slug}/REVIEW.md git commit -m "review: MP-{NNNN} {slug}" git push origin main ``` ---

```bash coordination/masterplans/active/MP-{NNNN}-{slug}/REVIEW.md # If second review: REVIEW-2.md ```

- [ ] Ready as-is - [ ] Needs minor adjustments (warnings) - [ ] Needs significant changes (critical gaps) - [ ] Must be rewritten (fundamental problems) ``` ---

...

...

**Category:** [number] **Problem:** [what's missing] **Consequence:** [what happens if not fixed] **Suggestion:** [concrete solution]

| # | Category | Score | Finding | |---|----------|-------|---------| | 1 | Upgrade Safety | [OK/WARN/MISSING/CRITICAL] | [short description] | | 2 | Cache Strategy | ... | ... | | 3 | SSH/Deploy Patterns | ... | ... | | 4 | SuiteCRM 8 Architecture | ... | ... | | 5 | MCP Usage | ... | ... | | 6 | Deploy Sequence | ... | ... | | 7 | Explore Alignment | ... | ... | | 8 | Task Completeness | ... | ... | | 9 | Vague Formulations | ... | ... | | 10 | Rollback Plan | ... | ... | | 11 | Node.js...

```markdown # Masterplan Review: MP-{NNNN} **Masterplan:** [path] **Reviewed:** [date] **MCP used:** [Yes/No — which tools] **Overall Score:** [A/B/C/D/F]

- No plaintext passwords (e.g., "Ansjos123") in any task, deploy step, or example command? - All sudo uses `$SUDO_PASS`? ---

- If plan requires Angular build: Node.js is NOT on server → plan must address this - Angular extension changes require build step — where/how is this done?

- How to undo if something breaks? - Git revert on remote? Restore from snapshot? - Which operations are reversible?

- "implement appropriate logic" — WHAT specifically? - "handle edge cases" — WHICH edge cases? - "configure as needed" — WHAT configuration?

- Each task has: files to create/modify, deploy steps, verification? - Task dependencies explicit and ordered correctly?

- Does the masterplan address the original prompt? - Are explore report's key findings reflected? - Are explore report's critical constraints respected? - Are there explore findings NOT addressed in the plan?

- Correct order: backend/vardefs → metadata → language → frontend → cache/QR&R → verify - Dependencies between tasks explicit? - Verification steps defined for each task?

- Are MCP tools specified where they could replace SSH? - deploy_metadata_file for viewdefs? - deploy_extension_file for Extension/ files? - rebuild_extensions MCP tool for QR&R?

- No SuiteCRM 7 / SugarCRM patterns (Smarty, old REST API, etc.) - detailviewdefs.php for layout (NOT editviewdefs.php) - Custom fields include `'source' => 'custom_fields'` in vardef - Angular extension requires `yarn run build:{extName}` (if Node.js available — it's NOT on this server!) - `customCode` in viewdefs is IGNORED by Angular frontend

- File writing: 3-step SCP pattern (local tmp → scp → sudo cp)? - NEVER heredoc+sudo over SSH - No hardcoded passwords — always `$SUDO_PASS` - No parallel SSH writes (sequential only)

- All 4 cache layers addressed? 1. Smarty templates: `rm -rf cache/smarty/templates_c/*` 2. Theme cache: `rm -rf cache/themes/suite8/modules/*/` 3. Symfony: `php bin/console cache:clear` 4. Extension compilation: `rebuild_extensions.php` (DIFFERENT from cache:clear!) - Extension file changes MUST use `rebuild_extensions.php`, not just `cache:clear`

- Every file change in `extensions/` or `public/legacy/custom/`? - Any `core/` modifications = IMMEDIATE FAIL - Any `public/legacy/modules/` modifications = IMMEDIATE FAIL

---

Use `get_module_fields` or `get_language_strings` ONLY if the plan claims specific field names or label keys that are NOT already confirmed in the explore report.

```bash ls coordination/explore/ # Read EXPLORE.md from relevant report if it exists ```

```bash ls coordination/masterplans/active/ cat coordination/masterplans/active/MP-{NNNN}-{slug}/MASTERPLAN.md ``` If CONTEXT.md exists, read it too — it contains pre-verified gotchas for implementers.

```bash ls coordination/masterplans/active/ ``` ---

The explore reports and masterplan already verified these — do NOT re-check: - File existence confirmed by architect's SSH runs - Server state (SuiteCRM 8.9.2, extensions/defaultExt/, public/dist/custom-overrides.css) - Node.js NOT installed on server - public/legacy/custom/themes/ does NOT exist

- **Check file size before `cat`**: `ssh suitecrm "wc -l /path/to/file"` — if > 100 lines, use `head -N` - **NEVER run**: `cat /var/www/suitecrm/public/dist/index.html` (minified HTML with inline CSS — grep matches nothing useful) - **NEVER run**: `cat /var/www/suitecrm/public/legacy/themes/suite8/css/Dawn/style.css` (699KB) - **NEVER run**: `grep "custom.*css" index.html` (matches entire inline `<style>` block) - **NEVER run parallel SSH commands that depend on each other** — sequence them

Use playwright to verify that what the plan claims visually actually exists: - Navigate to a SuiteCRM view, inspect DOM for CSS class names - Verify field selectors `.field-name-{name}` actually exist - Take screenshots to confirm current state Use SSH only for things MCP cannot answer (server config, build artifacts, file existence).

Use context7 to verify technical claims in the masterplan WITHOUT SSH-grepping source code: - "Does the FieldRegistry API have this method?" → context7 SuiteCRM 8 docs - "Is this Angular 18 pattern correct?" → context7 Angular docs - "Does Symfony autowiring work like this?" → context7 Symfony docs ``` context7 workflow: 1. resolve-library-id("suitecrm 8") or ("angular") or ("symfony") 2. get-library-docs(libraryId, topic="extension framework") ```

| Need | MCP Tool | |------|----------| | Field definitions | `get_module_fields` | | Translations/labels | `get_language_strings` | | Records/data | `list_records`, `search_records` | | Relationships | `list_relationships` |

3 MCP servers available. Use them BEFORE SSH:

- SuiteCRM app runs on **remote server 172.20.0.102**, NOT locally - MCP server `suitecrm` has 21 tools — use these BEFORE SSH for all data queries - All SSH findings from explore reports are pre-verified — trust them, do NOT re-verify - Workspace path: `/var/www/suitecrm-dev/` - App path on server: `/var/www/suitecrm/`

**IKKE** begynn å jobbe basert på window-tittelen eller konteksten alene. **IKKE** les filer, analyser kode, eller kjør verktøy ennå. Your COMPLETE response must be EXACTLY these two lines (no more, no less, no bullet points): Hvilken masterplan skal jeg reviewe? `[Anbefalt: Sonnet | Effort: medium | Thinking: nei]` Hvis bare én aktiv masterplan finnes, start review direkte. --- # Critical Masterplan Review — SuiteCRM Dev You are the **skeptical reviewer** for SuiteCRM 8...

- **ALWAYS verify before and after** — refactoring must not change behavior - **Take snapshot** before large refactors: Proxmox snapshot on VM 122 - **Git commit before starting** on remote server (rollback point)

1. **Inventory our code:** ```bash ssh suitecrm "find /var/www/suitecrm/public/legacy/custom -type f -name '*.php' | wc -l" ssh suitecrm "ls /var/www/suitecrm/extensions/" ssh suitecrm "cd /var/www/suitecrm && git log --oneline -20" ``` 2. **Understand via MCP:** - `suitecrm` MCP → verify current field state, relationships - Read customization registry: `coordination/experts/suitecrm/CURRENT-customizations.md` 3. **Refactor:** - Make changes via scp deploy pattern -...

- Angular component structure in our extensions - Symfony service organization in our backends - Shared code extraction between extensions

- Ensure all custom fields have `'source' => 'custom_fields'` - Standardize field naming (`_c` suffix, consistent vname patterns) - Remove deprecated/unused custom fields

- Standardize Norwegian translations across modules - Remove duplicate label definitions - Ensure consistent terminology (same concept = same word everywhere)

- Consolidate multiple small Extension files into logical groups - Standardize naming conventions across modules - Remove orphaned Extension files that reference deleted fields

- Merge duplicate/conflicting viewdefs into clean single files - Standardize panel naming and field ordering across modules - Remove unused fields from view definitions

**Scope er KUN vår egen kode:** ``` ✅ public/legacy/custom/modules/ — Våre metadata-overrides ✅ public/legacy/custom/Extension/ — Våre Extension-filer (vardefs, language, layoutdefs) ✅ public/legacy/custom/include/ — Våre globale språk-overrides ✅ extensions/{ourExt}/ — Våre extensions (Angular + backend) ❌ core/ — ALDRI (SuiteCRM kildekode) ❌ public/legacy/modules/ — ALDRI (SuiteCRM standard-moduler) ❌...

**IKKE** begynn å jobbe basert på window-tittelen eller konteksten alene. **IKKE** les filer, analyser kode, eller kjør verktøy ennå. Your COMPLETE response must be EXACTLY these two lines (no more, no less, no bullet points): Hva skal refaktoreres? `[Anbefalt: Sonnet | Effort: medium | Thinking: nei]` --- # Refactor — SuiteCRM Dev You refactor **our custom code only** — extensions, overrides, metadata files, language files, and vardefs that WE have created. You NEVER touch SuiteCRM core...

```bash # Use suitecrm MCP to verify fields, data, relationships exist correctly # Use playwright to verify UI renders as expected ```

- [ ] All changes registered in CURRENT-customizations.md with SC-NNNN ID - [ ] Gotchas discovered during implementation added to CURRENT-architecture.md - [ ] Git committed on remote server with descriptive messages

- [ ] SSH file writing uses scp method (not heredoc+sudo) - [ ] Cache clearing uses correct method per change type - [ ] QR&R used for Extension changes (not just cache:clear)