(1 of 5) Update Java README template transaction examples to transactions()/isTransactionsEnabled()

[curfew-marathon]

Context

openfga/java-sdk PR #352 added an affirmative transaction API to ClientWriteOptions: transactions(boolean) and isTransactionsEnabled(), replacing the double-negative disableTransactions(boolean) / disableTransactions(). The old methods are slated for deprecation once public guidance stops teaching them.

The java-sdk README.md is generated from this repo, so its transaction examples cannot be fixed in java-sdk directly: they would revert on the next generation. The source of truth is the Java README template here.

Scope

config/clients/java/template/README_calling_api.mustache:

• Line 291: .disableTransactions(false) becomes .transactions(true)
• Line 302: prose "Passing ClientWriteOptions with .disableTransactions(true) is required to use non-transaction mode" becomes the equivalent for .transactions(false)
• Line 327: .disableTransactions(true) becomes .transactions(false)

Regenerate java-sdk so README.md (lines 617, 628, 653) picks up the change.

Out of scope

• docs/GENERATING-A-NEW-SDK.md, which prescribes disableTransactions as a cross-SDK property. The Go, JS, Python, and .NET SDKs use different transaction option shapes today, so renaming the shared spec is a broader cross-SDK design question, not part of this Java-scoped fix.

Acceptance criteria

• No disableTransactions(...) in README_calling_api.mustache.
• The chunk-size example still shows .transactionChunkSize(...) alongside .transactions(false), since chunk size only applies when transactions are off.
• Regenerating java-sdk produces a README.md with no disableTransactions(...) in the write examples, and the diff is limited to those lines.

Sequencing

Part of step 1 (docs), alongside the java-sdk docs/examples issue. Both must ship in a published release before the java-sdk deprecation issue proceeds. Tracked in the java-sdk umbrella issue.

Owner: @curfew-marathon

[curfew-marathon]

Tracked by openfga/java-sdk#371. Step 1 (docs), source of the generated java-sdk README. Sibling step-1 work: openfga/java-sdk#368 and openfga/spring-boot-starter#186. All three must ship in a release before openfga/java-sdk#369 (deprecation) proceeds.

[curfew-marathon]

PR #719 implements this: the three template lines in README_calling_api.mustache now use transactions(true) / transactions(false). Verified by regenerating the Java SDK locally, no disableTransactions in the generated README and chunk size preserved. On merge, sync-sdks.yaml opens the downstream java-sdk README PR.

[curfew-marathon]

Done. The template change (PR #719) merged, and the generator sync carried it into java-sdk via openfga/java-sdk#372, merged 2026-08-02 (merge commit ed633206). The java-sdk README write examples now use transactions(true)/transactions(false) with no disableTransactions. Closing as complete.