fix(screenote): configure live integration endpoint - #37
Merged
Conversation
ivankuznetsov
temporarily deployed
to
screenote-integration
July 31, 2026 19:23 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
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.
Summary
The protected Screenote release gate can now reach production from a fresh GitHub runner. The first
3.1.0live run stopped before its first API request because the CLI requires a trusted base URL and the job supplied none. This configureshttps://screenote.aiin the protected job while keeping endpoint overrides out of agent-controlled arguments, and a scoped regression test locks that invariant.Validation
missing_base_urlin the pre-fix protected run.