fix(governance): restore fork overlay conformance - #13
Merged
Merged
Conversation
ragnos-dev
force-pushed
the
codex/hermes-conformance-contributor-20260721
branch
from
July 21, 2026 17:20
6fb5cef to
48296e3
Compare
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.
What does this PR do?
Removes the contributor email mapping added by PR #12 because that path is outside the governed RAGnos fork overlay. The Photon runtime changes remain intact.
Related Issue
Follow-up to #12.
Type of Change
Changes Made
contributors/emails/doctor@ragnos.io.hermes-upstream-conformanceproduction gate without widening its allowlist.How to Test
HERMES_UPSTREAM_FORK_PATHto this candidate worktree.just hermes-upstream-conformance --jsonfrom the RAGnos workspace.ok: trueandviolations: [].Checklist