feat(chrome): seed policy from portable markers

[mikeylong]

Summary

• extract deterministic chrome observations from portable markers instead of defaulting every web surface
• treat .contract-container as the primary layout-container signal, keep page-container optional, and preserve legacy data-contract-container compatibility
• seed chromePolicy conservatively from observed descriptors and document the portable opt-in adoption path

Testing

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

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
interfacectl	Ready	Preview, Comment	Mar 10, 2026 7:19pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6b2ec5b395

ℹ️ 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]

Ignore descendant selectors in chrome wrapper matching

This branch marks a section wrapper as matched whenever a selector string contains data-contract-section, but it never checks whether the selector actually targets the wrapper itself versus descendants. As a result, rules like [data-contract-section] > * { border-radius: 12px; } are incorrectly attributed to the section marker, inflating extracted chrome signals and seeding layout.chromePolicy with values that are not applied to governed wrappers.

Useful? React with 👍 / 👎.