fix(alerts): repair 404 on View full logs anomaly link

[TerrifiedBug]

Summary

Fixes Notion bug: 404 on "View full logs" under anomaly alerts.

The link in error-context-panel.tsx pointed at /pipelines/[id]/logs which is not a route — pipeline logs render inline on /pipelines/[id] via a togglable side panel.

• Change href to /pipelines/[id]?logs=1
• Read ?logs=1 in /pipelines/[id]/page.tsx to initialize logsOpen=true so the panel auto-opens on deep-link navigation

Test plan

• Trigger an anomaly with error context, click "View full logs" → lands on pipeline page with logs panel open
• Direct visit /pipelines/[valid-id]?logs=1 → logs panel open by default
• Direct visit /pipelines/[valid-id] → logs panel closed by default (no regression)

Greptile Summary

This PR fixes a 404 by correcting the "View full logs" link in error-context-panel.tsx from the non-existent /pipelines/[id]/logs route to /pipelines/[id]?logs=1, and reads that query param in page.tsx to auto-open the logs side panel on deep-link navigation. The core fix is correct and the lazy useState initialiser is the right pattern for one-shot URL-driven state.

Confidence Score: 4/5

Safe to merge — the fix is correct and the only finding is a missing Suspense wrapper that generates a build warning but does not cause a runtime failure.

Only P2 findings present; score stays at 4/5 per the P2-only ceiling guidance.

src/app/(dashboard)/pipelines/[id]/page.tsx — needs a Suspense boundary around PipelineBuilderInner to satisfy Next.js App Router requirements for useSearchParams.

Important Files Changed

Filename	Overview
src/app/(dashboard)/alerts/_components/error-context-panel.tsx	Fixes broken "View full logs" link — replaces the non-existent /pipelines/[id]/logs route with the correct /pipelines/[id]?logs=1 deep-link URL.
src/app/(dashboard)/pipelines/[id]/page.tsx	Adds useSearchParams to read ?logs=1 and initialise logsOpen state; missing <Suspense> wrapper around the consuming component will cause a Next.js build warning.

Sequence Diagram

sequenceDiagram
    participant User
    participant AlertPanel as ErrorContextPanel
    participant PipelinePage as /pipelines/[id]/page

    User->>AlertPanel: clicks "View full logs"
    AlertPanel->>PipelinePage: navigate to /pipelines/[id]?logs=1
    PipelinePage->>PipelinePage: useSearchParams().get("logs") === "1"
    PipelinePage->>PipelinePage: useState initialiser → logsOpen = true
    PipelinePage->>User: renders with logs panel open

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: src/app/(dashboard)/pipelines/[id]/page.tsx
Line: 203

Comment:
**`useSearchParams` requires a Suspense boundary**

Next.js requires any component that calls `useSearchParams()` to be wrapped in a `<Suspense>` boundary; without one, the entire route tree de-opts from partial prerendering (PPR) and Next.js emits a build warning (`MISSING_SUSPENSE_WITH_CSR_BAILOUT`). Since `PipelineBuilderInner` is already nested inside `ReactFlowProvider`, the simplest fix is to wrap it in `Suspense` inside `PipelineBuilderPage`:

```tsx
import { Suspense } from "react";

export default function PipelineBuilderPage() {
  const params = useParams<{ id: string }>();
  return (
    <ReactFlowProvider>
      <Suspense>
        <PipelineBuilderInner pipelineId={params.id} />
      </Suspense>
    </ReactFlowProvider>
  );
}
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix(alerts): repair "View full logs" 404..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[greptile-apps]

useSearchParams requires a Suspense boundary

Next.js requires any component that calls useSearchParams() to be wrapped in a <Suspense> boundary; without one, the entire route tree de-opts from partial prerendering (PPR) and Next.js emits a build warning (MISSING_SUSPENSE_WITH_CSR_BAILOUT). Since PipelineBuilderInner is already nested inside ReactFlowProvider, the simplest fix is to wrap it in Suspense inside PipelineBuilderPage:

import { Suspense } from "react";

export default function PipelineBuilderPage() {
  const params = useParams<{ id: string }>();
  return (
    <ReactFlowProvider>
      <Suspense>
        <PipelineBuilderInner pipelineId={params.id} />
      </Suspense>
    </ReactFlowProvider>
  );
}

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/app/(dashboard)/pipelines/[id]/page.tsx
Line: 203

Comment:
**`useSearchParams` requires a Suspense boundary**

Next.js requires any component that calls `useSearchParams()` to be wrapped in a `<Suspense>` boundary; without one, the entire route tree de-opts from partial prerendering (PPR) and Next.js emits a build warning (`MISSING_SUSPENSE_WITH_CSR_BAILOUT`). Since `PipelineBuilderInner` is already nested inside `ReactFlowProvider`, the simplest fix is to wrap it in `Suspense` inside `PipelineBuilderPage`:

```tsx
import { Suspense } from "react";

export default function PipelineBuilderPage() {
  const params = useParams<{ id: string }>();
  return (
    <ReactFlowProvider>
      <Suspense>
        <PipelineBuilderInner pipelineId={params.id} />
      </Suspense>
    </ReactFlowProvider>
  );
}
```

How can I resolve this? If you propose a fix, please make it concise.