Output.array generates an incorrect schema for root-recursive Zod elements

Finding: In an external GitHub report, Output.array({ element }) in ai@7.0.137 (also reported on upstream main at ba05943) generates a response-format schema that mishandles a root-recursive Zod element, because the root self-reference $ref "#" ends up pointing at the array envelope instead of the element. Source: https://github.com/vercel/ai/issues/22572 Reported symptom: the issue author says a recursive tree schema (value string, children array of the same tree) passes Zod validation and Ajv validation against the Output.object() schema. The Output.array() schema, however, rejects the same tree inside { elements: [tree] }, because children are required to have an elements property. A model following that schema would be asked to produce a different shape for child nodes than the SDK treats as the element. Source: https://github.com/vercel/ai/issues/22572 Reported cause: the issue says the array responseFormat builder relocates the element schema to properties.elements.items and hoists definitions/$defs, but does not rebase references to the original root. A later contributor comment says it reproduced the mismatch on main at ba05943 with Zod 4.4.3 and ai 7.0.137, and points to a reproduction PR #22588. Source: https://github.com/vercel/ai/issues/22572#issuecomment-6101739306. These are reported claims, not a maintainer-confirmed cause. Fix status: a third comment says a bugfix PR #22676 was opened. It reportedly adds a shared array-output schema builder that rebases element-root references while preserving hoisted definitions, applies it to Output.array and the legacy array output strategy, and adds regression tests plus a patch changeset. Source: https://github.com/vercel/ai/issues/22572#issuecomment-6102332311. The supplied data does not show that this PR is merged or released, so treat the issue as open with a proposed or in-review fix. Practical implication: if you use Output.array with recursive Zod elements that rely on root self-references, expect the generated JSON schema to be inconsistent with the element schema in the affected versions. You can inspect arrayFormat.schema and check whether $ref "#" appears inside properties.elements.items. No source-backed workaround was given, so none is recommended here. Limitations: this is an external report. The reproduction and cross-checks come from the author and contributor-labelled comments, which are not independent. KFA did not reproduce it. Reproduction output and the PR diff were not supplied, and comments coverage may be partial. Re-check the issue and PR #22676 for merge and release status before relying on a fix.