SmartCloud AI-Kit – Chatbot and Semantic Search

1.6.11 Country selection and compact quotes need a separate WP Suite Cloud Deployment update (not public v1.0.130). Republish static assets; review translations. Legacy backends remain compatible. Shipping checks require form submission, do not order or pay, and do not promise immediate cart deletion. 1.6.10 KB exclusions need marked source sections, reviewed resync and ingestion; saved template overrides take precedence. Installation does not rewrite old KB text. Backend paging, source counts and answer recovery need orchestration v1.0.130 or equivalent, deployed separately. 1.6.9 Storefront, confirmed shipping quotes and text formats need orchestration v1.0.129 or equivalent. Rich text needs template opt-in. Review Shopify grants, credentials, address privacy, paging and translations; resync format changes. Deploy the backend and republish static assets separately. 1.6.8 Existing field approvals and mappings are preserved; no new fields are automatically enabled. The separate omitted-search recovery and accurate source-validation activity need orchestration v1.0.125 or equivalent. Backend deployment is not automatic. 1.6.7 Document totals need orchestration v1.0.124 or equivalent. Older backends retain progress without misleading chunk totals. Unused prompt settings are hidden. Review saved Shopify schemas after a backend upgrade for larger catalog pages. Backend deployment is not automatic. 1.6.6 Progress feedback works with existing streaming backends. The separate bounded answer-completion retry needs orchestration v1.0.123 or equivalent. Citation rules remain enforced; structured fields and price records are not newly required. Backend deployment is not automatic. 1.6.5 Nested sync needs document-v2 capability; tool-control and empty-reply fixes need orchestration v1.0.122. Review schemas, mappings and profile access, then complete approved sync/ingestion. Aggregates need a site-owned producer. Backend deployment is not automatic. 1.6.4 Generated CTA links need orchestration v1.0.119 or display-policy capability 3. Native fields remain opt-in. Review mappings and complete sync/ingestion after source changes. Existing profiles are preserved; backend deployment is not automatic. 1.6.3 Typed display presets require orchestration v1.0.118 or presentation capability 2; older backends retain fallback. Static export needs exporter/workers 1.1.84 or later. Purge source caches and recrawl missing assets. Review source mappings; backend updates are not automatic. 1.6.2 Structured sync needs orchestration v1.0.117 or equivalent; display templates need answerPresentation support. Review fields, mappings, permissions and URL prefixes. Complete sync/ingestion; await acknowledgment of removals. See release history for full guidance. Backend not auto-deployed. 1.6.1 Local product links need orchestration v1.0.116 with product-page resolution, including existing v1.0.116 stacks. Review presets, shared profiles and page mappings; approve new external evidence sources. Backend not auto-deployed; cart/checkout not enabled. See release history. 1.6.0 Use SmartCloud > Answers. Existing settings and URLs remain; setup preserves unrelated settings, but confirmed Reset clears configuration. Chatbot/DocSearch require Pro and a compatible backend. Taxonomy filtering needs its backend update. The plugin does not deploy it. See release history. 1.5.9 Ingestion resume and cost details need orchestration v1.0.109 or equivalent backend updates. Full metadata resync runs in scheduled batches; wait for both the WordPress scan and backend ingestion before relying on refreshed results. 1.5.8 Source metadata is resynchronized. Release-gated sources wait for an acknowledged public release; Bedrock ingestion must finish before corrected search links appear. No orchestration update is required for this URL fix. 1.5.7 Category paths need the matching backend update. Enable migration mode, reconcile WordPress/docs metadata, complete ingestion, then enable ready mode. Capability/hierarchy changes reset the WordPress baseline, not ingestion completion. Legacy backends retain primary-category behavior. 1.5.6 Regenerate and review enrolled Knowledge Base sources whose public content comes from block-theme templates or dynamic blocks before publishing them again. Generated documents now capture server-rendered source content and exclude shared site chrome; no backend schema migration is required. 1.5.5 To show the new greeting and starter questions in each visitor language, add each authored source string and its translations to the shared WP Suite translation catalog. Existing chatbot settings continue to work without changes. 1.5.4 Update the AI Kit backend to Deployment Access orchestration v1.0.103, or apply the equivalent AI handler and authorizer fixes to a legacy deployment, to receive the response-format and Cognito authorizer repairs. The UI contrast improvement works independently. 1.5.3 Streaming chat requires an AI Kit backend built from Deployment Access orchestration v1.0.102 or later with chat streaming enabled. Without that optional backend capability, the chatbot continues to use the existing HTTP path. 1.5.2 Update the AI Kit backend to Deployment Access orchestration v1.0.100 or the equivalent legacy backend release before using the new cost reconciliation details. Historical AWS billing can cover the AWS account beyond this backend and is delayed; unavailable billing data does not mean zero spending. 1.5.0 Refresh the backend and capability manifest for profiles, grounded chat, isolated execution and spend controls. Resave pre-release Conversation Profiles with HTTPS URL prefixes; the old host-only grounding field is not retained. 1.4.26 Release gating needs Static Publisher 1.0.20 and one content-sync rule covering all enabled Knowledge Sync types. Leave it disabled for public WordPress. After enabling, complete a successful publish to bind the verified target; unreleased work stays queued. 1.4.25 Requires AI Kit backend 1.0.91 with API schema 12 and knowledge.automation capability 6. Run a Knowledge Base baseline synchronization after upgrading so existing WordPress documents receive locale metadata and language-specific document IDs. 1.4.21 Unifies metadata editors as YAML. Backend 1.0.86 also uses YAML for stored configuration layers; existing layer files require operator conversion before that backend update. Document .metadata.json sidecars remain unchanged. 1.4.20 Corrects misleading Needs Review warnings for auto-synchronized KB sources. Delivered confirms backend receipt, not completed indexing. Manual review requirements remain intact. No additional backend update is required over 1.4.19. 1.4.19 Knowledge Sync requires backend 1.0.85 or newer with knowledge.automation capability 5. Existing documents are automatically reconciled using URL and metadata overrides, subject to the configured approval policy. 1.4.16 Adds initial filter selection to the DocSearch JavaScript API. 1.4.15 Declares compatibility with WordPress 7.1. 1.4.13 Recommended for multisite installations using the shared WP Suite Hub. 1.4.12 Recommended update for editors using Knowledge Base sources. Content changes that require renewed review now produce one deduplicated admin notice with a direct link to Knowledge Base Admin. 1.4.11 Recommended dependency refresh away from deprecated SmartCloud Amplify UI releases. 1.4.10 Recommended compatibility update for Starter-managed WP Suite Theme CSS. 1.4.9 Recommended feature and compatibility update. Adds crawler-visible Gutenberg fallbacks, validates them through WordPress Abilities, migrates the shared runtime namespace, and adds plugin-owned uninstall cleanup while preserving shortcode, Elementor, and shared licence behavior. 1.4.7 Recommended update for actionable frontend AI errors, custom post type Knowledge Base screens, provider-based AI-Kit block theming, and safe shared WP Suite Theme CSS handling. 1.4.6 Recommended compatibility update for sites running multiple WP Suite plugins. It prevents a shared Abilities class redeclaration during plugin loading or updates. 1.4.5 Recommended update for SmartCloud Agent Composer provider integration testing. No configuration changes are required, and the new Abilities provider remains inactive when the WordPress Abilities API is unavailable. 1.4.4 Recommended compatibility update in preparation for upcoming WP Suite Agency subscriptions. No configuration changes are required. 1.4.3 No urgent update required for the documentation change. Update when convenient if you use Knowledge Base ingestion on sites that mix or migrate between Elementor and Gutenberg content. 1.4.2 Recommended feature update. Improves initial paint timing, adds shared WP Suite Theme CSS support for shadow-root UI, and lets synced patterns override selected block attributes. 1.4.1 Recommended performance update. Frontend scripts now load later and defer where safe, reducing render-blocking work while preserving existing plugin behavior. 1.4.0 Recommended update. Refreshes AI-Kit’s shared admin UI and WP Suite runtime dependencies, and marks compatibility with WordPress 7.0. No configuration changes are required. 1.3.3 This release fixes Mantine CSS versioning so the correct asset-specific version is used, improving cache invalidation for rendered styles. 1.3.2 This release updates dependencies, fixes site settings persistence so shared global reCAPTCHA settings are preserved correctly, and improves cache handling by versioning CSS files loaded into rendered shadow roots. 1.3.1 Adds a new admin setting for chatbot maxTokens, improves frontend handling of empty or truncated chatbot responses, and generates cleaner markdown from Knowledge Base sources by normalizing whitespace-only empty lines. 1.3.0 Recommended compatibility update. Modernizes AI-Kit admin and block packages for TypeScript 6 and current WordPress typings, and updates the admin help-label flow to the shared InfoLabelComponent pattern. 1.2.16 Recommended update. Improves frontend mounting reliability for DocSearch and AI Feature, and reduces unnecessary DocSearch metadata requests with lazy loading, client-side cache, and in-flight deduplication. 1.2.15 Expands Knowledge Base editing for section-based documents. You can now edit title, URL, and metadata such as category, subcategory, and tags directly for KB sections that are published as separate documents. 1.2.14 Adds a document description override option for Knowledge Base documents. The custom description is used as the excerpt shown under the title in DocSearch results. 1.2.13 Improves the KB admin editor for generated content. You can now override base document metadata and the Knowledge Base document title even for automatically enabled KB sources that do not have a dedicated KB Section override. 1.2.12 Recommended update. Improves Elementor widget parameter handling and fills in missing frontend translations for a more complete and reliable user experience. 1.2.11 Recommended update. Fixes an admin-side logger loading issue that could break affected PHP-based admin pages, and fully bundles Monaco Editor inside the plugin instead of loading it from an external CDN. 1.2.10 Recommended update. This release improves editor loading by adopting the Monaco team’s recommended integration approach without external CDN calls, updates Elementor widget loading to namespace-based registration, and makes shared hub loading more stable across WP Suite plugins. 1.2.9 This release improves how AI-Kit loads scripts and resolves dependencies, with broader use of deferred loading to reduce render-blocking during page load. 1.2.8 Improves AI Feature language switching. The UI language can now be changed even while the component is already running. The change takes effect immediately in the interface, while the current in-progress task continues uninterrupted with its original settings. 1.2.7 Recommended update. Improves startup reliability when multiple WP Suite plugins are active, preventing AI-Kit from initializing before the shared hub. Also adds a per-component UI language switcher to AI Feature, which updates the component language together with outputLanguage. 1.2.6 Improves how WP Suite site settings are loaded in the admin UI. 1.2.5 This release fixes how numeric DocSearch properties are rendered when the component is embedded via shortcode or Elementor widget. 1.2.4 This release updates language files and extends the chunked processing approach used by the summarizer to write and rewrite modes for better handling of larger inputs. 1.2.3 This release includes a small DocSearch mobile view fix to prevent long source URLs from breaking the layout. 1.2.2 This release fixes incorrect handling of boolean block attributes. 1.2.1 This release fixes missing kb-quick-edit.js. 1.2.0 This release moves reCAPTCHA integration into the shared WP Suite hub, adds optional PHP debug logging, improves AiFeature processing with Markdown conversion and chunk-aware handling, adds smarter backend fallback, and improves language-aware rendering based on the current WordPress language. 1.1.6 Improves default-value behavior for DocSearch and AI Feature settings. 1.1.5 Improves DocSearch citation rendering and fixes span alignment on the backend to prevent mid-word highlight breaks. 1.1.4 Recommended update if you use KB Admin: restores correct behavior by including the missing WP Admin REST API updates, plus small DocSearch/Chatbot UI fixes. 1.1.3 Improves DocSearch filter UX and makes category switching more reliable by resetting the KB session context. 1.1.2 Adds optional DocSearch filters. If enabled, search results are constrained by user-selected categories/subcategories/tags. 1.1.1 Improves DocSearch open-button behavior across all integrations, adds an admin debug logging toggle, and fixes KB updates for embedded content. 1.1.0 Recommended update if you use the AI-Kit backend Knowledge Base: this release adds WordPress-native KB source management and introduces KB Section controls (exclude/split/overrideable content). Also includes full Elementor widgets for AI Feature, DocSearch, and KB Section. 1.0.8 Recommended update if you use AI-Kit on non-HTTPS / non-secure contexts (e.g. local dev, staging, embedded previews). Ensures WebCrypto polyfills load deterministically and prevents missing crypto.subtle initialization issues. 1.0.7 No action required. Clear any page/CDN cache if the modal size doesn’t update immediately. 1.0.6 If you use AI-Kit Pro, this update adds the new Doc Search front-end UI (block + shortcode) and the matching JavaScript helper (renderSearchComponent) for Knowledge Base search experiences. 1.0.5 Recommended if you use the Chatbot with reCAPTCHA: reduces repeated verification calls (lower latency and cost) via a short verification window, and adds Classic reCAPTCHA support. 1.0.4 Recommended update if you use AI Features with result translation: ensures translations run in the correct context (admin vs frontend) and reliably translate outputs to the requested language. 1.0.3 Improved UX: backend processing now shows more natural on-device style status messages. 1.0.2 This update fixes language detection/translation that runs before individual AiFeature executions. If you use any AiFeature that relies on automatic language detection or translation, update is recommended. 1.0.1 Includes the new chatbot history retention control plus stability fixes for image attachments. Update if you rely on persisted chat history or need clearer error reporting (especially around reCAPTCHA). 1.0.0 First stable release.