docs: correct fabricated google-adk + gemini-cli runtime tutorials #2004
Reference in New Issue
Block a user
Delete Branch "fix/google-adk-runtime-doc-accuracy"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes the two molecule-core runtime tutorials flagged in RFC internal#730 as fabricated (misattributed PR refs + claims of shipped runtimes that did not exist).
google-adk[mcp]==2.1.0, never[a2a]), Vertex AI via ADC (keyless), a2a-1.x bridge; correct PR refs (template PR #1, core #2003, ci #26); honest landing-status banner.gemini-cliruntime exists. Added a correction banner pointing to the realgoogle-adkruntime.Follow-up: the same-class fabricated
marketing/devrel/gemini-cli-demo/README.mdlives in theinternalrepo (separate fix). tier:low (docs only).🤖 Generated with Claude Code
Reviewed: docs-only correction of two fabricated runtime tutorials. (1) gemini-cli page now carries an accurate banner saying it is aspirational/not-shipped (no gemini-cli in manifest.json or knownRuntimes) and corrects the bogus PR #379 citation. (2) google-adk page is rewritten to truthful "landing, not yet on main" status, removes the false "already first-class"/PR #550 claims, and now accurately documents the engine-only ADK model, the google-adk[mcp]==2.1.0 vs a2a-sdk>=1.0 pinning, the platform-bridged A2A executor, and Vertex-ADC/AI-Studio auth paths. Matches the real implementation in the template repo. No code paths touched. All required CI (Go/Python/E2E/lint/secret-scan) green. Approve.
QA review: docs-only change, no behavior/test surface. Verified the corrected claims against reality — no gemini-cli/google-adk runtime on main yet, cited PRs (#379/#550) are unrelated, and the new google-adk page accurately describes the landing implementation and auth modes. Truthfulness restored. Approve.
Security review (gate: security-team): docs-only change to two markdown tutorials under docs/tutorials/. No code, config, secrets, IAM, or workspace-surface changes; secret-scan CI is green. The edits remove fabricated capability claims and correct PR citations — net reduction in misleading content, no security-relevant attack surface. Approve.
/qa-recheck
/security-recheck
Gate refire: qa-team APPROVE present (core-qa) and security-team APPROVE present (core-security). Docs-only PR; required CI (all-required, API smoke, Handlers PG) already green.