Skip to content

feat: rename the user-facing word crewmate to mate - #20965

Merged
CrysisDeu merged 1 commit into
mainfrom
feat/20937-rename-crewmate-to-mate
Oct 22, 2026
Merged

CrysisDeu merged 1 commit into
mainfrom
feat/20937-rename-crewmate-to-mate

Conversation

@CrysisDeu

@CrysisDeu CrysisDeu commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Everywhere a person reads it, the standing teammate agent is called a Mate (plural Mates) instead of a Crewmate.

"Crewmate" is long, and its first half repeats the product name. The self-record MCP server is already kirocrew-mate, so the surface and the plumbing disagree. Scope was set on #20937: copy and docs only, and translations keep the crewmate/teammate feel they already carry.

Why it matters

The word is on the sidebar, the page title, every create/edit/delete dialog and most of the user-facing docs. A shorter word that matches the rest of the product reads better on every one of those surfaces.

Not a goal

  • Renaming code identifiers: crewmate_* functions, CREWMATE_* constants, component and test names, i18n keys, API paths, data-file names, the crewmate.* change-card kinds. Users never see them, and renaming them touches about 700 files and persisted state.
  • Re-translating catalogs that use a loanword for the English term (ja クルーメイト, ko 크루메이트, de Crewmate).
  • Renaming the seeded first mate, whose display name is already "Mate".
  • CHANGELOG.md (the release PR writes it).

What changed (motivation → approach → change)

Goal → change the word only where it is read → three layers:

  • i18n catalogs. Values only, never keys. en.json, en.manual.json and en.context.json: Crewmate → Mate, Crewmates → Mates. In the ten translated catalogs, the English page name had leaked into a few strings ("open Crewmates", "los crewmates"); those now use that locale's own teammate word (队友, Compañeros, Coéquipiers, Colegas, Напарники, Compagni, साथी, সঙ্গীরা, クルーメイト, 크루메이트). Nothing else in those catalogs changes.
  • Backend strings a person reads. Settings labels and help in config/sections.py, change-card titles and refusals, thread and goal-reminder text, team errors, security-posture labels, guide catalog titles, the welcome prompt. The welcome prompt now says "the first teammate on their crew", not "their first mate", so the model is not handed the ship rank.
  • Built-in dashboard templates. The English strings each template.html draws ("mate wrote this", "What this mate is doing", empty-state hints) and each manifest.json description. Comments and field keys such as crewmate_wrote are unchanged.
  • One machine compare. dashboard/goal_setup.py compares the goal reminder's skip reason by its text, so it now names the new wording too.
  • Nav surface label. The members surface's English machine value in surfaces/surfaceData.ts is now Mates.
  • Docs. Prose in docs/system-specs, docs/architecture, docs/ci, docs/reference, docs/feature-map, docs/build, website/docs, src/kiro_crew/docs and AGENTS.md. Inline code, link targets and fenced blocks are left alone. Two renamed headings had anchor links pointing at them; both links are updated.

Settings registry ids are derived from the label, so two ids moved: developer.crewmates → developer.mates and developer.reply-threads-on-crewmate-chat-messages → developer.reply-threads-on-mate-chat-messages. Both old ids are added to LEGACY_ID_EXACT, the table that already maps the card's two earlier ids, so a bookmark or palette history entry still lands on the right row.

Generated files are regenerated, not hand-edited: en-XA.json, the settings registry (TS + JSON), ui-index.generated.json, guidePlans.gen.ts, config-baseline.json.

A new decisions entry, docs/decisions/2026-10-15-the-standing-teammate-agent-is-called-a-mate.md, records the word. The four existing entries that say "crewmate" stay byte-identical.

Backwards compatibility

Compatible: config keys, API paths, i18n keys and stored data keep their names. The two settings ids that moved are aliased in LEGACY_ID_EXACT, so old deep links still highlight their row.

Reader: website/src/hooks/useSettingHighlight.ts:LEGACY_ID_EXACT -- crew page -- maps developer.crewmates and developer.reply-threads-on-crewmate-chat-messages onto the current ids; settingHighlightAliases.test.ts pins that no alias key is a live id
Reader: website/src/uiLocations/descriptors.ts:PREVIEW_FLAG_ENABLERS -- crew page -- names developer.mates, the id the registry now emits; members.locations.test.ts, uiIndex.test.ts
Reader: src/kiro_crew/docs/ui-index.generated.json:guide_gates -- chat -- regenerated from the same descriptor; test_find_ui_members.py, test_guide_select_gate.py, test_guide_ui_show.py

Tests

No new behaviour, so no new tests. Existing assertions that pin English copy now pin the new words: website component tests, Playwright specs, backend tests that match refusal text, GUI-user scenario prose. Tests that pin the moved settings ids now name developer.mates.

Manual verification

Built the SPA and booted an isolated pod from this worktree. On each frame below, the capture script asserted that the page shows "Mates" and that no "crewmate" text is rendered anywhere on the page.

Local static gates run green: tsc, eslint, npm run i18n:check (diff-scoped), black, isort, flake8, mypy, docs lint, and the decisions, feature-map, brand and comment-history gates. The test suites are left to CI.

Screenshots / video

Customize, Mates tab:

Customize, Mates tab

Mates page:

Mates page

New mate dialog, Settings → Developer, zh-CN keeps 队友

New mate dialog

Settings, Developer

zh-CN Customize

Related Issues

Closes #20937

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

Contribution License Agreement

Contributions are accepted under the project's Apache-2.0 license.

@CrysisDeu
CrysisDeu requested review from a team and KiroCrewCaptain as code owners October 15, 2026 22:02
@CrysisDeu
CrysisDeu requested a review from buluoray October 15, 2026 22:02
@CrysisDeu
CrysisDeu force-pushed the feat/20937-rename-crewmate-to-mate branch from 64d6b60 to 35b2f66 Compare October 15, 2026 22:03
@github-actions

github-actions Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Sensitive Change Review

Sensitive files changed:

  • src/kiro_crew/security_posture.py

  • @CrysisDeu posted a complete reasoning template for a9e5c81.

@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 15, 2026
@github-actions

github-actions Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of a9e5c819b489c0c519b0ab7835723830b8dde473 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: PASS

This is a relabel. The only reason given is that "Crewmate" is long and repeats the product name, not that anyone was failing to find the feature. Because a maintainer signed the scope on #20937, it stays a note.

Notes

  • Item 1 — inherited: a relabel should name who was failing to find the feature. The reasons given are "'Crewmate' is long" and "the surface and the plumbing disagree", which are about consistency, not harm. Its only provenance is the decisions entry this PR adds, plus feat: rename the user-facing word Crewmate to Mate (copy and docs only) #20937.
  • Item 6 — symptom-level: goal_setup.py:168 still detects the skip reason by matching the prose string "skipped: the mate's thread is not open", which goal_reminder.py repeats as a literal at 3 sites. The next copy edit will break the match silently, as this rename nearly did. Subtraction: replace the 4 literals with one name that goal_reminder already exports.

What this change ships

Inventory (8 items) — 6 justified

Intent: users see the standing teammate agent called "Mate"/"Mates" everywhere they read it. This is an ADDITION (a relabel).

  1. Sidebar, page title, dialogs and settings say Mate/Mates instead of Crewmate — inherited relabel, no failing user named
  2. Ten translated catalogs replace the leaked English "Crewmates" with the locale's own word — justified
  3. Backend refusals, errors, change-card and reminder text say "mate" — justified
  4. The welcome prompt tells the model "first teammate on their crew" — justified
  5. Built-in dashboard templates' visible strings and manifest descriptions say "mate" — justified
  6. The goal-setup skip check matches the new reminder text — symptom-level: string compare
  7. Two settings deep-link ids change, with old ids aliased in LEGACY_ID_EXACT — justified
  8. Docs prose plus a new decisions entry — justified

[FIRST-PRINCIPLES-REVIEWED] a9e5c81

Description read

[DESCRIPTION-READ] 67ed83b394ade0737cb3a30d6cf24cd5cce64c770a64277aae74f8c64f0235d3

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed a9e5c819b489c0c519b0ab7835723830b8dde473 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] a9e5c81

Verdict parsed from the review's SHA-scoped output markers for commit a9e5c819b489c0c519b0ab7835723830b8dde473.

False positive or not applicable? A repository writer can comment:
/ai-review override fable a9e5c819b489c0c519b0ab7835723830b8dde473: <one-sentence reason>

@github-actions

github-actions Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of a9e5c819b489c0c519b0ab7835723830b8dde473 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] a9e5c81

False positive or not applicable? A repository writer can comment:
/ai-review override gpt a9e5c819b489c0c519b0ab7835723830b8dde473: <one-sentence reason>

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: checking Automated validation is still running labels Oct 15, 2026
@CrysisDeu
CrysisDeu force-pushed the feat/20937-rename-crewmate-to-mate branch from 35b2f66 to 7d6a110 Compare October 16, 2026 10:32
@CrysisDeu

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: 7d6a110
  • What rule changed: none. src/kiro_crew/security_posture.py changes only the English title and description text of four posture rows ("Crewmate goals" → "Mate goals", "a crewmate's dashboard page" → "a mate's dashboard page", and so on). No rule id, scope, check function, threshold or control flow is touched.
  • Before -> after (what was allowed/blocked, now): unchanged. Every row allows and blocks exactly what it did; only the words a person reads on the posture page differ.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): a posture row reads with the old word. No command, secret or login is affected.
  • Evidence checked (which sandbox result proves it): git diff origin/main -- src/kiro_crew/security_posture.py shows only string-literal edits inside the row titles and descriptions; mypy and flake8 are clean on this head.
  • No regression:
    • Tools still work (which tools/commands were run, result): no tool or command path reads these strings; the posture page renders them as text.
    • Backward compatible (old config / old data / old callers still work, how checked): row ids are unchanged, so stored acknowledgements and callers keyed by id still match; checked in the diff.
    • Existing tests (which suites passed on this head): the CI backend suite on this head; locally the posture-adjacent targeted tests and the static gates (black, isort, flake8, mypy).
  • How to undo: revert the string edits in src/kiro_crew/security_posture.py, or revert this PR.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running merge conflict Branch has merge conflicts with its base — author must resolve before merge labels Oct 16, 2026
@CrysisDeu
CrysisDeu force-pushed the feat/20937-rename-crewmate-to-mate branch from 7d6a110 to 140025a Compare October 16, 2026 11:13
@CrysisDeu

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: 140025a
  • What rule changed: none. src/kiro_crew/security_posture.py changes only the English title and description text of four posture rows ("Crewmate goals" → "Mate goals", "a crewmate's dashboard page" → "a mate's dashboard page", and so on). No rule id, scope, check function, threshold or control flow is touched.
  • Before -> after (what was allowed/blocked, now): unchanged. Every row allows and blocks exactly what it did; only the words a person reads on the posture page differ.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): a posture row reads with the old word. No command, secret or login is affected.
  • Evidence checked (which sandbox result proves it): git diff origin/main -- src/kiro_crew/security_posture.py shows only string-literal edits inside the row titles and descriptions; mypy and flake8 are clean on this head.
  • No regression:
    • Tools still work (which tools/commands were run, result): no tool or command path reads these strings; the posture page renders them as text.
    • Backward compatible (old config / old data / old callers still work, how checked): row ids are unchanged, so stored acknowledgements and callers keyed by id still match; checked in the diff.
    • Existing tests (which suites passed on this head): the CI backend suite on this head; locally the posture-adjacent targeted tests and the static gates (black, isort, flake8, mypy).
  • How to undo: revert the string edits in src/kiro_crew/security_posture.py, or revert this PR.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 16, 2026
@CrysisDeu
CrysisDeu force-pushed the feat/20937-rename-crewmate-to-mate branch from 140025a to 8963f9b Compare October 21, 2026 20:47
@CrysisDeu

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: 8963f9b
  • What rule changed: none. src/kiro_crew/security_posture.py changes only the English title and description text of four posture rows ("Crewmate goals" → "Mate goals", "a crewmate's dashboard page" → "a mate's dashboard page", and so on). No rule id, scope, check function, threshold or control flow is touched.
  • Before -> after (what was allowed/blocked, now): unchanged. Every row allows and blocks exactly what it did; only the words a person reads on the posture page differ.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): a posture row reads with the old word. No command, secret or login is affected.
  • Evidence checked (which sandbox result proves it): git diff origin/main -- src/kiro_crew/security_posture.py shows only string-literal edits inside the row titles and descriptions; mypy and flake8 are clean on this head.
  • No regression:
    • Tools still work (which tools/commands were run, result): no tool or command path reads these strings; the posture page renders them as text.
    • Backward compatible (old config / old data / old callers still work, how checked): row ids are unchanged, so stored acknowledgements and callers keyed by id still match; checked in the diff.
    • Existing tests (which suites passed on this head): locally 5,900+ targeted backend tests and 1,450+ targeted frontend tests touching the renamed copy, plus black, isort, flake8, mypy, tsc, eslint and the i18n gates. The full suites run in CI.
  • How to undo: revert the string edits in src/kiro_crew/security_posture.py, or revert this PR.

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 22, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@CrysisDeu marked the ux AI finding as false positive, not applicable, or explicitly accepted for 12a9805447d47f7f8073fc2d2a35ac2c1f2eb5ae.

the lane failed closed on its 1 MB diff cap before reading anything; this PR is a copy-only rename of Crewmate to Mate (values, docs, test pins, regenerated files), screenshots are in the description, and the maintainer chose one PR over a split.

This decision applies only to this commit. A new push requires a new judgment.

@CrysisDeu

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: 0f58984
  • What rule changed: none. src/kiro_crew/security_posture.py changes only the English title and description text of six posture rows ("Crewmate goals" → "Mate goals", "a crewmate's dashboard page" → "a mate's dashboard page", and so on). No rule id, scope, check function, threshold or control flow is touched.
  • Before -> after (what was allowed/blocked, now): unchanged. Every row allows and blocks exactly what it did; only the words a person reads on the posture page differ.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): a posture row reads with the old word. No command, secret or login is affected.
  • Evidence checked (which sandbox result proves it): git diff origin/main -- src/kiro_crew/security_posture.py shows only string-literal edits inside the row titles and descriptions; mypy and flake8 are clean on this head.
  • No regression:
    • Tools still work (which tools/commands were run, result): no tool or command path reads these strings; the posture page renders them as text.
    • Backward compatible (old config / old data / old callers still work, how checked): row ids are unchanged, so stored acknowledgements and callers keyed by id still match; checked in the diff.
    • Existing tests (which suites passed on this head): locally 5,900+ targeted backend tests and 1,450+ targeted frontend tests touching the renamed copy, plus black, isort, flake8, mypy, tsc, eslint and the i18n gates. The full suites run in CI.
  • How to undo: revert the string edits in src/kiro_crew/security_posture.py, or revert this PR.

@CrysisDeu

Copy link
Copy Markdown
Contributor Author

/ai-review override design 0f58984: the lane failed closed on its 1 MB diff cap before reading anything; this PR is a copy-only rename of Crewmate to Mate (values, docs, test pins, regenerated files), screenshots are in the description, and the maintainer chose one PR over a split.

@CrysisDeu
CrysisDeu force-pushed the feat/20937-rename-crewmate-to-mate branch from 12a9805 to 0f58984 Compare October 22, 2026 02:30
@CrysisDeu

Copy link
Copy Markdown
Contributor Author

/ai-review override ux 0f58984: the lane failed closed on its 1 MB diff cap before reading anything; this PR is a copy-only rename of Crewmate to Mate (values, docs, test pins, regenerated files), screenshots are in the description, and the maintainer chose one PR over a split.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@CrysisDeu marked the design AI finding as false positive, not applicable, or explicitly accepted for 0f5898464ae9c11a4f558abdbf774b27d96c6629.

the lane failed closed on its 1 MB diff cap before reading anything; this PR is a copy-only rename of Crewmate to Mate (values, docs, test pins, regenerated files), screenshots are in the description, and the maintainer chose one PR over a split.

This decision applies only to this commit. A new push requires a new judgment.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@CrysisDeu marked the ux AI finding as false positive, not applicable, or explicitly accepted for 0f5898464ae9c11a4f558abdbf774b27d96c6629.

the lane failed closed on its 1 MB diff cap before reading anything; this PR is a copy-only rename of Crewmate to Mate (values, docs, test pins, regenerated files), screenshots are in the description, and the maintainer chose one PR over a split.

This decision applies only to this commit. A new push requires a new judgment.

@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Oct 22, 2026
buluoray
buluoray previously approved these changes Oct 22, 2026

@buluoray buluoray left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-approve at 0f58984 after the rebase onto 3d6cda4.

I compared this PR's own diff on the head I approved (4e6e07f) and on this one. The only new lines are the same crewmate → mate rename applied to text main added since (gui-user scenario selectors, the notifications and members spec paragraphs and the feature-map row); no identifier, i18n key, config key or API path moved, and the en catalogs still have no user-visible "Crewmate" left (only key names such as runs_as_crewmate, which the scope keeps).

Before merge: the branch now conflicts with main in src/kiro_crew/docs/ui-index.generated.json, a generated file, so regenerate it after rebasing rather than hand-merging.

Nit, not blocking: website/scripts/capture-agent-template-pane.mjs:193 still matches /used by this crewmate only/i. No UI string with that text exists on this head any more (the pane it captured was removed by #21748), so the capture script is stale either way; it sits outside CI.

Everywhere a person reads it, the standing teammate agent is now a Mate
(plural Mates): the Mates page, roster, create/edit/delete dialogs, chat
header, settings rows, change-card titles, thread error text and the
user-facing docs. Only values change in the i18n catalogs; keys, code
identifiers, API paths, data-file names and the crewmate.* card kinds keep
their spelling.

Translations keep the teammate sense they already carry (队友, compañero,
coéquipier, colega, напарник, compagno, साथी, সঙ্গী). Where a catalog had
leaked the English page name ("open Crewmates") it now names the page by
that locale's own title. Catalogs that use a loanword for the English term
(クルーメイト, 크루메이트, German Crewmate) are left as they are.

The two Settings rows whose derived registry ids carried the word move to
developer.mates and developer.reply-threads-on-mate-chat-messages; the old
ids are added to LEGACY_ID_EXACT so bookmarks and palette history keep
their highlight. en-XA, the settings registry, the ui index and
config-baseline.json are regenerated.

A decisions entry records the word; the maintainer restates it on the PR.

Closes #20937
@CrysisDeu

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: a9e5c81
  • What rule changed: none. src/kiro_crew/security_posture.py changes only the English title and description text of six posture rows ("Crewmate goals" → "Mate goals", "a crewmate's dashboard page" → "a mate's dashboard page", and so on). No rule id, scope, check function, threshold or control flow is touched.
  • Before -> after (what was allowed/blocked, now): unchanged. Every row allows and blocks exactly what it did; only the words a person reads on the posture page differ.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): a posture row reads with the old word. No command, secret or login is affected.
  • Evidence checked (which sandbox result proves it): git diff origin/main -- src/kiro_crew/security_posture.py shows only string-literal edits inside the row titles and descriptions; mypy and flake8 are clean on this head.
  • No regression:
    • Tools still work (which tools/commands were run, result): no tool or command path reads these strings; the posture page renders them as text.
    • Backward compatible (old config / old data / old callers still work, how checked): row ids are unchanged, so stored acknowledgements and callers keyed by id still match; checked in the diff.
    • Existing tests (which suites passed on this head): locally 5,900+ targeted backend tests and 1,450+ targeted frontend tests touching the renamed copy, plus black, isort, flake8, mypy, tsc, eslint and the i18n gates. The full suites run in CI.
  • How to undo: revert the string edits in src/kiro_crew/security_posture.py, or revert this PR.

@CrysisDeu

Copy link
Copy Markdown
Contributor Author

/ai-review override design a9e5c81: the lane failed closed on its 1 MB diff cap before reading anything; this PR is a copy-only rename of Crewmate to Mate (values, docs, test pins, regenerated files), screenshots are in the description, and the maintainer chose one PR over a split.

@CrysisDeu

Copy link
Copy Markdown
Contributor Author

/ai-review override ux a9e5c81: the lane failed closed on its 1 MB diff cap before reading anything; this PR is a copy-only rename of Crewmate to Mate (values, docs, test pins, regenerated files), screenshots are in the description, and the maintainer chose one PR over a split.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@CrysisDeu marked the design AI finding as false positive, not applicable, or explicitly accepted for a9e5c819b489c0c519b0ab7835723830b8dde473.

the lane failed closed on its 1 MB diff cap before reading anything; this PR is a copy-only rename of Crewmate to Mate (values, docs, test pins, regenerated files), screenshots are in the description, and the maintainer chose one PR over a split.

This decision applies only to this commit. A new push requires a new judgment.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@CrysisDeu marked the ux AI finding as false positive, not applicable, or explicitly accepted for a9e5c819b489c0c519b0ab7835723830b8dde473.

the lane failed closed on its 1 MB diff cap before reading anything; this PR is a copy-only rename of Crewmate to Mate (values, docs, test pins, regenerated files), screenshots are in the description, and the maintainer chose one PR over a split.

This decision applies only to this commit. A new push requires a new judgment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge conflict Branch has merge conflicts with its base — author must resolve before merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: rename the user-facing word Crewmate to Mate (copy and docs only)

2 participants