Add VaultModeTag field to TokenizedAssetStatusResponse

[rouzwelt]

Motivation

The liquidity bot needs to know which minting path each asset uses — either depositing directly into the vault (VaultDirect) or routing through the ST0xOrchestrator (Orchestrator) — so it can determine which assets require a signed MintAuthV1 to be delivered before their mints can be submitted. Previously, the GET /tokenized-assets/<underlying>/status response had no way to communicate this, leaving the liquidity bot without a reliable signal.

Solution

A new VaultModeTag enum (vault_direct | orchestrator) is introduced in the DTO crate and added as a vault_mode field on TokenizedAssetStatusResponse. The field is additive and defaults to VaultDirect when absent, so responses from servers that predate the field remain valid — a server that predates the field can only ever mint vault-direct, making the default truthful.

The status endpoint now reads the per-asset vault mode from the server's Config and maps it to the tag via a From<VaultMode> for VaultModeTag conversion. The orchestrator address is intentionally dropped in this mapping; the liquidity bot only needs the tag, and the issuance bot's config remains the single source of truth for addresses during the cutover.

VaultModeTag is also registered in the OpenAPI schema and TypeScript bindings exports, with wire format enforced as snake_case (matching TokenizedAssetStatus).

Closes RAI-1619

Checks

By submitting this for review, I'm confirming I've done the following:

• added comprehensive test coverage for any changes in logic
• made this PR as small as possible
• linked any relevant issues or PRs

Summary by CodeRabbit

• New Features

  • Tokenized asset status responses now indicate the vault mode: vault_direct or orchestrator.
  • API documentation and generated type definitions include the new vault mode information.

• Bug Fixes

  • Older responses without vault mode information remain compatible and default to direct vault mode.
  • Status reporting now accurately reflects mixed vault-mode configurations across assets.

[coderabbitai]

Warning

Review limit reached

@rouzwelt, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 seconds

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 88f842f0-7b1d-41e8-902e-c19c64445c2b

📥 Commits

Reviewing files that changed from the base of the PR and between 967e847 and 02ad0e7.

📒 Files selected for processing (4)

• crates/client/src/lib.rs
• crates/dto/src/lib.rs
• src/openapi.rs
• src/tokenized_asset/api.rs

Walkthrough

Changes

Tokenized-asset vault mode status

Layer / File(s)	Summary
Vault mode response contract crates/dto/src/lib.rs, src/openapi.rs	Adds VaultModeTag, adds vault_mode to TokenizedAssetStatusResponse, preserves legacy deserialization, exports TypeScript bindings, and validates the OpenAPI schema.
Status endpoint mode resolution src/tokenized_asset/api.rs, crates/client/src/lib.rs	Resolves per-underlying vault modes from Config, maps them to response tags, and updates direct, orchestrator, and client response tests.

Possibly related PRs

• ST0x-Technology/st0x.issuance#268: Adds the VaultMode configuration used by this status API.
• ST0x-Technology/st0x.issuance#303: Consumes vault_mode from tokenized-asset status responses.
• ST0x-Technology/st0x.issuance#271: Uses shared vault-mode configuration in redemption flows.

Suggested labels: enhancement

Suggested reviewers: juanirios, 0xgleb

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the primary change to TokenizedAssetStatusResponse.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 2026-07-28-orchestrator-mint-api

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[rouzwelt]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat: chunked receipt migration with crash-safe resume #332 : 3 dependent PRs (#293 , #306 , #335 )
• Add move-receipts and confirm-custody CLI commands with ERC-165 contract corroboration and post-migration reconciliation skip #331
• Move MintAuthorizationRequest/Response DTOs to shared st0x-issuance-dto crate #317
• refactor: remove retired Fireblocks integration #324
• Add orchestrator onboarding CLI subcommands, SPEC docs, and runbook #309
• Add orchestrator onboarding CLI subcommands (preflight, approve, verify-signing) #308
• feat: orchestrator-mode mint path with recipient authorization and e2e tests #303
• Add VaultModeTag field to TokenizedAssetStatusResponse #302 👈 (View in Graphite)
• feat: orchestrator mint recovery with classified failure handling #301
• feat: orchestrator mint confirmation with nonce-replay recovery and failure classification #300
• feat: orchestrator mint authorization endpoint (RAI-1243) #298
• feat: orchestrator mint preparation, confirmation, and authorization validation #296
• e2e tests and SPEC/README update #289
• Add /admin/orchestrator-health endpoint #288
• feat: orchestrator-aware balance checks and deferral in burn recovery #287
• feat: automate orchestrator burn-failed recovery with existing tx #286
• Scope burn verification by BurnProofKind for orchestrator vs vault-direct modes #285
• feat: add IntendBurn/prepare_orchestrator_burn_tx for orchestrator persist-before-broadcast #280
• feat: classify InsufficientReceipts via burn simulation before submission #279
• feat: skip classified/orchestrator burn failures in reconciler, add mode-correct recovery params #277
• feat: orchestrator burn mode with receipt lifecycle bypass #275
• feat: add BurnParams enum and orchestrator burn mode support #274
• feat: orchestrator burn vault service implementation #273
• Persist burn_mode anchor and BurnFailureClassification on redemption events #271
• Add VaultMode config with orchestrator support and smoke test #268
• Add st0x-deploy ABIs via soldeer-based Nix builder #267
• docs: spec orchestrator-based mint/burn flows #216
• main

---

How to use the Graphite Merge Queue

Add the label add-to-gt-merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has required the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

Merge activity

• Aug 14, 10:26 PM UTC: rouzwelt added this pull request to the Graphite merge queue.
• Aug 14, 10:26 PM UTC: CI is running for this pull request on a draft pull request (#345) due to your merge queue CI optimization settings.
• Aug 14, 10:27 PM UTC: Merged by the Graphite merge queue via draft PR: #345.