=== Netgardi Local Manager ===
Contributors: netgardi
Tags: dashboard, site-management, woocommerce, artificial-intelligence
Requires at least: 6.5
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 1.0.6
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

A Persian, mobile-friendly site management workspace. Normal management runs inside the customer WordPress site; optional intelligent services use the existing Netgardi account.

== Description ==

Install this package only on a standalone customer WordPress site. WooCommerce management is available when WooCommerce is installed; pages, articles, media and site visits also work on non-commerce sites. This package reuses the established Netgardi management interface and controller modules internally. A separate Netgardi Connector installation is not needed.

Normal management does not require a monthly subscription. AI services require available account credit and the tool permissions configured centrally. Current Netgardi plans, purchased credit, wallet, payment history, invoices and support remain the source of truth. No new pricing catalog or provider billing system is introduced.

Use the WordPress administrator account to link a verified phone number and site. The central installation verifies both SMS ownership and site possession. The default welcome offer is twenty credits once per verified phone; it is not repeated for reinstallation or another site. The central operator can configure the offer.

WordPress role permissions still apply. Administrators can connect the account, use AI services and manage finance. Shop managers retain permitted local operations; this plugin does not elevate their WordPress permissions.

The panel is an authenticated private workspace. It does not replace the public theme. It offers an explicit return to WordPress and does not intercept normal storefront requests with a service worker cache.

Normal support uses the existing central ticket system. The management panel and Account share one conversation interface with an empty title/message form, owned ticket history and replies. Creating ordinary support requests does not consume AI credit, wallet balance or the monthly revision allowance. The legacy central management panel and hosted Store Builder keep their existing service rules.

== External services and privacy ==

The optional external service is Netgardi, normally https://netgardi.com/ (or the HTTPS service origin configured by the site administrator). Account connection sends first name, last name, verified phone, site URL and installation identifiers after consent. Account, wallet, purchase and invoice actions are processed by that service.

When an intelligent tool is requested, the relevant prompt, selected site data and attachments are sent server-to-server to Netgardi. Netgardi uses its centrally configured AI providers and existing credit accounting. AI provider keys are not distributed to this plugin or to the browser. Provider terms and retention policies apply through that service.

Existing enabled automations and notifications can send the site events and related content needed for those services. Deactivate an automation or disconnect the account to stop future service operations. No new independent analytics tracking service is added by this package.

Service information: https://netgardi.com/
Service terms: https://netgardi.com/terms/
The operator must publish its actual current privacy policy and provider disclosures before distributing the service publicly. The plugin also contributes a WordPress Privacy Policy Guide paragraph.

== Installation ==

1. Update the central components and activate Netgardi Local Gateway last, using the supplied Persian installation guide.
2. Back up the customer site and upload netgardi-local-manager-1.0.6.zip through WordPress Plugins.
3. Activate the plugin. The separate old Connector is deactivated automatically when found; its data is retained.
4. The first ordinary administration screen after activation opens the management panel. Enter the account details and confirm the SMS code.
5. Open Account to use the existing plans, wallet, purchased credit and invoices.

A valid public HTTPS URL is required on both sites. Incoming signed REST requests and outgoing HTTPS requests must be allowed. Cron processing remains necessary for existing scheduled automations and notifications.

This package is not for the Netgardi central installation, the hosted Store Builder, or network-wide activation. It does not replace the hosted Store Builder runtime.

== Frequently Asked Questions ==

= How do I return to the WordPress dashboard? =
Use the visible WordPress dashboard button. WordPress opens for the current browser login for up to one hour; returning to the management panel restores the app default. The choice does not affect another browser and is not a permanent user preference. Default dashboard visits and administrator logins open the app. WordPress includes a visible return link. For recovery, open /wp-admin/?nglm_safe=1 with the correct site base URL. Editing links, background requests, plugin installation and updates retain their normal behavior.

= How do plugin updates work? =
Install this release once after the central Gateway is updated. Sites already on 1.0.4 can receive 1.0.5 through the central independent-panel release settings, without another manual customer installation. Later releases use that same channel. Automatic installation is enabled initially for this plugin only; the site administrator can pause it in Account > Updates or the native WordPress plugin settings. Other plugins retain their own preferences. Connected sites check roughly hourly and use the native WordPress upgrader, subject to working cron, filesystem access and hosting policies. Updating the plugin does not spend AI credit. Signed per-connection metadata and a pinned package checksum are verified before installation.

= Does free access grant the monthly credits of the base plan? =
No. The selected existing base plan governs tool availability. Included monthly credit requires an actual active subscription. Permanent purchased credit can be spent without an active subscription.

= Does changing the domain require database edits? =
Use the normal WordPress domain migration process first. Then reconnect this plugin with the same verified phone. The central service checks the new site and preserves the matching installation identity. Old-domain credentials are not silently reused.

= What happens on deactivation or deletion? =
Background jobs owned by this package are unscheduled. Site content, financial records, central accounts and saved connection data are retained to avoid destructive removal. Disconnect before deletion or revoke the installation from the central settings when you want access revoked. No external account is deleted automatically.

== Changelog ==

= 1.0.6 =
* Adapt the actual User Hub canvas, glass surfaces, semantic colors, shadows and mobile navigation to Account.
* Put the toolbar and desktop navigation in one header, with a Hub-style companion rail.
* Fix the plan-grid closing boundary so separate credit purchases occupy an independent full-width card.
* Make the credit form respond to its own container width, including narrow desktop embeddings.
* Add an optional illustrated empty support state without changing legacy support behavior.

= 1.0.5 =
* Bring Account into the management panel glass design, using the shared palette and bundled vector icons.
* Add an app-style mobile account bar, five-item bottom navigation and an accessible native More sheet.
* Improve plans, wallet, payments, support and profile layouts in both themes without changing central financial handlers.
* Keep URL state and browser back navigation in sync, and ignore stale account responses after switching sections.

= 1.0.4 =
* Publish validated immutable customer-panel releases from the existing independent-panel settings.
* Use signed connection-scoped metadata, pinned SHA-256 packages and native WordPress updates.
* Keep automatic-update consent, compatibility gates, publication pause and customer version status.

= 1.0.3 =
* Replace the local monthly revision form with one shared ordinary support interface in management and Account.
* Preserve existing conversations and legacy attachment links; safely render replies and retain request identity across retries.
* Remove the old customer-runtime revision handler and monthly quota surface.
* Improve light-mode text, semantic buttons, statuses, form boundaries and shared mode-aware palette tokens.
* Synchronize the existing account and management theme preferences.

= 1.0.2 =
* Make the local panel the default dashboard and default administrator login destination, before and after account connection.
* Open onboarding on the first ordinary admin screen after activation or migration from the previous dashboard-routing behavior.
* Replace the persistent WordPress preference with a bounded, browser-session workspace and add visible return links in WordPress.
* Preserve WordPress recovery, installation, updates, AJAX, REST, form submissions and existing role permissions.

= 1.0.1 =
* Fix explicit theme-button binding and isolate private documents from storefront assets/widgets.
* Preserve registration draft, OTP step and cooldown across refresh.
* Safe retry of uncertain SMS requests; validate Persian/Arabic digits and use bounded site-proof fallback.

= 1.0.0 =
* Local authenticated management via internal WordPress REST dispatch.
* Existing central AI, account, credit, wallet, payments and subscriptions integration.
* Verified SMS and site-possession registration; encrypted and revocable connection.
* Mobile account interface, private app entry, isolated notification worker and WordPress recovery route.

== Third-party components ==

Vazirmatn font by Saber Rastikerdar and contributors, SIL Open Font License 1.1; license included in assets/fonts/OFL-1.1.txt. Bundled Netgardi runtime modules remain source-readable PHP/JavaScript/CSS. Ordinary service responses contain data only. Plugin releases are delivered separately through the native WordPress updater after signed metadata and package integrity checks.
