The vitest-backed helpers every consuming SDK's suite carried as a
hand-maintained twin of this package's own — the type-breach and
partial-double boundaries, the logger and setting-store doubles, the
transport spy, the fetch Response mock, the HttpError factories
and the native-Temporal clock spies. It runs inside the consumer's
vitest process: vitest is imported here and declared nowhere,
because the SDKs install this package as a PRODUCTION dependency of
the Homey apps, and a peer — optional or not — would put the test
framework on the device. The root barrel never re-exports this
module for the same reason.
The mechanism the SDK family shares: the session lifecycle and request pipeline, the redaction-seated transport, the observability shells, the resilience primitives, the error hierarchy and the two decorators — everything a consuming SDK's PRODUCTION code reaches. The vitest-backed test helpers live on their own
./testingsubpath and are never re-exported from here.