test: Update test results, add bezoeker role tests, and expand Postman collection

- Add bezoeker (public visitor) test results with screenshots
- Update all role-based test results (architectuur-expert, functioneel-beheerder, gemeente, leverancier, samenwerking, security-officer)
- Refresh API issue test results for 120+ issues
- Expand Postman test collection with new test cases
- Update test skills with additional test scenarios
- Fix ContactpersoonService minor code update
- Add issue #457 (koppeling delete 400 error)
- Update issues.md and aanvullende-informatie.md

Author: rubenvdlinde

.claude/skills/test-architectuur-expert.md

@@ -23,6 +23,10 @@ Sarah validates GEMMA compliance, reviews architecture decisions, and monitors c
 - **Browser**: Use Playwright MCP browser tools (prefixed `mcp__browser-N__`, where N is assigned by the orchestrator)
 - **Login URL**: `{FRONTEND}/login`
 
+## Organization & Permissions Context
+
+Sarah's account is in the Default Organisation (expected for VNG roles). The org permission system requires the internal Nextcloud org UUID to match a register object. If org fetch fails (404 in console), edit/delete buttons will be disabled — this is expected for VNG-raadpleger roles that primarily read/view rather than edit. Run `bash softwarecatalog/test-setup.sh` if org assignments are broken.
+
 ## Test Scope
 
 ### Primary Steps

.claude/skills/test-functioneel-beheerder.md

@@ -24,6 +24,14 @@ Peter has full system access. He activates organizations, manages users, maintai
 - **Login URL**: `{FRONTEND}/login`
 - **Backend Admin**: `{BACKEND}/` ({ADMIN_USER}:{ADMIN_PASS})
 
+## Organization & Permissions Context
+
+Peter's account (`peter.vandijk@test.nl`) is in the Default Organisation. **Important**: the admin user (`admin`) has a known limitation — "Default Organisation" has no matching register object in `voorzieningen/organisatie`, which causes org fetch 404 errors and disables edit/delete in beheer.
+
+- **For frontend beheer testing**: Log in as `peter.vandijk@test.nl` (NOT `admin`). Peter has full admin group membership and a proper org assignment.
+- **For Nextcloud backend testing** (OpenCatalogi admin, OpenRegister config): Use `admin:admin` via the backend URL — these features don't depend on the org permission system.
+- If you see "org fetch error" or disabled edit/delete buttons, the active org UUID doesn't have a matching register object. Run `bash softwarecatalog/test-setup.sh` to fix org assignments.
+
 ## Test Scope
 
 ### Primary Steps

.claude/skills/test-gemeente.md

@@ -23,6 +23,16 @@ Maria manages her municipality's software landscape in the Softwarecatalogus. Sh
 - **Browser**: Use Playwright MCP browser tools (prefixed `mcp__browser-N__`, where N is assigned by the orchestrator)
 - **Login URL**: `{FRONTEND}/login`
 
+## Organization & Permissions Context
+
+Maria's active organization is **Test Gemeente**. The internal Nextcloud org UUID matches a register object in `voorzieningen/organisatie`, which is required for edit/delete permissions to work.
+
+- **Beheer tables** show objects based on RBAC rules — gebruik-beheerder can see ALL objects (not just own org) for most schemas
+- **Edit/Delete buttons** require the org data fetch to succeed — if you see disabled actions or missing buttons, check for org fetch 404 errors in the console
+- **Do NOT test beheer as admin** — admin's "Default Organisation" has no register object, so org fetch always fails and permissions are broken
+- The test setup script (`bash softwarecatalog/test-setup.sh`) creates test objects as maria.vanderberg so they get the correct org assignment
+- If beheer tables are empty or missing expected test objects, run the test setup script
+
 ## Test Scope
 
 ### Primary Steps

.claude/skills/test-leverancier.md

@@ -23,6 +23,16 @@ Jan manages his company's products in the Softwarecatalogus. He registers applic
 - **Browser**: Use Playwright MCP browser tools (prefixed `mcp__browser-N__`, where N is assigned by the orchestrator)
 - **Login URL**: `{FRONTEND}/login`
 
+## Organization & Permissions Context
+
+Jan's active organization is **Test Leverancier BV**. The internal Nextcloud org UUID matches a register object in `voorzieningen/organisatie`, which is required for edit/delete permissions to work.
+
+- **Beheer tables** only show objects owned by Jan's org (RBAC scoping by `@self.organisation`)
+- **Edit/Delete buttons** require the org data fetch to succeed — if you see disabled actions or missing buttons, check for org fetch 404 errors in the console
+- **Do NOT test beheer as admin** — admin's "Default Organisation" has no register object, so org fetch always fails and permissions are broken
+- The test setup script (`bash softwarecatalog/test-setup.sh`) creates test objects as jan.pietersen so they get the correct org assignment
+- If beheer tables are empty, run the test setup script to create/verify test objects
+
 ## Test Scope
 
 This agent tests the following steps from the test flow (`testen.md`):
@@ -126,6 +136,7 @@ This agent tests the following steps from the test flow (`testen.md`):
 | #453 | Zoeken: filters van slag met filter Type=Koppeling | Step 14 |
 | #454 | Wizard koppelingen: Reeds bestaande koppelingen voor worden niet gevonden | Step 11 |
 | #456 | Consistentie in werking van wizards | Step 7 |
+| #457 | Koppeling: verwijderen geeft een 400-error | Step 11 |
 
 ## Acceptance Criteria Reference
 

.claude/skills/test-samenwerking.md

@@ -23,6 +23,10 @@ Linda represents a collaboration that acts as BOTH a supplier (offering shared s
 - **Browser**: Use Playwright MCP browser tools (prefixed `mcp__browser-N__`, where N is assigned by the orchestrator)
 - **Login URL**: `{FRONTEND}/login`
 
+## Organization & Permissions Context
+
+Linda's active organization is **Test Samenwerking**. The org permission system requires the internal Nextcloud org UUID to match a register object in `voorzieningen/organisatie`. If org fetch fails (404 in console), edit/delete buttons will be disabled. Do NOT test beheer features as `admin` — use the test persona accounts. Run `bash softwarecatalog/test-setup.sh` if org assignments are broken.
+
 ## Test Scope
 
 ### Primary Steps

.claude/skills/test-security-officer.md

@@ -23,6 +23,10 @@ Mark monitors security requirements, validates privacy implementations, and ensu
 - **Browser**: Use Playwright MCP browser tools (prefixed `mcp__browser-N__`, where N is assigned by the orchestrator)
 - **Login URL**: `{FRONTEND}/login`
 
+## Organization & Permissions Context
+
+Mark's active organization is **Test Gemeente** (same as Maria). The org permission system requires the internal Nextcloud org UUID to match a register object in `voorzieningen/organisatie`. If org fetch fails (404 in console), edit/delete buttons will be disabled. Do NOT test beheer features as `admin` — use the test persona accounts. Run `bash softwarecatalog/test-setup.sh` if org assignments are broken.
+
 ## Test Scope
 
 ### Primary Steps

aanvullende-informatie.md

@@ -4,8 +4,8 @@
 > Alle issues zijn ook beschikbaar als individuele markdown bestanden in de [issues/](issues/) map (met beschrijving, reacties en afbeeldingen).
 > Zie ook: [issues.md](issues.md) voor de volledige lijst met acceptatiecriteria per issue.
 
-**Totaal: 159 issues** | Open: 207 | Gesloten: 233
-**Laatste sync:** 2026-03-05 | +6 nieuwe issues (#451-#456) | +2 gesloten issues (#225, #315)
+**Totaal: 160 issues** | Open: 207 | Gesloten: 233
+**Laatste sync:** 2026-03-09 | +1 nieuw issue (#457)
 
 ---
 
@@ -317,9 +317,9 @@ Na het verwerken van elk issue, update deze tabel:
 ---
 
 ## Open issues
-*76 issues*
+*77 issues*
 
-### Bug (45)
+### Bug (46)
 
 | # | Issue | Analyse | GitHub | Checked |
 |---|-------|---------|--------|--------|
@@ -368,6 +368,7 @@ Na het verwerken van elk issue, update deze tabel:
 | [454](issues/454.md) | Wizard koppelingen: Reeds bestaande koppelingen niet gevonden | Cross-supplier koppelingen niet zichtbaar in wizard | [#454](https://github.com/VNG-Realisatie/Softwarecatalogus/issues/454) | [ ] |
 | [455](issues/455.md) | Tabblad koppelingen en contactpersonen publiekelijk niet getoond | Koppelingen en contactpersonen tabs niet zichtbaar voor publiek (RBAC) | [#455](https://github.com/VNG-Realisatie/Softwarecatalogus/issues/455) | [ ] |
 | [456](issues/456.md) | Consistentie in werking van wizards | Wizard afsluiting inconsistent qua tekst, knoppen en flow | [#456](https://github.com/VNG-Realisatie/Softwarecatalogus/issues/456) | [ ] |
+| [457](issues/457.md) | Koppeling: verwijderen geeft een 400-error | DELETE koppeling retourneert 400 bij zowel geimporteerde als nieuwe koppelingen | [#457](https://github.com/VNG-Realisatie/Softwarecatalogus/issues/457) | [ ] |
 
 ### Datakwaliteit (10)
 

issues.md

@@ -1,14 +1,14 @@
 # Softwarecatalogus - Issues In Review
 
-**Date:** 2026-03-05
+**Date:** 2026-03-09
 **Source:** [VNG-Realisatie Project Board #17, View 22](https://github.com/orgs/VNG-Realisatie/projects/17/views/22)
 
 > Zie ook: [aanvullende-informatie.md](aanvullende-informatie.md) voor het overzicht van alle IGS-gelabelde issues (nieuw, overleg, review).
 
 ## Summary
 
 - **Total open issues on GitHub:** 207
-- **IGS issues (detailed with acceptance criteria):** 136 (was 130, +6 new issues)
+- **IGS issues (detailed with acceptance criteria):** 137 (was 136, +1 new issue)
 - **Other issues (summary table):** 79
 - **Issues closed since last update:** 58 (see closed list below)
 - **Reopened issues:** 3 (#6, #15, #23 — removed from closed list)
@@ -43,13 +43,17 @@ Previously closed (2026-02-22): #185, #266, #267, #286, #294, #300, #302, #307,
 
 **Reopened:** #6, #15, #23 (previously listed as closed, now open again on GitHub)
 
+### New Issues Added (2026-03-09)
+
+1 new issue synced: #457
+
 ### New Issues Added (2026-03-04)
 
 15 new issues synced: #187, #443, #444, #445, #446, #447, #448, #449, #450, #451, #452, #453, #454, #455, #456
 
 ---
 
-## IGS Issues (In Review) — 136 issues
+## IGS Issues (In Review) — 137 issues
 
 ### #6: Als aanbod-beheerder wil ik kunnen registreren welke standaarden door mijn pakket worden ondersteund en eventueel testrapporten beschikbaar stellen
 
@@ -2167,6 +2171,25 @@ Previously closed (2026-02-22): #185, #266, #267, #286, #294, #300, #302, #307,
 
 ---
 
+### #457: Koppeling: verwijderen geeft een 400-error
+
+**Labels:** Aanbod, IGS nieuw
+**Test Step:** Step 11
+
+**Summary:** Deleting a koppeling (both imported and newly created) returns a 400 error. The bug is reproducible via Dashboard > Koppelingen overzicht > Bekijken > Acties > Verwijderen. Tested with multiple koppelingen, including those without any gemeente usage.
+
+**Acceptance Criteria:**
+- [ ] [API] DELETE request for a koppeling object returns 200/204 (not 400)
+- [ ] [API] Deleting a koppeling that has no gemeente usage succeeds without error
+- [ ] [API] Deleting an imported koppeling succeeds without error
+- [ ] [API] Deleting a newly created koppeling succeeds without error
+- [ ] [UI] Clicking "Verwijderen" in the koppeling detail page removes the koppeling without error
+- [ ] [UI] After successful deletion, the koppeling no longer appears in the koppelingen overzicht
+
+**Key Context from Comments:** Bug reported by @Makkmetp. Affects both imported and manually created koppelingen. Related to koppeling management flow (Step 11). Screenshots show the 400 error in the browser.
+
+---
+
 ### #187: Tekstvoorstellen
 
 **Labels:** Tekstuele wijzigingen
@@ -3427,6 +3450,25 @@ Previously closed (2026-02-22): #185, #266, #267, #286, #294, #300, #302, #307,
 
 ---
 
+### #457: Koppeling: verwijderen geeft een 400-error
+
+**Labels:** Aanbod, IGS nieuw
+**Test Step:** Step 11
+
+**Summary:** Deleting a koppeling (both imported and newly created) returns a 400 error. The bug is reproducible via Dashboard > Koppelingen overzicht > Bekijken > Acties > Verwijderen. Tested with multiple koppelingen, including those without any gemeente usage.
+
+**Acceptance Criteria:**
+- [ ] [API] DELETE request for a koppeling object returns 200/204 (not 400)
+- [ ] [API] Deleting a koppeling that has no gemeente usage succeeds without error
+- [ ] [API] Deleting an imported koppeling succeeds without error
+- [ ] [API] Deleting a newly created koppeling succeeds without error
+- [ ] [UI] Clicking "Verwijderen" in the koppeling detail page removes the koppeling without error
+- [ ] [UI] After successful deletion, the koppeling no longer appears in the koppelingen overzicht
+
+**Key Context from Comments:** Bug reported by @Makkmetp. Affects both imported and manually created koppelingen. Related to koppeling management flow (Step 11). Screenshots show the 400 error in the browser.
+
+---
+
 ### #187: Tekstvoorstellen
 
 **Labels:** Aanbod, Tekstuele wijzigingen
@@ -3587,7 +3629,7 @@ The following issues are questions, PvE requirements, infrastructure tasks, test
 | Step 7 | Product aanmaken (applicaties) | 36 | 2 | 38 |
 | Step 9 | Dienst wizard | 17 | 0 | 17 |
 | Step 10 | Gebruik melden en beheren | 9 | 1 | 10 |
-| Step 11 | Koppeling wizard | 13 | 0 | 13 |
+| Step 11 | Koppeling wizard | 14 | 0 | 14 |
 | Step 12 | Privacy en zichtbaarheid | 4 | 4 | 8 |
 | Step 13 | Excel export | 2 | 1 | 3 |
 | Step 14 | Zoeken en resultaten | 12 | 2 | 14 |
@@ -3602,7 +3644,7 @@ The following issues are questions, PvE requirements, infrastructure tasks, test
 | Step 24 | AMEFF export | 0 | 1 | 1 |
 | General | Cross-cutting / multiple steps | 3 | 2 | 5 |
 | Infra | Infrastructure / non-testable | 1 | 3 | 4 |
-| **Total** | | **136** | **38** | **174** |
+| **Total** | | **137** | **38** | **175** |
 
 > Note: Some issues with broad scope (General/Infra) are not mapped to a specific test step.
 

issues/457.md

@@ -0,0 +1,37 @@
+# #457 — Koppeling: verwijderen geeft een 400-error
+
+**Status:** OPEN | **Labels:** Aanbod, IGS nieuw
+**Auteur:** @Makkmetp | **Datum:** 2026-03-05
+**Link:** https://github.com/VNG-Realisatie/Softwarecatalogus/issues/457
+
+---
+
+## Beschrijving
+
+Het verwijderen van een koppeling geeft een 400-error. Zowel bij een geimporteerde als nieuw aangemaakte leverancier.
+
+Ga via Dashboard naar je koppelingen overzicht.
+Klik bij een koppeling op ... Acties op Bekijken.
+Verwijder via ...Acties > Verwijderen de koppeling
+
+<img width="1161" height="784" alt="Image" src="https://github.com/user-attachments/assets/79ff1634-3267-4ac2-87cd-5ec29f2ad664" />
+
+<img width="1211" height="596" alt="Image" src="https://github.com/user-attachments/assets/d4cedc14-051a-4cae-bbd9-d2bbdfeed63d" />
+
+Dit is getest met meerdere koppelingen. Ook met koppelingen waar nog geen gebruik van wordt gemaakt door een gemeente.
+Graag ervoor zorgen dat koppelingen volgens integriteitsregels verwijderd kunnen worden en geen 400-error geven.
+
+---
+
+## Reacties (1)
+
+### Reactie 1 — @github-actions (2026-03-05)
+
+Bedankt voor het aanmaken van deze issue! 👋
+
+Voor meer informatie over onze spelregels voor het schrijven van issues, bekijk alsjeblieft onze [issues.md](../../issues/issues.md) documentatie.
+
+Belangrijke punten om te controleren:
+- ✍️ Is de beschrijving helder en compleet?
+- 📋 Zijn er duidelijke acceptatiecriteria toegevoegd?
+- 🎯 Is de context voldoende beschreven?

lib/Service/ContactpersoonService.php

@@ -218,8 +218,8 @@ public function processContactpersoon(object $contactpersoonObject, bool $isUpda
                         if ($organisationEntity !== null && $organisationEntity->getActive() === true) {
                             // Determine if this is the first contact for the organization.
                             $isFirstContact = $this->contactPersonHandler->isFirstContactForOrganization(
-                                contactpersoonObject: $contactpersoonObject,
-                                contactData: $contactData
+                                contactObject: $contactpersoonObject,
+                                objectData: $contactData
                             );
 
                             // Create user account - organization is active.