Date: 2026-09-19.
Baseline: the supplied complete Repomix representation of typesafe_sdk 0.4.0.
Goal
Extract the TypeSafe provider-specific API client into a standalone package
without carrying the provider-neutral semantic/evaluation framework that will
continue in system_one_sdk.
Mechanical transformations
TypeSafeSDKprovider modules ->TypeSafeAPISDK.:typesafe_sdk->:typesafe_api_sdk.- package/repository ->
typesafe_api_sdk. - generated code path ->
lib/typesafe_api_sdk/generated. - codegen source path ->
codegen/typesafe_api_sdk/codegen. - maintenance Mix tasks ->
typesafe_api.*. - user agent ->
typesafe-api-sdk/<version>.
Intentional code reduction
The implementation removes the 0.2-0.4 semantic framework rather than renaming
it into this provider package. See guides/extraction-boundary.md and
SOURCE_MAP.md.
Runtime architecture
Pristine remains the only HTTP/runtime substrate. TypeSafeAPISDK owns provider configuration, TypeSafe auth/header policy, TypeSafe retry/status classification, generated operations, and TypeSafe wire response normalization.
No second HTTP stack, retry engine, global process, local inference runtime, or provider-neutral evaluation system is introduced.
Verification state
Static repository checks were executed during assembly. BEAM, generated-source,
Hex, and live checks remain target-host gates because Elixir/Erlang/Mix were not
available in the delivery environment. HANDOFF.md is authoritative for those
steps.