{"id":322824,"date":"2026-06-07T19:35:47","date_gmt":"2026-06-07T19:35:47","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/site-briefing\/"},"modified":"2026-09-26T19:12:20","modified_gmt":"2026-09-26T19:12:20","slug":"aifq-site-review","status":"publish","type":"plugin","link":"https:\/\/arq.wordpress.org\/plugins\/aifq-site-review\/","author":23511736,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.17.0","stable_tag":"1.17.0","tested":"7.1.2","requires":"6.0","requires_php":"8.1","requires_plugins":null,"header_name":"Site Current","header_author":"Site Current","header_description":"The clean second opinion for WordPress. See what needs attention, why it matters and who should handle it.","assets_banners_color":"cadef8","last_updated":"2026-09-26 19:12:20","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"","rating":5,"author_block_rating":0,"active_installs":0,"downloads":719,"num_ratings":1,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.10.0":{"tag":"1.10.0","author":"aifq","date":"2026-08-26 07:33:40","revision":3666438},"1.11.0":{"tag":"1.11.0","author":"aifq","date":"2026-08-28 21:13:12","revision":3670932},"1.12.0":{"tag":"1.12.0","author":"aifq","date":"2026-08-29 19:33:39","revision":3671841},"1.13.0":{"tag":"1.13.0","author":"aifq","date":"2026-08-31 19:05:03","revision":3674834},"1.13.1":{"tag":"1.13.1","author":"aifq","date":"2026-08-31 22:54:53","revision":3675025},"1.14.0":{"tag":"1.14.0","author":"aifq","date":"2026-09-02 21:30:58","revision":3678694},"1.15.0":{"tag":"1.15.0","author":"aifq","date":"2026-09-04 15:58:54","revision":3681476},"1.16.0":{"tag":"1.16.0","author":"aifq","date":"2026-09-12 17:17:02","revision":3692950},"1.16.1":{"tag":"1.16.1","author":"aifq","date":"2026-09-15 12:20:23","revision":3696949},"1.17.0":{"tag":"1.17.0","author":"aifq","date":"2026-09-26 19:12:20","revision":3714651},"1.6.0":{"tag":"1.6.0","author":"aifq","date":"2026-06-07 19:35:23","revision":3563868},"1.7.0":{"tag":"1.7.0","author":"aifq","date":"2026-06-09 12:08:40","revision":3565967},"1.8.0":{"tag":"1.8.0","author":"aifq","date":"2026-06-11 08:39:07","revision":3568518},"1.9.0":{"tag":"1.9.0","author":"aifq","date":"2026-06-16 20:55:00","revision":3574993}},"upgrade_notice":{"1.17.0":"<p>Introduces Site Current, the new name for AIFQ Site Review, with redesigned Current, History, Data, Decisions and Settings workspaces plus optional external checks. Existing review history, Decision Memory and settings are preserved; external checks still require a deliberate administrator choice.<\/p>","1.16.1":"<p>Fixes a false positive where retained Action Scheduler failure history could be presented as a current site problem.<\/p>","1.16.0":"<p>Clarifies what AIFQ observed, what is interpretation, and what to do next, with a calmer returning-review hierarchy and clearer temporal context.<\/p>","1.15.0":"<p>Improves returning reviews with a clearer first step, visible change conclusions, contextual Why now and Decision on record, exact item-level change details, and calmer status wording.<\/p>","1.14.0":"<p>Adds reliable Meaningful Changes between saved reviews, with New, Resolved and checks that can now be reviewed, plus stronger review-history integrity across cache recovery and site identity changes.<\/p>","1.13.1":"<p>Fixes duplicate local page-cache guidance on WooCommerce sites while preserving the generic cache guidance on non-WooCommerce sites.<\/p>","1.13.0":"<p>Adds a conservative Operational Integrity foundation for selected WordPress and WooCommerce states, including WooCommerce database\/Checkout checks and provider-evidenced persistent object-cache failures, while keeping Decision Memory and review data local.<\/p>","1.12.0":"<p>Adds local Decision Memory for selected findings so previous decisions and optional context can remain available in later reviews without overriding current technical state.<\/p>","1.11.0":"<p>Improves the local continuity foundation used between reviews and hardens plugin\/theme change handling.<\/p>","1.10.2":"<p>Interaction polish lets expanded Since your last review change lists collapse back to the compact three-item view.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":1},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3714651,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3714651,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3714651,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3714651,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.10.0","1.11.0","1.12.0","1.13.0","1.13.1","1.14.0","1.15.0","1.16.0","1.16.1","1.17.0","1.6.0","1.7.0","1.8.0","1.9.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3714651,"resolution":"1","location":"assets","locale":"","width":1600,"height":1000},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3714651,"resolution":"2","location":"assets","locale":"","width":1600,"height":1000},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3714651,"resolution":"3","location":"assets","locale":"","width":1600,"height":1000},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3714651,"resolution":"4","location":"assets","locale":"","width":1600,"height":1000},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3714651,"resolution":"5","location":"assets","locale":"","width":1600,"height":1000}},"screenshots":{"1":"Current gives you a calm current picture: what needs attention, what is worth reviewing and what already looks good.","2":"History compares saved reviews over time without assuming that a disappeared finding was fixed.","3":"Data explains every check in plain language and keeps the underlying technical record one click away.","4":"Decisions keeps the human reason behind selected findings without changing the technical review result.","5":"Settings lets you choose local-only reviews or deliberate external checks while review history and Decision Memory remain in WordPress."}},"plugin_section":[],"plugin_tags":[23519,732,151481,8541,286],"plugin_category":[45,52],"plugin_contributors":[266105],"plugin_business_model":[],"class_list":["post-322824","plugin","type-plugin","status-publish","hentry","plugin_tags-diagnostics","plugin_tags-maintenance","plugin_tags-site-health","plugin_tags-troubleshooting","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_category-performance","plugin_contributors-aifq","plugin_committers-aifq"],"banners":{"banner":"https:\/\/ps.w.org\/aifq-site-review\/assets\/banner-772x250.png?rev=3714651","banner_2x":"https:\/\/ps.w.org\/aifq-site-review\/assets\/banner-1544x500.png?rev=3714651","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/aifq-site-review\/assets\/icon-128x128.png?rev=3714651","icon_2x":"https:\/\/ps.w.org\/aifq-site-review\/assets\/icon-256x256.png?rev=3714651","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/aifq-site-review\/assets\/screenshot-1.png?rev=3714651","caption":"Current gives you a calm current picture: what needs attention, what is worth reviewing and what already looks good."},{"src":"https:\/\/ps.w.org\/aifq-site-review\/assets\/screenshot-2.png?rev=3714651","caption":"History compares saved reviews over time without assuming that a disappeared finding was fixed."},{"src":"https:\/\/ps.w.org\/aifq-site-review\/assets\/screenshot-3.png?rev=3714651","caption":"Data explains every check in plain language and keeps the underlying technical record one click away."},{"src":"https:\/\/ps.w.org\/aifq-site-review\/assets\/screenshot-4.png?rev=3714651","caption":"Decisions keeps the human reason behind selected findings without changing the technical review result."},{"src":"https:\/\/ps.w.org\/aifq-site-review\/assets\/screenshot-5.png?rev=3714651","caption":"Settings lets you choose local-only reviews or deliberate external checks while review history and Decision Memory remain in WordPress."}],"raw_content":"<!--section=description-->\n<p>Site Current gives you a clear technical second opinion on a WordPress site without turning the result into another alarm dashboard.<\/p>\n\n<p>If you already use AIFQ Site Review, Site Current is the same plugin under its new name. Your saved reviews, Decision Memory and existing settings stay with the plugin when you upgrade.<\/p>\n\n<p>Run a review when you inherit a site, finish maintenance, change hosting or configuration, or simply want to know what deserves attention. Site Current reduces many technical checks into a smaller set of useful answers:<\/p>\n\n<ul>\n<li>what needs attention now<\/li>\n<li>what is worth reviewing<\/li>\n<li>what already looks good in the checks that were completed<\/li>\n<li>what Site Current could not verify<\/li>\n<li>what changed between saved reviews<\/li>\n<li>useful site context that does not imply a problem<\/li>\n<\/ul>\n\n<p>The main Current screen stays focused. History, Data, Decisions and Settings are there when you want more context or technical detail.<\/p>\n\n<h4>Built for repeat reviews<\/h4>\n\n<p>A review is a point-in-time picture. WordPress sites keep changing.<\/p>\n\n<p>Site Current stores review history locally so later reviews can be compared with earlier ones. It uses conservative wording: a finding that disappears is not automatically described as fixed, and missing evidence is not turned into a healthy result.<\/p>\n\n<p>For selected findings, Decision Memory lets you record why you chose to keep the current setup, handle something elsewhere, defer it or add your own context. Earlier decision records are kept instead of silently overwritten.<\/p>\n\n<h4>Local-first, with optional external checks<\/h4>\n\n<p>Core review analysis, review history and Decision Memory stay in your WordPress database. Site Current does not include telemetry or usage tracking.<\/p>\n\n<p>You can also choose to enable external checks. These run only when an administrator deliberately starts a review. WordPress sends only the site's public hostname to Site Current's external check service. The service can then inspect the site's public HTTPS connection and selected public endpoints such as the homepage, robots.txt and standard sitemap locations.<\/p>\n\n<p>The current service is operated for Site Current at these fixed HTTPS endpoints:<\/p>\n\n<ul>\n<li><code>https:\/\/aifq-external-tls-gateway-153652489836.europe-west4.run.app\/v1\/probe\/tls<\/code><\/li>\n<li><code>https:\/\/aifq-external-http-gateway-153652489836.europe-west4.run.app\/v1\/probe\/http<\/code><\/li>\n<\/ul>\n\n<p>Private WordPress content, users, credentials, plugin\/theme inventory and review history are not sent to the external check service. Service details, data handling and terms are documented at <a href=\"https:\/\/github.com\/AIFQ-SR\/AIFQ-Site-Review\/blob\/main\/EXTERNAL-SERVICE.md\">Site Current external service &amp; privacy<\/a>.<\/p>\n\n<h4>What Site Current is not<\/h4>\n\n<p>Site Current is not a replacement for specialist tools. It is not:<\/p>\n\n<ul>\n<li>a vulnerability or malware scanner<\/li>\n<li>a firewall<\/li>\n<li>a live speed test or PageSpeed tool<\/li>\n<li>an uptime guarantee<\/li>\n<li>a backup service<\/li>\n<li>a generic activity log<\/li>\n<li>an automatic fixer<\/li>\n<\/ul>\n\n<p>Where WordPress or one external observation cannot support a strong conclusion, Site Current keeps the claim narrow and shows the gap instead of guessing.<\/p>\n\n<h3>Privacy<\/h3>\n\n<p>Site Current is local-first:<\/p>\n\n<ul>\n<li>Core review analysis, saved reviews and Decision Memory stay in WordPress.<\/li>\n<li>No telemetry or usage tracking is included.<\/li>\n<li>External checks are optional and run only as part of a deliberately started review after an administrator enables them.<\/li>\n<li>When external checks are enabled, WordPress sends only the site's public hostname to the fixed Site Current-operated TLS and HTTP gateway endpoints listed above.<\/li>\n<li>The service may request the site's public homepage, robots.txt and standard sitemap locations and may follow a limited number of redirects that remain within the same public site.<\/li>\n<li>Service details, data handling and terms are published at <a href=\"https:\/\/github.com\/AIFQ-SR\/AIFQ-Site-Review\/blob\/main\/EXTERNAL-SERVICE.md\">Site Current external service &amp; privacy<\/a>.<\/li>\n<li>Raw page bodies are not returned in the review.<\/li>\n<li>Private WordPress content, users, credentials, plugin\/theme inventory and review history are not sent to the external check service.<\/li>\n<li>Like other web services, the external service receives ordinary request metadata such as request time and network address. Ordinary platform and request logs are currently retained for 30 days.<\/li>\n<li>WooCommerce customer records, orders and payment data are not read for review findings.<\/li>\n<li>Passwords, API keys, WordPress salts and secret credentials are not collected or reported.<\/li>\n<li>A small number of account-related checks use limited local facts such as whether the username <code>admin<\/code> exists and aggregate account counts. User email addresses and password values are not included in review output.<\/li>\n<\/ul>\n\n<p>Site Current does not provide a cloud dashboard and does not upload your saved review history.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>In WordPress, go to Plugins &gt; Add New.<\/li>\n<li>Search for \"Site Current\".<\/li>\n<li>Install and activate the plugin.<\/li>\n<li>Open Site Current from the admin menu.<\/li>\n<li>Choose whether reviews should stay local only or also use the optional external checks.<\/li>\n<li>Run your first review.<\/li>\n<\/ol>\n\n<p>Manual installation works the same way after uploading the plugin ZIP or extracted <code>aifq-site-review<\/code> folder.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"what%20does%20site%20current%20actually%20do%3F\"><h3>What does Site Current actually do?<\/h3><\/dt>\n<dd><p>It reviews selected WordPress configuration, operational and public-site signals and turns them into a focused current picture. The main screen separates items that need attention from items worth reviewing, while Data shows the checks and technical records behind that summary.<\/p><\/dd>\n<dt id=\"is%20site%20current%20the%20same%20plugin%20as%20aifq%20site%20review%3F\"><h3>Is Site Current the same plugin as AIFQ Site Review?<\/h3><\/dt>\n<dd><p>Yes. Site Current is the new name for AIFQ Site Review. Existing installations can upgrade normally, and saved review history, Decision Memory and settings remain available.<\/p><\/dd>\n<dt id=\"why%20would%20i%20keep%20site%20current%20installed%20after%20the%20first%20review%3F\"><h3>Why would I keep Site Current installed after the first review?<\/h3><\/dt>\n<dd><p>Because the site changes. Keeping Site Current installed lets you compare later reviews with earlier saved reviews instead of starting from zero each time. Decision Memory can also keep the reason behind selected human decisions.<\/p><\/dd>\n<dt id=\"does%20site%20current%20continuously%20monitor%20my%20site%3F\"><h3>Does Site Current continuously monitor my site?<\/h3><\/dt>\n<dd><p>No. Site Current does not run scheduled reviews in this version. Reviews are started deliberately by an administrator. A limited amount of local continuity data can be retained so later reviews can be interpreted more reliably.<\/p><\/dd>\n<dt id=\"does%20site%20current%20send%20review%20data%20externally%3F\"><h3>Does Site Current send review data externally?<\/h3><\/dt>\n<dd><p>Core review analysis and saved review history stay local. If you enable external checks, WordPress sends only the site's public hostname to Site Current's external check service when you deliberately start a review. The service then checks selected public endpoints itself. Private WordPress content, users, credentials, plugin\/theme inventory and review history are not sent.<\/p><\/dd>\n<dt id=\"what%20are%20external%20checks%20for%3F\"><h3>What are external checks for?<\/h3><\/dt>\n<dd><p>They add an outside view that WordPress cannot provide from inside the site. The current external checks can inspect the public HTTPS connection and selected public web responses. One external observation is still treated as one perspective, not as an uptime guarantee or Internet-wide consensus.<\/p><\/dd>\n<dt id=\"what%20is%20decision%20memory%3F\"><h3>What is Decision Memory?<\/h3><\/dt>\n<dd><p>For selected findings, Decision Memory lets you save the human context behind a choice such as keeping the current setup, handling it elsewhere or deferring it. A later review can show that context without treating the decision as technical truth or proof that something was fixed.<\/p><\/dd>\n<dt id=\"does%20site%20current%20fix%20issues%20automatically%3F\"><h3>Does Site Current fix issues automatically?<\/h3><\/dt>\n<dd><p>No. Site Current explains what it found and provides context for the next step, but it does not automatically change your website.<\/p><\/dd>\n<dt id=\"do%20all%20findings%20mean%20something%20is%20definitely%20wrong%3F\"><h3>Do all findings mean something is definitely wrong?<\/h3><\/dt>\n<dd><p>No. Some checks produce clear local facts, while others produce context, a review suggestion or a knowledge gap. Site Current is intentionally conservative when the available evidence does not support a stronger claim.<\/p><\/dd>\n<dt id=\"is%20site%20current%20a%20security%20scanner%20or%20speed%20test%3F\"><h3>Is Site Current a security scanner or speed test?<\/h3><\/dt>\n<dd><p>No. It can surface selected security, performance and reliability signals, but it is not a vulnerability scanner, malware scanner, firewall, PageSpeed replacement or full security\/performance audit.<\/p><\/dd>\n<dt id=\"who%20is%20site%20current%20for%3F\"><h3>Who is Site Current for?<\/h3><\/dt>\n<dd><p>WordPress site owners, WooCommerce store owners, freelancers, agencies and hosting\/support teams who want a clearer second opinion before changing something or asking someone else for help.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.17.0<\/h4>\n\n<ul>\n<li>Renames the public product from AIFQ Site Review to Site Current while preserving the existing WordPress.org installation and compatible stored identities.<\/li>\n<li>Introduces the redesigned Current workspace with a focused summary of what needs attention, what is worth reviewing and what already looks good.<\/li>\n<li>Adds dedicated History, Data, Decisions and Settings workspaces for review continuity, plain-language check detail, human decision context and review-mode control.<\/li>\n<li>Adds optional external HTTPS and public-site checks that run only after an administrator deliberately enables them and starts a review.<\/li>\n<li>Keeps saved review history and Decision Memory local in the WordPress installation while making their continuity visible across the new workspaces.<\/li>\n<li>Uses conservative temporal wording such as No longer flagged instead of assuming that a disappeared finding was fixed.<\/li>\n<li>Preserves existing review history, Decision Memory, site identity and settings when upgrading from 1.16.1.<\/li>\n<li>Improves plain-language check names and explanations so Current and Data make it clearer why an item is being shown.<\/li>\n<\/ul>\n\n<h4>1.16.1<\/h4>\n\n<ul>\n<li>Stops cumulative historical Action Scheduler failures from creating current Needs attention or Worth reviewing findings.<\/li>\n<li>Keeps the existing overdue pending-actions signal under a narrower, separate finding identity without adding a new threshold.<\/li>\n<li>Preserves historical readability for the retired Action Scheduler finding identities.<\/li>\n<\/ul>\n\n<h4>1.16.0<\/h4>\n\n<ul>\n<li>Reworks finding copy to distinguish direct observations, thresholds and heuristic signals, consequences, and recommended actions more clearly.<\/li>\n<li>Tightens impact and recommendation wording so AIFQ does not imply causes, outcomes, or infrastructure conditions that WordPress cannot verify.<\/li>\n<li>Keeps Review Assessment first on returning reviews, followed by Meaningful Changes, and attaches Start here to the already-prioritized first attention item.<\/li>\n<li>Gives New, Resolved, No longer shown and Can now be checked calmer temporal presentation without changing detector, state, or priority logic.<\/li>\n<li>Makes Decision on record and the developer \/ host handoff quieter context while Run new review remains the primary action.<\/li>\n<li>Refreshes and verifies the translation catalog against the current user-facing source strings.<\/li>\n<\/ul>\n\n<h4>1.15.0<\/h4>\n\n<ul>\n<li>Adds a clear Start here first step while keeping finding cards collapsed by default.<\/li>\n<li>Makes returning-review change conclusions visible and reports New, Resolved, newly reviewable and observed presence changes with exact item names.<\/li>\n<li>Adds Why now context for strong New and Can now be checked cases without overstating uncertain temporal changes.<\/li>\n<li>Shows current Decision Memory context as Decision on record before new advice.<\/li>\n<li>Improves returning-review hierarchy and calmer status copy, including headlines that reflect the total number of Needs attention items.<\/li>\n<\/ul>\n\n<h4>1.14.0<\/h4>\n\n<ul>\n<li>Adds reliable <code>Since your last review<\/code> tracking for meaningful New, Resolved and newly reviewable checks between saved reviews.<\/li>\n<li>Prevents findings from being marked New or Resolved when the underlying check could not be compared reliably.<\/li>\n<li>Strengthens local review history so successful reviews remain ordered and readable across persistent object-cache recovery and failed review saves.<\/li>\n<li>Keeps review continuity tied to the correct site and starts a fresh comparison boundary after site identity changes.<\/li>\n<li>Improves change-history wording so temporal claims stay scoped to what AIFQ could actually compare.<\/li>\n<li>Refines Object cache status in Site context to distinguish Active, Not active, Issue detected and Not detected states.<\/li>\n<\/ul>\n\n<h4>1.13.1<\/h4>\n\n<ul>\n<li>Prevents WooCommerce sites without a local page-cache signal from showing both the generic cache finding and the WooCommerce-specific cache finding for the same underlying signal.<\/li>\n<li>Preserves the generic <code>No local page-cache signal detected<\/code> finding on non-WooCommerce sites.<\/li>\n<\/ul>\n\n<h4>1.13.0<\/h4>\n\n<ul>\n<li>Adds an explicit local Capability &amp; Evaluation foundation for selected operational checks, distinguishing evaluated, not-applicable, unobservable and evaluation-error states so uncertainty remains explicit.<\/li>\n<li>Adds WooCommerce database integrity using WooCommerce's own database-update state and suppresses the finding while a WooCommerce database-update task is already queued.<\/li>\n<li>Adds WooCommerce Checkout structural checks for a missing configured Checkout page, a configured Checkout page that is not public, and a published Checkout page without WooCommerce-recognized Checkout block\/shortcode content.<\/li>\n<li>Adds conservative persistent object-cache integrity: a provider failure is shown only when AIFQ has trustworthy local provider-health evidence, while inactive or hosting-managed states remain neutral when failure evidence is unavailable.<\/li>\n<li>Adds a conservative Core Database Integrity safety net for rare local database-version mismatch states.<\/li>\n<li>Clarifies page-cache wording by keeping local WordPress page-cache signals separate from persistent object caching and server\/edge caching, while preserving stable finding identities and historical Decision Memory compatibility.<\/li>\n<li>Hardens cross-layer release quality: every current attention finding now has an explicit priority, developer\/host handoff counts remain accurate, repeated Memory initialization failures back off safely, Decision Memory schema checks are request-memoized, and current findings have explicit translatable display copy.<\/li>\n<li>Keeps current WordPress state authoritative and preserves immutable Decision Memory history.<\/li>\n<\/ul>\n\n<h4>1.12.0<\/h4>\n\n<ul>\n<li>Adds local Decision Memory for selected findings with clear outcomes and optional context notes.<\/li>\n<li>Keeps Decision history immutable: reviewing an existing decision creates a new superseding record instead of overwriting the earlier decision.<\/li>\n<li>Shows previous Decision context when the same finding is active again, while keeping current WordPress state authoritative.<\/li>\n<li>Extends the Decision flow to eligible Worth reviewing findings while preserving their Worth reviewing classification.<\/li>\n<li>Keeps ineligible findings on the established one-click reviewed flow.<\/li>\n<li>Keeps Decision Memory and technical continuity data local to WordPress.<\/li>\n<\/ul>\n\n<h4>1.11.0<\/h4>\n\n<ul>\n<li>Improves the local continuity foundation used between reviews so selected technical change context can be retained conservatively on the site.<\/li>\n<li>Hardens plugin and theme state handling across normal updates, automatic updates, direct filesystem changes, object-cache environments and reverse-proxy HTTP\/HTTPS differences.<\/li>\n<li>Treats uncertain filesystem reads conservatively so temporary read failures are not recorded as plugin or theme removals.<\/li>\n<li>Keeps historical continuity separate from the current review so active findings continue to come from current review state.<\/li>\n<li>Keeps continuity data local and bounded inside WordPress.<\/li>\n<\/ul>\n\n<h4>1.10.2<\/h4>\n\n<ul>\n<li>Makes the expanded <code>Since your last review<\/code> change list reversible: <code>View all<\/code> now toggles to <code>Show fewer changes<\/code> and collapses back to the compact three-change view.<\/li>\n<li>Keeps the change control keyboard-accessible with <code>aria-expanded<\/code> state and returns the control to view after collapsing a long list.<\/li>\n<\/ul>\n\n<h4>1.10.1<\/h4>\n\n<ul>\n<li>Removes the legacy 0\u2013100 score from the dashboard, review summary and developer\/host handoff; new reviews no longer store score or subscore values.<\/li>\n<li>Treats the first 1.10.1 review as a fresh comparison baseline so changed AIFQ semantics are not presented as site changes.<\/li>\n<li>Reworks Since your last review so saved-review comparisons keep change timing scoped to the review points AIFQ actually recorded.<\/li>\n<li>Shows when a previously reviewed finding becomes relevant again and adds an \"If left as-is\" consequence where useful.<\/li>\n<li>Makes HTTPS, caching, cron and plugin-absence wording more conservative where WordPress cannot see the full hosting or external setup.<\/li>\n<li>Moves missing SEO, security and backup plugin detections to neutral Site context.<\/li>\n<li>Adds <code>aifq_sr_findings<\/code>, <code>aifq_sr_handoff_message<\/code> and <code>aifq_sr_review_summary<\/code> filters for trusted local integrations.<\/li>\n<li>Improves text contrast, minimum label sizes and review-status accessibility while preserving the Calm Control layout.<\/li>\n<li>Removes obsolete category-tab JavaScript and selected dead score code.<\/li>\n<\/ul>\n\n<h4>1.10.0<\/h4>\n\n<ul>\n<li>Rebuilds the review dashboard around the Calm Control visual direction with warmer neutral surfaces and restrained status color.<\/li>\n<li>Leads with Site status, meaningful change, prioritized Needs attention and quieter Worth reviewing items.<\/li>\n<li>Moves the full check inventory to a separate on-demand view so the main review stays calm and focused.<\/li>\n<li>Adds calmer, high-signal local checks for privileged registration defaults, pending administrator email changes, disabled page-load cron, administrator access, Application Password use, Action Scheduler backlog, autoloaded option attribution, environment-aware indexing and advanced WordPress components.<\/li>\n<\/ul>\n\n<h4>1.9.0<\/h4>\n\n<ul>\n<li>Adds Since your last review context, Last checked, Mark as reviewed and a shorter action-first dashboard.<\/li>\n<li>Reviewed findings can leave the active recommendations while remaining distinct from resolved findings.<\/li>\n<li>Adds severity-upgrade resurfacing for reviewed findings.<\/li>\n<li>Improves category navigation and secondary disclosure sections.<\/li>\n<\/ul>","raw_excerpt":"A calm WordPress second opinion that shows what needs attention, what changed, and what to look at next.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/322824","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=322824"}],"author":[{"embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/aifq"}],"wp:attachment":[{"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=322824"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=322824"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=322824"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=322824"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=322824"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=322824"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}