chore(deps): bump @robosystems/client to ^1.13.0

[jfrench9]

Summary

Adopt @robosystems/client 1.13.0. It fixes every SSE-backed flow (operation monitoring, streaming queries, and the console's operator queries) going dead once a tab has lived past the session's first JWT refresh (~25 min): the SDK's clients singleton captured the JWT at construction, the backend revokes the previous JWT on every refresh, and the stream endpoint authenticates the JWT from the URL — so REST calls kept working through core's interceptor while every stream attach 401'd. Confirmed in RoboSystems prod API logs on 2026-08-29.

In 1.13.0 the SSE-backed clients resolve the credential on every connect through the tokenProvider core already registers via setSDKClientConfig, and OperatorClient follows a queued run over /v1/operations/{id}/status when the stream cannot open, so the result is never lost. Nothing in this app changes — the fix lives in the package (RoboFinSystems/robosystems-typescript-client#206).

Changes

• package.json — @robosystems/client ^1.12.2 → ^1.13.0.
• package-lock.json — resolves to 1.13.0.

Deploy Notes

None — no env vars, no CloudFormation, no API version requirement (the API was already correct; this is the client catching up). The fix reaches users with the next app release; until then a tab open longer than ~25 minutes still fails its first stream-backed action and a page refresh remains the workaround.

Testing

• npm run test:all (test → format → lint:fix → typecheck → cf-lint): 368 tests passed across 48 files, all checks clean.