#135595 made destructive_root_rm check every rm operand, not only the
first. That loop also accepted a bare `//` token later on the line, so a
JS/JSONC comment after the command matched as a delete rooted at `/`:
rm -rf node_modules dist // clean -> critical (was clean)
"rm -rf *": "deny", // Block recursive deletes -> critical (was clean)
The second line is the permission example in
igorwarzocha/opencode-workflows' opencode-config skill, which went from
caution to dangerous (no override) on main.
A bare `//` after the first operand is now skipped; the operands after
it are still checked (`rm -rf build // /etc` stays critical) and a
first-operand `//`, `//etc` or `/` stays the root.