Skip to content

feat: create a crewmate from one card on the Crewmates page - #18805

Merged
buluoray merged 2 commits into
mainfrom
feat/crewmate-one-card-create
Oct 13, 2026
Merged

buluoray merged 2 commits into
mainfrom
feat/crewmate-one-card-create

Conversation

@buluoray

@buluoray buluoray commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: A person makes a crewmate on the Crewmates page from one short card (a name and a look), and the new crewmate opens its chat by asking what it should do.

Today the Crewmates page's New crewmate opens the guided Meet CrewMates flow: four steps (goal, name and starting setup, schedule, ready) before a crewmate exists, then a creation receipt and a first message the page sends in the user's name. Someone who just wants a teammate has to answer a job description and a schedule up front, in a form, before they have talked to it at all. The full form sits behind a separate Advanced row in the "+" menu, so there are two different create surfaces for one action.

Why it matters

Making a crewmate is the first thing a person does on the Crewmates page. Every extra step there is paid before they see any value, and the questions the guided flow asks (what exactly should it do, when should it run) are ones people answer better in conversation once the crewmate is in front of them. One card with a crewmate that asks for its own goal makes creating a crewmate a few seconds of work, and keeps the goal and schedule in the place where they can be discussed and changed.

Not a goal

  • Change cards (crewmate.create proposals with first_greeting): they are not on main and stay in feat: let crewmates propose changes the user confirms as cards #18448.
  • Changing the crew manager's own create door beyond opening the same card with Advanced settings unfolded.
  • Removing the dashboard.crewmates_onboarded config field or its theme endpoints: the gateway keeps carrying it for compatibility.
  • New schedule UI: the crewmate offers a schedule in conversation with its existing schedule tool.
  • Mate's own first welcome: unchanged.

What changed (motivation → approach → change)

Goal → one create surface and a crewmate that asks for its own goal → port of #17617 (merged into feat/crewmate-assistant-integration as 49801cb) onto main, adapted to main's Mate welcome. The decision is recorded as an amendment to rfc-crewmates-launch.md § 02 in this PR (§ 08 marked superseded); that RFC is accepted on main and the amendment ships here. The product owner (rayrayxu) made this decision, and the First Principles lane is overridden on that basis.

  • One card. NewCrewmateDialog becomes the New crewmate card: the avatar, whose pencil opens the avatar editor (icon and colour only, with Back to 's original look to go back to the name's own face), Name under a visible label, and Create. There is no hint line under the name: the crewmate's first message says what happens next. Built from, What it looks after and the crew editor fields live under an inline Advanced settings fold in the same card. The "+" menu's one row, the empty roster's hero, the switcher, a crewmate's create link (/members?create=1&name=…&goal=…) and the crewmate.create guide all open it; the hero's Advanced link and the crew manager's door open it unfolded.
  • The crewmate asks first. The card's create sends first_greeting: true. POST /api/agents then records a goal welcome (members.mark_welcome_owed(..., kind="goal") in the existing welcome_owed.json). The existing POST /api/members/{slug}/greet dispatch in mate_welcome.py reads the kind (members.owed_welcome_kind) and runs goal_kickoff: a hidden turn in which the crewmate introduces itself by name and asks what it should work on, or confirms the job written under Advanced settings, and offers a schedule only once the goal is clear. The page asks for the greeting on dashboard-created rows as well as Mate's (useFirstGreeting).
  • Change cards ask first too. The crewmate.create change card's POST /api/agents step now sends "first_greeting": True (change_card_catalog.build_preview), so a card-made crewmate opens with the same goal welcome; the goal kickoff may set up an agreed schedule "or as a change card they confirm".
  • Guide. crewmate.create is now one commit step (the card's Create), completed only by the gateway from the crewmate it created, as before.
  • Removed. MeetCrewmatesFlow, useMeetCrewmatesGate and the first-run chapter mount; the created-crewmate receipts (sessionStorage); the seeded first-turn send, its retry notice and ChatPane's crewmateCreated slot; the "+" menu's Advanced row (members.add-menu.advanced); the theme's crewmates_onboarded reads, writes and localStorage mirrors (api/client/themes.ts, plus the greeting comment in api/client/agents.ts); i18n keys in i18n/locales/*.json and en.context.json (unused ones removed, the card's new ones added).
  • Fixed while porting. A create link followed from an open chat kept landing on Mate behind the card (main's never-chatted-Mate landing ran on the stripped /members URL). The create-link effect now keeps the open chat in the URL and the landing effect waits for it.
  • Docs. RFC § 02 amended; crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members.md and gui-user-test updated; UI index regenerated (npm run gen:ui).

The #17617 change-card hunks held back for #18448 are now included (it merged): change_card_catalog.py (DEFAULT_CREWMATE_TEMPLATE comment, first_greeting in build_preview), its test/test_change_cards.py assertion, the kickoff wording, and the crew-mode text. Not ported: website/scripts/verify-crewmate-assistant.mjs (not on main) and #17617's Captain-specific code (main's first crewmate is Mate).

Backwards compatibility

Compatible: POST /api/agents only gains an optional first_greeting flag (anything but true owes nothing); an existing welcome_owed.json with no kind still reads as Mate's welcome, and an unknown kind owes nothing; crewmates_onboarded is still accepted and returned by the theme endpoints.

  • Reader: website/src/shell/boot/firstRun.tsx:useFirstRunChapters -- crew page -- no longer mounts MeetCrewmatesFlow; first run ends after the Customize tour (App.importChapterReopen.test.tsx, App.lookPreviewFrame.test.tsx)
  • Reader: website/src/pages/members/MembersPage.tsx:openCreate -- crew page -- every door that opened the flow opens the card (MembersPage.test.tsx "MembersPage create links open the New crewmate card")
  • Reader: website/src/pages/members/MembersPage.tsx:CREATED_RECEIPTS_KEY -- crew page -- receipts are gone; a stale mc-members-created-receipts sessionStorage entry is never read again and dies with the tab
  • Reader: website/src/components/ChatPane.tsx:crewmateCreated -- crew page -- only MembersPage passed it; removed together (ChatPane.mateChat.test.tsx)
  • Reader: website/src/hooks/useTheme.tsx:markCrewmatesOnboarded -- crew page -- only the removed gate called it; GET /api/theme/boot still carries the flag and nothing on the dashboard reads it
  • Reader: website/playwright/auth.setup.ts:mc-crewmates-onboarded -- release (e2e) -- the chapter it suppressed no longer exists
  • Reader: src/kiro_crew/guide_catalog.py:ACTIONS["crewmate.create"].steps -- chat (guide) -- guides live in gateway memory only, so an upgrade restart drops any guide on the old three steps (test_guide_routes.py::test_crewmate_create_steps_match_the_page)
  • Reader: website/src/uiLocations/areas/members.ts:members.add-menu.advanced -- chat (find_ui / ui.show) -- the index no longer carries it; find_ui for "advanced crewmate setup" answers the "+" menu (test_find_ui_members.py)
  • Reader: src/kiro_crew/members.py:welcome_owed -- crew page -- kept, now owed_welcome_kind(...) is not None (test_mate_welcome.py)
  • Reader: website/scripts/capture-folder-indent-surfaces.mjs, website/scripts/lib/crew-pod-harness.mjs:meet-crewmates-not-now -- release (capture scripts) -- they dismiss the flow only when present, so they skip it

Tests

  • test/test_api_agents_create_template.py::TestFirstGreetingOwed: a first_greeting: true create records a goal welcome under its member id; None, False, "true" and 1 record nothing.
  • test/test_mate_welcome.py::TestGoalWelcome and the new route/dispatch cases: an owed crewmate greets once with the goal kickoff and no transcript row; a thread with messages or an unknown kind never greets; the kickoff names the crewmate (its key when unlabelled), never its template, and confirms a written goal.
  • test/test_change_cards.py::test_crewmate_create_binds_its_schedule_to_the_created_identity: the crewmate.create card's create step builds from kirocrew and carries first_greeting: True, and its schedule step runs as kirocrew. Removing the first_greeting line from build_preview turns this test red (KeyError: 'first_greeting').
  • test/test_guide_routes.py / test_guide_runs.py: crewmate.create is one commit step matching the page; the card's fields accept every pre-fill the catalog allows; the store's moves around a commit stay covered with a two-UI-step rig.
  • test/test_find_ui_members.py, test_slot_running_readers.py: the index and the reservation-reader list follow the change.
  • Website: NewCrewmateDialog.test.tsx and NewCrewmateDialog.guided.test.tsx (the card, its fold, drafts, guided Create), MembersPage.test.tsx (every door, create links keep the chat they came from, greeting asked for created crewmates), useFirstGreeting.test.tsx, rosterFilter.test.ts (hasNoCrewmates), GuideLayer.test.tsx (guide steps against the one-step action), CrewRoster.test.tsx (crew manager door opens unfolded).

Gates run locally on the head this PR carries (rebased onto b54fde7, which includes #18448): black, isort and flake8 on the touched Python files; tsc -p tsconfig.app.json and i18n:check pass; gen:ui regenerated. scripts/local-gate.py ran the related sets: frontend 738 files / 18,855 tests passed; backend 86 failures across its three batches (doctor/STT, design-tweak preview, file explorer, terminal probe, skill roots and similar), and every one of them also fails on a clean detached origin/main worktree in this sandbox, so none come from this diff. mypy src/kiro_crew reports 3 errors in wecom/client.py, a file this PR does not touch. The rebase conflicts were all two-sided additions (locale catalogs, crew-mode spec, feature map, ChatPane props) and kept both sides; the generated UI index was rebuilt.

Manual verification

Still required: on a running dashboard, create a crewmate from the "+" menu, the empty roster's hero and a crewmate's create link, and confirm the new chat opens with the crewmate introducing itself and asking what it should do (or confirming the written job). Not done yet: the greeting text is the model's own words and was only checked through the kickoff string in unit tests.

Screenshots / video

Before (this PR's base f07162523a, Crewmates preview on): New crewmate opens the four-step goal flow.

Desktop (1440×900):

Before: New crewmate on desktop

Phone (390×844):

Before: New crewmate on a phone

After: taken on a fresh pod built from head 72dd1d3d58 (Crewmates preview on).

Desktop (1440×900). The card: the avatar's pencil, the Name label, Create:

New crewmate card

The pencil opens the avatar editor, icon and colour only. Until a pick it previews the card's own face, nothing is framed and Apply is off; Back to Scribe's original look goes back to it after a pick:

Avatar editor, icon only

The card after Apply:

Card with the picked icon

With Advanced settings unfolded, down to the second Create at the end of the fields:

Advanced settings unfolded

A card prefilled from /members?create=1&name=Scribe&goal=…:

Prefilled card

The new crewmate's first message, a hello and its goal question:

First message

Created with a goal under Advanced settings, the first message repeats the goal back and asks to confirm it:

First message with a goal

Phone (390×844), same pod and head:

Mobile: New crewmate card

Mobile: avatar editor, icon only

Mobile: card with the picked icon

Mobile: first message

Related Issues

Part of #18300

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; see the Licensing section of CONTRIBUTING.md.

@buluoray
buluoray requested review from a team and KiroCrewCaptain as code owners October 10, 2026 09:12
@github-actions github-actions Bot added readiness: checking Automated validation is still running merge conflict Branch has merge conflicts with its base — author must resolve before merge labels Oct 10, 2026
@buluoray
buluoray force-pushed the feat/crewmate-one-card-create branch from 717dc98 to 7471249 Compare October 10, 2026 09:26
@github-actions

github-actions Bot commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

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

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 72dd1d3

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

@github-actions

github-actions Bot commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 72dd1d3d587ce7ddd2f25994d84c4f7c6d034a08 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Check that a crewmate created with a failed welcome_owed.json write still gives the user a visible next step, since its chat now opens empty with no prompt.

[DESIGN-REVIEWED] 72dd1d3

Description read

[DESCRIPTION-READ] cc706fb0e3ef5e597960f25f8f4e4bb6cda71c55b2cd4da74ec93b2420f6e542

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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — 🟡 CONCERNS

UX-level review of 72dd1d3d587ce7ddd2f25994d84c4f7c6d034a08 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

UX-Verdict: CONCERNS

Choosing a pose wipes the crewmate's own face, so Scribe and Radar end up as the same plain green ghost, and shot 4 doesn't match the shipped code.

Watch

  • Picking an icon removes the face the name came with. The icon-only editor offers only plain poses. Once you pick one and press Apply, the glasses and heart are gone. The blind reader said Scribe in shot 5 "no longer looks like 'Scribe'", and Radar in shot 12 "looks exactly like the green one Scribe got". In the chats, "the only thing that tells them apart is the name in the greeting." This hits everyone who opens the pencil on the main create path, and it stays until they find the revert link. Fix: keep the name's own face as the first, selected tile in the pose grid.
  • Shot 4 is stale. It shows "Use Scribe's own face" while Apply is still disabled. In the code the label is "Back to {{name}}'s original look", and it only appears when iconOnly && value !== null, so it can't show in that state. Its "nothing selected" grid ("I can't tell which one is 'current'") is therefore unverified at HEAD. Fix: re-capture shot 4 from HEAD.
  • "Goal" and "What it looks after" read as one thing under two names. The chat greeting says "What should my goal be", while the Advanced fold labels the same field "What it looks after". The blind reader flagged it: "They seem to be the same thing." Fix: call the field "Goal (optional)".

Suggestions

  • Advanced settings: "Model: Inherited" was "no idea → no". Show what it inherits, e.g. "Inherited (auto)".

[UX-REVIEWED] 72dd1d3

Description read

[DESCRIPTION-READ] 260c9872a1975ba7d27a0b0384fe53b82567590690bfc8f940be92a10bb7d1ae

That sha256 names everything this verdict read: the PR description, plus the 16 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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ human override accepted

@buluoray overrode this lane for 72dd1d3d587ce7ddd2f25994d84c4f7c6d034a08 via /ai-review override (this commit only).

@github-actions

github-actions Bot commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

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

Review details

No findings.

[OPUS-REVIEWED] 72dd1d3

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

False positive or not applicable? A repository writer can comment:
/ai-review override fable 72dd1d3d587ce7ddd2f25994d84c4f7c6d034a08: <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 merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Oct 10, 2026
@buluoray
buluoray force-pushed the feat/crewmate-one-card-create branch from 7471249 to 7aa7b10 Compare October 11, 2026 07:18
@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 merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Oct 11, 2026
@buluoray
buluoray force-pushed the feat/crewmate-one-card-create branch from 7aa7b10 to 95509ca Compare October 11, 2026 08:45
@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 merge conflict Branch has merge conflicts with its base — author must resolve before merge labels Oct 11, 2026
@buluoray

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 95509ca: agent: owner decision -- the one-card create replaces the guided create and the RFC is amended in this PR; restoring the change card's first_greeting was the owner's explicit request after #18448 merged.

@buluoray

Copy link
Copy Markdown
Contributor Author

/ai-review override ux 95509ca: agent: owner decision -- the BLOCK is only for missing captures (the Advanced fold's lower half and the no-job greeting); the four attached screenshots cover the card, the fold, a prefilled card and a first greeting.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@buluoray marked the first-principles AI finding as false positive, not applicable, or explicitly accepted for 95509caf01e85a2c22b28f63d649a94a0b763baf.

agent: owner decision -- the one-card create replaces the guided create and the RFC is amended in this PR; restoring the change card's first_greeting was the owner's explicit request after #18448 merged.

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

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@buluoray marked the ux AI finding as false positive, not applicable, or explicitly accepted for 95509caf01e85a2c22b28f63d649a94a0b763baf.

agent: owner decision -- the BLOCK is only for missing captures (the Advanced fold's lower half and the no-job greeting); the four attached screenshots cover the card, the fold, a prefilled card and a first greeting.

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

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@buluoray marked the first-principles AI finding as false positive, not applicable, or explicitly accepted for 1c347c1784318bd61602fb1c82cd94ff8d350583.

Ray (rayrayxu), the product owner, decided the one-card create replaces § 08's four-step flow and moves Built from and What it looks after under Advanced; the § 02 amendment records it. The first_greeting on change-card creates was added back at his explicit request after #18448 merged.

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

@buluoray

Copy link
Copy Markdown
Contributor Author

/ai-review override ux 1c347c1: screenshot evidence only; Ray (rayrayxu) decided not to re-capture the editor shots after the relabel. A unit test pins the shipped link: absent before an applied pick, labelled "Back to 's original look" after one, and it restores the original face.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@buluoray marked the ux AI finding as false positive, not applicable, or explicitly accepted for 1c347c1784318bd61602fb1c82cd94ff8d350583.

screenshot evidence only; Ray (rayrayxu) decided not to re-capture the editor shots after the relabel. A unit test pins the shipped link: absent before an applied pick, labelled "Back to 's original look" after one, and it restores the original face.

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

@buluoray

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 8191852: Ray (rayrayxu), the product owner, decided the one-card create replaces § 08's four-step flow and moves Built from and What it looks after under Advanced; the § 02 amendment records it. The first_greeting on change-card creates was added back at his explicit request after #18448 merged.

@buluoray

Copy link
Copy Markdown
Contributor Author

/ai-review override ux 8191852: screenshot evidence only; Ray (rayrayxu) decided not to re-capture the editor shots after the relabel. A unit test pins the shipped link: absent before an applied pick, labelled "Back to 's original look" after one, and it restores the original face.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@buluoray marked the first-principles AI finding as false positive, not applicable, or explicitly accepted for 8191852d44b35a595dc8c300777a2edd10550972.

Ray (rayrayxu), the product owner, decided the one-card create replaces § 08's four-step flow and moves Built from and What it looks after under Advanced; the § 02 amendment records it. The first_greeting on change-card creates was added back at his explicit request after #18448 merged.

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

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@buluoray marked the ux AI finding as false positive, not applicable, or explicitly accepted for 8191852d44b35a595dc8c300777a2edd10550972.

screenshot evidence only; Ray (rayrayxu) decided not to re-capture the editor shots after the relabel. A unit test pins the shipped link: absent before an applied pick, labelled "Back to 's original look" after one, and it restores the original face.

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

@buluoray

Copy link
Copy Markdown
Contributor Author
  • The editor's reset link as it ships: owner decision.

Ray (rayrayxu) chose not to re-capture the editor shots after the relabel. A unit test pins the shipped link: absent before an applied pick, labelled "Back to 's original look" after one, and it restores the original face.

@buluoray

Copy link
Copy Markdown
Contributor Author
  • The untouched editor as it ships: owner decision.

Same decision as the reset link: no re-capture. Before a pick the footer has no link, which the same unit test asserts.

@buluoray

Copy link
Copy Markdown
Contributor Author
  • Two "Create crewmate" buttons in one card: accepted as is.

Both run the same create, which is why they share a label. The second sits at the end of the unfolded Advanced fields so a person who scrolled through them does not scroll back up to finish.

@buluoray

Copy link
Copy Markdown
Contributor Author

The accepted goals RFC (#19488) relabels the Advanced field Goal and makes it write the long-term goal; that change ships with the goal record in #19539, so this PR leaves the shared "What it looks after" field as it is.

@buluoray

Copy link
Copy Markdown
Contributor Author
  • Create was read only as "a guess": rebutted.

Shots 01-02 already sit under the description's Before label ("this PR's base ... New crewmate opens the four-step goal flow"), shown for comparison with the card that replaces it.

@buluoray

Copy link
Copy Markdown
Contributor Author
  • A failed create the user left is never reported: fixed in 711a075.

The card now reports every failure to the page (onFailed), and when the user had left the busy card the page shows that failure inline in the card's own words, keeping the chat they chose. Covered by a create that fails after the user left it says so on the page, keeps the chosen chat, and the notice dismisses, which fails without the wiring.

Port of #17617 onto main. The Crewmates page creates a crewmate on one
New crewmate card (Name, Avatar with Try another look, Create), with
everything else under an inline Advanced settings fold, instead of the
guided Meet CrewMates flow. The "+" menu, the empty roster's hero, the
switcher, a crewmate's create link and the crewmate.create guide all
open that card; the guide's crewmate.create action is one commit step.

The card's create sends first_greeting. POST /api/agents then records a
goal welcome (welcome_owed.json, kind "goal"), and the existing
POST /api/members/{slug}/greet dispatch in mate_welcome.py runs a hidden
goal kickoff: the crewmate introduces itself and asks what it should do,
or confirms the job written under Advanced settings. The page asks for
the greeting on dashboard-created rows as well as Mate's.

Removed: MeetCrewmatesFlow, useMeetCrewmatesGate, the first-run chapter
mount, the created-crewmate receipts, the seeded first-turn send and its
retry notice, and the theme's crewmates_onboarded reads and writes (the
gateway keeps carrying the flag for compatibility).

Docs: RFC crewmates-launch section 02 amended (08 marked superseded),
crew-mode, config, feature map, mcp, learn-cron-dashboard, crew-members
and gui-user-test updated; UI index regenerated.

Part of #18300
The New crewmate card drops the random re-roll. Its avatar tile now
opens CrewAvatarBuilder in an icon-only mode (pose and colour), and a
pick survives a renamed draft; with no pick the record keeps the name's
own face. The Name field gets a visible label, and the first greeting
is a short hello with the crewmate's name followed by one plain
question about its goal.
@buluoray

Copy link
Copy Markdown
Contributor Author

/ai-review override first-principles 72dd1d3: Ray (rayrayxu), the product owner, decided the one-card create replaces § 08's four-step flow and moves Built from and What it looks after under Advanced; the § 02 amendment records it. The first_greeting on change-card creates was added back at his explicit request after #18448 merged.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@buluoray marked the first-principles AI finding as false positive, not applicable, or explicitly accepted for 72dd1d3d587ce7ddd2f25994d84c4f7c6d034a08.

Ray (rayrayxu), the product owner, decided the one-card create replaces § 08's four-step flow and moves Built from and What it looks after under Advanced; the § 02 amendment records it. The first_greeting on change-card creates was added back at his explicit request after #18448 merged.

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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants