nav/Fabric.Backend.Guild

Go to file

hzhang 985b06a886 feat(guild): system-key bypass + announce-only system path + gen CLI

Three coupled changes that let Dialectic.Backend (and future system
broadcasters) post to announce channels without needing a Fabric user
bearer.

1. ApiKeyGuard: when x-fabric-system-key matches
   FABRIC_BACKEND_GUILD_SYSTEM_API_KEY env, skip the Bearer requirement
   and set req.isSystem=true. Pre-Bearer system bypass; no per-user
   session token needed. Empty env -> bypass disabled (closed by default).

2. messaging.controller POST /channels/:id/messages: when req.isSystem,
   skip assertParticipant + fetch channel directly. Enforce xType=announce
   (system key only writes to announce channels - never to regular chats).
   Persist with sentinel author 00000000-0000-0000-0000-000000000000.
   Emit message.created + realtime.emitMessageCreated with xType=announce
   so the Phase 1 busy-discard logic kicks in for recipients.

3. New cli: src/cli/gen-system-api-key.ts. Generates a random 32-byte
   hex key (same shape as agent + admin keys) and prints it. Does NOT
   store - operator pastes into compose env and restarts guild. Pattern
   mirrors the existing print-commands-sync-key.ts.

Removes the need for a FABRIC_BOT_BEARER_TOKEN concept entirely - the
system key alone is sufficient. announce-channel posts by regular
authenticated users (who happen to know channel id but no system key)
are now 403 announce_system_only.

2026-05-23 17:49:53 +01:00

src

feat(guild): system-key bypass + announce-only system path + gen CLI

2026-05-23 17:49:53 +01:00

.env.example

refactor(guild): prefix environment variables with FABRIC_BACKEND_GUILD

2026-05-13 12:58:32 +00:00

.gitignore

feat: bootstrap from Fabric monorepo

2026-05-13 07:06:03 +00:00

Dockerfile

feat: bootstrap from Fabric monorepo

2026-05-13 07:06:03 +00:00

eslint.config.mjs

feat: bootstrap from Fabric monorepo

2026-05-13 07:06:03 +00:00

package-lock.json

feat: bootstrap from Fabric monorepo

2026-05-13 07:06:03 +00:00

package.json

feat(ops): CLI to print the commands-sync key (Guild C-2)

2026-05-16 18:28:23 +01:00

README.md

docs: slash-command registry section

2026-05-16 16:15:04 +01:00

tsconfig.build.json

feat: bootstrap from Fabric monorepo

2026-05-13 07:06:03 +00:00

tsconfig.json

refactor: migrate to ES modules

2026-05-15 18:47:36 +01:00

vitest.config.ts

feat: bootstrap from Fabric monorepo

2026-05-13 07:06:03 +00:00

README.md

Fabric.Backend.Guild

A guild node for Fabric (NestJS, ES modules, MySQL/TypeORM, socket.io). Default port 7002, global prefix /api. Many independent guild nodes can run; each registers with Fabric.Backend.Center and introspects the user/guild tokens Center issues.

Responsibilities

Guilds / channels / messaging — per-channel seq ordering, edit window, soft delete, reply, <@id> mentions (backtick-aware) plus <@user.name:NAME> → <@userId> translation via Center.
Channel x_type (required on create): general, work, report, discuss, triage, custom. Plus isPublic and closed (closed → history readable, posting returns 409).
wake_mapping — explicit wake list for triage (on-duty) and custom (listeners) channels.
Per-recipient wakeup — message.created is emitted per socket with its own wakeup flag (author=false; general→all; report→none; triage/custom→wake_mapping; discuss/work→the current speaker only). This is push-only metadata for the OpenClaw plugin; UIs ignore it.
discuss/work turn engine (channel_turn_state): speaking order and a disjoint bypass list (bypass members aren't woken unless @-mentioned); activation from idle, queue-jump, cross-round /no-reply pause, /force-proceed, end-of-round shuffle, guild /ack, and a mention sub-frame stack with a 5-level nesting cap (root + 4). moveToBypass mid-rotation.
Files — POST /files (multipart, configurable max size, default 100 MB), GET /files/:id (Bearer or ?access_token= for browser <img>/<a>), automatic retention sweep (default 7 days). Messages carry attachments[].
Channel canvas — one pinned document per channel (md/html/text), re-share replaces, only the original sharer may update/remove; emits canvas.updated / canvas.removed.
Slash-command registry — guild-global catalog: PUT /api/commands (the OpenClaw plugin syncs OpenClaw's native-command specs here), GET /api/commands (frontend / autocomplete). Stored verbatim; execution is unchanged (a /<cmd> message flows normally to the plugin → OpenClaw command system; only /no-reply,/force-proceed are server-intercepted).
Realtime — socket.io /realtime; join_channel/leave_channel, message.created/updated/deleted, canvas.*, presence, typing.

Required env (hard-checked at startup)

FABRIC_BACKEND_GUILD_CENTER_BASE_URL
FABRIC_BACKEND_GUILD_CENTER_API_KEY
FABRIC_BACKEND_GUILD_NODE_ID

Missing any of these aborts startup.

Other env

FABRIC_BACKEND_GUILD_PORT (default 7002)
FABRIC_BACKEND_GUILD_DB_*, FABRIC_BACKEND_GUILD_DB_SYNC
FABRIC_BACKEND_GUILD_FILE_DIR (storage root), FABRIC_BACKEND_GUILD_FILE_MAX_BYTES (default 100 MB), FABRIC_BACKEND_GUILD_FILE_TTL_DAYS (default 7)
FABRIC_BACKEND_GUILD_CORS_ORIGINS (empty = allow all; null origin — file:// desktop — is always allowed)

Run

npm install
npm run build && npm start          # or: npm run start:dev

Usually run via the root docker-compose.local.yml (backend-guild1 test-guild1 :7002, backend-guild2 test-guild2 :7003). Schema is auto-managed (DB_SYNC). ES modules (NodeNext).