Repository navigation
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.
Closes #1220. Implements the rows from the issue thread, with the scanner split from the discussion with @ottosulin folded in, in
1.02-dev/en/.Scope
Appends 9.3.10 to 9.3.14 to C9.3, adds one sentence to the C9.3 objective covering skill metadata and instructions (the point 3 discussion, so no row for it), adds a Skill glossary entry and the Appendix B rows. Nothing is renumbered and no existing requirement changes.
Compared to my first pass in the issue, two things changed. 9.3.10 now accepts review by a human or an org-approved scanner, and the new 9.3.14 (L3) requires human review for skills that bundle scripts or request tool permissions. 9.3.12 lets an admin-defined policy grant permissions, but says a scanner verdict on its own doesn't count, so the thing asking for a permission still can't be the thing granting it (same logic as 10.4.7).
Notes
Levels follow the client survey in the issue: pinning exists today only in installers, and no client I found re-approves a skill when its content changes, so 9.3.11 is L3. Happy to adjust wording or levels if anyone sees it differently.