Repository navigation
Conversation
Design Review (Fable 5) — 🟡 CONCERNSDesign-level review of Design-Verdict: CONCERNS Sound, well-decomposed design; one contract crack — the card asserts "Default applied" for a default the system deliberately never runs or verifies. Watch
Suggestions
[DESIGN-REVIEWED] 45b7ea7 |
GPT 5.6 Review — 🔴 changes requested (blocking)GPT 5.6 found at least one blocking issue that must be resolved before merging This comment is updated in place on each push. BLOCKING -- src/kiro_crew/dashboard/session_control.py:2414 -- successful escalations can be lost on restart
FINDING -- src/kiro_crew/dashboard/session_control.py:2290 -- [BLOCK-MERGE] f2ba19c Adjudication (Opus 4.8) — is blocking on each finding proportionate?The adjudicable block is empty. F1 is fenced (data-loss / unbounded-harm class): a crash in the window between The required window is an ordinary crash between append and async flush — not mutually-contradicting timing, not inputs the writer cannot produce. The recovery path is deletion, not reconstruction: the content is unrecoverable. I cannot state a rarity argument that a human would plausibly accept the residual risk, so the FLAG evidence bar is not met. When torn, UPHOLD-FENCED. False positive or not applicable? A repository writer can comment: |
First Principles Review (Fable 5) — 🟡 CONCERNSPremise-level review of All evidence gathered. Counts verified: First-Principles-Verdict: CONCERNS The conversation index ships future-proof fields nobody reads, and much of the new backend keeps a store its own spec calls a re-derivable projection. Not justified as shipped
What this change shipsIntent: let an unattended crew member raise a non-blocking decision to its human and keep working — an ADDITION. (More than 10 items; the 10 most visible kept.)
Watch
Subtractions
[FIRST-PRINCIPLES-REVIEWED] 45b7ea7 |
Opus 4.8 Review — ✅ no blocking findingsReviewed Review detailsThe candidate's mechanics check out (503 raised by No other grounded defect surfaced in the changed lines. No findings. [OPUS-REVIEWED] 45b7ea7 Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
3be88bd to
0675595
Compare
916eda8 to
2e8d603
Compare
0675595 to
1d1628e
Compare
2e8d603 to
7e122ff
Compare
1d1628e to
032d9e7
Compare
7e122ff to
c7e3957
Compare
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
@CrysisDeu I audited every open PR for relationships, and this one (audited at ee56ec6; the head has since moved to 62d4d98) overlaps textually with your own #8947. The overlap is four files: Nothing semantic collides. Escalation cards and the needs-you badge are independent of selection Quote / Ask, and both props can coexist on the mount line. This is a rebase-order question, not a design one. Suggested order: land this PR first, then rebase #8947 onto it. This PR's merge base is main's tip (12ecd45), while #8947 is 128 commits behind and already conflict-dirty, so it absorbs the Posted from the 2026-09-08 open-PR relationship audit (read-only, one auditor per PR); reply here if any of this is wrong. |
…ate) A crew member that hits a wall -- a permission it lacks, something only a person can reach, a one-way door -- gets its own verb to raise it to the human: `session_escalate(message, deadline?, default_action?, options?, goal?)`. It never starts a turn: it lands one `escalation` row in the DM thread of the member that owns the caller (a worker's creating member; a plain session's own transcript), mirrors it onto the bell bus with a per-goal group_key, and returns while the caller keeps working. Its own tool, not a reserved `target` of `session_send` (review): a send delivers text the target RUNS as a turn, an escalation writes a row and runs nothing, and a shared name made their policy inseparable. Each policy site now classifies the verb on its own: in SESSION_CONTROL_TOOLS (caller identity), in CHANNEL_AGENT_BLOCKED_TOOLS (on send_notification's grounds -- the bell mirror -- with the backend's linked/mirrored-caller gate agreeing), granted to members (writes only into their own thread), mounted-but-gated for the conductors, own schema in MCP_DASHBOARD_SCHEMAS. `session_send` is back to `target` + `message`; an escalation field on it is refused as unknown, never dropped. The per-member conversation index (crew_conversation.py, #8612) rides here with its consumer: pending records written before the card under a pre-minted row id, `needs_you` derived and projected on the slots frame and the roster, replies matched by `meta.escalation_id` or, for typed text, by exactly-one-pending at the row's position, restore-time reconciliation against the transcript. `options` is the card's contract (#8614 renders it); until then the row is a plain line and the options are readable in the bell mirror, not clickable -- the tool description promises exactly that. An `escalation` row ends the follow-up pill scan so a previous turn's `[OPTIONS:]` chips can never post as the escalation's answer. --- Frontend (folded in from #8614) --- feat(members): chat-profile projection and escalation cards in the DM thread The Crew Members DM thread rendered the member's raw transcript: every tool row, notice and nudge between the human's message and the member's reply. That is the right view on the Sessions page and the wrong one for a conversation. This gives ChatPane a `displayProfile` — `transcript` (default, unchanged) or `chat` — and mounts the chat profile on the Members page. The chat profile is a projection over the same rows (pages/members/ chatProjection.ts), computed client-side so the view can never disagree with the transcript it is drawn from: * human messages, the FINAL assistant reply of each turn, escalation cards, approval and error rows stay; tool / thinking / notice / nudge / inject / subagent rows are hidden and attached to the reply as `meta.chat_process`, reachable through a "View process (N steps)" expander; * while the member runs a turn, a "Working: <tool purpose>" line stands in for the hidden rows (WS tool_call -> slotStatusDetail; falls back to the tool name, then a generic line); * consecutive auto-nudge rounds whose reply said nothing new fold into one "N check-ins with nothing new" row with its own expander. (Implemented and unit-tested; a member thread cannot host an auto-nudge loop today because autonudge_authz refuses member-mode slots, so this ships dark until that guard is revisited.) Escalation rows (role `escalation`, from session_send target=user) render as a card: title, sender, goal chip, markdown body, a live countdown to the deadline, the default action if unanswered, and option chips that send the chosen text as the human's reply. Card state is derived on the client — answered when a later user row exists, expired when the deadline passed — so it needs no extra fetch. The roster row shows a "Needs you" badge from the slot frame's `needs_you`. A read-only card variant is registered in the SDK defaults and on the Sessions page so the row is never drawn raw. MembersPage.tsx changes are three small hunks (isNeedsYou, the badge, the displayProfile prop) to stay clear of the in-flight remember-last-member and driving-sessions work in the same file. i18n: 21 keys under pages.members.chat in all 12 catalogs + pseudolocale, with per-language plural forms (CJK _other only; es/fr/pt/it _many; ru _few/_many); bases registered in pluralKeys.json. Evidence: temp-screenshots/crew-chat/ — GIF recorded on an isolated pod against a real member session and real model turns, no fixtures.
|
Parking this as draft: we want to design the member->human messaging path holistically (DM thread, notifications, session_send target=user, channel DMs) before landing one more entry point. Will revisit after the design note. |
|
Closing for now (owner decision 2026-09-10). We want the member -> human messaging path designed holistically first — DM thread, notifications, session_send target=user, channel DMs, and how it relates to ask_question (good question @iamwhatever) — before adding another entry point. Design note: research/member-to-user-messaging.md in the crew workspace; the mailbox model (author/recipient-tagged messages, trigger_turn, child -> parent push) will supersede this. Branch stays; a fresh PR will follow once the design lands. |
Problem / Motivation
A crew member that hits a wall — a permission it lacks, something only a person can reach, a one-way door — has had two bad options: ring the bell (a notification with no conversation around it) or write an
[OPTIONS:]line in its own transcript and wait. Neither is how it talks to a peer, and neither leaves a record of what is waiting on the human.Why it matters
Members run with nobody at the keyboard. Without a non-blocking way to raise a decision and carry on, a member either stalls (blocking
ask_question) or acts without saying so. The human, in turn, has no roster-level signal of which member needs them.What changed (motivation → approach → change)
Goal: make the human addressable as a peer — a card in the owning member's DM thread, nothing blocks, a badge on the roster.
Approach (revised on review): the first revision overloaded
session_sendwith a reservedtarget="user". The review showed that does not survive contact with the rest of the surface: two disjoint parameter sets under one name (four fields silently dead unlesstargetwas one literal), two kinds of operation (a send runs a turn on the target; an escalation writes a row and runs nothing), and — the expensive part — policy keyed on the tool name, so escalation inheritedsession_send's containment by accident with no way to write a rule that tells them apart. This revision shipssession_escalateas its own tool and revertssession_sendtotarget+message.What was built:
session_escalate(message, deadline?, default_action?, options?, goal?)→POST /api/session-control/escalate. Notarget; "user" is no longer a reserved word (a session may be titleduser, nothing consults titles). Delivery lands oneescalationrow in the DM thread of the member that owns the caller (a member: its own thread; a worker a member created: the creating member's thread; any other session: its own transcript, no index), mirrors it onto the bell bus (kind: escalation,group_key: escalation:<slug>:<goal>) and returns. Every caller gate ofauthorize_targetapplies with the same codes; the human is not a slot so no target gate does.Each policy site classifies the verb explicitly (spec table in
session-control.md→ "Escalating to the human"): inSESSION_CONTROL_TOOLS(caller identity); inCHANNEL_AGENT_BLOCKED_TOOLS— blocked, not onsession_send's grounds but onsend_notification's (the bell mirror is exactly the reach-the-user path that list closes), and the backend'slinked_session_caller/mirrored_callergate agrees, so letting a channel agent escalate is a deliberate two-site change rather than an accident of a shared name; granted to members in_MEMBER_DASHBOARD_GRANTS(it runs nothing and writes only into the member's own thread — the mid-turn, nobody-at-the-keyboard case is what the verb exists for); mounted-but-gated for both conductors like every other write; own schema inMCP_DASHBOARD_SCHEMAS. An escalation field passed tosession_sendis now refused as an unknown field, never dropped.Three constraints (spec): non-blocking with a veto window (
deadline+default_action= "unless you stop me by t, I do X"; the window closing recordsdefaulted, never a failure; no deadline wakeup — the member that declared the default is the actor that runs it); attention budget (onegroup_keyper goal, no transport-specific switch); escalation is not approval (anything the human must actively grant stays on the approval surfaces).The per-member conversation index (
crew_conversation.py, feat(members): thin per-member conversation index #8612) now rides here with its consumer (its former host fix(members): dispatch server carries the gateway home override #8611 was narrowed to the dispatch-home fix). Record written before the card under a pre-minted row id;needs_you/pending_escalationsderived and projected on theslotsframe andGET /api/members;GET /api/members/{slug}/conversation(owner-only) exposes it. Open decisions per member are capped (MAX_PENDING_ESCALATIONS= 50): pending records are never evicted by the file's size cap, so at the ceiling the next escalation is refused atomically (escalation_backlog_full, 429) with the count, telling a runaway member to wait for answers rather than grow the index without bound; settled records (answered, or past a deadline) free slots. Reply matching is one rule on both sides: a live owneruserrow withmeta.escalation_id(through idle / queue / steer / merged-drain paths; a non-owner entry never launders an id onto an owner row) answers that record; typed text answers only when exactly one record was pending at the row's position; a replayed row answers nothing. A mixed merged batch (chips and typed text drained as one row) is replayed in order at the drain against the pending view, and the row then names every record the sequence answered — so "chip for A, then text" answers A and B exactly as the two replies would have separately, while "text, then chip for A" leaves B pending exactly as the sequence would; with no pending view the row names the chips alone (the under-answering side). Restore-time reconciliation re-derives the index from the transcript (orphans retracted after a grace, durable replies applied, judged at the reply row's own timestamp); live rows not yet flushed count for card presence only — theirhuman_replyis stripped before the replay, so a record is never settled on disk ahead of the reply that settles it — and an answered record whose card survives but whose reply was rewound away is reopened (the transcript is the truth), so reconciliation runs on every generation change, pending or not; cards the transcript holds but the size cap already evicted from the index count as candidates in that replay (never written back), so a reply that was ambiguous when made stays ambiguous. An index file that exists but cannot be read is not an empty index: writers refuse to overwrite it, the roster forces a reconciliation, and the reconciliation rebuilds every card the transcript holds as a real pending record before replaying replies — repaired from the truth, never replaced by a blank. Both readers of the index — the roster's pending count and the thread'sGET /api/members/{slug}/conversationview — go through the same reconcile step (_reconcile_member_sync) before they read, so a rewind that removed an answering reply reopens the record on whichever surface polls first. In a member thread the queue merge breaks at a human-provenance boundary (_dequeue_next_message): the owner's stamped replies never share a merged row with an unstamped neighbour (a peer'ssession_send, a cron prompt), which would otherwise striphuman_replyfrom the row and leave the answered escalation pending. A client POST may name one record via a validatedescalation_id; the pluralescalation_idsis the drain's merge artifact and is stripped from client meta, so one body can never answer every decision at once. The on-loop pending view is bound to the rawKIROCREW_HOMEit was resolved under, so a home change reads as unprimed until the next off-loop prime — never another home's badge — andprime()takes the same per-slug lock the writers hold, so a restore-time prime cannot install a stale view over a writer's fresh one. The live hook's persist-and-mark tasks are serialised per slot in transcript order, so a chip's slow save can no longer let a later typed reply be judged first (and decline against two pending).optionsand the two other choice surfaces (review).optionsis the card's contract — the interactiveEscalationCard(folded in from feat(members): chat-profile projection and escalation cards in the DM thread #8614, see below) renders it as the row's own chips in the Crew Members thread and answers withmeta.escalation_id. Every other surface draws the row by default:EscalationNoticeis registered in the default renderer registry (so the Crew Members thread — aChatPane, the surface the bell deep-links to — shows the member's markdown, the veto window in words — "Unless you reply by <localized time, with its zone>, Radar will: ", the same actor and clock the bell names — and the options bound to how to answer them ("Reply in this thread with one of these to answer: …"); in the Crew Members thread the interactive card claims the role and replaces that entry. The bell mirror body says the same things in words (a UTC clock time, no glyphs). The tool description promises exactly that and no click.deriveFollowUpOptionsgains an explicitescalationbranch that ends the pill scan, so an escalation row can never inherit a previous assistant turn's[OPTIONS:]chips (the stale-chip mis-answer the review traced). Theask_questioninteraction is now a stated rule: a card is resolved through its own endpoint and writes no transcript row, so answering it never answers an escalation, and an escalation arriving while a card is open changes nothing about the card.The bell's "Open" lands on the thread.
_mirror_escalationemits/members?member=<crew name>;MembersPagenow consumes that param once the roster loads (opens the member's thread through the same idempotentmemberThreadpath a click uses, then strips the param withreplace), so a notification opens the thread that needs the human rather than an unselected roster.GET /api/members/{slug}/conversation's 400 now carriescode: invalid_member_sluglike every other refusal in that handler.Tests
test/test_escalation.py— delivery into own / creating-member / plain thread with no turn started (any_run_chatcall asserts); a session titleduseris not a collision;session_sendhas no escalation arm (adeadlineon it is refused as unknown, never forwarded); the verb is classified at every policy site (SESSION_CONTROL_TOOLS,CHANNEL_AGENT_BLOCKED_TOOLS,MCP_DASHBOARD_SCHEMAS, member grants, not conductor grants;session_sendschema back totarget+message; escalate schema has notarget; description promises no click); MCP dispatch posts/api/session-control/escalateunder the verified key and renders the non-blocking reply; caller gates + SEL denial audit (escalate:<code>); index record before card,needs_youprojection, reply clears (live) / does not (replayed), merged-drain id laundering, deadline →defaulted, field validation refused before append, bell mirror payload now including the readable options line, route passthrough + 400, roster + conversation endpoint.test/test_crew_conversation.py(moved here with the index).test_mcp_dashboard_registration.py/test_mcp_dashboard_folders.pypin the advertised set withsession_escalate;test_channel_blocked_tools.py's existing "every session-control tool is contained" pin covers the containment entry.website/src/test/deriveFollowUpOptions.test.ts— anescalationrow ends the scan and offers nothing, its ownmeta.optionsnever leak into the bar.test_mixed_merged_batch_replays_chip_then_text_in_orderpins both orders of a mixed drained batch (chip→text answers both; text→chip leaves the second pending) andtest_replay_helper_falls_back_to_the_chips_alone_when_the_view_is_unavailablethe non-member / unprimed fallback;TestPendingViewFollowsTheDataHomepins that aKIROCREW_HOMEchange makes the memoized view unprimed, not another home's.test_restore_sweeps_orphaned_pending_recordsnow also pins that a reply present only in the live window does NOT settle its record on a roster read, and does once persisted.test_reply_marks_settle_in_transcript_order_even_when_saves_contendpins that a chip whose save is slower than the typed reply that follows still marks first, so both records settle.TestPendingCeiling(unit) andtest_backlog_ceiling_refuses_with_backpressure_and_no_row(route) pin the open-decision ceiling: refused at the cap with no row written, settled records do not count, an answer frees a slot.test_client_meta_carries_only_the_validated_singular_escalation_idpins thatescalation_idsand an ungrammaticalescalation_idnever reach the row;test_reconcile_retracts_orphans_defers_young_and_applies_durable_answersnow also pins that rewinding a reply reopens the records the transcript no longer answers, and that the reply coming back re-answers them with their original stamps;test_reconcile_counts_index_evicted_cards_still_in_the_transcriptpins that an index-evicted card still in the transcript keeps an ambiguous reply ambiguous and never reaches the index;test_unreadable_index_is_rebuilt_from_the_transcript_and_never_overwrittenpins that a torn index refuses writers, is rebuilt from the card rows (meta intact, then answered by the transcript's reply) and reads as repaired;test_a_human_reply_that_happens_to_start_with_the_peer_prefix_still_answerspins thathuman_replyalone decides.MembersPage.test.tsx—?member=opens the named member's thread once and strips the param; an unknown name leaves the roster.messageRenderers.test.ts—escalationresolves to a default entry;EscalationNotice.test.tsx— veto line in words (no raw timestamp), options as text, deadline-only and bare variants, defensive meta read. The bell-mirror test asserts the sentence form and the absence of glyphs.Manual verification
Verified live on the previous revision (isolated pod, crew "Radar", KAS backend): card landed in the member's thread, roster and slots frame reported
needs_you: true, index held the pending record, the member's turn continued; a reply in the thread flipped the record toansweredand clearedneeds_you. This revision changes the tool name, route and policy classification, not the delivery path; those are pinned by the tests above.Screenshots / video
The escalation row as the Crew Members thread draws it (the surface the bell deep-links to), rendered through the real
ChatMessageList+ default registry — three variants (deadline + default + options; deadline only; bare) — and the bell mirror body in words. Captured bywebsite/scripts/capture-escalation-notice.mjs(fixturewebsite/capture/escalation-notice.{html,tsx}), which self-checks the claim: three cards claimed by default, the veto line a sentence, no raw ISO timestamp, no glyphs.Light theme
Related Issues
no linked issue: stacked feature work (see Stack).
Stack
Collapsed on 2026-09-07: #8611
fix/member-dispatch-homemerged tomain; #8614feat/crew-chat-profile(Crew Members chat projection + interactive escalation card) merged INTO this branch. This PR now carries backend verb + conversation index + frontend card, based onmain, with no downstream.Checklist
feat|fix|docs|refactor|perf|test|chore|ci|build|revert: ...)Frontend: chat-profile projection and escalation cards (folded in from #8614)
#8614 was stacked on this branch and merged into it (2026-09-07); its body follows so the combined PR reads as one. Rebased onto
mainafter #8611 and #8546 landed: this branch's one-shot?member=deep-link effect and its two tests were dropped in favour of #8546's URL-driven member selection, which the bell mirror's/members?member=<name>link now rides.While the base was a feature branch only the 20-check reduced matrix ran, so the first full run on
mainsurfaced latent test debt in both PRs, fixed here: the slot projection'sneeds_youkey added to theto_dictkey-order contract; the roster reconcile usesmember_thread_session_alias(main's canonical-alias test); thesession_escalaterefusal audit redacts throughredact_log_via_context(main's gate-side redactor census);_mark_member_escalations_answered'sasyncio.runfallback allow-listed in the spawn audit as a non-spawn; three fixtures corrected (a reply stamped before its record'screated_tsis correctly not an answer; a past deadline written after both records sorecord_escalation's pre-append sweep does not default the first; the stale-grace card test now confirms the cancel, matching the card's rule and case (g)); and the newhi/kostrings brought in line with the catalog style tests (informal तुम,이(가), ‘ ’ quotes). Also from that round's review: an option send now binds its (empty) pre-send record under the queue id whether or not its in-flight entry is still present — two identical option chips are indistinguishable by wire text, so a sibling's pre-receipt cancel could consume this send's entry and leave its own later cancel to the content parser, which appended the option label to the draft. An unreadable receipt (unknown/response-late) keeps the in-flight record: the send may have queued under an id this pane will never learn, so that record is the only one a cancel of the card can find.Summary
The Crew Members DM thread rendered the member's raw transcript — every tool row, notice and nudge between the human's message and the member's reply. That is the right view on the Sessions page and the wrong one for a conversation. This PR gives
ChatPaneadisplayProfile(transcript, the unchanged default, orchat) and mounts the chat profile on the Members page.recorded from
693f9d3b5a327c73d4d9b698369cf4735f54166b· isolated podwt-escalation, seeded config, crew "Radar" on the KAS backend · mode:--approval yolo· real server + real model turns, no fixturesWhat the chat profile does
pages/members/chatProjection.tsis a pure projection over the same rows, computed client-side so the view can never disagree with the transcript it is drawn from:meta.chat_process— one click on View process (N steps) shows them.WS tool_call → slotStatusDetail; falls back to the tool name, then a generic line). It is the only busy indicator in the chat profile — the footer's ghost carousel is suppressed there (stopping/compacting states still show).autonudge_authzrefusesmember-mode slots, and the member'skirocrew-corehas no identity channel on KAS). Whether to lift that guard for member-armed loops is a separate decision.Escalation cards
role: escalationrows (from #8613'ssession_escalate/POST /api/session-control/escalate) render as a card: title ("Radar needs you"), sender, goal chip, markdown body, a live countdown to the deadline, the default action if unanswered, and the options as a vertical single-choice list with one Send reply button (the same shape asQuestionCard; double-click an option to select and send in one gesture). The pick-then-send step is drawn, not implied: each option carries a radio dot, the button restates the pick once one is made (“Send ‘Hold until Monday’”, clipped to a phrase with the full text as its title), and until something is picked the hint beside it reads “Pick an option, then Send reply.” — so a click on an option is never mistaken for the reply. The reply carriesmeta.escalation_id, so the backend answers exactly that record — and because it is addressed by id,ChatPane.doSenddoes not treat it as the answer to whatever stateless question card or blocking ask happens to be pending on the slot (no capture, no retire): a reply to the member's escalation cannot silently dismiss an unrelated pending question. Card state is derived on the client by the same rule the index applies (#8613): a reply carrying the id answers that card; a free-text reply answers only when exactly one escalation is pending; a reply after the deadline never answers; the 1-second tick flips a live card to expired / defaulted ("Default applied: …") the moment the clock passes the deadline. The roster row shows a Needs you badge from the slot frame'sneeds_you. Every other surface keeps drawing #8613's read-onlyEscalationNotice(the SDK default), which points at the Members thread; this card is the ONE place an escalation is answered. The conversation index (GET /api/members/{slug}/conversation) is the authority on which escalation is still open; when that request fails before any record has loaded the cards fall back to the client-side rule, and when a REFETCH fails the last good record stays authoritative (a stalependingbeats a window simulation that could read a truncated transcript as answered); either way an inlineErrorNoticeunder the thread says so (title + the raw error, noaskAgent: the hand-off would unmount the pane and the composer draft in it), and the 20 s safety-net poll keeps retrying while a card is pending. An optimistic (not yet acknowledged) reply never counts as an answer, so a refused send leaves the card answerable. A reply the pane had to queue behind a running member turn keeps the card latched for as long as its queue entry exists; when the entry leaves the stack the latch lets go only if the server confirmed the cancel (useQueuedMessageActionsnow also exposescancelledIds, the ids whose DELETE resolved) — the stack removes a cancelled entry optimistically, so an entry that is merely absent may still be queued behind a failed cancel and unlocking on absence alone would let a second reply run on top of the first. Unconfirmed, the authority (the index or the confirming row) is the only release. The same rule covers an uncertain acceptance — a 2xx the pane could not read, or one that arrived after the abort deadline (SendOutcome.uncertain): the reply may be queued under an id the host never learned, so the card drops its 45 s valve and waits for the authority instead of unlocking on a clock. One invariant, stated once: a reply the server may hold is never released by a timer or by an entry's absence — only by the index, the confirming row, or a server-confirmed cancel. Cancelling such a queued reply from the stack restores the pick on the card and nothing to the composer: the option send binds an empty pre-send record (queuedSendStash), so the cancel path takes the stash hit instead of parsing the row and appending the option label to the draft. For an option send only, that empty record is also registered under the send's ownsendId(inFlightSendStash) BEFORE the request goes out and moved under the queue id when the receipt names one, so a cancel that lands in thequeue_push-before-receipt gap still finds it by wire text — safe precisely because the record is empty by construction (typed sends, whose text and files could be mis-restored by a wire-text collision, stay bound by queue id only); and a server-confirmed cancel releases the card's latch even for an entry the stack never showed it, so that same gap cannot leave the card locked with no way out.Coordination
MembersPage.tsxis touched in three small hunks only (isNeedsYou, the badge, thedisplayProfileprop) to stay clear of the in-flight remember-last-member and driving-sessions work in the same file. Everything else is new files underpages/members/plus adisplayProfileseam inChatPane;messageRenderers.tsxis untouched (itsescalationdefault stays #8613's notice).i18n
26 keys under
pages.members.chatin all 12 catalogs + regenerated pseudolocale, with per-language plural forms (CJK_otheronly; es/fr/pt/it_many; ru_few/_many); plural bases registered inpluralKeys.json; translator context inen.context.json. All 19i18n:checkgates pass againstorigin/main.Tests
chatProjection.test.ts(11) — hiding, final-reply selection, process attachment, streaming kept while running, fold of 3 silent rounds, non-quiet round not folded, escalation/permission keptEscalationCard.test.tsx(18) — body/options, select + Send →onSend(text, {escalation_id}), double-click quick send, radio dot + restated Send label + pick hint, long-option clipping, expired/defaulted (fake timers) closes the card and swaps the default line to "Default applied", live countdown and clock-crossing flip, answered badge,formatRemainingchatProfileRenderers.test.tsx(6) — theassistantoverride wins aftermergeRenderers, process disclosure, fold row, chips send via host handler, the SDK default alone draws feat(session-control): escalate to the human as a peer (session_escalate) #8613'sEscalationNotice(not this card)useEscalationIndex.test.tsx— fetch/poll/abort/dedupe, anderroris set only by a FAILED request (null while loading, on success, and on a non-member slot)MembersPage.test.tsx— badge from live slot and from roster fallback; ChatPane receivesdisplayProfile="chat"tsc -b, eslint, and the full i18n gate set are clean locally; the vitest suite forsrc/pages/members+src/i18n+ the ChatPane working-loader harness passes (732 tests).Stack
fix/member-dispatch-homefeat/crew-conversation-indexfeat/escalation-user-peer(base of this branch)feat/crew-chat-profile