Repository navigation
feat: add board defaults for model, reasoning effort and preset - #43
Merged
Merged
Conversation
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
Add board-level defaults for the model, reasoning effort, and Agent preset used by newly created tasks.
defaultModel(includingreasoningEffort) anddefaultPresetIdwith the ledger; preserve them across restarts and JSON import/export.taskboard_create, without rewriting existing tasks when settings change.nullcreate payloads, rather than accidentally inheriting the board default again.Verification
npm run typechecknpm test -- --maxWorkers=2— 28 test files, 378 tests passednpm run buildgit diff --checkSeven new tests cover settings UI save/reset behavior, unavailable catalogs, template/default precedence, explicit deployment-default overrides, Host route and tool creation, settings validation, and import behavior. The existing persistence test also now covers model/effort/preset defaults.
The first full run at default worker concurrency hit three scheduler lifecycle timing failures. Those tests passed when run independently (both the working tree and untouched HEAD baseline), and the complete suite passed with two workers. No scheduler code was changed.
Live Desktop plugin reload and real-browser visual verification were not performed; UI interactions were verified in jsdom.