@nettee/beacon 0.3.2 → 0.3.4

package/README.md

@@ -111,16 +111,16 @@ per-Run directories with mode `0700` when Pi starts.
 
 Configuration is strict: unknown YAML/JSON fields, YAML aliases or warnings, missing paths, duplicate Schedule IDs, invalid timezones/cron expressions, a missing complete `persona.md` + `task.md` pair, escaped Profile markdown, permissive secret or runtime-environment permissions, missing Profile credentials, and unknown Feishu channel names all fail startup. Beacon validates all Profiles before opening a Feishu connection.
 
-Feishu delivery destinations are registered globally in `~/.beacon/channels.yaml`
-(beside `config.yaml`), then referenced by semantic `name` from each Profile:
+Group notify destinations are registered globally in `~/.beacon/channels.yaml`
+(beside `config.yaml`), then referenced by semantic `name` from each Profile's
+`notify`. Admin DMs are **not** channel entries: each Profile keeps a raw
+`admin.chat_id` (one bot×person private chat; putting those in the registry
+would explode as bots and people grow).
 
 ```yaml
-# ~/.beacon/channels.yaml
+# ~/.beacon/channels.yaml — group chats only
 version: 1
 channels:
-  - name: admin-dm
-    description: Example admin direct chat
-    chat_id: REPLACE_WITH_ADMIN_DIRECT_CHAT_ID
   - name: weekday-brief-group
     description: Example weekday brief notify group
     chat_id: REPLACE_WITH_GROUP_CHAT_ID
@@ -129,7 +129,7 @@ channels:
 ```yaml
 # profile.yaml destinations
 admin:
-  name: admin-dm
+  chat_id: REPLACE_WITH_ADMIN_DIRECT_CHAT_ID
 schedules:
   - id: weekday-brief
     cron: "0 9 * * 1-5"
@@ -140,11 +140,12 @@ schedules:
 ```
 
 Each channel has `name` (stable slug), `description` (human-readable Chinese or
-English label), and `chat_id` (the real Feishu chat id). Profile destinations
-bind `name` and may optionally override `description` for local readability;
+English label), and `chat_id` (the real Feishu group chat id). Profile `notify`
+binds `name` and may optionally override `description` for local readability;
 Beacon resolves `name` → `chat_id` at load time. Unknown names fail startup.
-Legacy `chat_id` directly under `admin` / `notify` is still accepted so existing
-hosts can migrate one Profile at a time; new Profiles should use `name`.
+`admin` must use bare `chat_id` (not a channel `name`). Legacy bare `chat_id`
+under `notify` still loads so hosts can migrate one Profile at a time; new
+`notify` entries should use `name`.
 
 Each Schedule uses a five-field cron expression and an IANA timezone. Profile
 `admin` is the private chat used for schedule `reply_text` /
@@ -216,7 +217,7 @@ Subscribe in the desired `profile.yaml`:
 
 ```yaml
 admin:
-  name: admin-dm
+  chat_id: REPLACE_WITH_ADMIN_DIRECT_CHAT_ID
 listener:
   sources:
     - https://deploy.example.com/production

package/dist/config/profile.js

@@ -10,6 +10,11 @@ const profileIdPattern = /^[a-z0-9](?:[a-z0-9_-]{0,62})$/;
 export const profilePersonaFile = "persona.md";
 export const profileTaskFile = "task.md";
 export const workspaceProfileDirectoryName = ".beacon-profile";
+/** Admin DM: raw Feishu chat_id only (bot×person DMs are not channel registry entries). */
+const adminDestinationSchema = z
+    .object({ chat_id: z.string().trim().min(1) })
+    .strict();
+/** Group notify: prefer semantic name from ~/.beacon/channels.yaml; bare chat_id still loads. */
 const namedDestinationSchema = z
     .object({
     name: z
@@ -21,7 +26,7 @@ const namedDestinationSchema = z
 const legacyChatDestinationSchema = z
     .object({ chat_id: z.string().trim().min(1) })
     .strict();
-const destinationSchema = z.union([
+const notifyDestinationSchema = z.union([
     namedDestinationSchema,
     legacyChatDestinationSchema,
 ]);
@@ -47,7 +52,7 @@ const scheduleSchema = z
         }
     }, "Schedule timezone must be a valid IANA timezone"),
     input: z.string().trim().min(1),
-    notify: destinationSchema.optional(),
+    notify: notifyDestinationSchema.optional(),
 })
     .strict();
 const profileDocumentSchema = z
@@ -60,13 +65,13 @@ const profileDocumentSchema = z
         id: z.string().min(1),
     })
         .strict(),
-    admin: destinationSchema.optional(),
+    admin: adminDestinationSchema.optional(),
     schedules: z.array(scheduleSchema).default([]),
     listener: z
         .object({
         sources: z.array(eventSourceSchema).min(1),
         types: z.array(z.string().min(1)).min(1),
-        notify: destinationSchema.optional(),
+        notify: notifyDestinationSchema.optional(),
     })
         .strict()
         .optional(),
@@ -163,7 +168,7 @@ async function loadPersonaAndTask(profileId, workspace, profileDirectory) {
     ];
     throw new Error(`Profile ${profileId} has no complete ${profilePersonaFile} + ${profileTaskFile} pair. Missing: ${missing.join(", ")}`);
 }
-function resolveDestination(destination, channels, channelsPath) {
+function resolveNotifyDestination(destination, channels, channelsPath) {
     if ("chat_id" in destination) {
         return { chatId: destination.chat_id };
     }
@@ -202,9 +207,7 @@ export async function loadProfile(profileId, profilesDirectory = join(homedir(),
     if (config.listener && !config.admin) {
         throw new Error(`Profile ${profileId} with listener must declare admin`);
     }
-    const admin = config.admin
-        ? resolveDestination(config.admin, channels, channelsPath)
-        : undefined;
+    const admin = config.admin ? { chatId: config.admin.chat_id } : undefined;
     const canonicalProfileDirectory = await realpath(profileDirectory);
     const workspace = isAbsolute(config.workspace)
         ? config.workspace
@@ -238,7 +241,7 @@ export async function loadProfile(profileId, profilesDirectory = join(homedir(),
                     types: config.listener.types,
                     ...(config.listener.notify
                         ? {
-                            notify: resolveDestination(config.listener.notify, channels, channelsPath),
+                            notify: resolveNotifyDestination(config.listener.notify, channels, channelsPath),
                         }
                         : {}),
                 },
@@ -251,7 +254,7 @@ export async function loadProfile(profileId, profilesDirectory = join(homedir(),
             input: schedule.input,
             ...(schedule.notify
                 ? {
-                    notify: resolveDestination(schedule.notify, channels, channelsPath),
+                    notify: resolveNotifyDestination(schedule.notify, channels, channelsPath),
                 }
                 : {}),
         })),

package/examples/channels.yaml.example

@@ -1,8 +1,7 @@
 version: 1
 channels:
-  - name: admin-dm
-    description: Example admin direct chat
-    chat_id: REPLACE_WITH_ADMIN_DIRECT_CHAT_ID
+  # Group chats only (notify_card). Admin DMs stay on profile admin.chat_id —
+  # one bot×person pair each, so they do not belong in this registry.
   - name: weekday-brief-group
     description: Example weekday brief notify group
     chat_id: REPLACE_WITH_GROUP_CHAT_ID

package/examples/profiles/example/profile.yaml

@@ -4,7 +4,7 @@ model:
   provider: REPLACE_WITH_PI_PROVIDER
   id: REPLACE_WITH_PI_MODEL
 admin:
-  name: admin-dm
+  chat_id: REPLACE_WITH_ADMIN_DIRECT_CHAT_ID
 schedules:
   - id: weekday-brief
     cron: "0 9 * * 1-5"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nettee/beacon",
-  "version": "0.3.2",
+  "version": "0.3.4",
   "description": "A single-host bridge from messaging and schedules to isolated agent runs",
   "license": "Apache-2.0",
   "repository": {