html2wp 1.0.0-gamma.11

html2wp 1.0.0-gamma.11

This release preserves each comparison source and its provenance across viewports, so a missing reference is reported rather than silently compared against a different page. It also restores a cleaned WordPress preview through the bounded repair path.

Astro delivery can now recover an incomplete conversion transactionally. It retries supported missing output within a fixed budget, records the repair outcome, and retains an existing Astro ZIP when the recovery does not replace it. The agent instructions use the detected source root throughout the recovery path.

Validation on the release source included Astro recovery 9, prerender template 12, writer 14, browser readiness, and Full delivery 19 tests. Integration exercised the real helper output through the app's completion path, including a retained ZIP and a ready deliverable. The published plugin is picked up by the desktop app at a future startup; an already running conversion is unchanged.

html2wp 1.0.0-gamma.10

html2wp 1.0.0-gamma.10

This plugin release lets the Astro input stage capture a supported Lovable TanStack site whose Nitro Cloudflare adapter conflicts with TanStack prerendering. The adapter is scoped to the verified @lovable.dev/vite-tanstack-config 2.5.3 configuration; unrecognized variants stop with an explicit unsupported adapter error. It changes only the isolated build copy, preserving the uploaded source and lockfile.

Browser capture now waits for document and non-media requests within one bounded 30-second budget, while allowing streaming media to continue loading. Navigation errors and pending script, fetch, style, image, and font requests still fail the capture when appropriate. The runbook also directs the agent to use the detected project root for nested imports.

Validation included five adapter tests, browser readiness cases for media, pending fetches, HTTP errors, timeouts, concurrency and the shared deadline, seven project detection tests, and two existing prerender route tests. An isolated Aero Scent run captured six routes, built Astro 5.18.2 and produced an Astro ZIP. Four public pages had usable content and ready hero video; the admin and auth routes showed the same missing-Supabase error as the source. This release does not supply backend credentials or certify full visual and interaction parity.

The desktop app 1.0.6 picks up the new plugin from the Codex publication at a future startup. Existing active conversions and delivered artifacts are not changed by publishing this release.

html2wp 1.0.0-gamma.9

html2wp 1.0.0-gamma.9

Fixes import of Astro ZIPs exported by html2wp when every page is self-contained under public/. ZIP archives omit the empty src/fragments/bodies/ directory; the project detector now recognizes these exports using public/index.html alongside the existing Astro dependency, config, built dist/index.html, and html2wp report checks.

An exported Astro project is recognized as html2wp-astro and can continue through the Astro import path without regenerating its source project. Ordinary Astro projects without the html2wp report retain their previous classification.

Validation: 7 detection tests passed, including a real export → ZIP extraction → detection → preparation round trip; a 12-page Caribbean export also passed detection and preparation.

html2wp 1.0.0-gamma.8

html2wp 1.0.0-gamma.8

This plugin release improves the accuracy of the Astro stage before WordPress theme generation.

• Recover a missing source image from the Live app URL declared in the project root README when no explicit asset origin was supplied. Existing public URL, redirect, content type and size checks still apply.
• Preserve transparency in responsive PNG to WebP variants, including grayscale alpha and palette transparency.
• Detect an unambiguous nonsemantic header around navigation and carry its measured selector into Flash comparison. Reject selectors that also collide with inert text in the source HTML.
• Add a preservation checklist for Astro 5 conversion and regression coverage for source assets, transparency and header selection.

Validation: source asset regressions 29/29, PNG alpha modes across both optimization stages, source chrome unit and integration checks, Flash manifest 7/7, and Claude plugin validation passed. An isolated Caribbean Astro rebuild passed Gate A at 36/36 and Gate A2 at 48/48 against the saved prerendered input with the recovered hero image. This was not a new end to end conversion or a live WordPress lifecycle test.

The desktop app 1.0.6 fetches the latest plugin from the Codex publication on its next startup. Existing delivered themes and generated image variants are not changed by installing this release.

html2wp 1.0.0-gamma.7

html2wp 1.0.0-gamma.7

The converter now recovers missing source images before HTML, Flash, Full and Astro capture when a verifiable origin or matching local asset is available. Unresolved images remain explicit in the report. Concurrent conversions use a canonical workspace and runtime identity so one project's preview cleanup cannot remove another project's WordPress preview.

Preview setup activates Visual Edit Lite when installed and inactive, while preserving an active Visual Edit Pro. Single-page visual comparison refreshes only the chosen page and keeps the previous index if capture fails. Reports record available model selections, effort and elapsed time.

The matching desktop app is 1.0.6. It opens previews in the default browser, exposes the original project ZIP in Exports and diagnostic logs in the project menu, supports targeted comparison refresh, and adds the experimental Gutenberg toggle and a six-conversion maximum.

Validation: publication sync checks, Claude plugin validation, preview editor (8), preview ownership (23), image recovery (23), run metadata (3), report writer (14), and visual comparison (6) tests. Desktop targeted Rust tests, TypeScript, production frontend build and ARM64 DMG integrity/signature checks passed. Live WordPress activation and a new full end-to-end conversion were not repeated for this release.

html2wp 1.0.0-gamma.6

html2wp 1.0.0-gamma.6

Full conversion can repair failed stages within a bounded retry budget and deliver a usable theme ZIP with unresolved checks reported honestly. The owner can choose a model and continue repair without discarding the previous ZIP.

Edits to a completed HTML theme can be recorded as persistent patches with a reason, diff and content hashes. A later server build replays compatible patches; a conflict preserves the current theme and ZIP for explicit resolution. Packaging rejects a patch that is still being edited or has an unresolved conflict.

The desktop app 1.0.5 exposes the repair action and preserves delivered themes and repair context when a conversion pauses. It fetches the current plugin release on startup.

Validation on the local release commits: 17 theme patch tests, 17 Full tests, 9 Flash tests, 37 desktop Vitest tests, TypeScript type check, Rust cargo check --locked, publication sync checks and Claude plugin validation. The complete live Homeware conversion and live WordPress import have not been repeated for this release.

html2wp 1.0.0-gamma.5

html2wp 1.0.0-gamma.5: a stop gets 3 automatic repairs, and a site nested in a folder converts.

Self-repair before a stop

• A failure that would stop the run gets up to 3 attempts in its stage (9 per run). The named fixes come first, then the AI's own diagnosed fix.
• The AI's own fix also covers a failure that no script named. It never changes a gate, a check or its thresholds, and the report says what it changed.
• The run stops only after its 3 attempts. The app then offers Repair and continue, and you can choose a stronger model first. Each Repair and continue again allows 3 attempts.

Fixes from real runs

• A static site inside a folder (for example Amanda Rose/index.html beside a README) is taken from that folder. Before, the build landed one level down and stage 2 stopped.
• Stage 2 ends with a plain verdict: red gate A or A2 is recorded and the run goes on. Only the steps the upload needs can stop stage 2.

Server: api.html2wp.dev 0.2.5. Mac app: 1.0.4.

html2wp 1.0.0-gamma.4

html2wp 1.0.0-gamma.4: Flash repairs itself within a bounded budget, stops can be repaired, the prerender is much faster, and Astro gets live changes.

Self-repair (Flash)

• A failing step names its failure, and Flash tries the matching fixes from a fixed list: at most 4 attempts per run and 2 per stage, and never the same fix twice.
• A fix that doesn't work is given up, the stage is recorded red, and the run continues. It never loops.
• The report and PDF gain Repairs (stage, attempt, fix, outcome) and What Flash could not fix.

Fixes from real runs

• Blog posts no longer stop Flash at packaging. The post layout is derived from the site's own article page when the service produces only its generic one.
• Stage 3.5 is one command: the post layout, the shop fixes, then the theme ZIP.
• The run's own verdict step is no longer blocked by a draft result.
• A stopped run is protected like a delivered one: nothing restarts it, and only "Start over from the original" begins a new run.
• A stopped run can be repaired: your next message lets Flash try up to 2 more fixes on the stopped stage, then continue from there.

Shops

• The Flash shop check now shops like a customer: the header cart count after adding, the count following + / − / remove, and two sizes of one product as two cart lines.
• When the check finds a problem, the matching fix is added automatically: the count in the header, count sync with the WooCommerce block cart, and the chosen option saved on the cart line.

Faster prerender for apps

• Pages of one route pattern are recorded once, and the rest are captured statically with the same interactions replayed where the controls match. This covers product, category and blog pages in React Router and TanStack Start / Lovable.
• The header, footer and navigation are recorded once.
• Pages are captured in parallel, and progress shows "N of M pages".

Astro 5 project only

• After delivery, a chat change edits the Astro project and runs only the Astro build.
• Make release packages the next revision, and Compare shows the original next to the built site.

Server: api.html2wp.dev 0.2.5. Mac app: 1.0.3.

html2wp 1.0.0-gamma.3

html2wp 1.0.0-gamma.3: "Make release" wording.

• After delivery, the ZIP is yours to take with the html2wp Desktop app's Make release. It packages the live theme as the next revision and opens Exports.
• The AI never packages the theme in a change turn, even when you ask it for the ZIP. It points you to Make release instead.
• Wording only. Behaviour is unchanged from 1.0.0-gamma.2. Server: api.html2wp.dev 0.2.5. Mac app: 1.0.2.

html2wp 1.0.0-gamma.2

html2wp 1.0.0-gamma.2: changes after delivery are made in the live theme, never by a new build.

Once a conversion is delivered, every change you ask for is made in the installed theme and shows in the preview within seconds. It never starts the conversion again.

• Changes after delivery (H2WP_MODE=change)
  • The AI edits only the installed theme's files: templates, parts, the site CSS, assets and page sources. It never edits the site's source, and it never runs prerender, the Astro build or the service conversion.
  • apply-change.py replaces the theme in the running preview with WordPress's own theme update, then refreshes the pages that changed. A page you already edited yourself in the preview keeps your text; the AI tells you when that blocks a change.
  • The AI checks the touched pages at 1440 and 390 px before it answers. Each change is logged in workspace/changes.json, with a count of the changes since the last ZIP.
  • Anything the theme files cannot change, the AI says plainly.
• Guard: once a project is delivered, starting a conversion stage, and rewriting the delivered result, are both refused. A new conversion starts only from the app's "Start over from the original" (progress.sh mode <flash|full> --new), which replaces the theme and drops the changes made after delivery.
• Get ZIP (package-theme.py, no AI): packages the current live theme as the next revision (<slug>-<version>-r<N>.zip). If nothing changed since the last ZIP, you get the existing ZIP back. A ZIP packaged after changes is marked as not checked again.

Everything in 1.0.0-gamma.1 is unchanged. Server: api.html2wp.dev 0.2.5.