GeminiClaw Public Workspace
This file is intentionally public-safe.
What belongs here
- Current public release notes that are safe to publish.
- High-level roadmap items visible to contributors.
- Short operational reminders that apply to all users.
What must not live here
- Incident logs with private runtime data.
- Customer names, account IDs, or internal project references.
- Recovery transcripts, production screenshots, or support notes.
- Secrets, tokens, or environment-specific instructions.
Histórico de Entregas
| Data | Entrega | Detalhes | |---|---|---| | 2026-04-22 | Módulo Google Search Console — 100% concluído | 7 tools: `gsc_sites_list`, `gsc_search_analytics_query`, `gsc_sitemaps_list`, `gsc_sitemaps_get`, `gsc_sitemaps_submit`, `gsc_sitemaps_delete`, `gsc_url_inspection_inspect`. OAuth 2.0 PKCE delegado ao usuário. Auth + client + repository + audit log + confirmação 2 etapas. 44 testes verdes. Build TS limpo. | | 2026-04-21 | ADK Delivery Contract V4 — 100% concluído | Phase 2d: tools `generate_image`, `edit_image`, `generate_google_ads_report` migradas para `ToolArtifactResult`. Phase 7 T16/T17: concorrência e fallback outputSchema cobertos. Phase 5c: endpoint `/api/contract-kpis` + dashboard `contract-kpis.jsx`. Phase 6: endpoint admin `POST /api/sessions/:id/rollback`. Fix otimístico no rescue (claim `sent=true` pré-await). 64 testes verdes. Build TS limpo. |
Public Roadmap Snapshot
- Keep the Telegram-first quickstart stable and easy to validate.
- Treat advanced integrations as optional extensions, never prerequisites.
- Preserve local-first storage defaults and explain them clearly in docs.
- Maintain public-safe audits that block private references from re-entering the repo.
Documentation Contract
When a structural change lands, update at least one of:
- `README.md`
- `ARCHITECT.md`
- `WORKSPACE.md`
Audit Policy
- Public-facing audits should allow only neutral placeholders like `brand-example`.
- Runtime code, docs, UI copy, and tests must not reintroduce private client names, domains, or account identifiers.
- Audit implementation details should also stay generic, so history sanitization cannot mutate the guardrails themselves into invalid code.
- High-risk integrations can stay in the repo only as optional install paths; they must not be part of the default public dependency graph unless their vulnerability baseline is acceptable.