Version. 0.1
Date. 2026-07-02
Status. Drafted, not staged for build. Number 136 confirmed free at staging (highest prior: CR-2026-135). Base: engine main @ f9cf51f, OL main @ 5311dca. No build yet.
Repos. loomworks-engine, loomworks.
Root cause diagnosed via. Diagnosis Brief — Missing Descriptions on Repeat Upload — v0.1 (unstaged, this session).
Uploading a file shows the full description (image or document) in chat only for as long as the browser tab stays open. On reload or navigation away and back, the description disappears from chat — only the short outcome sentence ("Here's what I found in that file.") remains. This affects every upload, not a specific file or repeat count.
record_turn (CR-2026-131) persists only the composed outcome sentence, never the description text. The full description exists solely in the browser's live upload response (uploadResults), attached to the turn in memory. ConversationTurn has no field to carry it. On reload, history is fetched from the persisted (short) turn only.
Persist the full per-file description as part of the turn record (or a linked record the turn references), so it survives reload the same way the outcome sentence does. The Memory panel already stores the description reliably as an assertion — the fix should make the chat turn's history reconstruction pull from that same durable source, rather than depending on client-side state that vanishes.
No conflict. Seed's Memory principle — accumulates with provenance — supports this: the description is contributed knowledge and should be reliably recallable, not lost on reload.
No change to CR-2026-135's brief-description prompt tuning (already shipped). No change to the assertion/Memory-panel storage, which already works correctly.