> Users do have access to its from a shared_context block. I don't see a spec here for that, but I'm convinced that works due to how shared_context works. (Feel free to add a spec to verify; really that would be a good idea).

Ooops.  Thanks. I definitely confused the `SharedContext` module with the `shared_context` method. I added a test for `shared_context` and, separately, confirmed that it worked without sending the `:include` to `SharedContext`.

> The RSpec::SharedContext module needs to have an its method for it to be available in that context, so you have to include your module for that to work. Does that make sense?

Yes and no. :-)  I apologize if I'm missing something here (again!) and I'm not going to hold up the merge for this, but I was just thinking that in the same way that a user expects their `extend` API call to result in the method being added becoming available within a `shared_context` block as well as `ExampleGroup` proper, they would also expect it to become available in `SharedContext` with no other action on their part being required.