refactor: TypeScript SDK modernization and protobuf enhancements

[BRBussy]

Summary

This PR introduces significant improvements to the TypeScript SDKs and protobuf definitions, focusing on modernizing the API surface, enhancing type safety, and standardizing naming conventions across all language SDKs.

Key Changes

🔄 TypeScript SDK Modernization

Functional Options Pattern (ts-node & ts-web)

• Replaced object-based configuration with functional options pattern for better composability
• Modular package structure with separate @meshtrade/config exports
• Improved type safety and IntelliSense support
• Backward compatible migration path

Client-Side Validation

• Integrated buf.validate for client-side validation in both TypeScript SDKs
• Added comprehensive integration tests for validation scenarios
• Validates requests before sending to server, reducing network errors
• Full support for protobuf validation constraints

Testing Infrastructure

• Added Jest type definitions for better test authoring experience
• New integration tests for IAM User and API User validation
• Comprehensive test coverage for functional options pattern

📦 Protobuf Enhancements

Resource Ownership Model

• Added owners field to all resource messages (Client, User, Group, APIUser, Account, Instrument, LimitOrder)
• Enables hierarchical ownership tracking across the platform
• Supports multi-tenancy and permission inheritance

Java SDK Standardization

• Standardized api_user.proto to use ApiUserOuterClass naming convention
• Removed special case handling in protoc-gen-meshjava generator
• Consistent with all other resource OuterClass patterns (ClientOuterClass, GroupOuterClass, etc.)
• Updated all Java imports and test files

🛠️ Generator Improvements

TypeScript Generators

• Updated protoc-gen-mesh_ts_node to generate functional options API
• Updated protoc-gen-mesh_ts_web to generate functional options API
• Both generators now support modular exports and validation integration

Java Generator

• Fixed naming inconsistency in protoc-gen-meshjava
• Removed hardcoded special case for api_user proto file

Statistics

46 files changed: 2,201 insertions(+), 3,430 deletions(-)

By Language:

• TypeScript: ~1,500 lines (refactored configuration, added validation)
• Protobuf: ~140 lines (owners fields, java_outer_classname)
• Go: ~200 lines (regenerated with owners fields)
• Java: -2,000 lines (removed duplicate file, updated imports)

Testing

✅ All SDK tests passing:

• Go SDK: All tests pass
• Java SDK: All tests pass (including new OuterClass references)
• TypeScript (ts-node): All tests pass with validation integration tests
• TypeScript (ts-web): All tests pass with validation integration tests

Migration Guide

TypeScript Users

Before (Object-based):

const client = new AccountServiceClient({
  endpoint: "api.example.com",
  apiKey: "key",
  timeout: 5000
});

After (Functional options):

import { withEndpoint, withApiKey, withTimeout } from '@meshtrade/config';

const client = new AccountServiceClient(
  withEndpoint("api.example.com"),
  withApiKey("key"),
  withTimeout(5000)
);

Java Users

Update imports from:

import co.meshtrade.api.iam.api_user.v1.ApiUser.APIUser;

To:

import co.meshtrade.api.iam.api_user.v1.ApiUserOuterClass.APIUser;

Breaking Changes

⚠️ TypeScript: Configuration API changed from object-based to functional options

• Migration path: Both patterns temporarily supported
• Recommended: Update to functional options for better type safety

⚠️ Java: Import path change for APIUser-related types

• Search and replace: ApiUser.APIUser → ApiUserOuterClass.APIUser
• Affects: Hand-written Java code that imports APIUser types

Related Issues

• Resolves inconsistent Java OuterClass naming
• Improves TypeScript SDK ergonomics and type safety
• Enables client-side validation reducing server round-trips

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com