1. All spec files should have `require 'spec_helper'` as the first line.  There's configuration there that we want loaded, even when running one spec file in isolation.
2. I know you made this it's own spec file named after the issue because there's that pattern elsewhere in the rspec-mocks specs, but I'm not a fan of doing this.  I'd much rather have this in the `any_instance_spec.rb` file, so that when someone is making changes to the `any_instance` implementation code, they just have that one spec file to run in their inner TDD loop, and don't have to hunt around for other files to run.

The pattern of creating a spec file for an issue was around long before I started working on rspec, and I suspect it originated in the days when rspec didn't support example metadata.  I think what I'd like to see instead is tagging examples or example groups with `:issue => 229` as a way of documenting what issue a particular example originated from.

Actually, it would be a pretty cool re-organization project for someone to go through and re-organize the `bug_report_xxx_spec` files using this strategy.  (Although, I wonder if those bug numbers are from the old lighthouse issue tracker, not github....).