Consolidate year-month template directories into root templates

[PaulRBerg]

@razgraf 👋

While exploring the templates/ directory, I noticed there are year-month subdirectories (2025-02, 2025-03, 2025-10) containing preview templates for upcoming features:

Directory	Feature	New Column(s)
2025-02	Custom cliff amounts	cliffAmount
2025-03	Exponential + cliff amounts	cliffAmount for exponential curves
2025-10	Flow with start date	start

Since all these dates have passed (we're in December 2025), these features should now be live.

Question: Can we consolidate these into the root templates/ directory? Specifically:

1. Update the root templates with the new columns where applicable
2. Delete the year-month directories

This would simplify the template structure and avoid confusion about which templates to use.

Let me know if there's a reason to keep them separate or if I should proceed with the consolidation.

[razgraf]

Used this to enable a very rudimentary version control for when we need a different template for each environment.

For example: production needs a template with x columns, development uses a new template with x+1 columns.

Wanted a way to keep everything backwards compatible without having to time the launch to production with overriding the file. That's where the dated directories came from.

Would be helpful to keep something similar for when the above happens again, but we can indeed clear some of the dates / reset the structure from time to time or use something else for "version control" (like the commit hash of the file itself, if git keeps it available) if you have a cleaner option.

[PaulRBerg]

I see, thx for the context.

last week I built a system in the SDK that solves the problem you encountered:

• feat: csv templates sdk#114
• feat(csv): add shapes module and rename templates to camelCase sdk#117

TL;DR we can pull the CSV from the SDK. ~There's only one issue with Phantom's blocklist, but if they don't respond quickly, we can switch to a different provider (other than unpkg.com).

~ update: they fixed it!