This repository was archived by the owner on Oct 16, 2026. It is now read-only.
Repository navigation
Shorten repeated tool text to win back tools/list headroom - #1470
Merged
Merged
Conversation
The full profile was 3 bytes under its budget, so the next change to add a byte would fail. Text repeated across tools, and reasoning a refusal already gives, is shorter now. Full drops from 210397 to 208495 bytes and core from 96868 to 96207. The shared overwrite text said a call with overwrite: true is confirmation-gated. scene_create and scene_pack_branch take it and cannot ask for a token, so it was false for both. It now says only what is true for every tool that takes it, and resource_create, which is gated, says so in its own entry. A test fails any tool that says it is confirmation-gated and has no confirmation_token.
scene_create's root_name said it defaults to a name derived from the file. Both routes and the schema name the root Root. The root_type entry beside it was never served, because the schema's own text wins, and it still listed the three classes #740 widened, so it is gone. The contract snapshots move for the description text only.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
After #1469 the full
tools/listprofile was 3 bytes under its 210,400 budget, so the next change to add a byte would fail the Python suite. This wins back room by shortening text that repeats across tools, or that gives reasoning the refusal already gives. Nothing a caller needs to call a tool right is gone, and the budgets are unchanged.Where the bytes came from.
confirmation_token, on 15 tools, is now "Single-use token from a dry run of this exact call." It still says single use and exact call._meta.didihas none.select_main_screen,create_if_missing,symbol_typeandboardlose the clause that explained a default or a refusal. The refusal still explains itself. A misspelt symbol, for one, is a 404 whoseretry_withnamescreate_if_missing.overwrite, below.Two descriptions were wrong.
overwritetext said a call withoverwrite: trueis confirmation-gated.scene_createandscene_pack_branchuse that text, and neither can ask for a token, so a caller was told to dry-run for a token that never comes. It now says only what is true of every tool that uses it.resource_create, the one gated tool that used it, says so in its own entry, asscript_createalready did. A new test fails any tool that says it is confirmation-gated and publishes noconfirmation_token. With the old text put back, it fails namingscene_create.scene_create'sroot_namesaid it defaults to a name derived from the file. Both routes and the schema name the rootRoot. Theroot_typeentry beside it was never served, because the schema's own text wins, and it still listed the three classes scene_create can only make Node2D, Node3D and Control roots, so every scene a 2D game needs has to be built through scene_pack_branch and nothing says so聽#740 widened, so it is gone.I checked every other "Defaults to" sentence against its schema default, and the rest agree.
The contract snapshots move for description text only. The reference never said
scene_createwas gated, so no doc changed. The full native suite, the Python suite, the docs validator and the test counts pass locally.