feat: Divi tools edit Theme Builder layouts; visible layouts need confirm

TB layouts load through ThemeBuilderAccess (P12), live layouts (attached +
enabled, Q8) need a dry run and confirm (Q9) and get the shared restore point
of VisibleEdits, extracted from GlobalEdits (Q2: backup when revisions are
off, P9 refusals, P14 naming). divi/post-content only in body layouts (F22),
also for nested stored nodes. SaveScope::ThemeBuilderLayout sets Divi flags
and clears site CSS + TB cache.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-09-27 15:45:07 +02:00
co-authored by Claude Opus 5.5
parent 4ff1c1e2a5
commit b1dd35abd8
27 changed files with 1106 additions and 132 deletions
@@ -0,0 +1,21 @@
<?php
declare(strict_types=1);
namespace LIT\MCP\Tests\Unit\Integrations\Divi\Pages;
use LIT\MCP\Integrations\Divi\Pages\SaveScope;
use PHPUnit\Framework\TestCase;
final class SaveScopeTest extends TestCase
{
/** Finding 4: TB layouts carry Divi's flags after a builder save; a layout change shows site-wide (§5.6). */
public function testThemeBuilderLayoutsGetFlagsAndClearEveryPage(): void
{
self::assertTrue(SaveScope::ThemeBuilderLayout->setsFlags());
self::assertTrue(SaveScope::ThemeBuilderLayout->clearsSiteCss());
self::assertTrue(SaveScope::Page->setsFlags());
self::assertFalse(SaveScope::Page->clearsSiteCss());
self::assertFalse(SaveScope::LibraryItem->setsFlags());
}
}