Timmy_Foundation/timmy-config
16
0
Fork 0
Code Issues 100 Pull Requests 16 Actions 1 Packages Projects Releases Wiki Activity

[OPS] Canonicalize the Google AI Studio / Gemini portal lane into a real daily quota path #292

New Issue
Open
opened 2026-04-06 17:29:33 +00:00 by Timmy · 0 comments
Timmy commented 2026-04-06 17:29:33 +00:00
Owner
Copy Link

Cross-audit finding: the Google AI Studio lane exists in fragments but is not a canonical routed worker lane. google exists as a Gitea user, aistudio appears stale/orphaned, and the active event/dispatch system does not treat AI Studio as a first-class quota path.

Why this matters:

  • daily free/manual Gemini portal quota is underused
  • dispatch is currently half-manual and identity drift makes the lane brittle

Acceptance criteria:

  • Choose and document one canonical identity for the AI Studio lane (google or an intentionally recreated replacement).
  • Remove or archive stale/orphaned token/user assumptions for the non-canonical lane.
  • Document the standard dispatch workflow in repo truth (prompt generation, tab focus, send, expected proof back into Gitea).
  • Prove one real issue is dispatched through the canonical Gemini portal lane and leaves durable evidence (comment, branch, PR, or issue update).
  • The resulting workflow is linked from this issue and usable daily without rediscovery.
Cross-audit finding: the Google AI Studio lane exists in fragments but is not a canonical routed worker lane. `google` exists as a Gitea user, `aistudio` appears stale/orphaned, and the active event/dispatch system does not treat AI Studio as a first-class quota path. Why this matters: - daily free/manual Gemini portal quota is underused - dispatch is currently half-manual and identity drift makes the lane brittle Acceptance criteria: - [ ] Choose and document one canonical identity for the AI Studio lane (`google` or an intentionally recreated replacement). - [ ] Remove or archive stale/orphaned token/user assumptions for the non-canonical lane. - [ ] Document the standard dispatch workflow in repo truth (prompt generation, tab focus, send, expected proof back into Gitea). - [ ] Prove one real issue is dispatched through the canonical Gemini portal lane and leaves durable evidence (comment, branch, PR, or issue update). - [ ] The resulting workflow is linked from this issue and usable daily without rediscovery.
Timmy self-assigned this 2026-04-06 17:29:34 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-sonnet
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 research
sonnet-ready
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity sonnet
No Assignees Timmy
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#292
Delete Branch "%!s()"

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?