GPT-5.5 vs GPT-5.6 Luna for code review

### Finding 1 — correctness bug: nullable customer

`Customer.findByPk(o.customerId)` can return `null` when the customer row is soft-deleted. This line will then throw:

```js
customer.name
```

That is a correctness bug because a valid `Order` row can make this code crash.

This should block the merge because the code is not safe for data that the system explicitly allows: orders may reference soft-deleted customers.

---

### Finding 2 — performance problem: N+1 queries

This code does one query for the orders, then one customer query per or…

### 1. Correctness bug — should block the merge

`findByPk` can return `null` for a soft-deleted customer, so this line can throw:

```js
customer.name
```

That makes the entire operation fail for an otherwise valid open order. This should block the merge because it is an unhandled valid data state, not merely an edge-case performance concern.

### 2. Performance problem — N+1 queries

The code performs:

- one query to load all open orders, plus
- one customer query for every open order.

So `N` open orders produce `N + 1` database queries.…