Edge: reserve GLM reasoning budget for skill outputs#15
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
message.contentafter its reasoning phase.output.summary,output.translation, etc.; the PR fix(web): render per-skill invoke outputs #13 frontend renderer remains the canonical display path.chat_template_kwargs.enable_thinking=false.Production evidence
After PR #14 deployed, the
[object Object]bug was gone but a production invoke with the old small budget returned leaked reasoning text asoutput.summarybecause GLM returnedcontent: nullafter exhausting the skill budget. Raw provider tests showed the same prompt emits clean final content once the request has ~1536 completion tokens available.Verification
pnpm -F @apogee/edge typecheckpnpm -F @apogee/edge buildpnpm -F @apogee/edge testScope
No changes to receipt minting, ownership checks, policy enforcement, status gates, auto-promote logic, Pilot endpoint, Aurora/Vesper/Helix, or heartbeat runtime.