Memory Wiki

I can see the issue clearly. The event listener at lines 695-712 directly maps `$payload['userId']` (an int) to `'userUuid'` which needs a string UUID. I'll patch it to add the UUID resolution step before calling `createFromPayment()`.

The diff shows some escaping noise — let me verify the actual file content is correct.

I see line 707 has double-escaped backslashes. Let me fix that.

Let me check the current state and also fix the indentation.

I need to fix the indentation on line 707 and add the `resolveUserUuid` method. Let me fix the indentation first.

Good, indentation is fixed. Now I need to add the `resolveUserUuid()` private method to the `OrderManagementModule` class. I'll add it right after the existing `getProfeUser()` method.

Now I'll add the `resolveUserUuid()` method between `getProfeUser()` and `getDiContainer()`.

Let me verify the final state of both patched sections to confirm everything is correct.

Let me also update the FAULT-002/007 workaround notes to include the new `resolveUserUuid()` method as a third direct query location.

All changes are complete. Here's a summary of what was done: ## Summary ### What I did Patched `/root/.hermes/plans/task-t18-build-plan.md` to fix the `userId` → `userUuid` blocker in T18's build plan by adding a UUID resolution step in the event listener. ### Changes made **1. Event listener (Step 8 — `registerEventListeners()`, lines 694-721):** - Replaced the direct `$payload['userId']` → `'userUuid'` mapping with a two-step process: - **Step 1:** Extracts `userId` (int) from payload, validates it's positive, then calls `$this->resolveUserUuid($userId)` to get the string UUID - **Step 2:** Passes the resolved `$userUuid` to `createFromPayment()` - Added input validation: throws `\InvalidArgumentException` if `userId` is missing or ≤ 0 **2. New `resolveUserUuid()` private method (added at line 859):** - Queries `profe_users` with `SELECT uuid WHERE id = :id` using a prepared statement - Returns the string UUID - Throws `\RuntimeException` with a descriptive message if the user is not found - Annotated with `FAULT-002 workaround` comment documenting the direct DB query **3. FAULT-002/007 workaround notes (Step 6, line 522):** - Updated from "two places" to "three places" and added `resolveUserUuid()` as the third direct `profe_users` query location **4. Fault Compliance Table (Section 6):** - Updated the FAULT-002/007 row to mention `resolveUserUuid()` in the event listener alongside the existing `createFromPayment()` and `getUserOrders()` locations ### Files modified - `/root/.hermes/plans/task-t18-build-plan.md` — 4 patches applied, all successful ### Issues encountered - Double-escaped backslashes (`\\\\\\\\`) initially appeared in the patched `$orderMgmt` line due to the patch tool's escaping behavior; corrected in a follow-up fix - Indentation was lost on the `$orderMgmt` line after the backslash fix; re-fixed to match the 24-space indentation of surrounding code