Problem
When the client's CreateTaskResult already reports a terminal task, trigger-sampling-request-async skips polling but ignores the returned task.statusMessage, so an immediate failure is reported as "No message".
Where it is pinned
src/everything/__tests__/tasks.test.ts: "does not poll a client task that is already finished when it is created", added in #4978 (Wave 1 of #4857). Each of these tests carries a KNOWN BUG marker: it asserts the current, wrong behavior, so the fix has to change it.
Expected
The tool reports the status message carried by the task it got back at creation.
Done when
- The behavior above is fixed, in the legacy-era (2025-11-25) server on SDK 1.x.
- The pinning tests assert the correct behavior, and their
KNOWN BUG markers are gone.
- The per-file 90% coverage gate still passes.
Problem
When the client's
CreateTaskResultalready reports a terminal task,trigger-sampling-request-asyncskips polling but ignores the returnedtask.statusMessage, so an immediate failure is reported as "No message".Where it is pinned
src/everything/__tests__/tasks.test.ts: "does not poll a client task that is already finished when it is created", added in #4978 (Wave 1 of #4857). Each of these tests carries aKNOWN BUGmarker: it asserts the current, wrong behavior, so the fix has to change it.Expected
The tool reports the status message carried by the task it got back at creation.
Done when
KNOWN BUGmarkers are gone.