feat: Divi module catalog, attribute paths, short form and lit/divi-catalog

Adds per-path attribute kind (text/richtext/code/url/image/color/enum/
onoff/number/list/icon), derived from Divi's field component metadata
where an attribute path names one unambiguously (module.paths() itself
is unchanged; kinds() is a new, separate lookup exposed as path_kinds
on lit/divi-catalog's module detail). This is not in the task-4 brief;
it is added because 2b's sanitization routing (ruling R3) needs a
metadata-derived field kind per attribute path. Verified live against
the full 100-module catalog (564/4358 paths resolve a kind; the rest
default to "unknown" and fall back to 2b's key-name routing).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01At3V6SjwbMe6eMzVGW3Hs7

src/Integrations/Divi/DiviIntegration.php

@@ -0,0 +1,41 @@
+<?php
+
+declare(strict_types=1);
+
+namespace LIT\MCP\Integrations\Divi;
+
+use LIT\MCP\Integrations\Divi\Schema\DiviCatalogAbility;
+use LIT\MCP\Integrations\Divi\Schema\DiviModules;
+use LIT\MCP\Integrations\Integration;
+use LIT\MCP\Integrations\WordPress\Schema\ContentSchema;
+
+/**
+ * Divi 5 pages (spec §5, Etappe 2). Only available when the Divi 5 builder is loaded
+ * (spec §2 principle 4); Divi 4 is never edited (spec §3.4).
+ */
+final class DiviIntegration implements Integration
+{
+    private DiviModules $modules;
+
+    public function __construct(private ContentSchema $schema)
+    {
+        $this->modules = new DiviModules();
+    }
+
+    public function id(): string
+    {
+        return 'divi';
+    }
+
+    public function isAvailable(): bool
+    {
+        return DiviModules::isAvailable();
+    }
+
+    public function abilities(): array
+    {
+        return [
+            new DiviCatalogAbility($this->modules),
+        ];
+    }
+}