=== Senvarel ===
Contributors: elghamdi
Tags: content, publishing, ai, seo, automation
Requires at least: 5.8
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.4.2
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Connect your WordPress website to Senvarel to manage AI-assisted content, synchronize articles, create drafts and publish approved content.

== Description ==

Senvarel connects a self-hosted WordPress website to the Senvarel service through a verified and revocable pairing flow.

The connector can:

* Verify the WordPress site, multisite blog and administrator permissions.
* Synchronize authorized posts and pages with Senvarel.
* Send signed content-change events to Senvarel.
* Create and update WordPress drafts requested from Senvarel.
* Publish an existing draft only after an explicit manual approval in Senvarel.
* Revoke the connection locally or from Senvarel.

Connecting WordPress does not enable automatic publishing. This plugin does not contain an automatic publishing scheduler. Draft creation, draft updates and manual publication remain separate operations with separate permission checks.

Senvarel is a hosted service. A Senvarel account and an OWNER or ADMIN role for the matching Senvarel site are required to complete pairing. The WordPress user who starts pairing must have the `manage_options` capability. Feature availability in the service may depend on the customer's Senvarel plan.

For service terms, see https://senvarel.com/terms. For the privacy policy, see https://senvarel.com/privacy.

== Installation ==

1. Install the Senvarel plugin from the WordPress Plugin Directory when it becomes available, or upload an official ZIP supplied by Senvarel for an authorized test.
2. Activate **Senvarel** for the intended site. On multisite, activate it for the intended blog or network-activate it.
3. Open **Settings > Senvarel** in the administration area of the exact blog to connect.
4. Select **Connect Senvarel**. WordPress requests a short-lived pairing code from Senvarel.
5. Open the verification link and confirm the matching organization, site, domain and blog in Senvarel.
6. Return to WordPress and select **Finalize verification**.
7. Confirm that WordPress reports the connection as verified before starting a synchronization.

No WordPress password or manually copied API key is required by the official pairing flow.

Upgrades from the historical token connector remove the local legacy token. The deprecated `geo-growth/v1/status` and `geo-growth/v1/publish` routes return a non-mutating HTTP 410 response. Reconnect through the verified pairing flow; legacy credentials are never converted automatically.

== Frequently Asked Questions ==

= Does connecting WordPress enable automatic publishing? =

No. Pairing verifies identity and permissions only. The plugin has no automatic publishing scheduler, and the official connection keeps automatic publishing disabled.

= Can Senvarel publish an article? =

Senvarel can create and update drafts. An existing draft can become public only through the manual publication flow after an OWNER or ADMIN explicitly reviews and confirms that operation in Senvarel. WordPress permissions are checked again immediately before publication.

= Is my WordPress password sent to Senvarel? =

No. The plugin never asks for or sends a WordPress password. Pairing exchanges dedicated random signing credentials over HTTPS after confirmation on both sides.

= Which WordPress permissions are required? =

`manage_options` is required to pair or revoke the connector. Read, draft and publish operations additionally require the relevant WordPress capabilities for the connected user and content type. If those capabilities are removed, the operation is rejected.

= Does the plugin support WordPress multisite? =

Yes. Credentials and signed requests are scoped to the exact WordPress network and blog. A request for a different blog is rejected.

= What happens when the plugin is deactivated? =

The connector endpoints and event delivery stop. Connection credentials remain stored so reactivation can restore the connection. Disconnect first if you want Senvarel to revoke the remote installation.

= What happens when the plugin is deleted? =

Uninstallation removes Senvarel credentials, pending pairing data, connector options, replay nonces, scheduled events and the plugin's custom journal tables from every affected blog. WordPress posts and pages are not deleted. Because uninstall code does not contact an external service, disconnect before deletion when possible so the remote credential is revoked as well.

= Where are connection credentials stored? =

Dedicated HMAC credentials are stored as non-autoloaded WordPress options in the database of the connected blog. They are never displayed in the WordPress interface or included in connector logs.

== Screenshots ==

1. The Senvarel settings page before pairing, with automatic publishing clearly disabled.
2. The short-lived pairing code and double-confirmation instructions.
3. A verified WordPress connection with the revocation action and automatic-publishing limitation.

== External services and privacy ==

This plugin communicates with the Senvarel service at `https://senvarel.com`. It does not contact Senvarel merely because the plugin files are installed. Communication begins when an administrator explicitly starts pairing, and continues while the verified connection remains active.

During pairing, the plugin sends the WordPress home URL, site URL, REST URL, site name, generated instance identifier, numeric WordPress user identifier, blog and network identifiers, multisite status, WordPress/PHP/plugin versions and capability booleans. It receives short-lived pairing data and dedicated signing credentials.

When synchronization is requested, the plugin can send authorized post or page identifiers, status, title, excerpt, content, slug, timestamps, categories, author display name and Senvarel provenance metadata. Private content and author information are included only when the connected WordPress user has the corresponding permissions.

While connected, the plugin records local content-change events and delivers signed event metadata to Senvarel. Draft creation, draft updates and manual publication receive signed operation data from Senvarel. Requests include installation and binding identifiers, timestamps, nonces and HMAC signatures.

Senvarel processes this data to provide the connector, synchronization, draft-management and manually approved publication features requested by the customer. See https://senvarel.com/privacy and https://senvarel.com/terms for the service's policies.

== Changelog ==

= 1.4.2 =

* Internationalize the WordPress administration and connector error messages.
* Bundle the French translation and the source translation catalogue.
* Complete the final WordPress.org compatibility and packaging review.
* Keep the legacy writer retired and automatic publishing disabled.

= 1.4.1 =

* Retire the historical bearer-token writer and remove its token controls.
* Delete the historical token on upgrade without changing WordPress content.
* Return a non-mutating HTTP 410 response from the deprecated legacy routes.
* Require the verified pairing, scoped HMAC credentials and official operation engine for every mutation.

= 1.4.0 =

* Add manually approved publication of an existing WordPress draft.
* Recheck WordPress publication permissions, binding scope and remote version before mutation.
* Reuse the durable operation journal for idempotency and reconciliation.
* Keep automatic publishing disabled.

= 1.3.0 =

* Add signed, durable content-change events with retry and replay support.
* Add idempotent draft creation, draft updates and remote-state reconciliation.
* Preserve multisite blog isolation and reject writes after revocation.

= 1.2.0 =

* Add signed connector health and capability diagnostics.
* Add initial and incremental synchronization for authorized articles and pages.
* Bind signed requests to the paired WordPress network and blog.

= 1.1.0 =

* Add short-lived, double-confirmed Senvarel pairing.
* Add signed identity verification and anti-replay protection.
* Add capability reporting and bidirectional revocation.

= 1.0.0 =

* Initial connector with legacy token compatibility.

== Upgrade Notice ==

= 1.4.2 =

Version 1.4.2 adds complete English and French administration translations and final release-candidate compliance updates. Connection credentials, WordPress content and publishing consent are unchanged.

= 1.4.1 =

The historical token writer is retired and its local token is deleted. Existing WordPress content is preserved. Reconnect through the official Senvarel pairing flow before using synchronization, drafts or manually approved publication.

= 1.4.0 =

Version 1.4.0 adds secure manual publication and durable operation recovery. It does not enable automatic publishing. After upgrading, use the Senvarel health check to verify the connected user's current permissions.
