Conversation
|
Verification footprint for 799 authored additions; 29,488 generated additions; 2 deletions. Generated classifications and destructive regeneration procedure are recorded in the shared API2 receipt and maintainer guide. Generated lines are not a claim of native/runtime proof; both SDK CI and API2's local-native acceptance passed separately. Raw canonical numstat (additions, deletions, path): |
Final source footprint and review receiptThe approved first-party SDK slice is implemented. Existing SDK entrypoints remain intact; the new namespaces are experimental. No SDK release, deployment or merge was performed.
Measured with the canonical text/Myers/no-renames/no-indent-heuristic numstat command from the living document. Generated ownership: API2's generated contract; each SDK's client/manifest/coverage/vectors; Node's existing legacy-package README/package projection. All native transport, tests, documentation and receipt additions count as authored. The conservative historical authored lower bound is now 59,141, not a fully reconciled program total or an additional footprint authorization. The last API2 increment is the targeted cold-artifact test-budget correction and its CI receipt; production and generated SDK bytes are unchanged. All council findings have dispositions and fail-first evidence in API2's All three exact-head CI runs are now green: API2 36161865722, Node 36136692611, and Go 36153479049. The prescribed API2 watcher finished with all checks passed on September 25 at 17:34 UTC. The generator suite passed in 2.8 minutes under coverage and the actual native SDK server canary in 30.5 seconds. API2 changed-line coverage is 93.62% (514/549); the unchanged 80% gate passed. No review threads were open at this final checkpoint. The green API2 run also reports two already nonblocking cloud-image Before landing: API2 main has since advanced by one Slack-workflow/test commit, Producer first, then consumers: |
Why
Exercise the API2 canonical contract in a maintained SDK, rather than treating a generated OpenAPI probe as the finished product. This adds an experimental low-level client without replacing existing upload, tus or polling APIs.
Changes
contract.json.Transloadit.contract()and the@transloadit/node/contractentrypoint. Preserve existing methods, endpoint prefixes, timeouts and client identification.Scope and verification
The namespace is experimental and single-attempt: legacy
gotRetry/maxRetriespolicies are not inherited. It is not a lifecycle/tus replacement or SDK release. Types describe wire shapes, not a complete runtime JSON Schema validator.Native wire tests pass, including fail-first council regressions. Final
yarn checkandyarn verify:fullpass after the second council review reported no issues. Exact-head CI is fully green for30cb8807dab7b8098ba8eb5c53635c84e08b98cc, including Node 20/22/24, both verification jobs, E2E, build, release dry run, Supabase Edge and the Next.js fixture.API2's cross-repository canary fetches exact source commits and hashes, deletes/regenerates outputs, strict-compiles with
exactOptionalPropertyTypes, and exercises owned devdock resources. It passes with this native source, including built-in Template list/get and multipart file digests. No production credentials are used by that canary.Generated files must be changed through API2
contracts sdks --target typescript, never edited here. Maintainer pointers and the source contract SHA are committed.Companion PRs
Land the producer first. No SDK release or deployment is part of these PRs.
The shared review checklist, findings/dispositions and footprint receipt are maintained in API2's
repodocs/prompts/2026-09-25-sdk-contract.md, alongside the canonical living program document. There were no open GitHub review threads at the final SDK review checkpoint.