Skip to content

Preserve separate responsive navigation surfaces - #1669

Merged
chubes4 merged 6 commits into
trunkfrom
fix/separate-responsive-menu-artifact
Sep 11, 2026
Merged

Preserve separate responsive navigation surfaces#1669
chubes4 merged 6 commits into
trunkfrom
fix/separate-responsive-menu-artifact

Conversation

@chubes4

@chubes4 chubes4 commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Purpose

Keep independently authored desktop navigation and mobile details-disclosure navigation as separate responsive surfaces. This stacked PR depends on #1647.

Changes

  • Keep captured disclosure navigation out of overlay-pair suppression.
  • Avoid projecting navigation spacing onto the list-navigation class.
  • Add a contract fixture for desktop navigation paired with a native mobile details disclosure.

Verification

  • Navigation contract passed: canonical block style attributes, HTML-to-blocks, and format bridge scaffold.
  • PHP lint passed for both production files.
  • Frontend artifact compilation matched the authored desktop/mobile visibility variants and preserved the disclosure interaction.

Draft Gate

This is not a solved-site claim. Canonical fresh import verification has not yet run.

AI assistance: GPT-6 Astra through OpenCode was used for parallel implementation, review, and test orchestration.

Base automatically changed from fix/form-auxiliary-visual-payload to trunk September 11, 2026 16:45
@chubes4
chubes4 marked this pull request as ready for review September 11, 2026 16:45
@chubes4
chubes4 merged commit 58a1cbc into trunk Sep 11, 2026
10 checks passed
@chubes4
chubes4 deleted the fix/separate-responsive-menu-artifact branch September 11, 2026 16:46
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