Follow sluiceway v0.49.0: a Telegram message can go to one topic of a forum group

[robbeverhelst]

The docs follow sluiceway v0.49.0. Step 0 saw pin=v0.48.0 latest=v0.49.0 open_prs=0. The release has one change (#295): a Telegram notification can go to one topic of a forum group, with a new input telegram-thread-id (the topic's id, a whole number, sent as message_thread_id). A topic id that is not a whole number above 0 is a "Notification channel not used" warning, and the id is not masked in the log. No page moves, no heading moves, and no record, glossary term, picture, mode or schema key changes.

What it does

• The pin moves from v0.48.0 to v0.49.0: the submodule and the branch line of .gitmodules together (bun run pin: "vendor/sluiceway is at v0.49.0, and .gitmodules says so."). The build was green at the new pin with no mapping change. No check was weakened, and README_UNMAPPED is unchanged because the README has no new h2 (only its picture URLs and footer moved to the new tag).
• Nothing written in this repo names the new input, so no other file changes. The one sentence of this repo about Telegram, the Notifications description in pages.ts ("Opt-in messages to Slack, Telegram or a webhook when stacks are pending or a deploy fails, …"), stays true.

These arrive by themselves: the Notifications guide's new paragraph under Telegram ("To post in one topic of a forum group, add telegram-thread-id …") and its changed "When a send fails" sentence, the action reference's telegram-thread-id entry (from action.yml, with its own "On this page" link, anchor #telegram-thread-id), the new row in What v1 is (Names fixed for v1), and the changelog.

Now wrong on the live site (fixed here)

The live site pins v0.48.0.

Where	Before (live)	After
Start page, JSON-LD, footer	"Sluiceway v0.48.0", softwareVersion 0.48.0	v0.49.0 (all read the pin)
Notifications, Telegram	no way to post in one topic of a forum group	the telegram-thread-id paragraph
Notifications, When a send fails	the set-up-wrong examples end at "a Telegram token without a chat id"	plus "or a topic id that is not a whole number"
Action reference	no telegram-thread-id	its entry between telegram-chat-id and webhook-url
What v1 is	no telegram-thread-id row	the row, citing record 0078
Changelog	ends at 0.48.0	0.49.0

Checked and still right at v0.49.0: every description and title in pages.ts, the JSON-LD's operatingSystem and keywords, the start page's hero, steps and guide list, the example dashboard (only its picture URLs and footer moved to the new tag, and the site serves pictures from the submodule), the header page and gallery (no picture changed), the What it looks like walk-through (the renderer of the dashboard did not change; only src/render/notification.ts did), the Command line page (the fake app, the OpenAPI copy and every command are unchanged, so all 20 examples hold), the anchor redirects (no heading moved) and the water lines (src/render/voice.ts is unchanged).

Different at the real tag from the plan

#31 found no open PR in sluiceway/sluiceway and left no plan. Nothing to compare.

When the open action PRs are released

• fix: a tick made while a writer writes the body is written back sluiceway#298, "a tick made while a writer writes the body is written back" (record 0119, amends 0004, 0017 and 0025, changes the glossary's Stretch). What breaks: nothing expected. The record's page and index row, the "Amended by" lines on the three records and the changed glossary entry arrive by themselves, and the term keeps its name, so #stretch holds. What to do: check that the records index reads all three amendments; 0119 is not about Penny's pictures, so it keeps the mark and stays out of RECORD_PICTURES; check its long title in the sidebar and at 390 wide. Nothing written in this repo quotes 0017's request counts or the write loop (the hosted app's Install page says the app reads "the dashboard and its edit history", which stays true).
• docs: record the acceptance walk-through of 2026-10-06 sluiceway#296, "record the acceptance walk-through of 2026-10-06". What breaks: nothing. docs/acceptance.md has no page on the site, and the one docs/build-plan.md line it changes (the Marketplace listing, line 481) sits in a section What v1 is does not import. What to do: nothing on the site. The PR itself notes that docs/roadmap.md and docs/later.md still list the Marketplace listing as launch work; both pages import whole, so once the listing is real they will say so wrongly (see below).

Ambiguous or wrong

In the action's own text at v0.49.0, for the coordinator to pass on. New this release first; the files behind the older items did not change, so each one still holds.

• action.yml gives the notification inputs three modes, the other pages four. telegram-thread-id (like slack-webhook-url, telegram-bot-token, telegram-chat-id and webhook-url) starts "scan, resolve and apply", while docs/reference.md and docs/build-plan.md say scan, resolve, apply and auto. The action reference on the site reads action.yml, so it shows three.
• telegram-thread-id cites record 0078 in What v1 is, but 0078 says nothing of topics, and no record amends it. A small thing, but the row's "the record in the last column" promise does not hold for it.
• docs/roadmap.md lists "a listing on the GitHub Marketplace, a docs site" under the launch, and docs/later.md has "Docs site and Marketplace launch". The site is live, and docs: record the acceptance walk-through of 2026-10-06 sluiceway#296 says the listing is too.
• Record 0031 writes two amendments in one blockquote line.
• docs/using-the-dashboard.md quotes the busy row short.
• docs/command-line.md's preview example leaves out the Policies block the command prints.
• no-write-access has no line in the exit table.
• The README still does not link the Command line page.
• Records 0102, 0104, 0106, 0107 and 0109 still write no "Amended by" line on the records they amend, and record 0095's seven amended records still do not say so.
• Record 0113's lead lacks a full stop; record 0047's lead has a date and no record; record 0094 is "Amended by slice 5.32".
• Top-level cost in the schema has no description; recordWriters' description ends "Empty hands none on."; action.yml's env-file wraps "relative to the" onto its own line.
• docs/init.md still does not mention Terraform; workflow.md#the-workflow still points at the page title from 11 links; link text that is a file path in docs/using-the-dashboard.md.

How I verified

• DOCS_SITE=https://docs.sluiceway.dev DOCS_BASE=/ bun run check (lint, tokens, pin, release, astro check, build, tests) passes: 737 pass, 0 fail, 0 errors, 0 warnings, 0 hints. The build's only warning is the one main has too (the empty i18n collection). bun run release: "vendor/sluiceway pins v0.49.0, the action's latest release."

• Under both addresses, / and the default /docs: build, bun test (737 pass) and bun run links ("Checked 33834 links on 152 pages. All of them land." under each).

• Lighthouse, locally with bun run lighthouse (the repo's lighthouserc.json, a production build under /, phone, median of three). No assertion failed, and all four scores are 90 or more on every audited URL:

  URL	Perf	A11y	Best practices	SEO
  /	99	100	100	100
  /get-started/	99	100	100	100
  /guides/configuration/	98	100	100	100
  /guides/notifications/	99	100	100	100
  /guides/policies/	99	100	100	100
  /guides/workflow/	99	100	100	100
  /reference/sluiceway-yaml/	99	100	100	100
  /reference/what-sluiceway-writes/	99	100	100	100
  /the-header/	99	100	100	100
  /using-the-dashboard/	99	100	100	100
  /what-it-looks-like/	99	96	100	100

  What it looks like still scores 96 on accessibility, for the same two <summary> folds under 44 pixels as since docs: follow sluiceway v0.42.1, a policies page and redirects for two renumbered records #20.

• Screenshots: Playwright (global install), Chromium, 1280 and 390 wide, light and dark via prefers-color-scheme. Four URLs (Notifications, the action reference, What v1 is, the start page), each scrolled to the end first so lazy pictures load, then checked: no sideways scroll and no broken picture in any of the 16 views. The start page and its JSON-LD say v0.49.0.

  • Notifications, the Telegram section, dark, 390 and light, 1280: the new paragraph, telegram-thread-id: 56 fits at 390. The whole page, dark, 1280.
  • Action reference, telegram-thread-id, light, 1280 and dark, 390.
  • What v1 is, light, 390 and dark, 390: the names table scrolls inside itself, the page does not.

Decisions no record covers

• No page of this repo's own gains a word on topics. The Notifications guide imports the action's paragraph whole, and the page's description names the channels, not their inputs, so a sentence here would only repeat it.

Follow-ups

• The hosted app's org view and the busy row: a word from the app's side on whether the console counts a busy="true" row as busy or as preview failed, then one sentence on Using the app. Carried from Follow sluiceway v0.48.0: a busy stack, a second try, and the failing header's alt text #31.
• The two <summary> folds of the example dashboard on What it looks like are under 44 pixels tall (Lighthouse, 96). A min-height on summary inside .sw-issue would fix it. Carried from docs: follow sluiceway v0.42.1, a policies page and redirects for two renumbered records #20.
• The action reference leaves a camelCase key without a dot as prose, such as "envFile" in the env-file description. Carried from docs: follow sluiceway v0.42.1, a policies page and redirects for two renumbered records #20.
• docs: a Command line page for sluiceway v0.45.0, its commands, their --json answers and exit codes #23's owner note still stands: What the app keeps says "The app keeps no token of yours, so it cannot act as you", while personal tokens let the command line act as the person.
• A no-write-access example, once the action's page says what it means and how it exits.

🤖 Generated with Claude Code