feat: Pods fields in Theme Builder bodies checked against the template's post types (E12)

Both forms Divi writes are recognized (ruling Q11): custom_meta_<key> and the
dialog form post_meta_key + select_meta_key. Choice fields get a note about the
stored value, relation fields name IDs (F4). Only templates the user may edit
are checked or named; others are counted (Q21 pattern). Warnings only, also in
the dry run of a live body. DynamicFields extracted from lit/divi-dynamic-sources.

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

src/Integrations/Divi/DiviIntegration.php

@@ -20,6 +20,7 @@ use LIT\MCP\Integrations\Divi\Pages\DiviContentComposer;
 use LIT\MCP\Integrations\Divi\Pages\DiviDeleteAbility;
 use LIT\MCP\Integrations\Divi\Pages\DiviDuplicateNodeAbility;
 use LIT\MCP\Integrations\Divi\Pages\DiviDynamicSourcesAbility;
+use LIT\MCP\Integrations\Divi\Pages\DynamicFields;
 use LIT\MCP\Integrations\Divi\Pages\DiviInsertAbility;
 use LIT\MCP\Integrations\Divi\Pages\DiviMoveAbility;
 use LIT\MCP\Integrations\Divi\Pages\DiviNodeCopyAbility;
@@ -178,7 +179,8 @@ final class DiviIntegration implements Integration
             $this->themeBuilderAccess,
             new DiviComposition($this->modules, $this->design),
             new DiviSaver(),
-            $this->log
+            $this->log,
+            new DynamicFields($this->schema)
         );
     }
 
@@ -191,7 +193,7 @@ final class DiviIntegration implements Integration
             $this->design,
             new DiviComposition($this->modules, $this->design),
             new GlobalEdits($this->access, new GlobalUsages(null, $this->access->roles())),
-            new ThemeBuilderEdits($this->themeBuilderAccess)
+            new ThemeBuilderEdits($this->themeBuilderAccess, fields: new DynamicFields($this->schema))
         );
     }