_Disclaimer: I've written the following with Claude. I encountered the bug running STH and the AI-gateway locally. I checked an env in prod but it couldn't replicate the bug there. The proposed fixed worked for me._ ### What is the current *bug* behavior? When creating a message model spec using the GenAI option in the wizard, no toast notifications are shown for the async AI task (e.g. "Task in progress", "Task completed"). The AI generation itself works correctly in the background, but the user gets no visual feedback and must manually refresh the page to see the generated data model. ### What is the expected *correct* behavior? After submitting the GenAI wizard, the user should see toast notifications indicating the task status: "Task in progress" while the AI gateway is generating, and "Task completed" (or "Task failed") when done. This works correctly in v4.2.0 production. ### Context information * Version info: post-v4.2.0, any version containing commit `9c5059711` * Environment: local dev, but will affect all environments once deployed * Resource links: N/A ### Steps to reproduce 1. Create a new message model spec using the "AI Generate" option in the wizard 2. Enter a description and click "Create message model" 3. Observe that you are redirected to the canvas, but no toast notification appears 4. The AI task completes silently in the background — only visible after a page refresh ### Relevant logs and/or screenshots The messenger consumer processes the task successfully: ``` INFO [messenger] Received message App\Message\InvokeAi INFO [http_client] Request: "POST http://host.docker.internal:2024/call/GenerateSpecificationFromDescription" INFO [http_client] Response: "200 ..." 11.21s INFO [messenger] App\Message\InvokeAi was handled successfully (acknowledging to transport). ``` But the `task` query parameter is absent from the canvas URL, so `TaskStatusComponent` never starts polling. ### Possible fixes The bug was introduced in commit `9c5059711` ("Canvas refactor: use specVersionId instead of messageId/rootNodeId everywhere"). The refactor changed `WizardMessageTreeviewComponent` (step-2) to redirect from `/message-model/wizard/step-2/:id` to `/canvas` with explicit `queryParams`, but only includes `panes` — dropping the `task` query parameter that `WizardCreateComponent` passes on line 394. **File:** `frontend/src/app/ui/message-model/wizard-message-treeview/wizard-message-treeview.component.ts` **Fix:** Read the `task` query param via `injectQueryParam('task', null)` and forward it in the `queryParams` object when navigating to `/canvas` (around line 43).