docs/package.json (1)

17-17: ⚡ Quick win

Move drizzle-kit to devDependencies.

drizzle-kit is a CLI tool for schema migrations and generation, not a runtime dependency. It should be in devDependencies to avoid including it in production installs. No runtime usage of this package was found in the codebase.

Suggested change

   "dependencies": {
     "@libsql/client": "^0.17.2",
     "@nuxt/content": "link:..",
     "@nuxthub/core": "^0.10.7",
     "@nuxtjs/plausible": "^3.0.2",
     "@vercel/analytics": "^2.0.1",
     "@vercel/speed-insights": "^2.0.0",
     "@vueuse/nuxt": "^14.2.1",
     "better-sqlite3": "^12.8.0",
     "docus": "^5.8.1",
-    "drizzle-kit": "^0.31.10",
     "drizzle-orm": "^0.45.1",
     "minisearch": "^7.2.0",
     "nuxt": "^4.4.2",
     "nuxt-studio": "^1.5.1"
+  },
+  "devDependencies": {
+    "drizzle-kit": "^0.31.10"
   }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/package.json` at line 17, The package.json currently lists "drizzle-kit"
in dependencies; move "drizzle-kit" into devDependencies instead because it's a
CLI/build tool not required at runtime: remove the "drizzle-kit" entry from the
top-level "dependencies" and add the same version string under "devDependencies"
(preserve the version "^0.31.10"), then update your lockfile by running your
package manager (npm/yarn/pnpm install) to reflect the change; verify no runtime
imports reference "drizzle-kit" and commit the modified package.json and updated
lockfile.

src/runtime/client.ts (2)

100-100: ⚖️ Poor tradeoff

Consider adding a cleanup method.

The composable doesn't expose a way to dispose of the DatabaseAdapter. If the component using this composable is unmounted or the collections change significantly, the database adapter and FTS index remain in memory.

Consider adding a destroy() or cleanup() method to the return object that closes the database adapter if the underlying implementation supports it:

function destroy() {
  db = undefined
  initPromise = undefined
  indexedFor = []
  status.value = 'idle'
}

return { status, search, init, destroy }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/runtime/client.ts` at line 100, Add a cleanup method to the composable
that disposes the DatabaseAdapter and resets internal state: implement a destroy
or cleanup function that, if the underlying DatabaseAdapter supports a
close/closeAsync method, calls it, then sets db = undefined, initPromise =
undefined, indexedFor = [], and status.value = 'idle'; finally include this
method in the returned object alongside status, search, and init so callers can
explicitly release resources.

---

74-74: 💤 Low value

Type assertion bypasses collection key validation.

The cast col as T assumes that the string from toIndex is a valid collection key, but the type system doesn't verify this at runtime. While the function signature constrains the input to keyof PageCollections, the string manipulation path through resolveCollections() erases that type information.

This is acceptable given the constraints, but if stricter type safety is desired, consider maintaining typed arrays throughout:

function resolveCollections(): T[] {
  const val = toValue(collection)
  return (Array.isArray(val) ? val : [val]) as T[]
}

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/runtime/client.ts` at line 74, The cast `col as T` in the line calling
queryCollection(col as T) bypasses collection key validation; change
resolveCollections() (and any path using toIndex/from toValue) to preserve the
narrower T[] type so callers can pass a properly typed collection key instead of
asserting. Concretely, update resolveCollections() to return T[] (e.g., coerce
the result of toValue(collection) to T[] once and use that typed array wherever
queryCollection is called), and remove the inline `as T` cast in queryCollection
calls so the compiler enforces the correct keyof PageCollections type at call
sites.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes