Public OSS projection update - #10
Closed
jearonwong wants to merge 25 commits into
Closed
Conversation
added 25 commits
June 6, 2026 19:12
Contributor
Author
|
Superseded by PUBLIC-OSS-CLEAN-PROJECTION-RECOVERY-AUDIT-AND-CONTAINMENT-01. This PR carried the mistaken Public-repo governance/process-chain projection path; Public OSS should receive a regenerated clean projection PR from Dev-side projection policy instead. Closing without merge; branch deletion/cleanup is intentionally deferred to a separate owner-authorized cleanup plan. |
jearonwong
deleted the
codex/owner-authorize-public-oss-projection-pr-merge-execution-01
branch
June 9, 2026 05:16
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.
Summary
This PR carries the owner-authorized public OSS projection merge result through the GitHub protected-branch path after direct push to
mainwas rejected by branch protection.Source branch carried forward:
codex/public-oss-projection-protected-merge-decision-01at0741c5915ebc330013fbb4f85cbcb6878fc38d35.Blocked direct push reason: GitHub protected branch policy requires changes through a pull request and required check
Build Docusaurus.Release/projection evidence chain includes public projection plan, execution, branch review, branch/release/proposal baseline, protected merge decision, blocked direct merge execution evidence, and this PR-path execution record.
No tag, seal, GitHub release, npm publish, PyPI upload, registry mutation, branch cleanup, Website deploy, Validation Lab publication, downstream sync, Dev mutation, or V1 mutation is included. Website/Lab pointer sync remains a separate follow-up after remote
mainactually receives the projection.