=== GESWP ===
Contributors: asmaulhq
Tags: ai, mcp, automation, content, workflow
Requires at least: 6.9
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 0.1.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Connect your AI assistant to WordPress with reviewed changes, permissions and verification.

== Description ==

GESWP (Generative Engine Solution for Web Platforms) connects compatible AI assistants to controlled WordPress operations through MCP and structured JSON/CSV Jobs.

Free works without signup, a subscription, Pro or an account service. It supports exact plain-text changes in supported Gutenberg regions, title/excerpt and image metadata edits, content discovery, supported exports and reviewed background Jobs. Read -> Preview -> Review/Approve -> Apply -> Verify -> Audit. Native WordPress capabilities, per-connection permissions, OAuth scopes, exact targeting, live-state checks, confirmations, revisions where supported and durable audit remain authoritative. Unsupported or ambiguous changes fail closed; uncertain writes require inspection, not blind replay.

The separately installed official WordPress MCP Adapter enables compatible AI connections. JSON/CSV work does not require it. No AI model or ChatGPT/Claude subscription is included. No AI provider or customer account is connected automatically.

GESWP Pro is a separate add-on distributed outside WordPress.org, supplying supported publishing, rich text, layout, media and SEO writes. Business adds supported administration operations through the same add-on. Compatible paid code, verified entitlement and original WordPress/MCP authority are all required. Core contains no external plugin updater or premium installer. Optional Upgrade to Pro links open https://geswp.com/pricing/ . Paid accounts are managed on their trusted service website.

Open GESWP after Pages in wp-admin. The packaged docs explain current scope, AI onboarding, privacy, supported recovery and deliberate compatibility identifiers. Full third-party builder certification, a built-in AI assistant and arbitrary wp-admin parity are not claimed.

== Privacy and external services ==

Free features run locally with no licensing connection or telemetry. UI assets are local files. Jobs may contain submitted/before/after content, user/connection references and audit/recovery evidence. OAuth records and permissions are stored locally. Default deactivation/uninstall retains history; explicit owned-data purge requires GESWP_UNINSTALL_PURGE_DATA. See docs/retention-and-recovery.md.

Optional account service: an administrator explicitly configures a trusted HTTPS URL/public key and starts Connect account / Verify plan. Credentials stay on that service's website. Binding, one-use challenge, return URI, state and PKCE data are sent for connection; refresh/service controls send installation identity and authenticated session authorization. Signed entitlement and encrypted session are stored locally. Core shares the protocol; private Pro handles its own authorized update/download channel. Disconnect/revoke through account controls; billing cancellation is separate. Official operator policies: https://geswp.com/privacy-policy/ and https://geswp.com/terms/ . For alternative configured operators, review their own policies. No service is configured by default.

Optional Pexels search sends query/limit/page and an Authorization API key to https://api.pexels.com/v1/search . Optional Pixabay search sends key/query/parameters to https://pixabay.com/api/ and caches results for 24 hours. Queries can derive from requested title/heading context. Source/preview/creator/image URLs return to the authorized client; previews/imports contact selected image hosts. Clear API keys in Settings to disconnect. Provider attribution/reuse requirements still apply. Pexels: https://www.pexels.com/api/documentation/ , https://www.pexels.com/terms-of-service/ , https://www.pexels.com/privacy-policy/ . Pixabay: https://pixabay.com/api/docs/ , https://pixabay.com/service/terms/ , https://pixabay.com/service/privacy/ . Unsplash search/import is unavailable until a complete provider-compliant workflow exists; no Unsplash API call/download is made.

Requested/configured source URL checks, media imports and frontend verification use WordPress HTTP calls to selected URLs with normal server request metadata; no account bearer is attached. Evidence may retain snippets/status/hashes. Disable optional official URL checks in New Job when not wanted. Native embeds may contact selected oEmbed/media providers and frontend browser requests disclose viewer network/cookie metadata under those providers' policies. See https://policies.google.com/privacy , https://www.youtube.com/t/terms , https://vimeo.com/privacy and https://vimeo.com/terms as applicable.

MCP clients receive only authorized tool results under their own privacy/terms. GESWP does not automatically send content to an AI provider. Revoke OAuth connections in MCP & OAuth and disconnect in the client. Common policies: https://openai.com/policies/privacy-policy/ , https://openai.com/policies/terms-of-use/ , https://www.anthropic.com/legal/privacy , https://www.anthropic.com/legal/consumer-terms . WordPress may contact api.wordpress.org/downloads.wordpress.org for native update/dependency operations: https://wordpress.org/about/privacy/ . Full trigger/data/storage/disconnect details are in docs/privacy-and-services.md.

== Installation ==

1. Upload geswp.zip through Plugins -> Add Plugin -> Upload Plugin and activate GESWP.
2. Open GESWP -> New Job. Paste JSON or upload JSON/CSV for supported Free operations; analyze, review and Apply.
3. For MCP, separately install/activate WordPress MCP Adapter. Enable OAuth and select narrow per-connection permissions in MCP & OAuth; use the endpoint shown there.
4. For paid capabilities, manually install compatible GESWP Pro and connect the optional trusted account service in Account & Plan. Keep Core active.
5. Read the packaged guides and verify changes on a disposable site before sensitive work.

== Frequently Asked Questions ==

= Is signup required? =

No. Free local operations, JSON/CSV Jobs and permitted reads work without signup or Pro. Paid add-on access needs a verified entitlement; plan access does not grant WordPress permissions.

= Can it publish Pages, Posts or custom post types? =

Supported paid lifecycle adapters use installed native endpoints and the authenticated user's capabilities. Draft creation and publishing are distinct, reviewed actions. Inspect the live catalog; not every post type or endpoint is supported.

= Does every remote change use a Job? =

Yes. Direct remote Apply cannot bypass reviewed Jobs, exact confirmation, live-state validation and verification. Reads do not need Jobs. Cross-resource compensation is guarded, not atomic.

= What happens if a connection drops? =

Inspect the existing Job and reconcile supported uncertain writes before retrying. Do not blindly replay Apply. Recovery availability depends on authenticated exact evidence and the adapter.

= Are local files or executable theme code editable? =

No arbitrary PHP, JavaScript, filesystem or database editing is exposed. Supported paid theme stylesheet operations have separate native capability/permission, exact file guards and reviewed Jobs.

= Does removing Pro erase my work? =

Removing the add-on does not erase previously saved content, Jobs or audit/recovery evidence. New paid writes are unavailable. Default Core uninstall also retains plugin history; explicit purge is separate.

== Changelog ==

= 0.1.0 =
* Initial GESWP review build with local Free operations, reviewed Jobs, exact verification and optional MCP connections.
* Paid implementations are supplied separately by GESWP Pro; production account proofs use a pinned safe HTTPS service.
* Local UI assets, current AI/user guides and explicit service/retention disclosures.


== Staging test flavor only ==
This separate review ZIP pins the owner-approved public key and https://stg.geswp.com/wp-json/bipixels-account. Set WP_ENVIRONMENT_TYPE to staging, development or local before connecting. Accepts only correctly signed test-environment entitlements, preserving all signature, installation, audience, issuer, sequence and time checks. Production-environment WordPress rejects these test entitlements. No private key, payment secret or unsigned plan simulation is included. Free local operations remain available. Do not submit this flavor to WordPress.org or use it for production.
