Fullbleed Commerce alpha.3: automation activity and verified upgrades

Fullbleed Commerce alpha.3 packages the WooCommerce automation activity view and the visual editor's WordPress integration fixes. This is a staging evaluation preview; paid sales, automatic updates and marketplace listings are not live.

What changed

• WooCommerce → Fullbleed activity in Pro shows the latest email-attachment and customer-download results, filters failures, links to the order, and explains recovery. A successful retry clears the old failure. The status describes PDF preparation, not customer receipt.
• The visual editor uses WordPress's shared Backbone, Underscore and CodeMirror without replacing their global behavior. Visual editing, HTML/CSS customization and saved designs remain available in the free plugin.
• Upgrading from alpha.2 preserves both document templates, their revisions and automation settings. The new activity table initializes after the update.

Install or upgrade

For a new staging installation, activate WooCommerce, upload the free ZIP, then open WooCommerce → Fullbleed documents. Install the separate Pro ZIP to evaluate batch downloads and optional server automation.

To upgrade, back up the staging store and export templates. Upload the new free ZIP through Plugins → Add New → Upload Plugin, choose Replace current with uploaded, then repeat for Pro. Keep both packages on this version. Existing enabled workflows stay enabled: check the renderer connection and a synthetic order after updating. There is no automatic updater in this preview.

Try the free editor in a temporary sample store · Merchant guide · Automation setup

Verified for this release

• Both downloadable ZIPs match the Windows and Linux builds byte for byte.
• 45 shared tests; 60 email/activity checks and 38 customer-download checks in each of HPOS and legacy storage.
• 20 upgrade checks in each storage mode on Windows and Linux, using the real alpha.2 ZIPs and WordPress's package replacement path.
• 14 real Chrome checks on the upgraded Pro store; 12 on the local sample-store journey; 13 on the public demo in the authorized browser session; 11 on native WordPress with the free ZIP. All five public demo PDF artifacts match the local files byte for byte.
• Strict WordPress Plugin Check reports no errors. Renderer deployment, Shopify integration and container jobs pass.

Source: e26de12c68ece1895474171c4e5a871e9356f65a. Integration CI · Native WordPress CI.

Checks use fictional orders. Email hooks and real PDF generation are exercised through a test transport; production email delivery is not claimed. The sample store demonstrates the free editor and browser downloads, not Pro automation. Order summaries are not fiscal invoices; refunded orders and unsupported glyphs are rejected. Merchant pilots, Safari coverage, paid lifecycle testing and marketplace review remain open.

The retained verification record contains exact checks, source commits, PDF hashes and scope. The pinned sample-store Blueprint additionally corrects its download link to use the installed plugin version; four focused public browser checks verify that notice change.

packages.json and SHA256SUMS.txt record the archive hashes. WordPress plugin code is GPL-compatible; the Fullbleed engine remains MIT.

Additional browser verification

The unchanged alpha.3 base and Pro ZIPs now pass 144 browser checks across Chrome, Playwright Firefox and Playwright WebKit on Windows and Linux: 12 merchant-editor checks and 12 customer-account checks per combination. Default, edited, saved, batch and customer PDFs are byte-identical across the six combinations; final PDF pages were rendered and visually inspected.

The browser workflow record retains exact versions, archive/document hashes, test scope and Linux CI. These are synthetic headless-browser checks, not branded Safari, physical-device or production email-delivery verification. Customer renderer transport uses a test filter around actual Fullbleed output. No runtime package, tag or download checksum was changed.