=== VoxFind AI Search ===
Contributors: jazxinnovation
Tags: search, voice search, woocommerce, product search, multilingual
Requires at least: 6.0
Requires PHP: 7.4
Tested up to: 7.1
Stable tag: 0.2.15
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Urdu and English voice-first intelligent product search for WordPress and WooCommerce.

== Description ==

VoxFind AI provides a public search experience for WordPress and WooCommerce.

VoxFind AI includes a platform-neutral query pipeline, WooCommerce catalog adapter, REST search endpoint, local provider architecture, Urdu and English query normalization, structured product filters, catalog validation/indexing and configurable frontend search settings.

Current capabilities include:

* Text search.
* Browser voice input where the browser supports the Web Speech Recognition API.
* Urdu, English and mixed-language query handling.
* WooCommerce product discovery.
* Brand and product-type matching.
* Price constraints such as "under 50000".
* Product attribute and catalog-vocabulary matching.
* Semantic-intent matching against public catalog content.
* Public REST-based product search.
* Shortcode-based frontend search.
* Configurable result limit, floating assistant and Urdu/English voice-recognition language.
* Catalog validation/indexing for reusable multilingual catalog vocabulary.
* Separate Dashboard, Settings, System Status and Search Tests admin pages.

VoxFind AI is designed so commerce-specific behavior remains inside catalog adapters. WooCommerce is the active commerce adapter in this release, while the core query architecture remains platform-neutral.

== Requirements ==

* WordPress 6.0 or newer.
* PHP 7.4 or newer.
* WooCommerce for WooCommerce product catalog search.
* HTTPS is strongly recommended for microphone access.
* Voice recognition depends on browser/device support and microphone permission.

Voice recognition is a browser capability. Availability, supported languages and recognition quality can vary by browser, operating system and device.

== Installation ==

1. Upload the `voxfind-ai` plugin folder to `/wp-content/plugins/`, or install the plugin ZIP through WordPress Plugins > Add New > Upload Plugin.
2. Activate VoxFind AI.
3. Ensure WooCommerce is active when WooCommerce catalog search is required.
4. Open VoxFind AI > Validate Catalog and run Scan & Validate Catalog.
5. Review VoxFind AI > Settings for frontend and voice options.
6. Add the VoxFind search shortcode to a page, post or supported widget area when required.
7. Test text search and, on a supported browser, microphone search.

== Shortcode ==

Basic usage:

`[jazx_voxfind_search]`

The shortcode supports these attributes:

* `placeholder` - custom search-field placeholder.
* `button_text` - custom search-button text.
* `limit` - maximum number of returned products, from 1 to 100.

Example:

`[jazx_voxfind_search placeholder="Search products" button_text="Search" limit="10"]`

== Search Behavior ==

VoxFind AI converts natural-language input into a structured catalog query before sending it to the active catalog adapter.

The WooCommerce adapter searches public, published catalog products and applies supported constraints such as price and recognized catalog attributes.

A query that does not satisfy an explicit constraint should return no matching product rather than silently ignoring that constraint.

== REST API ==

VoxFind AI registers a public product-search endpoint under the `voxfind-ai/v1` REST namespace.

The public endpoint is intentionally limited to normalized public product data. Query length and result limits are bounded, and internal query/provider diagnostic structures are not part of the public response contract.

== Privacy ==

VoxFind AI does not itself create user accounts, advertising profiles or analytics tracking.

Text entered into the VoxFind search interface is sent to the site's own WordPress REST endpoint so the query can be processed.

When voice input is used, speech recognition is provided by the visitor's browser/device through its speech-recognition implementation. Depending on the browser and operating system, audio or speech data may be processed by the browser vendor or an external speech service. Site owners should review the privacy behavior of the browsers/services they support and update their own privacy policy where appropriate.

This release uses the local VoxFind provider by default. If a future provider sends queries to an external AI service, that provider should document its own data handling and privacy requirements.

== Security ==

The public search endpoint validates and bounds incoming search queries and result limits.

Public REST output is restricted to normalized public catalog data. WooCommerce search is limited to published products that are eligible for public catalog/search visibility.

Administrators should keep WordPress, WooCommerce, VoxFind AI and PHP updated and use HTTPS on production sites.

== Uninstall ==

Deactivating VoxFind AI preserves plugin settings.

Uninstalling VoxFind AI through WordPress removes VoxFind AI options created or consumed by this version, including installation metadata, settings, provider selection, catalog index data, custom vocabulary/brand aliases and any legacy settings from earlier builds.

Uninstalling the plugin does not delete WooCommerce products, WordPress posts, media, users, orders or other store content.

== Frequently Asked Questions ==

= Does VoxFind AI require WooCommerce? =

The plugin can load without WooCommerce, but WooCommerce is required for WooCommerce product catalog search.

= Does voice search work in every browser? =

No. Voice recognition depends on browser/device support, microphone permission and the speech-recognition implementation available to that browser.

= Can visitors type searches instead of speaking? =

Yes. Text search and voice input are both supported by the frontend interface.

= Does VoxFind AI support Urdu? =

The query pipeline includes Urdu, English and mixed-language normalization. Actual speech-to-text recognition quality depends on the browser/device speech-recognition service.

= What happens to settings when I deactivate the plugin? =

They are preserved.

= What happens when I uninstall the plugin? =

The included `uninstall.php` removes VoxFind AI options used by the plugin. Store products and normal WordPress content are not removed.

== Changelog ==

= 0.2.15 =
* Declare the enforced minimum WordPress 6.0 and PHP 7.4 requirements in the main plugin header so WordPress can validate compatibility before activation.

= 0.2.14 =
* Prefix all plugin-owned PHP symbols, hooks, options, AJAX actions, nonces, shortcodes, and JavaScript globals with the unique `jazx_voxfind` prefix.

= 0.2.13 =
* Aligned the text domain with the WordPress.org plugin slug.
* Moved the catalog validator JavaScript into an enqueued static asset.
* Updated plugin metadata and reviewed public declarations for directory compliance.

= 0.2.12 =
* Added translator context for the catalog validation timestamp.
* Documented nonce verification for catalog scan requests and read-only admin routing.
* Documented the required WooCommerce taxonomy query for coding-standard checks.

= 0.2.10 =
* Made the public widget language follow the selected Default Voice Language.
* Added localized interface copy and correct RTL/LTR direction for supported languages.
* Fixed Latin speech transcripts that split or slightly misspell catalog names, including “cal Nama” for “Kalnama”.

= 0.2.6 =
* Restored early frontend CSS/JavaScript enqueueing so the floating VoxFind launcher and voice-search assistant render correctly after the 0.2.5 admin/settings restructure.
* Keeps the new Dashboard, Settings, Validate Catalog, System Status and Search Tests administration structure.

= 0.2.5 =
* Reorganized VoxFind administration into Dashboard, Settings, Validate Catalog, System Status and Search Tests pages.
* Added WordPress-native settings for search availability, result limit, floating assistant, voice search and default voice-recognition language.
* Connected frontend and REST result limits to saved VoxFind settings.
* Preserved the multilingual catalog validation/indexing and WooCommerce search behavior from 0.2.4.

= 0.2.4 =
* Fixed the Validate Catalog admin submenu URL by registering it after the VoxFind AI parent admin menu.
* Preserved the catalog validation/indexing workflow introduced in 0.2.3.

= 0.2.3 =
* Hardened the public frontend search flow.
* Hardened REST request validation and public response handling.
* Hardened WooCommerce catalog visibility and public product retrieval.
* Preserved explicit price-filter behavior.
* Improved multilingual and semantic product-query behavior.
* Aligned plugin header and runtime version metadata.
* Hardened dependency loading during plugin bootstrap.
* Added release documentation, license information and uninstall cleanup.
