docs: fix dead Haystack docs links and nightly badge

README.md

@@ -8,7 +8,7 @@ This is the repository where we keep all the Haystack tutorials 📓 👇 These
 
 To contribute to the tutorials, please check out our [Contributing Guidelines](./Contributing.md).
 
-[![Run Tutorials Nightly](https://github.com/deepset-ai/haystack-tutorials/actions/workflows/nightly.yml/badge.svg)](https://github.com/deepset-ai/haystack-tutorials/actions/workflows/nightly.yml)
+[![Run Tutorials Nightly](https://github.com/deepset-ai/haystack-tutorials/actions/workflows/run_tutorials.yml/badge.svg)](https://github.com/deepset-ai/haystack-tutorials/actions/workflows/run_tutorials.yml)
 [![Publish tutorials on Haystack Home](https://github.com/deepset-ai/haystack-tutorials/actions/workflows/publish_tutorials.yml/badge.svg)](https://github.com/deepset-ai/haystack-tutorials/actions/workflows/publish_tutorials.yml)
 
 ## Tutorials

tutorials/33_Hybrid_Retrieval.ipynb

@@ -266,7 +266,7 @@
    "source": [
     "### 5) Visualize the Pipeline (Optional)\n",
     "\n",
-    "To understand how you formed a hybrid retrieval pipeline, use [draw()](https://docs.haystack.deepset.ai/docs/drawing-pipeline-graphs) method of the pipeline. If you're running this notebook on Google Colab, the generate file will be saved in \"Files\" section on the sidebar."
+    "To understand how you formed a hybrid retrieval pipeline, use [draw()](https://docs.haystack.deepset.ai/docs/visualizing-pipelines) method of the pipeline. If you're running this notebook on Google Colab, the generate file will be saved in \"Files\" section on the sidebar."
    ]
   },
   {

tutorials/36_Building_Fallbacks_with_Conditional_Routing.ipynb

@@ -46,7 +46,7 @@
     "### Prepare the Colab Environment\n",
     "\n",
     "- [Enable GPU Runtime in Colab](https://docs.haystack.deepset.ai/docs/enabling-gpu-acceleration)\n",
-    "- [Set logging level to INFO](https://docs.haystack.deepset.ai/docs/setting-the-log-level)"
+    "- [Set logging level to INFO](https://docs.haystack.deepset.ai/docs/logging#changing-the-log-level)"
    ]
   },
   {

tutorials/39_Embedding_Metadata_for_Improved_Retrieval.ipynb

@@ -34,7 +34,7 @@
     "### Prepare the Colab Environment\n",
     "\n",
     "- [Enable GPU Runtime in Colab](https://docs.haystack.deepset.ai/docs/enabling-gpu-acceleration)\n",
-    "- [Set logging level to INFO](https://docs.haystack.deepset.ai/docs/setting-the-log-level)"
+    "- [Set logging level to INFO](https://docs.haystack.deepset.ai/docs/logging#changing-the-log-level)"
    ]
   },
   {

tutorials/47_Human_in_the_Loop_Agent.ipynb

@@ -176,7 +176,7 @@
    "metadata": {
     "id": "5c2e21f4-b84f-4411-a5f1-7312afd44188"
    },
-   "source": "## Instantiate the Agent\n\nInstantiate the [`Agent`](https://docs.haystack.deepset.ai/docs/agent) with multiple tools. To add human-in-the-loop behavior, create a [`ConfirmationHook`](https://docs.haystack.deepset.ai/docs/confirmationhook) that assigns each tool a **confirmation strategy**, and register it on the Agent's `before_tool` hook point."
+   "source": "## Instantiate the Agent\n\nInstantiate the [`Agent`](https://docs.haystack.deepset.ai/docs/agent) with multiple tools. To add human-in-the-loop behavior, create a [`ConfirmationHook`](https://docs.haystack.deepset.ai/docs/human-in-the-loop) that assigns each tool a **confirmation strategy**, and register it on the Agent's `before_tool` hook point."
   },
   {
    "cell_type": "code",
@@ -194,7 +194,7 @@
    "metadata": {
     "id": "4a1e1fc9-bf38-4207-a50f-dded827c4ae6"
    },
-   "source": "### Explanation\n\nThe `ConfirmationHook` runs at the Agent's `before_tool` hook point, after the model requests a tool call but before the tool actually runs. For each requested tool, it looks up the matching entry in `confirmation_strategies`. A key can be a single tool name, a tuple of tool names sharing one strategy, or the wildcard `\"*\"` which applies to any tool without a more specific entry.\n\nEach [`BlockingConfirmationStrategy`](https://docs.haystack.deepset.ai/docs/blockingconfirmationstrategy) defines when and how the agent asks for confirmation before executing a tool. The `confirmation_policy` decides *when* to ask:\n\n* **`AlwaysAskPolicy`** – Always asks for approval before running.\n* **`NeverAskPolicy`** – Executes automatically without user confirmation.\n* **`AskOncePolicy`** – Asks once per tool, remembers approval for future runs.\n\nThe `confirmation_ui` decides *how* to ask:\n\n* `RichConsoleUI` for colorized and more aesthetic prompts.\n* `SimpleConsoleUI` for basic prompts.\n\n\nBoth UIs will present three options:\n\n- **y**: Proceed with the tool execution as planned\n- **n**: Cancel the tool execution; agent will try alternative approaches\n- **m**: Edit the tool parameters before execution\n\n**NOTE**: Custom UIs and Policies can also be implemented by following the respective `ConfirmationUI` and `ConfirmationPolicy` protocols. This allows full flexibility for domain-specific workflows."
+   "source": "### Explanation\n\nThe `ConfirmationHook` runs at the Agent's `before_tool` hook point, after the model requests a tool call but before the tool actually runs. For each requested tool, it looks up the matching entry in `confirmation_strategies`. A key can be a single tool name, a tuple of tool names sharing one strategy, or the wildcard `\"*\"` which applies to any tool without a more specific entry.\n\nEach [`BlockingConfirmationStrategy`](https://docs.haystack.deepset.ai/docs/human-in-the-loop) defines when and how the agent asks for confirmation before executing a tool. The `confirmation_policy` decides *when* to ask:\n\n* **`AlwaysAskPolicy`** – Always asks for approval before running.\n* **`NeverAskPolicy`** – Executes automatically without user confirmation.\n* **`AskOncePolicy`** – Asks once per tool, remembers approval for future runs.\n\nThe `confirmation_ui` decides *how* to ask:\n\n* `RichConsoleUI` for colorized and more aesthetic prompts.\n* `SimpleConsoleUI` for basic prompts.\n\n\nBoth UIs will present three options:\n\n- **y**: Proceed with the tool execution as planned\n- **n**: Cancel the tool execution; agent will try alternative approaches\n- **m**: Edit the tool parameters before execution\n\n**NOTE**: Custom UIs and Policies can also be implemented by following the respective `ConfirmationUI` and `ConfirmationPolicy` protocols. This allows full flexibility for domain-specific workflows."
   },
   {
    "cell_type": "markdown",