Track ide-gsm FDM 7-layer contract landing for hierarchidb

[kubohiroya]

Track ide-gsm FDM 7-layer contract landing for hierarchidb

Purpose

Tracking issue for upstream ide-gsm FDM 7-layer contract changes that hierarchidb must consume.

Implementation planning now lives in #1728 and its child issues. This issue remains the upstream landing gate and compatibility/deprecation tracker.

Primary source:

• kubohiroya/ide-gsm#2653

Related upstream issues:

• kubohiroya/ide-gsm#2654
• kubohiroya/ide-gsm#2655
• kubohiroya/ide-gsm#2656
• kubohiroya/ide-gsm#2657
• kubohiroya/ide-gsm#2658
• kubohiroya/ide-gsm#2660
• kubohiroya/ide-gsm#2662

Hierarchidb implementation entrypoint

• Parent implementation issue: FDM 7-layer alignment for hierarchidb ide-gsm client and dashboard #1728
• L0-L2 DTO/normalizer: Align L0-L2 FDM DTOs with timeline, range, and snapshot provenance #1729
• L3 fdmSweep/run-job client: Stage fdmSweep and L3 run-job handle support in ide-gsm-client #1730
• L4/L5 dashboard projections: Render L4 workflow and L5 ruleset projections without client-side decisions #1731
• L6 baselineSpace/catalog provenance: Consume L6 baselineSpace provenance and space catalog capabilities #1732
• Terminology audit: Freeze FDM 7-layer terminology and contract-audit mapping #1733
• Fixture/coverage scaffold: Scaffold FDM 7-layer contract fixtures and audit regression coverage #1734
• L6 lifecycle actions: Audit and add server-authorized L6 space lifecycle actions #1735
• L6 fork/cross-space views: Add L6 fork and cross-space read-only views #1736
• FDM dashboard GraphQL adapter: Connect FdmDashboardPort to ide-gsm GraphQL dashboard APIs #1737
• React/Jotai-TanStack dashboard architecture: Rebuild FDM dashboard presentation with MUI, custom hooks, Jotai, and TanStack Query #1738

ide-gsm origin/main schema review update

Reviewed against ide-gsm origin/main commit 9e0a5a3a9 (feat(api): expose fdm run metadata schema) and the generated schema snapshot api-idegsm/docs/generated/schema.graphql.

Treat the following as the current stable implementation baseline for hierarchidb planning:

• fdmSpaces
• fdmDashboardStatus
• fdmCellDetail
• subscribeFdmCellLog
• subscribeFdmRuntimeEvents
• fdmRuntimeDiagnostics
• fdmSpaceCreate
• fdmSpaceUpdate
• fdmSpaceDelete
• fdmDirectoryRemove
• fdmVerify
• fdmFill
• fdmCompare
• fdmClean
• fdmDiagnose

Important current limitations:

• fdmDashboardStatus uses timeline, but fdmCellDetail, subscribeFdmCellLog, DashboardCell, and CellStageIdentity still use checkpoint.
• ActiveProjectTask, Task, VerifyReport, and TaskInputInput now expose runId, jobId, workflowId, and executionKind, so hierarchidb should consume these as additive run metadata.
• fdmSweep is not in the current GraphQL schema. Keep it upstream-gated and do not invent the method name client-side.
• ideGsmServerInfo.capabilities exists, but the advertised capability list currently contains project/task capabilities only. Missing FDM capability must mean optional FDM actions are disabled/unavailable, not that the dashboard APIs are absent.

Upstream gate matrix

ide-gsm change	Upstream issue	hierarchidb consumer	hierarchidb issue	Current action
Dashboard/status axis checkpoint -> timeline; checkpoint remains in cell/detail/log identity	kubohiroya/ide-gsm#2660	fdmDashboardStatus, fdmCellDetail, axis labels, validators	#1729, #1737, #1738	Implement additive normalizer; preserve operation-specific input names because status currently uses timeline while detail/log/cell identity still use checkpoint.
GraphQL/MCP fdmSweep additive alias; fdmVerify compatibility alias	kubohiroya/ide-gsm#2658	ide-gsm client execution methods and dashboard actions	#1730, #1737, #1738	fdmVerify is current baseline; keep fdmSweep gated until it appears in generated schema.
L3 run/job/task separation, runner local/ssh/batch, live progress evidence	kubohiroya/ide-gsm#2656	execution handle, status/log/cancel/progress projection	#1730, #1737	Consume existing runId/jobId/workflowId/executionKind metadata now; keep taskId subscription/cancel/log as the compatibility stream until dedicated run/job APIs exist.
L4 workflow status and nextAction vocabulary	kubohiroya/ide-gsm#2654, #2662	dashboard workflow projection	#1731, #1737	Support confirmed enum values; unknown values render unsupported/contract error.
L5 ruleset governance and accepted known issue handling	kubohiroya/ide-gsm#2655	dashboard ruleset projection	#1731, #1737	Display server governance metadata; do not mutate/accept/waive locally.
L6 baselineSpace provenance and space catalog	kubohiroya/ide-gsm#2657	FDM space read model and dashboard origin metadata	#1732	Scaffold read-only DTOs; live wiring waits for confirmed server fields.
Existing GraphQL fdmSpaceCreate / fdmSpaceUpdate / fdmSpaceDelete	existing generated schema, #2657 for final semantics	ide-gsm client space lifecycle methods	#1735	Audit existing operations now; do not treat them as complete reference-aware L6 lifecycle until #2657 confirms semantics.
L6 lifecycle update/archive/delete	kubohiroya/ide-gsm#2657	server-authorized lifecycle actions	#1735	Blocked for final lifecycle until operation names, capability keys, authorization, reference-aware denial, and dry-run/apply schemas are fixed.
L6 fork/cross-space view	kubohiroya/ide-gsm#2657	fork provenance and read-only cross-space views	#1736	Blocked until fork/view schema and origin requirements are fixed.
Live dashboard GraphQL adapter	current origin/main schema plus #2660/#2656/#2657 gated fields	FdmDashboardPort implementation over IdeGsmClient	#1737	Add typed adapter and GraphQL documents from the generated schema snapshot; do not let React components bypass FdmDashboardPort.
React dashboard architecture	current mocked FdmDashboardPort plus live #1737 adapter	FDM dashboard and FDM space selection UI	#1738	Use MUI, custom hooks, Jotai, TanStack Query, and jotai-tanstack-query; start with mock port and connect live data through #1737.

Contract gate

All upstream-facing GraphQL/API changes must pass the contract-audit classification before hierarchidb consumes them:

• existing
• additive
• deprecated compatibility
• removal/migration
• blocked by upstream

Do not implement by guessing upstream API names, GraphQL fields, capability keys, or enum values.

Use ideGsmServerInfo.capabilities / apiContractVersion where available to gate optional FDM behavior.

Done for this tracker

• FDM 7-layer alignment for hierarchidb ide-gsm client and dashboard #1728 and child issues are complete or explicitly superseded.
• Every upstream FDM 7-layer landing item has a corresponding hierarchidb issue or a documented no-op reason.
• ide-gsm deprecated compatibility aliases can be removed only after hierarchidb confirms consumption of the new contract.

[kubohiroya]

hierarchidb 側の実装 issue 分解

#1728 を親 issue として詳細化し、ide-gsm#2653 の L0〜L6 モデルと用語変更を hierarchidb 側へ反映する子 issue を作成した。

• Align L0-L2 FDM DTOs with timeline, range, and snapshot provenance #1729 L0/L1/L2 DTO と node contract: timeline / range / snapshot provenance
• Stage fdmSweep and L3 run-job handle support in ide-gsm-client #1730 L3 fdmSweep と run/job execution handle
• Render L4 workflow and L5 ruleset projections without client-side decisions #1731 L4/L5 workflow/ruleset projection の表示、client 側 next-action 計算禁止
• Consume L6 baselineSpace provenance and space catalog capabilities #1732 L6 space lifecycle と cross-space read-only view
• Freeze FDM 7-layer terminology and contract-audit mapping #1733 docs/UI wording/Contract Audit Gate の 7層語彙固定
• Scaffold FDM 7-layer contract fixtures and audit regression coverage #1734 7層化 contract fixtures と regression tests

旧名削除期限の判断は、#1728 配下の対応完了後にこの tracking issue から ide-gsm#2653 へ戻す。

[kubohiroya]

Tracker update: fdmSweep client gate unblocked

hierarchidb PR #1741 was squash-merged as 110d7f1ee33ab5160c4540490c0ad2fecd87e53a.

Status changes:

• Stage fdmSweep and L3 run-job handle support in ide-gsm-client #1730 Phase 2 is complete: ide-gsm-client now calls the confirmed fdmSweep mutation using canonical parameterSet / originalSourceParameterSet variables.
• The compatibility fdmVerify method remains available, but its request variables are also canonicalized to the current IDE-GSM schema.
• The contract audit docs now use IDE-GSM baseline kubohiroya/ide-gsm@1f0c50d32634b8e08f0d80b8ec3a9e0e447e01fb.

Still open:

• Stage fdmSweep and L3 run-job handle support in ide-gsm-client #1730 Phase 3 remains blocked on the dedicated run/job lifecycle surface from kubohiroya/ide-gsm#2656.
• Connect FdmDashboardPort to ide-gsm GraphQL dashboard APIs #1737 is the next actionable hierarchidb item because the dashboard adapter can now wire sweep launch through the confirmed fdmSweep client method.

[kubohiroya]

Tracker update: selected-cell dashboard sweep wired

hierarchidb PR #1744 was squash-merged as e434a57aa118e6fff74db76965e6c14d66e4d509.

Status changes:

• Connect FdmDashboardPort to ide-gsm GraphQL dashboard APIs #1737 now has the selected-cell dashboard action wired to the confirmed canonical fdmSweep GraphQL client method.
• The dashboard action path sends canonical parameterSet / dataset / computeEngine / timeline selectors and preserves the current dashboard filters, axisMap, and selected state directory from UI state.
• Missing or stale selected-cell ids are explicit contract errors rather than silent no-ops.

Still open:

• Connect FdmDashboardPort to ide-gsm GraphQL dashboard APIs #1737 remains open for fdmCellDetail, subscribeFdmCellLog, and subscribeFdmRuntimeEvents wiring.
• Runtime events still require a safe projectRelativePath resolution path before subscription can be enabled.

[kubohiroya]

Tracker update: dashboard cell detail/log wired

hierarchidb PR #1745 was squash-merged as 64543c23f433850b421923f84e4681adc1f6bacb.

Status changes:

• Connect FdmDashboardPort to ide-gsm GraphQL dashboard APIs #1737 now has status, selected-cell sweep, selected-cell detail, and selected-cell log subscription wired through FdmDashboardPort and IdeGsmClient.
• The React dashboard still depends on FdmDashboardPort; no component calls IdeGsmClient directly.

Still open:

• Connect FdmDashboardPort to ide-gsm GraphQL dashboard APIs #1737 has one remaining live-adapter gap: subscribeFdmRuntimeEvents.
• That gap is blocked on adding or injecting a safe resolver from the linked ide-gsm project root to validated projectRelativePath.

[kubohiroya]

Tracker update: dashboard runtime event gate wired

hierarchidb PR #1746 was squash-merged as 80f94765c93c8ff38997ef258f75734a7ad79497.

Status changes:

• Connect FdmDashboardPort to ide-gsm GraphQL dashboard APIs #1737 is now complete and closed.
• FdmDashboardPort now covers status, selected-cell sweep, selected-cell detail, cell log subscription, and runtime event subscription.
• Runtime event subscription is capability-gated by an explicit projectRelativePath resolver; the adapter does not infer server paths from spaceId.
• Dashboard UI still consumes live data through FdmDashboardPort; React components do not call IdeGsmClient directly.

Validation:

• local pnpm -w turbo run typecheck --filter @hierarchidb/fdm-plugin
• local pnpm -w turbo run test --filter @hierarchidb/fdm-plugin
• local pnpm -w turbo run build --filter @hierarchidb/fdm-plugin
• local pnpm -w turbo run typecheck --filter @hierarchidb/fdm-api
• local pnpm -w turbo run test --filter @hierarchidb/fdm-api
• local Biome checks
• local git diff --check
• CI for feat(fdm-plugin): gate runtime dashboard events #1746 pass

Next selection:

• Re-checking Rebuild FDM dashboard presentation with MUI, custom hooks, Jotai, and TanStack Query #1738, Render L4 workflow and L5 ruleset projections without client-side decisions #1731, Consume L6 baselineSpace provenance and space catalog capabilities #1732, Audit and add server-authorized L6 space lifecycle actions #1735, Add L6 fork and cross-space read-only views #1736, and Scaffold FDM 7-layer contract fixtures and audit regression coverage #1734 against current main to pick the next non-blocked child item.

[kubohiroya]

Progress update:

• done: Rebuild FDM dashboard presentation with MUI, custom hooks, Jotai, and TanStack Query #1738 was completed by test(fdm-plugin): cover dashboard query invalidation #1747.
• PR: test(fdm-plugin): cover dashboard query invalidation #1747
• merge commit: 9d548d2704434f2f2b6fd0882fad9cc14861aad8
• CI: passed (Affected package test, Affected package typecheck, Affected repository checks, Run CI validation)
• local validation before PR:
  • pnpm -w turbo run test --filter @hierarchidb/fdm-plugin
  • pnpm -w turbo run typecheck --filter @hierarchidb/fdm-plugin
  • pnpm -w turbo run build --filter @hierarchidb/fdm-plugin
  • ./node_modules/.bin/biome check plugins/fdm-plugin/src/ui/dashboard/fdmDashboardAtoms.ts plugins/fdm-plugin/src/ui/dashboard/FdmDashboardPresentation.tsx plugins/fdm-plugin/src/ui/dashboard/__tests__/FdmDashboardView.test.tsx
  • git diff --check

Implemented coverage/result:

• dashboard action mutations now invalidate the authoritative dashboard query and refetch instead of directly writing mutation payloads into cache
• regression tests cover recoverable query errors, post-action refetch, local-only selected cell/view state, and server-scope filter reloads
• Rebuild FDM dashboard presentation with MUI, custom hooks, Jotai, and TanStack Query #1738 is closed by the merged PR

Next planned item:

• Scaffold FDM 7-layer contract fixtures and audit regression coverage #1734 Phase B1 ready-scope coverage audit, unless the epic tracker changes priority after review

[kubohiroya]

Progress update:

• done: Scaffold FDM 7-layer contract fixtures and audit regression coverage #1734 was completed by test(fdm-api): add seven-layer contract audit fixtures #1748.
• PR: test(fdm-api): add seven-layer contract audit fixtures #1748
• merge commit: c092e4c9d94b09bd5ad5e661549d52250f7a5a3c
• CI: passed (Affected package test, Affected package typecheck, Affected repository checks, Run CI validation)
• local validation before PR:
  • pnpm -w turbo run test --filter @hierarchidb/fdm-api
  • pnpm -w turbo run typecheck --filter @hierarchidb/fdm-api
  • pnpm -w turbo run build --filter @hierarchidb/fdm-api
  • ./node_modules/.bin/biome check packages/fdm-api/src/__tests__/fdmSevenLayerFixtures.test.ts packages/fdm-api/src/__fixtures__/fdm-seven-layer/README.md packages/fdm-api/src/__fixtures__/fdm-seven-layer/l0-timeline/README.md packages/fdm-api/src/__fixtures__/fdm-seven-layer/l1-parameter-set/README.md packages/fdm-api/src/__fixtures__/fdm-seven-layer/l2-range-snapshot/README.md packages/fdm-api/src/__fixtures__/fdm-seven-layer/l3-run-job/README.md packages/fdm-api/src/__fixtures__/fdm-seven-layer/l4-workflow/README.md packages/fdm-api/src/__fixtures__/fdm-seven-layer/l5-ruleset/README.md packages/fdm-api/src/__fixtures__/fdm-seven-layer/l6-space/README.md docs/fdm-seven-layer-contract-audit.md
  • git diff --check

Implemented coverage/result:

• executable/readable L0-L6 FDM seven-layer contract fixtures now exist under packages/fdm-api/src/__fixtures__/fdm-seven-layer/
• fixture-driven @hierarchidb/fdm-api tests cover ready-scope positive cases plus negative alias conflict, forbidden credential-like keys, and unknown workflow enum values
• audit doc now records current ready coverage and assigns remaining expansion to Consume L6 baselineSpace provenance and space catalog capabilities #1732, Audit and add server-authorized L6 space lifecycle actions #1735, and Add L6 fork and cross-space read-only views #1736
• Scaffold FDM 7-layer contract fixtures and audit regression coverage #1734 is closed by the merged PR

Next planned item:

• Consume L6 baselineSpace provenance and space catalog capabilities #1732 L6 baseline/fork provenance schema intake is the next mainline item.
• Audit and add server-authorized L6 space lifecycle actions #1735 lifecycle dry-run/client safety can be prepared in a separate parallel slice after Consume L6 baselineSpace provenance and space catalog capabilities #1732 scope is confirmed.
• Add L6 fork and cross-space read-only views #1736 remains gated until Consume L6 baselineSpace provenance and space catalog capabilities #1732 brings in the cross-space/provenance client schema.

[kubohiroya]

Progress update:

• done: Consume L6 baselineSpace provenance and space catalog capabilities #1732 was completed by feat(fdm-api): project L6 capability summaries #1749.
• PR: feat(fdm-api): project L6 capability summaries #1749
• merge commit: a31268223bd6ee776d42e9919d151bace712f753
• CI: passed (Affected package test, Affected package typecheck, Affected repository checks, Run CI validation)
• local validation before PR:
  • pnpm -w turbo run test --filter @hierarchidb/fdm-api
  • pnpm -w turbo run typecheck --filter @hierarchidb/fdm-api
  • pnpm -w turbo run build --filter @hierarchidb/fdm-api
  • ./node_modules/.bin/biome check packages/fdm-api/src/fdmTypes.ts packages/fdm-api/src/fdmValidators.ts packages/fdm-api/src/__tests__/fdmSevenLayerFixtures.test.ts docs/fdm-seven-layer-contract-audit.md packages/fdm-api/src/__fixtures__/fdm-seven-layer/README.md packages/fdm-api/src/__fixtures__/fdm-seven-layer/l6-space/README.md
  • git diff --check

Implemented coverage/result:

• FdmSpaceCatalog can now carry the existing FdmCapabilitiesPayload from @hierarchidb/ide-gsm-client
• L6 read-only catalog entries expose server capability names plus baseline/fork/lineage summary counts
• per-space provenance remains unavailable with FDM_SPACE_PROVENANCE_UNSCOPED when upstream capability summaries do not identify a space
• no lifecycle actions or cross-space views were enabled
• Consume L6 baselineSpace provenance and space catalog capabilities #1732 is closed by the merged PR

Next planned item:

• Audit and add server-authorized L6 space lifecycle actions #1735 lifecycle dry-run/client safety is next.
• Add L6 fork and cross-space read-only views #1736 remains after Audit and add server-authorized L6 space lifecycle actions #1735/Consume L6 baselineSpace provenance and space catalog capabilities #1732 because it needs cross-space view wiring and stricter origin/provenance handling.

[kubohiroya]

Progress update:

• done: Audit and add server-authorized L6 space lifecycle actions #1735 was completed by feat(ide-gsm-client): add FDM space delete dry-run helper #1750.
• PR: feat(ide-gsm-client): add FDM space delete dry-run helper #1750
• merge commit: 7d9e76660cca5eba78b96125bc7bce1db0b882ec
• CI: passed (Affected package test, Affected package typecheck, Affected repository checks, Run CI validation)
• local validation before PR:
  • pnpm -w turbo run test --filter @hierarchidb/ide-gsm-client
  • pnpm -w turbo run typecheck --filter @hierarchidb/ide-gsm-client
  • pnpm -w turbo run build --filter @hierarchidb/ide-gsm-client
  • ./node_modules/.bin/biome check packages/ide-gsm-client/src/ideGsmDirectoryTypes.ts packages/ide-gsm-client/src/index.ts packages/ide-gsm-client/src/IdeGsmClient.ts packages/ide-gsm-client/__tests__/IdeGsmClient.test.ts docs/fdm-node-spec.md docs/fdm-seven-layer-contract-audit.md
  • git diff --check

Implemented coverage/result:

• added IdeGsmClient.fdmSpaceDeleteDryRun() as the explicit safe helper for server-side FDM space delete/archive inspection
• helper always sends apply: false
• test proves the helper calls fdmSpaceDelete and not fdmDirectoryRemove
• docs record that destructive apply/UI lifecycle actions remain gated on server authorization and reference-aware semantics
• Audit and add server-authorized L6 space lifecycle actions #1735 is closed by the merged PR

Next planned item:

• Render L4 workflow and L5 ruleset projections without client-side decisions #1731 L4/L5 projection follow-through is the next low-risk item.
• Add L6 fork and cross-space read-only views #1736 follows after Render L4 workflow and L5 ruleset projections without client-side decisions #1731 because fork/cross-space views need the stricter projection/origin contracts settled.

[kubohiroya]

#1728 child progress update (2026-09-08 JST)

Completed now:

• Render L4 workflow and L5 ruleset projections without client-side decisions #1731 is closed by PR test(fdm): cover workflow and ruleset projections #1751 (d54e151e69fecb95e9b6f8c360681874a44110f3).
• L4 workflow and L5 ruleset projections now have explicit validator/UI coverage for known enum values, representative workflow states, ruleset fingerprint/digest display, missing issue-number visibility, and unavailable/unsupported/stale projection messages.

Remaining/open:

• Stage fdmSweep and L3 run-job handle support in ide-gsm-client #1730 remains open only for Phase 3: dedicated run/job lifecycle status/log/cancel/retry/progress wiring. This is still gated on the upstream ide-gsm#2656 contract and should not be implemented by guessing GraphQL operation names.
• Add L6 fork and cross-space read-only views #1736 is the next actionable item. Live fork/cross-space wiring remains gated on ide-gsm#2657, but DTO/interface placeholders and unavailable/read-only UI states can proceed without guessing server API names.

Next step:

• Start Add L6 fork and cross-space read-only views #1736 with a narrow scope: read-only fork/cross-space DTO placeholders, explicit origin/provenance validator coverage, and UI unavailable/read-only states through FdmDashboardPort. No lifecycle writes and no inferred origin spaceId.

Validation for #1731 / PR #1751:

• pnpm -w turbo run test typecheck build --filter @hierarchidb/fdm-api
• pnpm -w turbo run test typecheck build --filter @hierarchidb/fdm-plugin
• Biome check on changed files
• git diff --check
• GitHub CI passed before merge.

[kubohiroya]

#1728 child progress update (2026-09-08 JST)

Completed now:

• Add L6 fork and cross-space read-only views #1736 is closed by PR feat(fdm): add cross-space read-only projections #1752 (c2c791941d24cd49f8964eb70f2d830f81173442).
• L6 fork/cross-space read-only placeholder support now exists without guessing upstream GraphQL names: optional crossSpace dashboard projection, explicit origin validation for cross-space cells/forks, read-only dashboard rendering, and fixture/audit coverage.

Remaining/open:

• Stage fdmSweep and L3 run-job handle support in ide-gsm-client #1730 remains open only for Phase 3 dedicated run/job lifecycle status/log/cancel/retry/progress wiring. This is still gated on upstream ide-gsm#2656.

Current tracker status:

• Align L0-L2 FDM DTOs with timeline, range, and snapshot provenance #1729, Render L4 workflow and L5 ruleset projections without client-side decisions #1731, Consume L6 baselineSpace provenance and space catalog capabilities #1732, Freeze FDM 7-layer terminology and contract-audit mapping #1733, Scaffold FDM 7-layer contract fixtures and audit regression coverage #1734, Audit and add server-authorized L6 space lifecycle actions #1735, Add L6 fork and cross-space read-only views #1736, Connect FdmDashboardPort to ide-gsm GraphQL dashboard APIs #1737, Rebuild FDM dashboard presentation with MUI, custom hooks, Jotai, and TanStack Query #1738 are closed.
• No further hierarchidb implementation should invent run/job lifecycle GraphQL names before ide-gsm#2656 provides the contract.

Validation for #1736 / PR #1752:

• pnpm -w turbo run test typecheck build --filter @hierarchidb/fdm-api
• pnpm -w turbo run test typecheck build --filter @hierarchidb/fdm-plugin
• pnpm -w turbo run test typecheck build --filter @hierarchidb/fdm-api --filter @hierarchidb/fdm-plugin
• Biome check changed files
• git diff --check
• GitHub CI passed before merge.

[kubohiroya]

Gate retention decision (2026-09-08 JST)

#1730 Phase 3 will remain open as the upstream gate for dedicated FDM run/job lifecycle integration.

All other #1728 implementation child issues are closed. The tracker remains open only to watch kubohiroya/ide-gsm#2656 and prevent speculative hierarchidb implementation of run/job lifecycle GraphQL names, subscriptions, cancel/retry operations, progress/ETA fields, or capability keys.

Next action when upstream lands:

1. Re-read the generated ide-gsm schema and capability surface.
2. Update Stage fdmSweep and L3 run-job handle support in ide-gsm-client #1730 with the confirmed operation/field names.
3. Implement a new small PR for Phase 3 wiring and tests.