ci(smoke): assert newly added docs routes after each R2 upload - #139
Merged
Conversation
Derive routes added in the dispatching run's commit range and probe them live alongside the fixed pages, so a dropped upload of a new page fails the smoke instead of 404ing silently (2026-08-27 why-openclaw incident). Adds a daily scheduled sampler that checks docs_map.md routes against the live site, and forwards range continuity through the head-drift successor dispatch.
This was referenced Aug 27, 2026
Merged
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.
Extends docs-live-smoke so each post-upload dispatch also asserts routes newly added by the commits covered by that r2-pages run, derived from the commit-range diff of added files under docs/ mapped to routes via a new scripts/docs-site/added-routes.mjs helper (mirrors build.mjs page-collection rules; deterministic 100-route sampling cap with logged truncation). A malformed range or failed fetch fails the run instead of silently skipping. r2-pages passes event.before..sha on push runs, forwards continuity through the head-drift successor dispatch via a new smoke_commit_range input, and the smoke workflow gains a daily scheduled sampler probing 25 deterministic docs_map.md routes against the live site. Fixed probes unchanged.
Motivation: 2026-08-27 incident where docs/start/why-openclaw.md was dropped from an upload and 404'd silently; the fixed-probe smoke structurally could not detect it.
Validation: 48/48 node tests, actionlint clean, and two manual dispatches on this branch: run 33076424857 (commit_range covering the incident sync commit) derived and asserted /start/why-openclaw live; run 33076645608 (no input) confirmed the legacy fixed-probe path unchanged.