Repository navigation
fix(i18n): gloss "remote crew" on the Developer feature previews - #16708
Conversation
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing to check. [DESIGN-REVIEWED] 4b5b430 Description read[DESCRIPTION-READ] 1592022ae28f95141eb0c54fc1056aeb3536a1e2fface5752a5629c48bb7501c That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
First Principles Review (Opus 5.5) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS Nothing to check. What this change shipsInventory (2 items) — 2 justifiedIntent: Make it clear to someone on Developer > Feature Previews that "remote crew" means another machine they connected, not their own agents. This is a FIX (Closes #12767).
[FIRST-PRINCIPLES-REVIEWED] 4b5b430 Description read[DESCRIPTION-READ] fccce7468b1c5129e8f427eca484c13a4ecb7206cb4b581787f7d186f29ba880 That sha256 names the PR description this verdict read. Recompute it with |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
UX Review (Opus 5.5) — ✅ PASSUX-level review of UX-Verdict: PASS Check that the gloss is enough while it sits behind the (i): from the row alone, the blind reader still had "no idea from this shot" what "Remote crew sessions" does. Suggestions
[UX-REVIEWED] 4b5b430 Description read[DESCRIPTION-READ] 42306074210c11df339b990dd2b0d71ec22bd19b15d9abb3c3f2577ac8313107 That sha256 names everything this verdict read: the PR description, plus the 6 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
The Remote crew sessions preview hint now says a remote crew is another machine you have connected, not your agents, so the word no longer reads as the agent team on a page that shows both senses. Translated in every locale; en-XA and the settings registry regenerated. Closes #12767
f2987a5 to
4b5b430
Compare
Problem / Motivation
Goal: On Developer > Feature Previews, a reader can tell that "remote crew" means another machine, not their agents.
The Feature Previews page shows "crew" in two senses side by side: the Crewmates card (your agents) and the Remote crew sessions card (another machine you connected). The Remote crew sessions hint says "Merge a connected remote crew's live sessions…" with no gloss, so it reads as the agent team. In Russian it is worse, since «команда» also means "team".
Why it matters
Someone turning on the preview can think it merges their own agents' sessions. That is wrong, and the toggle gives no other clue.
Not a goal
What changed (motivation → approach → change)
Two senses of one word on one page → say which sense this card means, once → one sentence added to the existing hint
pages.developer.featurePreviewsTab.merge_a_connected_remote_instances_live_sessions: "A remote crew is another machine you have connected, not your agents." It sits before the closing "Functional, but not finished." Amending the existing hint is smaller than a new key and needs no component change. The sentence is translated in all 11 other locale catalogs underwebsite/src/i18n/locales/(en.jsonplusbn,de,es,fr,hi,it,ja,ko,pt,ru,zh-CN), reusing each locale's existing word for remote crew. The en-XA pseudolocale and the generated settings registry (settingsRegistry.gen.ts,settings-registry.generated.json) are regenerated, so the command palette shows the same text.Backwards compatibility
Compatible: one string value changes; no key is added, renamed, or removed.
Removes nothing: only adds a sentence to an existing hint.
Tests
No new tests: this is a copy change.
npm run i18n:checkwithI18N_BASE_REF=origin/mainpasses all 19 checks, including changed-values QA and pseudolocale sync.vitest run src/i18n(45 files, 733 tests, includes every locale style test) andvitest run src/pages/settings(20 files, 494 tests) pass.Manual verification
Built the SPA and opened Settings > Developer with stubbed APIs, in light and dark themes. The Remote crew sessions hint shows the new sentence.
Screenshots / video
Settings > Developer > Feature Previews, Remote crew sessions card.
Remote crew sessions hint open, showing the new sentence (light theme):
Related Issues
Closes #12767
Pattern harvest
Not generalizable: a one-off copy gloss for one overloaded word on one card.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)