docs(zammad): state why the ruby apply scripts have no unit mirror

The lint wants either a mirrored unit test per role script or a
nocheck: mirrored-unit-test directive with a reason.

ai_provider.rb runs in the Zammad console and writes through Setting, whose
validator pings the gateway on save, so the round trip against the live
provider is the entire contract; a mocked transport would assert the mock.
mcp_bot.rb works against User, Role and Token and depends on the
before_create hook the live models supply, none of which is callable outside
the Zammad image.

There is no tests/unit/ruby tree for such a mirror to live in.

The first reason is confirmed by this session: writing the AI provider
setting is itself the reachability proof, because Setting.set pings.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

roles/web-app-zammad/files/ruby/apply/ai_provider.rb

@@ -1,3 +1,7 @@
+# nocheck: mirrored-unit-test - runs in the Zammad console and writes through Setting,
+# whose validator pings the gateway on save; the round trip against the live provider is
+# the entire contract
+#
 # Bind Zammad Smart Assist to the platform LiteLLM gateway.
 #
 # Order matters: ai_provider is the boolean "a provider is configured", and its

roles/web-app-zammad/files/ruby/apply/mcp_bot.rb

@@ -1,3 +1,7 @@
+# nocheck: mirrored-unit-test - runs in the Zammad console against User, Role and Token,
+# and depends on the before_create hook the live models supply; none of it is callable
+# outside the Zammad image
+#
 # Give the MCP adapter a read-only Zammad agent and pin its API token.
 #
 # Zammad overwrites any token handed to create with a generated one, but only