You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
main fails the Frontend Checks (quality, i18n, docs, coverage) lane: tsc reports two TS2741 errors in app/src/pages/__tests__/Conversations.render.test.tsx, where ToolTimelineEntry fixtures are missing the now-required seq property. Every PR that syncs main inherits the failure.
Problem
What happened. CI Lite on main went from success at b48b62327 (08:04) to failure at 4a68fd727 (08:18):
src/pages/__tests__/Conversations.render.test.tsx(2414,21): error TS2741:
Property 'seq' is missing in type '{ id: string; name: string; round: number; status: "success"; }'
but required in type 'ToolTimelineEntry'.
src/pages/__tests__/Conversations.render.test.tsx(2438,21): error TS2741: (same)
##[error]Process completed with exit code 2.
Root cause — a semantic conflict between two individually-green PRs.
Each PR passed CI on its own base. Merged 14 minutes apart, the combination breaks main. Per-PR CI cannot catch this class of defect; it only appears post-merge.
Impact. Release-blocking — release is cut from main. Every open PR that merges current main fails Frontend Checks: already observed on #4912 and #4934 (both Rust-only feature-gate PRs that touch no frontend code, failing purely on inherited breakage). #4913 and #4914 will fail on their next sync.
Steps to reproduce.
git checkout main && git pull upstream main
cd app && pnpm typecheck
Two TS2741 errors at Conversations.render.test.tsx:2414 and :2438.
Platform: CI (ubuntu runner) and local dev; not platform-specific.
Solution
Add seq: 0 to both fixtures in app/src/pages/__tests__/Conversations.render.test.tsx:
seq: 0 is the correct value and matches #4945's own convention for every comparable fixture it updated (e.g. timeline/selectors.test.ts, SubMascotLayer.test.tsx, ToolTimelineBlock.test.tsx): both are single-entry timelines on distinct threads, so issue-order index 0 is accurate. The change is test-fixture-only — no production code, no behavior change.
Acceptance criteria
Repro gone — pnpm typecheck passes on main; CI Lite green on the merge commit.
Summary
mainfails the Frontend Checks (quality, i18n, docs, coverage) lane:tscreports twoTS2741errors inapp/src/pages/__tests__/Conversations.render.test.tsx, whereToolTimelineEntryfixtures are missing the now-requiredseqproperty. Every PR that syncsmaininherits the failure.Problem
What happened. CI Lite on
mainwent fromsuccessatb48b62327(08:04) tofailureat4a68fd727(08:18):Root cause — a semantic conflict between two individually-green PRs.
b48b62327, merged 08:04) added twoToolTimelineEntryfixtures toConversations.render.test.tsx(the cross-thread disclosure-leak test).4a68fd727, merged 08:18) madeseq: numberrequired onToolTimelineEntry(app/src/store/chatRuntimeSlice.ts:286) and updated 12 test files — including this one — but was authored against a base predating fix(conversations): key the proactive-thread insights fallback (disclosure state leak) #4944, so it never saw those two fixtures.Each PR passed CI on its own base. Merged 14 minutes apart, the combination breaks
main. Per-PR CI cannot catch this class of defect; it only appears post-merge.Impact. Release-blocking —
releaseis cut frommain. Every open PR that merges currentmainfails Frontend Checks: already observed on #4912 and #4934 (both Rust-only feature-gate PRs that touch no frontend code, failing purely on inherited breakage). #4913 and #4914 will fail on their next sync.Steps to reproduce.
git checkout main && git pull upstream maincd app && pnpm typecheckTS2741errors atConversations.render.test.tsx:2414and:2438.Platform: CI (ubuntu runner) and local dev; not platform-specific.
Solution
Add
seq: 0to both fixtures inapp/src/pages/__tests__/Conversations.render.test.tsx:entries: [{ id: 'a-1', name: 'web_fetch', round: 1, status: 'success' }]entries: [{ id: 'b-1', name: 'send_email', round: 1, status: 'success' }]seq: 0is the correct value and matches #4945's own convention for every comparable fixture it updated (e.g.timeline/selectors.test.ts,SubMascotLayer.test.tsx,ToolTimelineBlock.test.tsx): both are single-entry timelines on distinct threads, so issue-order index0is accurate. The change is test-fixture-only — no production code, no behavior change.Acceptance criteria
pnpm typecheckpasses onmain; CI Lite green on the merge commit.main.Related
b48b62327)seqrequired (4a68fd727), the merge that surfaced the conflict