v3.12.0

Changed

• Beta App localization creates and updates preserve the same three states for all five nullable Apple feedback, marketing, privacy, tvOS privacy, and description attributes.
• Beta submission inspection uses Apple's build relationship endpoint as a bounded fallback when neither primary linkage nor an included Build resource is available.

Fixed

• Reject blank or whitespace-padded required identifiers and inconsistent primary, included, or fallback Build linkage before returning a misleading success.
• Mark malformed or invalid-identity successful create responses and post-create lineage validation failures as committed, and network, HTTP 408, or 5xx outcomes as commit-unknown; all remain unsafe to retry until the submission is inspected.
• Validate Beta App localization and review-submission continuation URLs against the concrete collection path, complete originating query, effective page size, exact query-name allowlist, and Apple's non-empty cursor.
• Emit fallback-specific output only when the relationship endpoint was actually required, keeping the public response lineage consistent with the operation manifest.

Compatibility

• No public MCP tool or required input was added, removed, or renamed; existing concrete update values and scalar filters remain valid.
• Passing null to a nullable Beta App localization attribute now forwards an explicit JSON null to Apple; omitting the input continues to leave that attribute absent from the request.
• Required identifiers with empty values or surrounding whitespace now fail locally before network access.
• The operation manifest now maps 366 Apple operations, explicitly defers 534, and scopes out 363; the optional-input pin remains fully classified at 2,154 total with 0 unclassified.