Repository navigation
fix(free): isolate public Woo payload from historical runtime (#120) - #132
Merged
Merged
Conversation
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
Closes #120. Based on merged main
1a5c2fcb4caa9f4f49785cf65eee1fec71b8d615.wordpress/release/PUBLIC-PAYLOAD.md(57 PHP files, each classified once).Verification
Local: public staging/preflight, all 35 public PHP lints, source/readme audit, complete PHP inventory, adversarial packaging cases, fixture PHP/shell lint, and #107 unit suite (2,564 assertions) pass.
The actual manifest-only #111 fixture now checks clean Woo 11.1.2 activation without Redirection or restricted credentials, registered menus/hooks/routes/CLI absence, deactivate/reactivate, runner-first uninstall, retained evidence, owned-only scheduler cancellation, and stock Redirection 5.5.2 global Disable with public WriteLeash inactive/active (including forged historical options in a fresh process). It continues to execute the full Admin/browser preview/execution/history/Undo journey on MySQL/MariaDB and default/Redis cache.
Final head:
83b3b58588045f998ec990c5ee43017a7b43d344— all 20 checks PASS. Diff: 32 files, +721/-202. Public payload: 37 files, including 35 PHP files and 54 resolved class/interface/trait definitions. All 22 historical PHP files and the #61/#109/#110 race assertions are unchanged.The
woo-admin-111artifact proves on both MySQL and MariaDB:#61 failed-attempt disclosure (assertions unchanged)
Every failed transcript is retained on GitHub under attempt-specific artifact names for 30 days and was downloaded locally before rerunning. No concurrency/barrier test was edited or skipped.
83b3b58: adapter attempts 1 and 2 FAIL at the known MySQLawait_overlap(update)harness timeout; exact unchanged-SHA attempt 3 PASS. Release matrix attempt 1 FAIL at the same known MariaDB timeout; exact unchanged-SHA attempt 2 PASS. Passing artifacts prove distinct restricted sessions blocked on the certified UPDATE in both engines before barrier release, followed by both requests COMMITTED with consumed=6 and L=10.26c7bcd: adapter attempt 1 FAIL (MySQL CommitCap for WordPress: review the cooperative shared-runtime and selected adapter threat model #61 timeout), exact unchanged-SHA attempt 2 PASS. Release matrix attempts 1 and 2 FAIL at the MySQL CommitCap for WordPress: review the cooperative shared-runtime and selected adapter threat model #61 timeout; both retained. Lateref26b5dadapter and release matrix both passed.deactivatedrunner value and initialize CLI Admin menu globals; omititemsin the genuine stock Redirection global request (its stock handler givesisset(items)precedence, including empty arrays). Public runtime and historical invariants did not change in these corrections.Preserved support contract
NEW Free job max 100; engineering selector max 1000; Woo 11.1.2 exactly; grandfathered >100 bounded recovery/Undo; multisite unsupported. No journal redesign or compatibility expansion. This PR must not be merged by its author.