Returns mint and burn requests awaiting a decision, newest first. /dtcc/supply-events
reports issuance that has already happened; this reports issuance that has been
asked for, which is the queue an operations desk actually works.

direction is the field that matters operationally. The registry models two
opposite flows and they place the obligation on different parties:

• requested — a holder asked the registry to mint or burn. The registry decides.
• offered — the registry offered a mint or burn to a holder. The holder decides,
  so an open record in this direction is an item in your queue, not theirs.

Together with operation that covers the registry's four issuance records, which are
four separate resources elsewhere and one filtered collection here:

So mint and burn offers are served here — ?operation=mint&direction=offered — not
by a separate offers endpoint.

Filter direction=offered&status=open to get exactly the set awaiting your action,
and expiresAt[lte] to find what is about to lapse.

A closed request does not tell you how it ended. Accept, reject and cancel are
three distinct choices on the ledger and all three leave status: closed. Worse,
the registry writes the resulting executed and rejected records optionally, so
finding no matching supply event and no rejection does not prove the request was
cancelled. Where the outcome must be established definitively, reconcile against the
holder's positions — a mint that took effect always credits a holding.