docs(free): prepare WooCommerce listing copy and claim matrix (#121)

[MrDarkRoot]

Summary

Closes #121. Phase B rebases this existing PR onto exact post-#133 main and repairs listing conflict language and historical minimum/dependency fixtures.

Exact final-head hosted CI PASS. Run 37024596744, attempt 2, on unchanged
head c5c427f1b7f9a6d1a2860961e4f6bf3e65ed858c: PR_FAST, both foundation
engines, adapter, historical matrix and CI_COVERAGE passed. No new commits or
pushes were needed. The repository is PUBLIC; visibility was not changed by
the agent. All unselected integrations were skipped as required.

Ref	SHA
POST-#133 BASE MAIN	4bc45a9345a814e75a65f6d6293756f447603e91
PRE-PHASE-B HEAD	56e90cc9c12057c81d1f9312aa51bec11039415f
REBASING RESULT	14eaa1f580848964134b4f6b0f415ee791a20c36
REPAIRED HEAD	c5c427f1b7f9a6d1a2860961e4f6bf3e65ed858c

Listing and evidence boundary

Public metadata remains Plugin Name: WriteLeash, Requires at least: 7.0, Tested up to: 7.1, Requires PHP: 7.4, Requires Plugins: woocommerce, Stable tag: 0.1.0.

Exact conflict copy:

If the stored regular price or another execution precondition no longer matches the approved plan, that item is reported as a conflict instead of being blindly overwritten.

Exact prepared caption:

A later regular-price or execution-state change becomes a conflict instead of a blind overwrite.

Readme, FAQ, claim matrix and deterministic audit guards now distinguish SKU, name/title and category membership as provenance-only. Those edits alone are not automatic execution conflicts. Seven adversarial copy regressions ensure appended broad wording fails even if the bounded sentence remains.

Merchant scope remains up to 100 products per new job, published core simple products, stored regular price, base currency, no sale-price/date configuration, five operations (Set, + fixed, - fixed, + percent, - percent), frozen preview, exact-plan approval, durable progress, bounded Resume and conflict-aware eligible Undo. External effects are not reversed. Multisite is unsupported; real managed/shared hosting is not tested.

Primary immutable WooCommerce evidence: https://downloads.wordpress.org/plugin/woocommerce.11.1.2.zip — SHA-256 9de9350a1cf5671b9960afb3151f40f7980e223217a441bf2ea5921b5fce8e9e. The mutable API response is dated secondary corroboration only; local ignored cache paths are not primary evidence. Support remains WooCommerce 11.1.2 EXACT.

Public versus historical fixture split

1. Public WP 6.8.3 negative: exact allowlist package, no shim or overlay. Normal Core activation must return plugin_wp_incompatible naming WP 7.0, leave WriteLeash inactive/unloaded, and preserve seeded product/postmeta plus WriteLeash durable/option snapshots. This expected refusal is PASS; Woo dependency messaging is not expected before the WP minimum gate.
2. Supported public dependency proof — exact WP 7.1.2: the existing current-core fixture stages public files first. Missing Woo must produce the Core refusal naming WooCommerce. Active Woo 11.1.2 must satisfy the dependency and permit public activation. Active-dependent, dependency-loss fail-closed and released-dependency assertions precede any legacy overlay.
3. HISTORICAL TEST ONLY WP 6.8.3: wordpress/tests/historical-minimum-121.php rewrites only independently copied disposable /tmp/ plugin entrypoint/readme metadata to 6.8.3, with an explicit HISTORICAL TEST ONLY comment. It checks the exact core fixture, rejects modified copies/symlinks/hardlinks and verifies both public source files are untouched. The staged header/readme remain coherent for official Plugin Check. The existing repository-only legacy files/bootstrap overlay follows. Woo 9.9.7 remains only the historical activation dependency, and Redirection remains 5.5.2. Container teardown destroys the disposable lab.

Production wordpress/writeleash/writeleash.php is never shimmed. Neither shim nor legacy bootstrap enters the public manifest or allowlist-only future release ZIP. No authority code is added by the metadata shim. See wordpress/release/PHASE-B-121.md.

#133 CI architecture and #61

Classifier result against exact current main: adapter, foundation, historical. Listing-only changes remain PR_FAST. Historical helper ownership is explicit. No broad workflow triggers were restored. Direct #112 acceptance is unselected; RELEASE_FULL is not run.

The #61 concurrency implementation is unchanged: trusted two-stage barrier, two restricted sessions, real concurrent UPDATE overlap, durable accounting and no stale success. Failed attempts will be retained; a flake rerun must use this exact unchanged head without relaxed assertions.

Validation

Local final-head static validation PASS:

• bash .github/ci/pr-fast.sh: package-preflight, inventory audit, public runtime closure/adversarial audit, source audit, readme validation, claim matrix audit, historical metadata-shim boundary regressions and all 141 tracked PHP files linted.
• bash .github/ci/workflow-lint.sh.
• python3 .github/ci/ownership.py --audit.
• Changed shell fixture syntax checks and new PHP fixture lint.

Local Docker integrations unavailable: bash wordpress/tests/run.sh mysql could not connect to the stopped daemon; sudo needs a password and the rootless fallback lacks newuidmap. Hosted selected-owner integration evidence is required; local static checks are not a substitute.

Official WordPress.org readme validator rerun on the final text 2026-10-02: 0 errors, 0 warnings, three notes: Contributors missing, no Upgrade Notice section, no donate link. Submitted using the official form's base64-encoded UTF-8 readme_contents format.

Retained first hosted run: https://github.com/MrDarkRoot/WriteLeash/actions/runs/37023355769 (attempt 1, head 0943e8dc816a08cc1618761bf24be22d98792cc1). PR_FAST and both foundation engines passed. Adapter hit the unchanged #61 UPDATE-overlap timeout; historical Plugin Check found the staged header/readme mismatch, now corrected without an ignore rule. GitHub blocked CI_COVERAGE on billing/spending limits. All failed artifacts are retained. The user confirmed budget was cleared and authorized one corrected-head selected-owner run.

Final hosted evidence: https://github.com/MrDarkRoot/WriteLeash/actions/runs/37024596744/attempts/2

All jobs checked out exact SHA c5c427f1b7f9a6d1a2860961e4f6bf3e65ed858c on
standard GitHub-hosted ubuntu-24.04 runners:

Check	Job ID	Result
PR_FAST	110901404011	PASS
foundation / mysql	110901511121	PASS
foundation / mariadb	110901511108	PASS
adapter	110901511338	PASS
historical	110901511170	PASS
CI_COVERAGE	110903412814	PASS

Hosted classifier selected only foundation, adapter, historical against
base 4bc45a9345a814e75a65f6d6293756f447603e91. Acceptance, native, engine,
research, plan, journal, jobs, undo, admin and feasibility were unselected and
skipped. CI_COVERAGE's actual marker:

#133 CI_COVERAGE: 3 selected integrations succeeded; no skipped owner PASS

Both foundation engines produced these required markers before/after shimming:

#121 WP 6.8.3 PUBLIC ACTIVATION: EXPECTED CORE REFUSAL (minimum 7.0 first), inactive, zero WriteLeash durable/product mutation: PASS

#121 HISTORICAL TEST ONLY: staged header/readme WP minimum 6.8.3; production remains 7.0; no runtime authority added: PASS

The historical matrix reached the public supported WP 7.1.2 / Woo 11.1.2
fixture on both engines before applying the legacy overlay. Actual markers:

#63 dependency block: Core refuses WriteLeash activation while WooCommerce is missing: PASS

#63 public dependency installed: WooCommerce 11.1.2 active, Core dependency satisfied and public WriteLeash activation succeeds: PASS

#63 dependency active: Core withholds normal dependency deactivation while WriteLeash is active: PASS

#63 dependency lost: Free planning fails closed and zero product mutation: PASS

#63 dependency released: no active dependents once WriteLeash is inactive: PASS

The executed missing-Woo assertion checks the actual Core refusal message names
WooCommerce; these are hosted assertions, not source-only conclusions.

Official Plugin Check 2.1.0 passed the historical classification on both engines.
readme_mismatched_header_requires is absent from the final historical
transcript; no ignore/suppression was added. Existing reviewed historical
findings retain their prior classification (not a claim of zero raw findings).
Historical final marker:

#63 technical release matrix PASS (source-tree preflight only; see RELEASE-MATRIX.md for UNKNOWN/DEFERRED)

#61 attempts and invariant evidence

• Run 37023355769 / attempt 1 / head 0943e8d:
  retained known await_overlap(update) timeout after two restricted sessions
  queued at the trusted row-1 barrier. Its historical Plugin Check metadata
  failure was a separate genuine defect repaired by the starting head.
• Run 37024596744 / attempt 1 / head c5c427f:
  runner allocation was blocked by billing/spending restriction. CommitCap for WordPress: review the cooperative shared-runtime and selected adapter threat model #61 did not
  execute; this is infrastructure failure, not a product or test failure.
• Run 37024596744 / attempt 2 / same exact c5c427f head: first executable
  final-head adapter attempt PASS, including historical matrix's separate
  CommitCap for WordPress: review the cooperative shared-runtime and selected adapter threat model #61 execution. No flake retry or source changes were needed this session.

Actual overlap session IDs: adapter MySQL 218,223, MariaDB 245,242;
historical matrix MySQL 217,212, MariaDB 234,233. Each pair was proven
blocked on the certified Redirection UPDATE while the rows-2-6 trusted barrier
was held. Barrier release followed that proof; both requests COMMITTED with
consumed 6 and L=10, and each engine reported:

two independent certified requests; durable (6,6); zero stale accounting; READY: PASS

All failed attempts remain retained. Barrier, timeout, two-session overlap,
actual concurrent UPDATE, durable accounting and no-stale-success assertions
are unchanged. The account restriction did not recur in attempt 2.

PR_FAST's hosted shim boundary cases passed, including untouched production
entrypoint/readme, independent copies, supported-Core refusal, repeat-shim
refusal and symlink/hardlink rejection. The exact public manifest excludes
historical-minimum-121.php, historical-shim-cases.php, legacy bootstrap and
legacy overlay. Conflict copy, provenance-only clarification and screenshot
caption are unchanged. The 2026-10-02 official readme-validator result is retained
because source did not change: 0 errors, 0 warnings, notes only.

Boundaries

This updates PR #134; no second #121 PR. #122 assets are untouched; #123 work is none. No release ZIP, WordPress.org publication or merge.

Repository visibility was PRIVATE at the start and PUBLIC at the final check.
The agent made no visibility change. The user explicitly directed leaving the
current visibility as-is after this discrepancy was reported.