Typed Criteria query API on JavaRepository (intent glue foundation)

[delchev]

What

Adds a typed, fluent Criteria query API to the client-Java JavaRepository, so glue and hand-written client code can filter rows type-safely instead of hand-writing HQL.

repository.findAll(Criteria.create()
    .lt("dueOn", today)
    .eq("status", "ACTIVE")
    .orderByDesc("dueOn"));

This is the query surface the declarative-glue catalog needs — e.g. a scheduled "find overdue loans" activity (see engine-intent/CLAUDE.md → "Planned: declarative glue", Tier 1 #3).

How

• Criteria (in data-store-java's repository package, next to JavaRepository — the package client code already imports from): eq/ne/gt/ge/lt/le/like/between/in/isNull/isNotNull + orderByAsc/Desc. Renders to an HQL fragment + a named-parameter map.
• Safe by construction: values are bound as named parameters (never inlined); property names are validated to plain (optionally dotted) identifiers, so eq("status; drop table", …) throws.
• JavaRepository.findAll(Criteria) → JavaEntityStore.findAll(type, criteria), which builds from <entityName> … and reuses the existing map-projection query(...) path (returns typed T). No new Hibernate plumbing, no new module dependency.

Testing

CriteriaTest (4 cases, unit-level, no DB) covers AND-combination + parameter binding, BETWEEN/IN/null checks, and the injection-rejection guard. Run green locally (Tests run: 4, Failures: 0).

🤖 Generated with Claude Code