chore(stlc): seal custom-code tracking files

[kernel-internal]

Opened by the stlc generate workflow. The last build on main re-sealed custom code and rewrote the tracking files under stainless/custom-code/; merging brings this repo back in sync with the SDK repos.

---

Note

Low Risk
Metadata-only updates to Stainless custom-code tracking files with no application or security logic touched.

Overview
Updates stainless/custom-code seal metadata for the Go and TypeScript SDKs after the latest main build re-sealed custom code.

In both 2026-08-04T13-39-02-159Z-custom-code.json files, only the base and integrated commit hashes change; filename and branch stay the same. This keeps the repo aligned with the SDK repos’ current sealed custom-code state—no runtime or API changes.

^{Reviewed by Cursor Bugbot for commit ca6ddb1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

-->

✱ stlc build

✅ go code · compare

Your SDK build was successful.

generate ✅ → bootstrap ✅ → format ✅

112 files generated at ddd5506 (pushed)

go get github.com/kernel/hypeman-go-staging@ddd55067335f7af291161b0681dd5d9fc0b94034

✅ typescript code · compare

Your SDK build was successful.

generate ✅ → bootstrap ✅ → format ✅

134 files generated at 53a5ba4 (pushed)

Diagnostics: 💡 0 new / 5 total note

Level	Code	Message	Targets

Build metadata

Build	bd_766rrtCz-warm-rut
Timestamp	2026-08-10T20:10:54.725Z
stlc	8413509
Spec hash	1fced2594ced
Config hash	9125eb22cb4c

---

This comment is auto-generated by stlc and is kept up to date as you push.
If you push new commits, re-run this workflow to update this comment.
Last updated: 2026-08-10 20:11:13 UTC