Valiemon 0.05 fails boolean, nested-schema, and dynamic-loading tests on both backends

Start by running the focused cases in t/01-attr-primitives.t, t/02-attr-required.t, t/03-attr-format.t, and t/03-attr-oneOf.t on both backends. Trace the shared runtime handling for Types::Serialiser booleans, schemas without properties, nested oneOf schemas, and loading Valiemon::Attributes::Format. Done means all 25 upstream test files and 142 tests pass on both backends, with focused regression coverage for these failures.

Summary

Valiemon v0.05 fails six upstream subtests under PerlOnJava even though its complete upstream suite passes under system Perl. The failures reproduce on both the JVM and interpreter backends and cover boolean classification, nested schema properties, dynamic attribute loading, and oneOf validation.

Observed in CPAN random tester run 20260916-111623-23683.

Reproduction results

• System Perl 5.42.2: all 25 test files and 142 tests pass.
• PerlOnJava JVM backend: the archived run reports 6 failed subtests; focused reruns reproduce the failures.
• PerlOnJava interpreter backend: the same focused failures reproduce.

The affected upstream tests are:

• t/01-attr-primitives.t
• t/02-attr-required.t
• t/03-attr-format.t
• t/03-attr-oneOf.t

Most of the remaining suite passes, including context, validator, type, collection, reference, draft, and other attribute tests.

Observed failures

Boolean classification

is_boolean and is_boolean_perl reject boolean values supplied by Types::Serialiser, including the values tested through Types::Serialiser::true and Types::Serialiser::false. The failures are present on both backends. The suite's TODO checks for weak numeric typing are separate from these non-TODO failures.

Required schemas and nested properties

t/02-attr-required.t aborts while validating a schema that has required but no properties member:

`properties` must be an object at /properties

The same error appears in t/03-attr-oneOf.t for a nested schema with properties, reported at /oneOf/properties. This points to incorrect nested-hash dereference/autovivification or schema handling in the shared runtime. The upstream implementation behaves correctly under system Perl.

Dynamic attribute loading and version handling

use Valiemon::Attributes::Format fails with:

Invalid version format

After the import failure, the test falls through to the base Valiemon::Attributes::is_valid method and reports that the method is not implemented. This indicates a PerlOnJava module-loading/version-resolution problem rather than a format-validation result.

Dependency and environment context

Valiemon is pure Perl. The test run used its normal dependencies, including Class::Accessor::Lite 0.08, Data::Validate::URI 0.07, List::MoreUtils 0.430, and Types::Serialiser 1.01. NetAddr::IP 4.079 appears as an XS dependency of the URI validation stack and was handled by the PerlOnJava fallback, but none of the reported failures is an XS-load error or a missing service/platform prerequisite. Reverse-dependency analysis is not applicable to the pure-Perl target distribution.

Acceptance criteria

• All 25 upstream test files and 142 tests pass on the JVM backend.
• The same suite passes on the interpreter backend.
• Types::Serialiser booleans are recognized consistently by is_boolean and is_boolean_perl.
• Schemas without properties do not acquire an invalid property structure during validation, and nested properties schemas work through oneOf.
• Valiemon::Attributes::Format loads without an invalid-version error and its date-time tests execute normally.
• Add focused project-owned regression coverage for the boolean, nested-schema/autovivification, and dynamic module-loading cases.