mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
f5d21af60b
The per-file coverage gate caught three uncovered paths in the error handling this round added: the page banner for a failed row removal, the editor card's transport-rejection catch, and `store.fail` itself. Two of them are one click each — Remove with a rejecting write, Apply with a rejecting write — so they are covered through the UI rather than by calling the helpers directly. The third was a duplicated `error instanceof Error ? error.message : String(error)` in two files; it becomes one exported `messageOf`, which removes the branch from both call sites and gives the fallback arm a home a direct unit test can reach (the lint rule forbids rejecting a promise with a non-Error, so a rejection cannot exercise it).