chore(metadata): record public-surface label remediations - #1642
Merged
Conversation
|
Warning Review limit reachedNext included review available in 2 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Outcome
Persist evidence-backed classifications already applied to live repository-facing work so organization metadata reconciliation remains declarative and idempotent.
This records reviewed classifications for the existing public-surface lanes, including:
.github#1579— feature/enhancement classification for the least-privilege repository-settings writer provisioning blocker;governance-risk-compliance#65,pingora-gateway#4,life-os#211, andscopeweave#650— documentation classifications for repository-facing docs/Pages work;newsdom-api#782— documentation classification for the README badge, MkDocs metadata, and current Pages landing refresh;kaefa#81— documentation classification for the active README/ADR writer, currently blocked in Draft while its source/generated README pair remains the canonical writer lane;kaefa#82— documentation classification for the isolated existinggh-pagespublic-site refresh.It also corrects the Keyverse assignment after writer consolidation: closed superseded child
keyverse#127no longer remains the desired target; active Draftkeyverse#103owns the folded README/DeepWiki/Pages source and is classified as the feature/enhancement lane it actually is. The stalestatus: needs-reviewlabel was removed from closed #127 andenhancementwas applied to #103 live.The exact-assignment contract test is extended in lockstep, preserving drift detection rather than weakening taxonomy validation.
Concurrency
This branch was created from protected
main@7683f1da91f1fc9e046660169f1f7ac4aabcc3c6after the workflow-Pages reconciliation repair had landed. It does not modify repository descriptions, topics, Pages settings, workflow credentials, or the still-open metadata desired-state wave in #1639. The new assignments are confined to the same taxonomy/test pair already owned by this PR. No force-push or destructive rebase is used.Verification boundary
The public-surface PRs are classifiable from their concrete files and product/docs intent, #1579 is an explicit owner-side settings-writer feature/provisioning task, and Keyverse #103 is the consolidated feature owner explicitly named by closed #127. Live labels were applied/re-read before recording the declarative assignments here. Merge only through normal protected governance after current-head checks and review are satisfied.