Skip to content

fix: reverse-chronological transcript order + markdown rendering#147

Merged
gbasin merged 1 commit into
masterfrom
fix/transcript-reverse-markdown
Jun 15, 2026
Merged

fix: reverse-chronological transcript order + markdown rendering#147
gbasin merged 1 commit into
masterfrom
fix/transcript-reverse-markdown

Conversation

@gbasin

@gbasin gbasin commented Jun 15, 2026

Copy link
Copy Markdown
Owner

Summary

Follow-up polish to the hibernated transcript reader (patch 0.3.1), addressing feedback:

  • Reverse-chronological order — newest entries render at the top, oldest at the bottom (Messages and Events). "Load earlier" moves to the bottom; older history appends below without yanking scroll, and the view opens scrolled to the top so the latest is visible.
  • Markdown rendering — message bodies render as markdown via react-markdown + remark-gfm + remark-breaks (headings, bold/italic, lists, fenced code, tables, links, blockquotes). Tool output stays raw <pre>. Single newlines are preserved as line breaks.

The data model and pagination/keys are unchanged — only render order and message formatting changed.

Validation

  • bun run lint && bun run typecheck && bun run test (728 pass) — updated ordering assertion + added a markdown-rendering test.
  • bun run build.
  • Visual check (isolated dev harness, mocked fetch): confirmed newest-at-top ordering (09:03 → 09:00 descending) and markdown rendering (heading, bold, italic, ordered/bullet lists, inline code, fenced code block, table, blockquote, link) with no literal markdown syntax left.

- Render newest entries first (Messages and Events); 'Load earlier' moves
  to the bottom and older history appends below without yanking scroll.
- Open scrolled to the top so the latest is visible.
- Render message bodies as markdown (react-markdown + remark-gfm +
  remark-breaks); tool output stays raw. Data model/pagination unchanged.
@gbasin gbasin merged commit 2683d02 into master Jun 15, 2026
5 checks passed
@gbasin gbasin deleted the fix/transcript-reverse-markdown branch June 15, 2026 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant