fix(core): harden routing reliability and add quiet-hours controls - #375

'@prisma/client' import is duplicated.

'NotificationChannel' is defined but never used. Allowed unused vars must match /^_/u.

Generic Object Injection Sink

Unexpected any. Specify a different type.

`'` can be escaped with `'`, `‘`, `'`, `’`.

Unexpected alert.

Do not use `window.location.href` to navigate to internal Next.js pages. Use `redirect()` in the render phase, or `useRouter().push()` in Client Components' event handlers instead. See: https://nextjs.org/docs/messages/no-location-assign-relative-destination

Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element

Error: Calling setState synchronously within an effect can trigger cascading renders  Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following: * Update external systems with the latest state from React. * Subscribe for updates from some external system, calling setState in a callback function when external state changes.  Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).  /home/runner/work/OpsKnight/OpsKnight/src/app/(public)/m/login/MobileLoginClient.tsx:107:20   105 |   106 |   useEffect(() => { > 107 |     if (errorCode) setError(formatError(errorCode));       |                    ^^^^^^^^ Avoid calling setState() directly within an effect   108 |   }, [errorCode]);   109 |   110 |   useEffect(() => {

Potential timing attack, left side: true

'handleSecondKey' is never reassigned. Use 'const' instead.

React Hook useEffect has missing dependencies: 'isMobileMenuOpen' and 'setIsMobileMenuOpen'. Either include them or remove the dependency array.

Found non-literal argument to RegExp Constructor

Do not use an `<a>` element to navigate to `/incidents/`. Use `<Link />` from `next/link` instead. See: https://nextjs.org/docs/messages/no-html-link-for-pages

Compilation Skipped: Use of incompatible library  This API returns functions which cannot be memoized without leading to stale UI. To prevent this, by default React Compiler will skip memoizing this component/hook. However, you may see issues if values from this API are passed to other components/hooks that are memoized.  /home/runner/work/OpsKnight/OpsKnight/src/components/settings/forms/AutosaveForm.tsx:44:23   42 |   43 |   const { watch, formState } = form; > 44 |   const watchedData = watch();      |                       ^^^^^ React Hook Form's `useForm()` API returns a `watch()` function which cannot be memoized safely.   45 |   46 |   const { status, error, isSaving } = useAutosave({   47 |     data: watchedData,

The attribute aria-invalid is not supported by the role radio. This role is implicit on the element input.

Unsafe Regular Expression

Expected an error object to be thrown.

Expected an assignment or function call and instead saw an expression.

A `require()` style import is forbidden.

Found readFileSync from package "node:fs" with non literal argument at index 0