[Cross-Repo] Wire up max_op_return_outputs from GetInfoResponse

[arkanaai]

Context

arkd PR #987 was merged (2026-03-19T14:55:44Z) adding max_op_return_outputs to the gRPC GetInfoResponse (proto field 21) and OpenAPI spec.

arkd change: api-spec/protobuf/ark/v1/service.proto

int64 max_op_return_outputs = 21;

OpenAPI: maxOpReturnOutputs added to GetInfoResponse schema.

What needs to change in ts-sdk

• Add maxOpReturnOutputs to the GetInfo() response/Info type
• Use the server-provided value when enforcing the client-side OP_RETURN limit (currently hardcoded in PR arkTransaction: support two OP_RETURN outputs #366)

Note: PR #366 (support two OP_RETURN outputs) is in-flight and currently hardcodes the limit to 2. The server default is 3. Once this field is wired up from /info, the client will automatically respect the server's configured limit, eliminating the mismatch.

Impact

Without this, the client enforces a hardcoded OP_RETURN limit that may diverge from the server's configured value, causing false rejections or silent over-allowances.

---

Opened by: Arkana cross-repo impact analyzer
Trigger: arkade-os/arkd@0a5e8d1a merged to master