refactor(data-access): move tag/saved-reply/custom-field logic onto repository pattern

Introduces dedicated tag and saved-reply repositories under
packages/database/src/repositories, hashes workspace tokens
(new tokenHash column + index), and centralizes the owner
quota/trial gate into authorize-workspace-access.ts shared by
server actions and oRPC auth. Relocates the affected business-
logic tests from apps/builder/__tests__ into package-level
__tests__ per repository convention.

Author: realcodesiman

.agents/skills/drizzle-database/SKILL.md

@@ -210,6 +210,47 @@ import { myModel } from "@chatbotx.io/database/schema"
 const item = await findOrFail({ table: myModel, where: { id } })
 ```
 
+## Repository Convention
+
+Repositories live in `packages/database/src/repositories/<name>/` and are **pure data access**: they receive params, run Drizzle queries, return rows. No caching, no business rules, no audit — those belong to the service in `packages/business`.
+
+**Shape (mandatory for new repositories; migrate old ones when touched):**
+
+```
+packages/database/src/repositories/<name>/
+  repository.ts   → class <Name>Repository { ... } + export const <name>Repository = new <Name>Repository()
+  index.ts        → export { <name>Repository } from "./repository" + exported param/row types
+```
+
+```typescript
+// packages/database/src/repositories/tag/repository.ts
+import { type DatabaseClient, db } from "../../client"
+import { tagModel } from "../../schema"
+
+export type ListTagsParams = { workspaceId: string; page?: number | null }
+
+class TagRepository {
+  async list(params: ListTagsParams, tx: DatabaseClient = db) {
+    return await tx.query.tagModel.findMany({ where: { workspaceId: params.workspaceId } })
+  }
+}
+
+export const tagRepository = new TagRepository()
+```
+
+Rules:
+
+- **Class + singleton**, not object literals and not loose exported functions. Uniform shape means uniform mocking (`vi.spyOn(tagRepository, "list")`) and room for a shared base (tx injection, tenant scoping, sharding) without rewriting callers.
+- **Stateless.** No fields other than what a constructor injects; never hold a cache or request state inside a repository.
+- **Method names are short verbs without the resource name**: `list`, `findById`, `findByKey`, `create`, `update`, `delete`, `count`, `incrementX`. `tagRepository.list(...)`, never `tagRepository.listTags(...)`.
+- **Accept `tx: DatabaseClient = db` as the last parameter** so the same method works inside and outside `db.transaction()`.
+- **Import internally with relative paths** (`../../client`, `../../schema`, `../../utils`) — never `@chatbotx.io/database/*` from inside the package.
+- **Register once** in `packages/database/src/repositories/index.ts` with `export * from "./<name>"`.
+
+Cache placement: `withCache` / `invalidateCacheTags` (from `@chatbotx.io/redis`) are called in the **service**, wrapping the repository call. The service is the only layer that knows every write path and therefore the only layer that can invalidate correctly.
+
+Create a repository only when the query is reused across services, is complex enough to deserve isolated tests, or needs to swap its data source (e.g. sharding — see `message/`). A service with a handful of one-line queries may call `db` directly; do not add a repository as pure indirection.
+
 ## Soft-delete convention
 
 `Workspace.scheduledDeletionAt` is the repository's soft-delete convention:

.agents/skills/orpc-api/SKILL.md

@@ -12,15 +12,16 @@ description: >-
 
 - **oRPC** serves both **RPC** (`/rpc`) and **OpenAPI** (`/api`) endpoints
 - Base context: `{ headers, user?, workspace? }`
-- Two auth stacks: `authorizedAPI` (session) and `workspaceTokenAuthAPI` (header token)
+- Three auth stacks: `authorizedAPI` (session), `workspaceTokenAuthAPI` (workspace bearer/query token), and `channelApiTokenAPI` (per-inbox channel API bearer token)
 - Routers are plain objects of procedures, composed via object spreading
 
 ## Auth Stacks
 
 Defined in `apps/builder/src/orpc.ts`:
 
 - **`authorizedAPI`**: `base` → error mapping → `authMiddleware` (session/cookie auth)
-- **`workspaceTokenAuthAPI`**: `base` → error mapping → `workspaceTokenAuthMidddleware` (Authorization: Bearer header)
+- **`workspaceTokenAuthAPI`**: `base` → error mapping → `workspaceTokenAuthMidddleware` (Authorization: Bearer header, with a legacy `?token=` query fallback and a deprecated plaintext-token dual-read; see `middlewares/workspace-token-auth.ts`)
+- **`channelApiTokenAPI`**: `base` → error mapping → `channelApiTokenAuthMidddleware` (Authorization: Bearer header only — no query fallback; token is looked up by hash, never plaintext; scoped to a single inbox, not a whole workspace; see `middlewares/channel-api-token-auth.ts`)
 
 Workspace-scoped procedures add `workspaceAuthorizedMidddleware` per-procedure.
 

.agents/skills/public-api-tooling/SKILL.md

@@ -168,7 +168,7 @@ NEXT_PUBLIC_BUILDER_URL=http://localhost:3123
 SCHEDULER_BUCKET_RANGE=0-255
 
 # Increase Node.js heap for large workloads. Set per-process, not globally.
-# NODE_OPTIONS="--max_old_space_size=4096"
+# NODE_OPTIONS="--max_old_space_size=8192"
 
 # ─────────────────────────────────────────────
 # Logging

.env.example

@@ -23,7 +23,7 @@ This file summarizes how **ChatbotX** (this repository) is structured and how to
 | `apps/cli`        | Command-line client (`chatbotx-cli`).                                                                                   |
 | `apps/mcp-server` | MCP server exposing public API surfaces.                                                                                |
 | `apps/javascript-executor` | Internal HTTP service that executes flow-step JavaScript in isolated-vm.                                      |
-| `packages/*`      | Shared libraries: `database` (Drizzle + PostgreSQL), `ui`, `public-apis`, `sdk`, `worker-config`, `ai`, etc.            |
+| `packages/*`      | Shared libraries: `database` (Drizzle + PostgreSQL), `ui`, `sdk`, `worker-config`, `ai`, etc.                           |
 | `integrations/*`  | Channel and vendor integrations (WhatsApp, Messenger, Telegram, Zalo, TikTok, webchat, SMTP, OpenAI, Google Sheets, …). |
 
 ## Stack (high level)