* test(#4709): assert no shipped surface mints a retired runtime id
Extends the #1928 removal guard to the surfaces it structurally could not
reach. Its own docblock scopes it to the installer CLI contract and the
runtime-name-policy exports; it spawns the installer and inspects module
exports, and never reads gsd-core/workflows/**, commands/** or skills/**.
Four structural assertions, all RED on next:
- every RUNTIME= assignment must name a canonical runtime
- the runtime->model-tier table must name only model-catalog runtimes
- runtime selection menus must offer only canonical runtimes
- config-set runtime / model_profile_overrides examples must be canonical
Structural, not textual: each asserts the literal is canonical or the runtime
exists as a catalog key, never that the string "gemini" is absent. That string
is load-bearing across Antigravity's real on-disk contract, so a fifth test
pins that contract from the descriptor (not from a resolved path, which would
read $ANTIGRAVITY_CONFIG_DIR and the real $HOME -- the #4312 defect class).
An over-broad gemini -> antigravity replacement fails there rather than ships.
The menu assertion is scoped by the nearest preceding `question:` matching
/runtime/i, because the same file carries a provider menu (anthropic, openai)
and a budget menu (high, medium, low) whose labels are single lowercase tokens
too and name neither a runtime nor anything the policy should judge.
Refs #4709
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* fix(#4709): stop minting the retired gemini runtime id in workflow text
#1928 removed the gemini runtime after Google sunset Gemini CLI on 2026-06-18,
but the removal stopped at the installer boundary. Runtime-loaded workflow text
kept assigning the id, and the name policy's unknown-id fallbacks then applied a
default designed for a never-known FUTURE runtime to an id GSD itself retired:
getRuntimeLabel('gemini') is 'Claude Code', getProjectInstructionFile('gemini')
is 'AGENTS.md', getGlobalConfigDir('gemini') is ~/.claude. A stale id produced a
plausible wrong answer instead of an error.
Those fallbacks are DELIBERATE and are left untouched here -- four docblocks
document them, src/runtime-name-policy.cts:220-222 calls the label default "the
always-safe default, fail-closed", and an existing test in this very suite pins
getProjectInstructionFile('gemini') === 'AGENTS.md'. This commit removes the
REACHABILITY of the retired id instead:
- new-project.md, ingest-docs.md: the runtime-detection cascade mapped
/.gemini/ and $GEMINI_CONFIG_DIR to RUNTIME=gemini. Both now map
/.gemini/antigravity{,-ide,-cli}/ and $ANTIGRAVITY_CONFIG_DIR to
RUNTIME=antigravity, the documented successor. ingest-docs.md was not in the
original report; the new structural test found it.
- settings-advanced.md: dropped the `gemini` row from the runtime->model-tier
table. The model catalog has no gemini runtime (runtimeTierDefaults has 18
keys, none of them gemini), so the row advertised built-in defaults for a
runtime whose config key is ignored. Its three model IDs were copied from the
`google` PROVIDER preset -- a provider axis rendered as a runtime axis.
- settings-advanced.md: removed the `gemini` / "Gemini CLI." runtime menu
option and its group listing, so no menu offers a runtime GSD cannot install.
- settings-advanced.md: repointed the config examples from `runtime gemini` to
`runtime antigravity`, which ships no built-in tier defaults and is therefore
the case those overrides actually exist for.
- reapply-patches.md: $GEMINI_CONFIG_DIR -> $ANTIGRAVITY_CONFIG_DIR,
~/.gemini/gsd-local-patches -> ~/.gemini/antigravity/gsd-local-patches, and
the local scan's bare .gemini -> .agents (Antigravity's localConfigDir). This
file is hand-written, so `npm run sync:launcher` never reached it.
- update.md: bare ~/.gemini and ./.gemini as GSD config dirs -> the real
~/.gemini/antigravity and ./.agents.
Antigravity's own Gemini-family surfaces are untouched by design: ~/.gemini as
its configHome parent, ~/.gemini/config for global skills/agents (#3738),
hookEvents "gemini", GEMINI.md as its projectInstructionFile, the
~/.gemini/antigravity{,-ide,-cli} ambiguity probes (#1441), and every gemini-*
model ID. The launcher's own GEMINI_CONFIG_DIR arm is left to #4632, which
absorbed #4347 for it.
Refs #4709
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* docs(#4709): record the Gemini -> Antigravity migration research
Primary-source research note behind #4709: the sense taxonomy that separates a
runtime-axis `gemini` (stale) from Antigravity's on-disk contract, Google's
model IDs, and release history (all load-bearing); the PRESERVE table; the
guard-gap analysis; and the per-file inventory with file:line citations.
Refs #4709
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* fix(#4709): keep the legacy patches probe, and stop tripping two lint gates
Three review findings, fixed inline.
1. Dropping the global ~/.gemini/gsd-local-patches probe was a regression: a
pre-#1928 Gemini CLI install put patches there, and a stranded patches dir is
still the user's work. Restored as an explicitly-labelled legacy arm probed
AFTER Antigravity, so a live install always wins. This is a directory probe,
not a runtime home -- it assigns no runtime id, so it does not reintroduce
the defect this PR closes. The $GEMINI_CONFIG_DIR env probe is deliberately
NOT restored: that names a runtime config home, which
tests/declarative-reference-antigravity.test.cjs:307 pins as ignored.
2. The comment added in (1) originally contained the literal string that the new
structural test matches, so the test flagged its own fix's comment as a mint.
Reworded. The test was right; a comment in shipped workflow text is as
readable to a matcher as code is.
3. docs/research/gemini-to-antigravity-migration.md used the colon slash-form
inside a quoted manifest description. lint-docs-command-form rejects it:
docs are never passed through the install-time converters, so the colon form
names a command no runtime registers. Normalised to the hyphen form.
Also verified, rather than assumed: the local scan's .agents entry is
unambiguous. Antigravity is the ONLY runtime declaring localConfigDir '.agents'
across all 19 capability manifests; grok and codex use ~/.agents as a GLOBAL
home, and this scan is local (./$dir).
Refs #4709
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* fix(#4709): retire Gemini CLI from the PR templates, and close two review gaps
Adversarial review findings, all fixed inline.
1. All three .github/PULL_REQUEST_TEMPLATE/*.md still offered "Gemini CLI" under
"Runtimes tested", and none offered Antigravity. #1928's follow-up dropped
Gemini CLI from .github/ISSUE_TEMPLATE/*.yml but missed the PR templates, so
every contributor opening a fix/feature/enhancement PR has been asked for two
releases which runtime they tested and offered a retired one. Now Antigravity.
Guarded by a new assertion: runtime checklist labels in the PR templates must
appear in the runtime label table. Proven non-vacuous by reverting one
template line and watching the probe report the offender.
2. The #4709 scanning corpus excluded agents/, which also ships runtime-loaded
markdown including .compact.md variants. Widened: 318 -> 382 files (+64), zero
new offenders, so the gap was coverage rather than a live defect.
3. gsd-core/workflows/sync-skills.md said "grok and gemini have no dedicated
installer flag — they alias the codex and claude skills roots respectively."
The gemini half is wrong twice over: the runtime is retired, and it never
aliased claude -- canonicalizeRuntimeName returns null for it and the caller's
fail-closed default merely happens to be claude. Describing that as designed
aliasing is exactly the confusion this issue is about. Reduced to grok, which
genuinely does alias the codex skills root.
4. The changeset said the runtime was removed in 1.11. It shipped in 1.8.0
(CHANGELOG.md:1023 is the enclosing release heading for the #1928 entry at
:1124). Corrected.
Refs #4709
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* test(#4709): follow the corrected sync-skills prose, and refresh the compact baseline
Three GREEN-run failures, all caused by this PR's own edits.
1. tests/sync-skills-cross-runtime-refuse.test.cjs pinned the literal phrase
"grok and gemini have no dedicated installer flag" — a test REQUIRING shipped
text to name a runtime retired in 1.8.0, which is the exact class #4709
exists to remove. The assertion and its rationale comment now track the
corrected prose ("grok has no dedicated installer flag"), and the docblock's
runtime list drops gemini. The remaining assertions in that file — the
guard's exit, the installer pointer, the $DEST reference, guard-before-copy
ordering — are untouched, so #3025's contract is otherwise intact.
2. tests/fixtures/compact-content-benchmark-baseline.json drifted because the
new-project.md edits changed its compacted size (split "new-project": off
14279 -> 14308, on 12335 -> 12364; aggregate off 107411 -> 107440).
Refreshed with `node scripts/benchmark-compact-content.cjs --write`, which
is that script's own documented remedy.
3. emitted-attribution reported four grown workflow files with no
acknowledgment. Acked below as commit trailers per ADR-3942, which moved the
acknowledgment out of tests/emitted-drift-acks/*.json fragments and into the
PR's own commit range (read with three-dot base...head). Exactly the four
files the gate named are acked — settings-advanced.md and sync-skills.md
shrank and are deliberately absent, since a trailer no delta consumed is a
staleAcks error.
Refs #4709
Emitted-Drift-Ack-Growth: ingest-docs.md — the runtime-detection cascade now names Antigravity's three real directories (/.gemini/antigravity{,-ide,-cli}/) and $ANTIGRAVITY_CONFIG_DIR in place of the single retired /.gemini/ arm and $GEMINI_CONFIG_DIR; three correct paths cost more bytes than the one wrong path they replace.
Emitted-Drift-Ack-Growth: new-project.md — same runtime-detection correction as ingest-docs.md, plus dropping "gemini/" from the two GEMINI.md instruction-file sentences so the prose stops contradicting getProjectInstructionFile, which returns AGENTS.md for that retired id.
Emitted-Drift-Ack-Growth: reapply-patches.md — restores the legacy ~/.gemini/gsd-local-patches probe as an explicitly-labelled arm after an adversarial-review finding that dropping it stranded a pre-#1928 user's patches, and repoints the env/global probes at Antigravity; the four-line comment is load-bearing, since a bare retired-runtime path with no explanation is exactly what the next reader would delete.
Emitted-Drift-Ack-Growth: update.md — bare ~/.gemini and ./.gemini as GSD config dirs are replaced by the real ~/.gemini/antigravity and ./.agents, which are longer strings; no content was added beyond the corrected paths.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* chore(#4709): backfill the changeset PR number
pr: 0 -> 4711, now that the PR exists. Never guessed ahead of the number.
Refs #4709
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---------
Co-authored-by: sim <sim@local>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
1110c3b4ee