Repository navigation
compat(free,#280): pair-rule support and listing position (#322) - #330
Merged
Merged
Conversation
Keep the accidental price and stock overwrite listing, and state the tested legacy pairs without a WooCommerce 9.0 through 11.x rectangle. Redis on WordPress 6.8.3 with WooCommerce 9.9.7 stays untested. Stable tag remains 0.2.0.
The pinned v0.1 builder audits that source with package-preflight and readme-validate. Those checks now expect WordPress 6.7 only for the live package. The reviewed 0.1.0 header stays 7.0, and the pair-rule listing facts stay on the live tree.
The v0.2 package check was still requiring WordPress 7.0 and WooCommerce 10.0. Those floors now match the reviewed headers, 6.7 and 9.0. The readme cap matches the 10240-byte directory check. Screenshot captions stay exact.
MrDarkRoot
added
the
ci112:d58612c9cf6c0fd541e8bcff5ce8996959022415
The hermetic admin unit now supplies WordPress 7.1.2, so Resume still reaches the job-id check on the modern pair. WordPress 6.8.3 with WooCommerce 11 is refused before Resume or Undo and starts no worker. A live WordPress version outside both bands fails Apply at the environment gate. The journal case expects WOOCOMMERCE_VERSION_UNSUPPORTED, a PENDING row, and an unchanged price. In-band contract drift stays CONFLICT.
MrDarkRoot
added
the
ci112:28d65a413416edb69913cae034e265d973848283
Replace the public Supported scope heading with Requirements, What is supported, and Current limitations. Keep the tested pairs, the pair rule, and the same limitations. The restricted principal is bounded to documented monitored WooCommerce write paths and a matching Execution Frame. Direct SQL, hostile plugins, and unmonitored paths stay uncovered, including when the grant store is unavailable. Stable tag stays 0.2.0.
MrDarkRoot
added
the
ci112:dc84bce1083418305affa0acb814995c5f5dca65
This was referenced Oct 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
woo_supported()/wp_supported()are not authorization;support_band()is the gate, and a frozen plan must stay on the same band.Requires at least: 6.7andWC requires at least: 9.0are minimums, not a coverage map. Stable tag and Version stay 0.2.0. Tested up to stays 7.1 / WooCommerce 11.1.woocommerce, prices, stock, variations, undo. The restricted-agent subsection keeps the seatbelt sentence and the monitored grant path limits. It does not claim a firewall, hostile-plugin isolation, direct SQL protection, or universal agent safety.Evidence already run locally
Journeys ran on the pair-rule bytes later committed as
e8e14078and cherry-picked here. They were not repeated after #329 merged. Modern WordPress 7.1.2 + WooCommerce 11.1.2 was not re-executed. Persistent cache on WordPress 6.8.3 + WooCommerce 9.9.7 was not run.woocommerce_version_unsupportedplugin_wp_incompatible, minimum 6.7, plugin inactivePins: WooCommerce 9.0.4
230ba96dbd288c98ce76e8ce430a7d52ec0994596717bde978b5613839ff8333, 9.9.796facedd12e32b6e0b120dcaa4a62b9c6b1ae12159d32510ea416c8e9b44f4dd, 8.9.5260abd0d6dfd8afe0e10fb64d72b071be3b5623de8af072265758b35380b428b. Images:wordpress:6.7.2-php8.2-apache@sha256:85c7d25eaf9726eeff21adad930aa43d2894bd73e9253ab250737b6d994a1181,wordpress:6.8.3-php8.2-apache@sha256:1e6215749283955d5c9ffea6c297651ed23cdfdbb91677ad7abd705b2682f2cf,wordpress:6.6.2-php8.2-apache@sha256:c30c1376b4d2c9d1e2328c2ee6149d133104d65873a98cbc6adc743a2964c4ba.Hermetic on this head:
readme-validate.phpPASS (readme 10215 bytes, 121-character description, 5 tags, Stable tag 0.2.0),claim-matrix-audit.phpPASS (includes the conflict-copy audit),woo-candidate.phpPASS,package-preflight.phpPASS,free/unit.phppair-rule marker PASS (2623 assertions), historical shim boundary PASS.Review notes
PR_FASTandCI_COVERAGEare green on this exact head. Acceptance, foundation, and historical suites are in the path-ownership set because the support contract, plugin header, and acceptance harness changed.EOF