Support for SHACL-SPARQL:

support for nodes (minus comprehensive error checking).
property constraints.
Create an aggregate repository to contain both the data graph and the shapes graph, named by the location of the first shapes graph found. This is makes it available to a SPARQL query using shapesGraph.
No support for SHACL-based Constraint Components yet, just SHACL-based Constraints.

Additional:

Use parameter definitions for constraint components when transforming from JSON.
Normalize qualifiedValueShape parsing and dispatch.
Collect operator/component parameters and add as operands, rather than relying on options flow-through. This moves towards better support for components with multiple and optional parameters.
Use SHACL::Error instead of ArgumentError in most places.
Allow logger to be set in SHACL::Shapes#execute, which is the result of parsing the shapes graph.