[AAASM-4728] ⬆️ (examples): Bump SDK pins to v0.0.1-rc.6

[Chisanan232]

What changed

Bump every example in the repo onto the just-published Agent Assembly SDK v0.0.1-rc.6 (python 0.0.1rc6, node 0.0.1-rc.6, go v0.0.1-rc.6), which are live on PyPI / npm / the Go module proxy. Driven end-to-end by the repo's sdk-version-bump skill: the only hand-edit is metadata/sdk-versions.yaml (the single source of truth); scripts/generate_example_metadata.py + extract_snippets.py rewrite every version-bearing surface (manifests, scenario Dockerfile pins, generated sdk-install README block, Prerequisites rows in table + bullet form, and the CI install pins), and each ecosystem's lockfiles are regenerated to match.

Commits are split for bisectability: the version swap (source of truth + all generator-owned surfaces, --check green at that commit), then per-ecosystem lockfile regen (go.sum ×5, pnpm-lock ×7, uv.lock ×18).

Related ticket

Closes AAASM-4728

How to verify

• python scripts/generate_example_metadata.py --check exits 0 (no orphan version literal disagrees with the source of truth).
• Re-running the generator + snippet extractor leaves a clean tree (idempotent).
• example-metadata-check.yml re-runs the generator, snippet extractor, the orphan audit, and the generator unit tests; the per-ecosystem verify-* mock lanes install the pinned rc.6 SDK and run each example's offline --mock path.

Checklist

• PR title follows [AAASM-XXXX] <GitEmoji> (<scope>): <summary>
• No secrets, API keys, or .env files committed
• Example sub-projects include their own README.md with prerequisites and run instructions
• SDK/runtime version dependencies are documented or pinned

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Chisanan232]

Review — Claude Code

Reviewed against AAASM-4728 and the repo's sdk-version-bump skill runbook.

1. CI — all green. 49 checks success, 1 skipped (the intentionally rc-gated live: live-core-enforcement (real gateway) lane, quarantined per the repo's live-lane policy — not a regression). The metadata drift audit gate and SonarCloud Code Analysis both pass.

2. Scope — complete. Every version-bearing surface moved to v0.0.1-rc.6 from the single source of truth (metadata/sdk-versions.yaml): 30 manifests, 32 README/doc surfaces, 1 scenario Dockerfile pin, the CI install pin (verify-live.yml), and the 30 regenerated lockfiles (18 uv + 7 pnpm + 5 go). Generator --check orphan-literal audit exits 0 and regeneration is idempotent (clean tree). No hand-edited version literals. Matches the ticket AC exactly; nothing missing.

3. No side effects on existing behavior. Zero source-code files changed (no .py/.ts/.go). The diff is version pins + regenerated lockfiles + generated README literals only. The single behavioral change is which SDK version each example installs/advertises (rc.5 → rc.6) — the intended change — with no alteration to any example's governance logic, mock trajectory, or business logic.

4. Front-end — N/A. No front-end surface in this repo (python/node/go example gallery, no dashboard/UI), so no Playwright validation applies.

One fix applied during review: CI pins pnpm v10, but the initial node-lock regen used pnpm 11, whose different pnpm.overrides encoding tripped ERR_PNPM_LOCKFILE_CONFIG_MISMATCH on mastra (the only node example with a pnpm.overrides block). Regenerated mastra's lock with pnpm 10 to match CI (commit 8551ef2); mastra is now green.

Verdict: ready to approve + merge. Needs one Pioneer approval (branch protection).