fix(e2e): #2788 residual — shell-safe chat seed JSON + Activity API auth #2792
Reference in New Issue
Block a user
Delete Branch "fix/2788-e2e-chat-residual"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes the two harness regressions left by #2788 on main (job 492389).
canvas/e2e/fixtures/chat-seed.ts:seedChatHistory()now uses psql dollar-quoted literals for JSON request/response bodies, so seeded messages containing quotes or backslashes no longer produceinvalid input syntax for type json.canvas/e2e/chat-separation.spec.ts: Activity API source-filter tests now send the workspace auth token, fixing the exposed 401s.Researcher RCA: #2782 (comment).
SOP checklist
npx tsc --noEmitandnpx eslintclean on both modified files; fullE2E Chatrun is expected in CI.E2E Chatworkflow on main.activity_logsbut kept hand-escaped JSON string literals, which break on quote-containing seed text; the Activity API tests were also missing auth headers.APPROVED on head
a3206741506e9ff96d49400a1d5b09aa7f9df8d7.Verified the #2782/#100749 residual fixes:
seedChatHistory()now writes MessageStore-compatibleactivity_logsrows using per-row dollar-quoted JSON literals, so quote/backslash-containing seed text is preserved as validjsonb; the spec includes quote-containing seeded user/agent messages that would have reproduced the prior invalid-json failure.entries.length > 0) andsource_idassertions for canvas-vs-agent separation.chat-seed.tsandchat-separation.spec.ts; the #2764/#2788 source separation structure remains intact.E2E Chat is green on this head, including the desktop echo coverage path from the repaired push-mode fixture. Remaining visible red/pending statuses are review/SOP/pending gate statuses, not a code failure in this diff. No blocking issues found.