@bettercms-ai/convert 0.9.0 → 0.11.0

package/CHANGELOG.md

@@ -1,5 +1,39 @@
 # @bettercms-ai/convert
 
+## 0.11.0
+
+### Minor Changes
+
+- `--componentize` extracts FLAT field families (`wrap-h2-latest`, whose key is `h2_latest`), which were
+  refused as `PROP_MAP_INCONSISTENT`. The section reads its copy through the new helper `bcmsSectionPaths`
+  and addresses instance copy by the override key the plan names (`overrideKey`, including repeater rows).
+- An Astro section carries the page's scoped plain-CSS `<style>` blocks, so it renders styled on its own —
+  for every newly extracted section, dotted families included (Astro scopes styles per file, so page CSS
+  never reached a moved section). `is:global`, `define:vars`, `lang="…"` and `@import`/`@use` blocks stay on
+  the page.
+- The componentize receipt lists `componentFiles` (`{ slug, path, export }`): submit it with the MCP tool
+  `submit_componentize_receipt` so every extracted section is recorded as its component's source and the
+  dashboard's Output can build, validate and render it.
+- Helper v7. A v6 helper is recognised and upgraded in place.
+
+## 0.10.0
+
+### Minor Changes
+
+- ac3a9ff: Declare the shapes the derive lane mints for every visible body tag: a heading whose styled run is
+  part of its value (`richtext inline`, bound whole rather than wrapped around its text node), a
+  standalone `span`/`time`/`small`/`label`/`option` leaf, a `<pre>` code block (the `<pre>` is the
+  field, not the `<code>` inside it), and a group row whose optional leaf is empty (covered by its
+  own route's templated declaration instead of reported `NO_ORIGINAL`). A heading split by a `<br />`
+  is found again: its value carries no space, because no text node holds one.
+
+  An inline heading the lane cannot own whole — its element holds a component, a `<slot>` or an
+  expression, which no stored string can re-emit — is refused by name (`SUBTREE_NOT_HTML`) instead of
+  being bound over the top of it.
+
+  New `--xray <dist-dir>` mode: how much of each built page's visible copy no binding owns, and the
+  biggest buckets of it, so the loop is build -> measure -> fix -> build with no deploy in it.
+
 ## 0.9.0
 
 ### Minor Changes

package/README.md

@@ -38,6 +38,27 @@ Exit codes: `0` done — the pending list is printed, not hidden; `1` something
 | `--strict` | exit 2 when any path is pending. |
 | `--overwrite-helper` | replace a `bcms-content` helper whose bytes this tool did not write — including one of ours that has since been edited. |
 | `--verbose` | stack traces, and every file considered. |
+| `--xray <dist-dir>` | a mode of its own: measure a LOCAL build instead of converting one. |
+
+### `--xray` — what is not editable
+
+A receipt says what the codemod bound. It cannot say what it was never asked to bind, so a site can
+report full coverage while a quarter of its visible text is unreachable from the editor. `--xray`
+walks a build and counts that, per page, with no deploy in the loop:
+
+```bash
+npm run build && npx @bettercms-ai/convert --xray dist
+```
+
+```
+docs/index.html  visible=3512 unaddressable=701 (20.0%)
+     379ch    4n  code @ main  e.g. "const site = { direction: 'rtl', language: 'ar'," | "npm install"
+     188ch   12n  span @ main>ul  e.g. "Performance" | "100"
+```
+
+Glyphs, ordinals, the platform badge and skip links are excluded from BOTH halves of the ratio —
+counting them would put a floor under every route that no amount of binding could lift. `--strict`
+exits 2 while any page is above 2 %. It takes no `--brief`: it measures, it does not convert.
 
 ## What it actually does
 
@@ -152,6 +173,8 @@ rendering that binding — `<img>`, `<source>`, `<video poster>`, or `<Image>`/`
 different paths share a sentence and position cannot separate them (both are skipped; the rest of
 the file still converts), `SUBSTRING_ONLY`, `IN_SCRIPT_OR_COMMENT`, `KIND_MISMATCH`,
 `REPEATER_AMBIGUOUS` (one array declaration, two loops over it — the row has two homes),
+`SUBTREE_NOT_HTML` (an INLINE richtext heading whose element holds a component, a `<slot>` or an
+expression: its whole subtree is the value and no stored string can re-emit that),
 `IMAGE_ASSET_UNRESOLVED`, `PARSE_ERROR`. `NOT_IN_SOURCE` is reserved for what it says: a path
 `locate` found in a file is `IN_EXPRESSION` when it sits in the module region or an expression
 node, and where `NOT_IN_SOURCE` is still the answer the row names the file it was found in. And