[jsyolo]

and revealing/affording further API navigation via hypermedia controls (e.g. links)

I haven't a hard time understanding the utility of this, the article gives an example (removing ability of transfers), but why would a webpage need those hypermedia controls in the response if they are already encoded in the API of the business logic? for ex: The business logic tells the presentation layer, "if X field is true, disable transfers button".

[recursivedoubts]

The presentation layer needs to interpret the business layer information in your example. This couples the two together if, for example, the form of the business data changes.

This is in contrast to hypermedia where the client (a browser) simply sees the new hypermedia and renders it. In this case, the client is decoupled from the particulars of the business logic.

This is due to the uniform interface of REST. See https://htmx.org/essays/hateoas/