fix: updating stainless.yml for latest changes

[pengying]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
grid-flow-builder	Ready	Preview, Comment	Apr 1, 2026 1:32am

[pengying]

• fix: updating stainless.yml for latest changes #311 👈 (View in Graphite)
• main

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

[greptile-apps]

Greptile Summary

This PR updates .stainless/stainless.yml with two categories of changes: (1) adding five new top-level resources to drive SDK code generation, and (2) fixing the openapi section key from transformations to transforms.

• New resources added: crypto (estimate_withdrawal_fee), beneficial_owners (CRUD minus delete), documents (upload/list/retrieve/replace/delete), verifications (submit/list/retrieve), and discoveries (non-paginated list).
• Key fix: openapi.transformations → openapi.transforms — aligns with the Stainless config JSON schema ($schema: https://app.stainless.com/config.schema.json). Previously, the wrong key name meant all remove transforms (discriminator clean-up, allOf $ref stripping, etc.) were likely being silently ignored during SDK generation. The rename activates them.
• Minor: Trailing whitespace on the discoveries.list entry (P2 style nit).

Confidence Score: 5/5

• Safe to merge — all findings are P2 style nits with no correctness impact.
• The only issue found is trivial trailing whitespace. The transformations → transforms rename is intentional and aligns the config with the schema. New resource entries follow established patterns in the file.
• No files require special attention.

Important Files Changed

Filename	Overview
.stainless/stainless.yml	Adds five new top-level resources (crypto, beneficial_owners, documents, verifications, discoveries) to the Stainless SDK config, and fixes the openapi key from transformations to transforms to match the schema.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    Resources["resources (stainless.yml)"]
    Resources --> Crypto["crypto\nPOST /crypto/estimate-withdrawal-fee"]
    Resources --> BeneficialOwners["beneficial_owners\nCREATE · LIST · RETRIEVE · UPDATE"]
    Resources --> Documents["documents\nUPLOAD · LIST · RETRIEVE · REPLACE · DELETE"]
    Resources --> Verifications["verifications\nSUBMIT · LIST · RETRIEVE"]
    Resources --> Discoveries["discoveries\nLIST (paginated: false)"]

    OpenAPI["openapi section"]
    OldKey["transformations ❌ (was silently ignored)"]
    NewKey["transforms ✅ (schema-correct key)"]
    OldKey -->|renamed to| NewKey
    NewKey --> Transforms["Remove transforms applied\n(discriminator cleanup,\nallOf $ref stripping)"]

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: .stainless/stainless.yml
Line: 320

Comment:
**Trailing whitespace after `list:`**

There is a trailing space after `list:` on this line. While YAML parsers are tolerant of this, it can trip up stricter linters or schema validators.

```suggestion
      list:
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix: updating stainless.yml for latest c..." | Re-trigger Greptile}

[greptile-apps]

Trailing whitespace after list:

There is a trailing space after list: on this line. While YAML parsers are tolerant of this, it can trip up stricter linters or schema validators.

Suggested change

	list:
	list:

Prompt To Fix With AI

This is a comment left during a code review.
Path: .stainless/stainless.yml
Line: 320

Comment:
**Trailing whitespace after `list:`**

There is a trailing space after `list:` on this line. While YAML parsers are tolerant of this, it can trip up stricter linters or schema validators.

```suggestion
      list:
```

How can I resolve this? If you propose a fix, please make it concise.

[pengying]

Merge activity

• Apr 1, 1:39 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Apr 1, 1:39 AM UTC: @pengying merged this pull request with Graphite.