Repository navigation
chore: bump platform version to 0.6.8 and deduplicate admin navigation - #71
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Catalog curation, judge calibration and funnel reports now use the admin layout's single global menu. Child controls and footers are preserved, and nested main landmarks are removed. Platform version: 0.6.8.
Evidence
After: all 11 project checks pass, including 232 tests. The generated hierarchy audit covers 173 routes and 193 ancestor relationships with zero violations. Regression fixtures reject direct and wrapper-based duplication, accept alternative loading branches, and reject empty/incomplete inventory. Production visual checks follow native deployment.
npm run check:navigationis included in the existing release batch and documented in the release skill. It checks nested layout ownership; visual judgment remains required.Merge Danger
Door: two-way
Blast Radius: layout
Three admin content wrappers and release validation/metadata. No permission, database, model or publication-gate changes. No Lovable generation calls.