Repository navigation
docs: reconcile 10 distinct first-party authority defects across active issues - #484
Merged
Knapp-Kevin merged 5 commits intoOct 29, 2026
Merged
Conversation
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.
Purpose
Reconcile live first-party authority debt across the passive catalog and curation status, without altering any skill, source pin, provenance, verification, scanner state or corpus denominator.
Exact scope
CURATION_QUEUE.md: distinguish P1: gate five first-party recurring-scan skills on explicit scheduling and data-access authority #478 (5 recurring-scan skills, draft fix: require explicit host authority for five recurring review skills (#478) #480), P1: require separate authorization for four additional first-party recurring review procedures #481 (4 other recurring-review skills, draft fix: gate four additional recurring review skills on explicit host authority (#481) #482), and new P1: remove obsolete permission-tier and source-trust scoring contracts from two first-party security skills #483 (2 legacy permission-tier/source-trust defects, no implementation).docs/SYSTEM_STATE.md: make the overlap explicit:permissions-reviewappears in P1: require separate authorization for four additional first-party recurring review procedures #481 and P1: remove obsolete permission-tier and source-trust scoring contracts from two first-party security skills #483, so 10 unique current-main affected first-party manifests, not 11.INDEX.md: surface the same truthful live blockers in the passive catalog.Accounting: 44 first-party, 826 third-party exact-version reviews, 870 total verification YAML records (previous independently established corpus count); 0 source admissions, 0 denominator delta, 0 new package reviews. README and index.json remain unchanged because their inventory/accounting values have not changed. All five public surfaces were read on the branch and checked for consistency; no five-surface count transition is required.
Lifecycle and acceptance
All five open PRs #412, #413, #416, #480, #482 remain drafts pending external exact-package security evidence and independent acceptance. This documentation-only PR is disjoint from their skill/registry branches, introduces no security/behavioral pass, and requires no repository-owned CI/scanner/runtime. The underlying ten current-main skill defects remain open; the two scheduling repair PRs have not merged. Current governance controls over historical tier language.
No issue closure is claimed. No external scan or behavioral test ran.
Issue #483 contains the two-skill exact-blob defect evidence and bounded correction.