fix(ci): a failed yarn run is not a dependency install (#359) - #360

Closes #359.

The bug

yarn classic ends every command with info Visit https://yarnpkg.com/en/docs/cli/<cmd> for documentation about this command., and node_dependency_install matched the bare host yarnpkg.com. So a failed yarn run prettier / yarn lint / yarn test scored a dependency verdict on a documentation link and the maintainer was told to reconcile a lockfile.

facebook/react's "Run prettier" step, run 29335289512, failed because a file wasn't formatted. The footer was /cli/run, not /cli/install. Reproduces identically on 0.6.1 through 0.7.1:

node_dependency_install  0.53  ['info Visit https://yarnpkg\.com']

Here node_dependency_install and javascript_lint each match exactly one witness (the footer vs prettier), and the dependency rule wins the tie on rule order.

The fix

One regex in classify.py: pin the footer to the two subcommands that are a dependency operation (install, add). The run/lint/test footers no longer match, so the log's real prettier witness wins:

javascript_lint  0.53  ['prettier']

Real yarn install failures keep their /cli/install footer (and the older /lang/en/…/install form), plus their other strong signals — untouched.

Evidence

• Narrowness: the other five real logs I swept (scipy, tokio, duckdb, vue, polars) classify identically before and after — zero collateral.
• Regression test tests/test_yarn_run_footer_notice.py: the react excerpt → javascript_lint; the footer line alone is no longer a dependency verdict; and a negative subtest keeps install / add / /lang/en/…install footers landing node_dependency_install.
• Mutation-check: reverting the regex turns the two false-positive assertions red.
• Benchmark 221/221, top-1 1.0 unchanged (no new fixture, no new class). Real-log excerpt committed at examples/real-world/react-29335289512-excerpt.log; benchmark page and CHANGELOG updated.