ci: omp compatibility probe (POAM R-01) — safe omp bumps#67
Merged
Conversation
A scheduled (weekly) + on-demand (workflow_dispatch) workflow that bumps omp to the latest (or a chosen version) ON A BRANCH and runs the full suite plus the two correctness keystones: the FAIL-CLOSED gate test (kill the sidecar mid-call → gate must block) and the BYTE-STABLE frozen-prefix check (demo02_prefix_hash). Also runs root+desktop tsc, the desktop suite, and the scanner pytest. Green → opens a ready-to-merge bump PR (master untouched; a human reviews the omp seam changes and merges). Red → files a tracking issue and leaves the safe pin in place. Never auto-merges. This is the safe path to adopt omp's reliability fixes without gambling the gate or the prefix on hundreds of unreviewed commits. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
mlcyclops
added a commit
that referenced
this pull request
Jun 24, 2026
…e-gated bumps) (#69) Formalizes the shipped policy: exact-pin all four @oh-my-pi/* at the tested baseline 16.0.6 (PR #49), and bump only via the compatibility probe (PR #67) that runs the full suite + both correctness keystones on a branch, opening a ready-to-merge PR on green and filing an issue on red. Never auto-merges. Closes the loop with invariant #1 (extend, never fork) and POAM R-01/R-10. Co-authored-by: mlcyclops <mlcyclops@users.noreply.github.com> 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.
Stands up the compatibility CI from POAM R-01 so you can adopt omp's reliability fixes without risk.
What it does
A scheduled (weekly Monday) + on-demand (
workflow_dispatch, with an optional version input) workflow that:demo02_prefix_hash(KV-cache stability).Red → files a tracking issue and leaves the safe pin in place.
It never auto-merges. The sidecar is zero-dependency, so the job just needs
pythonon PATH (added via setup-python) for the gate test.How you'll use it
When you want to upgrade, trigger it from the Actions tab (optionally pin a specific version). If it's green, merge the bump PR it opens. If red, you'll have an issue telling you which keystone omp broke — so you stay on 16.0.6 safely.
YAML validated. Pairs with #49 (the exact-pin).
🤖 Generated with Claude Code