Repository navigation
docs(marketing,#323): add search-intent price-overwrite guides - #331
Conversation
Five merchant articles, a keyword evidence table, a claims audit, a measurement note, and a publication manifest. Publication stays blocked: this repository has no approved content destination. The guides describe WordPress.org WriteLeash 0.2.2 as it is listed. Restricted-agent and stock-on-grant behavior from #312 stays labeled unpublished. No plugin runtime, readme, or SVN change.
Refresh the five articles for the shipped 0.3.0 listing, teach the restore first, and check in the static site plus its generator. GitHub Pages serves only that site from docs/323-seo-pages. Search volume stays unmeasured.
|
QA verdict: FAIL at Mergeable against The five articles now name directory WriteLeash 0.3.0 and keep the negations (not a firewall, not a sandbox, not universal agent-safe, direct SQL / hostile plugins / unmonitored writes uncovered). I fetched HTTP 200 for Still false in this head: Local article/runtime tests: NOT_TESTED. |
The evidence note still called the directory 0.2.2 and said there was no project site. The listing opened 10 November 2026 is 0.3.0, and the guides are already on GitHub Pages. Article teaching is unchanged.
|
QA fix on
Corrected sentences:
|
Summary
Updates the five merchant guides for shipped WriteLeash 0.3.0 and publishes them as a static site. Search volume is not measured. No plugin runtime, readme, demo, or launch-campaign files change.
The guides teach the WooCommerce repair first. Each page has one visible call to action: the WordPress.org listing and the GitHub repository. Preview, conflict preservation, and eligible price Undo are described as shipped. Stock Undo is not supported. Opt-in grants stay off until an operator issues one. The pages say this is not a firewall, not a sandbox, and not a universal agent-safe guarantee.
Live site
GitHub Pages is a legacy build of branch
docs/323-seo-pagesat/(commit3445680abd944e5260e5d3ade7cd5bceb29147cf). That branch contains only the generated HTML. It does not publish the repositorydocs/product documentation. Do not mergedocs/323-seo-pagesintomain.Checked HTTP 200 on 10 November 2026:
No workflow file was added. An unmapped
.github/workflows/file failsownership.py, and that policy file is outside this change.Test plan
docs/marketing/323-seo-content/.python3 docs/marketing/323-seo-content/build_site.pychecks unique titles, one CTA, canonicals, and relative links.python3 -m http.serverreturned HTTP 200 for every page, the sitemap, robots, and CSS. No browser was available.