Repository navigation
ci: check docs-pipeline checkpoints and code examples [PANL-015] - #36
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bihc4e3Pg6Ago5K1xfMbe5
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.
Context
The review panel's docs engineer found that
ci.ymlonly tests the job-assessment pipeline, so the README claim of "a real gate between every stage" in the docs pipeline had nothing behind it. It also found no check on code examples. Ticket: PANL-015.Changes
check_pipeline.pynow also checks that the orchestrator calls every stage skill and that every stage summary ends in a "Proceed to ..." checkpoint. Removing a checkpoint makes it fail (tried by hand)..github/scripts/check_examples.pyparses every json, yaml and bash block in the Markdown docs (85 today, all clean). Saved model outputs undertests/are skipped.docs checksjob inci.yml.Review notes: the checkpoint is a prompt to the person running the pipeline, not code that blocks a stage, so the README wording "real gate" still overstates it. That sentence is the author's voice and is left for a separate edit.