Skip to content

feat(shared-crew): fix the teammate experience for a shared Crew - #38803

Merged
KiroCrewCaptain merged 1 commit into
mainfrom
fix/shared-crew-teammate-ux
Nov 18, 2026
Merged

KiroCrewCaptain merged 1 commit into
mainfrom
fix/shared-crew-teammate-ux

Conversation

@bolichen97

@bolichen97 bolichen97 commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: A teammate on a Shared Crew can tell their own messages from other people's, filter sessions by who started them in the existing Sort & filter menu, sees who they are signed in as, never sees the host owner's sandbox runbook, and can sign in to Kiro on a fresh Linux install without getting stuck; and the Remote Crew page, the People page and the header switcher follow the layout in #38790.

Replaces #38314, reopened under the author's own account. Scope follows the Crew for Teams re:Invent Bug Bash doc and the rulings since: the in-window pane moved to #38293, owner-only locks / host wording / the first People page moved to #38437. #38790's Remote Crew, People and switcher layout is built here on top of #38437's code.

The Linux E2E run (an Amazon Linux host, two teammates on separate desktop apps over the Kiro relay, one fresh-HOME install) showed:

Why it matters

This is the re:Invent demo path: every teammate who opens a Shared Crew hits these screens in the first minute, and each one reads as broken or as someone else's machine.

Not a goal

What changed (motivation → approach → change)

A teammate sees whose message is whose, filters by who started a session, sees who they are, never reads the host's sandbox runbook, and gets through a fresh sign-in; the Remote Crew page, People and the switcher follow #38790.

Change What the reader gets Where
Whose message (#38458, rows 15/20) Only the viewer's own messages sit on the end side; a teammate's sit on the start side with their name (logical sides, so RTL mirrors). A queued send's queue_pop and a steer's row, steer_push and requeue carry the author, so steered and queued rows are named live and on reload. UserMessage.tsx, ChatMessageList.tsx, chat_turn/queue_drain.py, chat_delivery.py, chat_send.py, websocket/chatStream.ts
Started by (#38703) A section of Sort & filter (You, each person, Unattributed, with counts, multi-select), filtered on the client like the other dimensions, with a chip saying how many match and how many it hides. The separate creator bar and its server-filtered list are gone. Hidden on a personal Crew. rows.ts, creatorFilterMenu.tsx, creators.ts, switchSlotCallsiteClassification.test.ts
Who you are, Shared Crew copy (item 6, row 10) The mode body adds viewer_via and owner_label; the sidebar shows " via Kiro Login" and a Shared count. The owner is named by one owner.owner_name() (Kiro e-mail, else Tailscale name, else host name). "Shared Crew(s)" in all 12 locales. SidebarIdentityRow.tsx, shared_crew/owner.py, sharedCrewMode.ts, hooks/sharedCrew/, i18n/locales, en.context.json
Host cannot start chats (item 4) A missing sandbox backend or a launcher that fails at start is typed host_sandbox_unavailable on every row path. A non-owner reads one plain line with Copy details on the WebSocket, SSE and every buffered HTTP body (gzipped and JSON lines included); the owner keeps the diagnostic. A row an older build stored untyped (a no-backend refusal, a launcher failure behind its lead, a background-start stop notice of either) is matched by its raiser's fixed wording. Session search and the session-list preview never quote such a row; exports carry no error rows. host_sandbox_refusal.py, redaction_audience.py, eager_spawn.py, turn_failures.py, acp_vocab.py, history_search.py, history_projection_reads.py, chatErrorRecovery.ts, HostSandboxUnavailableCard.tsx
Fresh-install sign-in (L1-L5) KAS's SignInRequiredError is tagged auth_required, so the card offers Sign in. A sign-in refreshes the top bar's reading and the Shared Crews list at once; a usage or status read still in flight is cancelled first, so it cannot put the previous account's answer back. A GetUsageLimits AUTH_REJECTED is a failed balance read, not signin_required. The device-code screen has labelled Copy link and Copy code. The switcher's Kiro-account group has Connect, which opens the Crew in its own window and never connects on its own. transport_errors.py, useKasLogin.ts, KasLoginGate.tsx
Remote Crew page (#38790 items 1-5) "My Crews" and "Shared with me" sections; one "+ Add Crew" modal ("Set up a new Crew", "Connect a machine you have"); a launch in progress is a "Setting up" row. A row shows one blocking tag and one main action; its chevron opens details and Diagnose / Edit settings / Remove in place of the ⋯ menu. Settings > Advanced is not routed since #38312, so the unchanged "Turn off Remote Control" card sits at the page's foot. RemoteCrewPanel*.tsx, SettingsPage.tsx, launch_job.py
People (#38790 items 6-7) GET /api/shared-crew/mode returns sources (Tailscale, AWS SSM, organization, Kiro Login) with state and people count. One card per source with its own invite button; a source not set up is a dashed card with its setup link; organization is read-only. One People list follows, a source chip per row, a distinct-people count, Remove only where it works. A teammate's invite buttons stay locked. crew_mode.sources_view, PeopleSources.tsx, PeopleCrew.tsx, sharedCrewUi.ts
Switcher (#38790 item 8) Heading "Remote Crews"; "Private" with a lock and "Shared" with a group icon, read the same wherever the strings recur. The open-in-new-window arrow is byte-identical to main. TeamCrewsGroup.tsx

Specs: shared-crew.md, instances.md, cloud.md, history.md, kas-auth.md, acp-client.md, learn-cron-dashboard.md, feature map. Every locale and the generated en-XA carry the new strings (settingsGluedFragments.test.ts pins the joined ones).

Backwards compatibility

Compatible: every new response and frame field (viewer_via, owner_label, sources on the mode body, author on queue_pop / steer_push) is additive and optional on the client; no route accepts or refuses anything it did not before.

Reader: website/src/pages/chat-sidebar/CreatorFilter.tsx:CreatorFilteredSessions -- crew page -- removed with the bar; the sidebar's own lanes now filter by creator (ChatSidebar.creatorFilter.test.tsx)
Reader: src/kiro_crew/shared_crew/routes_identity.py:GET /api/shared-crew/sessions -- crew page -- the route stays; the sidebar no longer calls it (api.sharedCrewSessions kept, ApiClient.refactor.surface.test.ts)

Tests

  • test_shared_crew_steer_author.py: a teammate's steer row, steer_push and requeue carry the author; an author-less steer keeps its old shape.
  • test_shared_crew_queue_pop_author.py: a teammate's queued send drains with a queue_pop naming them.
  • test_host_sandbox_refusal.py: typed row; owner vs teammate on WS, SSE, JSON, gzipped and JSON-lines bodies.
  • test_shared_crew_owner.py, test_shared_crew_mode_viewer_fields.py: the owner_name order and the viewer fields.
  • test_usage_crew_vault.py, test_acp_refactor_error_surface.py: L1/L2.
  • test_host_sandbox_refusal.py also: a stored untyped setgroups row on JSON, JSON lines and the socket; each untyped legacy shape (bare no-backend row, Error:-led launcher failure, background-start stop notice of either) read by a teammate as the plain line with no notice_args, and by the owner as stored; no search excerpt or session-list preview of a refusal row. The four teammate shapes fail on the unfixed module (12 of 20 new cases red, every owner case green).
  • test_shared_crew_mode_sources.py: sources lists every path at once with its state and people count.
  • Website: RemoteCrewPanel.layout.test.tsx (sections, Add Crew modal, Setting up row, one main action per state, chevron details), PeoplePanel.test.tsx (source cards, per-source invite, teammate lock, chips, distinct count, Remove placement), TeamCrewsGroup.test.tsx (heading, Private/Shared icons, arrow kept, no pin), MessageByline.runs.test.tsx (sides per viewer, a teammate's steer named), ChatMessageList.userSide.test.tsx, UseWebSocketCoverage.test.tsx (steer echo author), CreatorFilter.test.tsx, rows.test.ts, ChatSidebar.creatorFilter.test.tsx, TeamCrewsGroup.test.tsx, SidebarIdentityRow.test.tsx, ErrorCard.hostSandbox.test.tsx, KasLoginGate.test.tsx, KiroSignInCard.test.tsx (a usage poll or status refetch in flight when the sign-in lands does not overwrite the new answer; both red without the cancel, green with it, 5 shuffled seeds).

Proof: not provable -- frontend test

Manual verification

Every kept item was reproduced on real boxes (AL2023 host at origin/main, teammate viewers A and B over the Kiro relay), then rerun with the host and viewer A on this branch, plus a fresh-HOME sign-in on viewer C and the owner's own view in a browser on the host. All FIXED: #38703, rows 10/15/20, items 4 and 6, L1-L5, and Connect. #38790 items 1-8: see the shots below. Row 20's literal "first message" case did not reproduce on main (B's first message was named); the nameless rows were the steered and queued ones, now named. Viewer B's own Local app stayed on Nightly; everything B used here is served by the host build.

Screenshots / video

Teammate view, Linux desktop app (e-mails blurred). BEFORE on main: a teammate's message and steer on the right, no name on the steer, the separate "All sessions" bar.

BEFORE on main: teammate messages on the right, nameless steer, separate creator bar

AFTER: the teammate's messages on the left with their name, steer included; the viewer's own on the right.

AFTER: teammate on the left with name, steer named, own message on the right

AFTER: Started by chip under the search box with matching and hidden counts

AFTER, owner on the host: Started by in Sort & filter with You, each person, Unattributed and counts

AFTER: switcher says Shared, From your Kiro account with Connect

AFTER: host cannot start the chat, one plain line with Copy details and Resume, no runbook

Related Issues

Closes #38703
Closes #38458
Closes #38790

Replaces #38314. Related: #38293 (pane, merged), #38437 (owner locks, host wording, People), #38304 (Kiro account tab), #37523 (added-to-a-Shared-Crew notice).

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.

@github-actions

github-actions Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ human override accepted

@bolichen97 overrode this lane for 6fd3b2ef696bf091d02f49827e655f6c6413610f via /ai-review override (this commit only).

@github-actions

github-actions Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ human override accepted

@bolichen97 overrode this lane for 6fd3b2ef696bf091d02f49827e655f6c6413610f via /ai-review override (this commit only).

@github-actions

github-actions Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 6fd3b2ef696bf091d02f49827e655f6c6413610f — 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

Nothing blocks: each item traces to a Bug Bash row or a linked issue. The creator-filter replacement leaves the old server-filtered list path with no caller.

Notes

  • Item 2 — rides along: "The separate creator bar and its server-filtered list are gone" removes the only caller of api.sharedCrewSessions. Grepping sharedCrewSessions and shared-crew/sessions across website/src and src/kiro_crew (tests excluded) finds 0 callers outside the definition at website/src/api/client/sharedCrew.ts:48. Subtraction: delete that client method and its SharedCrewSessionPage/SharedCrewSessionQuery types, and delete api_shared_crew_sessions (registered at routes_identity.py:278 and dashboard/routes/shared_crew.py:50) unless something outside this repo reads it.
  • Items 6–8 — unjustified move: removing the Remote Crew tabs and the ⋯ menu, regrouping People, and relabelling the switcher rest on issue Remote Crew, People and the Crew switcher: organize Crews, connection sources and people into clear sections #38790, not on a base RFC. rfc-remote-crew-sidebar (partial) covers the chat sidebar, not these pages. Whether this counts as product shape is a judgement call, so it stays a note.

What this change ships

Inventory (10 items) — 8 justified

Intent: let a teammate on a Shared Crew tell whose message is whose, filter by creator, see who they are, avoid the owner's sandbox runbook, and sign in on a fresh Linux install. FIX, with an #38790 layout ADDITION bundled in.

  1. A teammate's messages now sit on the start side with their name, including steered and queued rows — justified
  2. Creator filter moved from its own bar into Sort & filter, filtered on the client; leaves the server list path without a caller — rides along
  3. Sidebar shows " via Kiro Login" and a Shared count — justified
  4. Owner is labelled by Kiro e-mail, then Tailscale name, then host name, instead of machine name — justified
  5. A non-owner sees one plain host-sandbox line instead of the owner's runbook, on every path — justified
  6. Remote Crew page: two sections, one "+ Add Crew" modal, chevron details instead of ⋯ menu and tabs — unjustified move
  7. People page: one card per source, one combined list (sources on the mode body) — unjustified move
  8. Switcher heading "Remote Crews", "Private"/"Shared" labels, "Shared Crew(s)" replaces "Team Crews" — unjustified move
  9. Fresh sign-in: auth_required tagging, immediate refresh of the top bar and Shared Crews, AUTH_REJECTED read as a failed balance read — justified
  10. Device-code screen gets labelled Copy link and Copy code; Kiro-account group gets Connect — justified

The change has more than 10 items; these are the 10 most visible.

[FIRST-PRINCIPLES-REVIEWED] 6fd3b2e

Description read

[DESCRIPTION-READ] 2aafc53e3021c0ac6b41e29d4929f8eb08206566b06e82fa8867b954154d889e

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 Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

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

Review details

No findings.

[OPUS-REVIEWED] 6fd3b2e

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

False positive or not applicable? A repository writer can comment:
/ai-review override fable 6fd3b2ef696bf091d02f49827e655f6c6413610f false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

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

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 6fd3b2e

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 6fd3b2ef696bf091d02f49827e655f6c6413610f false-positive: <reason, 20 to 500 characters>

@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 17, 2026
@KiroCrewCaptain
KiroCrewCaptain force-pushed the fix/shared-crew-teammate-ux branch from b9da410 to 25ef673 Compare November 17, 2026 23:49
@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 merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Nov 17, 2026
@KiroCrewCaptain
KiroCrewCaptain force-pushed the fix/shared-crew-teammate-ux branch from 25ef673 to d134a64 Compare November 18, 2026 01:22
@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 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 labels Nov 18, 2026
@KiroCrewCaptain
KiroCrewCaptain force-pushed the fix/shared-crew-teammate-ux branch from d134a64 to 137db76 Compare November 18, 2026 03:09
@bolichen97

Copy link
Copy Markdown
Contributor Author

Bolin asked for #38790's scope (the Remote Crew page, the People page and the header switcher layout) to be built into this PR, on top of #38437's People and RemoteCrew code. The Goal line, "Not a goal" and "Related Issues" (now Closes #38790) were edited for that, at his request. Item 5's move to Settings > Advanced is not possible since #38312 hid that page, so the Remote Control card sits at the foot of Remote Crew instead.

@github-actions github-actions Bot removed the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 18, 2026
@KiroCrewCaptain
KiroCrewCaptain force-pushed the fix/shared-crew-teammate-ux branch from 137db76 to b290b50 Compare November 18, 2026 03:36
@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 Nov 18, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

/ai-review override ux 2c7ff44 owner-decision: the diff is over the lane's 1 MB cap because Bolin asked for #38790 to land in this PR (#38803 (comment)), so the lane cannot run; real-machine before/after proof is in the PR and after-shots. Failed run: https://github.com/kirodotdev/KiroCrew/actions/runs/44340285983

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@bolichen97 recorded a owner-decision release (class owner-decision) for the design AI finding on 2c7ff44bdd20b8e6f389761d0d1691c1f6cc3416.

the diff is over the lane's 1 MB cap because Bolin asked for #38790 to land in this PR (#38803 (comment)), so the lane cannot run; real-machine before/after proof is in the PR and after-shots. Failed run: https://github.com/kirodotdev/KiroCrew/actions/runs/44340286328

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

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@bolichen97 recorded a owner-decision release (class owner-decision) for the ux AI finding on 2c7ff44bdd20b8e6f389761d0d1691c1f6cc3416.

the diff is over the lane's 1 MB cap because Bolin asked for #38790 to land in this PR (#38803 (comment)), so the lane cannot run; real-machine before/after proof is in the PR and after-shots. Failed run: https://github.com/kirodotdev/KiroCrew/actions/runs/44340285983

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

@github-actions github-actions Bot removed the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 18, 2026
A teammate on a Shared Crew saw the host owner's runbook when the host
could not start chats, controls that only refused them, no name for whom
to ask, People that said "Tailscale: Not set up" on a Crew shared over
Kiro, and a Team Crew that opened in a separate window and could land on
the relay's bare 403 page.

- Desktop: a Team Crew opens in the main window as a pane with a top-bar
  chip and the Cmd/Ctrl+digit chord; older desktops keep the window path.
  A main-frame 401/403 mints once more, then shows a notice instead of
  the bare page, and the owner turning off access has its own notice.
- Host cannot start chats: the error row gets the typed code
  host_sandbox_unavailable; a non-owner audience gets one plain line and
  Copy details, never host paths or config keys, and no Resume that
  replays the same refusal.
- Owner-only areas (secrets, phone, sign-in links, webhooks, remote
  Crews, channel connection writes, cron secret grants, invites, the
  preview switch, admission keys, redaction, reveal) show one lock that
  names the person at the host machine, driven by /api/auth/me teammate
  and an owner_only 403, pinned to the backend table by a test.
- Sidebar identity row ("<name> via Kiro Login") and a read-only Shared
  state under the one showsTeamAttribution rule; People grouped by path
  from each row's provenance, with an owner row for a teammate.
- Copy: name the Crew's computer instead of "your device" in Security and
  About, plain Computer Use and Voice host copy, a retired stale
  session-not-found banner, and a full-path tooltip in Task Runner.
@bolichen97
bolichen97 force-pushed the fix/shared-crew-teammate-ux branch from 2c7ff44 to 6fd3b2e Compare November 18, 2026 16:31
@bolichen97

Copy link
Copy Markdown
Contributor Author
  • span=521e9d0052da: An in-flight usage poll can overwrite the successful sign-in refresh

fixed in 6fd3b2e: invalidateSignInCaches awaits cancelQueries(['kiro-usage']) before it clears the reading and again before it publishes the refresh POST's result, so neither a GET in flight at sign-in nor one sent during the refresh can land after it.
Class: a direct write to a key a poll also fetches. The cancel path's status write (setQueryData(KAS_LOGIN_STATUS_KEY, fresh)) cancels the in-flight status refetch first too; KiroAccountModal's write is followed by invalidateQueries, whose default cancelRefetch already cancels.
Tests: KiroSignInCard.test.tsx, a usage poll and a status refetch held open across the sign-in; both red without the cancel, green with it.

@bolichen97

Copy link
Copy Markdown
Contributor Author
  • span=288e8de5022b: the session-list preview quotes the host's sandbox diagnostic to a non-owner

fixed in 6fd3b2e: TranscriptReadProjection._tail_walk skips a host-sandbox refusal row (is_refusal_row, typed or untyped), the same skip history_search._searchable_contents makes, so GET /api/sessions?preview=1 previews the message before it for every reader.
Class: text derived from the row as a bare string. Every preview read (last_message_preview / last_message_info, the crew reads that copy row["preview"]) goes through that walk; the speech-only walk and slot_row_memo read user and assistant rows only.
Test: test_host_sandbox_refusal.py::test_the_session_list_preview_never_quotes_a_refusal_row, typed and untyped; both red without the skip.

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

Copy link
Copy Markdown
Contributor Author

/ai-review override design 6fd3b2e owner-decision: the diff is over the lane's 1 MB cap because Bolin asked for #38790 to land in this PR (#38803 (comment)), so the lane cannot run; real-machine before/after proof is in the PR and after-shots. Failed run: https://github.com/kirodotdev/KiroCrew/actions/runs/44348315452

@bolichen97

Copy link
Copy Markdown
Contributor Author

/ai-review override ux 6fd3b2e owner-decision: the diff is over the lane's 1 MB cap because Bolin asked for #38790 to land in this PR (#38803 (comment)), so the lane cannot run; real-machine before/after proof is in the PR and after-shots. Failed run: https://github.com/kirodotdev/KiroCrew/actions/runs/44348315085

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@bolichen97 recorded a owner-decision release (class owner-decision) for the design AI finding on 6fd3b2ef696bf091d02f49827e655f6c6413610f.

the diff is over the lane's 1 MB cap because Bolin asked for #38790 to land in this PR (#38803 (comment)), so the lane cannot run; real-machine before/after proof is in the PR and after-shots. Failed run: https://github.com/kirodotdev/KiroCrew/actions/runs/44348315452

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

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@bolichen97 recorded a owner-decision release (class owner-decision) for the ux AI finding on 6fd3b2ef696bf091d02f49827e655f6c6413610f.

the diff is over the lane's 1 MB cap because Bolin asked for #38790 to land in this PR (#38803 (comment)), so the lane cannot run; real-machine before/after proof is in the PR and after-shots. Failed run: https://github.com/kirodotdev/KiroCrew/actions/runs/44348315085

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

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention labels Nov 18, 2026

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I reviewed head 6fd3b2e against the earlier approved head, focusing on the two rebases, the legacy refusal redaction and the sign-in refresh fix. Both sides of every conflict survive: the refused-credential wording and the 'Error:' lead from main, the plugin-missing steps now living in the setup cards, and the new sign-in props on the error card. A refusal row stored by an older build is now recognized by either raiser's fixed wording wherever it sits in the row, including the background-start stop notice. A teammate gets the plain line on history reads, socket frames, chat events, the status stream and JSON bodies, while the owner reads the row unchanged. Search and the session-list preview never quote such a row, and cancelling the in-flight queries keeps a stale poll from overwriting the fresh sign-in reading. The related backend tests pass, removing either fix makes the new tests fail, and I found no blocking defect.

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

Labels

None yet

Projects

None yet

2 participants