What problems was I solving

The @architect/database-client public entry point re-exported TransactionOptions, but the interface was only used internally inside the database.ts module. Leaving the public export in place added unnecessary surface area to the package API and made tooling like Knip flag the identifier as unused.

What user-facing changes did I ship

None. This is an internal package API cleanup. Callers of DatabaseClient.read() and write() pass options inline and are unaffected.

How I implemented it

Removed TransactionOptions from the export list in architect/database-client/main/index.ts. The interface and its usage remain exactly the same in database.ts, so DatabaseClient.read() and write() still accept the same options shape; only the public re-export is gone.

Description for the changelog

Removed the unused TransactionOptions re-export from @architect/database-client's public entry point. The type remains defined internally and is still accepted by DatabaseClient.read() and write(), so there is no behavior change or breakage for in-tree consumers.