The runtime error bubbles up because shadcn’s <Input> component (just like Select and others) calls useFormField() internally.
In components/template-list.tsx the search bar was rendered standalone, so the hook couldn’t find the surrounding <FormField> provider and threw the error.

Fix: wrap the search bar in a dummy React-Hook-Form <FormField> just like the other filters.

Reload /templates; the page should render without the “useFormField” error.

The error means a shadcn UI component (Input / Select / Switch, etc.) is still rendered without the React-Hook-Form context provided by <FormField>.
The only element outside the context was the search bar in components/template-list.tsx.

Below is a concise patch that wraps that search input (and its icon) in the proper RHF <FormField> ➜ <FormItem> ➜ <FormControl> hierarchy.
Nothing else is touched.

After this change every shadcn form control on the /templates page is nested inside <FormField>, eliminating the runtime error.