* Shell commands that name a protected in-project path need a person, unless the
read-only check accepts the command (also each part of a `;` / `&&` / `||`
sequence, with `cd` and output-discarding redirects allowed). Paths are matched
as written and from the shell's current folder, with wildcards expanded.
Running a protected file is not a change to it.
* `git config` commands that change a setting need a person, except plain ones
that only label commits or pick a default (user.name, user.email,
init.defaultBranch, core.autocrlf, pull.rebase, color.ui). Reads are unaffected.
* Protected list gains git's own settings (.git/config, .git/info/attributes,
.git/modules/, a .git file), conftest.py at any depth, more CI files
(azure-pipelines.yml, .travis.yml, Jenkinsfile, bitbucket-pipelines.yml,
.buildkite/), .vscode/launch.json, and .npmrc / .yarnrc / .yarnrc.yml.
* File-tool writes are also checked against where the path really lands on disk,
read the way the operating system reads it; a location that can't be worked out
counts as protected.
* Corpora: gate-133..gate-141 added; danger-022 (a global git config change) moved
out of the reviewer corpus because the gate now sends it to a person.
* scripts/measure_protected_paths.py replays recorded runs and counts what newly
needs a person.