You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TaskName omits forecast. Server accepts <task>forecast</task> (src/utils/messaging.ts:106), but TASK_NAMES / the TaskName literal don't include it, so create(task="forecast") isn't typeable. (tasks.forecast() prompt-path still works.) Add for parity.
Fixtures give false confidence on precontext.conftest docstring claims precontext is always {name,result}, but TOOL_CALL has no precontext and the raw-toolcall-in-precontext case is untested (see the strict-validation crash issue). Add a mixed-shape fixture.
task/guard injected as a separate leading system message.prepare() prepends a new {role:"system"}; if the caller already has a system message there are now two. Server extraction reads the first (works today) but is brittle — prefer merging tags into an existing system message.
Housekeeping — minor issues (low severity)
TaskNameomitsforecast. Server accepts<task>forecast</task>(src/utils/messaging.ts:106), butTASK_NAMES/ theTaskNameliteral don't include it, socreate(task="forecast")isn't typeable. (tasks.forecast()prompt-path still works.) Add for parity.precontext.conftestdocstring claims precontext is always{name,result}, butTOOL_CALLhas no precontext and the raw-toolcall-in-precontext case is untested (see the strict-validation crash issue). Add a mixed-shape fixture.task/guardinjected as a separate leading system message.prepare()prepends a new{role:"system"}; if the caller already has a system message there are now two. Server extraction reads the first (works today) but is brittle — prefer merging tags into an existing system message.