To perform deeper refactoring a unit test suite will be useful.

I like to make explicit the distinction between the specs which document
the public API (tagged as :public) and those which are only refactoring
guards and can be changed when necessary (tagged as :protected or
:private depending on how stable they are intended to be).

The 'spec:public' and 'spec:development' Rake tasks reflect
that distinction.

Minor fix missing link in testing documentation

This will allow later to store the hooks content in the runner.

Minor use parens in multiple arguments method calls
Minor use parens in non-tivial method calls

The DreddHooks::Methods exposes the public DSL of DreddHooks.
As an interface, I would like it to be as simple as possible,
and as immutable as possible.

Since the DSL and the runner were closely related already, the latter
seems to be a good place to store the hooks that need to be runned.

Also, because the DSL is an interface for the runner, I prefer the
dependency to go from the interface to the runner, that the contrary.

Finally, I made the runner a Singleton because it was already unique
when defined as a Module, and because it make trivial its retrieval
from the DSL.

Isolating them will make clearer the dynamic method generation in
the next DRYing step.

Isolating them will make clearer the dynamic method generation in
the next DRYing step.

… hooks

…on hooks

The default values are clodely related to their setters anyway, so
they can be generated in place at the price of very little duplication.