feat: add pageFrame containerMinWidthPx CI enforcement

[mikeylong]

Summary

• add optional layout.pageFrame.containerMinWidthPx to contract schema/types
• enforce exact deterministic px min-width matching in validator at CI/CD time
• extend static extractor (inline/CSS/Tailwind/css-var) for min-width
• add CLI finding mapping for layout.pageframe.minwidth-mismatch
• add tests, fixtures, docs, and dist rebuilds

Validation

• pnpm run build
• pnpm --filter @surfaces/interfacectl-validator run test
• pnpm --filter @surfaces/interfacectl-cli run test

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
interfacectl	Error		Feb 18, 2026 10:53pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c21c62e4d7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Scope Tailwind min-width extraction to page container

This fallback extracts min-w-[...] from the entire file content, not from the element marked with data-contract="page-container". In a surface where the page-frame container has no min-width but some unrelated component uses min-w-[1024px], minWidthPx is populated anyway and CI can incorrectly pass containerMinWidthPx enforcement. Because this commit adds strict min-width matching, this creates a real false-negative path for the new check.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Skip min-width fallback scans when min-width is not contracted

The new guard makes every fallback strategy run whenever minWidthPx is null, but minWidthPx stays null for contracts that omit containerMinWidthPx (the common optional case). That means validation now always scans CSS/TSX fallbacks even after max-width and padding are already resolved, which is an avoidable CI-time regression introduced by this change.

Useful? React with 👍 / 👎.