feat: adapter-level Divi release lock, content-create and site status

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

src/Plugin.php

@@ -25,6 +25,7 @@ use LIT\MCP\Integrations\Core\CoreIntegration;
 use LIT\MCP\Integrations\Divi\DiviIntegration;
 use LIT\MCP\Integrations\Divi\Library\LibraryAccess;
 use LIT\MCP\Integrations\Divi\Release\DiviToolGate;
+use LIT\MCP\Integrations\Divi\Release\ReleaseResolver;
 use LIT\MCP\Integrations\Divi\ThemeBuilder\ThemeBuilderAccess;
 use LIT\MCP\Integrations\IntegrationRegistry;
 use LIT\MCP\Integrations\Media\MediaIntegration;
@@ -73,6 +74,11 @@ final class Plugin
         (new ChangeLogInstaller($changeLog))->maybeInstall();
         (new ChangeLogCleanup($changeLog, $limits))->register();
 
+        // Spec §5.4: a theme update checks the Divi fingerprints again at once (the state key would, too).
+        add_action('upgrader_process_complete', static function (): void {
+            delete_transient(ReleaseResolver::CACHE);
+        });
+
         $schema = self::contentSchema();
         $registry = null;
         $policy = null;