[Option B] Phase 2 — Non-breaking downstream alignment

**Part of the [Option B identifier-naming migration](https://github.com/layer5labs/meshery-extensions/pull/4205). Cross-session state anchor for Phase 2.** ## Scope Ten non-breaking PRs across three downstream repos. Each repo pins `@meshery/schemas` to the Phase 1.I version. Agents run in parallel. ## Sub-agents ### meshery/meshery - [ ] **Agent 2.A** — query-param extraction alignment (`orgID` → `orgId` in workspace/pattern handlers) - [ ] **Agent 2.B** — outbound URL alignment (`remote_provider.go` `q.Set("orgID", ...)` → `"orgId"`) - [ ] **Agent 2.H** — Meshery UI RTK hook unification (`user.ts`, `design.ts`, `environments.ts`) ### layer5io/meshery-cloud - [ ] **Agent 2.C (PR 1)** — `QueryParamOrganizationID` constant flip - [ ] **Agent 2.C (PR 2, +1 release)** — `utils.QueryParam` dual-accept retirement - [ ] **Agent 2.D** — 9 mapping-model `json:"ID"` → `json:"id"` - [ ] **Agent 2.E** — `ContentID`/`MesheryPattern.OrgID` confirm-and-close (docs only) - [ ] **Agent 2.F** — Cloud UI `api.ts` endpoint dedup vs. `@meshery/schemas/cloudApi` ### layer5labs/meshery-extensions - [ ] **Agent 2.G** — Kanvas `catalog.ts` + `designs.ts` case-flip + wrapper alignment - [ ] **Agent 2.I** — Kanvas `mesherySdk.ts` event-type casing alignment - [ ] **Agent 2.J** — Kanvas `collab/config.ts` user-ID duality resolution ## Acceptance All 10 PRs merged. `make consumer-audit` from schemas repo shows reduced-but-nonzero divergence (remaining divergences are Phase 3's scope). No open high/medium review-bot threads. ## References - Master plan §8 (agent specs) - Per-repo handoffs: `docs/option-b-plan-{meshery,meshery-cloud,meshery-extensions}.md` in `layer5labs/meshery-extensions` ## Blocked by #$(echo "$ISSUE_1" | grep -oE '[0-9]+$') (Phase 1)