Bryan Helmkamp f91e51162f Describe the parallel branch fields in generated clients ... `parallel_group_id` used `oneOf: [$ref StageId, null]`, and the generator drops a sibling description in that position, so the TypeScript client documented the field as "Canonical stage execution identifier in `node_id@visit` form" — the shared StageId text, which says nothing about what this field means. Switching to `allOf` lets the field's own description through. Dropping `type: "null"` also makes the contract match the server, which omits both fields rather than sending null (`skip_serializing_if` on `Option`, pinned by list_run_stages_exposes_parallel_branch_identity). The Rust types are unchanged — still `Option<StageId>` and `Option<u32>`, which accept an explicit null on input either way — so this only narrows what clients are told to expect on the wire. Wording updated to match, and reworded to avoid an apostrophe the generator escapes into the JSDoc. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>		2026-07-28 18:05:24 -04:00
..
fabro-api-client	Describe the parallel branch fields in generated clients	2026-07-28 18:05:24 -04:00