@mikitasazan/notify 1.16.0 → 1.18.0

package/README.md

@@ -3,7 +3,7 @@
 Единая типизированная отправка Telegram-уведомлений: **форум на проект**,
 внутри вкладки «⚙️ Ops» (роботы) и «💬 Dev» (люди), один бот, семь типов
 событий. Заменяет 18 разных имён переменных и 4+ независимых реализации
-`jq | curl`, что были в playhub, arvent, game-publisher до 26.07.2026.
+`jq | curl`, что были в playhub, zabukai, game-publisher до 26.07.2026.
 
 **Почему форум на проект, а не один общий форум с темой на проект.** Второе
 пробовали первым — не работает: Telegram не умеет закрывать отдельную тему от
@@ -180,8 +180,8 @@ notify report --project playhub --json < payload.json   # весь объект
 
 | Отправитель | Старый тег (авто из русского названия) | Новый тег (из `--key`) |
 |---|---|---|
-| `arvent-eval-report.sh`, отчёт по эвалу | `#eval_качество_ответов_бота` | `#arvent_eval` |
-| `arvent-eval-report.sh`, файл диалогов | нет — шёл мимо пакета, сырым `sendDocument` Bot API | `#arvent_eval_dialogues` |
+| `zabukai-eval-report.sh`, отчёт по эвалу | `#eval_качество_ответов_бота` | `#zabukai_eval` |
+| `zabukai-eval-report.sh`, файл диалогов | нет — шёл мимо пакета, сырым `sendDocument` Bot API | `#zabukai_eval_dialogues` |
 | `daily-digest.sh`, дайджест задач (`job`) | `#дайджест_задач` | `#daily_digest` |
 | `daily-digest.sh`, дайджест задач (`report`) | `#дайджест_задач` (то же слово, другой тип-тег: `#report` вместо `#job`) | `#daily_digest` |
 | `daily-digest.sh`, отключённые Actions | `#github_actions_выключены` | `#actions_off` |
@@ -197,7 +197,7 @@ notify report --project playhub --json < payload.json   # весь объект
 - Автосоздания темы при первой отправке — сбой мог бы наплодить дублей;
   создание — явная команда `notify setup`.
 - Любых зависимостей, сборки, MarkdownV2, мультиязычности, троттла (троттл —
-  забота вызывающего кода, он есть в `arvent/web/src/server/alert.ts` и там
+  забота вызывающего кода, он есть в `zabukai/web/src/server/alert.ts` и там
   и остаётся: работает только внутри долгоживущего процесса, а CLI стартует
   заново на каждый вызов).
 

package/dist/cli.js

@@ -13,11 +13,11 @@
  *   notify deploy   --project playhub --status ok --commit "msg" [--commit-url "..."] --url "..."
  *   notify job      --project playhub --job "Game import" --status ok --stat "added=5" [--via vps] [--took "4m 12s"]
  *   notify report   --project playhub --title "Daily summary" --line "Games=1284"
- *   notify ci       --project arvent  --status fail --branch master
- *   notify pr       --project arvent  --action opened --number 142 --title "..."
- *   notify incident --project arvent  --title "Redis is unreachable" --detail "$ERR"
+ *   notify ci       --project zabukai  --status fail --branch master
+ *   notify pr       --project zabukai  --action opened --number 142 --title "..."
+ *   notify incident --project zabukai  --title "Redis is unreachable" --detail "$ERR"
  *   notify session  --project mac-config --action "burning the limit"   # DEPRECATED alias of incident
- *   notify file     --project arvent  --title "Full dialogues" --path ./out.txt [--filename name.txt]
+ *   notify file     --project zabukai  --title "Full dialogues" --path ./out.txt [--filename name.txt]
  *   notify <type> [--key stable-key]   # the task's key on the card's last line
  *   notify <type> --json < payload.json   # the whole event object on stdin
  *   notify setup <forum chat_id> <project key>   # create the tabs, see setup.ts

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' | 'arvent' | 'game-publisher' | 'vault' | 'mac-config' | 'alitools';
+export type Project = 'playhub' | 'one-q' | 'zabukai' | 'game-publisher' | 'vault' | 'mac-config' | 'alitools' | 'playgust';
 /**
  * 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
@@ -28,7 +28,7 @@ export type Project = 'playhub' | 'one-q' | 'arvent' | 'game-publisher' | 'vault
 /**
  * The common part of any event. `path` is a local file that travels WITH the
  * card: the card becomes a caption on the attachment. There has been no
- * separate `file` type since 25.08.2026 — an Arvent run used to send the
+ * separate `file` type since 25.08.2026 — an Zabukai run used to send the
  * verdict and the log as two cards about one piece of news.
  */
 type Keyed = {

package/dist/render.js

@@ -168,7 +168,7 @@ const fieldLink = (label, url, text) => {
         return null;
     }
     // `firstLine` here for the same reason `field` has it: the linked case used to
-    // skip it, so a multi-line value (arvent's two-line `commit`) became two-line
+    // skip it, so a multi-line value (zabukai's two-line `commit`) became two-line
     // LINK TEXT instead of one identifier.
     return url
         ? `<b>${esc(cap(label))}:</b> <a href="${esc(url)}">${esc(firstLine(text))}</a>`
@@ -1048,7 +1048,7 @@ const RENDERERS = {
 };
 // The tag at the top of the card AND the parser's machine key are ONE AND THE
 // SAME value (the owner's decision, 20.08.2026): they used to be two separate
-// representations of one fact (a hyphenated `#ci-arvent` at the bottom, tags
+// representations of one fact (a hyphenated `#ci-zabukai` at the bottom, tags
 // typed by hand at the top), and that read as duplication. The separator is
 // an underscore, not a hyphen: a hyphen splits a Telegram hashtag in the
 // middle of a word (`#mac-config` links only as `#mac`), and the tag MUST be

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 `playgust`). 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

@@ -4,7 +4,7 @@ export const ROUTES = {
     // 27.07.2026, and Telegram removes a topic's messages along with it. A
     // recreated topic gets a NEW id — a topic's id is the id of its first
     // message, it is never reused.
-    arvent: { chat: '-1004299939100', ops: 22, dev: 23 },
+    zabukai: { chat: '-1004299939100', ops: 22, dev: 23 },
     playhub: { chat: '-1004418379613', ops: 3, dev: 4 },
     'game-publisher': { chat: '-1004292453693', ops: 3, dev: 4 },
     'one-q': { chat: '-1004466909784', ops: 3, dev: 4 },
@@ -20,7 +20,11 @@ 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 «Playgust · Ops».
+    playgust: { chat: '-1004334723487' }
 };
 /**
  * Where an event goes. Everything goes to its own project's "Ops" tab; a
@@ -42,5 +46,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.16.0",
+  "version": "1.18.0",
   "description": "Единая типизированная отправка Telegram-уведомлений (форум-темы, маршрутизация, ретраи) для всех проектов",
   "type": "module",
   "license": "MIT",