@mikitasazan/notify 1.19.0 → 1.21.0

package/README.md

@@ -91,8 +91,10 @@ notify report --project playhub --json < payload.json   # весь объект
 Скобка у слова типа говорит одним словом, чем кончилось: `Deploy (OK)`,
 `CI (Fail)`, `Job (Off)`, `Job (Silent)`, `Issue (Assigned)`, `PR (Merged)`.
 Она стоит там, где у типа исходов больше одного. У `incident` состояние одно,
-поэтому его скобка называет МЕСТО, где горит: `Incident (Vault)`,
-`Incident (Session)` — слово из `--scope`, без него имя проекта. У `report`
+поэтому его скобка называет МЕСТО, где горит: `Incident (vault)`,
+`Incident (Session)` — слово из `--scope`, без него человеческое имя проекта
+(таблица `DISPLAY` в `src/events.ts`; `vault` и `mac-config` — нарочно со
+строчной, это машина и хранилище, а не бренды). У `report`
 исхода нет вовсе, и скобку занимает день: `Report (2026-08-23 / 2026-08-22)`.
 
 У `job` есть ещё два необязательных флага: `--via` — где задача крутилась
@@ -147,8 +149,9 @@ notify report --project playhub --json < payload.json   # весь объект
    живому аккаунту, ботом это не сделать.
 2. `notify setup <chat_id> maphub` — заведёт вкладки «⚙️ Ops» и «💬 Dev» и
    напечатает готовую строку.
-3. Вставить строку в `src/routes.ts` (и значение в тип `Project` в
-   `src/events.ts`), выпустить пакет.
+3. Вставить строку в `src/routes.ts`, значение в тип `Project` и человеческое
+   имя в `DISPLAY` в `src/events.ts` (тест держит их в одном списке), выпустить
+   пакет.
 4. В репозиторий проекта — трёхстрочный `.github/workflows/notify.yml`,
    вызывающий `mikitasazan/notify/.github/workflows/ops-notify.yml@v1`:
    CI, деплой, PR и задачи начинают приходить сами.

package/dist/cli.js

@@ -23,11 +23,12 @@
  *   notify setup <forum chat_id> <project key>   # create the tabs, see setup.ts
  */
 import { readFileSync } from 'node:fs';
+import { DISPLAY } from "./events.js";
 import { KNOWN_FLAGS } from "./cli-flags.js";
 import { render, sessionTitle } from "./render.js";
 import { lintCard } from "./lint.js";
 import { notify } from "./send.js";
-import { ROUTES } from "./routes.js";
+import { ROUTES, chatTitle } from "./routes.js";
 import { setupTopic } from "./setup.js";
 const log = (msg) => console.error(`[notify] ${msg}`);
 /**
@@ -58,7 +59,15 @@ if (command === 'lint-text') {
     process.exit(0);
 }
 if (command === 'routes') {
-    process.stdout.write(`${JSON.stringify(ROUTES, null, 2)}\n`);
+    // `display`/`title` ride alongside the routing facts, not instead of them —
+    // every existing field stays. The avatar scripts and the name-drift check
+    // read `title` here rather than asking Telegram, so it must be `chatTitle()`
+    // verbatim, not a second guess at the same name.
+    const rows = Object.fromEntries(Object.keys(ROUTES).map((p) => [
+        p,
+        { ...ROUTES[p], display: DISPLAY[p], title: chatTitle(p) }
+    ]));
+    process.stdout.write(`${JSON.stringify(rows, null, 2)}\n`);
     process.exit(0);
 }
 if (command === 'setup') {

package/dist/events.d.ts

@@ -10,7 +10,22 @@
  *   - 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' | 'htmlg';
+export type Project = 'playhub' | 'one-q' | 'zabukai' | 'game-publisher' | 'vault' | 'mac-config' | 'alitools' | 'htmlg' | '2roles';
+/**
+ * The human name of a project, written exactly as the owner writes it.
+ * Source of truth is the project card index (`project-index` skill,
+ * `site-profiles.md`) in mac-config — a project key is a machine identifier
+ * and was never meant to be printed; `cap()` guessed at a name by capitalizing
+ * the key, which is how `htmlg` showed up as «Htmlg» on the one card that
+ * printed it (the Incident scope fallback, `render.ts`).
+ *
+ * `mac-config` and `vault` stay lowercase on purpose: a machine and a store,
+ * not brands — capitalizing them would invent a name the owner never uses.
+ *
+ * A Telegram chat title must equal `chatTitle()` in `routes.ts`, which is
+ * built out of this table.
+ */
+export declare const DISPLAY: Record<Project, string>;
 /**
  * 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/events.js

@@ -10,6 +10,31 @@
  *   - required fields are never added — only a new event type.
  * That keeps old caller code and a new package compatible both ways.
  */
+/**
+ * The human name of a project, written exactly as the owner writes it.
+ * Source of truth is the project card index (`project-index` skill,
+ * `site-profiles.md`) in mac-config — a project key is a machine identifier
+ * and was never meant to be printed; `cap()` guessed at a name by capitalizing
+ * the key, which is how `htmlg` showed up as «Htmlg» on the one card that
+ * printed it (the Incident scope fallback, `render.ts`).
+ *
+ * `mac-config` and `vault` stay lowercase on purpose: a machine and a store,
+ * not brands — capitalizing them would invent a name the owner never uses.
+ *
+ * A Telegram chat title must equal `chatTitle()` in `routes.ts`, which is
+ * built out of this table.
+ */
+export const DISPLAY = {
+    playhub: 'PlayHub',
+    'one-q': 'One-Q',
+    zabukai: 'Zabukai',
+    'game-publisher': 'Game Publisher',
+    vault: 'vault',
+    'mac-config': 'mac-config',
+    alitools: 'Alitools',
+    htmlg: 'HTMLG',
+    '2roles': '2Roles'
+};
 /** Red = with sound. Everything else is silent. (There is no separate "incidents" topic any more — an incident is visible in the project's feed.) */
 /**
  * The icon dictionary. Two laws, both set by the owner on 25.08.2026:

package/dist/render.js

@@ -19,7 +19,7 @@
  * separates BLOCKS BY MEANING (header / body / actions), not mechanically
  * after every line.
  */
-import { ICON, iconFor } from "./events.js";
+import { DISPLAY, ICON, iconFor } from "./events.js";
 /**
  * A label gets a capital letter — but NOT a name that is deliberately
  * written lowercase: `iOS` was turning into `IOS`. The signal is a capital
@@ -971,12 +971,14 @@ const renderIncident = (e) => {
     const findings = bullets(e.items, false);
     return join([
         // The bracket on an incident names WHERE it burns, not how it ended —
-        // it has one ending. `Incident (Vault):`, `Incident (Session):`; with no
-        // word from the sender, the project name stands in.
+        // it has one ending. `Incident (vault):`, `Incident (Session):`; with no
+        // word from the sender, the project's own DISPLAY name stands in — the
+        // owner's human spelling, not `cap()`'s guess at one (`cap('htmlg')` gave
+        // «Htmlg», the one place a project key ever reached a human eye).
         // `filled`, not `??`: `scope: ''` and `scope: ' '` are a sender that
         // named no place, and `??` let the first past the project fallback (no
         // bracket at all) and the second into a visibly empty one.
-        typeLine(iconFor(e), 'Incident', e.title, e.url, filled(e.scope) ?? cap(e.project)),
+        typeLine(iconFor(e), 'Incident', e.title, e.url, filled(e.scope) ?? DISPLAY[e.project]),
         e.detail && e.detail !== e.title ? note(e.detail) : null,
         // The rows below came from the `session` card when it was folded in
         // (03.09.2026), in the order they had there: which copy, what the guard

package/dist/routes.d.ts

@@ -44,6 +44,14 @@ type Forum = {
     dev?: number;
 };
 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. 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.
+ */
+export declare const chatTitle: (p: Project) => string;
 export type Target = {
     chat: string;
     thread?: number;

package/dist/routes.js

@@ -1,32 +1,38 @@
-import { severity } from "./events.js";
+import { DISPLAY, severity } from "./events.js";
 export const ROUTES = {
-    // ops/dev = 22/23, not 3/4: the old tabs were deleted by hand on
-    // 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.
+    // The only project with a team, and so the only forum left. ops/dev =
+    // 22/23, not 3/4: the old tabs were deleted by hand on 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.
     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 },
-    // No `dev`: the safe is infrastructure, there is no one to discuss it
-    // with. Only reports from the weekly check, and only when something
-    // broke.
-    vault: { chat: '-1004459314999', ops: 3 },
-    // Also infrastructure, no `dev`: the daily task digest and the Monday
-    // stumbles summary. Before this row, both used to die silently on
-    // "unknown project."
-    'mac-config': { chat: '-1004442522004', ops: 2 },
-    // The owner's corporate project: only its own reports on "what the
-    // 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 },
-    // 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' }
+    // Every row below is a project the owner runs alone. Their Topics were
+    // turned off on 06.09.2026 and their `ops` numbers went with them: a card
+    // now goes to the chat itself. Sending a thread id into a chat that is no
+    // longer a forum fails with "message thread not found", so a row here and
+    // the chat's own setting must always agree.
+    playhub: { chat: '-1004418379613' },
+    'game-publisher': { chat: '-1004292453693' },
+    'one-q': { chat: '-1004466909784' },
+    vault: { chat: '-1004459314999' },
+    'mac-config': { chat: '-1004442522004' },
+    alitools: { chat: '-1003904331479' },
+    // Created 05.09.2026 as «HTMLG · Ops», the first chat built this way
+    // (HTMLG is the HTML5-games business; the brand and domain of its portal
+    // may change, the project name does not).
+    htmlg: { chat: '-1004334723487' },
+    // Created 08.09.2026 as «2Roles · Ops»: the third focus project, the owner
+    // runs it alone.
+    '2roles': { chat: '-1004314188744' }
 };
+/**
+ * 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. 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.
+ */
+export const chatTitle = (p) => ROUTES[p].ops === undefined ? `${DISPLAY[p]} · Ops` : DISPLAY[p];
 /**
  * Where an event goes. Everything goes to its own project's "Ops" tab; a
  * red one arrives there too, just with sound.

package/package.json

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