@ammduncan/easel 0.2.19 → 0.2.21

package/CHANGELOG.md

@@ -2,6 +2,17 @@
 
 All notable changes to easel. This project adheres to [Semantic Versioning](https://semver.org/).
 
+## 0.2.21 — 2026-05-23
+
+### Fixed
+- **Stray backticks in a CSS comment blanked every card.** The 0.2.20 prose-cap comment contained `` `.wrap` `` / `` `.full-bleed` `` in backticks. That comment lives inside `buildDefaultWrapper`'s JS template literal, so the backticks prematurely closed the template string → the function threw `… .wrap is not a function` on every render → hydrate failed and no cards showed (the push count still read 5). Removed the backticks from the comment.
+- **Build now syntax-checks the client JS.** `viewer.js` / `index.js` are plain browser JS copied as-is (never run through `tsc`), so this class of bug shipped undetected. `scripts/copy-client.mjs` now runs `node --check` on each after copying and fails the build on a syntax error — this exact bug would have been caught at build time.
+
+## 0.2.20 — 2026-05-23
+
+### Fixed
+- **Prose reading-width cap silently missed when content was wrapped in `.wrap`.** The 880px cap only targeted direct body children (`body > p`, `body > h1`, …). But the skill recommends wrapping push content in `<div class="wrap">`, so prose became `body > .wrap > p` and the selector never matched — prose stretched the full card width (defeating the whole point of the reading column, and making the 0.2.19 full-bleed demo look like "everything's wide" rather than "prose narrow, mockup wide"). Extended the cap to also match one level deep through `.wrap`. `.full-bleed` was unaffected (it escapes via viewport units regardless of nesting).
+
 ## 0.2.19 — 2026-05-23
 
 ### Added

package/dist/client/viewer.js

@@ -693,9 +693,16 @@ body {
   body { max-width: 1600px; }
 }
 /* Constrain prose to a comfortable reading length, but let visual blocks
-   (cards, grids, tables, mockups) use the full card width. */
+   (cards, grids, tables, mockups) use the full card width. Match prose both
+   as direct body children AND one level deep through a .wrap container —
+   the skill recommends wrapping content in div.wrap, and without the
+   .wrap branch the cap silently misses and prose stretches full width.
+   .full-bleed still escapes via viewport units regardless of nesting. */
 body > p, body > .deck, body > .lede, body > ul, body > ol, body > blockquote,
-body > h1, body > h2, body > h3, body > h4 {
+body > h1, body > h2, body > h3, body > h4,
+body > .wrap > p, body > .wrap > .deck, body > .wrap > .lede,
+body > .wrap > ul, body > .wrap > ol, body > .wrap > blockquote,
+body > .wrap > h1, body > .wrap > h2, body > .wrap > h3, body > .wrap > h4 {
   max-width: 880px;
 }
 body > *:first-child { margin-top: 0 !important; }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ammduncan/easel",
-  "version": "0.2.19",
+  "version": "0.2.21",
   "description": "A live browser tab for every Claude Code (and MCP) session. The push MCP tool appends HTML cards to a scrolling feed you keep open in split-screen.",
   "type": "module",
   "license": "MIT",