test: remove misleading third test case from task.statusMessage tests

The third test asserted that a stale intermediate statusMessage is preserved
through storeTaskResult — which tests InMemoryTaskStore internals, not the
bug. The two remaining cases are sufficient regression coverage.

Author: jirispilka

tests/unit/task.statusMessage.test.ts

@@ -52,21 +52,4 @@ describe('Task statusMessage after terminal transition', () => {
         expect(task!.status).toBe('failed');
         expect(task!.statusMessage).toBe('my-tool: failed');
     });
-
-    it('should show stale statusMessage when final updateTaskStatus is skipped (documents the bug)', async () => {
-        const store = new InMemoryTaskStore();
-        const taskId = await createWorkingTask(store);
-
-        await store.updateTaskStatus(taskId, 'working', 'Starting the crawler.');
-
-        // No final updateTaskStatus — this is the buggy path
-        await store.storeTaskResult(taskId, 'completed', {
-            content: [{ type: 'text', text: 'result data' }],
-        });
-
-        const task = await store.getTask(taskId);
-        expect(task!.status).toBe('completed');
-        // statusMessage is stale — still the intermediate progress message
-        expect(task!.statusMessage).toBe('Starting the crawler.');
-    });
 });