feat: Telegram guardian verification flow (setup + inbound command)#6655
Merged
Conversation
Co-Authored-By: Claude <noreply@anthropic.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f933952568
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Contributor
Author
|
Addressed in #6664 |
ashleeradka
added a commit
that referenced
this pull request
May 13, 2026
…s) (#30642) The enrichment script added in #30639 was meant to inject magic-word Linear identifiers into cherry-pick PR bodies so the Linear Release CLI could extract them from the squash commit. Empirical testing against Linear's GraphQL API proved this is unnecessary: when the CLI passes `pullRequestReferences` to `releaseSyncByAccessKey`, Linear's server resolves each PR to its Development- panel-linked issues and stamps the release with them, regardless of whether any Linear identifier appears in commit text. The cherry-pick squash commit already contains `(#NNN)` references to each original main PR, which the CLI extracts as `pullRequestReferences`. Linear's server then finds each main PR's linked issues via the Development panel and attaches them to the release automatically. Test case: PR vellum-ai/vellum-assistant-platform#6655 has Dev-panel attachment ATL-545 and zero LUM/ATL/JARVIS-N mentions in its title, branch, body, or commit message. Calling `releaseSyncByAccessKey` with only `pullRequestReferences: [#6655]` (no `issueReferences`) produced a release stamped with ATL-545. Repeating the test with PR #6708 (LUM-1536 linked) produced a release stamped with LUM-1536. The resolution is purely server- side via attachment records. Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
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
1 participant
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.
Implement end-to-end guardian verification for Telegram channels.\n\n## Changes\n- Add /guardian-verify command intercept in channel-routes.ts\n- Add guardian_verification IPC handler in daemon config\n- Update Telegram setup SKILL.md with guardian verification step\n\nPart of #6644