=== Laudia Connect ===
Contributors: laudia
Tags: ai, json-ld, schema, llms.txt, robots.txt
Requires at least: 5.6
Tested up to: 7.0
Requires PHP: 7.4
Stable tag: 1.0.1
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

A narrow, auditable connection that lets Laudia publish only the AI-visibility fixes you approve. Nothing else.

== Description ==

Laudia Connect is the companion plugin for [Laudia](https://laudia.ai), the AI search visibility service. After you approve a fix in your Laudia dashboard, Laudia publishes it to your site through this plugin's small REST surface:

* **JSON-LD schema** and an **FAQ block**, printed in your site's head. Theme-independent and reversible.
* A **virtual llms.txt** served at `/llms.txt`. No file is written to your server.
* **Additive robots.txt lines** (`Sitemap:`, `Allow:`) appended to the robots.txt WordPress generates. The plugin refuses any `Disallow:` or `Noindex:` line, so it can never block a crawler. If a physical robots.txt file exists, the plugin reports that honestly instead of pretending to deploy.

Deliberate non-goals: the plugin writes no files, edits no themes, manages no users, and has no settings screen. Everything it serves lives in four options rows and is removed when you delete the plugin.

= Least-privilege access =

The plugin registers a dedicated **Laudia Connect** role carrying only its own capability (plus `read`). You create one user with that role and issue a WordPress Application Password for it. Laudia refuses to operate with an administrator account.

Every REST request must carry that capability. All content is pinned by hash: the plugin recomputes the checksum of every payload and refuses a mismatch.

== Installation ==

1. Install and activate the plugin.
2. Create a new user (for example `laudia-connect`) with the **Laudia Connect** role.
3. On that user's profile, create an **Application Password**.
4. In your Laudia dashboard, connect your site with the username and Application Password.

== Frequently Asked Questions ==

= What can Laudia change on my site? =

Only the four artifacts above (schema, FAQ, llms.txt, additive robots lines), and only after you approve the exact content in your dashboard. The plugin refuses everything else.

= Does deactivating the plugin delete anything? =

No. Deactivation only stops serving; the role and stored content are kept. Deleting the plugin removes its options and the role.

= Can this block search engines or AI crawlers? =

No. The robots surface is additive-only and the plugin rejects any `Disallow:` or `Noindex:` line at the API and again at serve time.

== Changelog ==

= 1.0.1 =
* Packaging fix: the distributed archive is now a valid zip (the 1.0.0 download was mispackaged).

= 1.0.0 =
* Initial release: the laudia/v1 REST surface (status, artifacts), JSON-LD head embeds, virtual /llms.txt, additive robots.txt filter, dedicated minimal role.
