Skip to content

Pin the minimum supported width and refresh launch status - #45

Merged
mandiau-matthias merged 1 commit into
mainfrom
test/minimum-width-and-status
Nov 17, 2026
Merged

mandiau-matthias merged 1 commit into
mainfrom
test/minimum-width-and-status

Conversation

@mandiau-matthias

Copy link
Copy Markdown
Contributor

What changed

  • The browser harness now exercises the experiment at 320 CSS pixels, the body's declared minimum, alongside 640 and 390.
  • Asserts no horizontal overflow, the 196×48 primary action, 44px utility targets and a dialog inside the viewport at all three widths.
  • Refreshes the 17 November traffic snapshot: 42 views from 4 unique visitors, 860 clones from 237 unique cloners, 0 referrers. Clones are still not users.
  • Updates the evidence date and the harness descriptions.

Release audit

Downloaded the published v0.9.0 tarball, MCPB and server.json; all three matched SHA256SUMS. The MCP Registry entry is active at 0.9.0 with the same bundle URL. Published artifacts remain immutable.

Verification

  • npm run test:browser — exit 0; 640/390/320 layout passes
  • npm run check — exit 0, 146 unit tests, 5 integration tests, package and bundle checks
  • Release checksums — 3/3 OK
  • Registry — io.github.Automatron-workflows/hardwire 0.9.0 active

Boundary

The 320px check is a layout regression, not a new device or assistive-technology result. No outside completion appeared.

Exercise the experiment at 320 CSS pixels, the body's declared minimum, in addition to 640 and 390. The primary action, utility targets, dialog and overflow checks pass.\n\nRefresh the 17 November traffic snapshot and evidence date. Release audit: published v0.9.0 SHA256SUMS verified for the tarball, bundle and server metadata, and the registry entry is active at 0.9.0.
@mandiau-matthias
mandiau-matthias merged commit 403749e into main Nov 17, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant