Keep Tailwind's scan off the server-side folders

The task work added ref strings ([file:ID], [bot:3]) in new prompt and tool
files, so the warning about "file" not being a known CSS property came back:
Tailwind read them as arbitrary-property utilities and emitted `file: ID`.

The exclusion list now covers every server-side directory whole instead of
one file at a time (none of them holds a className, so nothing is lost), and
`dict` stays scanned for the static hue classes. The ref literals that must
live in scanned files are reworded in comments, and task-file-row builds its
chip through `fileRef` rather than its own template literal.

src/pages/admin/bots/[bot_id]/(hooks)/use-composer-editor.ts

@@ -43,8 +43,8 @@ type Params = {
 /**
  * The composer's editor (Tiptap): markdown in and out, with bold, italic,
  * strike, code, lists, quotes and links (no headings), and mentions of
- * bots (`@`) and workspaces (`#`) written as `[bot:ID]` and
- * `[workspace:ID]`. Enter sends and Shift+Enter breaks the line, except
+ * bots (`@`) and workspaces (`#`), written as their bot or workspace ref.
+ * Enter sends and Shift+Enter breaks the line, except
  * in a code block or list, where Enter is the editor's and Mod+Enter
  * sends. Enter picks from an open mention menu. Pasted text comes in
  * plain, without another site's styling; pasted or dropped files go to