Add cli/ folder for the Foundry Local CLI 0.10.0 preview

[Wayne-Ch]

Add cli/ folder for the Foundry Local CLI preview

What this PR does

Adds a new top-level cli/ folder with documentation for the Foundry Local CLI 0.10.0 preview. No binaries are committed to the repo — the 8 signed binaries ship as assets on the GitHub Release tagged cli-preview-0.10.0 (created separately after this PR merges).

cli/
├── README.md                 (~2 KB) — what the CLI is, install per OS, quick start, links
├── RELEASE-NOTES-0.10.0.md   (~3 KB) — body for the GitHub Release page
└── LICENSE.txt               (~1 KB) — MIT (same as the SDKs in this repo)

Why this folder, and why now

The Foundry Local CLI has been an internal tool until now. With 0.10.0 we are publishing a public preview so external users can try it directly from the terminal. The folder exists to:

1. Give the binary release a documented home in the public repo
2. Set explicit expectations that this is a preview (rough edges expected, please file issues)
3. Make clear that the SDKs remain the supported integration surface — the CLI is an optional companion tool, not a required dependency

Positioning (important)

• The CLI is preview-tier and the surface may change.
• The CLI is optional. The Foundry Local SDKs (C#, JavaScript, Python, Rust) are the supported contract for application integration.
• This preview ships under MIT license, matching the SDKs already in this repo.

Version

0.10.0 (intentionally sub-1.0 to signal preview status). The corresponding GitHub Release will be tagged cli-preview-0.10.0 with the prerelease flag set, so the repo's "Latest release" pointer continues to reference the SDK GA release.

What is NOT in this PR

• CLI source code (lives in a separate private tree, not affected by this PR)
• Binary artifacts (will be uploaded to the GitHub Release directly, not committed)
• Changes to existing sdk/, samples/, docs/, etc.
• Top-level README changes (can be a follow-up if you want a pointer added)

Release follow-up (separate from this PR)

After this PR merges:

1. Tag cli-preview-0.10.0 on the merge commit
2. Create the GitHub Release with prerelease enabled
3. Upload the 8 signed binaries + SHA256SUMS.txt:
   • foundry-0.10.0-win-x64-winml.msix / -win-x64.msix
   • foundry-0.10.0-win-arm64-winml.msix / -win-arm64.msix
   • foundry-0.10.0-osx-arm64.pkg / .zip
   • foundry-0.10.0-linux-x64.tar.gz / -linux-arm64.tar.gz
4. Release body = contents of cli/RELEASE-NOTES-0.10.0.md

Verification

• All 4 Windows MSIX signed by CN=Microsoft Corporation, issuer Microsoft Code Signing PCA 2024, Authenticode Valid
• macOS .pkg and .zip produced through the macOS signing/notarization pipeline (see ADO build 1246347)
• Hashes committed alongside the binaries in SHA256SUMS.txt

Checklist

• Files use the same conventions as existing top-level READMEs in this repo
• License declared (MIT) and matches SDK licensing
• No binaries committed
• Preview status called out prominently in both README and release notes
• Release branch / tag created (follow-up)
• Release published with prerelease flag (follow-up)

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
foundry-local	Ready	Preview, Comment	Jun 4, 2026 6:33pm

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Wayne-Ch]

Switching to release-only delivery (no docs in repo for this preview). Branch will be deleted; the 3 docs are preserved locally and the binaries + release notes ship as a prerelease GitHub Release tagged cli-preview-0.10.0.