=== LatentKit AI Provider ===
Contributors: amirehman
Tags: ai, latentkit, artificial-intelligence, connector, provider
Requires at least: 7.0
Tested up to: 7.0
Stable tag: 0.1.0
Requires PHP: 8.1
License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Use LatentKit as a route-based AI provider in WordPress.

== Description ==

LatentKit AI Provider connects the official WordPress AI Client to a
LatentKit app. WordPress sends text-generation requests to LatentKit; the
published LatentKit route controls the provider, model, fallback, policy,
credits, and analytics.

This connector does not add a competing editor assistant. It supplies the
provider used by existing WordPress AI features and adds a compact status page
under Settings → LatentKit for connection, route, model, and recent-request
visibility.

External service disclosure: this plugin sends administrator-initiated AI
prompts and related generation settings to the configured LatentKit API. The
service returns generated content and request metadata. Review the LatentKit
privacy policy and terms before connecting a production site:

* https://ai.latentkit.com/
* https://latentkit.com/privacy/
* https://latentkit.com/terms/

== Installation ==

1. Upload and activate LatentKit AI Provider.
2. If WordPress AI is missing, use the wp-admin notice to install or activate
   it. LatentKit remains safely disabled until WordPress AI is active.
3. Configure your LatentKit API key in the WordPress AI credentials screen, or
   define `LATENTKIT_API_KEY` in `wp-config.php`.
4. Open Settings → LatentKit to verify the connection and assigned route.
5. Use an existing WordPress AI text feature and select LatentKit when needed.

== Frequently Asked Questions ==

= Does WordPress choose the upstream model? =

No. WordPress sees one logical `latentkit-route` model. Your published
LatentKit route chooses the provider and model.

= Is the API key sent to browser JavaScript? =

No. Authentication and LatentKit requests remain server-side.

= What data is sent to LatentKit? =

Only data needed for the administrator-initiated AI request, including the
prompt, generation settings, and connector attribution headers. The connector
does not send the site URL, title, administrator email, or arbitrary telemetry.

== Support ==

Read the connector documentation at:

* https://docs.latentkit.com/integrations/wordpress/

== Changelog ==

= 0.1.0 =

* Prepare the complete first WordPress.org release with stable directory
  metadata, external-service disclosure, support links, and PHP SDK beta.3.
* Remove private repository links that are unavailable to WordPress.org users
  and reviewers.

= 0.1.0-alpha.8 =

* Bundle PHP SDK beta.3 so route model totals remain accurate when the API
  returns the ordered model list without a redundant `model_count` field.

= 0.1.0-alpha.7 =

* Use the PHP SDK beta.2 typed connection and route context instead of a
  connector-specific response parser.
* Use the supplied square LatentKit JPG mark in the connector catalog.

= 0.1.0-alpha.6 =

* Do not report zero models when the connected gateway still returns the old
  route-summary shape; show an update notice until model details are available.

= 0.1.0-alpha.5 =

* Display the LatentKit brand mark on the WordPress AI connector card.

= 0.1.0-alpha.4 =

* Add a Settings → LatentKit dashboard for connection, route, route models,
  credits, and the latest winning provider/model.
* Keep API keys hidden and send route changes to the authorized LatentKit
  console instead of allowing runtime keys to mutate routing.

= 0.1.0-alpha.3 =

* Require the official WordPress AI plugin to be active even when WordPress
  core already exposes the underlying AI Client class.
* Align the minimum supported WordPress version with WordPress AI at 7.0.

= 0.1.0-alpha.2 =

* Replace the WordPress dependency error screen with a recoverable wp-admin
  notice and direct install or activate action for WordPress AI.

= 0.1.0-alpha.1 =

* Initial source alpha with text generation and connection validation.
