Files
pipelines/app/notes/C3-bar.md
T

1.2 KiB

Manager completion after the server persistence failure

The run ended with the server's duplicate step_file_changes insert bug, not an app fault; the worktree held a complete slice. The manager ran the chat suite (98 tests pass) and inspected the composer: host-native multiline field, draft owned by the controller so a live rebuild keeps the caret, Enter newline with Ctrl/Cmd+Enter send, one Send/Stop control using the host's semantic error tint, queued and refusal lines as polite live regions. Attachments and the slash palette are deliberately absent and recorded as open work.

The server defect is fixed with a regression and deployed separately; this app slice needed no retry.

Real-app verification

The normal-app browser probe now focuses the composer as an operator does, types, sends through the primary control, and asserts exactly one chat_prompt with the exact text, session id, operation id and native message id, plus the optimistic message in the rendered thread (OCR). It passes with the existing run/changes/ artifacts/chat/settings steps in one flow. The Ctrl/Cmd+Enter shortcut stays covered by the widget probe: a synthetic key event does not set the engine's hardware-keyboard state reliably in headless Chrome.