@volter/twin-telegram 1.0.0 → 1.0.1

package/README.md

@@ -7,7 +7,7 @@ semantics.
 ## What it serves, and for whom
 
 The calls the demand's applications make (`journeys/demand.json`): Volter Harness's Telegram channel (the Chat SDK's
-`@chat-adapter/telegram`, polling) and Postiz's Telegram provider (`node-telegram-bot-api`).
+`@chat-adapter/telegram`, polling).
 
 - A bot reads itself (`getMe`), removes its webhook (`deleteWebhook`) and polls for its updates (`getUpdates`: offset,
   limit, allowed_updates, and a timeout that holds the request until an update arrives, a long poll).
@@ -48,6 +48,6 @@ host, `api.telegram.org`.
 - Editing messages, reactions, inline keyboards and callback queries, stickers, payments, inline mode, games, business
   and passport methods, forum topics, and every other method of the page.
 - A medium sent by an HTTP URL, which Telegram downloads: a World lets the twin reach nothing outside it, so it answers
-  as Telegram does for a URL it could not get (Postiz sends URLs only with its opt-in Cloudflare storage).
+  as Telegram does for a URL it could not get.
 - A photo's other sizes (the twin keeps the one it was given), thumbnails, and a video's frames beyond its header.
 - The 3-second hold the server puts on a repeated short poll, and a second poller's conflict.

package/dist/journeys/customer-life.json

@@ -2,7 +2,7 @@
  "vendor": "telegram",
  "author": "Contributor 173",
  "host": "api.telegram.org",
- "about": "Tide Labs, a two-person studio, runs its Volter Harness agent on Telegram (a bot polling for updates, answering in private and in the team group, where privacy mode keeps a plain member from hearing the team until it is made an administrator, posting a scheduled digest, and sending a finished card's release notes as a document) and publishes its news to a Telegram channel through Postiz (connected by a /connect post, then text, an album, a reply, a photo, a video and a PDF), from January to the agent's retirement at the end of February.",
+ "about": "Tide Labs, a two-person studio, runs its Volter Harness agent on Telegram (a bot polling for updates, answering in private and in the team group, where privacy mode keeps a plain member from hearing the team until it is made an administrator, posting a scheduled digest, and sending a finished card's release notes as a document) and publishes its news to a Telegram channel through Scheduler (connected by a /connect post, then text, an album, a reply, a photo, a video and a PDF), from January to the agent's retirement at the end of February.",
  "steps": [
   {
    "name": "Monday 5 January, 10:00 in Lisbon",
@@ -530,7 +530,7 @@
    ]
   },
   {
-   "name": "Ana makes the news bot with BotFather for Postiz, which she runs herself (docker compose, local storage)",
+   "name": "Ana makes the news bot with BotFather for Scheduler, which she runs herself (docker compose, local storage)",
    "method": "POST",
    "path": "/_twin/bots",
    "body": {
@@ -571,11 +571,11 @@
    ]
   },
   {
-   "name": "14:06: Ana sets her Postiz's TELEGRAM_TOKEN to the news bot's token and, in Postiz, chooses to add Telegram",
+   "name": "14:06: Ana sets her Scheduler's TELEGRAM_TOKEN to the news bot's token and, in Scheduler, chooses to add Telegram",
    "wait": "1m"
   },
   {
-   "name": "Postiz's connect screen polls the news bot: only the bot's own promotion is waiting, and it holds no /connect",
+   "name": "Scheduler's connect screen polls the news bot: only the bot's own promotion is waiting, and it holds no /connect",
    "method": "POST",
    "path": "/bot{news_token}/getUpdates",
    "headers": {
@@ -602,7 +602,7 @@
    ]
   },
   {
-   "name": "Ana posts the command Postiz shows her in the channel",
+   "name": "Ana posts the command Scheduler shows her in the channel",
    "method": "POST",
    "path": "/_twin/messages",
    "body": {
@@ -613,7 +613,7 @@
    "status": 200
   },
   {
-   "name": "Postiz polls again from the next update (the last update_id it saw plus one) and finds the /connect post",
+   "name": "Scheduler polls again from the next update (the last update_id it saw plus one) and finds the /connect post",
    "method": "POST",
    "path": "/bot{news_token}/getUpdates",
    "headers": {
@@ -637,7 +637,7 @@
    ]
   },
   {
-   "name": "Postiz reads its bot",
+   "name": "Scheduler reads its bot",
    "method": "POST",
    "path": "/bot{news_token}/getMe",
    "headers": {
@@ -709,7 +709,7 @@
    "wait": "10s"
   },
   {
-   "name": "Postiz deletes its notice",
+   "name": "Scheduler deletes its notice",
    "method": "POST",
    "path": "/bot{news_token}/deleteMessage",
    "headers": {
@@ -725,7 +725,7 @@
    ]
   },
   {
-   "name": "Postiz reads the channel it is connecting",
+   "name": "Scheduler reads the channel it is connecting",
    "method": "POST",
    "path": "/bot{news_token}/getChat",
    "headers": {
@@ -783,7 +783,7 @@
    "wait": "71630s"
   },
   {
-   "name": "Postiz publishes the launch post (Postiz's HTML: a bold title, two paragraphs)",
+   "name": "Scheduler publishes the launch post (Scheduler's HTML: a bold title, two paragraphs)",
    "method": "POST",
    "path": "/bot{news_token}/sendMessage",
    "headers": {
@@ -944,7 +944,7 @@
    "wait": "67h"
   },
   {
-   "name": "Postiz publishes the 0.9 release with three screenshots as one album, the text on the first",
+   "name": "Scheduler publishes the 0.9 release with three screenshots as one album, the text on the first",
    "method": "POST",
    "path": "/bot{news_token}/sendMediaGroup?chat_id={channel}&media=%5B%7B%22type%22%3A%22photo%22%2C%22media%22%3A%22attach%3A%2F%2F0%22%2C%22caption%22%3A%22%3Cb%3ETide%200.9%3C%2Fb%3E%5CnA%20dashboard%20for%20every%20release%2C%20a%20timeline%20you%20can%20drag%2C%20and%20settings%20in%20one%20place.%22%2C%22parse_mode%22%3A%22HTML%22%7D%2C%7B%22type%22%3A%22photo%22%2C%22media%22%3A%22attach%3A%2F%2F1%22%2C%22parse_mode%22%3A%22HTML%22%7D%2C%7B%22type%22%3A%22photo%22%2C%22media%22%3A%22attach%3A%2F%2F2%22%2C%22parse_mode%22%3A%22HTML%22%7D%5D",
    "form": {
@@ -979,11 +979,11 @@
      "equals": "Tide 0.9\nA dashboard for every release, a timeline you can drag, and settings in one place."
     },
     {
-     "path": "result.0.photo.0.width",
+     "path": "result.0.photo.2.width",
      "equals": 480
     },
     {
-     "path": "result.2.photo.0.height",
+     "path": "result.2.photo.2.height",
      "equals": 300
     },
     {
@@ -1001,13 +1001,13 @@
    "wait": "1h"
   },
   {
-   "name": "Postiz publishes the post's comment, the changelog, as a reply to the album",
+   "name": "Scheduler publishes the post's comment, the changelog, as a reply to the album",
    "method": "POST",
    "path": "/bot{news_token}/sendMessage",
    "headers": {
     "content-type": "application/x-www-form-urlencoded"
    },
-   "body": "chat_id={channel}&text=Changelog%3A%20drag%20to%20reschedule%20a%20release%3B%20faster%20dashboard%3B%20fixed%20the%20login%20redirect.%0A&parse_mode=HTML&reply_to_message_id={album}",
+   "body": "chat_id={channel}&text=Changelog%3A%20drag%20to%20reschedule%20a%20release%3B%20faster%20dashboard%3B%20fixed%20the%20login%20redirect.%0A&parse_mode=HTML&reply_parameters=%7B%22message_id%22%3A{album}%7D",
    "status": 200,
    "expect": [
     {
@@ -1062,7 +1062,7 @@
    "wait": "1845m"
   },
   {
-   "name": "Postiz sends Ana's product photo with its 1,091-character story, and Telegram refuses the caption",
+   "name": "Scheduler sends Ana's product photo with its 1,091-character story, and Telegram refuses the caption",
    "method": "POST",
    "path": "/bot{news_token}/sendPhoto?chat_id={channel}&caption=Tide%20Desk%20started%20as%20a%20sketch%20on%20a%20caf%C3%A9%20napkin%20in%20Porto%2C%20the%20week%20our%20second%20release%20slipped%20for%20the%20third%20time.%20We%20were%20two%20people%20with%20a%20shared%20spreadsheet%2C%20a%20calendar%20nobody%20trusted%20and%20a%20habit%20of%20shipping%20on%20Fridays%20at%20midnight.%20Ana%20drew%20three%20columns%3A%20what%20is%20ready%2C%20what%20is%20waiting%2C%20what%20is%20promised.%20Bruno%20added%20a%20fourth%3A%20who%20is%20waiting%20for%20it.%20That%20napkin%20became%20the%20first%20board%2C%20and%20the%20board%20became%20the%20planner%20we%20use%20every%20Monday.%20We%20kept%20the%20rule%20from%20that%20night%3A%20nothing%20goes%20on%20the%20timeline%20unless%20someone%20can%20say%20who%20is%20waiting%20for%20it.%20It%20sounds%20small%2C%20but%20it%20changed%20how%20we%20talk%20about%20releases.%20We%20stopped%20arguing%20about%20dates%20and%20started%20asking%20who%20would%20notice.%20The%20desk%20in%20the%20photo%20is%20where%20it%20all%20happens%20now%3A%20one%20screen%20for%20the%20timeline%2C%20one%20for%20the%20changelog%2C%20and%20a%20cup%20that%20says%20Friday.%20Today%20Tide%20plans%20the%20weekly%20releases%20of%20forty%20small%20teams%2C%20from%20a%20bakery%27s%20ordering%20app%20in%20Braga%20to%20a%20school%20timetable%20in%20Coimbra.%20If%20your%20team%20still%20keeps%20its%20releases%20in%20a%20spreadsheet%2C%20we%20were%20you%20two%20years%20ago.%20Come%20and%20try%20the%20board%3B%20the%20napkin%20is%20framed%20on%20the%20wall%20behind%20it.&parse_mode=HTML",
    "form": {
@@ -1092,7 +1092,7 @@
    "wait": "20m"
   },
   {
-   "name": "Postiz sends the photo again with the short caption",
+   "name": "Scheduler sends the photo again with the short caption",
    "method": "POST",
    "path": "/bot{news_token}/sendPhoto?chat_id={channel}&caption=Tide%20Desk%20started%20as%20a%20sketch%20on%20a%20caf%C3%A9%20napkin%20in%20Porto%2C%20the%20week%20our%20second%20release%20slipped%20for%20the%20third%20time.%20That%20napkin%20became%20the%20first%20board%2C%20and%20the%20board%20became%20the%20planner%20we%20use%20every%20Monday.%20Today%20Tide%20plans%20the%20weekly%20releases%20of%20forty%20small%20teams.&parse_mode=HTML",
    "form": {
@@ -1108,11 +1108,11 @@
    "status": 200,
    "expect": [
     {
-     "path": "result.photo.0.width",
+     "path": "result.photo.2.width",
      "equals": 640
     },
     {
-     "path": "result.photo.0.height",
+     "path": "result.photo.2.height",
      "equals": 480
     },
     {
@@ -1126,7 +1126,7 @@
    "wait": "6880m"
   },
   {
-   "name": "Postiz publishes the product demo video",
+   "name": "Scheduler publishes the product demo video",
    "method": "POST",
    "path": "/bot{news_token}/sendVideo?chat_id={channel}&caption=Three%20seconds%20of%20Tide%200.9%3A%20a%20release%20dragged%20to%20Friday.&parse_mode=HTML",
    "form": {
@@ -1164,7 +1164,7 @@
    "wait": "4h"
   },
   {
-   "name": "Postiz publishes the white paper as a PDF",
+   "name": "Scheduler publishes the white paper as a PDF",
    "method": "POST",
    "path": "/bot{news_token}/sendDocument?chat_id={channel}&caption=How%20a%20two-person%20team%20ships%20every%20week%3A%20our%20notes%2C%20as%20a%20PDF.&parse_mode=HTML",
    "form": {

package/dist/journeys/customer-life.outline.md

@@ -2,8 +2,8 @@
 
 **The customer.** Tide Labs, a two-person software studio in Lisbon. Ana Ribeiro, its founder, runs an agent on Volter
 Harness that she and the team talk to on Telegram, and publishes the studio's news to its Telegram channel with
-Postiz. Bruno Costa, its engineer, is on the team chat. The story runs from Monday 5 January to Friday 27 February
-2026: two bots made, the agent at work in a private chat and a group, a news channel connected to Postiz and posted to
+Scheduler. Bruno Costa, its engineer, is on the team chat. The story runs from Monday 5 January to Friday 27 February
+2026: two bots made, the agent at work in a private chat and a group, a news channel connected to Scheduler and posted to
 for six weeks, the agent's group retired and, at the end, the agent's token revoked. The channel and its bot stay.
 
 ## Who acts, and with what
@@ -21,8 +21,8 @@ for six weeks, the agent's group retired and, at the end, the agent's token revo
   Harness's board, where the agent files work as cards, tells a chat subscribed to a card when it is done, the card's
   files attached; the Chat SDK sends a message with files as MarkdownV2 (supercode board/dispatch.mjs notifyChats,
   @chat-adapter/telegram's resolveParseMode).
-- **The news bot**, @tidelabs_news_bot, token N: the bot Postiz posts with. Postiz's Telegram integration calls with
-  the one bot its deployment configures, its TELEGRAM_TOKEN (postiz-app telegram.provider.ts), so Ana runs Postiz
+- **The news bot**, @tidelabs_news_bot, token N: the bot Scheduler posts with. Scheduler's Telegram integration calls with
+  the one bot its deployment configures, its TELEGRAM_TOKEN, so Ana runs Scheduler
   herself (docker compose, local storage) and sets its TELEGRAM_TOKEN to token N. She makes the bot an administrator of
   the channel allowed to post and to delete messages.
 
@@ -54,17 +54,17 @@ is a member; a bot deletes another's message in a channel only with the right to
    exactly those items to the home chat (sendMessage to the group).
 5. **Wednesday 7 January, 14:00. The news channel.** Ana makes the public channel "Tide Labs News" (@tidelabs_news)
    with the studio's logo as its photo (door). She makes the news bot with BotFather (token N) and adds it to the
-   channel as an administrator that may post and delete messages (door). In the Postiz she runs herself (docker compose,
-   local storage) she sets TELEGRAM_TOKEN to token N, and then chooses to add Telegram; Postiz
-   shows the command to post, "/connect" and a word, and she posts it in the channel (door). Postiz's connect screen
+   channel as an administrator that may post and delete messages (door). In the Scheduler she runs herself (docker compose,
+   local storage) she sets TELEGRAM_TOKEN to token N, and then chooses to add Telegram; Scheduler
+   shows the command to post, "/connect" and a word, and she posts it in the channel (door). Scheduler's connect screen
    polls (getUpdates, its library sending allowed_updates as the fields allowed_updates[0]=message and
    allowed_updates[1]=channel_post, which the Bot API does not read as its JSON-serialized list, so every update type
-   comes back): the bot's own membership change and her post come back. Postiz reads its bot (getMe), checks the bot
+   comes back): the bot's own membership change and her post come back. Scheduler reads its bot (getMe), checks the bot
    may delete messages there (getChatMember: an administrator with can_delete_messages), deletes her /connect post
    (deleteMessage), posts "Connection Successful. Message will be deleted in 10 seconds." (sendMessage) and, ten
    seconds later, deletes that too (deleteMessage). It then reads the channel (getChat), the photo's file (getFile), and copies the photo into its
    storage from the file's link (the file download).
-6. **Thursday 8 January, 10:00. The launch post, and the release notes.** Postiz publishes Ana's announcement, bold title and two paragraphs
+6. **Thursday 8 January, 10:00. The launch post, and the release notes.** Scheduler publishes Ana's announcement, bold title and two paragraphs
    (sendMessage, parse_mode HTML).
    At 11:00 Ana asks the agent in her private chat for the 0.9 release notes by Friday; Harness's poll receives it,
    it shows the bot typing, and the agent answers that the work is card t_7c1e9a04 on its board and that this chat
@@ -72,23 +72,23 @@ is a member; a bot deletes another's message in a channel only with the right to
    January, 15:00**: the card is done with its notes file, and Harness's board tells the chat: the notice "card … done
    — Draft the 0.9 release notes" and its summary as the caption of the file (sendDocument, the file uploaded, the
    caption in MarkdownV2 as the Chat SDK escapes it).
-7. **Monday 12 January, 10:00. A release with screenshots.** Postiz publishes the release post with three screenshots
+7. **Monday 12 January, 10:00. A release with screenshots.** Scheduler publishes the release post with three screenshots
    as one album, the text on the first (sendMediaGroup, the images uploaded). At 11:00 it publishes the post's comment,
-   the changelog, as a reply to the album's first message (sendMessage with reply_to_message_id).
+   the changelog, as a reply to the album's first message (sendMessage with reply_parameters naming it).
 8. **Monday 12 January, 18:00. The standups move.** The team moves its standups to a video call and Ana removes the
    agent bot from "Tide Labs team" (door), but leaves the digest job on. Tuesday 13 January at 09:15 the job posts its
    digest to the home chat, which says no standup items were posted this week (that morning's standup was on the
    call), and Telegram refuses: "Forbidden: bot was kicked from the group chat". Ana deletes the job in Harness (no
    Telegram call).
 9. **Wednesday 14 January, 16:00. A caption too long.** Ana's next post is one product photo with a 1,091-character
-   story. Postiz sends it (sendPhoto) and Telegram refuses it: a photo's caption holds at most 1,024 characters
-   ("Bad Request: message caption is too long"); Postiz shows "Telegram rejected the post". At 16:20 she cuts the story
-   to a paragraph and Postiz sends it again, which posts.
-10. **Monday 19 January, 11:00. A demo and a paper.** Postiz publishes the product demo video (sendVideo, uploaded) and,
+   story. Scheduler sends it (sendPhoto) and Telegram refuses it: a photo's caption holds at most 1,024 characters
+   ("Bad Request: message caption is too long"); Scheduler shows "Telegram rejected the post". At 16:20 she cuts the story
+   to a paragraph and Scheduler sends it again, which posts.
+10. **Monday 19 January, 11:00. A demo and a paper.** Scheduler publishes the product demo video (sendVideo, uploaded) and,
    at 15:00, the white paper as a PDF (sendDocument, uploaded).
 11. **Friday 27 February, 17:00. The agent retired.** Ana stops using the agent on Telegram and, in BotFather, makes a new
     token for it (/token), which revokes token A. Harness, still running on her laptop, polls with it and is refused ("Unauthorized"); she stops it. The
-    news channel, its posts and the news bot stay with Postiz.
+    news channel, its posts and the news bot stay with Scheduler.
 
 ## What the story reaches
 
@@ -96,4 +96,4 @@ getMe (both bots), deleteWebhook, getUpdates (held, a long poll; with allowed_up
 privacy mode (a plain member bot sent a service message and not a plain mention; an administrator bot sent every
 message), sendChatAction, sendMessage (plain, HTML, a reply; refused for a removed bot), getChatMember, deleteMessage
 (twice), getChat, getFile, the file download, sendPhoto (refused for its caption, then sent), sendVideo, sendDocument
-(Postiz's PDF; Harness's notes with a MarkdownV2 caption), sendMediaGroup; and a revoked token's refusal.
+(Scheduler's PDF; Harness's notes with a MarkdownV2 caption), sendMediaGroup; and a revoked token's refusal.

package/dist/journeys/customer-life.outline.verdict.json

@@ -1,75 +1,40 @@
 {
   "judge": {
-    "agent": "Claude Code (Claude Agent SDK), model claude-opus-5-5",
-    "name": "Contributor 106"
+    "agent": "Claude journey judge (Opus)",
+    "name": "Independent journey judge"
   },
   "authors": [
-    "Contributor 173"
+    "yueranyuan",
+    "Aaron (A-001)",
+    "Claude Opus 5.5",
+    "Codex"
   ],
-  "bar": "829132787d94a2d4",
-  "sha256": "267e4ae00d8d6bd435831be1a5b9dc741a7003bd0a43641ea7c4c000ee974e20",
-  "judgedAt": "2026-10-02",
+  "sha256": "4186f9087ab35bb7639a6d5aaa3471c51695ed2be4c086e417a7e2ebd2310d19",
+  "judgedAt": "2026-10-15",
   "plausible": true,
   "rulings": [
     {
-      "id": "three-tuesdays-skipped",
+      "id": "reply-to-message-id-era",
       "steps": [
-        "act 3",
-        "act 4",
-        "act 7",
-        "act 8",
-        "act 9",
-        "act 10"
+        "act 7"
       ],
-      "barItem": "a stated cause that never happens, and a promise never kept",
-      "reason": "Act 3 sets the standup weekly on Tuesdays and makes the agent an administrator, which is sent every group message (https://core.telegram.org/bots/features#privacy-mode). Act 4 runs the first standup and digest on 6 January. The standups move to the call only on Monday 2 February (act 10). Tuesdays 13, 20 and 27 January fall within acts 7-9 with no standup, no poll and no digest. Act 10's digest then says that no items were posted \"this week\", as if earlier weeks had them.",
-      "correction": "Move act 10 to Monday 12 January, 18:00, so that the refused digest is Tuesday 13 January's. Or tell the three January Tuesdays' standups and digests."
-    },
-    {
-      "id": "postiz-never-given-token-n",
-      "steps": [
-        "Who acts",
-        "act 5"
-      ],
-      "barItem": "the wrong actor or credential for an act",
-      "reason": "Postiz posts to Telegram through the one bot its deployment configures, process.env.TELEGRAM_TOKEN (postiz-app e0a08a7, libraries/nestjs-libraries/src/integrations/social/telegram.provider.ts:19). In hosted Postiz, that bot is Postiz's own. The outline calls @tidelabs_news_bot, token N, \"Postiz's Telegram integration\", and in act 5 Ana makes the bot and Postiz then calls with it. The outline never says that she runs Postiz herself or that token N becomes its TELEGRAM_TOKEN.",
-      "correction": "In 'Who acts' and act 5, say that Ana self-hosts Postiz (docker compose, local storage) and sets its TELEGRAM_TOKEN to token N before she adds Telegram."
+      "barItem": "the wrong era: building on an API the vendor had deprecated by the World's date; a call through a door the vendor does not document",
+      "reason": "Act 7 has Scheduler publish the changelog comment as a reply 'with reply_to_message_id'. Telegram replaced that parameter in Bot API 7.0, December 29, 2023 (https://core.telegram.org/bots/api-changelog: 'Replaced parameters reply_to_message_id and allow_sending_without_reply in the methods ... with the field reply_parameters'), two years before the story's January 2026, and the reference page the spec is written from (https://core.telegram.org/bots/api#sendmessage, Bot API 10.3) no longer documents it at all, as spec/SOURCE.md itself states; the act builds on a door the vendor withdrew, even though the server still reads it.",
+      "correction": "Act 7 sends the reply with reply_parameters (a JSON-serialized ReplyParameters naming the album's first message_id), as https://core.telegram.org/bots/api#sendmessage documents, and the 'What the story reaches' line says so."
     }
   ],
   "applied": {
-    "from": "7f1802b57b256e32061a52ede0d2972060c725a7550b068ac1ae23f131c63c6c",
+    "from": "4bdc79fa09692fb332a4eac8080c9a10e5d7b2234435712284ef4e599d37d4eb",
     "wasPlausible": false,
     "steps": [
-      "0",
-      "5",
-      "8",
-      "9",
-      "10"
+      "act 7"
     ],
     "rulings": [
       {
-        "id": "three-tuesdays-skipped",
-        "steps": [
-          "act 3",
-          "act 4",
-          "act 7",
-          "act 8",
-          "act 9",
-          "act 10"
-        ],
-        "barItem": "a stated cause that never happens, and a promise never kept",
-        "reason": "Act 3 sets the standup weekly on Tuesdays and makes the agent an administrator, which is sent every group message (https://core.telegram.org/bots/features#privacy-mode). Act 4 runs the first standup and digest on 6 January. The standups move to the call only on Monday 2 February (act 10). Tuesdays 13, 20 and 27 January fall within acts 7-9 with no standup, no poll and no digest. Act 10's digest then says that no items were posted \"this week\", as if earlier weeks had them.",
-        "correction": "Move act 10 to Monday 12 January, 18:00, so that the refused digest is Tuesday 13 January's. Or tell the three January Tuesdays' standups and digests."
-      },
-      {
-        "id": "postiz-never-given-token-n",
         "steps": [
-          "Who acts",
-          "act 5"
+          "act 7"
         ],
-        "barItem": "the wrong actor or credential for an act",
-        "reason": "Postiz posts to Telegram through the one bot its deployment configures, process.env.TELEGRAM_TOKEN (postiz-app e0a08a7, libraries/nestjs-libraries/src/integrations/social/telegram.provider.ts:19). In hosted Postiz, that bot is Postiz's own. The outline calls @tidelabs_news_bot, token N, \"Postiz's Telegram integration\", and in act 5 Ana makes the bot and Postiz then calls with it. The outline never says that she runs Postiz herself or that token N becomes its TELEGRAM_TOKEN.",
-        "correction": "In 'Who acts' and act 5, say that Ana self-hosts Postiz (docker compose, local storage) and sets its TELEGRAM_TOKEN to token N before she adds Telegram."
+        "why": "Act 7 sends the reply with reply_parameters (a JSON-serialized ReplyParameters naming the album's first message_id), as https://core.telegram.org/bots/api#sendmessage documents, and the 'What the story reaches' line says so."
       }
     ]
   }

package/dist/journeys/customer-life.verdict.json

@@ -1,133 +1,59 @@
 {
   "judge": {
-    "agent": "Claude Code (Claude Agent SDK), model claude-opus-5-5",
-    "name": "Contributor 106"
+    "agent": "Claude journey judge (Opus)",
+    "name": "Independent journey judge"
   },
   "authors": [
-    "Contributor 173"
+    "yueranyuan",
+    "Aaron (A-001)",
+    "Claude Opus 5.5",
+    "Codex"
   ],
-  "bar": "829132787d94a2d4",
-  "sha256": "f58ee4db9e9c90c0f87f6018cf370f00963898ae16e0d4e7069e6afca17a6cf3",
-  "judgedAt": "2026-10-02",
+  "sha256": "d4f45ec531a3cafd7ec746629b2fb110cf5bb5adb0664f52a5d279eaf7f59ad3",
+  "judgedAt": "2026-10-15",
   "plausible": true,
   "rulings": [
     {
-      "id": "three-tuesdays-skipped",
+      "id": "reply-to-message-id-era",
       "steps": [
-        16,
-        20,
-        22,
-        30,
-        58,
-        62,
-        66,
-        70,
-        73
+        61
       ],
-      "barItem": "a stated cause that never happens, and a promise never kept",
-      "reason": "Steps 16, 20 and 22 set the standup for 9:00 every Tuesday, with items posted in the group, and the agent promises the digest at 9:15. From step 19 the agent is an administrator, and an administrator is sent every group message (https://core.telegram.org/bots/features#privacy-mode, \"bot admins always receive all messages\"). The job runs once, Tuesday 6 January (step 30). The team keeps the group standup until Monday 2 February (step 70: \"the standups move to a video call\"), yet Tuesdays 13, 20 and 27 January pass inside steps 58-70 with no items posted, no poll and no digest. Step 73's digest then says \"No standup items were posted this week\", which implies the earlier weeks had items. Three of the four weekly runs the story promises never happen, and nothing in the story explains why.",
-      "correction": "Move the standups' move and the bot's removal to Monday 12 January, 18:00, after step 61. The job's next run, Tuesday 13 January at 09:15, is then the refused one, and the waits to Wednesday 14 January 16:00 and onward are adjusted. Alternatively, show the Tuesday standups of 13, 20 and 27 January: items posted, a poll, and a digest each week."
+      "barItem": "the wrong era: building on an API the vendor had deprecated by the World's date; a call through a door the vendor does not document",
+      "reason": "Step 61 (Monday 12 January 2026) replies to the album with the form field reply_to_message_id={album}. Telegram replaced that parameter in Bot API 7.0, December 29, 2023 (https://core.telegram.org/bots/api-changelog: 'Replaced parameters reply_to_message_id and allow_sending_without_reply in the methods ... with the field reply_parameters'), and the page the spec is written from (https://core.telegram.org/bots/api#sendmessage, Bot API 10.3) no longer documents it; spec/SOURCE.md admits the page 'no longer lists it' and patches it in. A step through a parameter the vendor withdrew two years before the World's date is rejected even where the twin answers it.",
+      "correction": "Step 61 sends reply_parameters={\"message_id\":{album}} (JSON-serialized ReplyParameters, as https://core.telegram.org/bots/api#sendmessage documents) in place of reply_to_message_id, keeping its expectation result.reply_to_message.message_id equals {album}."
     },
     {
-      "id": "postiz-never-given-token-n",
+      "id": "photo-sizes-order",
       "steps": [
-        33,
-        37,
-        40,
-        41,
-        42,
-        43,
-        45,
-        46,
-        47,
-        48,
-        50,
         59,
-        61,
-        63,
-        65,
-        67,
         69
       ],
-      "barItem": "the wrong actor or credential for an act",
-      "reason": "Postiz's Telegram provider calls with one bot, the one its deployment configures: `new TelegramBot(process.env.TELEGRAM_TOKEN!)` (libraries/nestjs-libraries/src/integrations/social/telegram.provider.ts:19, postiz-app e0a08a7; demand.json, Postiz's client: \"TELEGRAM_TOKEN\"). In hosted Postiz, that is Postiz's own bot and not one a customer makes. Step 33 has Ana make @tidelabs_news_bot \"for Postiz\", and from step 37 on Postiz calls with {news_token}. But no step or name says that Ana runs Postiz herself, or that token N is set as its TELEGRAM_TOKEN. The life never shows how the credential Postiz uses reaches it, and as written it reads as the hosted product calling with a bot that belongs to the customer.",
-      "correction": "In step 33 or a step beside it, say that Ana runs Postiz herself (docker compose, local storage, as demand.json reads it) and sets TELEGRAM_TOKEN to the news bot's token before she adds Telegram. Use the same wording in the outline."
-    },
-    {
-      "id": "running-harness-polls-without-offset",
-      "steps": [
-        76
-      ],
-      "barItem": "content that does not bear out the step's name",
-      "reason": "Step 76 is Harness \"still running on her laptop\". The adapter it runs keeps its offset in its polling loop and sends it on every poll: `offset = update.update_id + 1` (@chat-adapter/telegram 4.39.0, dist/index.js:3327-3345, pollingLoop; demand.json: \"confirming the last with offset\"). The life last confirmed one at step 53. Step 76's body, {\"limit\": 100, \"timeout\": 30}, is the request a freshly started adapter sends (step 9), not the request of the process the step names.",
-      "correction": "Step 76's body: {\"offset\": \"{agent_next}\", \"limit\": 100, \"timeout\": 30}."
+      "barItem": "vendor behaviour the vendor's documentation contradicts",
+      "reason": "Step 59 expects result.0.photo.0.width 480 and result.2.photo.0.height 300 for 480x300 PNG uploads, and step 69 expects result.photo.0.width 640 and height 480 for a 640x480 JPEG: the first PhotoSize being the uploaded image itself. Telegram 'attaches a vector of thumbnails with reduced resolution to all uploaded media', the smallest type s 'bounded by 100x100 pixels' and m by 320x320 (https://core.telegram.org/api/files, image thumbnail types; Message.photo is 'available sizes of the photo', https://core.telegram.org/bots/api#message), and the Bot API answers them in ascending order (TDLib at 42e6a52, td/telegram/PhotoSize.cpp get_photo_sizes_object, stable_sort by size then width*height, the TDLib source the spec cites). photo.0 is the 100-pixel thumbnail; the original's dimensions are on the last size.",
+      "correction": "Steps 59 and 69 expect the uploaded dimensions on the last PhotoSize (step 59: result.0.photo.2.width 480 and result.2.photo.2.height 300; step 69: result.photo.2.width 640 and height 480), with photo.0 the s thumbnail, bounded by 100x100."
     }
   ],
   "applied": {
-    "from": "1248e944117c27955453a626f8ed5a44ff07ad520f525feaa0a7a6dc53399963",
+    "from": "8251bda4592d9f3dae1bb5067727bee657d212ebd5aca36c32e8a7f4d1beb222",
     "wasPlausible": false,
     "steps": [
-      "33",
-      "36",
-      "62",
-      "70",
-      "71",
-      "72",
-      "73",
-      "74",
-      "76"
+      "59",
+      "61",
+      "69"
     ],
     "rulings": [
       {
-        "id": "three-tuesdays-skipped",
         "steps": [
-          16,
-          20,
-          22,
-          30,
-          58,
-          62,
-          66,
-          70,
-          73
+          61
         ],
-        "barItem": "a stated cause that never happens, and a promise never kept",
-        "reason": "Steps 16, 20 and 22 set the standup for 9:00 every Tuesday, with items posted in the group, and the agent promises the digest at 9:15. From step 19 the agent is an administrator, and an administrator is sent every group message (https://core.telegram.org/bots/features#privacy-mode, \"bot admins always receive all messages\"). The job runs once, Tuesday 6 January (step 30). The team keeps the group standup until Monday 2 February (step 70: \"the standups move to a video call\"), yet Tuesdays 13, 20 and 27 January pass inside steps 58-70 with no items posted, no poll and no digest. Step 73's digest then says \"No standup items were posted this week\", which implies the earlier weeks had items. Three of the four weekly runs the story promises never happen, and nothing in the story explains why.",
-        "correction": "Move the standups' move and the bot's removal to Monday 12 January, 18:00, after step 61. The job's next run, Tuesday 13 January at 09:15, is then the refused one, and the waits to Wednesday 14 January 16:00 and onward are adjusted. Alternatively, show the Tuesday standups of 13, 20 and 27 January: items posted, a poll, and a digest each week."
+        "why": "Step 61 sends reply_parameters={\"message_id\":{album}} (JSON-serialized ReplyParameters, as https://core.telegram.org/bots/api#sendmessage documents) in place of reply_to_message_id, keeping its expectation result.reply_to_message.message_id equals {album}."
       },
       {
-        "id": "postiz-never-given-token-n",
         "steps": [
-          33,
-          37,
-          40,
-          41,
-          42,
-          43,
-          45,
-          46,
-          47,
-          48,
-          50,
           59,
-          61,
-          63,
-          65,
-          67,
           69
         ],
-        "barItem": "the wrong actor or credential for an act",
-        "reason": "Postiz's Telegram provider calls with one bot, the one its deployment configures: `new TelegramBot(process.env.TELEGRAM_TOKEN!)` (libraries/nestjs-libraries/src/integrations/social/telegram.provider.ts:19, postiz-app e0a08a7; demand.json, Postiz's client: \"TELEGRAM_TOKEN\"). In hosted Postiz, that is Postiz's own bot and not one a customer makes. Step 33 has Ana make @tidelabs_news_bot \"for Postiz\", and from step 37 on Postiz calls with {news_token}. But no step or name says that Ana runs Postiz herself, or that token N is set as its TELEGRAM_TOKEN. The life never shows how the credential Postiz uses reaches it, and as written it reads as the hosted product calling with a bot that belongs to the customer.",
-        "correction": "In step 33 or a step beside it, say that Ana runs Postiz herself (docker compose, local storage, as demand.json reads it) and sets TELEGRAM_TOKEN to the news bot's token before she adds Telegram. Use the same wording in the outline."
-      },
-      {
-        "id": "running-harness-polls-without-offset",
-        "steps": [
-          76
-        ],
-        "barItem": "content that does not bear out the step's name",
-        "reason": "Step 76 is Harness \"still running on her laptop\". The adapter it runs keeps its offset in its polling loop and sends it on every poll: `offset = update.update_id + 1` (@chat-adapter/telegram 4.39.0, dist/index.js:3327-3345, pollingLoop; demand.json: \"confirming the last with offset\"). The life last confirmed one at step 53. Step 76's body, {\"limit\": 100, \"timeout\": 30}, is the request a freshly started adapter sends (step 9), not the request of the process the step names.",
-        "correction": "Step 76's body: {\"offset\": \"{agent_next}\", \"limit\": 100, \"timeout\": 30}."
+        "why": "Steps 59 and 69 expect the uploaded dimensions on the last PhotoSize (step 59: result.0.photo.2.width 480 and result.2.photo.2.height 300; step 69: result.photo.2.width 640 and height 480), with photo.0 the s thumbnail, bounded by 100x100."
       }
     ]
   }