@mikitasazan/notify 1.24.0 → 1.25.0

package/dist/routes.d.ts

@@ -4,12 +4,12 @@
  * the projects themselves.
  *
  * 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.
+ * supergroup with an "Ops" tab (robot notifications, native 🤖 topic icon)
+ * 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
@@ -31,10 +31,11 @@ type Forum = {
     /** The id of the project's supergroup (forum or plain). */
     chat: string;
     /**
-     * The chat's own title, and ONLY for a chat shared by several repositories
-     * of one product. A repository is a project row here, but the chat belongs
-     * to the product above them, so its name cannot be derived from any single
-     * row — every row sharing a chat carries the same `title`. Left out
+     * The chat's own title, wherever it cannot be derived from the project key:
+     * a product of several repositories (every row sharing that chat carries
+     * the same `title`), and a team forum whose product name is prettier than
+     * its repository key (owner's rule of 2026-09-10: a FORUM wears the
+     * product's own name; a solo chat wears the repository's). Left out
      * everywhere else, where `chatTitle()` derives the name from the project.
      */
     title?: string;
@@ -56,8 +57,9 @@ export declare const ROUTES: Record<Project, Forum>;
  * A solo project's chat is «<Name> · Ops»; a team forum is just the name — the
  * forum already carries its own «Ops»/«Dev» tabs, so the chat's own title
  * does not need to repeat the word. A chat shared by several repositories of
- * one product carries the product's name in `title`, and every row sharing
- * that chat repeats it, so any of them answers with the same title. The real
+ * one product, or a forum whose product name differs from the repo key,
+ * carries the product's name in `title`, and every row sharing that chat
+ * repeats it, so any of them answers with the same title. The real
  * Telegram chat title and this function must agree: the avatar scripts and the
  * name-drift check both read it through `notify routes --json`, not by asking
  * Telegram.

package/dist/routes.js

@@ -31,15 +31,18 @@ export const ROUTES = {
     // runs it alone.
     '2roles': { chat: '-1004314188744' },
     // Created 09.09.2026 by create-ops-chat.py as «Market Lens»: the owner and
-    // Semyon, so a forum; the tab numbers come from `notify setup`.
-    'market-lens': { chat: '-1004489147617', ops: 4, dev: 5 }
+    // Semyon, so a forum; the tab numbers come from `notify setup`. A forum
+    // wears the product's own name even when it is one repository (owner's
+    // rule of 2026-09-10) — hence `title`, like Zabukai above.
+    'market-lens': { chat: '-1004489147617', title: 'Market Lens', ops: 4, dev: 5 }
 };
 /**
  * A solo project's chat is «<Name> · Ops»; a team forum is just the name — the
  * forum already carries its own «Ops»/«Dev» tabs, so the chat's own title
  * does not need to repeat the word. A chat shared by several repositories of
- * one product carries the product's name in `title`, and every row sharing
- * that chat repeats it, so any of them answers with the same title. The real
+ * one product, or a forum whose product name differs from the repo key,
+ * carries the product's name in `title`, and every row sharing that chat
+ * repeats it, so any of them answers with the same title. The real
  * Telegram chat title and this function must agree: the avatar scripts and the
  * name-drift check both read it through `notify routes --json`, not by asking
  * Telegram.

package/dist/setup.js

@@ -1,24 +1,42 @@
 /**
- * `notify setup "<Project name>"` creates the "⚙️ Ops" and "💬 Dev" tabs in a
- * forum that already exists, and prints the ready line for `ROUTES`.
+ * `notify setup <forum chat_id> <project key>` creates the "Ops" and "Dev"
+ * tabs in a forum that already exists, and prints the ready line for `ROUTES`.
+ *
+ * Tab shape (the standard tests/check-telegram-shape.py enforces): plain
+ * titles with a NATIVE topic icon, never an emoji in the title text — Ops
+ * carries 🤖 (robots post there), Dev carries 💬 (people talk there). The
+ * icon ids below are documents of Telegram's topic-icon sticker set,
+ * resolved live on 2026-09-10; ⚙️ is NOT in that set, which is why the
+ * robot glyph is 🤖.
+ *
+ * A product of SEVERAL repositories shares one forum, one Ops tab PER
+ * repository (a card belongs to the repo it came from) and ONE Dev tab.
+ * The Bot API cannot list a forum's topics, so the shape is decided from
+ * `ROUTES` itself: peers are rows that already point at this chat.
  *
  * The bot cannot create the forum supergroup itself — Telegram only allows a
- * real account to do that. So the order for a new project is:
+ * real account to do that. So the order for a new project is
+ * (mac-config's tg-forums skill, scripts/create-ops-chat.py --forum does all
+ * of step 1):
  *   1. create a group in Telegram, turn on "Topics" in it, add
  *      @mikita_ops_bot as an admin with the "Manage topics" right;
- *   2. run `notify setup <chat_id>` — it creates both tabs and prints the line;
+ *   2. run `notify setup <chat_id> <project key>` — it creates the tabs and
+ *      prints the line;
  *   3. paste the line into `src/routes.ts`.
- *
- * Step 1 happens once per project and takes half a minute. Steps 2 and 3 are
- * mechanical.
  */
+import { ROUTES } from "./routes.js";
 const log = (msg) => console.error(`[notify] ${msg}`);
-const createTopic = async (token, chat, name, color) => {
+// Documents of Telegram's topic-icon set (InputStickerSetEmojiDefaultTopicIcons):
+// 🤖 for Ops, 💬 for Dev. A wrong id here writes a dead icon into every new
+// forum — tests/check-telegram-shape.py catches a dropped icon live.
+const OPS_ICON_ID = '5309832892262654231'; // 🤖
+const DEV_ICON_ID = '5417915203100613993'; // 💬
+const createTopic = async (token, chat, name, iconId, color) => {
     try {
         const res = await fetch(`https://api.telegram.org/bot${token}/createForumTopic`, {
             method: 'POST',
             headers: { 'Content-Type': 'application/json' },
-            body: JSON.stringify({ chat_id: chat, name, icon_color: color }),
+            body: JSON.stringify({ chat_id: chat, name, icon_color: color, icon_custom_emoji_id: iconId }),
             signal: AbortSignal.timeout(10_000)
         });
         const body = (await res.json());
@@ -40,21 +58,35 @@ export const setupTopic = async (chatId, projectKey) => {
         log('no OPS_BOT_TOKEN — cannot create the tabs');
         return;
     }
-    const ops = await createTopic(token, chatId, '⚙️ Ops', 9367192);
-    const dev = await createTopic(token, chatId, '💬 Dev', 7322096);
+    // The Bot API cannot enumerate topics, so the forum's shape is read from
+    // ROUTES: a row already pointing here is a peer repository of the same
+    // product.
+    const existing = ROUTES[projectKey];
+    if (existing && existing.chat === chatId && existing.ops !== undefined) {
+        log(`${projectKey} is already in ROUTES with ops=${existing.ops} — nothing to create`);
+        return;
+    }
+    const peers = Object.entries(ROUTES).filter(([key, row]) => key !== projectKey && row.chat === chatId);
+    // A second repository of the same product gets its name on its own Ops tab;
+    // the product's FIRST tab is plain "Ops" (rename it when a second repo
+    // joins — tests/check-telegram-shape.py goes red until it is done).
+    const opsTitle = peers.length > 0 ? `Ops · ${projectKey}` : 'Ops';
+    const sharedDev = peers.map(([, row]) => row.dev).find((id) => id !== undefined);
+    const ops = await createTopic(token, chatId, opsTitle, OPS_ICON_ID, 9367192);
+    const dev = sharedDev ?? (await createTopic(token, chatId, 'Dev', DEV_ICON_ID, 7322096));
     // Partial success: if only Ops was created, print it. Otherwise running the
     // command again would create A DIFFERENT Ops topic, and the old id would be lost.
     if (ops === null) {
         log('Ops was not created — check: is the bot a group admin with "Manage topics", and are topics on?');
         return;
     }
-    if (dev === null) {
+    if (dev === null || dev === undefined) {
         log(`Ops created (id=${ops}), Dev was not — add Dev by hand or run again, and keep ops=${ops}`);
         log('add to src/routes.ts (fill dev in afterwards):');
         log(`  ${JSON.stringify(projectKey)}: { chat: '${chatId}', ops: ${ops}, dev: <fill in> },`);
         return;
     }
-    log(`tabs created: Ops=${ops}, Dev=${dev}`);
+    log(`tabs created: Ops="${opsTitle}" (${ops}), Dev (${dev})${sharedDev ? ' [shared with a peer repo]' : ''}`);
     log('add to src/routes.ts:');
     log(`  ${JSON.stringify(projectKey)}: { chat: '${chatId}', ops: ${ops}, dev: ${dev} },`);
 };

package/package.json

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