canary: add render leg (covers the secretless browser/media worker on the paid path)#457
Merged
Merged
Conversation
…d on the paid path
The paid canary had no render/screenshot/media leg, so it verified payment +
gateway but NOT the secretless browser/media worker (F02/F04/F06) the render
route now dispatches to. Add a render leg: POST /api/render {url:example.com},
$0.02, asserts rendered:true + a stable "Example Domain" title + non-empty
content. A 200 proves the live main->worker hop + Chromium render + extraction
end-to-end on the paid path; a worker outage 5xx's and the canary treats that as
an upstream warning (payment settles pre-handler), not a buying break.
test-canary-coverage.js locks the leg (exists, POSTs a url, priceUsd matches the
advertised $0.02, check accepts the happy path and rejects non-rendered /
title-mismatch). 140 passed. example.com is IANA-reserved so the title is stable.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.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.
Adds a render leg to the paid canary so the secretless browser/media worker (F02/F04/F06) is exercised on the paid path, not just payment + gateway.
POST /api/render {url: https://example.com}, $0.02, assertsrendered:true+ a stable "Example Domain" title + non-empty content. A 200 proves the live main->worker hop + Chromium render + extraction end-to-end.test-canary-coverage.jslocks the leg (exists, POSTs a url, price matches the advertised $0.02, check accepts the happy path and rejects non-rendered / title-mismatch). 140 passed offline.Note: the canary workflow runs on
ref main, so this leg only takes effect once merged.