fix(screenote): publish existing images without browser - #34
Merged
Conversation
ivankuznetsov
had a problem deploying
to
screenote-integration
July 30, 2026 18:30 — with
GitHub Actions
Failure
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
Allow
/screenoteto publish explicitly named PNG/JPEG files without startingbrowser automation or requiring viewport verification.
Fresh page captures still use the verified browser workflow. Existing files use
a separate fail-closed preparation path because there is no browser viewport to
verify.
What changed
existing_imageas a supported Screenote input mode.prepare-existing-imagehelper that:symlinked, changing, and non-regular sources;
0600file in a mode-0700directory;screenshot createcommand.
or other remote metadata.
evaluations, and lint mutation fixtures.
Why
Viewport verification proves that a newly captured page matches the requested
desktop, tablet, or mobile dimensions before publication. An existing image has
already been captured, so forcing browser startup adds no integrity signal and
can block a valid upload when the browser runtime is unavailable.
The replacement check is deterministic local validation plus an isolated
private copy. This preserves the original safety goal without coupling existing
image publication to Browser Use startup.
Validation
python3 -m unittest discover -s tests -q(72 tests)bash plugins/screenote/evals/lint-skills.shbash plugins/screenote/evals/lint-skills-test.shpython3 scripts/generate-agent-packages.py --checkpython3 scripts/validate-agent-packages.py --inventorypython3 -m py_compile plugins/screenote/scripts/screenote_flow.pybash -nfor changed Screenote shell scripts