2 Commits

Include renames

Author	SHA1	Message	Date
amosblomqvist	7f51259fc6	feat: Wave C - pi-native steer/follow-up delivery ... Delivery now rides pi's OWN follow-up queue when a run is live, and a carry-everything idle wake otherwise. One registry, two vehicles; claimSteers and continuation coalescing are deleted (owner rulings, 2026-09-26: follow-ups only; one queue; the wake is the only appender). THE LIVE RUN (vehicle 1): the chat-handler registers the streaming turn's agent (registerLiveAgent, next to registerTurn); the pump hands every eligible queued marker to agent.followUp() - pi polls that queue when the run would otherwise stop, injects the markers (message_start/message_end on the live wire), and CONTINUES the same run. followUpMode "all" joins every handed marker in one continuation turn. The question stopper runs before the follow-up poll, so an open quiz is never overridden - a handed marker strands at settlement and waits (today's pacing). probe-handoffs never take this path (the handoff must START the teacher's run - a record-level branch). SETTLEMENT RECONCILIATION: settleSteers(chatId, persisted) at onFinish (after unregisterLiveAgent) resolves+flips entries the run delivered and returns stranded ones to pending - the registry stays the truth; the dead agent's queued copy is abandoned. This is what makes the handoff safe: pi owns no retry for a stranded follow-up. THE IDLE WAKE (vehicle 2): waitForIdle (unchanged gates) then ONE turn carrying EVERY pending marker as its input appends - dequeue-at-fire (the Wave B regression lesson: the wake run's own follow-up poll must never see its own cargo; a 409 pushes the cargo back and retries). CLIENT: applyWireEvent now upserts non-assistant messages by id, so in-run injected markers render live instead of dropping until settle. Tests: jobs 44/44 (live handoff, settlement stranding, handoff-waits, one-wake-carries-all); chat-flow 23/23 (the double-append pin drives the real pump through the new input); session-core 28/28 (custom-role wire appends). Full suite 997/997, tsc/lint/build green. Live smoke (PORT=3004): research job delivered mid-probe - parked behind the dangling questions exactly per semantics, landed once on the open gates, teacher folded the brief in and re-dispatched; the second (good) result rendered the full 10-source brief card and the lesson continued from it. No duplicate ids anywhere in the record. Known gap flagged to owner (NOT from this change): the server accepts malformed answer events via raw API (answers without the answers[] shape) and AnsweredCard then crashes the page render - surfaced by the smoke's scripted answers, repaired by hand in the scratch record.	2026-09-26 03:46:09 +03:00
amosblomqvist	7ab47d4fcb	Wave B: the native message record — input events, projection, adapter death ... The chat record is now pi-native agent history (LhMessage[]), the AI SDK's UIMessage transcript contract is gone from the server, and every client turn arrives as ONE explicit input event. Core (new): - src/core/native-messages.ts — the LhMessage taxonomy (user/assistant/ toolResult + lhMarker customs: verdict, probe-handoff, subagent-steer, subagent-abort, plan-block), constructors, and toLlmMessages — the single model-facing seam (convertToLlm): strips ids, flattens markers to user text, drops UI-only plan-blocks, synthesizes INTERRUPTED results for dangling aborted calls, never throws. - src/core/projection.ts — projectNative: the one-way native → UIMessage projection (consecutive assistant+toolResult runs group into one assistant view message; toolResults attach backward by toolCallId; markers project to data parts; plan-blocks splice after the last successful plan_init). Every existing consumer reads through it. - src/core/input-events.ts — the ChatInput union (text/answer/verdict/ continue), parseChatInput validation, and inputAppends (answer targets the dangling question call or 400s; verdict = optional note user message + native verdict marker). Server: - chat-handler.ts — the turn root takes {chatId, input}; write-ahead persists input appends + claimed steers before the turn; claimSteers coalesces the whole queue with the handler's steerDelivered filter as the dedupe seam; teacher-vs-prober branch on hasProbeDone. - turn-service.ts — persistTurn stamps ids, drops clean question placeholder toolResults (the record ends at the unanswered call), emits plan-block markers idempotently (plan-blocks.ts rewrite), and persists abort partials. - ui-stream.ts — PiTurnSpec takes the native base; the wire dialect is unchanged. jobs.ts steers are native markers (steer_<jobId> dedup ids); waitForIdle reads danglingQuestionOf. teacher-agent.ts wires convertToLlm: toLlmMessages. record-adapter.ts DELETED wholesale. - GET /api/chats/[id] serves messages: projectNative(record.messages). Client: - chat-transport.ts — the 409 retry is IDENTITY (re-POST the same event body after the turn settles — the event was never persisted pre-acceptance; the merge logic is gone). The transport consumes the stashed input event via prepareSendMessagesRequest and throws loudly on a missing stash. - chat.tsx — every send call site stashes exactly one ChatInput event (text, answer, verdict, continue) before invoking the SDK send. Tests: full native migration (chat-flow rewritten to input events and native record pins; jobs/extraction/demos/graph/usage/plan-blocks/ probe-done/reattach-transport converted; record-adapter.test.ts deleted; chat-transport tests pin the identity retry). 982/982, typecheck, lint, build all green.	2026-09-26 00:37:46 +03:00