=== OpsGate ===
Contributors: opsgate
Tags: site monitoring, wordpress security, reports, alerts, uptime, performance, vulnerability management, agency tools
Requires at least: 6.5
Tested up to: 6.9
Requires PHP: 8.1
Stable tag: 0.10.8
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

OpsGate connects WordPress sites to the OpsGate platform for evidence-backed site triage, reports, alerts, and operational visibility.

== Description ==

OpsGate is a hybrid WordPress site operations and alert automation platform.

The OpsGate WordPress plugin connects a WordPress site to the OpsGate platform so the site can participate in evidence-backed triage, reports, alerts, history, and operational visibility.

The plugin is a compact site companion and connector. It is not a second full dashboard. Deeper account, report, alert, billing, portfolio, and agency management happens in the OpsGate web console according to the site’s plan.

OpsGate helps answer one practical question:

What is the condition of this site right now, why is it in that condition, and where do I need to act?

= What OpsGate provides =

* Public/external checks for Free sites.
* Connected WordPress triage for Starter and higher plans.
* Evidence-backed posture summaries.
* Site-scoped reports and history.
* Alert routing according to plan limits.
* Operational visibility for site owners, operators, and agencies.
* Hybrid plugin + web console workflows for Pro and Agency plans.

= Tier model =

Free:
External/public checks only. Free does not require connected plugin credentials and does not imply authenticated WordPress inventory, plugin, theme, PHP/runtime, or update-posture truth.

Starter:
Plugin-led connected triage for one connected site, with limited reports and alert routing according to the active plan.

Pro:
Hybrid plugin + web console operations for deeper site triage, reports, alerts, activity, and settings according to Pro limits.

Agency:
Hybrid multi-site and portfolio operations for agencies managing multiple WordPress sites.

= Product surface model =

The installed WordPress plugin is the local connector and site companion.

The OpsGate web console is the management layer for account, billing, reports, alerts, portfolio, activity, and deeper operations.

This separation keeps the plugin site-scoped and avoids exposing broad account or portfolio controls inside every connected WordPress admin.

= Privacy and authority model =

OpsGate uses the OpsGate API and canonical backend records as the source of truth for connected site identity, triage runs, reports, alerts, and plan limits.

The plugin does not act as the authority for plan entitlement, run truth, report truth, or alert truth.

== Installation ==

= From WordPress.org when publicly listed =

1. In WordPress Admin, go to Plugins > Add New.
2. Search for “OpsGate”.
3. Click Install.
4. Click Activate.
5. Open the OpsGate menu in WordPress Admin.
6. Follow the onboarding instructions to run a public check or connect the site to OpsGate.

= From a ZIP package during beta or custom distribution =

1. Download the current OpsGate plugin ZIP from the official OpsGate distribution path.
2. In WordPress Admin, go to Plugins > Add New.
3. Click Upload Plugin.
4. Choose the OpsGate ZIP file.
5. Click Install Now.
6. Activate the plugin.
7. Open the OpsGate menu in WordPress Admin.

= Free public check =

Free users can run public/external checks without connecting authenticated WordPress inventory.

The plugin may help identify the current site URL and guide the user to the public check or upgrade path.

= Starter, Pro, and Agency connection =

Connected plans use an OpsGate-authorized pairing flow.

1. Create or open your OpsGate account.
2. Add or select the WordPress site.
3. Generate or open the connection flow from OpsGate.
4. Complete pairing from the WordPress plugin.
5. Once connected, run site triage and review results according to your plan.

Do not manually invent account IDs, site IDs, or API credentials. Use the OpsGate connection flow.

== Frequently Asked Questions ==

= Is the plugin the full OpsGate dashboard? =

No. The plugin is a compact connector and site companion. The OpsGate web console is the management surface for deeper reports, alerts, billing, portfolio, and agency operations.

= Can Free users connect authenticated WordPress inventory? =

No. Free is external/public only. It can use public checks such as reachability, SSL/TLS posture, public availability, and public performance signals. Connected WordPress inventory and deeper authenticated evidence require a connected plan.

= What happens after I upgrade to Starter? =

Starter enables plugin-led connected triage for a connected site. The plugin can connect to OpsGate, run site triage, show latest result summaries, and route to allowed report and alert actions.

= Does OpsGate store the truth in the WordPress plugin? =

No. OpsGate uses the OpsGate API and backend database as the canonical source of truth for connected site identity, triage runs, reports, alerts, and plan limits. The plugin reads and displays that truth.

= Can agencies manage multiple sites? =

Yes, Agency is designed for multi-site portfolio operations through the OpsGate web console, with the plugin installed as a site-specific companion on each connected WordPress site.

= Does OpsGate use n8n? =

n8n may be used by OpsGate as private downstream orchestration behind the OpsGate API. It is not a customer-facing product surface and is not required for WordPress users to configure.

= Where do I view reports and alerts? =

The plugin may show summaries and tier-allowed shortcuts. Deeper report, alert, activity, billing, and portfolio management happens in the OpsGate web console according to your plan.

== Screenshots ==

1. OpsGate compact WordPress companion surface.
2. Site connection and latest triage summary.
3. Evidence-backed report summary.
4. OpsGate web console overview.
5. Tier-aware report and alert surfaces.

== Changelog ==

= 0.10.8 =
* Remote companion rebuilt as premium 2026+ SaaS connector experience (Slice 5.12).
* Two-path onboarding: Free public check vs Connect with Pairing Code.
* State-aware shell: onboarding_required, free_public_companion, connected_companion, credential_invalid, disconnected variants.
* Repair banner for credential_invalid and disconnected states with direct CTA.
* Hero band: identity block (site name + URL), tier badge, connection mode/status pills.
* 2-card topline grid: score with tone-color left border, last-checked timestamp.
* Scope card in secondary column sidebar: scope label, site, URL, mode.
* Support diagnostics section: collapsed behind Open support diagnostics affordance.
* Refresh tertiary action in connected_companion hero actions.
* Surface shape policy harness updated to locked tab architecture (no standalone clients tab for Free/Starter/Pro).

= 0.10.7 =
* Aligned release version contract to 0.10.7 across plugin header, update metadata, and DB release row.
* Closed the Multi-Site Onboarding + Context Law implementation: canonical onboarding session table, 6 API endpoints, remote plugin creates DB session before every central handoff, central resolver reads session token first.
* Closed the remote onboarding to paid connection lifecycle: pending_auth sessions can be claimed by any operator account, pairing session auto-advances onboarding session to pairing_ready.
* Closed requested-site paid lifecycle on remote proof sites: wrong-account safe handoff, setup/pairing binding to requested site, remote connected readback from API-backed truth.

= 0.10.6 =
* Fixed remote paid-pairing lifecycle: roster suppression, pairing button states, account_id mismatch on session resolve.
* Fixed pending_auth session claim and pairing auto-bind for remote to paid lifecycle.
* Fixed remote onboarding to paid connection lifecycle.

= 0.10.5 =
* Closed the final central WP Admin Alerts and Activity readback gap for the entitled vulnerability-delivery proof path.
* Recorded human-confirmed Gmail receipt for the canonical vulnerability alert proof destination.
* Promoted the stable public package and update metadata to 0.10.5.

== Upgrade Notice ==

= 0.10.7 =
Release contract alignment and onboarding session lifecycle closure. Multi-site onboarding, paid pairing lifecycle, and requested-site scope authority are now fully API-backed.

= 0.10.5 =
Final readback-closure release. Central Alerts and Activity now have release-recorded proof for the canonical vulnerability event path.
