[Dav-14]

Summary

Restore Ledger.V1.GetInfo in the composed SDK while retaining Ledger.V3.Info. Stack #2007 removed the V1 operation when adding V3 because both use GET /api/ledger/_info with different response models.

Keep both source operations and let Speakeasy represent the collision with its native namespace fragments. Limit the existing fragment check to these two known entries and validate both operation IDs, tags and response references. No Ledger server or FCTL command change.

/api/ledger/_info#ledger   -> Ledger.V1.GetInfo -> data envelope
/api/ledger/_info#ledgerV3 -> Ledger.V3.Info    -> build metadata
HTTP request for both: GET /api/ledger/_info

Evidence

• Before: FCTL commands restored to their original logic (328 Go files checked; SDK imports only) fail to compile because Ledger.V1.GetInfo is missing.
• After: local composition and SDK generation restore both methods. go test -race ./cmd/ledger/... ./pkg/clientcontract passes. Transport tests confirm neither a fragment nor %23 reaches the HTTP path, and each method retains its response model.
• The restored generated V1 method called staging Ledger v2.4.17 successfully: HTTP 200, server=ledger, version=v2.4.17. V3 was tested with its response fixture; no live V3 qualification is claimed.
• New validate-openapi assertions reject the previous composed artifact without V1 and pass the corrected one.
• Local just pre-commit passed with publication disabled and the repository's pinned Speakeasy 1.759.2. The original workflow and workflow lock were restored afterward. Consumer generation used Speakeasy 1.757.1 / generator 2.866.2.
• git diff --check passed.

Related: FCTL #204. Ledger query-schema decoding is a separate issue.

Merge Danger

Door: two-way

Blast Radius: SDK composition

HTTP routes and response contracts are unchanged. Composed path keys now distinguish V1 and V3 with namespace fragments; generated Go V3 method/signature/route remain intact and V1 is restored. Other OpenAPI consumers must support that representation. Speakeasy documents fragment paths for conflicting operations, with portability limitations outside its tooling.

This qualifies the Ledger info methods, not a full Stack SDK compatibility matrix. Wallets and Reconciliation import-only compile differences remain outside this PR. No merge, release, registry publication or deployment.

[NumaryBot]

The required automated review completed with no remaining findings.