Reseal SDK custom code on main

[sjmiller609]

Summary

Updates the Go and TypeScript custom-code tracking files after reconciling the new staging repositories with their sealed SDK histories.

Validation

• real stlc build --no-lint completed for Go and TypeScript
• Go bootstrap, lint, and tests passed
• TypeScript bootstrap, lint, build, and tests passed (377 passed, 88 skipped)
• both SDK worktrees were clean before the deterministic push build
• TypeScript pushed successfully to staging main; the prior generation failure was caused by the initial staging-history reconciliation

[github-actions]

-->

✱ stlc build

✅ go code · compare

Your SDK build was successful.

generate ✅ → bootstrap ✅ → format ✅

112 files generated at 3d2b0a5 (pushed)

go get github.com/kernel/hypeman-go-staging@3d2b0a558b461ac7987d04c47f0df8456ff61141

✅ typescript code · compare

Your SDK build was successful.

generate ✅ → bootstrap ✅ → format ✅

134 files generated at ea00702 (pushed)

Diagnostics: 💡 0 new / 5 total note

Level	Code	Message	Targets

Build metadata

Build	bd_765Ghj9y-tough-shutter
Timestamp	2026-08-06T00:54:55.322Z
stlc	8413509
Spec hash	33da8d5c02bb
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-06 00:55:11 UTC

[sjmiller609]

Superseded by the successful generation workflow’s canonical seal-back PR #357.