Skip to content

fix(free): isolate public Woo payload from historical runtime (#120) - #132

Merged
MrDarkRoot merged 3 commits into
mainfrom
release/120-public-free-payload
Oct 2, 2026
Merged

MrDarkRoot merged 3 commits into
mainfrom
release/120-public-free-payload

Conversation

@MrDarkRoot

@MrDarkRoot MrDarkRoot commented Oct 2, 2026 •

Copy link
Copy Markdown
Owner

Summary

Closes #120. Based on merged main 1a5c2fcb4caa9f4f49785cf65eee1fec71b8d615.

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.

Final-head evidence Result / run
#107 immutable plan PASS — 37002200698
#108 durable journal PASS — 37002200690
#109 durable jobs PASS — 37002200881
#110 Undo and unchanged uninstall races PASS — 37002200984
#111 and #120 exact public payload smoke PASS — 37002200734
#112 seven acceptance jobs, including 10,000-product catalog and PHP 7.4/8.0/8.1 PASS — 37002200860
Historical Redirection adapter, #61 PASS — 37002200695 attempt 3
Historical release matrix, including operator example and Plugin Check PASS — 37002200878 attempt 2
Foundation, both engines PASS — 37002200754
Engine/Guard/Doctor/provisioning research PASS — 37002200803
Plugin research PASS — 37002200799
MySQL/MariaDB feasibility PASS — 37002200955
Native PG security research PASS — 37002200850

The woo-admin-111 artifact proves on both MySQL and MariaDB:

  • Manifest-only Woo 11.1.2 activation, Redirection absent, restricted credentials absent, no trigger/routine setup.
  • Registered WriteLeash callback classes are only Lifecycle, Free_Admin, Job_Resume_Rest, Undo_Rest, Job_Worker, Undo_Worker and Undo_Scheduler. Exactly two Free REST routes; no Advanced menu/handler, Guard query interception, certified Redirection interception or WriteLeash CLI namespace.
  • The full Admin/browser preview/execution/history/Undo path passes in default and Redis cache modes.
  • Deactivate/reactivate retains evidence and prices. Actual WordPress uninstall shuts the runner down as its FIRST write, cancels only owned AS groups, retains durable evidence, and executes no privilege/DDL/Woo/Redirection mutation.
  • Stock Redirection inactive baseline and public WriteLeash-active requests both return HTTP 200, execute one stock global Disable UPDATE, and leave all six redirects disabled as seen by a fresh ordinary-account observer. Fresh-process forged historical options cannot enable interception.

#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.

  • Final SHA 83b3b58: adapter attempts 1 and 2 FAIL at the known MySQL await_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.
  • Earlier SHA 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. Later ef26b5d adapter and release matrix both passed.
  • Earlier new public-smoke fixture errors were corrected in test-only follow-up commits: use the existing deactivated runner value and initialize CLI Admin menu globals; omit items in the genuine stock Redirection global request (its stock handler gives isset(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.

@MrDarkRoot
MrDarkRoot merged commit 22a89ec into main Oct 2, 2026
20 of 23 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.

WriteLeash Free 1.0: isolate legacy Redirection/Advanced substrate from the public WooCommerce release

1 participant