chore(deps): Bump @aindy/ui-kit from 2.1.0 to 2.1.1 in /platform

[dependabot]

Bumps @aindy/ui-kit from 2.1.0 to 2.1.1.

Release notes

Sourced from @​aindy/ui-kit's releases.

@​aindy/ui-kit v2.1.1

What's Changed

• fix: export _resetEnvelopeDetection + ENVELOPE_HEADER; document the envelope latch (runtime FR-45) by @​Masterplanner25 in Masterplanner25/aindy-ui-kit#5
• fix: land FR-47 on main (per-call timeout) + release 2.1.1 by @​Masterplanner25 in Masterplanner25/aindy-ui-kit#7

Full Changelog: Masterplanner25/aindy-ui-kit@v2.1.0...v2.1.1

Changelog

Sourced from @​aindy/ui-kit's changelog.

2.1.1 — 2026-09-26

Pairs with any aindy-runtime>=2.6.0. Additive except one narrowed error mapping (below).

Added — a per-call request timeout, timeoutMs (runtime FR-47)

Every request aborted at 30 s with no override. Creating an agent run is one synchronous request that includes planning (an LLM call, routinely 30–40 s), so the console reported a failure for a run the server created seconds later, and the owner submitted again: two duplicate runs in one morning. request(), requestAbsolute() and everything built on them now take timeoutMs (default DEFAULT_TIMEOUT_MS = 30000, unchanged). 0 arms no kit timer. An invalid value falls back to the default, never to "no timeout". The 503 Retry-After retry keeps the caller's value. timeoutMs is not forwarded to fetch.

Changed — a 408 means the kit's own timer fired

Previously ANY abort became ApiError(408, "Request timed out after 30 seconds."), including an abort from the caller's own signal, which is untrue. A caller-initiated abort now rejects with the AbortError itself. The 408 message names the timeout actually used. A consumer that caught ApiError(408) to detect its OWN aborts must check err.name === "AbortError" instead.

Added — _resetEnvelopeDetection and ENVELOPE_HEADER exported from the package entry (runtime FR-45)

Both were declared in the published .d.ts but not exported from dist/index.js, so a consumer's tests could not reset the envelope latch between cases. The only workaround was test ordering. No behaviour change.

Changed — unwrapEnvelope's latch is documented where it is used

After the first stamped response, unwrapEnvelope is a no-op for everything, which is not what its name says. The README and the function's doc comment now say so, and say that the cure for an unstamped envelope is on the server (runtime FR-45).

Commits

• 7bff4fe Merge pull request #7 from Masterplanner25/feat/fr47-per-call-timeout-to-main
• 00265f9 release: 2.1.1 (runtime FR-45 exports + FR-47 per-call timeout)
• fc57cf1 feat: per-call request timeout (timeoutMs); 408 only when the kit's timer fir...
• 5fbbfdd Merge pull request #5 from Masterplanner25/fix/fr45-export-envelope-reset
• 3b94ede fix: export _resetEnvelopeDetection + ENVELOPE_HEADER from the entry; documen...
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)