@mikitasazan/notify 1.17.0 → 1.19.0

package/dist/events.d.ts

@@ -10,7 +10,7 @@
  *   - required fields are never added — only a new event type.
  * That keeps old caller code and a new package compatible both ways.
  */
-export type Project = 'playhub' | 'one-q' | 'zabukai' | 'game-publisher' | 'vault' | 'mac-config' | 'alitools';
+export type Project = 'playhub' | 'one-q' | 'zabukai' | 'game-publisher' | 'vault' | 'mac-config' | 'alitools' | 'htmlg';
 /**
  * A stable machine key for the task — the instance tag on the FIRST line of
  * every card, shaped as `#key` (with no project name: the card already sits

package/dist/routes.d.ts

@@ -3,8 +3,13 @@
  * touches: add a row to `ROUTES` — no new bot, no new secret, no edits in
  * the projects themselves.
  *
- * The scheme: ONE FORUM PER PROJECT, with an "⚙️ Ops" tab (robot
- * notifications) and a "💬 Dev" tab (people's live chat) inside it.
+ * The scheme: ONE CHAT PER PROJECT. A project with a team is a forum
+ * supergroup with an "⚙️ Ops" tab (robot notifications) and a "💬 Dev" tab
+ * (people's live chat). A project the owner runs alone is a plain
+ * supergroup without topics — the robots post straight into it and there
+ * is nobody to talk to in a Dev tab (owner's rule of 2026-09-05; the first
+ * such chat is `htmlg`). A plain chat has no `ops` number: the message
+ * goes to the chat itself.
  *
  * Why not one shared forum with a topic per project — that was the first
  * version, and it turned out to be a mistake: Telegram cannot hide one
@@ -23,10 +28,13 @@
  */
 import type { NotifyEvent, Project } from './events.ts';
 type Forum = {
-    /** The id of the project's forum supergroup. */
+    /** The id of the project's supergroup (forum or plain). */
     chat: string;
-    /** The "⚙️ Ops" tab — robots write here. */
-    ops: number;
+    /**
+     * The "⚙️ Ops" tab — robots write here. Absent for a plain chat without
+     * topics (a solo project): the message then goes to the chat itself.
+     */
+    ops?: number;
     /**
      * The "💬 Dev" tab — people. The bot does not write here; the field is
      * kept for completeness. Optional: an infrastructure forum has no people

package/dist/routes.js

@@ -20,7 +20,12 @@ export const ROUTES = {
     // publish delivered" (ali98x-sentry). No `dev` — the project's team lives
     // in other systems, there are no people here. Until 18.08.2026 reports
     // were getting lost on "unknown project" for weeks.
-    alitools: { chat: '-1003904331479', ops: 3 }
+    alitools: { chat: '-1003904331479', ops: 3 },
+    // Solo project, plain supergroup without topics (owner's rule 05.09.2026):
+    // no `ops`, no `dev`, the bot posts into the chat itself. Created
+    // 05.09.2026 as «HTMLG · Ops» (HTMLG is the HTML5-games business; the brand
+    // and domain of its portal may change, the project name does not).
+    htmlg: { chat: '-1004334723487' }
 };
 /**
  * Where an event goes. Everything goes to its own project's "Ops" tab; a
@@ -42,5 +47,5 @@ export const targets = (e) => {
         console.error(`[notify] unknown project "${e.project}" — known: ${Object.keys(ROUTES).join(', ')}`);
         return [];
     }
-    return [{ chat: forum.chat, thread: forum.ops, silent: severity(e) === 'info' }];
+    return [{ chat: forum.chat, ...(forum.ops === undefined ? {} : { thread: forum.ops }), silent: severity(e) === 'info' }];
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mikitasazan/notify",
-  "version": "1.17.0",
+  "version": "1.19.0",
   "description": "Единая типизированная отправка Telegram-уведомлений (форум-темы, маршрутизация, ретраи) для всех проектов",
   "type": "module",
   "license": "MIT",