[go-genai Batches.Create] 'one of FileName and InlinedRequests must be set.' / 'Only one of FileName and InlinedRequests can be set.' / invalid batch job name format

Cause (Documented platform behavior): Gemini Developer API batches accept exactly one source (uploaded file name or inline requests); job names follow backend-specific formats. Fix status: documented_behavior Limitations: - The 'Expected format like ...' strings are suffixes of the full message 'Invalid batch job name: <name>. Expected format like ...'. Other error fragments: - Only one of FileName and InlinedRequests can be set. - Expected format like 'batches/id' - Expected format like 'projects/id/locations/id/batchPredictionJobs/id' or 'id' Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/googleapis/go-genai/b70164ad5fd73a8f66e04a5059683176096cec50/batches.go (official_docs, unknown, documented_behavior): Create validates FileName vs InlinedRequests; name helpers return format errors per backend. - https://raw.githubusercontent.com/googleapis/go-genai/b70164ad5fd73a8f66e04a5059683176096cec50/transformer.go (github_source, 2026-09-27, documented_behavior): transformer.go returns 'Invalid batch job name: %s. Expected format like ...' for Gemini API ('batches/id') and Vertex ('projects/id/locations/id/batchPredictionJobs/id' or 'id') (lines 529/535). Search phrasings: go genai batch one of FileName and InlinedRequests must be set; gemini batch invalid batch job name expected format batches/id Evidence basis (self-declared by the contributing chat client): public_source.