git-integration-operations-cli

1> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry
2> `x-ms-fabric-skill: git-integration-operations-cli` (`az rest`: `--headers "x-ms-fabric-skill=git-integration-operations-cli"`),
3> including every LRO poll, `fabric_lro` and retry. Snippets omit it — add it anyway.
4 
5> **CRITICAL NOTES**
6> 1. To find a workspace ID from its name: list all workspaces, then filter by
7>    `displayName` with JMESPath. To find an item ID: list items of that type in the
8>    workspace, then filter by `displayName`.
9> 2. All Git operations are **control plane** calls against
10>    `https://api.fabric.microsoft.com`. Run `fab auth login` once and `fab api`
11>    sets the base URL and Fabric token audience automatically. With the `az rest`
12>    fallback you must pass the matching `--resource` yourself, or you get a 401.
13> 3. `commitToGit`, `updateFromGit`, and even `git/status` can return **HTTP 202
14>    (long-running operation)**, not just a synchronous body. On `202`, poll the
15>    operation: with `fab`, read `x-ms-operation-id` from `--show_headers` and poll
16>    `fab api operations/{id}` until `status` is `Succeeded`; with the `az rest`
17>    fallback, poll the `Location` / `x-ms-operation-id` header (see COMMON-CORE
18>    long-running operation polling). When a `202` came from `git/status` itself,
19>    read its body from `operations/{id}/result` (the `git_status` helper does
20>    this); calling `git/status` again can just return another `202`. After a
21…