Skip to content

Add evidence-based plugin impact report - #239

Merged
mehul0810 merged 1 commit into
release/1.8.0from
feature/182-plugin-impact-report
Aug 11, 2026
Merged

Add evidence-based plugin impact report#239
mehul0810 merged 1 commit into
release/1.8.0from
feature/182-plugin-impact-report

Conversation

@mehul0810

Copy link
Copy Markdown
Collaborator

Closes #182.

Summary

  • adds a bounded Plugin Impact report that joins active-plugin Site Inventory data with high-confidence Admin Asset Audit evidence
  • reports measured admin screens, scripts, and styles without ranking plugins or claiming an observed asset is slow or safe to disable
  • labels frontend assets, query contribution, callback timing, and memory contribution as unavailable until dedicated measurement contracts exist
  • keeps collection local, private, bounded, and read-only; the report does not start scans or make external requests
  • documents the evidence and limitation contract

Validation

  • composer lint
  • scoped PHPCS for changed PHP files
  • composer test — 137 tests, 435 assertions
  • npm run test:unit — 37 tests
  • npm run lint
  • npm run build
  • PHPStan across 59 files
  • git diff --check

Hosted WordPress smoke proof must confirm the desktop/mobile report, responsive layout, and evidence/limitation language before merge.

@github-actions

Copy link
Copy Markdown

WordPress Playground Preview

The changes in this pull request can previewed and tested using a WordPress Playground instance.

Open WordPress Playground Preview

@mehul0810
mehul0810 merged commit 89494a4 into release/1.8.0 Aug 11, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant