humanish 0.20.4 → 0.21.0

package/docs/architecture/external-public-shared-world.md

@@ -102,11 +102,14 @@ e2b-URL / host-digest redaction discipline.
 ## Mobile fidelity caveat
 
 The example roster runs mobile-LAYOUT seats (`device: mobile` 414×896, `small-mobile` 360×740). On the
-E2B-desktop route ONLY width/height physically render — the X screen is sized to the preset so the
-app's width-based responsive CSS fires (real mobile LAYOUT), but there is NO touch input, and
-`isMobile`/DPR are prompt-signal + metadata (DPR renders only via the CDP geometry path). "3 mobile
-personas" = 3 mobile-LAYOUT desktop-Chromium seats, not touch devices. Do not over-read the results as
-true mobile-device coverage.
+E2B-desktop route the rendered WIDTH is floored to `MIN_DESKTOP_RENDER_WIDTH` (500) because Chrome
+refuses a narrower window and a narrower X screen clipped the page (0.20.3, #304), so both presets
+render at 500 wide and are identical in layout; only HEIGHT renders as declared.
+`desktopGeometry.screen.verified` compares the floored number with itself, so it does not attest the
+preset width. There is NO touch input, and `isMobile`/DPR are prompt-signal + metadata (DPR renders
+only via the CDP geometry path). "3 mobile personas" = 3 mobile-LAYOUT desktop-Chromium seats, not
+touch devices. Do not over-read the results as true mobile-device coverage. True sub-500 rendering is
+the #221 upgrade.
 
 ## Watch-from-phone
 

package/docs/contracts/run-bundle.md

@@ -81,11 +81,17 @@ responses, but durable run bundles use the public-safe `[target-cwd]` marker.
 
 ## Hosted Desktop Geometry
 
-Hosted browser streams may carry additive `desktopGeometry` evidence. Its fields keep four
+Hosted browser streams may carry additive `desktopGeometry` evidence. Its fields keep five
 different facts separate:
 
 - `screen.requested`: the E2B/X screen size requested by config;
 - `screen.verified`: the screen size measured in-sandbox with `xdpyinfo`;
+- `screen.declared`: the device preset the lab ASKED for, present only when it differs from
+  `screen.requested` because the rendered width was floored to Chrome's ~500px window minimum.
+  `verified` compares the floored number with itself and reports a match, so a matching
+  `verified` block is NOT evidence that the preset width rendered. When `declared` is present,
+  it did not: a `mobile` (414) and a `small-mobile` (360) seat both render at 500 and are
+  indistinguishable by rendered width;
 - `browserWindow`: outer browser bounds measured after the window-fill attempt;
 - `viewport`: the page's CSS layout viewport and device-pixel ratio measured through CDP on
   Chromium-family hosted browsers.

package/docs/contracts/schemas.md

@@ -3,7 +3,7 @@
 Date: 2026-06-02 (current-state note updated 2026-07-14)
 
 Status: reference map for the major contracts shipped through source version
-`0.20.4`; it is not an exhaustive inventory of command/result envelopes. Exported types,
+`0.21.0`; it is not an exhaustive inventory of command/result envelopes. Exported types,
 schema constants, parsers, and validators in `src/` are authoritative. Rows
 marked "reserved" name layering intent only — no code emits or validates them
 yet. Do not emit a reserved schema.

package/docs/goals/current.md

@@ -16,7 +16,7 @@ Humanish should be the open-source CLI that lets a maintainer ask:
 The answer should be observable, verifiable, public-safe, and easy to turn into
 actionable feedback.
 
-## Current Program Truth (source `0.20.4`)
+## Current Program Truth (source `0.21.0`)
 
 The package source and repository implementation in this tree agree on these
 points:

package/docs/product/cineguessr-3player-external-public.md

@@ -18,11 +18,20 @@ a public deployment YOU own/operate.
 ## Mobile fidelity caveat (read before over-reading the results)
 
 The seats are `device: mobile` (414×896) and `device: small-mobile` (360×740). On the E2B-desktop
-route ONLY width/height physically render — the X screen is sized to the preset so the app's
-width-based responsive CSS fires (real mobile LAYOUT), but there is NO touch input, and isMobile/DPR
-are prompt-signal + metadata (DPR renders only via the CDP geometry path). So "3 mobile personas"
-means 3 mobile-LAYOUT desktop-Chromium seats, NOT touch devices. If a flow needs true touch/tap
-semantics, these seats will not exercise it.
+route the rendered WIDTH is floored to `MIN_DESKTOP_RENDER_WIDTH` (500): Chrome refuses a window
+narrower than ~500 CSS px, and a narrower X screen let the window overflow and clip the page
+(0.20.3, #304). So both presets render at **500 wide**, `mobile` and `small-mobile` are identical in
+layout on this route, and this example does NOT currently exercise two different mobile widths. Only
+the HEIGHT renders as declared (896 and 740).
+
+Note that `desktopGeometry.screen.verified` checks the FLOORED number against itself, so a matching
+`verified` block is not evidence that the preset width rendered. Read `requested` against the preset
+in `device-presets.ts` if you need to know.
+
+There is NO touch input, and isMobile/DPR are prompt-signal + metadata (DPR renders only via the CDP
+geometry path). So "3 mobile personas" means 3 mobile-LAYOUT desktop-Chromium seats, NOT touch
+devices. If a flow needs true touch/tap semantics, these seats will not exercise it. True sub-500
+CSS-viewport rendering is the #221 CDP-device-emulation upgrade.
 
 ## Run it
 

package/docs/ramp/README.md

@@ -2,7 +2,7 @@
 
 Status: public-safe contributor and agent ramp.
 
-Package/source version in this tree: `0.20.4` (2026-08-03). The containment boundary introduced in
+Package/source version in this tree: `0.21.0` (2026-08-04). The containment boundary introduced in
 `0.15.1` remains in force: managed run and output paths bind to validated
 physical filesystem identities, and stored provider IDs are evidence, not
 cleanup authority. The bundled OSS meta-lab is dry-run only until

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "humanish",
-  "version": "0.20.4",
+  "version": "0.21.0",
   "description": "Open-source-safe CLI for persona simulation, observer review, and public-safe feedback drafts.",
   "author": "Daniel G Wilson <daniel@danielgwilson.com>",
   "keywords": [