Browser SDK v1 facade omits materializer methods top-level (setFrontendAdminBarVisible, ensureDirectory, writeFile, runRecipe)

[chubes4]

Problem

browserSdkFacade (packages/wordpress-plugin/assets/browser-runtime.js:456) exposes some operations as top-level v1 members (startBrowserPreview, runBrowserSessionRecipe, bootExecutableBrowserSession, …) but others only inside the frozen v1.methods map (line ~477): setFrontendAdminBarVisible, ensureDirectory, writeFile, runRecipe, and possibly more.

Studio Native's browser materializer — per its documented contract — calls these as top-level window.wpCodeboxBrowser.v1.<method> and fails closed: WP Codebox browser SDK v1 is missing setFrontendAdminBarVisible. This blocks the entire preview boot on the Studio Native dogfood runtime, caught by the new headless product-flow e2e (chubes4/studio-native#941/#943). Consumer-side smokes were source-shape assertions, so the gap was invisible until a real browser exercised the flow.

Fix shape

Expose the full sanctioned method set top-level on the v1 facade (thin passthroughs like the existing entries), keeping v1.methods as-is. Audit the studio-native materializer's consumed set (ensureDirectory, writeFile, runBrowserSessionRecipe, consumeContainedSiteSync, runRecipe, setFrontendAdminBarVisible) and cover the facade surface with a real facade test (not source-shape matching).

[chubes4]

Fixed and live-proven.

• PR: Expose browser SDK materializer facade methods #1715
• Merge commit: 62476680f071f1971c1eeb1bb687ae1bf63c94be
• Deployment: Studio Native dogfood runtime wp-codebox plugin deployed from the merged commit with Homeboy; deployed assets/browser-runtime.js contains the top-level facade passthroughs for ensureDirectory, writeFile, runRecipe, and setFrontendAdminBarVisible.
• Consumed top-level method audit from Studio Native materializer: ensureDirectory, writeFile, runBrowserSessionRecipe, consumeContainedSiteSync, runRecipe, setFrontendAdminBarVisible. No other direct wpCodeboxBrowser.v1. usages were found under the Studio Native browser assets.
• Targeted test: perl -e 'alarm shift; exec @ARGV' 300 npm run test:browser-sdk-facade passed.\n- Live e2e: npm run preview-boot-e2e passed against https://affectionate-multicolored-mars.wpcloudstation.dev through the SOCKS proxy. Real preview boot reported ready: true, phase: editable_preview_ready, status: complete; iframe navigated to https://playground.wordpress.net/remote.html?progressbar=true&blueprints-runner=v1. The blocked-SDK negative case also passed with expected sdk_unavailable failure classification.