CRE: Solana Guide follow

[dev-dist]

This pull request adds a new Solana Forwarder Directory reference for both Go and TypeScript SDKs, and improves the Solana workflow documentation for generating and using bindings. The changes clarify directory structure, simplify the example workflows, and direct users to the new forwarder directory for up-to-date addresses. The most important changes are:

---

New Solana Forwarder Directory Reference:

• Added forwarder-directory pages for both Go and TypeScript (forwarder-directory-go.mdx, forwarder-directory-ts.mdx), listing mock and production forwarder program IDs and state accounts, with usage instructions and network notes. [1] [2]
• Updated the sidebar (sidebar.ts) to include the new Forwarder Directory, with highlighting for both language variants.

Improvements to Solana Workflow and Bindings Docs:

• Updated the Go and TypeScript bindings guides to clarify the recommended directory structure (e.g., using my-workflow/contracts/solana/src/idl/), and simplified the workflow handler examples to focus on usage of the generated bindings. [1] [2] [3] [4]
• Replaced step-by-step workflow setup instructions with concise code examples, and now direct users to the main "Writing to Solana" guide for end-to-end config, simulation, and deployment. [1] [2]
• Improved explanation of what the CLI generates and where, making the file paths relative to the workflow directory for clarity.

These changes make it easier for users to find and use the correct Solana forwarder addresses, and streamline the process of generating and integrating workflow bindings.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
documentation	Ready	Preview	Jul 16, 2026 9:59pm

[github-actions]

👋 dev-dist, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!