fix: address WordPress.org plugin review (rename + prefixing + headers)

[kidunot89]

Your checklist for this pull request

• Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
• Make sure you are requesting to pull request from a topic/feature/bugfix/devops branch (right side). Don't pull request from your master!
• Have you ensured/updated that CLI tests to extend coverage to any new logic.

What does this implement/fix? Explain your changes.

Addresses the issues raised in the WordPress.org Plugin Directory review.

Trademark / naming (the gating issue). The directory display name/slug began with the WPGraphQL trademark (and WooGraphQL is a portmanteau of the WooCommerce mark), which can imply official affiliation.

• Display name (plugin header + README.txt title) → GraphQL for eCommerce.
• Slug / text domain → graphql-for-ecommerce (header, all i18n string literals across the plugin, and the PHPCS WordPress.WP.I18n text_domain config).
• User-facing notices/errors that named the old plugin were updated.
• WooGraphQL is kept only as the project's informal nickname (repo/docs/community), not in the directory's official name/slug. Internal file names and GitHub URLs are unchanged.

Prefix data storage. The session transaction queue transient used the generic woo_ word; it now uses the plugin's graphql_woocommerce_ namespace. (Audited the rest — define()s, options, and namespaced classes were already distinct.)

Plugin headers / packaging.

• Added Requires Plugins: woocommerce.
• README.txt "Tested up to" → 7.0.
• Ship composer.json in the distributed plugin (removed it, and composer.lock, from the composer archive excludes).

Items reviewed and left as-is (compliant): the only admin_notices is a current_user_can-gated dependency-missing error (not an upgrade nag, Guideline 11), and there is no unprotected request handling — the one pre-auth $_GET download endpoint validates an HMAC token (a nonce doesn't apply to unauthenticated download links).

Does this close any currently open issues?

…

Any relevant logs, error output, GraphiQL screenshots, etc?

composer lint and composer stan are clean. Full wpunit suite green after the rename:

vendor/bin/codecept run wpunit
Tests: 304, Assertions: 833, Skipped: 2

Any other comments?

The WordPress.org slug reservation (graphql-for-ecommerce) still needs to be requested by replying to the review email — that part is on the WordPress.org side and is not a code change.

[coveralls]

Coverage Report for CI Build 28450585642

Warning

Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes.
Quick fix: rebase this PR. Learn more →

Coverage remained the same at 91.801%

Details

• Coverage remained the same as the base build.
• Patch coverage: 257 uncovered changes across 83 files (1330 of 1587 lines covered, 83.81%).
• 1 coverage regression across 1 file.

Uncovered Changes

Top 10 Files by Coverage Impact	Changed	Covered	%
includes/type/object/class-root-query.php	74	49	66.22%
includes/data/mutation/class-checkout-mutation.php	17	1	5.88%
includes/type/interface/class-product-union.php	14	4	28.57%
includes/data/mutation/class-cart-mutation.php	9	3	33.33%
includes/mutation/class-order-note-delete.php	10	4	40.0%
includes/mutation/class-product-attribute-term-create.php	12	6	50.0%
includes/type/object/class-cart-error-types.php	12	6	50.0%
includes/connection/class-orders.php	13	8	61.54%
includes/mutation/class-product-attribute-term-delete.php	8	3	37.5%
includes/mutation/class-product-delete.php	8	3	37.5%
Total (201 files)	1587	1330	83.81%

Coverage Regressions

1 previously-covered line in 1 file lost coverage.

File	Lines Losing Coverage	Coverage
includes/mutation/class-product-attribute-term-create.php	1	86.41%

---

Coverage Stats

Relevant Lines:	20186
Covered Lines:	18531
Line Coverage:	91.8%
Coverage Strength:	153.15 hits per line

---

💛 - Coveralls