Repository navigation
Correct the documented limit defaults after unlimited limits and the execution-only graph - #125
Merged
Merged
Conversation
…execution-only graph
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.
Change
Follow-up to #121 and #124: a few docs still described the old limit defaults and behavior.
docs/resource-limits.md: core node and graph timeouts are now unlimited by default (the table still said 60 seconds and 5 minutes). Adds a row for what reaching a limit does (onLimit), splits the token budget row to showmaxTokens, and says whymaxTokensis not a hard cost ceiling (it counts reported usage as executions settle).README.md:startBraidrun untilsetLimitsraises it; failing withGRAPH_TIMEOUTapplies tobraid()andonLimit: "fail".ROADMAP.md: ticks Core: replace the schedule/execution split with an execution-only graph #113 in RSI Mode.Version-specific lines ("The 0.5 API is experimental", the previous-release link) are left to the release preparation.
Validation
Documentation only; anchors (
#migrating-from-05-to-06,#limits,#milestones) checked against the current docs.documentation).