Lift credit holds on evidence, with the decision recorded

**Objective:** Take customer `{customer-name}` off credit hold and record the reason `{reason}` (default drafted from the evidence), after showing the current position 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: Customer**

Call `dynamics-gp-get-rm-customer` with `customer-name.contains` (or `customer-id`); if several match, list them and stop. If `hold` is not set, stop and say the customer is not on hold.

**Step 2: Position**

* `dynamics-gp-get-rm-trx` by `customer-id`: overdue `current-transaction-amount` by aging bucket on non-voided debit documents.
* `dynamics-gp-get-rm-trx-apply` by `customer-id` with `document-date.from` 60 days ago: payments received recently.
* `customer-balance` against `credit-limit-amount`.

**Step 3: Confirm**

Show the position and the note text (`{reason}`, or a one-sentence reason drafted from recent payments, prefixed with today's date). If a large amount is still over 60 days overdue, say so plainly. Show the user exactly what will be written, field by field, and 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 false. Pass no other fields.
2. Only if that succeeded, call `dynamics-gp-rm-customer-note` once with `customer-id`, the confirmed `note`, `append-to-existing-note` true and `add-date-and-time` true.

If the note fails, tell the user the hold is lifted but the reason was not recorded. Do not retry a failed write automatically. Report the error exactly as returned.

**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 or any other field.

**Validation:**

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