Re-enable Dart SDK generation/release (kratos-client-dart lagging behind v26.2.0)

Context

Self-hosted Kratos is at v26.2.0, and the OpenAPI spec is already in this repo (spec/kratos/v26.2.0.json). Most language SDKs (e.g. Go, JS) were released for that version, but Dart is stuck:

Observation

Dart appears to be intentionally disabled in the SDK pipeline:

1. PR #455 (feat: bump dependencies and re-enable dotnet) commented # dart out of scripts/generate.sh while re-enabling dotnet.
2. PR #468 (chore: disable dart) then commented Dart out of scripts/test.sh and scripts/release.sh on the same day Kratos v26.2.0 landed.

Neither PR explains why Dart had to be turned off (failure mode, generator bug, pub publish issue, etc.).

Questions

1. Why was Dart commented out? Was there a specific generation/test/publish failure after the OpenAPI Generator bump, and is there a linked issue or known upstream bug?
2. Is re-enabling Dart + releasing kratos (and hydra) clients for v26.2.0 on the roadmap?
3. Until then, is generating a local dart-dio client from spec/kratos/v26.2.0.json the recommended workaround for self-hosted Kratos?

Ask

If Dart is only temporarily disabled: please re-enable generation/test/release and cut v26.2.0 for ory/kratos-client-dart (and ideally publish to pub.dev as well).

Happy to help test a regenerated Dart client if useful.

Start by reviewing scripts/generate.sh, scripts/test.sh, and scripts/release.sh alongside PRs #455 and #468 to identify why Dart was disabled. Check spec/kratos/v26.2.0.json and the existing Dart client workflow, then verify that generation, tests, and release steps complete for the Kratos and Hydra clients; done means a v26.2.0 client can be released and published as requested.