️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 19, 2026 4:10am

PR Summary

Low Risk
Low risk: adds two isolated not-found.tsx components to change error rendering for invalid slugs, without touching routing logic, data access, or auth.

Overview
Invalid routes under /models and /integrations now render dedicated, section-scoped 404 pages instead of falling back to the global app/not-found.tsx.

The new not-found.tsx files display the centered “Page not found” message and a “Return to Home” CTA while inheriting the surrounding landing layout (avoiding duplicated global 404 UI like the navbar/background).

^{Reviewed by Cursor Bugbot for commit 8ad41a2. Configure here.}

Greptile Summary

This PR adds scoped not-found.tsx files under (landing)/integrations/ and (landing)/models/ so that notFound() calls in those route segments (triggered by dynamicParams = false on invalid slugs) are caught by the nearest boundary rather than falling back to app/not-found.tsx. The root 404 previously duplicated the <Navbar> and <AuthBackground> on top of the section layout's own <Navbar>/<Footer>, causing a crash. The new files correctly delegate chrome to the existing section layouts and render only the centered 404 message.

Confidence Score: 5/5

Safe to merge — minimal, focused fix with no logic issues or regressions

Both new files are pure server components with no state, no data-fetching, and no side effects. The CSS variables used by AUTH_PRIMARY_CTA_BASE are globally defined in globals.css so they resolve correctly inside the landing layout context. Next.js correctly bubbles notFound() to the nearest not-found.tsx boundary, so the scoped files will intercept all invalid slug requests for their respective sections. No P1 or P0 issues found.

No files require special attention

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant User
    participant Next as Next.js Router
    participant Page as [slug]/page.tsx<br/>(dynamicParams=false)
    participant ScopedNF as integrations/not-found.tsx<br/>(NEW)
    participant Layout as IntegrationsLayout<br/>(Navbar + Footer)
    participant RootNF as app/not-found.tsx<br/>(BEFORE — duplicate Navbar)

    User->>Next: GET /integrations/rand
    Next->>Page: render page
    Page-->>Next: notFound() thrown

    Note over Next,RootNF: BEFORE this PR
    Next->>RootNF: bubble to root not-found
    RootNF->>Layout: layout wraps → duplicate Navbar crash

    Note over Next,ScopedNF: AFTER this PR
    Next->>ScopedNF: caught by nearest not-found.tsx
    Layout->>ScopedNF: wraps with Navbar + Footer (correct)
    ScopedNF-->>User: styled 404 with single Navbar

_{Reviews (2): Last reviewed commit: "fix(landing): render proper 404 for inva..." | Re-trigger Greptile}

@greptile

@cursor review