amal66 gives Mike's client-side chat a safety net

A new testing gate aims to catch broken conversations, uploads and sign-in flows before they reach users.

chat-uiworkflow

This is reliability work, but it lands where legal teams notice it: the browser experience. amal66 has added checks around the layer that connects every screen to Mike's services, then made a minimum level of test coverage a requirement for future changes.

Sign-in and error handling, including clearer responses when multi-factor authentication is required.
Live chat responses that still appear coherently when a network delivers a response in awkward fragments or includes an error.
File downloads and upload checks, so supported files and retrieved material behave predictably.
Available AI options and saved chat history, helping the interface show the right choices and prior exchanges.

The next priorities are testing how assistant answers render and how table-based review work holds its state.

So what Teams considering Mike for day-to-day legal work should care because this makes the visible product less likely to regress quietly.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from amal66/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

2392e677 test(frontend): SSE/client unit tests + coverage ratchet Amalanand Muthukumaran 2026-07-25 ↗ GitHub

SHA	Subject	Author	Date
`2392e677`	test(frontend): SSE/client unit tests + coverage ratchet	Amalanand Muthukumaran	2026-07-25	↗ GitHub
commit body Unit tests for the frontend client library and the SSE stream consumer, plus a v8 coverage ratchet over src/app/lib/** mirroring the backend's (floors just below measured, only ever raised): - mikeApi.ts: request/auth/error plumbing, blob downloads, getChat and mapTRMessages mapping, and all four streaming endpoints (the frontend half of the SSE contract - raw Response passed through unconsumed). - useAssistantChat: SSE parse loop against real ReadableStream bodies - chunk-boundary reassembly, multi-event chunks, reasoning/content interleave, error events, malformed lines, EOF without trailing newline. - documentUploadValidation.ts and modelAvailability.ts: full coverage. - test:coverage script + @vitest/coverage-v8; CI frontend test step now runs it (still --if-present). - docs/frontend-testing.md: how to run, ratchet rules, TODO backlog. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

commit body

Unit tests for the frontend client library and the SSE stream consumer,
plus a v8 coverage ratchet over src/app/lib/** mirroring the backend's
(floors just below measured, only ever raised):

- mikeApi.ts: request/auth/error plumbing, blob downloads, getChat and
  mapTRMessages mapping, and all four streaming endpoints (the frontend
  half of the SSE contract - raw Response passed through unconsumed).
- useAssistantChat: SSE parse loop against real ReadableStream bodies -
  chunk-boundary reassembly, multi-event chunks, reasoning/content
  interleave, error events, malformed lines, EOF without trailing newline.
- documentUploadValidation.ts and modelAvailability.ts: full coverage.
- test:coverage script + @vitest/coverage-v8; CI frontend test step now
  runs it (still --if-present).
- docs/frontend-testing.md: how to run, ratchet rules, TODO backlog.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1322.md from inside the repo you want the changes in.

⬇ Download capture-thread-1322.md