[Node.js] deserialize fails because Buffers are converted to arrays

[0xrouss-miden]

Packages versions

@miden-sdk/miden-sdk@0.16.0-rc.5

Bug description

In Node.js, the SDK wrapper converts Buffer and Uint8Array arguments into plain arrays.
AuthSecretKey.deserialize() expects a Buffer, so it fails through the public SDK export.

This also affects Word.deserialize(). Calling the same method through getNativeModule() works because it bypasses the wrapper.

How can this be reproduced?

import { AuthSecretKey } from "@miden-sdk/miden-sdk";

const key = AuthSecretKey.rpoFalconWithRNG(new Uint8Array(32));
const base64 = key.serialize().toString("base64");

AuthSecretKey.deserialize(Buffer.from(base64, "base64"));

Relevant log output

Failed to get Buffer pointer and length

[Mabolla]

I'd like to work on this if it's available.

My proposed approach is to adjust the Node.js wrapper so binary inputs passed to deserialization methods remain compatible with the native binding instead of being converted into plain arrays. I would cover both Buffer and Uint8Array inputs for AuthSecretKey.deserialize() and Word.deserialize(), while checking that the browser-facing behavior remains unchanged.

I would also add regression tests exercising these methods through the public package export, rather than through getNativeModule().

Would this scope be appropriate, and may I take the issue?