From 86f962ee7d4bf34f213217933c7a896d9226b2b0 Mon Sep 17 00:00:00 2001
From: mika kuns <mika.kuns@fb-tuning.de>
Date: Thu, 6 Aug 2026 11:07:48 +0200
Subject: [PATCH] test(installer): prove RegisterMcpStep still resolves from
 the DI container

---
 .../StepDiRegistrationTests.cs                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 tests/ClaudeDo.Installer.Tests/StepDiRegistrationTests.cs

diff --git a/tests/ClaudeDo.Installer.Tests/StepDiRegistrationTests.cs b/tests/ClaudeDo.Installer.Tests/StepDiRegistrationTests.cs
new file mode 100644
index 00000000..6610947f
--- /dev/null
+++ b/tests/ClaudeDo.Installer.Tests/StepDiRegistrationTests.cs
@@ -0,0 +1,21 @@
+using ClaudeDo.Installer.Steps;
+using Microsoft.Extensions.DependencyInjection;
+
+namespace ClaudeDo.Installer.Tests;
+
+public sealed class StepDiRegistrationTests
+{
+    // RegisterMcpStep is registered type-based (App.xaml.cs) and has an optional
+    // Func<InstallerWorkerConfig> constructor parameter. A compile-time build proves
+    // nothing here — if the container refused to honour the default value, the
+    // installer would only blow up at runtime, where it cannot be smoke-tested.
+    [Fact]
+    public void RegisterMcpStep_resolves_from_the_container_without_a_config_loader()
+    {
+        var sp = new ServiceCollection()
+            .AddSingleton<RegisterMcpStep>()
+            .BuildServiceProvider();
+
+        Assert.NotNull(sp.GetRequiredService<RegisterMcpStep>());
+    }
+}