@mikitasazan/notify 1.8.1 → 1.9.0

package/README.md

@@ -95,17 +95,18 @@ notify report --project playhub --json < payload.json   # весь объект
 
 Полные сигнатуры — `src/events.ts`.
 
-**Ключ задачи.** Первая строка каждой карточки — два тега: `#тип #ключ`.
+**Ключ задачи.** Первая строка каждой карточки — три тега: `#тип #ключ
+#итог`.
 По ним дневной разборщик сверяет «это 🔴 уже закрыто более поздней карточкой
 той же задачи?» без сравнения человеческих формулировок. Явный `--key`
 побеждает; без него ключ выводится из заголовка и меняется вместе с ним —
 регулярный отправитель передаёт `--key` явно. В stdout CLI ключ не попадает.
 
-**Единственная дверь для свободного HTML** — `sendReport()` (`report --json` у
-аналитик): плотную строку дневного отчёта не разложить в `label=value` не
-испортив. Стандартизирован транспорт, формат тела — нет, и только здесь.
-Строку тегов `#report #ключ` пакет ставит и здесь: тег — фильтр владельца, к
-формату тела он отношения не имеет. Без явного ключа берётся `daily`.
+**Свободного HTML в пакете нет.** Дверь `sendReport()` удалена 25.08.2026:
+она отдавала произвольную разметку и ставила карточке два тега вместо трёх —
+единственный вид, который нельзя было отфильтровать по итогу. Последний её
+отправитель перешёл на типизированный `report` ещё 25.08; тип события задаёт
+каждый знак карточки, других путей нет.
 
 **Неизвестный проект** не роняет вызвавший крон (код возврата 0), но больше и
 не исчезает молча: в mac-config Ops уходит красная карточка «notify: событие

package/dist/events.js

@@ -68,7 +68,11 @@ export const iconFor = (e) => {
         case 'ci':
             return e.status === 'ok' ? ICON.ok : ICON.red;
         case 'job':
-            return JOB_ICON[e.status];
+            // `?? ICON.unknown`: an untyped `--json` payload can carry a status
+            // outside the map, and an undefined icon printed the literal word
+            // `undefined` at the head of line 2. Not knowing is itself a state the
+            // package already has a word and a sound for.
+            return JOB_ICON[e.status] ?? ICON.unknown;
         case 'session':
             return e.status === 'ok' ? ICON.ok : ICON.alarm;
         case 'incident':
@@ -76,9 +80,9 @@ export const iconFor = (e) => {
         case 'heartbeat_miss':
             return e.recovered ? ICON.ok : ICON.unknown;
         case 'pr':
-            return PR_ICON[e.action];
+            return PR_ICON[e.action] ?? ICON.unknown;
         case 'issue':
-            return ISSUE_ICON[e.action];
+            return ISSUE_ICON[e.action] ?? ICON.unknown;
         case 'report':
             return ICON.info;
     }

package/dist/index.d.ts

@@ -1,6 +1,6 @@
 export type { EventType, NotifyEvent, Project } from './events.ts';
 export { severity } from './events.ts';
-export { notify, sendReport } from './send.ts';
+export { notify } from './send.ts';
 export { render } from './render.ts';
 export { trend } from './trend.ts';
 export type { SendResult } from './send.ts';

package/dist/index.js

@@ -1,5 +1,5 @@
 export { severity } from "./events.js";
-export { notify, sendReport } from "./send.js";
+export { notify } from "./send.js";
 // `render` is exported so a sender can put on disk EXACTLY the card that was
 // sent rather than its own second version of the text. A hand-built copy had
 // already drifted from what went out.

package/dist/render.d.ts

@@ -19,7 +19,7 @@
  * separates BLOCKS BY MEANING (header / body / actions), not mechanically
  * after every line.
  */
-import { type NotifyEvent } from './events.ts';
+import { ICON, type NotifyEvent } from './events.ts';
 /** Escapes EVERYTHING that comes from outside — only the template adds tags. */
 export declare const esc: (v: unknown) => string;
 /**
@@ -65,16 +65,20 @@ export declare const eventKey: (e: NotifyEvent) => string;
  * `#fail` under a 🚫 and said so. Nor is a task that has simply gone quiet —
  * nobody knows yet whether it broke, and `#unknown` is the honest word for it.
  */
-export declare const OUTCOME_TAG: Readonly<Record<string, string>>;
-export declare const outcomeTag: (e: NotifyEvent) => string;
+/** Every icon the package can print — the key space of the outcome table. */
+type Icon = (typeof ICON)[keyof typeof ICON];
+/** The five words the third tag is allowed to be, and there is no sixth. */
+type OutcomeTag = 'ok' | 'fail' | 'off' | 'unknown' | 'news';
 /**
- * The tag line for free-form HTML (`sendReport`). The tag is the owner's
- * FILTER, and it has nothing to do with the body's format: a daily report
- * stays free-form text, but stops being the one card with no tags. The key
- * used to hang off the tail as `<i><code>#key</code></i>` — that is the old
- * format, from before tags moved to the first line.
+ * The type is `Record` over EVERY icon, not over `string`. A new icon added to
+ * `ICON` without a word here now fails to compile. Under the old loose type it
+ * fell through a `?? 'news'` default instead: a card whose outcome nobody had
+ * decided was indistinguishable from a card that is genuinely just news, and
+ * nothing anywhere went red. `news` is therefore written out for each icon
+ * that means it, never left to a fallback.
  */
-export declare const reportTags: (key: string) => string;
+export declare const OUTCOME_TAG: Readonly<Record<Icon, OutcomeTag>>;
+export declare const outcomeTag: (e: NotifyEvent) => OutcomeTag;
 /**
  * Renders an event into finished HTML text, cut to Telegram's limit.
  * Tags are the FIRST line, added before the cut (not after, as before):
@@ -83,3 +87,4 @@ export declare const reportTags: (key: string) => string;
  * parser on exactly the longest, meaning the most important, messages.
  */
 export declare const render: (e: NotifyEvent) => string;
+export {};

package/dist/render.js

@@ -383,10 +383,20 @@ const typeLine = (icon, type, action, url, aside) => {
     // template prints the word "null". That is how line 2 of a card became
     // `ℹ️ null` — reachable through `--json` and through a direct call from JS,
     // where there are no types.
-    // `action || 'open'` in the linked case: an empty title must not swallow the
-    // link, which would be the one thing the card cannot afford to lose.
-    const line = url ? fieldLink(type, url, action || 'open') : field(type, action);
     const tail = aside ? ` (${esc(aside)})` : '';
+    const name = action?.trim();
+    // No name: the card must not invent one. It used to write the word `open`
+    // into the identifier slot, so a report with a link and no title arrived as
+    // `Report: open` — and a deploy with neither fell back to its own status
+    // word, `Deploy: fail`, saying the outcome a third time after the icon and
+    // the tag. Both are the same mistake: a slot that must hold a name holding
+    // something else instead. The type word itself takes the link, so nothing
+    // clickable is lost and nothing false is said.
+    if (!name) {
+        const bare = `<b>${esc(cap(type))}</b>`;
+        return `${icon} ${url ? `<a href="${esc(url)}">${bare}</a>` : bare}${tail}`;
+    }
+    const line = url ? fieldLink(type, url, name) : field(type, name);
     return line === null ? `${icon} <b>${esc(cap(type))}</b>${tail}` : `${icon} ${line}${tail}`;
 };
 // `workflowUrl ?? url`: half the senders send the run link under the name
@@ -405,7 +415,7 @@ const typeLine = (icon, type, action, url, aside) => {
  * GitHub Action always fills the workflow name, and the hand-run scripts send
  * no run link at all.
  */
-const mechanism = (workflowName, via, runUrl) => workflowName ?? via ?? (runUrl ? 'the run' : undefined);
+const mechanism = (workflowName, via, runUrl) => workflowName ?? via;
 // The name of what ran sits WITH the type line, not eight lines below it.
 // `Deploy: fail` and `by what means it ran` answer one question, and the owner
 // read the two rows as unrelated things. It used to be one fact split in two:
@@ -426,7 +436,7 @@ const renderDeploy = (e) => {
         // is already said by the icon and the third tag; there is nothing to
         // repeat in words, and it is the same law a job and a report follow. The
         // `Via` row is gone: it used to carry this same name one floor below.
-        typeLine(icon, 'Deploy', mechanism(e.workflowName, e.via, runUrl) ?? e.status, runUrl),
+        typeLine(icon, 'Deploy', mechanism(e.workflowName, e.via, runUrl), runUrl),
         ...twoBlocks([field('Target', e.target), field('Reason', e.note)], [fieldLink('Commit', e.commitUrl, e.commit), titleField(e.commitTitle), bodyQuote(e.commitBody)])
     ]);
 };
@@ -465,11 +475,11 @@ const renderJob = (e) => {
         ...(hasItems ? bullets(e.items, disabledList) : []),
         e.command || e.logs ? '' : null,
         fieldCode('Log', e.logs),
-        ...fieldRun(e.command, e.commandNote),
-        // Kept only when the caller actually names the workflow — a named row is a
-        // second, different destination; an unnamed one repeats the Task link.
-        e.workflowName && (e.workflowUrl ?? e.url) ? '' : null,
-        e.workflowName ? fieldAction('Workflow', e.workflowUrl ?? e.url, e.workflowName) : null
+        ...fieldRun(e.command, e.commandNote)
+        // No trailing `Workflow:` row. It pointed at `workflowUrl ?? url` — the
+        // exact address line 2 already carries — so it was one destination
+        // written twice, and it stood BELOW the `To do:` command, which is the
+        // last thing the card is supposed to say.
     ]);
 };
 const renderReport = (e) => {
@@ -508,7 +518,7 @@ const renderCi = (e) => {
     const icon = iconFor(e);
     const runUrl = e.workflowUrl ?? e.url;
     return join([
-        typeLine(icon, 'CI', mechanism(e.workflowName, undefined, runUrl) ?? e.status, runUrl),
+        typeLine(icon, 'CI', mechanism(e.workflowName, undefined, runUrl), runUrl),
         ...twoBlocks([field('Actor', e.actor), field('Reason', e.note)], [fieldLink('Commit', e.commitUrl, e.commit), titleField(e.commitTitle), bodyQuote(e.commitBody)])
     ]);
 };
@@ -554,7 +564,7 @@ const renderIncident = (e) => join([
     typeLine(iconFor(e), 'Incident', e.title, e.url),
     e.detail && e.detail !== e.title ? note(e.detail) : null,
     e.logs ? '' : null,
-    fieldCode('Logs', e.logs)
+    fieldCode('Log', e.logs)
 ]);
 // A session in trouble. Same law as every other card: identifier first, then
 // the facts as fields, then his own words as a quote — never as a field, which
@@ -578,14 +588,16 @@ const renderSession = (e) => join([
 ]);
 const renderHeartbeatMiss = (e) => {
     const icon = iconFor(e);
-    const action = e.recovered ? 'ok' : 'miss';
     return join([
         // The task's name on the type line, exactly as a job card carries it. The
         // `Task:` row said the same thing a floor below. No sender in any
         // repository builds this event any more — the silence watchdog sends an
         // ordinary job with `--status silent` — but a machine still running the old
         // copy of that watchdog can, and the card it gets must obey the template.
-        typeLine(icon, 'Heartbeat', e.job, undefined, action),
+        // No bracket saying `ok` or `miss`: the icon says it, the third tag says
+        // it, and `miss` is not one of the five words the outcome is allowed to
+        // be. The bracket is for what finishes the NAME, never for a verdict.
+        typeLine(icon, 'Heartbeat', e.job),
         field('Reason', e.note),
         ...schedule(e.expected, e.lastSeen, e.recovered ? 'Last run' : 'Last seen')
     ]);
@@ -660,24 +672,19 @@ export const eventKey = (e) => {
                 return `i${e.number}`;
         }
     };
-    return e.key ? slug(e.key) : fallback();
+    // An empty instance tag (`#session # #fail`) is not a tag: it groups
+    // nothing and the parser cannot pair a red card with its green one. An
+    // untyped `--json` payload can leave every field it is derived from blank,
+    // so the project name is the last resort.
+    return (e.key ? slug(e.key) : fallback()) || slug(e.project) || 'event';
 };
 /**
- * The third tag is the OUTCOME, and it is always there. The owner: "I'm
- * missing a fail tag or something like it, so failures can be grouped and
- * ok can be grouped." One tap in Telegram collects every failure of a
- * project at once, no matter what type it arrived as — a deploy, a check,
- * a scheduled task, an incident.
- *
- * The value comes from the ICON, never from the status word. The icon is
- * already the single source of truth for the sound, and a second list of "what
- * counts as broken" would drift from the first — it already did once, when a
- * red card arrived silent.
- *
- * One icon meaning, one tag. A watchdog that SWITCHED SOMETHING OFF is not a
- * failure and must not be filed under the same word as one: the owner read
- * `#fail` under a 🚫 and said so. Nor is a task that has simply gone quiet —
- * nobody knows yet whether it broke, and `#unknown` is the honest word for it.
+ * The type is `Record` over EVERY icon, not over `string`. A new icon added to
+ * `ICON` without a word here now fails to compile. Under the old loose type it
+ * fell through a `?? 'news'` default instead: a card whose outcome nobody had
+ * decided was indistinguishable from a card that is genuinely just news, and
+ * nothing anywhere went red. `news` is therefore written out for each icon
+ * that means it, never left to a fallback.
  */
 export const OUTCOME_TAG = {
     [ICON.red]: 'fail',
@@ -686,20 +693,16 @@ export const OUTCOME_TAG = {
     [ICON.unknown]: 'unknown',
     [ICON.ok]: 'ok',
     [ICON.landed]: 'ok',
-    [ICON.approved]: 'ok'
+    [ICON.approved]: 'ok',
+    // Something happened; no verdict was passed on it.
+    [ICON.fresh]: 'news',
+    [ICON.taken]: 'news',
+    [ICON.discarded]: 'news',
+    [ICON.changes]: 'news',
+    [ICON.info]: 'news'
 };
-// Everything left over — a task was opened, a PR opened, edits asked for, a
-// digest — is news: something happened, no verdict was passed.
-export const outcomeTag = (e) => OUTCOME_TAG[iconFor(e)] ?? 'news';
+export const outcomeTag = (e) => OUTCOME_TAG[iconFor(e)];
 const tagsLine = (e) => `#${TYPE_TAG[e.type]} #${esc(eventKey(e))} #${outcomeTag(e)}`;
-/**
- * The tag line for free-form HTML (`sendReport`). The tag is the owner's
- * FILTER, and it has nothing to do with the body's format: a daily report
- * stays free-form text, but stops being the one card with no tags. The key
- * used to hang off the tail as `<i><code>#key</code></i>` — that is the old
- * format, from before tags moved to the first line.
- */
-export const reportTags = (key) => `#report #${esc(slug(key))}`;
 /**
  * Renders an event into finished HTML text, cut to Telegram's limit.
  * Tags are the FIRST line, added before the cut (not after, as before):

package/dist/send.d.ts

@@ -1,21 +1,3 @@
-import type { NotifyEvent, Project } from './events.ts';
+import type { NotifyEvent } from './events.ts';
 export type SendResult = 'sent' | 'skipped' | 'failed';
 export declare const notify: (e: NotifyEvent) => Promise<SendResult>;
-/**
- * Готовый HTML во вкладку «Ops» проекта — ТОЛЬКО для дневных отчётов.
- *
- * Зачем исключение из правила «свободного текста в API нет». Отчёт — это не
- * событие: в нём плотная строка вроде
- * `🎮 1284 игр (🍎 412 iOS +3 · 🤖 890 Android +5) | 📈 +240 запусков`,
- * и разложить её в `label=value` можно только испортив. Но транспорт у отчёта
- * ТОТ ЖЕ: ретраи, 429, таймауты, curl-фолбэк, номер вкладки. Пока его копировали
- * в каждый скрипт, один и тот же баг с дублями на таймауте пришлось чинить
- * дважды — в пакете и в game-publisher (27.07.2026).
- *
- * Граница: формат событий по-прежнему задаёт только пакет, «своё» уведомление
- * о деплое или упавшей задаче написать нельзя. Здесь стандартизирован транспорт,
- * а не формат — и в этом весь смысл.
- *
- * Всегда беззвучно: отчёт читают утром, а не по звонку.
- */
-export declare const sendReport: (project: Project, html: string, key?: string) => Promise<SendResult>;

package/dist/send.js

@@ -15,7 +15,7 @@
 import { execFileSync } from 'node:child_process';
 import { readFileSync } from 'node:fs';
 import { basename } from 'node:path';
-import { clampMessage, render, reportTags } from "./render.js";
+import { render } from "./render.js";
 import { ROUTES, targets } from "./routes.js";
 const log = (msg) => {
     // stderr, не stdout — stdout зарезервирован под возможный машинный вывод CLI.
@@ -133,7 +133,7 @@ const sendOne = async (token, target, text) => {
     log('out of send attempts');
     return 'failed';
 };
-/** Общий хвост для `notify` и `sendReport`: токен, цели, последовательная отправка. */
+/** The shared tail of `notify()`: token, targets, delivery one after another. */
 const deliver = async (where, text) => {
     const token = process.env.OPS_BOT_TOKEN?.trim();
     if (!token) {
@@ -285,34 +285,3 @@ export const notify = async (e) => {
     }
     return deliver(targets(e), render(e));
 };
-/**
- * Готовый HTML во вкладку «Ops» проекта — ТОЛЬКО для дневных отчётов.
- *
- * Зачем исключение из правила «свободного текста в API нет». Отчёт — это не
- * событие: в нём плотная строка вроде
- * `🎮 1284 игр (🍎 412 iOS +3 · 🤖 890 Android +5) | 📈 +240 запусков`,
- * и разложить её в `label=value` можно только испортив. Но транспорт у отчёта
- * ТОТ ЖЕ: ретраи, 429, таймауты, curl-фолбэк, номер вкладки. Пока его копировали
- * в каждый скрипт, один и тот же баг с дублями на таймауте пришлось чинить
- * дважды — в пакете и в game-publisher (27.07.2026).
- *
- * Граница: формат событий по-прежнему задаёт только пакет, «своё» уведомление
- * о деплое или упавшей задаче написать нельзя. Здесь стандартизирован транспорт,
- * а не формат — и в этом весь смысл.
- *
- * Всегда беззвучно: отчёт читают утром, а не по звонку.
- */
-export const sendReport = async (project, html, key) => {
-    if (!Object.hasOwn(ROUTES, project)) {
-        // Та же красная карточка, что у notify(): дверь свободного HTML — не
-        // лазейка для молчаливой потери (этот класс уже жил неделями дважды).
-        await reportLostProject(project, 'report');
-        return 'skipped';
-    }
-    const forum = ROUTES[project];
-    // Без проекта — как и render.ts: карточка уже лежит в форуме своего
-    // проекта, дублировать его в теге незачем. Строка тегов ПЕРВАЯ и до обрезки,
-    // как у любой другой карточки.
-    const tags = reportTags(key ?? 'daily');
-    return deliver([{ chat: forum.chat, thread: forum.ops, silent: true }], `${tags}\n${clampMessage(html, Math.max(64, 4000 - tags.length - 1))}`);
-};

package/package.json

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