Release 1.0.0-beta.28

Author: iOSDevSK

.claude-plugin/marketplace.json

@@ -14,7 +14,7 @@
       "source": "./",
       "displayName": "html2wp — HTML to WordPress",
       "description": "BETA. Convert a static HTML site into a standalone WordPress block theme, verified against the original at three viewport widths — and reviewed by you before handover. The conversion runs through a verified Astro 5 build, so the Astro project is a real output too — compared pixel by pixel against the source before anything WordPress-shaped is generated.",
-      "version": "1.0.0-beta.26",
+      "version": "1.0.0-beta.28",
       "author": {
         "name": "BELNEM s.r.o.",
         "email": "hello@html2wp.dev",

.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "html2wp",
   "displayName": "html2wp — HTML to WordPress",
   "description": "BETA. Convert a static HTML site — or anything that builds to one (Lovable, Bolt, v0, Next export) — into a standalone WordPress block theme: verified pixel by pixel, pages, blog, forms, menus, SEO and redirects, with no plugin required and verification gates at every stage. Every conversion ends in your own page-by-page review; the gates catch most fidelity drift, not all of it.",
-  "version": "1.0.0-beta.26",
+  "version": "1.0.0-beta.28",
   "author": {
     "name": "BELNEM s.r.o.",
     "email": "hello@html2wp.dev",

.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "html2wp",
-  "version": "1.0.0-beta.26",
+  "version": "1.0.0-beta.28",
   "description": "Convert static HTML or buildable web projects into verified, editable WordPress block themes.",
   "author": {
     "name": "BELNEM s.r.o.",

.github/workflows/gate.yml

@@ -139,9 +139,29 @@ jobs:
           # files mention make-theme.mjs in a comment explaining what they
           # share with it, so a name-based grep reports hits on a clean tree
           # and becomes a check people learn to ignore.
+          #
+          # The Gutenberg compiler is the second generator. Its client half
+          # (prepare-block-plan.mjs, gutenberg-*.py) ships, so these are
+          # exact names, never a *gutenberg* pattern.
+          #
+          # The generators' own libraries follow. The client shares other
+          # libraries with them (selector.mjs, nav-stamp.mjs), so these are
+          # named one by one too. The list is tools/sync-lib.sh's moat_scan.
           found=$(find . -path ./.git -prune -o \
             \( -name 'make-theme.mjs' -o -name 'dist-to-bundle.mjs' \
                -o -name 'build-posts.mjs' -o -name 'build-products.mjs' \
+               -o -name 'make-gutenberg-theme.mjs' -o -name 'gutenberg-compiler.mjs' \
+               -o -name 'gutenberg-blocks.mjs' -o -name 'gutenberg-blocks-extra.mjs' \
+               -o -name 'gutenberg-editor-css.mjs' \
+               -o -name 'asset-refs.mjs' -o -name 'card-category.mjs' -o -name 'dates.mjs' \
+               -o -name 'price-region.mjs' -o -name 'site-chrome.mjs' -o -name 'trailing-roles.mjs' \
+               -o -name 'product-read.mjs' -o -name 'class-transplant.mjs' -o -name 'cart-parts.mjs' -o -name 'front-footer.mjs' \
+               -o -name 'buy-style.mjs' -o -name 'card-wrappers.mjs' -o -name 'cart-badge.mjs' \
+               -o -name 'cart-dress.mjs' -o -name 'commerce-chrome.mjs' -o -name 'commerce-frame.mjs' \
+               -o -name 'empty-state.mjs' -o -name 'listing-order.mjs' -o -name 'menu-categories.mjs' \
+               -o -name 'not-found.mjs' -o -name 'pager.mjs' -o -name 'related-rule.mjs' \
+               -o -name 'reveal-css.mjs' -o -name 'shop-design.mjs' -o -name 'source-index.mjs' \
+               -o -name 'lead-cards.mjs' -o -name 'article-head.mjs' -o -name 'cascade-slot.mjs' -o -name 'utility-body.mjs' -o -name 'owned-selectors.mjs' -o -name 'part-band.mjs' -o -name 'selector-tree.mjs' \
                -o -name 'visual-edit.zip' -o -name 'THREAT-MODEL.md' \
                -o -name 'gotcha-classification.md' -o -type d -name templates \) -print)
           if [ -n "$found" ]; then
@@ -150,3 +170,15 @@ jobs:
             exit 1
           fi
           echo "clean"
+
+      - name: no build debris
+        run: |
+          # Bytecode compiled for one Python is useless to every other and
+          # unreadable to anyone auditing what the plugin runs.
+          found=$(find . -path ./.git -prune -o \( -name __pycache__ -o -name '*.pyc' -o -name .DS_Store \) -print)
+          if [ -n "$found" ]; then
+            echo "::error::build debris is committed:"
+            echo "$found"
+            exit 1
+          fi
+          echo "clean"

.gitignore

@@ -2,3 +2,5 @@ node_modules/
 .DS_Store
 ._*
 *.log
+__pycache__/
+*.pyc

PRIVACY.md

@@ -60,7 +60,8 @@ days**.
 
 One row per conversion: how many pages, how many chrome variants, whether it
 had a blog or a shop, whether it was a re-run, which stage refused if one did,
-and the generator's own warnings about itself. The warnings are redacted —
+how long each of the service's own scripts ran, and the generator's own
+warnings about itself. The warnings are redacted —
 page filenames and URLs are replaced before the row is written. Kept **365
 days**. No content, no addresses, no identifiers for the site.
 

README.md

@@ -10,6 +10,11 @@ export, hand-written pages), becomes a standalone WordPress block theme. Pages,
 and redirects work with **no plugin required**. The markup stays the design's
 own — no page builder, no rebuild.
 
+Two outputs, chosen when a conversion starts: the **HTML theme** (the
+default: the source markup kept 1:1, click-to-edit with Visual Edit Lite) or a
+**native Gutenberg block theme** whose pages, header and footer are core
+blocks, edited in the block editor. Visual Edit Lite is linked for both.
+
 > **Beta.** This converts real sites and is used on real work, but the
 > gates catch most fidelity drift, not all of it. The last stage of every
 > conversion is your own page-by-page review, and the skill walks you
@@ -127,12 +132,18 @@ with `codex plugin remove html2wp@<that-name>` so it cannot shadow this one.
 /plugin install html2wp@html2wp
 ```
 
-Installing the plugin also registers one hook, `hooks/stage-progress.sh`, which
-runs after every Bash call. It reads the command line the tool just ran, and if
-that line invoked one of the conversion's stage scripts it reminds the model to
-report the stage boundary. It runs nothing, writes nothing, and sends nothing;
-on every other call it prints `{}` and exits. The source is short and is the
-whole of what it does.
+Installing the plugin also registers one hook, `hooks/stage-progress.sh` (the
+work is in `hooks/stage-progress.py`), which runs after every Bash call,
+successful or failed. It reads the command line the tool just ran, and if that
+line invoked one of the conversion's stage scripts it reminds the model to
+report the stage boundary and appends one timing row to
+`.h2wp-timing.jsonl` in that conversion's workspace. Under
+`~/.cache/html2wp/.sessions/` it keeps a small per-session pointer to the
+workspace, plus timing rows held until a workspace is known; both are swept
+after 30 days. It runs nothing but its own Python file and sends nothing over
+the network; on
+every other call it prints `{}` and exits. The source is the whole of what it
+does.
 
 ### Keeping Claude Code current
 
@@ -308,9 +319,9 @@ and the skill will not call a conversion finished until it is done.
 - **a conversion report** — pages converted, menus wired, every finding from
   your review, every warning from every stage including the ones judged
   acceptable, and anything left for you to do;
-- **`visual-edit.zip`**, if the conversion was licensed. A free conversion
-  ships the theme alone and it is fully usable — the editor is an extra, not
-  a missing piece.
+- **the editor** is Visual Edit Lite, not in the bundle — the delivery is the
+  theme alone and fully usable, with a link to the Lite release for anyone who
+  wants click-to-edit authoring. (Visual Edit Pro is a separate purchase.)
 
 ## Requirements
 
@@ -353,26 +364,38 @@ convert a real site and judge the result properly.
 
 The free tier is for **evaluation, personal sites and other non-commercial
 work**. Converting a site for a client, or for a business you run, is
-commercial use and needs a licence key — see [LICENSE](LICENSE).
+commercial use and needs a Pro key — see [LICENSE](LICENSE).
 
-| | Free | With a licence key |
+| | Free | Pro |
 |---|---|---|
+| Price | €0 | €49 / month · €490 / year |
 | Commercial use, client work | no | yes |
-| Pages per conversion | 5 | 20 (Theme Unlock, Pro) · 10 (yearly Visual Edit Pro) · 100 (Agency) |
-| Conversions | 3 per IP address | 1 (Theme Unlock) · 5 (Pro) · 30 (Agency) · 2 (yearly Visual Edit Pro) — a fixed pool per licence, not a monthly refill |
-| Parallel conversions | — | Agency: up to 3 side by side |
-| Re-runs | 5 in total | unlimited while the licence is live |
+| Conversions | 3 per IP address | unlimited |
+| Pages per conversion | 5 | unlimited |
+| Re-runs | 5 in total | unlimited |
 | Blog → WordPress Posts | yes | yes |
-| Shop → WooCommerce | no | yes — except Visual Edit Pro licences |
-| Visual Edit Pro plugin | — | delivered with every licensed conversion |
+| Shop → WooCommerce | no | yes |
+| Editor | Visual Edit Lite | Visual Edit Lite |
 | The theme itself | identical | identical |
 
-Keys issued before the tiers existed keep the allowance they were issued
-with — the `credit` line at job open states yours either way.
+**Pro is a subscription.** Monthly or yearly, it converts without limit while
+it is live — cancel any time and the key keeps working to the end of the
+period you paid for. There is no per-page or per-conversion cap and nothing to
+run out of.
+
+**Visual Edit Pro (€59 / year) is a separate product** — the paid editor, and
+only the editor. It is **not** a conversion key and includes no conversions;
+you buy it for a site and activate it there. See *Editing the converted site*
+below.
 
 **The licence never buys fidelity.** The theme a free conversion produces is
-the same theme a licensed one produces — it buys page headroom, re-runs,
-WooCommerce and the editor.
+the same theme a Pro one produces — Pro buys page headroom, unlimited
+conversions and re-runs, and the shop stage.
+
+- **Beta:** 30% off the first payment (first month or first year); full price
+  after that.
+- Sold through **Paddle** (invoice with VAT). Refund within 14 days if the key
+  was never used.
 
 Licences: **[html2wp.dev/licenses](https://html2wp.dev/licenses)**
 
@@ -397,12 +420,14 @@ For point-and-click editing there is **Visual Edit**, a WordPress plugin that
 lets you (or your client) edit text, images, links, forms and menus by
 clicking them on the page, while keeping the markup 1:1 with the design.
 
-- **Free edition** — click-to-edit content editing, forms, menus, SEO fields.
+- **Lite** — click-to-edit content editing, forms, menus, SEO fields. Free,
+  public, and what every conversion links you to (its GitHub release).
 - **Pro** — adds AI chat editing (with your own API key), theme export,
   Turnstile spam protection, and a 300-step edit history instead of 10.
 
-Pro is delivered with every licensed conversion, and activating its Pro
-features on a site needs a Visual Edit Pro licence.
+No editor is bundled with a conversion — free or Pro, you are pointed at the
+Lite release to install. Visual Edit **Pro** (€59/year) is bought separately
+and activated on the site; it is the only thing that unlocks the Pro features.
 
 Details: **[html2wp.dev/visualedit](https://html2wp.dev/visualedit)**
 

VERSION

@@ -1 +1 @@
-1.0.0-beta.26
+1.0.0-beta.28

hooks/hooks.json

@@ -10,6 +10,17 @@
           }
         ]
       }
+    ],
+    "PostToolUseFailure": [
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/stage-progress.sh"
+          }
+        ]
+      }
     ]
   }
 }