When archied starts after an installed release upgrade, notify authorized Telegram users once with an exact component-aware rundown from CHANGELOG.md. Present archied as THE GATEWAY and archie-agent as THE RUNTIME, explicitly saying when either component has no changes. Persist announced versions per recipient so ordinary restarts do not repeat notifications.
Acceptance Criteria
Repository has a maintained component-aware CHANGELOG.md. On an installed version advance, each configured authorized Telegram user receives one concise message with separate THE GATEWAY and THE RUNTIME sections and explicit no-change wording where applicable. Announced component versions are persisted and duplicate restarts do not repeat. First-run and development builds have explicit non-spam behavior. Parsing, version transition, persistence failure, and delivery failure paths are tested.
Close reason
Closed
Imported from beads archie-core-1786637498723-338-ca9b163b · GitHub #359 · type feature · priority P2 · created 2026-08-08 · closed 2026-10-01
When archied starts after an installed release upgrade, notify authorized Telegram users once with an exact component-aware rundown from CHANGELOG.md. Present archied as THE GATEWAY and archie-agent as THE RUNTIME, explicitly saying when either component has no changes. Persist announced versions per recipient so ordinary restarts do not repeat notifications.
### Acceptance Criteria
Repository has a maintained component-aware CHANGELOG.md. On an installed version advance, each configured authorized Telegram user receives one concise message with separate THE GATEWAY and THE RUNTIME sections and explicit no-change wording where applicable. Announced component versions are persisted and duplicate restarts do not repeat. First-run and development builds have explicit non-spam behavior. Parsing, version transition, persistence failure, and delivery failure paths are tested.
### Close reason
Closed
---
_Imported from beads `archie-core-1786637498723-338-ca9b163b` · GitHub #359 · type feature · priority P2 · created 2026-08-08 · closed 2026-10-01_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When archied starts after an installed release upgrade, notify authorized Telegram users once with an exact component-aware rundown from CHANGELOG.md. Present archied as THE GATEWAY and archie-agent as THE RUNTIME, explicitly saying when either component has no changes. Persist announced versions per recipient so ordinary restarts do not repeat notifications.
Acceptance Criteria
Repository has a maintained component-aware CHANGELOG.md. On an installed version advance, each configured authorized Telegram user receives one concise message with separate THE GATEWAY and THE RUNTIME sections and explicit no-change wording where applicable. Announced component versions are persisted and duplicate restarts do not repeat. First-run and development builds have explicit non-spam behavior. Parsing, version transition, persistence failure, and delivery failure paths are tested.
Close reason
Closed
Imported from beads
archie-core-1786637498723-338-ca9b163b· GitHub #359 · type feature · priority P2 · created 2026-08-08 · closed 2026-10-01