CR-2026-139 — File Type on Memory Entries

Version. 0.1 · Date. 2026-07-03
Status. Drafted, not staged for build. Number 139 confirmed free at staging (highest prior: CR-2026-138). Base: OL main @ 443c950. No build yet.
Repo. loomworks (frontend display only, unless investigation finds otherwise).

What this fixes

Memory entries with a source file (held or committed) show content, provenance, and View source — but not what kind of file produced them. A PDF summary and an image description look the same in the list.

Fix

Display the file type on each Memory entry with a source file. The engine already tracks this as source_mode ("text"|"voice"|"pdf"|"image", confirmed present on every assertion via CR-2026-130/134). Add a display label — plain terms, not the raw wire value (e.g. "PDF," "Image," not pdf/image) — matching the pattern already used for held/settled state labels (CR-2026-137's matchedFileStateLabel).

Seed check

No conflict. Plain-terms discipline requires translating raw wire values to Operator-facing labels — this fix follows the same pattern already established.

Out of scope

No change to how source_mode is set or stored. No change to View source itself.

DUNIN7 — Done In Seven LLC — Miami, Florida · Loomworks — CR-2026-139 — File Type on Memory Entries — v0.1 — 2026-07-03