The optional parameter sh:flags is ignored.
Apparently, there is no eye built-in capable of interpreting its values.
As a consequence, the following tests from the official suite fails:

• core/node/pattern-002.ttl
• core/property/pattern-002.ttl

An error is raised by the eye reasoner when trying to parse ill-typed literals like "aldi"^^xsd:integer.

As a consequence, the following tests from the official suite fails:

• core/node/datatype-001.ttl
• core/property/datatype-ill-formed.ttl
• core/property/or-datatypes-001.ttl

According to the spec:

each time a property shape is reached via sh:property, a validation engine MUST produce fresh validation result nodes. This includes cases where the same focus node is validated against the same property shape although it is reached via different paths in the shapes graph

The following tests likely fail for the above reason:

• core/property/lessThan-002.ttl
• core/property/property-001.ttl
• core/validation-reports/shared.ttl

The following test:

• core/node/minInclusive-003.ttl

fails due to a strange date offset issue (to be further investigated).

Result details are not produced. Not mandatory but useful.

The following official tests fail:

• core/path/path-alternative-001.ttl
• core/path/path-complex-001.ttl
• core/path/path-complex-002.ttl
• core/path/path-inverse-001.ttl
• core/path/path-oneOrMore-001.ttl

due to a minor issue with the validation report.
According to test requirements:

the blank node structures representing property paths via sh:resultPath must not be shared among multiple results, i.e. they may need to be cloned prior to comparison

The needed cloning is not performed, causing test failures.

The (non-official) test:

• custom/test19.ttl

fails, likely due to some Skolemization issue when dynamically loading a shapes graph