[MrDarkRoot]

Scope

Issue #322. Conversion copy for the WordPress.org listing only. No runtime, compatibility, or package change.

Invariant / Current Spec Reference

wordpress/writeleash/FREE-GRANT-CONTRACT.md and wordpress/release/CLAIM-MATRIX.md. Public claims stay inside the seatbelt sentence, the exact conflict sentences, and the v0.3.0 pair rule. Stable tag and WRITELEASH_VERSION stay 0.3.0.

Relevant Canonical CC-* Tests (docs/test-plan.md)

None. This is listing copy. No legacy experiment ID is treated as acceptance.

What Changed

• wordpress/writeleash/readme.txt leads with protecting prices and stock, then the leash. The first heading is "Put a restricted account on a leash". "See the price before it goes live" is the second heading. Requirements, the exact seatbelt paragraph, and the six screenshot captions are unchanged.
• Plugin header Description is the same one-line short description. Version constants stay 0.3.0.
• docs/marketing/322-listing-conversion.md records before/after, the claim table, SEO notes with no volumes, screenshot caption recommendations, and the founder SVN gate.

Short description (126 characters): Protect WooCommerce prices and stock from bad overwrites. Keep newer edits, undo eligible prices, and leash restricted agents.

Security Impact

None. Copy only. The listing still says the restricted path is not a firewall, not a sandbox, and not a universal fail-closed guarantee when the grant store is unavailable.

PostgreSQL Semantics Considered

None. WordPress plugin listing.

Adversarial / Bypass Testing

Not applicable. No enforcement code changed.

Limitations / Unknowns

• Git readme.txt does not change the live directory. Founder must commit it to WordPress.org SVN trunk with Stable tag left at 0.3.0, or ship a later release. This PR does not do that commit and does not retag 0.3.0.
• Screenshot captions were not rewritten. Asset audit requires the current six lines. A denial screenshot is not live and needs founder SVN approval.
• Directory check on 2026-11-10: v0.3.0, active installs 0, ratings 0. API tested reported 7.1.4. Readme Tested up to stays 7.1.
• A bulk price change stays in Preview until you approve it. A restricted account can change price or stock only inside a grant you already issued, and only on the monitored paths. A grant-mode job does not need a fresh human approval of that job. Writes outside WriteLeash are not stopped. CLAIM-MATRIX row 21 was not changed.

Validators on b524248edc071d967c76aebfe01067da9e7d38c6:

php wordpress/tests/release/readme-validate.php wordpress/writeleash
#63/#121 readme preflight: title, 126-char description, 5 tags, Stable tag 0.3.0, directory/header requirements coherent, GPLv2-or-later PASS

php wordpress/tests/release/claim-matrix-audit.php .
#121 claim matrix audit: 16 required topics, forbidden-claim guard, readme/matrix wording and packaging boundary PASS

Out-of-Scope Work Explicitly Not Included

• I did not silently expand the support envelope.
• I updated the current spec, test plan, threat model, or decisions if behavior changed.
• Security-sensitive behavior has adversarial test coverage.
• No secrets or credentials are included.

Behavior did not change, so the spec, test plan, and threat model were left as they are. The second and third boxes are true because there was nothing new to add.

[MrDarkRoot]

First screen rewritten so it does not read as a bulk editor.

Short description (126 characters): Protect WooCommerce prices and stock from bad overwrites. Keep newer edits, undo eligible prices, and leash restricted agents.

First two headings: Put a restricted account on a leash. See the price before it goes live.

Validators on b524248edc071d967c76aebfe01067da9e7d38c6: PASS.

• php wordpress/tests/release/readme-validate.php wordpress/writeleash — #63/#121 readme preflight: title, 126-char description, 5 tags, Stable tag 0.3.0, directory/header requirements coherent, GPLv2-or-later PASS
• php wordpress/tests/release/claim-matrix-audit.php . — #121 claim matrix audit: 16 required topics, forbidden-claim guard, readme/matrix wording and packaging boundary PASS

Stable tag and version stay 0.3.0. The seatbelt paragraph is unchanged. Founder SVN gate is unchanged: this PR does not publish the directory and does not retag 0.3.0. Issue #322 stays open.

[MrDarkRoot]

QA verdict: FAIL at b524248edc071d967c76aebfe01067da9e7d38c6.

Mergeable against main, not behind. PR_FAST and CI_COVERAGE succeeded. Acceptance skipped. This does not publish SVN, so issue #322 stays open until the directory text actually changes.

Enforcement is unchanged. wordpress/writeleash/writeleash.php changes only the plugin header Description. Version and WRITELEASH_VERSION stay 0.3.0. No guard, mutator, or grant logic is edited. The exact seatbelt sentence is still in wordpress/writeleash/readme.txt (not a firewall, not universal agent-safe, direct SQL not covered).

The new opening is not allowed by the contract. readme.txt says "With WriteLeash, the catalog does not change until a person approves." A grant job uses approval_mode: grant and does not wait for a person, and CSV, other plugins, direct SQL, and an unrestricted administrator can still change the catalog. docs/marketing/322-listing-conversion.md says that sentence is only for a person-run WriteLeash price change, but the public paragraph does not say so. wordpress/release/CLAIM-MATRIX.md row 21 is not updated; its allowed short description is still the 121-character overwrite sentence, not this 126-character line.

Live directory short description remains "See WooCommerce price changes before they go live." This pull request does not change that.

[MrDarkRoot]

QA correction on 932e8bd0d37f1a8578a0bdc5d9b2cc66ef193e25.

The opening no longer says the catalog waits for a person. A grant-mode job can change a price without a fresh human approval of that job, and writes outside WriteLeash are not stopped.

New opening: A wrong percentage, a CSV overwrite, or an assistant account editing a product is the expensive mistake. A bulk price change stays in Preview until you approve it. A restricted account can change price or stock only inside a grant you already issued, and only on the monitored paths.

Short description is unchanged (126 characters) and still starts with "Protect WooCommerce prices and stock from bad overwrites." The leash section stays first. The seatbelt paragraph, Stable tag 0.3.0, and Requirements facts are unchanged. CLAIM-MATRIX row 21 was not edited.

Validators: PASS.

• php wordpress/tests/release/readme-validate.php wordpress/writeleash — #63/#121 readme preflight: title, 126-char description, 5 tags, Stable tag 0.3.0, directory/header requirements coherent, GPLv2-or-later PASS
• php wordpress/tests/release/claim-matrix-audit.php . — #121 claim matrix audit: 16 required topics, forbidden-claim guard, readme/matrix wording and packaging boundary PASS

Not merged. Issue #322 stays open.

[MrDarkRoot]

First screen now leads with costly price and stock mistakes, then restricted AI agents and automation. Local readme-validate.php and claim-matrix-audit.php passed on 17ae7dc. Stable tag and version stay 0.3.0.

SVN is not committed. The handbook says a Stable tag of 0.3.0 makes the directory read tags/0.3.0/readme.txt, so a trunk-only readme edit would not change the page. The copy packet is docs/marketing/322-svn-listing-update.md. It needs a separate founder approval before any svn commit, and that commit would be the two readme files only.