chore(release): bump microsandbox to 0.7.0

[appcypher]

TL;DR

Bump the microsandbox release train from 0.6.9 to 0.7.0 across Rust crates, shared packages, SDKs, TypeScript examples, MCP, and the microsandbox skill.

Description

• Move all microsandbox* Rust workspace packages and exact internal dependency pins to 0.7.0.
• Bump @microsandbox/agent-client, @microsandbox/types, and the Node, Go, and Ruby SDK release metadata to 0.7.0.
• Update TypeScript examples, native Node platform package references, runtime version checks, and current Rust install snippets to 0.7.0.
• Regenerate Cargo and npm release lock metadata; unpublished Node platform packages remain omitted until the post-publish lockfile refresh resolves their tarballs.
• Advance the MCP and skills gitlinks through microsandbox-mcp#27 and skills#25.
• Include the changes since 0.6.9: native Windows console TTY handling, parallel release artifact builds, clearer bind-mount permission diagnostics and their build fix, dependency updates, and a Windows troubleshooting correction.

Test Plan

• cargo fmt --all -- --check and CI=1 MSB_HOME=/tmp/msb-release-0.7.0 cargo check --workspace pass
• CARGO_INCREMENTAL=0 CI=1 MSB_HOME=/tmp/msb-release-0.7.0 cargo test --workspace passes with host permissions required by Unix-socket tests
• CARGO_INCREMENTAL=0 CI=1 MSB_HOME=/tmp/msb-release-0.7.0 cargo clippy --workspace -- -D warnings passes
• Shared TypeScript packages and the Node SDK build, typecheck, test, and package successfully; generated TypeScript declarations and Ruby 0.7.0 metadata checks pass
• scripts/ci/publish-crates.py --validate-only validates the Rust publication waves, and npm dry-run publishes pass for all changed JavaScript packages
• cd sdk/go && go test -count=1 . and cd sdk/python && uv run ruff check . (deferred: Go and uv/Ruff are unavailable in this environment; the Rust workspace covers both native SDK crates)

Prompt To Fix All With AI

### Issue 1
sdk/ruby/ext/microsandbox/Cargo.toml:18
**Stale Ruby extension lockfile**

The source gem includes the standalone `Cargo.lock`, but this exact dependency now requires 0.7.0 while that lockfile still records the 0.6.9 dependency graph. Cargo therefore rewrites the shipped lockfile during extension compilation, making the build non-reproducible and preventing installation until the 0.7.0 crates are available.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "chore(release): bump microsandbox to 0.7..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

Context used:

• Context used - AGENTS.md (source)

[greptile-apps]

Stale Ruby extension lockfile

The source gem includes the standalone Cargo.lock, but this exact dependency now requires 0.7.0 while that lockfile still records the 0.6.9 dependency graph. Cargo therefore rewrites the shipped lockfile during extension compilation, making the build non-reproducible and preventing installation until the 0.7.0 crates are available.

Context Used: AGENTS.md (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: sdk/ruby/ext/microsandbox/Cargo.toml
Line: 18

Comment:
**Stale Ruby extension lockfile**

The source gem includes the standalone `Cargo.lock`, but this exact dependency now requires 0.7.0 while that lockfile still records the 0.6.9 dependency graph. Cargo therefore rewrites the shipped lockfile during extension compilation, making the build non-reproducible and preventing installation until the 0.7.0 crates are available.

**Context Used:** AGENTS.md ([source](https://github.com/superradcompany/microsandbox/blob/main/AGENTS.md))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.