fix: correctly distinguish between first participant and applicant

src/Form/Service/Condition/AuthenticatedUserPersonalDataCondition.php

@@ -8,46 +8,37 @@ use App\Form\Model\BookingDto;
 use App\Form\Service\Contract\FieldConditionInterface;
 
 /**
- * Condition that determines if personal data fields should be hidden for authenticated users.
+ * Condition that determines if personal data fields should be shown as static text.
  *
- * ⚠️ IMPORTANT: This condition is used in CREATE MODE ONLY to protect authenticated
- * applicant data during booking creation. It is NOT used in edit mode.
+ * This condition protects the logged-in user's personal data from being modified
+ * within the booking form. Instead, users should edit their data via the personal
+ * data form to prevent:
+ * - Creating duplicate customer records in BPN
+ * - Disconnecting bookings from the user's account
+ * - Causing data inconsistencies between booking and account data
  *
- * In CREATE mode:
- * - When a logged-in user creates a booking, their personal data is prepopulated from
- *   their BPN account (including personId).
- * - Their personal data fields should be hidden and displayed as static text to prevent
- *   modifications that could:
- *   - Create duplicate customer records in BPN
- *   - Disconnect bookings from the user's account
- *   - Cause data inconsistencies between booking and account data
+ * The condition compares the participant's personId with the booking applicant's
+ * personId to determine if the participant IS the logged-in user:
+ * - Customer-initiated bookings: Participant 0's personId matches applicant's personId
+ * - Agency-initiated bookings: Participant 0's personId differs from applicant's personId
  *
- * In EDIT mode:
- * - DO NOT use this condition. Edit mode uses PersonalDataMutabilityCondition instead,
- *   which respects the BPN API's per-participant `mutable` flag (aenderungmoeglich).
- * - The mutability flag determines editability for ALL participants uniformly in edit mode.
- *
- * When this condition is satisfied (returns true), the template should:
- * - Hide the form fields for personal data
- * - Display the values as static, read-only text via the field_or_static macro
+ * In CREATE mode: Checks if participant has a personId (prepopulated from BPN account)
+ * In EDIT mode: Compares participant's personId with applicant's personId
  */
 class AuthenticatedUserPersonalDataCondition implements FieldConditionInterface
 {
     /**
-     * Evaluates if personal data fields should be hidden (not editable) in CREATE mode.
+     * Evaluates if personal data fields should be shown as static text.
      *
-     * Returns true when the participant has a personId set, indicating they are
-     * a logged-in user whose data was prepopulated from their BPN account.
-     * When true, personal data fields should be hidden and displayed as static text.
+     * In CREATE mode: Returns true when participant has a personId (prepopulated).
+     * In EDIT mode: Returns true when participant's personId matches applicant's personId,
+     * indicating the participant IS the logged-in user.
      *
-     * This condition is only used during booking creation, not in edit mode.
-     * Edit mode uses PersonalDataMutabilityCondition to respect BPN's mutability flag.
-     *
-     * @param BookingDto           $bookingDto       The current booking data (create flow)
+     * @param BookingDto           $bookingDto       The booking data
      * @param int                  $participantIndex The index of the participant being evaluated
      * @param array<string, mixed> $formData         Current form data (unused)
      *
-     * @return bool True if fields should be hidden (authenticated user in create mode)
+     * @return bool True if fields should be shown as static text
      */
     public function evaluate(BookingDto $bookingDto, int $participantIndex, array $formData): bool
     {
@@ -56,8 +47,18 @@ class AuthenticatedUserPersonalDataCondition implements FieldConditionInterface
             return false;
         }
 
-        // Hide personal data fields if participant has BPN person ID (authenticated user in create mode)
-        // The personId is set during prepopulation when a logged-in user starts creating a booking
+        // In edit mode, compare participant's personId with applicant's personId
+        // This distinguishes customer-initiated (match) from agency-initiated (no match) bookings
+        if (BookingDto::MODE_EDIT === $bookingDto->getMode()) {
+            $applicantPersonId = $bookingDto->booking?->applicant?->personId;
+            if (null === $applicantPersonId) {
+                return false;
+            }
+
+            return $participant->personId === $applicantPersonId;
+        }
+
+        // In create mode, check if participant has personId (prepopulated from BPN account)
         return null !== $participant->personId;
     }
 
@@ -81,6 +82,6 @@ class AuthenticatedUserPersonalDataCondition implements FieldConditionInterface
      */
     public function getDescription(): string
     {
-        return 'Personal data is not editable for authenticated users in create mode (prevents duplicate records)';
+        return 'Personal data is shown as static text for the logged-in user (edit via personal data form)';
     }
 }