Place credit holds on evidence, with the reason recorded

**Objective:** Put customer `{customer-name}` on credit hold and record the reason `{reason}` (default a reason drafted from the evidence) in a customer note, but only after showing the evidence and getting the user's confirmation.

Pass `{company}` as `company` on every call (if it is empty, omit `company` and the default company is used). Pass a generous `max-records` (1000). If a result comes back with exactly that many rows, say the result may be truncated.

**Step 1: Resolve the customer**

Call `dynamics-gp-get-rm-customer` with `customer-name.contains` set to `{customer-name}`; if nothing matches, try `customer-id`. If more than one customer matches, list them and stop. If `hold` is already set, stop and say the customer is already on hold. Note `customer-balance`, `credit-limit-amount`, `payment-terms-id` and `salesperson-id`.

**Step 2: Evidence**

* Call `dynamics-gp-get-rm-trx` filtered by `customer-id`. Total the overdue `current-transaction-amount` on non-voided debit documents, aged 1-30, 31-60, 61-90 and over 90 days past `due-date`, and note the oldest overdue document.
* Compare `customer-balance` with `credit-limit-amount` (a limit of 0 means none is set).
* Call `dynamics-gp-get-rm-sales-trx` filtered by `customer-id` and list unposted orders, which the hold will affect.

**Step 3: Confirm**

Show the user: customer id and name, balance, credit limit, overdue by bucket, oldest overdue document, the open orders affected, and the note text you will write (`{reason}`, or a one-sentence reason drafted from the evidence, prefixed with today's date). If the customer has nothing overdue and is not over limit, say plainly that the evidence does not support a hold. Ask for explicit confirmation. Do nothing further without a clear yes.

**Step 4: Write**

1. Call `dynamics-gp-rm-customer-update` once with `customer-id` and `hold` set to true. Pass no other fields, so nothing else on the customer changes.
2. Only if that succeeded, call `dynamics-gp-rm-customer-note` once with `customer-id`, `note` set to the confirmed text, `append-to-existing-note` true and `add-date-and-time` true.

If the note fails after the hold succeeded, tell the user the customer is on hold but the reason was not recorded. Do not retry either call automatically.

**Step 5: Verify**

Call `dynamics-gp-get-rm-customer` again and report the stored `hold` value.

**Rules & Guidelines:**

* The only write tools this prompt may call are `dynamics-gp-rm-customer-update` and `dynamics-gp-rm-customer-note`, once each, after Step 3.
* Do not change the credit limit, terms, salesperson or any other field, and do not call `dynamics-gp-rm-sales-trx-update` to cancel or change orders.

**Validation:**

* If Step 1 finds no customer, stop and suggest a shorter part of the name.