[codex] Export ledger command types

[HardlyDifficult]

Summary

• export ledger JSON API command/disclosed-contract types from the public SDK entrypoint
• add a unit test proving consumers can import the types from the package root

Root cause

Consumers need Command and DisclosedContract, but the public ledger-json-api barrel only exported TraceContext. That forced downstream SDKs to import from generated build/src/... internals.

Validation

• npx prettier --check src/clients/ledger-json-api/index.ts test/unit/clients/ledger-json-api-exports.test.ts
• npx jest test/unit/clients/ledger-json-api-exports.test.ts --runInBand
• npm run build:core after initializing libs/splice
• npx jest test/unit --runInBand
• npx eslint src/clients/ledger-json-api/index.ts test/unit/clients/ledger-json-api-exports.test.ts

Repo-wide npm run lint currently fails on unrelated existing files; this PR's changed files pass targeted ESLint.

---

Note

Low Risk
Type-only public API expansion with no runtime or behavioral changes to ledger submission logic.

Overview
The ledger-json-api public barrel now re-exports ledger JSON API command and submission types (Command, DisclosedContract, CommandRequest, variant command shapes, JsCommands, and related types) from ./schemas, alongside the existing TraceContext export. Consumers can import these from the package root instead of generated build/src/... paths.

A unit test asserts that Command, DisclosedContract, and LedgerJsonApiClient resolve when imported from ../../../src.

^{Reviewed by Cursor Bugbot for commit 2ad8a46. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 10 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: e7f8f265-06c1-4396-9492-ec2ff93037fb

📥 Commits

Reviewing files that changed from the base of the PR and between b4a837d and 2ad8a46.

📒 Files selected for processing (2)

• src/clients/ledger-json-api/index.ts
• test/unit/clients/ledger-json-api-exports.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/ledger-schema-type-exports

---

_{Comment @coderabbitai help to get the list of available commands.}

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.