docs(openspec): propose cross-messenger progress updates#78
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds an OpenSpec change proposal to bring “live progress edit-in-place” parity to Slack and Discord (matching existing Telegram behavior) by defining optional adapter capabilities, platform-specific live client requirements, and a shared fallback ladder.
Changes:
- Adds a shared delivery/fallback model and implementation/test task plan for live progress updates across Slack/Discord/Telegram paths.
- Defines new OpenSpec requirements for optional adapter live-progress refs/updates plus Slack (
chat.update) and Discord (message edit) live client behavior. - Documents goals, risks, and migration plan for keeping per-destination live progress references in-memory and clearing them safely.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| openspec/changes/update-live-progress-across-messengers/.openspec.yaml | Declares the new spec-driven OpenSpec change and creation date. |
| openspec/changes/update-live-progress-across-messengers/design.md | Captures background, goals, decisions, fallback ladder, and risks for cross-messenger live progress updates. |
| openspec/changes/update-live-progress-across-messengers/proposal.md | Summarizes motivation, intended behavior changes, and impact areas (adapters, runtimes, live clients, tests). |
| openspec/changes/update-live-progress-across-messengers/tasks.md | Breaks the work into shared helper, Slack, Discord, parity/safety, and validation tasks. |
| openspec/changes/update-live-progress-across-messengers/specs/discord-runtime-client/spec.md | Adds requirements for Discord live client returning message IDs and supporting message edits with safe fallback. |
| openspec/changes/update-live-progress-across-messengers/specs/messenger-relay-sessions/spec.md | Adds system-level requirements for in-place live progress updates where supported, with snapshot fallback and mode semantics. |
| openspec/changes/update-live-progress-across-messengers/specs/relay-channel-adapters/spec.md | Adds adapter-contract requirements for optional live progress refs/updates and a consistent fallback invariant. |
| openspec/changes/update-live-progress-across-messengers/specs/slack-runtime-client/spec.md | Adds requirements for Slack live client returning ts references and supporting updates with safe fallback. |
Co-authored-by: Copilot Autofix powered by AI <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
chat.updateand Discord message edit requirementsValidation