@mikitasazan/notify 1.11.0 → 1.12.0

package/README.md

@@ -158,6 +158,23 @@ notify report --project playhub --json < payload.json   # весь объект
 никогда, только новый тип события**. Тогда старый вызывающий код и новый
 пакет всегда совместимы.
 
+## Тег сменился 18.08.2026 у шести отправителей
+
+Коммит `85564fc` в mac-config дал явный `--key` шести местам вызова, которые
+раньше отправляли карточку БЕЗ ключа — тег брался из `--job`/`--title`
+автоматически (`slug()`, см. `src/render.ts`). Без этой таблицы старую
+красную карточку в Telegram не найти поиском по новому тегу — она там под
+старым.
+
+| Отправитель | Старый тег (авто из русского названия) | Новый тег (из `--key`) |
+|---|---|---|
+| `arvent-eval-report.sh`, отчёт по эвалу | `#eval_качество_ответов_бота` | `#arvent_eval` |
+| `arvent-eval-report.sh`, файл диалогов | нет — шёл мимо пакета, сырым `sendDocument` Bot API | `#arvent_eval_dialogues` |
+| `daily-digest.sh`, дайджест задач (`job`) | `#дайджест_задач` | `#daily_digest` |
+| `daily-digest.sh`, дайджест задач (`report`) | `#дайджест_задач` (то же слово, другой тип-тег: `#report` вместо `#job`) | `#daily_digest` |
+| `daily-digest.sh`, отключённые Actions | `#github_actions_выключены` | `#actions_off` |
+| `daily-digest.sh`, Config doctor | `#config_doctor` | `#config_doctor` — не изменился: `slug()` приводит и старое, и новое к одной строке |
+
 ## Чего в пакете нет и почему
 
 - Очереди, брокера, демона — десятки сообщений в день, ретрай в памяти

package/dist/cli-flags.js

@@ -11,7 +11,8 @@
 export const KNOWN_FLAGS = new Set([
     'action', 'actor', 'assignee', 'author', 'body', 'branch', 'commit',
     'id', 'opened', 'reason', 'workdir',
-    'command', 'command-note', 'commit-body', 'commit-title', 'commit-url', 'detail',
+    'check', 'command', 'command-note', 'commit-author', 'commit-body', 'commit-title', 'commit-url',
+    'detail', 'detail-label',
     'expected', 'filename', 'item',
     'item-group', 'job', 'key', 'last-seen', 'line', 'logs', 'note',
     'aside', 'number', 'path', 'period', 'project', 'reviewer', 'stat', 'status',

package/dist/cli.js

@@ -24,7 +24,9 @@
 import { readFileSync } from 'node:fs';
 import { KNOWN_FLAGS } from "./cli-flags.js";
 import { render } from "./render.js";
+import { lintCard } from "./lint.js";
 import { notify } from "./send.js";
+import { ROUTES } from "./routes.js";
 import { setupTopic } from "./setup.js";
 const log = (msg) => console.error(`[notify] ${msg}`);
 /**
@@ -41,6 +43,23 @@ const log = (msg) => console.error(`[notify] ${msg}`);
 const safe = (v) => String(v ?? '').replace(/\b(sent|failed|skipped)\b/gi, (w) => `${w[0]}·${w.slice(1)}`);
 const args = process.argv.slice(2);
 const command = args[0];
+// `lint-text` and `routes` exist so the nightly audit asks the PACKAGE
+// instead of keeping its own copy of the rules and the routing table — the
+// copies had already drifted twice.
+if (command === 'lint-text') {
+    // The finished card HTML on stdin; every fault on stdout, one per line.
+    // Empty output means the card obeys the standard. Exit code stays 0 —
+    // the CLI-wide contract.
+    const text = readFileSync(0, 'utf-8').replace(/\n$/, '');
+    for (const fault of lintCard(text)) {
+        process.stdout.write(`${fault}\n`);
+    }
+    process.exit(0);
+}
+if (command === 'routes') {
+    process.stdout.write(`${JSON.stringify(ROUTES, null, 2)}\n`);
+    process.exit(0);
+}
 if (command === 'setup') {
     const [, chatId, projectKey] = args;
     if (!chatId || !projectKey) {
@@ -103,7 +122,13 @@ const num = (key) => {
     return n;
 };
 /**
- * `--item "text"` or `--item "text|https://link"`.
+ * `--item "text"`, `--item "text|https://link"`, or, since 26.08.2026,
+ * `--item "LABEL::text"` (and `LABEL::text|https://link`) for a bold label
+ * in front of the row — the same shape a search query's `facts` render,
+ * so a list of independent findings (vault's BAD/STALE/DIVERGED lines) does
+ * not have to smuggle its own heading inside the text. `::` and not `|`,
+ * which the link already owns, and not `:`, which shows up inside real
+ * findings ("STALE IN ARCHIVE: ssh-keys.tar.gz.age" already has one).
  *
  * An item's group name cannot be passed the same way `--stat` does it: the
  * bar here is already taken by the link. So `--item-group "Red checks"` is
@@ -114,9 +139,12 @@ const num = (key) => {
 const items = () => {
     const name = flags.get('item-group')?.[0];
     return (flags.get('item') ?? []).map((raw) => {
-        const idx = raw.lastIndexOf('|');
-        const base = idx === -1 ? { text: raw } : { text: raw.slice(0, idx), url: raw.slice(idx + 1) };
-        return name ? { ...base, group: name } : base;
+        const labelEnd = raw.indexOf('::');
+        const label = labelEnd === -1 ? undefined : raw.slice(0, labelEnd);
+        const rest = labelEnd === -1 ? raw : raw.slice(labelEnd + 2);
+        const idx = rest.lastIndexOf('|');
+        const base = idx === -1 ? { text: rest } : { text: rest.slice(0, idx), url: rest.slice(idx + 1) };
+        return { ...base, ...(label ? { label } : {}), ...(name ? { group: name } : {}) };
     });
 };
 /**
@@ -228,6 +256,7 @@ else {
                 commitUrl: one('commit-url'),
                 commitTitle: one('commit-title'),
                 commitBody: one('commit-body'),
+                commitAuthor: one('commit-author'),
                 workflowUrl: one('workflow-url'),
                 workflowName: one('workflow-name'),
                 url: one('url'),
@@ -251,6 +280,8 @@ else {
                 command: one('command'),
                 commandNote: one('command-note'),
                 logs: one('logs'),
+                detail: one('detail'),
+                detailLabel: one('detail-label'),
                 workflowUrl: one('workflow-url'),
                 workflowName: one('workflow-name'),
                 url: one('url')
@@ -279,6 +310,7 @@ else {
                 commitUrl: one('commit-url'),
                 commitTitle: one('commit-title'),
                 commitBody: one('commit-body'),
+                commitAuthor: one('commit-author'),
                 actor: one('actor'),
                 note: one('note'),
                 workflowUrl: one('workflow-url'),
@@ -333,6 +365,7 @@ else {
                 project: project(),
                 title: one('title') ?? '(no title)',
                 detail: one('detail'),
+                items: items(),
                 logs: one('logs'),
                 url: one('url')
             };
@@ -357,8 +390,10 @@ else {
                 type: 'report',
                 project: project(),
                 title: one('title') ?? '(no title)',
-                // A file card has no period; the caption is its title.
-                lines: []
+                aside: one('aside') ?? one('period'),
+                lines: pairs('line'),
+                items: items(),
+                url: one('url')
             };
             break;
         default:
@@ -376,6 +411,9 @@ if (event) {
     // --path is applicable to any type too, for the same reason --key is.
     event.path = one('path') ?? event.path;
     event.filename = one('filename') ?? event.filename;
+    // --check applies to any type (rule S): the verification command for a
+    // card whose event has no canonical URL.
+    event.check = one('check') ?? event.check;
 }
 if (event?.filename && !event.path) {
     parseErrors.push('--filename: given without --path, so there is no file to name');

package/dist/events.d.ts

@@ -12,9 +12,10 @@
  */
 export type Project = 'playhub' | 'one-q' | 'arvent' | 'game-publisher' | 'vault' | 'mac-config' | 'alitools';
 /**
- * A stable machine key for the task — the last line of every card, shaped
- * as `#key` (with no project name: the card already sits in its own
- * project's forum — `targets()` never sends it to someone else's). The
+ * 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
+ * in its own project's forum — `targets()` never sends it to someone else's).
+ * The
  * daily parser uses it to check "is this 🔴 already closed by a later card
  * with the same key?" without comparing human wording, which changes. It
  * is optional: without it, the key is derived from the type and the title
@@ -36,6 +37,18 @@ type Keyed = {
     path?: string;
     /** The file's name in the chat; defaults to the name from `path`. */
     filename?: string;
+    /**
+     * The verification command — `Check:` in the card's last block, monospaced
+     * and tap-to-copy. The standard (v2.1, rule S) wants every card to say
+     * where to verify it: a `Source:` link when the event has a canonical URL,
+     * this command when the event is local. Usually `config jobs --log <key>`.
+     */
+    check?: string;
+    /**
+     * Set by the send-side suppression, never by a caller: which day of the
+     * same unresolved failure this is. Renders as `Still red: day N`.
+     */
+    stillRed?: number;
 };
 /**
  * A list item inside a message: a task from a digest, a failed check, a
@@ -57,11 +70,19 @@ type Keyed = {
  * 🆕 came out today, 🔁 came out of the queue, ⚠ did not come out at all.
  * The icon was doing a heading's job.
  */
+/**
+ * `facts` — sub-rows under an item, indented, each `label: value`. For an
+ * item whose own value is not one number but several (a search query with
+ * its own clicks AND position) — a nested list, not a sentence stuffed into
+ * `text`: "0 clicks, pos. 55" was two facts hand-joined into a string, the
+ * exact shape that gets pulled apart into its own field everywhere else.
+ */
 export type Item = {
     text: string;
     url?: string;
     label?: string;
     group?: string;
+    facts?: Array<[label: string, value: string | number]>;
 };
 export type NotifyEvent = Keyed & (
 /** Shipping code to the server. */
@@ -72,12 +93,14 @@ export type NotifyEvent = Keyed & (
     commit?: string;
     /** A link to the commit — the "commit" row becomes clickable. */
     commitUrl?: string;
-    /** The commit's title — renders as the `Title:` field, the body follows as a quote. */
+    /** The commit's title — joins the `Commit:` row after the hash, the body follows as a quote. */
     commitTitle?: string;
     /** The commit's body, if there is one — the same quote shape as the title. */
     commitBody?: string;
+    /** The commit's author (GitHub login) — the `Author:` row links to their profile. */
+    commitAuthor?: string;
     workflowUrl?: string;
-    /** The run's name, for the link's visible text (defaults to `open`). */
+    /** The run's name, for the link's visible text. Without it, the type line itself becomes the link. */
     workflowName?: string;
     url?: string;
     /**
@@ -161,10 +184,22 @@ export type NotifyEvent = Keyed & (
      * A local log path — monospaced, not a link, same as on an incident.
      * It used to be glued onto the end of the reason sentence behind a
      * colon, which is what made a red card read as one long run-on line.
+     * Under rule S it is an ADDITION to `check`/a link, never the card's
+     * only pointer — a path cannot be tapped, only copied.
      */
     logs?: string;
+    /**
+     * A multi-line quoted block with its own caption (`detailLabel`) — the
+     * shape the watchdog uses to show the offending card's first lines
+     * under `Offender:`. Generic on purpose: any job with a verbatim
+     * excerpt to show (someone else's text, not the sender's own words)
+     * uses this instead of stuffing it into `note`.
+     */
+    detail?: string;
+    /** The caption over `detail`; defaults to `Detail`. */
+    detailLabel?: string;
     workflowUrl?: string;
-    /** The run's name, for the link's visible text (defaults to `open`). */
+    /** The run's name, for the link's visible text. Without it, the type line itself becomes the link. */
     workflowName?: string;
     /**
      * A fallback name for the run link: half the senders send it as
@@ -185,19 +220,25 @@ export type NotifyEvent = Keyed & (
      * accepts `--period` for it.
      */
     aside?: string;
-    /** Empty/not passed when `groups` is used — the two kinds of report are not mixed in one event. */
+    /**
+     * Renders even when `groups` is also set — a report's headline numbers
+     * (Pages, People, Impressions…) sit above the grouped section, not
+     * replaced by it. `lines` and `groups` answer different questions:
+     * "what changed" and "what's in each list".
+     */
     lines?: Array<[label: string, value: string | number, group?: string]>;
     /**
      * A list of items with links — for task digests, where the value is
      * in the names themselves, not in a number. Renders as a separate
-     * block after `lines`.
+     * block after `lines`. Ignored (not merged, not an error) when `groups`
+     * is also set — no live sender sets both today.
      */
     items?: Item[];
     /**
      * Named groups (a task board: Ready/In Progress/Not on the board;
-     * analytics: Metrics/Links) — each with its own heading and list of
-     * items. Replaces `lines`/`items` when set: different reports use
-     * either the flat form or groups, never both at once.
+     * analytics: Top search queries) — each with its own heading and list
+     * of items. Replaces `items` when set, but `lines` still renders above
+     * it — see that field's own doc.
      */
     groups?: Array<{
         name: string;
@@ -214,10 +255,12 @@ export type NotifyEvent = Keyed & (
     commit?: string;
     /** A link to the commit — the hash becomes clickable. */
     commitUrl?: string;
-    /** The commit's title (subject) — a separate `Title:` field, not a quote. */
+    /** The commit's title (subject) — joins the `Commit:` row after the hash, not a quote. */
     commitTitle?: string;
     /** The commit's body (after the subject) — the same quote shape as the title. */
     commitBody?: string;
+    /** The commit's author (GitHub login) — the `Author:` row links to their profile. Distinct from `actor`: on a scheduled run `actor` is whoever is on duty to fix it, not who wrote the code. */
+    commitAuthor?: string;
     actor?: string;
     /**
      * Why this run happened, when there is no commit to point at: a nightly
@@ -226,7 +269,7 @@ export type NotifyEvent = Keyed & (
     note?: string;
     /** A link to the run (workflow run) — separate from `url`, a fallback for `workflowUrl`. */
     workflowUrl?: string;
-    /** The run's name, for the link's visible text (defaults to `open`). */
+    /** The run's name, for the link's visible text. Without it, the type line itself becomes the link. */
     workflowName?: string;
     url?: string;
 }
@@ -242,7 +285,12 @@ export type NotifyEvent = Keyed & (
     action: 'opened' | 'approved' | 'changes_requested' | 'merged' | 'closed';
     number: number;
     title: string;
-    /** PR description — quoted on its own; the title is the `Title:` field above it. */
+    /**
+     * On `opened`: the PR's own description. On `approved`/
+     * `changes_requested`: the reviewer's comment, not the PR's
+     * description again — quoted on its own either way; the title joins
+     * the `PR:` type line above it, there is no separate field for it.
+     */
     body?: string;
     author?: string;
     reviewer?: string;
@@ -255,7 +303,7 @@ export type NotifyEvent = Keyed & (
     action: 'opened' | 'assigned' | 'closed';
     number: number;
     title: string;
-    /** The issue's body — a quote under the `Title:` field, separate from the title. */
+    /** The issue's body — a quote under the `Issue:` type line, which already carries the title. */
     body?: string;
     author?: string;
     assignee?: string;
@@ -266,7 +314,16 @@ export type NotifyEvent = Keyed & (
     type: 'incident';
     project: Project;
     title: string;
+    /** One free-form paragraph — a diagnosis that is genuinely one thought, not several findings glued by newlines. */
     detail?: string;
+    /**
+     * Several INDEPENDENT findings (a self-check emitting up to three
+     * unrelated diagnostic lines, each starting with its own marker word
+     * — `BAD`, `STALE`, `DIVERGED`) go here, not into `detail`: a list
+     * squeezed into one blockquote read as a wall of text with no
+     * category, the marker words doing a label's job inside a value.
+     */
+    items?: Item[];
     /** A local path to the logs (not a URL — renders monospaced, to copy, not to click). */
     logs?: string;
     url?: string;
@@ -287,7 +344,7 @@ export type NotifyEvent = Keyed & (
     project: Project;
     /** What happened, as the second line reads it: `Session: burning the limit`. */
     action: string;
-    /** The session's own id — the identifier field, first, as everywhere else. */
+    /** The session's own id. Never printed as a field — he cannot type it or search it; it only reaches the card inside the `command`'s `rm`. */
     id?: string;
     /** Working directory name, when several sessions opened with a similar line. */
     workdir?: string;
@@ -320,7 +377,7 @@ export type NotifyEvent = Keyed & (
     expected?: string;
     /** The task reported in again — same type, a green card instead of a red one, the key (for matching) does not change. */
     recovered?: boolean;
-    /** A ready-made reason sentence; without it, one is built from lastSeen/expected. */
+    /** A ready-made reason sentence. Without it there is no `Reason:` row at all — `lastSeen`/`expected` still print, under their own `Schedule` group. */
     note?: string;
 });
 export type EventType = NotifyEvent['type'];

package/dist/lint.js

@@ -32,8 +32,12 @@ const NOT_A_NAME = new Set([
 ]);
 /** The five words the third tag is allowed to be, and there is no sixth. */
 const OUTCOMES = new Set(['ok', 'fail', 'off', 'unknown', 'info']);
-/** Labels the template retired. Each one used to say what a neighbour said. */
-const RETIRED = ['Title', 'Number', 'State', 'Via', 'Check', 'Logs', 'Task', 'Id', 'Period'];
+/**
+ * Labels the template retired. Each one used to say what a neighbour said.
+ * `Check` LEFT this list in v2.1: rule S brought it back as the standard
+ * verification-command row. `Logs` stays retired — the new spelling is `Log`.
+ */
+const RETIRED = ['Title', 'Number', 'State', 'Via', 'Logs', 'Task', 'Id', 'Period'];
 /**
  * Reads a finished card and returns what is wrong with it, in the owner's
  * terms. An empty array means the card obeys the standard.
@@ -45,8 +49,23 @@ export const lintCard = (html) => {
     if (tags.length !== 3 || !tags.every((t) => t.startsWith('#'))) {
         found.push(`line 1 is "${rows[0] ?? ''}" — it must be exactly three tags`);
     }
-    else if (!OUTCOMES.has(tags[2].slice(1))) {
-        found.push(`the outcome tag is "${tags[2]}" — the vocabulary is ok, fail, off, unknown, info`);
+    else {
+        if (!OUTCOMES.has(tags[2].slice(1))) {
+            found.push(`the outcome tag is "${tags[2]}" — the vocabulary is ok, fail, off, unknown, info`);
+        }
+        // The charset is checked HERE, not trusted to slug(): slug keeps any
+        // Unicode letter, so a Russian-named job produces a Cyrillic tag with no
+        // complaint anywhere — confirmed against render.ts on 31.08.2026.
+        for (const t of tags) {
+            if (!/^#[a-z0-9_]+$/.test(t)) {
+                found.push(`the tag "${t}" carries characters outside [a-z0-9_] — tags are English, lowercase`);
+            }
+        }
+        // A dated tag groups nothing: every day mints a new one and the filter
+        // the tags exist for never collects two cards.
+        if (/(_|^#)20\d{2}_\d{2}_\d{2}$/.test(tags[1]) || /_20\d{6}$/.test(tags[1])) {
+            found.push(`the instance tag "${tags[1]}" ends in a date — a dated tag groups nothing`);
+        }
     }
     if (tags[1] === '#' || tags[1] === '#_') {
         found.push('the instance tag is empty — it groups nothing and pairs with nothing');
@@ -98,17 +117,39 @@ export const lintCard = (html) => {
             break;
         }
     }
-    // A red card must say where to look. Here — and only here — that can be
-    // judged completely: a log row, a command to run, or any address at all,
-    // including the one riding on line 2 where the standard puts it. Read back
-    // from Telegram the addresses are gone, so the same rule there accused a
-    // deploy card whose own second line was the link to the failed run.
-    // `#fail` only. A task that has gone silent is `#unknown`, and it has no log
-    // by definition — it never ran. Demanding one there would be demanding a
-    // thing that cannot exist.
-    const broke = (rows[0] ?? '').includes('#fail');
-    if (broke && !html.includes('<b>Log:</b>') && !html.includes('<b>To do:</b>') && !html.includes('<a href=')) {
-        found.push('a red card with no log, no command and no link — nowhere to look');
+    // Rule L (v2.1): everything the SYSTEM says is English. Cyrillic is
+    // allowed only as QUOTED CONTENT — text that exists in Russian outside the
+    // card: a blockquote (commit bodies, issue bodies, an offender's lines),
+    // the text of a link (issue titles in digests), and the title slot on
+    // line 2. Everywhere else — a label, a bare field value, a tag, a command —
+    // it is system text and a fault.
+    const quotedStripped = html
+        .replace(/<blockquote[^>]*>[\s\S]*?<\/blockquote>/g, '')
+        .replace(/<a href="[^"]*">[^<]*<\/a>/g, '')
+        // A commit's title rides the `Commit:` row after the hash — it is a
+        // commit message, the canonical quoted content.
+        .replace(/^<b>Commit:<\/b>.*$/gm, '')
+        // List items carry content (issue titles in a digest, findings) — the
+        // row's own text is the subject's, not the system's.
+        .replace(/^(?:•|\d+\.) .*$/gm, '');
+    const strippedRows = quotedStripped.split('\n');
+    // Line 2's value after the label is the one non-quoted slot allowed to
+    // carry a title written in Russian (issue/PR/report/incident titles).
+    if (strippedRows[1]) {
+        strippedRows[1] = strippedRows[1].replace(/(<b>[^<]+:<\/b>|<b>[^<]+<\/b>).*/, '$1');
+    }
+    if (/[а-яё]/i.test(strippedRows.join('\n'))) {
+        found.push('Cyrillic outside quoted content — system text is English (rule L)');
+    }
+    // Rule S (v2.1): a card that reports trouble must say where to verify it —
+    // a `Check:` command, a `Source:` link, a `To do:` command, or any link at
+    // all. A `Log:` path alone is not enough: a path cannot be tapped, and a
+    // card whose only pointer needs a file manager is a card with no pointer.
+    // `#fail` and `#unknown` both: a silent task has no log, but `config jobs
+    // --log <key>` answers it too.
+    const broke = (rows[0] ?? '').includes('#fail') || (rows[0] ?? '').includes('#unknown');
+    if (broke && !html.includes('<b>Check:</b>') && !html.includes('<b>To do:</b>') && !html.includes('<a href=')) {
+        found.push('a trouble card with no check command and no link — nowhere to look (rule S)');
     }
     return found;
 };

package/dist/render.d.ts

@@ -36,7 +36,7 @@ export declare const esc: (v: unknown) => string;
  *    Telegram replies `400 can't parse entities`, and we treat a 4xx as a
  *    permanent error and do not retry — the message disappeared for good.
  */
-export declare const clampMessage: (text: string, limit?: number) => string;
+export declare const clampMessage: (text: string, limit?: number, marker?: string) => string;
 export declare const slug: (raw: string) => string;
 /**
  * The instance tag: exactly which concrete event this is (branch,
@@ -81,10 +81,13 @@ 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):
- * they carry both the human filter and the parser's machine key — a card
- * cut without them would be not only unclickable but invisible to the
- * parser on exactly the longest, meaning the most important, messages.
+ *
+ * Assembly is TAIL-FIRST (v2.1): the parts that must survive any cut — the
+ * tag line (the human filter and the parser's machine key), the pointer
+ * block (`Log`/`Check`/`Source`) and the cut marker — are measured before
+ * the body is clamped, and the body gets what is left. Under the old order
+ * the pointer was part of the body, so the longest cards lost exactly the
+ * line saying where to look.
  */
 export declare const render: (e: NotifyEvent) => string;
 export {};