@mikitasazan/notify 1.11.0 → 1.11.1

package/dist/cli-flags.js

@@ -11,7 +11,7 @@
 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',
+    'command', 'command-note', 'commit-author', 'commit-body', 'commit-title', 'commit-url', 'detail',
     'expected', 'filename', 'item',
     'item-group', 'job', 'key', 'last-seen', 'line', 'logs', 'note',
     'aside', 'number', 'path', 'period', 'project', 'reviewer', 'stat', 'status',

package/dist/cli.js

@@ -103,7 +103,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 +120,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 +237,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'),
@@ -279,6 +289,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 +344,7 @@ else {
                 project: project(),
                 title: one('title') ?? '(no title)',
                 detail: one('detail'),
+                items: items(),
                 logs: one('logs'),
                 url: one('url')
             };
@@ -357,8 +369,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:

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
@@ -57,11 +58,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 +81,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;
     /**
@@ -164,7 +175,7 @@ export type NotifyEvent = Keyed & (
      */
     logs?: 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 +196,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 +231,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 +245,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 +261,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 +279,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 +290,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 +320,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 +353,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/render.js

@@ -20,7 +20,6 @@
  * after every line.
  */
 import { ICON, iconFor } from "./events.js";
-/** First letter capitalized, the rest left as is (ga4/GitHub stay themselves). */
 /**
  * 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
@@ -61,8 +60,14 @@ export const clampMessage = (text, limit = 4000) => {
     // Cut on a line boundary — only if that keeps most of the content.
     let end = lastBreak > limit * 0.6 ? lastBreak : limit;
     // Never cut inside `<...>` or inside `&...;` — otherwise the markup breaks.
+    // The closing `>` must be searched for only up to `end`, not across all of
+    // `cut`: a `>` that belongs to a LATER, already-doomed part of the message
+    // (still inside `cut` because `cut` runs to `limit`, past `end`) used to
+    // read as "this tag is closed" and let a tag get cut mid-attribute anyway —
+    // found by GLM review, reproduces with a long `href` that straddles the
+    // line-boundary cut point.
     const openTag = cut.lastIndexOf('<', end - 1);
-    if (openTag !== -1 && cut.indexOf('>', openTag) === -1) {
+    if (openTag !== -1 && cut.slice(openTag, end).indexOf('>') === -1) {
         end = openTag;
     }
     const amp = cut.lastIndexOf('&', end - 1);
@@ -140,19 +145,43 @@ const fieldLink = (label, url, text) => {
         ? `<b>${esc(cap(label))}:</b> <a href="${esc(url)}">${esc(firstLine(text))}</a>`
         : field(label, text);
 };
-/**
- * An action field (`workflow:`): unlike `fieldLink`, without a URL this is
- * NOT a field — the run simply has nowhere to lead, and showing the bare
- * word "run" with no link is more meaningless than not showing the row at
- * all.
- */
-// The link text is the name of where it leads (the workflow's name, the run's
-// name). The fallback word used to be "run": a noun that names nothing — the
-// owner read "Workflow: run" and did not understand what it was. "open" is a
-// verb, and it is at least honest about being a link, not a name.
-const fieldAction = (label, url, text) => url ? `<b>${esc(cap(label))}:</b> <a href="${esc(url)}">${esc(text ?? 'open')}</a>` : null;
 /** A monospace field — a path/command to copy, not a link. */
 const fieldCode = (label, value) => value ? `<b>${esc(cap(label))}:</b> <code>${esc(value)}</code>` : null;
+/**
+ * A person field — Author, Assignee, Reviewer. Every one of them is a
+ * GitHub login (`github-cards.py` reads it off `.user.login`/`.assignee.login`
+ * on the GitHub API object), and every GitHub login is a profile at one fixed
+ * address: `github.com/<login>`. The owner: "автор должен вести на страницу
+ * автора" — a name is an identifier like a commit hash or a PR number, and
+ * every other identifier on the card is a link.
+ */
+// `firstLine`, same as `fieldLink`: a login with an embedded `\n` (found by
+// Codex/GLM review) would otherwise land a raw newline inside the `href`
+// itself, not just the link text — every other field guards against a
+// multi-line value, this one didn't.
+const fieldPerson = (label, login) => {
+    if (!login) {
+        return null;
+    }
+    const oneLine = firstLine(login);
+    return `<b>${esc(cap(label))}:</b> <a href="https://github.com/${esc(oneLine)}">${esc(oneLine)}</a>`;
+};
+/**
+ * `Actor` on a CI card is a Telegram handle, not a GitHub login
+ * (`nightly.yml`, step "Кто чинит" — "по «@chelsnebes» приходит уведомление
+ * тому, кто чинит, по «mikitasazan» — нет"), so it links to Telegram, not
+ * GitHub: `github.com/@chelsnebes` would open a page that does not exist.
+ * Telegram DOES auto-link a bare `@handle` on its own, but the owner asked
+ * for an explicit link like every other identifier on the card, not an
+ * implicit one riding on a client behavior he cannot see from here.
+ */
+const fieldTelegram = (label, handle) => {
+    if (!handle) {
+        return null;
+    }
+    const oneLine = firstLine(handle);
+    return `<b>${esc(cap(label))}:</b> <a href="https://t.me/${esc(oneLine.replace(/^@/, ''))}">${esc(oneLine)}</a>`;
+};
 /**
  * A row that asks something FROM THE OWNER, rather than reports a fact. It
  * already stood last, set off by a blank line, and still read as an
@@ -178,13 +207,25 @@ const fieldRun = (value, why) => {
 };
 /** A group heading: italic + underline, no bold, no colon. */
 const group = (name) => `<i><u>${esc(cap(name))}</u></i>`;
-/** An item inside a group: `<b>label:</b> <a>text</a>` — or a plain bulleted/numbered row with no label. */
+/**
+ * An item inside a group: `<b>label:</b> <a>text</a>` — or a plain
+ * bulleted/numbered row with no label. `facts`, when the item carries them,
+ * print as indented `label: value` rows underneath — a nested list, one
+ * item with several facts of its own, the way a search query has both a
+ * click count and a position.
+ */
 const groupItem = (it, index, numbered) => {
     const linked = it.url ? `<a href="${esc(it.url)}">${esc(it.text)}</a>` : esc(it.text);
-    if (it.label) {
-        return `<b>${esc(it.label)}:</b> ${linked}`;
+    const head = it.label
+        ? `<b>${esc(cap(it.label))}:</b> ${linked}`
+        : numbered
+            ? `${index + 1}. ${linked}`
+            : `• ${linked}`;
+    if (!it.facts || it.facts.length === 0) {
+        return head;
     }
-    return numbered ? `${index + 1}. ${linked}` : `• ${linked}`;
+    const sub = it.facts.map(([label, value]) => `   <b>${esc(cap(label))}:</b> ${esc(String(value))}`);
+    return [head, ...sub].join('\n');
 };
 // A long explanation (a note, incident details) — as a quote: in Telegram
 // that is a bar on the left and a light indent, reading as "details," not as
@@ -206,15 +247,16 @@ const note = (text) => {
  * the card says it nowhere. The caption stands on its own line, because
  * the text itself does not fit in a field: a field holds one line and cuts
  * it.
+ *
+ * The caption is a bold field label with nothing after the colon, not the
+ * group() heading (italic-underline). It was the group heading first, and
+ * the owner read that and said it did not look like a category — correctly:
+ * a group is a heading over a LIST, and this caption sits over one quote,
+ * never more than one. A bold label with no value on the line is the same
+ * shape `Title:` already has right before a PR's body — the reader has
+ * already seen this exact pattern mean "what follows is quoted text."
  */
-/**
- * A quote that needs saying what it is. The heading is a GROUP heading — the
- * same italic-underline every other card uses over a block — not a bold field
- * label: a bold label means `label: value` on one line, and using it here made
- * the session card the only one whose block was titled a third way. The owner
- * read the card and asked where its group was.
- */
-const quoted = (label, text) => text ? `${group(label)}\n${note(text)}` : null;
+const quoted = (label, text) => text ? `<b>${esc(cap(label))}:</b>\n${note(text)}` : null;
 /**
  * Assembles the card. A blank line here marks a block change, not
  * indentation: two in a row mean an empty block, a leading one means a
@@ -421,14 +463,12 @@ const typeLine = (icon, type, action, url, aside) => {
 /**
  * What to call the thing that ran. The workflow's own name first — it is the
  * only text here that identifies THIS run. Then the caller's own word for the
- * mechanism (`manual, from the Mac`). Last resort `the run`, and only when a
- * link exists: losing the link to the logs on a red card is the one loss this
- * format cannot afford, and a row that says nothing is still better than a
- * card with nowhere to click. No live sender reaches that last resort — the
- * GitHub Action always fills the workflow name, and the hand-run scripts send
- * no run link at all.
+ * mechanism (`manual, from the Mac`). No third fallback: a row that says
+ * nothing distinctive is worse than not printing a name at all, and
+ * `typeLine` already handles the case with no name — a bare `<b>Deploy</b>`,
+ * still linked when a run URL exists.
  */
-const mechanism = (workflowName, via, runUrl) => workflowName ?? via;
+const mechanism = (workflowName, via) => 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:
@@ -445,12 +485,17 @@ const renderDeploy = (e) => {
     const icon = iconFor(e);
     const runUrl = e.workflowUrl ?? e.url;
     return join([
-        // The name of what shipped the deploy sits on the type line. The outcome
-        // 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), runUrl),
-        ...twoBlocks([field('Target', e.target), field('Reason', e.note)], [commitRow(e.commit, e.commitUrl, e.commitTitle), bodyQuote(e.commitBody)])
+        // The name of what shipped the deploy sits on the type line, the outcome
+        // in parens beside it — icon and tag alone were judged, live, not to be
+        // enough: a plain 🔴 next to a workflow name still read as "something
+        // happened," not "it failed," on a screen small enough to lose the color.
+        // 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 === 'fail' ? 'Fail' : 'OK'),
+        ...twoBlocks([field('Target', e.target), field('Reason', e.note)], [
+            commitRow(e.commit, e.commitUrl, e.commitTitle),
+            fieldPerson('Author', e.commitAuthor),
+            bodyQuote(e.commitBody)
+        ])
     ]);
 };
 const schedule = (expected, lastSeen, lastLabel) => {
@@ -523,16 +568,29 @@ const renderReport = (e) => {
         ...items
     ]);
 };
-// Same law as the deploy card, one row up: what ran is named beside the type
-// line and carries the link to its run. The label is `Check` and not `Via`
-// because here the name answers WHICH gate spoke — `nightly`, `Quality` —
-// while on a deploy it answers by what means the code was shipped.
+// Same law as the deploy card: what ran joins the type line itself and
+// carries the link to its run — `CI: nightly`, not a separate `Check:`/`Via:`
+// row. There is no separate label here at all: on deploy the mechanism
+// answers by what means the code was shipped, on CI it answers WHICH gate
+// spoke (`nightly`, `Quality`) — but both are the name on the type line.
 const renderCi = (e) => {
     const icon = iconFor(e);
     const runUrl = e.workflowUrl ?? e.url;
     return join([
-        typeLine(icon, 'CI', mechanism(e.workflowName, undefined, runUrl), runUrl),
-        ...twoBlocks([field('Actor', e.actor), field('Reason', e.note)], [commitRow(e.commit, e.commitUrl, e.commitTitle), bodyQuote(e.commitBody)])
+        typeLine(icon, 'CI', mechanism(e.workflowName, undefined), runUrl, e.status === 'fail' ? 'Fail' : 'OK'),
+        // `Actor` used to be read as "who wrote the commit," and on most runs it
+        // is — `github.actor` for a push IS the person who pushed. It stops being
+        // that on a scheduled run: arvent's nightly rewrites it to whoever is on
+        // duty to fix a red run, which can be someone other than the commit's
+        // author. So Actor answers "who is responsible for this run," `Author`
+        // below the commit answers "who wrote this code" — two different people
+        // on a nightly card, the same person everywhere else.
+        ...twoBlocks([field('Reason', e.note)], [
+            fieldTelegram('Actor', e.actor),
+            commitRow(e.commit, e.commitUrl, e.commitTitle),
+            fieldPerson('Author', e.commitAuthor),
+            bodyQuote(e.commitBody)
+        ])
     ]);
 };
 // A pull request and an issue are identified the way GitHub itself identifies
@@ -548,22 +606,39 @@ const named = (number, title) => title ? `#${number} ${title}` : `#${number}`;
 // about someone taking issue #312 and asked who, because he never got that far.
 //
 // The description is the news exactly once, when the thing is opened. On
-// assigned, closed, merged or a review verdict it is text he has already read,
-// and it buries the one line he came for.
-const opening = (action, body) => action === 'opened' ? bodyQuote(body) : null;
+// assigned, closed or merged it is text he has already read, and it buries
+// the one line he came for.
+//
+// A review verdict is the one exception: on `approved`/`changes_requested`
+// `body` is not the PR's description any more — the sender puts the
+// REVIEWER'S OWN comment there, which is new text he has not seen. "Verdict:
+// changes_requested, then nothing" was the owner's complaint: a verdict with
+// no comment attached said less than the review itself did.
+const VERDICT = new Set(['approved', 'changes_requested']);
+const opening = (action, body) => action === 'opened' || VERDICT.has(action) ? bodyQuote(body) : null;
+// The body is what the title stands for — it sits directly under the name,
+// with nothing between them. The people come after, consolidated in one
+// place, never splitting the title from what it names: the owner on the
+// old order, title then Author then Assignee then finally the body — "why
+// does the assignee cut apart what should be inseparable?"
 const renderPr = (e) => join([
     typeLine(iconFor(e), 'PR', named(e.number, e.title), e.url),
-    field('Author', e.author),
-    field('Reviewer', e.reviewer),
-    e.action === 'opened' && e.body ? '' : null,
-    opening(e.action, e.body)
+    opening(e.action, e.body),
+    (e.action === 'opened' || VERDICT.has(e.action)) && e.body ? '' : null,
+    fieldPerson('Author', e.author),
+    fieldPerson('Reviewer', e.reviewer)
 ]);
+// Unlike a PR, an issue's `body` means one thing on every action — its own
+// description, never someone else's verdict — so it prints whenever it is
+// there, not only on `opened`. The owner: hiding it on `assigned` read as
+// inconsistent with the same card type showing it moments earlier — his call
+// to keep, 26.08.2026, over the earlier "he already saw it" reasoning.
 const renderIssue = (e) => join([
     typeLine(iconFor(e), 'Issue', named(e.number, e.title), e.url),
-    field('Author', e.author),
-    field('Assignee', e.assignee),
-    e.action === 'opened' && e.body ? '' : null,
-    opening(e.action, e.body)
+    bodyQuote(e.body),
+    e.body ? '' : null,
+    fieldPerson('Author', e.author),
+    fieldPerson('Assignee', e.assignee)
 ]);
 // The incident's own title IS line 2, exactly as an issue's is. It used to say
 // the word `open` there — which the 🚨 already says, and no other card repeats
@@ -573,12 +648,17 @@ const renderIssue = (e) => join([
 // log path). It used to go through `field`, which keeps only the first line, so
 // every alarm this package ever sent arrived gutted. It is quoted now, the same
 // shape a commit body takes.
-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('Log', e.logs)
-]);
+const renderIncident = (e) => {
+    const findings = bullets(e.items, false);
+    return join([
+        typeLine(iconFor(e), 'Incident', e.title, e.url),
+        e.detail && e.detail !== e.title ? note(e.detail) : null,
+        findings.length > 0 ? '' : null,
+        ...findings,
+        e.logs ? '' : null,
+        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
 // keeps one line and clipped the name of the very session the card is about.

package/dist/trend.d.ts

@@ -10,15 +10,18 @@
  * So the shape is not a sender's business any more. It lives here, one
  * implementation, and every report calls it:
  *
- *   trend(210, 207)        → '210 / 207 ▲3'
- *   trend(202, 207)        → '202 / 207 ▼5'
+ *   trend(210, 207)        → '207 / 210 ▲3'
+ *   trend(202, 207)        → '207 / 202 ▼5'
  *   trend(0, 0)            → '0 / 0 ='
  *   trend(37)              → '37'          nothing to compare to, so no mark
- *   trend(4.4, 3.6, '%')   → '4.4% / 3.6% ▲0.8'
+ *   trend(4.4, 3.6, '%')   → '3.6% / 4.4% ▲0.8'
  *
- * Both numbers are printed, now first and before first. The owner read
- * `51 ▲5` and asked what the 5 was — the new value or the old one. Neither: it
- * was the distance between two numbers, one of which the card never showed.
+ * Both numbers are printed, old first, new second — left is what it was,
+ * right is what it became. The owner read `51 ▲5` first and asked what the 5
+ * was — the new value or the old one. Neither: it was the distance between
+ * two numbers, one of which the card never showed. Once both were on the
+ * card the owner asked for THIS order specifically, so a reader can read the
+ * row left to right as a sentence: was, became, and by how much.
  *
  * The rule the owner asked for, in one line: where there is data to compare
  * against, the arrow is printed; where there is none, nothing is printed —

package/dist/trend.js

@@ -10,15 +10,18 @@
  * So the shape is not a sender's business any more. It lives here, one
  * implementation, and every report calls it:
  *
- *   trend(210, 207)        → '210 / 207 ▲3'
- *   trend(202, 207)        → '202 / 207 ▼5'
+ *   trend(210, 207)        → '207 / 210 ▲3'
+ *   trend(202, 207)        → '207 / 202 ▼5'
  *   trend(0, 0)            → '0 / 0 ='
  *   trend(37)              → '37'          nothing to compare to, so no mark
- *   trend(4.4, 3.6, '%')   → '4.4% / 3.6% ▲0.8'
+ *   trend(4.4, 3.6, '%')   → '3.6% / 4.4% ▲0.8'
  *
- * Both numbers are printed, now first and before first. The owner read
- * `51 ▲5` and asked what the 5 was — the new value or the old one. Neither: it
- * was the distance between two numbers, one of which the card never showed.
+ * Both numbers are printed, old first, new second — left is what it was,
+ * right is what it became. The owner read `51 ▲5` first and asked what the 5
+ * was — the new value or the old one. Neither: it was the distance between
+ * two numbers, one of which the card never showed. Once both were on the
+ * card the owner asked for THIS order specifically, so a reader can read the
+ * row left to right as a sentence: was, became, and by how much.
  *
  * The rule the owner asked for, in one line: where there is data to compare
  * against, the arrow is printed; where there is none, nothing is printed —
@@ -26,19 +29,23 @@
  */
 /** Integers stay integers; anything else keeps one decimal. */
 const fmt = (n) => (Number.isInteger(n) ? String(n) : n.toFixed(1));
-/**
- * Two values that round to the same first decimal are equal: `4.42%` against
- * `4.44%` is not movement, it is noise, and `▲0.0` reads as a lie.
- */
-const same = (a, b) => Math.abs(a - b) < 0.05;
 export const trend = (now, was, unit = '') => {
     const head = `${fmt(now)}${unit}`;
     if (was === undefined || !Number.isFinite(was)) {
         return head;
     }
-    const pair = `${head} / ${fmt(was)}${unit}`;
-    if (same(now, was)) {
+    const pair = `${fmt(was)}${unit} / ${head}`;
+    // Equality is judged on the printed digits, not the raw numbers: `4.44` and
+    // `4.46` round to different labels (`4.4%` / `4.5%`), and printing `=` next
+    // to two different numbers reads as a lie no threshold on the raw values
+    // can prevent.
+    if (fmt(now) === fmt(was)) {
         return `${pair} =`;
     }
-    return now > was ? `${pair} ▲${fmt(now - was)}` : `${pair} ▼${fmt(was - now)}`;
+    // The diff is computed from the two PRINTED numbers, not the raw ones: a
+    // diff of the raw values can round to `0.0` even when the printed pair
+    // reads `4.4% / 4.5%` — the arrow would show movement of nothing next to
+    // two numbers that are visibly different.
+    const diff = Number(fmt(now)) - Number(fmt(was));
+    return diff > 0 ? `${pair} ▲${fmt(Math.abs(diff))}` : `${pair} ▼${fmt(Math.abs(diff))}`;
 };

package/package.json

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