@quario/landing 0.2.0 → 0.2.1

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @quario/landing
 
+## 0.2.1
+
+### Patch Changes
+
+- Updated dependencies
+  - @quario/layout@0.6.0
+
 ## 0.2.0
 
 ### Minor Changes

package/README.md

@@ -6,7 +6,7 @@ render boundary across their lifetime, and both draw a panel when something fail
 that which are easy to get subtly wrong — and invisible when they are — live here once.
 
 You almost certainly do not install this package. The two surfaces depend on it and run it for
-you; it holds no report vocabulary and renders nothing.
+you. It holds no report vocabulary and renders nothing.
 
 ## Install
 
@@ -15,8 +15,8 @@ npm install @quario/landing
 ```
 
 One runtime dependency, `@quario/layout`, which the paged sheet paints through. It implements
-Lit's `ReactiveController` protocol, which is structural, so nothing is imported from `lit` at run
-time and this adds none of it to your tree.
+Lit's `ReactiveController` protocol, which is structural, so this package imports nothing from
+`lit` at run time and adds none of it to your tree.
 
 ESM-only, Node 22+, and browser-ready through a standards-based bundler. CSP-safe: no
 string-to-code paths anywhere.
@@ -24,32 +24,36 @@ string-to-code paths anywhere.
 ## What is here
 
 **`options()`** — the option check across one update cycle. A host writes several properties at
-once and gets one render, so the checks have to agree that one bad property does not block a good
-write to another, that a property still broken keeps the element failing rather than being cleared
-by an unrelated write, and that writing one property does not clobber what another committed. The
-checks themselves are each surface's own; only that agreement is here.
+once and gets one render, so the checks have to agree that:
 
-**`Landing`** — the render boundary: whether a render has ever painted the sheet, whether work was
-abandoned mid-flight, and the counter that asks for a fresh one. A disconnected element abandons
-work rather than hiding it, and comes back owing a render.
+- one bad property does not block a good write to another,
+- a property still broken keeps the element failing, rather than an unrelated write clearing it,
+- writing one property does not clobber what another committed.
+
+The checks themselves are each surface's own. Only that agreement is here.
+
+**`Landing`** — the render boundary: whether a render has ever painted the sheet, whether the
+element abandoned work mid-flight, and the counter that asks for a fresh one. A disconnected
+element abandons work rather than hiding it, and comes back owing a render.
 
 **`sheet()`** — the paged sheet both surfaces paint on: the extent of a display list, and the
-reach within it carrying elements and pixels. The sheet element is given its own height and width
+reach within it carrying elements and pixels. The sheet element takes its own height and width
 from the list's paper and paints the page silhouettes itself, so the extent a reader scrolls
-through is whole whatever is standing; only the pages in the reach have a canvas, positioned
+through is whole whatever is standing. Only the pages in the reach have a canvas, positioned
 absolutely at the offset `topOf()` reports. A list has one paper, so the pages are a pitch apart:
-a position is a multiple of it and the reach's two ends are a division by it. It takes a `scale()` thunk and the two elements, so
-scale policy stays with each surface, and so does the look of a page — the paper, the shadow, the
-margins. Everything that places a page is `sheet()`'s and needs no stylesheet from the caller.
+a position is a multiple of it and the reach's two ends are a division by it. `sheet()` takes a
+`scale()` thunk and the two elements, so scale policy stays with each surface, and so does the
+look of a page — the paper, the shadow, the margins. Everything that places a page is `sheet()`'s
+and needs no stylesheet from the caller.
 
-**`failures()`** — which failure a panel is showing and whether the reader put it away. Whether a
-repeat announces again is a policy the caller passes in, never a rule settled here: it is
+**`failures()`** — which failure a panel carries and whether the reader dismissed it. Whether
+a repeat announces again is a policy the caller passes in, never a rule settled here. It is
 downstream of what re-runs the render, which is the one thing the two surfaces do not share.
 
 ## What is not here
 
 Each surface's own property checks, its panel markup, and its public API. The two elements differ
-in their vocabulary and in their policy; only the machinery underneath is one thing.
+in their vocabulary and in their policy. Only the machinery underneath is one thing.
 
 ## Documentation
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quario/landing",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "What quario's two surface elements share — the option check, the render boundary and the failure state — in the makings, not yet released",
   "homepage": "https://getquario.com",
   "license": "SEE LICENSE IN LICENSE",
@@ -36,7 +36,7 @@
     "test:browser": "node test/browser/setup.js"
   },
   "dependencies": {
-    "@quario/layout": "^0.5.0"
+    "@quario/layout": "^0.6.0"
   },
   "devDependencies": {
     "@arethetypeswrong/cli": "^0.18.3",