1.2.1

Built and verified locally, since GitHub Actions is not running jobs for this account (billing); the package follows deploy.yml step for step.

A release of corrections to the settings screen. The storefront is the one 1.2.0 shipped: its script, its styles and every PHP class are the same files.

Settings screen

• The words in the header no longer flicker as they appear. The title and the description fade in word by word, and a frame after a word had arrived it was gone for one frame and back.
• The confirmation before disconnecting says what disconnecting does. It said that only the saved credentials are removed and that nothing in the Search Cloud account changes. Disconnecting has Search Cloud remove the site and permanently delete its search index; the shop uses WordPress's own search until the site is connected and synced again, and nothing in WordPress is deleted. The button that goes ahead reads Disconnect and delete the index.
• Numbers and dates follow the language of the WordPress profile, not the language of the browser. An English screen in a Persian browser read "۲۷۰٬۰۰۰ of ۳۰۰٬۰۰۰", and a date in the sync history came out in the Persian calendar. A date in the sync history is now written in the site's date format and time zone.
• How connecting works names the link for another email address by its label, Not this email?.
• The Terms of Service, Privacy Policy and Data Processing Agreement links on the Connection tab lead to the documents at searcio.com when Search Cloud cannot be reached. They led to an address that asks for a password.

Also

• The package holds no vendor folder and no composer.json. The plugin loads its own files through includes/autoload.php; it used to carry a vendor that held Composer's autoloader and nothing else. Nothing changes in how it works.
• webhead plugin framework 1.5.0. The build gives a package the dependency npm installed for it, which is what ended the flicker: the settings script carried an older animation engine than the one it asks for.
• The readme says what connecting sends to Search Cloud, and what saving the Search Config tab sends.

The full list is in readme.txt and CHANGELOG.md. Merged in #19 to #24.

---

Package: webhead-search-cloud-1.2.1.zip - 0.99 MB zipped, 4.4 MB installed, 273 files, built from the merge commit with one composer install. Its public/ is byte-identical to the build the end-to-end specs ran against. Installed from the zip on a clean WordPress 7.1 (PHP 8.3) with WP_DEBUG on: activates with an empty debug log and without a vendor folder, 16 REST routes, both blocks, the admin menu, 3 capabilities, both tables, the scheduled sync and 7 Site Health checks registered; the framework's ten helper functions are there in the plugin's own namespace; the German translation loads; the uninstall routine runs clean. A package of the same tree, built one commit earlier: both Elementor widgets with Elementor and WooCommerce active; a page without a search block loads nothing of the plugin; in a browser, desktop and phone, the settings screen, the Sync tab, the Connection tab and the search modal pass 72 specs with the debug log empty; Plugin Check reports no errors in the plugin's own code, nothing at all in it when run as wordpress.org runs it, and no missing_composer_json_file.

Tests: on 8457938, the tree this release holds apart from two entries moved in CHANGELOG.md and readme.txt: unit 108, integration 240 with 3 skipped on PHP 8.3 with WooCommerce and Elementor loaded, multisite 240, JS 283, and the 72 browser specs above. On the tree of #22, which builds to the same public/: the seven admin specs, 77 passed and 1 skipped by its own rule on a narrow screen. The storefront specs were not run again, since no file they load changed since 1.2.0. All passing. Run on the host with PHP 8.3 and MySQL 8, not in wp-env.

This release replaces one published under the same number on 2026-10-07 from 07a5660, which had not been installed anywhere; that one carried vendor and composer.json and framework 1.4.1.