Decide exactly where the client/server boundary belongs in your component tree

<context>
Framework: Next.js App Router, React 19.
Component tree to review: app/dashboard/page.tsx renders <Header>, <RevenueChart interactive filters>, <RecentOrdersTable> with a sort-by-column click handler
What actually needs to be interactive (state, event handlers, browser APIs): Users can filter the revenue chart by date range and click a table header to re-sort orders client-side
</context>

<task>
Go through the component tree above and decide, component by component, whether it should be a Server Component (the default — no directive) or a Client Component ('use client'). Do not default to marking a whole page or layout as a Client Component because one child needs interactivity.
</task>

<decision_rules>
Mark a component 'use client' ONLY if it directly does at least one of:
- calls useState, useReducer, useEffect, or any other React hook that needs the browser
- attaches an event handler (onClick, onChange, onSubmit as a client handler, etc.)
- reads browser-only APIs (window, localStorage, navigator, IntersectionObserver)
- imports a third-party library that itself requires the client (a charting library, a rich-text editor, most drag-and-drop libraries)
- uses React context created with createContext for state that changes at runtime

Everything else stays a Server Component by default, including anything that only fetches data, reads env vars/secrets, or renders static markup.
When a component needs both — server-fetched data AND client interactivity — split it: fetch in a Server Component parent, pass the data down as props/children to a small Client Component that only handles the interactive part. Never lift the boundary higher than the smallest node that actually needs it.
</decision_rules>

<output_format>
A table: Component | Server or Client | One-line reason | If Client, which specific trigger from decision_rules applies.
Then, for any component you'd restructure (split a mixed component into a server parent + client leaf), show the before/after component boundary as a short tree diagram, not full code.
</output_format>