Conversation
The hosted MCP endpoint is an external dependency we don't control, and the Phase 2 design leans on behavior verified in the #22 spike (including the undocumented X-MCP-Tools header). A scheduled run turns the e2e suite into an early-warning system for GitHub-side changes instead of only running when we push.
thepagent
approved these changes
Jul 13, 2026
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
2 participants
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
The e2e suite currently runs only on our own pushes to main — but its most valuable failure mode is detecting GitHub-side contract drift (tool renames like
get_issue→issue_read, session-semantics changes, header behavior), which arrives on GitHub's schedule, not ours. Phase 2 (#17) additionally depends on behavior verified in the #22 spike, including the undocumentedX-MCP-Toolsheader.Change
One hunk: add
schedule: cron "17 6 * * *"(daily, off-peak) to the existing triggers. Costs one short CI run per day; a red run means the upstream changed underneath us.Uses App-minted tokens (#23), so no long-lived secret is exercised by the schedule.