Telegram Send

2026.09.19.2

Changed

• Repo-wide maintenance release: version bump to republish the current source. No schema change.

2026.09.17.1

Changed

• Repo-wide maintenance release: version bump to republish the current source. No schema change.

2026.08.20.1

Added

• sendVideo — send a video by https URL, Telegram file_id, or local file path (multipart upload), with optional width/height so Telegram sizes the player correctly instead of guessing the aspect ratio. Mirrors sendDocument exactly: same local-vs-remote branch via isLocalPath, the same sentMessage resource mapping, and the same token-redacting error path.

  This closes a drift rather than inventing a feature: the method had been running in the homelab's own in-repo copy of the model (the printer-timelapse workflow calls it) but was never carried back into this published package, so registry consumers could not send video at all.

• Fixture fixtures/sendVideo.json plus two tests — a contract test pinning the sentMessage mapping, and one asserting width/height actually reach the wire and are omitted when not supplied. The fixture is doc-derived like every other file in fixtures/; no live capture (see PROVENANCE.md).

• Test helper withEnvelopeCapturing — records each request's decoded JSON body so a test can assert what went ON THE WIRE, not just what came back. The existing withEnvelope discards the request, which would have let a dropped width pass unnoticed.

Still missing

• sendRichMessage remains un-ported from the in-repo copy — tracked as telegram-send-hardening-richmessage-port. It is a much larger surface (block-based article formatting plus multipart attach:// media) and is deliberately left to its own change.

2026.08.01.1

Security hardening: closes the HIGH bot-token credential-leak tracked below as a "Known gap" in the Unreleased entry (filed and planned as the issue-lifecycle model telegram-send-hardening-richmessage-port).

• Added a module-private redactToken(message, token) pure helper to telegram_send.ts. It replaces the live /bot<token>/ URL segment with /bot<redacted>/, then applies a generic /bot[^/]+/ regex backstop so any /bot.../ path segment is scrubbed even if the token reaches the message reformatted (re-cased, percent-encoded, or otherwise transformed) rather than byte-for-byte. message is accepted as unknown and safely coerced to a string — a fetch rejection is not guaranteed to be an Error with a string .message (it may be a DOMException, a thrown string, or an arbitrary non-Error value) — so no unsanitized shape can pass through unredacted.
• telegramJson and telegramMultipart now wrap their fetch() call in try/catch: a network-layer rejection (DNS failure, TLS error, connection reset) is caught and rethrown with its message redacted via redactToken, preserving the original rejection as cause for downstream diagnostics. Only the fetch() call itself is wrapped — the ok:false API-error throw (never carries the token, pinned GREEN and covered by property test c) is untouched.
• Behavior-preserving otherwise: legitimate sends and the ok:false API-error path are unchanged.
• Tests: flipped the two adversarial suite's former "HONEST GAP pin" tests (telegram_send_adversarial_test.ts, telegramJson/getMe and telegramMultipart/sendPhoto) to assert the fetch-rejection message is now redacted (contains /bot<redacted>/, excludes the raw token, preserves .cause) instead of asserting verbatim propagation. Added direct redactToken unit tests: exact-token redaction, token-free passthrough, the generic backstop for a reformatted token, and non-Error/DOMException/ thrown-string/plain-object coercion (including a case where a non-Error value's own string form embeds the token). All 72 suite tests green; property suite green at FC_NUM_RUNS=5000.
• README.md: updated the Security note — the token-in-URL fetch-rejection gap is now redacted rather than an open gap.
• quality.yaml: the byte-frozen-source justification no longer applies (source is modified); ratchet re-measured live.
• Deferred, tracked separately: porting sendRichMessage from the homelab dev copy is OUT OF SCOPE for this security fix (its homelab source-of-truth is not in this read-only snapshot, so folding it in would be a blind, unverifiable port). It remains tracked by the issue-lifecycle model telegram-send-hardening-richmessage-port as a follow-up.

Release 2026.07.16.2 — align model versions with manifests

Maintenance release across the @magistr extensions. For most packages this carries no functional change: the only edit is the model's version: field, brought back in line with its manifest version so the published model type version and the package version no longer drift.

Functional changes in this release are limited to:

• anime-cron: normalizeTitle now strips a ": subtitle" suffix and a trailing parenthesized year before comparison, fixing dedup false-misses where the torrent title carries a subtitle or year that the AniList romaji does not.

• arckit: first publish. Standalone ArcKit port — a 12-phase architecture governance state machine with 65 bundled templates, driven by a bundled skill.

Also tracks three extensions (kaiten, observability-agent, music-library) that previously existed only as untracked working-tree directories, recovered from stashes.