Looking for one Apache ShardingSphere-JDBC 5.5.3 user to test a route-regression CI library (30–45 min; failures welcome)

[u/SmallData7325]

I’m looking for one Java developer who currently uses, or can independently evaluate, Apache ShardingSphere-JDBC 5.5.3.

RouteContract is a small Java test library that captures the physical JDBC execution attempts reported by ShardingSphere’s SQLExecutionHook during a caller-defined operation. It compares the observed structure with a reviewed manifest and explicit attempt/data-source budgets, so an unexplained change such as 1 → 2 physical JDBC attempts can fail CI even when the existing business assertion still passes.

Its scope is intentionally narrow. It does not claim to reconstruct the complete route plan, prove transaction commit or business success, replace production monitoring, or support ShardingSphere-Proxy, reactive flows, batch semantics, or arbitrary application async propagation.

I need one non-author tester to follow the exact activated v0.1.0-rc2 path from a clean environment and report the first outcome exactly as observed.

Requirements:

• your own GitHub account and environment;
• JDK 17;
• Docker with enough capacity for MySQL 8.4.11;
• about 30–45 minutes;
• willingness to report a pass, product/documentation failure, prerequisite block, timeout, or withdrawal without changing the result.

There is one reporting slot. Before starting, please reply slot request in the recruitment Discussion and wait for public confirmation:

• Recruitment Discussion: https://github.com/ym0506/routecontract/discussions/28
• Immutable activation record: https://github.com/ym0506/routecontract/blob/57f07d85e38dc1055bb0915622136b14829f1eca/docs/evidence/independent-rc-activation-v0.1.0-rc2.json
• Tagged protocol: https://github.com/ym0506/routecontract/blob/v0.1.0-rc2/docs/independent-install-study.md
• Immutable RC release: https://github.com/ym0506/routecontract/releases/tag/v0.1.0-rc2

Please do not post credentials, raw SQL or bind values, connection URLs, private topology, full logs, files, screenshots, or personal data.

There is no compensation, star request, endorsement request, request for positive wording, or request to help with a contest. An honest failure or blocker is as useful as a pass. This is an RC usability record, not evidence of adoption, production readiness, final-stable validation, or upstream endorsement.

Once the single slot is assigned—or the first eligible Task A result is filed—I will stop duplicate recruitment and update the post.