Episode 2 — React Frontend Architecture NextJS / 2.11 — Routing and Application Structure
2.11.e — Layout components & shared chrome
Learning outcomes
- Model header/sidebar as a parent layout route.
- Keep auth gating consistent for nested private sections.
- Avoid duplicating chrome in every page.
Pattern
Parent route element renders persistent UI + <Outlet /> for nested pages. Children swap while chrome remains.
Auth shell (conceptual)
Private routes live under a layout that checks session (loader, wrapper component, or route guard pattern depending on router mode). Ensure deep links cannot bypass the guard accidentally.
Appendix — Scenario bank (basic → advanced)
Drill format: broken URL / UX → root cause → fix → interview phrase.
RR4-001 — Layouts #1
- Level: Beginner
- Symptom: 404 on refresh at depth
13or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-002 — Layouts #2
- Level: Beginner+
- Symptom: 404 on refresh at depth
26or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-003 — Layouts #3
- Level: Intermediate
- Symptom: 404 on refresh at depth
39or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-004 — Layouts #4
- Level: Intermediate+
- Symptom: 404 on refresh at depth
52or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-005 — Layouts #5
- Level: Advanced
- Symptom: 404 on refresh at depth
65or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-006 — Layouts #6
- Level: Advanced+
- Symptom: 404 on refresh at depth
78or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-007 — Layouts #7
- Level: Beginner
- Symptom: 404 on refresh at depth
91or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-008 — Layouts #8
- Level: Beginner+
- Symptom: 404 on refresh at depth
104or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-009 — Layouts #9
- Level: Intermediate
- Symptom: 404 on refresh at depth
117or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-010 — Layouts #10
- Level: Intermediate+
- Symptom: 404 on refresh at depth
130or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-011 — Layouts #11
- Level: Advanced
- Symptom: 404 on refresh at depth
143or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-012 — Layouts #12
- Level: Advanced+
- Symptom: 404 on refresh at depth
156or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-013 — Layouts #13
- Level: Beginner
- Symptom: 404 on refresh at depth
169or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-014 — Layouts #14
- Level: Beginner+
- Symptom: 404 on refresh at depth
182or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-015 — Layouts #15
- Level: Intermediate
- Symptom: 404 on refresh at depth
195or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-016 — Layouts #16
- Level: Intermediate+
- Symptom: 404 on refresh at depth
8or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-017 — Layouts #17
- Level: Advanced
- Symptom: 404 on refresh at depth
21or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-018 — Layouts #18
- Level: Advanced+
- Symptom: 404 on refresh at depth
34or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-019 — Layouts #19
- Level: Beginner
- Symptom: 404 on refresh at depth
47or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-020 — Layouts #20
- Level: Beginner+
- Symptom: 404 on refresh at depth
60or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-021 — Layouts #21
- Level: Intermediate
- Symptom: 404 on refresh at depth
73or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-022 — Layouts #22
- Level: Intermediate+
- Symptom: 404 on refresh at depth
86or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-023 — Layouts #23
- Level: Advanced
- Symptom: 404 on refresh at depth
99or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-024 — Layouts #24
- Level: Advanced+
- Symptom: 404 on refresh at depth
112or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-025 — Layouts #25
- Level: Beginner
- Symptom: 404 on refresh at depth
125or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-026 — Layouts #26
- Level: Beginner+
- Symptom: 404 on refresh at depth
138or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-027 — Layouts #27
- Level: Intermediate
- Symptom: 404 on refresh at depth
151or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-028 — Layouts #28
- Level: Intermediate+
- Symptom: 404 on refresh at depth
164or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-029 — Layouts #29
- Level: Advanced
- Symptom: 404 on refresh at depth
177or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-030 — Layouts #30
- Level: Advanced+
- Symptom: 404 on refresh at depth
190or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-031 — Layouts #31
- Level: Beginner
- Symptom: 404 on refresh at depth
3or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-032 — Layouts #32
- Level: Beginner+
- Symptom: 404 on refresh at depth
16or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-033 — Layouts #33
- Level: Intermediate
- Symptom: 404 on refresh at depth
29or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-034 — Layouts #34
- Level: Intermediate+
- Symptom: 404 on refresh at depth
42or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-035 — Layouts #35
- Level: Advanced
- Symptom: 404 on refresh at depth
55or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-036 — Layouts #36
- Level: Advanced+
- Symptom: 404 on refresh at depth
68or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-037 — Layouts #37
- Level: Beginner
- Symptom: 404 on refresh at depth
81or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-038 — Layouts #38
- Level: Beginner+
- Symptom: 404 on refresh at depth
94or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-039 — Layouts #39
- Level: Intermediate
- Symptom: 404 on refresh at depth
107or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-040 — Layouts #40
- Level: Intermediate+
- Symptom: 404 on refresh at depth
120or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-041 — Layouts #41
- Level: Advanced
- Symptom: 404 on refresh at depth
133or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-042 — Layouts #42
- Level: Advanced+
- Symptom: 404 on refresh at depth
146or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-043 — Layouts #43
- Level: Beginner
- Symptom: 404 on refresh at depth
159or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-044 — Layouts #44
- Level: Beginner+
- Symptom: 404 on refresh at depth
172or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-045 — Layouts #45
- Level: Intermediate
- Symptom: 404 on refresh at depth
185or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-046 — Layouts #46
- Level: Intermediate+
- Symptom: 404 on refresh at depth
198or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-047 — Layouts #47
- Level: Advanced
- Symptom: 404 on refresh at depth
11or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-048 — Layouts #48
- Level: Advanced+
- Symptom: 404 on refresh at depth
24or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-049 — Layouts #49
- Level: Beginner
- Symptom: 404 on refresh at depth
37or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-050 — Layouts #50
- Level: Beginner+
- Symptom: 404 on refresh at depth
50or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-051 — Layouts #51
- Level: Intermediate
- Symptom: 404 on refresh at depth
63or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-052 — Layouts #52
- Level: Intermediate+
- Symptom: 404 on refresh at depth
76or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-053 — Layouts #53
- Level: Advanced
- Symptom: 404 on refresh at depth
89or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-054 — Layouts #54
- Level: Advanced+
- Symptom: 404 on refresh at depth
102or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-055 — Layouts #55
- Level: Beginner
- Symptom: 404 on refresh at depth
115or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-056 — Layouts #56
- Level: Beginner+
- Symptom: 404 on refresh at depth
128or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-057 — Layouts #57
- Level: Intermediate
- Symptom: 404 on refresh at depth
141or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-058 — Layouts #58
- Level: Intermediate+
- Symptom: 404 on refresh at depth
154or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-059 — Layouts #59
- Level: Advanced
- Symptom: 404 on refresh at depth
167or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-060 — Layouts #60
- Level: Advanced+
- Symptom: 404 on refresh at depth
180or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-061 — Layouts #61
- Level: Beginner
- Symptom: 404 on refresh at depth
193or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-062 — Layouts #62
- Level: Beginner+
- Symptom: 404 on refresh at depth
6or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-063 — Layouts #63
- Level: Intermediate
- Symptom: 404 on refresh at depth
19or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-064 — Layouts #64
- Level: Intermediate+
- Symptom: 404 on refresh at depth
32or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-065 — Layouts #65
- Level: Advanced
- Symptom: 404 on refresh at depth
45or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-066 — Layouts #66
- Level: Advanced+
- Symptom: 404 on refresh at depth
58or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-067 — Layouts #67
- Level: Beginner
- Symptom: 404 on refresh at depth
71or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-068 — Layouts #68
- Level: Beginner+
- Symptom: 404 on refresh at depth
84or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-069 — Layouts #69
- Level: Intermediate
- Symptom: 404 on refresh at depth
97or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-070 — Layouts #70
- Level: Intermediate+
- Symptom: 404 on refresh at depth
110or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-071 — Layouts #71
- Level: Advanced
- Symptom: 404 on refresh at depth
123or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-072 — Layouts #72
- Level: Advanced+
- Symptom: 404 on refresh at depth
136or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-073 — Layouts #73
- Level: Beginner
- Symptom: 404 on refresh at depth
149or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-074 — Layouts #74
- Level: Beginner+
- Symptom: 404 on refresh at depth
162or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-075 — Layouts #75
- Level: Intermediate
- Symptom: 404 on refresh at depth
175or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-076 — Layouts #76
- Level: Intermediate+
- Symptom: 404 on refresh at depth
188or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-077 — Layouts #77
- Level: Advanced
- Symptom: 404 on refresh at depth
1or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-078 — Layouts #78
- Level: Advanced+
- Symptom: 404 on refresh at depth
14or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-079 — Layouts #79
- Level: Beginner
- Symptom: 404 on refresh at depth
27or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-080 — Layouts #80
- Level: Beginner+
- Symptom: 404 on refresh at depth
40or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-081 — Layouts #81
- Level: Intermediate
- Symptom: 404 on refresh at depth
53or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-082 — Layouts #82
- Level: Intermediate+
- Symptom: 404 on refresh at depth
66or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-083 — Layouts #83
- Level: Advanced
- Symptom: 404 on refresh at depth
79or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-084 — Layouts #84
- Level: Advanced+
- Symptom: 404 on refresh at depth
92or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-085 — Layouts #85
- Level: Beginner
- Symptom: 404 on refresh at depth
105or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-086 — Layouts #86
- Level: Beginner+
- Symptom: 404 on refresh at depth
118or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-087 — Layouts #87
- Level: Intermediate
- Symptom: 404 on refresh at depth
131or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-088 — Layouts #88
- Level: Intermediate+
- Symptom: 404 on refresh at depth
144or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-089 — Layouts #89
- Level: Advanced
- Symptom: 404 on refresh at depth
157or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-090 — Layouts #90
- Level: Advanced+
- Symptom: 404 on refresh at depth
170or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-091 — Layouts #91
- Level: Beginner
- Symptom: 404 on refresh at depth
183or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-092 — Layouts #92
- Level: Beginner+
- Symptom: 404 on refresh at depth
196or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-093 — Layouts #93
- Level: Intermediate
- Symptom: 404 on refresh at depth
9or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-094 — Layouts #94
- Level: Intermediate+
- Symptom: 404 on refresh at depth
22or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-095 — Layouts #95
- Level: Advanced
- Symptom: 404 on refresh at depth
35or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-096 — Layouts #96
- Level: Advanced+
- Symptom: 404 on refresh at depth
48or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-097 — Layouts #97
- Level: Beginner
- Symptom: 404 on refresh at depth
61or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-098 — Layouts #98
- Level: Beginner+
- Symptom: 404 on refresh at depth
74or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-099 — Layouts #99
- Level: Intermediate
- Symptom: 404 on refresh at depth
87or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-100 — Layouts #100
- Level: Intermediate+
- Symptom: 404 on refresh at depth
100or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-101 — Layouts #101
- Level: Advanced
- Symptom: 404 on refresh at depth
113or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-102 — Layouts #102
- Level: Advanced+
- Symptom: 404 on refresh at depth
126or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-103 — Layouts #103
- Level: Beginner
- Symptom: 404 on refresh at depth
139or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-104 — Layouts #104
- Level: Beginner+
- Symptom: 404 on refresh at depth
152or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-105 — Layouts #105
- Level: Intermediate
- Symptom: 404 on refresh at depth
165or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-106 — Layouts #106
- Level: Intermediate+
- Symptom: 404 on refresh at depth
178or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-107 — Layouts #107
- Level: Advanced
- Symptom: 404 on refresh at depth
191or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-108 — Layouts #108
- Level: Advanced+
- Symptom: 404 on refresh at depth
4or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-109 — Layouts #109
- Level: Beginner
- Symptom: 404 on refresh at depth
17or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-110 — Layouts #110
- Level: Beginner+
- Symptom: 404 on refresh at depth
30or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-111 — Layouts #111
- Level: Intermediate
- Symptom: 404 on refresh at depth
43or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-112 — Layouts #112
- Level: Intermediate+
- Symptom: 404 on refresh at depth
56or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-113 — Layouts #113
- Level: Advanced
- Symptom: 404 on refresh at depth
69or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-114 — Layouts #114
- Level: Advanced+
- Symptom: 404 on refresh at depth
82or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-115 — Layouts #115
- Level: Beginner
- Symptom: 404 on refresh at depth
95or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-116 — Layouts #116
- Level: Beginner+
- Symptom: 404 on refresh at depth
108or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-117 — Layouts #117
- Level: Intermediate
- Symptom: 404 on refresh at depth
121or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-118 — Layouts #118
- Level: Intermediate+
- Symptom: 404 on refresh at depth
134or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-119 — Layouts #119
- Level: Advanced
- Symptom: 404 on refresh at depth
147or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-120 — Layouts #120
- Level: Advanced+
- Symptom: 404 on refresh at depth
160or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-121 — Layouts #121
- Level: Beginner
- Symptom: 404 on refresh at depth
173or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-122 — Layouts #122
- Level: Beginner+
- Symptom: 404 on refresh at depth
186or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-123 — Layouts #123
- Level: Intermediate
- Symptom: 404 on refresh at depth
199or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-124 — Layouts #124
- Level: Intermediate+
- Symptom: 404 on refresh at depth
12or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-125 — Layouts #125
- Level: Advanced
- Symptom: 404 on refresh at depth
25or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-126 — Layouts #126
- Level: Advanced+
- Symptom: 404 on refresh at depth
38or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-127 — Layouts #127
- Level: Beginner
- Symptom: 404 on refresh at depth
51or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-128 — Layouts #128
- Level: Beginner+
- Symptom: 404 on refresh at depth
64or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-129 — Layouts #129
- Level: Intermediate
- Symptom: 404 on refresh at depth
77or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-130 — Layouts #130
- Level: Intermediate+
- Symptom: 404 on refresh at depth
90or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-131 — Layouts #131
- Level: Advanced
- Symptom: 404 on refresh at depth
103or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-132 — Layouts #132
- Level: Advanced+
- Symptom: 404 on refresh at depth
116or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-133 — Layouts #133
- Level: Beginner
- Symptom: 404 on refresh at depth
129or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-134 — Layouts #134
- Level: Beginner+
- Symptom: 404 on refresh at depth
142or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-135 — Layouts #135
- Level: Intermediate
- Symptom: 404 on refresh at depth
155or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-136 — Layouts #136
- Level: Intermediate+
- Symptom: 404 on refresh at depth
168or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-137 — Layouts #137
- Level: Advanced
- Symptom: 404 on refresh at depth
181or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-138 — Layouts #138
- Level: Advanced+
- Symptom: 404 on refresh at depth
194or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-139 — Layouts #139
- Level: Beginner
- Symptom: 404 on refresh at depth
7or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-140 — Layouts #140
- Level: Beginner+
- Symptom: 404 on refresh at depth
20or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-141 — Layouts #141
- Level: Intermediate
- Symptom: 404 on refresh at depth
33or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-142 — Layouts #142
- Level: Intermediate+
- Symptom: 404 on refresh at depth
46or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-143 — Layouts #143
- Level: Advanced
- Symptom: 404 on refresh at depth
59or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-144 — Layouts #144
- Level: Advanced+
- Symptom: 404 on refresh at depth
72or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-145 — Layouts #145
- Level: Beginner
- Symptom: 404 on refresh at depth
85or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-146 — Layouts #146
- Level: Beginner+
- Symptom: 404 on refresh at depth
98or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-147 — Layouts #147
- Level: Intermediate
- Symptom: 404 on refresh at depth
111or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-148 — Layouts #148
- Level: Intermediate+
- Symptom: 404 on refresh at depth
124or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-149 — Layouts #149
- Level: Advanced
- Symptom: 404 on refresh at depth
137or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-150 — Layouts #150
- Level: Advanced+
- Symptom: 404 on refresh at depth
150or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-151 — Layouts #151
- Level: Beginner
- Symptom: 404 on refresh at depth
163or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-152 — Layouts #152
- Level: Beginner+
- Symptom: 404 on refresh at depth
176or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-153 — Layouts #153
- Level: Intermediate
- Symptom: 404 on refresh at depth
189or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Outlet wrapped in extra div breaking CSS grid areas.
- Primary remediation: Adjust markup/CSS grid to account for Outlet wrapper or use fragment patterns.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-154 — Layouts #154
- Level: Intermediate+
- Symptom: 404 on refresh at depth
2or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Sidebar state reset on navigation because stored in page not layout.
- Primary remediation: Reserve layout space for predictable skeleton placement.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-155 — Layouts #155
- Level: Advanced
- Symptom: 404 on refresh at depth
15or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Auth layout bypassed by deep link if guard only in child.
- Primary remediation: Centralize breadcrumb config keyed by route metadata.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-156 — Layouts #156
- Level: Advanced+
- Symptom: 404 on refresh at depth
28or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Header duplicated in both parent and child by mistake.
- Primary remediation: Single layout owns chrome; children only add page body.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-157 — Layouts #157
- Level: Beginner
- Symptom: 404 on refresh at depth
41or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Breadcrumb derived incorrectly for nested path segments.
- Primary remediation: Guard at layout route or data router loader level consistently.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.
RR4-158 — Layouts #158
- Level: Beginner+
- Symptom: 404 on refresh at depth
54or wrong active nav highlight. - Structure symptom: duplicated layout or import cycles after refactor.
- Root cause class: Loading skeleton only in child causing layout shift in header.
- Primary remediation: Lift persistent UI state to layout-level component or store.
- Verify: direct URL load, back/forward, deep link from email, mobile share sheet.
- Interview one-liner: Layout routes are composition boundaries—match them to design system regions.