chore(stlc): seal custom-code tracking files - #456
Open
agentex-sdk-sync[bot] wants to merge 1 commit into
Open
agentex-sdk-sync[bot] wants to merge 1 commit into
agentex-sdk-sync[bot] wants to merge 1 commit into
Conversation
agentex-sdk-sync
Bot
force-pushed
the
stlc/seal-tracking
branch
6 times, most recently
from
September 27, 2026 18:20
df57889 to
b0e9a9a
Compare
agentex-sdk-sync
Bot
force-pushed
the
stlc/seal-tracking
branch
from
September 28, 2026 00:50
b0e9a9a to
1cfeb5e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated by the stlc generate workflow:
stlc buildre-sealed custom code (after a spec change onmain, or after absorbing custom code that landed on a staging repo out of band), updating the tracking files understainless/custom-code/. Merging brings the config repo in sync with the SDK repos. Safe to merge — tracking-files-only commits are skipped by this workflow, so it won't trigger another build.The PR appears safe to merge. No new issue is supported by the changed tracking data.
Summary
The PR refreshes the sealed custom-code commit references for the Python and TypeScript SDKs. The
stlctracking files now point to newer base and integrated commits formain.Diagram
sequenceDiagram participant Workflow as stlc generate workflow participant Build as stlc build participant Tracking as custom-code tracking files participant SDK as SDK staging repos Workflow->>Build: Run generation Build->>Tracking: Read base and integrated commits Build->>Build: Replay the base-to-integrated custom-code diff Build->>Tracking: Write updated seal metadata Workflow->>SDK: Check integrated commits reached main SDK-->>Workflow: Confirm commit ancestry Workflow->>Tracking: Commit the resealed filesReviews (8) · Last reviewed commit: "chore(stlc): seal custom-code tracking f..."