From cca6ae408a1575dbbc52fcce34ad1358935fdfbd Mon Sep 17 00:00:00 2001
From: Ruben van der Linde <ruben@conduction.nl>
Date: Tue, 11 Aug 2026 21:00:54 +0200
Subject: [PATCH] chore(softwarecatalog): remove two committed debug scripts
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Task 5.2 of openspec/changes/english-vocabulary: the spec says DELETE these rather
than rename them, because a committed debug script is not vocabulary worth
migrating.

Read both before removing. They are pure echo scripts from a 2026-05-29 debugging
session — notes-to-self about why a contactpersoon's username looked empty. No
queries, no credentials, no logic; nothing imports or executes them, and neither
appears in phpcs.xml, phpmd.baseline.xml, psalm.xml, phpstan.neon, composer.json
or any workflow.

Two things worth noting on the way out. They hardcode a real-looking contactpersoon
UUID, which is the sort of thing that should not sit in a public repo even when it
is not a secret. And their whole premise was querying oc_openregister_objects,
which is the EMPTY shared table — objects live in the per-schema
oc_openregister_table_<reg>_<schema> shards, so the debugging session was reading
the wrong place. That is the same lookup error that made a stored-object count
report a false zero earlier in this programme.

softwarecatalog's vocabulary rename itself is NOT in this commit: it is 6757
references across 194 files over roughly 9,500 imported VNG production records,
and the spec requires the migration to be authored and tested against copied data
before any rename merges.
---
 debug_contactpersoon_data.php     | 40 ----------------------------
 debug_contactpersoon_database.php | 44 -------------------------------
 2 files changed, 84 deletions(-)
 delete mode 100644 debug_contactpersoon_data.php
 delete mode 100644 debug_contactpersoon_database.php

diff --git a/debug_contactpersoon_data.php b/debug_contactpersoon_data.php
deleted file mode 100644
index 215a58a5..00000000
--- a/debug_contactpersoon_data.php
+++ /dev/null
@@ -1,40 +0,0 @@
-<?php
-/**
- * Debug script to check what's in the database for the contactpersoon
- */
-
-echo "=== DEBUG CONTACTPERSOON DATABASE DATA ===\n";
-
-// The contactpersoon ID from the API response
-$contactpersoonId = 'e8ba22ba-35ab-4b59-a097-91df6fa2cd3d';
-
-echo "Contactpersoon ID: $contactpersoonId\n\n";
-
-echo "1. Checking what's in the database for this contactpersoon...\n";
-echo "   - Query: SELECT * FROM oc_openregister_objects WHERE id = '$contactpersoonId'\n";
-echo "   - Expected fields: id, name, object (JSON), created, updated, etc.\n\n";
-
-echo "2. The 'object' field should contain JSON with:\n";
-echo "   - username: the Nextcloud username\n";
-echo "   - email: the email address\n";
-echo "   - other contactpersoon data\n\n";
-
-echo "3. If username is empty or null, the service returns:\n";
-echo "   - hasUser: false\n";
-echo "   - username: ''\n";
-echo "   - disabled: false (default for non-users)\n\n";
-
-echo "4. POSSIBLE ISSUES:\n";
-echo "   a) Username field is empty in database but user exists in Nextcloud\n";
-echo "   b) Username field has different format than expected\n";
-echo "   c) User was disabled but username was removed from contactpersoon data\n";
-echo "   d) There's a mismatch between what we think the username is vs what's stored\n\n";
-
-echo "5. TO FIX THIS:\n";
-echo "   a) Check the actual database record\n";
-echo "   b) Verify what username should be associated with this contactpersoon\n";
-echo "   c) Update the contactpersoon data with the correct username\n";
-echo "   d) Or fix the logic to handle this edge case\n\n";
-
-echo "=== END DEBUG ===\n";
-?>
diff --git a/debug_contactpersoon_database.php b/debug_contactpersoon_database.php
deleted file mode 100644
index c0339d64..00000000
--- a/debug_contactpersoon_database.php
+++ /dev/null
@@ -1,44 +0,0 @@
-<?php
-/**
- * Debug script to check what's actually in the database for the contactpersoon
- */
-
-echo "=== DEBUG CONTACTPERSOON DATABASE ===\n";
-
-// The contactpersoon ID from the API response
-$contactpersoonId = 'e8ba22ba-35ab-4b59-a097-91df6fa2cd3d';
-
-echo "Contactpersoon ID: $contactpersoonId\n\n";
-
-echo "1. We need to check what's actually in the database:\n";
-echo "   - Table: oc_openregister_objects\n";
-echo "   - Field: object (JSON)\n";
-echo "   - Should contain: username, email, etc.\n\n";
-
-echo "2. Current API response shows:\n";
-echo "   - hasUser: false\n";
-echo "   - username: ''\n";
-echo "   - disabled: false\n\n";
-
-echo "3. But user says this contactpersoon HAS a user!\n\n";
-
-echo "4. POSSIBLE CAUSES:\n";
-echo "   a) Username field is empty/null in database but user exists in Nextcloud\n";
-echo "   b) Username field has different name (not 'username')\n";
-echo "   c) Data structure is different than expected\n";
-echo "   d) Contactpersoon data was corrupted or not properly saved\n\n";
-
-echo "5. TO DEBUG:\n";
-echo "   a) Check the actual database record\n";
-echo "   b) Check if username is stored under a different field name\n";
-echo "   c) Check if the user exists in Nextcloud but isn't linked properly\n";
-echo "   d) Check if there's a mismatch between what we expect vs reality\n\n";
-
-echo "6. NEXT STEPS:\n";
-echo "   - Run a direct database query to see the raw data\n";
-echo "   - Check if username is stored differently\n";
-echo "   - Verify the user actually exists in Nextcloud\n";
-echo "   - Fix the data or the logic\n\n";
-
-echo "=== END DEBUG ===\n";
-?>