[danielegaleazzi92]

Note

⏳ Draft · slice 4 of #80 (Antigravity host), the last · stacked on #83 → #82 → #81: merge in order, the diff shows the earlier slices until then

Problem

• Where: skills/super-board/references/run-workflow.md, skills/super-board/SKILL.md, scripts/super-board-usage.sh, docs/hosts.md, onboard
  • a. with ✨ [feat] host: detect Google Antigravity (agy) as a host #81–✨ [feat] lanes: headless Build, QA and Review on Antigravity (run --agy) #83 the host is named, the guards and permissions are installed and the lanes exist
  • b. the orchestrator still has no instructions for an Antigravity run: no --agy flag in the skill, no "Antigravity runs" section, a usage guard that only knows Claude's status line, a hosts page that says "not supported yet"
• Who: anyone typing /super-board run in Antigravity, or run --agy from Claude
• What happened: the backend works but nothing tells the orchestrator to use it, or how to tell when the agy quota is gone

Solution

• run-workflow.md: an "Antigravity runs" section as the twin of "Codex runs" (wave command, lane, router, ladder, no sub-agents, permissions, guards, quota, fallback, precondition, Windows shell); "inside Antigravity, plain run is --agy"; agy no longer halts at the host check; preconditions, the legacy-run scan, the skills-ready host list, the Launch step, the usage guard, the usage_fallback: "agy" bullet, the resume line and the stop line know the host; the run allowlist lists the two lane scripts and the permissions helper (tests/test_run_allowlist.py keeps them honest)
• SKILL.md: --agy [--low|--high] and --agy=<model> in the run verb, a routing row for --agy and for an Antigravity session, the cardinal rule names agy -p workers
• scripts/super-board-usage.sh: record recognises the agy status line (quota.<bucket>.{remaining_fraction, reset_time}), converts every bucket to {used_percentage, resets_at} and keeps it in its own snapshot (~/.gemini/super-board/usage.json); check --host agy weighs the buckets of the model the lanes use (--model, else agy.model: a gemini-* slug reads gemini-5h / gemini-weekly, a claude-* / gpt-* slug the 3p-* ones, a model-specific bucket only when the slug names it; no model known weighs every bucket) with the same usage_pause_pct, exits and staleness rules; --host claude is the unchanged default
• super-board-setup.py check/fix --host agy accepted (the resolver already knows the host since ✨ [feat] lanes: headless Build, QA and Review on Antigravity (run --agy) #83); onboard's silent detect names the host and step 8 runs the permissions helper with consent and reminds about the status line
• docs/hosts.md: the agy row becomes a supported host, plus a "First run on Antigravity" checklist (install, permissions, a guard probe, an allowed command, skills, quota, one card) with what each failure means

Acceptance criteria

• The agy status line JSON is recorded into the agy snapshot without touching Claude's; check --host agy reports the highest bucket, pauses at usage_pause_pct, reads unknown without a snapshot and refuses an unknown host
  ↳ verified: tests/test-usage.sh scenarios 11–14 (14 green)
• Every .claude/bin script the Antigravity path calls has a rule in the run allowlist
  ↳ verified: tests/test_run_allowlist.py
• Every accepted host value has a row in docs/hosts.md; the host script and setup accept agy
  ↳ verified: tests/test-hosts-doc.sh (4 hosts), tests/test-host.sh, super-board-setup.py check --host agy
• Following "Antigravity runs" by hand (plan, claim, super-board-agy-wave.sh, reconcile, release, manifest, throttle) a card went Ready → Done on agy 1.4.6: ✨ [feat] cart: percentage discount applied to the total danielegaleazzi92/super-board-agy-playground#2 (✨ [feat] host: run the board on Google Antigravity (agy) #80 has the run's manifest)
• End-to-end with this stack installed from the branches (install.sh --hosts agy --protect-main), agy 1.4.6 / gemini-3.8-flash on Windows 11, 2026-10-23: card feat: dynamic-workflow worker backend (worker_backend: "workflow") #3 of the playground went Ready → Done, ✨ [feat] cart: clearCart empties the cart and drops its discount danielegaleazzi92/super-board-agy-playground#4 (squash cc1b8ef), Build 8.5 min, QA + Review 19 min, every lane returning a valid structured result. The one lane that failed in between was denied on its first command because agy had rewritten its own settings file with a UTF-8 BOM and loaded no permissions from it; the helper now strips it (✨ [feat] install: guard hooks and permissions for Antigravity (agy) #82). The quota guard read the real status-line buckets (gemini-5h, gemini-weekly, gemini-argon-wtu-weekly, 3p-5h, 3p-weekly) and, once made per model family, answered ok for a Flash run while the Argon weekly bucket stood at 100%.

Iteration history

Lane	Done	Time	Details
🔨 author	✅	Oct 23	orchestrator reference + skill flags + usage guard + hosts doc · five suites green on Git Bash

Risk

🟢 Low · documentation for a new path plus one script that gains a second input shape.

• Door: two-way · revert and the Claude usage guard is the previous script line for line; the references lose a section
• Blast radius: super-board-usage.sh record for every Claude user (the Claude branch is untouched and tested first in the suite) · the Antigravity path for Antigravity users

Part of #80 (slice 4 of 4), stacked on #83. Windows note in the hosts page: agy runs statusLine.command through cmd /c, where a bare bash is WSL's and exits 127 on C:/ paths; name Git Bash by its space-free path. Note on tests: on Windows Git Bash test_run_allowlist.py and test_writing_format.py need PYTHONUTF8=1 on main too (they read the references with the console code page); with it both pass here.

🤖 Generated with Claude Code