[NoahHendrickson]

Threads, PRs, changelogs and automations for a project live in separate places, so there's no one spot to work "in" a project. Spaces gives each project one.

What changed

• Sidebar: a fourth V2 grouping, Spaces. Each project becomes a space: its favicon and name, then Threads (collapsed by default, with a count and status marks), the cards, and PRs, Changelog and Automations rows.
  • The children step in on a rounded guide line.
  • A folded space shows a summary: its thread count and marks, and its open PRs.
  • Header buttons slide in on hover.
  • A space with no active threads keeps its header and rows.
• Home: the space's name opens its Home. That's the space's new-thread draft: the real composer (model, effort, modes), started near the top, with the space's active threads, PRs and automations beneath it. A Home with text already in it is reopened as it is, not replaced.
• Tabs: a browser-like tab row at the top of the chat column, above the header, never sharing its row.
  • Tabs are ranked by status: needs you, then done, working, monitoring, idle.
  • Each tab leads with its provider mark (Claude mascot, Codex cloud) and ends with its status mark.
  • Close and ⋯ widen the tab on hover; double-click renames.
  • A split draws one row over both panes, with the two threads lit together in a tray. Closing one half ends the split and keeps the other pane.
  • A float window gets no row.
• Sidebar split pair: under a space, a split's two cards stack in the same tray, both lit.
• Rows: PRs opens the PR page filtered to the space. Changelog is a new /changelog?space= page of merged PRs by week. Automations opens /scheduled?space=.

The work is client-only (fork-spaces in .fork/customizations.yaml, guard test forkSpaces.test.ts). The Feedback and Figma rows are deferred because they need server work.

Ported onto the upstream sync

This branch now carries #239 (04f2e74) so it lands after the sync. 838c9a2 ports Spaces to what the sync changed: project grouping moved into client-runtime, the sidebar visibility filter takes the delegated-child set, the thread menu needs canShareWithGuest, the rename helper and formatRelativeTimeUntil are gone, and the new "request" card status ranks with what needs you. Comments are cut to the new four-line limit, and render-time clocks and the tab-list effect carry reasoned lint disables, as upstream does in the sidebar.

Reviewed with sol-loop: 3 rounds with gpt-6.1-sol on high. Sol verdict: approved

Built with Claude Opus 5.5 in Claude Code (running in T3 Code).

🤖 Generated with Claude Code

[NoahHendrickson]

Code quality review — commit 216bce6a6c1d513e199afc9b8572d77fcbf1759a

Verdict: changes requested (posted as a comment because the reviewing account is the PR author). The behavior looks deliberate and the new logic modules (spaceTabs.ts, changelog.logic.ts, spaceSidebar.ts) are tidy, tested, pure functions. The integration into existing code is the problem. Spaces is wired in as a mode flag threaded through shared paths (Sidebar.tsx, SidebarV2ProjectGroupHeader, the list animation, and ~30 CSS rules), when it should be its own section model and its own components. Several helpers are copy-pasted across the new files.

No file crosses 1k lines for the first time: Sidebar.tsx (5384→5621) and ChatView.tsx were already far past it. But +237 lines of spacesGrouped branches in Sidebar.tsx is exactly the growth the fork should be keeping out of upstream files.

1. SidebarV2ProjectGroupHeader became a two-mode component (structural)

variant?: "project" | "space" plus four space-only optional props (onOpenSpace, spaceActive, collapsedSummary, spaceProject). Each one means nothing unless variant === "space". Nearly every element now branches on space:

• the hit button spreads one of two prop bags (open vs. collapse semantics, different aria)
• the mark is either a favicon or the folder/chevron stack
• a wrapper span is display: contents in one mode and a flex box in the other
• the actions get an extra reveal wrapper in space mode
• the caret button exists only in space mode
• rounded-full overrides are sprinkled on top

These are two different headers: one is a collapse toggle with a folder, the other a navigation pill with a favicon and a separate fold caret. Suggested fix:

• Extract the shared menu+plus cluster (sectionActions) into a small SidebarV2SectionActions component.
• Add a dedicated SidebarV2SpaceHeader in custom/spaces/ with required project, active, onOpen, summary props.
• Restore the project header to its pre-PR shape.

That removes the variant flag, the ?? undefined optionality, and the contents trick.

2. Sidebar.tsx: spacesGrouped spliced into ~12 unrelated flows (spaghetti growth)

New spacesGrouped conditionals appear in:

• the threadLastVisitedAtById selector
• section building
• threadsVisibleInProjectSection (collapsed and keepThread)
• afterOpenSection
• projectReorderEnabled
• both shelf toggles
• five header props
• pre/post row injection

header.projectKey !== UNGROUPED_PROJECT_KEY is restated 5 times. projectGroups.find(...) runs twice for the same header (space and spaceProject). Two separate new Map(activeSections.flatMap(...)) passes compute per-space data.

Code-judo: build one space model per section in spaceSidebar.ts, for example buildSpaceSections({ sections, projectGroups, expanded, kindOf }) → Map<projectKey, { group, summary, openPullRequests, threadsFolded }>, which returns nothing for the ungrouped section. The render site then does one const space = spaceSections.get(header.projectKey) lookup. Every UNGROUPED_PROJECT_KEY check, both finds, both Maps and spaceThreadsFolded collapse into it. Better still, a single <SidebarV2SpaceSection> that takes the rendered cards as children would cut the header / Threads row / cards / link rows splice down to one fenced call.

3. Spaces mode inferred from DOM shape in CSS and JS (magic / brittle)

• ul:has(> li[data-fork-space-header]) appears in about a dozen theme.custom.css rules, and isSidebarV2SpaceListItem runs a querySelector on every animated item to rediscover the same thing. Sidebar already knows the grouping. Put data-fork-grouping={grouping} on the list once and key CSS and the animation plugin off it. That's cheaper than a broad :has() on the whole list on every recalc, and it can't break when the header li changes shape.
• The shelf toggles render both the upstream chevron and a SidebarV2SpaceCaret, and CSS (& > svg:not([data-fork-shelf-caret]) { display: none }) hides one. Render one or the other with a single ternary.
• The split-pair tray radius matches Tailwind utility class names (.rounded-\[16px\], .rounded-full, .rounded-md) on the cards, and other rules target span.h-px and span:first-child. A radius tweak on the card silently breaks the tray. Expose the card radius as a CSS variable (or a data attribute) instead.

4. A parallel status vocabulary that can drift from the cards

spaceSidebar.ts defines SpaceThreadMark + MARK_BY_KIND, SidebarV2SpaceRows.tsx hand-writes SPACE_MARK_STATUS (label/tone/mark), and spaceTabs.ts adds TAB_RANK_BY_KIND. The docs say the summary is "read off the cards' own status ladder, so the row and the cards cannot disagree". It isn't: the labels are re-typed (for example "Needs you" vs. the card's "Needs approval" / "Needs input"), and any new kind or tone needs edits in three tables. Export sidebarV2CardTopStatus (or dedupe each card's own topStatus by tone:mark) and drop SpaceThreadMark entirely.

Relatedly, resolveSidebarV2CardStatus(shell, { lastVisitedAt: resolveThreadLastVisitedAt(...), wokeAt: threadWokeAt(...) }) is repeated three times: the Sidebar summary, ThreadStatusMark, and rankSpaceTabs. The tab copies read new Date() in render while the sidebar uses its snoozeNow tick, so a tab and its card can briefly disagree on "woke". One resolveThreadCardStatus(shell, localVisitedAt, now) helper fixes both.

5. Copy-paste across the new spaces files

• The filled-caret SVG (M2.71 4.75H11.29L7 9.04Z) now exists in 4 places: the status header, the space header, the Threads row, and SidebarV2SpaceCaret. SidebarV2SpaceCaret was added in this PR but isn't reused by the other two new copies. Give it a className and use it everywhere.
• The space PR query (projectIdsByEnvironment → EnvironmentQueryTarget[] → usePullRequestList → filter by spaceHasProject → sort by updatedAt) is duplicated almost line-for-line in SpaceOverview.SpacePullRequests and ChangelogList. Extract useSpacePullRequests(space, state, limit).
• Route search objects are duplicated: "space's open PRs" (SidebarV2SpaceLinkRows and SpaceOverview), "one PR" (SpaceOverview and ChangelogPage), plus /scheduled?space= and /changelog?space=. One small spaceRoutes.ts keeps the "fresh view, not saved filters" decision in one place.
• useSpaceOfProject re-implements spaceHasProject inline, in the same file.
• SpaceOverview imports ThreadStatusMark / useThreadProvider from the 531-line SpaceThreadTabs.tsx. Move the shared thread-presentation bits into their own module so the overview doesn't depend on the tab row.

6. SpaceTabRow orchestration is more indirect than it needs to be

• onOpenHome is passed in by both callers (ChatView and SplitSpaceTabRow) only to be wrapped again in useOpenSpaceHome(space.key, props.onOpenHome). Sidebar does the same with a () => handleNewThreadInProject(...) closure. The "pass a fallback callback" API is the smell. Let useOpenSpaceHome own the fallback (call useNewThreadHandler with the space's representative ref) and take a space. That deletes the onOpenHome prop, the openNew parameter and both caller closures.
• Tab persistence serializes sets to "\n"-joined strings (openable, closedSignature) so they can serve as effect deps, then splits them back apart. Two effects reconcile one stored list. One pure reconcileSpaceTabs(keys, { opened, closed }) in spaceTabs.ts (unit-tested with the others) plus one effect is simpler and avoids the string round-trip.

Smaller

• useSpaceThreadsExpanded stores an expanded set through useSidebarV2CollapsedKeys. Rename the generic hook (it's a persisted key set) rather than reading it backwards.
• buildActiveThreadSections gains an optional keepEmptyGroups?: boolean. Fine as a param, but make it required (or fold it into the spaces branch's own builder) so the default isn't an implicit second mode.
• The forkSpaces.test.ts docblock says the chat header draws the tabs "either side of its breadcrumb". The tabs moved to ChatView / SplitThreadPanes, and the test itself now asserts ChatHeader has no fork-spaces fence. Update the comment.

Reviewed commit: 216bce6a6c1d513e199afc9b8572d77fcbf1759a.

[NoahHendrickson]

This mode flag (plus four space-only optional props) turns the header into two components behind space ? … : … at nearly every element. Can we split out a SidebarV2SpaceHeader with required props and share only the actions cluster? See the review summary, item 1.

[NoahHendrickson]

Done in a82425f. New custom/spaces/SidebarV2SpaceHeader.tsx takes required project, active, onOpen and summary props. The project header is back to its pre-PR shape. Both share SidebarV2SectionActions (the menu and plus cluster, exported from the header file so its pinned strings stay put); the space header passes it pill buttons. The two headers share no mode flag.

[NoahHendrickson]

This is the second projectGroups.find for this header (spaceProject below repeats it), and the fifth UNGROUPED_PROJECT_KEY guard. One precomputed spaceSections.get(header.projectKey) from spaceSidebar.ts would replace this, spaceProject, the two summary Maps, and spaceThreadsFolded. See the review summary, item 2.

[NoahHendrickson]

Done in a82425f. buildSpaceSections in spaceSidebar.ts returns Map<projectKey, { group, summary, openPullRequests, threadsFolded }> and leaves out the unresolved section. The render does one spaceSections.get(header.projectKey), and the fold filter and afterOpenSection read the same map. That removes both projectGroups.find calls, both summary Maps, spaceThreadsFolded, and the UNGROUPED_PROJECT_KEY guards. Unit tests added.

[NoahHendrickson]

This re-infers the grouping from DOM shape with a querySelector per animated item. Sidebar already knows grouping: put data-fork-grouping on the list and read that here and in theme.custom.css (which repeats ul:has(> li[data-fork-space-header]) about a dozen times).

[NoahHendrickson]

Done in a82425f. The list ul carries data-fork-grouping={grouping}. theme.custom.css keys off ul[data-fork-grouping="spaces"], and the animation plugin reads the parent's attribute instead of running a querySelector.

[NoahHendrickson]

This renders two carets and hides one with CSS. A ternary in Sidebar.tsx that renders only the one we want removes this rule.

[NoahHendrickson]

Done in a82425f. The shelves render spacesGrouped ? <SidebarV2SpaceCaret> : <ChevronDownIcon>. The hairline and the Snoozed ink are set in TSX too, so the span.h-px, span:first-child and hide-the-chevron rules are gone.

[NoahHendrickson]

The tray radius matches Tailwind class names on the card (.rounded-[16px], .rounded-full, .rounded-md). Any radius tweak on the card silently breaks this. Can the card expose its radius as a CSS variable instead?

[NoahHendrickson]

Done in a82425f, slightly differently. The tray is an ancestor of the cards, so it can't read a variable set on them (custom properties only inherit downward). Instead the pair row gets its cards' ThreadRowShape from threadRowShape() and stamps data-fork-row-shape; the CSS keys off that, not Tailwind class names. The radii sit next to a comment pointing at THREAD_ROW_RADIUS.

[NoahHendrickson]

This, SPACE_MARK_STATUS in SidebarV2SpaceRows, and TAB_RANK_BY_KIND re-encode the card status ladder by hand (and the labels already differ from the card's). Can we derive the marks from the card's own topStatus and drop SpaceThreadMark?

[NoahHendrickson]

Done in a82425f. summarizeSpaceThreads takes each card's own topStatus and dedupes by mark and tone, so labels and tones come from sidebarV2CardStatus. SPACE_MARK_STATUS and the hand-written mark union are gone; only a display order remains. TAB_RANK_BY_KIND stays on purpose: it's the tab order you asked for (needs you, done, working, monitoring, idle), which isn't the card ladder. The tab row and the overview now compute status through one threadCardStatus helper in the new spaceThreadMarks.tsx.

[NoahHendrickson]

This target-building, filter and sort block is duplicated almost verbatim in ChangelogPage.tsx:61. Extract useSpacePullRequests(space, state, limit).

[NoahHendrickson]

Done in 7ff76e6: useSpacePullRequests(space, state, limit) in spacePullRequests.ts, used by the overview and the Changelog. It also dedupes per environment.

[NoahHendrickson]

onOpenHome comes in from both callers only to be wrapped as useOpenSpaceHome's fallback. If useOpenSpaceHome owned the new-thread fallback, this prop, the openNew parameter, and the closures in ChatView, SplitSpaceTabRow and Sidebar would all go away.

[NoahHendrickson]

Done in a82425f. useOpenSpaceHome() owns the fallback: it calls useNewThreadHandler itself, in the caller's project when the space has it, else the space's representative. The onOpenHome prop, the openNew parameter and the closures in ChatView, SplitSpaceTabRow and Sidebar are gone.

[NoahHendrickson]

Serializing to \n-joined strings for effect deps and splitting back is a workaround. One pure reconcileSpaceTabs(keys, { opened, closed }) in spaceTabs.ts plus a single effect would be clearer and testable alongside the existing spaceTabs tests.

[NoahHendrickson]

Done in a82425f. New pure reconcileSpaceTabs(keys, { opened, closed }) in spaceTabs.ts returns the same list when nothing changes. One effect writes only when the result differs by identity. Tests added; the string round-trip is gone.

[NoahHendrickson]

Reviewed commit 216bce6a6c1d513e199afc9b8572d77fcbf1759a against base e63be3e7f92f64f7e095131a6ec6b39442ea3dda. Found three issues, detailed inline.

Validation: the focused Spaces, sidebar grouping/animation, scheduled-page logic, and Spaces guard tests passed (7 files, 71 tests); the web typecheck passed. Review used source inspection and focused checks; no browser verification was performed.

[NoahHendrickson]

[P2] Keep older unsent drafts reachable in Spaces

This removes every draft, although Home can reopen only the single draft currently mapped to the logical project. For example, type a prompt into a space's draft, click that space header's + to create another draft, and navigate away: useNewThreadHandler replaces the logical-project mapping while setLogicalProjectDraftThreadId deliberately retains the older draft containing text. Home now opens the newer draft, this filter hides the older one, and the tab strip reads server shells only, so the original prompt has no recovery entry within Spaces. Keep non-Home drafts visible or provide a way to select all retained drafts.

[NoahHendrickson]

Fixed in 7ff76e6. Spaces now hides only each logical project's current Home draft (logicalProjectDraftThreadKeyByLogicalProjectKey). An older draft the Home has moved on from stays listed as a draft card, so nothing written is stranded.

[NoahHendrickson]

[P2] Include selected split threads from outside the focused space

A supported split can contain threads from two different logical projects, but this query loads only the focused space's member projects. The later selectedKeys filter cannot add a shell absent from that query, and resolveSpaceTabs skips active keys missing from its thread map. Pair a thread from project A with one from project B: while A is focused, B has no tab or tab close/menu actions, and focusing B makes A disappear instead. Load the selected refs independently and merge them with the space shells so both on-screen panes remain represented.

[NoahHendrickson]

Fixed in 7ff76e6. SplitSpaceTabRow passes both panes' own shells as onScreenShells, and SpaceTabRow merges them with the space's shells. A partner from another space keeps its tab, close, and menu.

[NoahHendrickson]

[P2] Avoid applying the window offset to header-relative controls

With Spaces enabled and an inline right panel open, ChatView renders threadPanelHeaderControl inside its position: relative chat header. That control is position: absolute with top: var(--workspace-controls-top), so it also inherits this new 2.75rem offset. The tab row has already moved the header down by 2.75rem; adding the offset again places the thread-details toggle below the header, over the chat body. Apply the extra offset only to viewport-positioned controls, keeping controls positioned relative to the header at its own top.

[NoahHendrickson]

Fixed in 7ff76e6. The absolute header control (threadPanelHeaderControl) gets --workspace-controls-top reset under the tab row. Only the window-fixed controls take the 2.75rem drop.

[NoahHendrickson]

Code review of 216bce6a6c1d513e199afc9b8572d77fcbf1759a (Claude Code /code-review high, findings checked by hand against the source).

Correctness

1. Scratch space Home never resumes its draft or lights its header (space key vs. draft logical key mismatch). spaceHome.ts
2. Archived/deleted threads' tabs are never pruned from storage and come back on unarchive. SpaceThreadTabs.tsx
3. In a split, the trailing pane's fixed panel controls cover the shared tab row. theme.custom.css
4. A split whose focused pane is a draft shows the partner's space. SpaceThreadTabs.tsx
5. PRs are duplicated per environment in Home's PR sections and the Changelog. SpaceOverview.tsx / ChangelogPage.tsx
6. Automations card shows one Loading/empty row per environment. SpaceOverview.tsx

Performance
7. The tab row (and Home's thread list) subscribe to non-quiet shells and the whole visited map, so they re-render per streamed token.

Minor

• Changelog week keys/labels lack a year.
• Home's Threads section has no SECTION_LIMIT slice or link through, unlike the other sections, so a busy space pushes PRs/automations far below the composer.
• Duplication: the env→projectIds PR target builder is copy-pasted between SpacePullRequests and ChangelogList; the filled caret SVG is inlined in SidebarV2SpaceThreadsRow instead of reusing SidebarV2SpaceCaret; spaceSidebar.ts redefines isAnyKey from sidebarV2ProjectGrouping.ts.

Items 3 and 4 are reasoned from the code and not reproduced in a client. Nothing was run.

🤖 Generated with Claude Code

[NoahHendrickson]

Scratch space never resumes or lights its Home. Space keys come from buildProjectGroups({ groupScratchProjects: true }), so the Scratch space's key is SCRATCH_PROJECT_SCOPE_KEY. useHandleNewThread stores the draft under deriveLogicalProjectKeyFromSettings(project, settings) with groupScratchProjects off, i.e. the scratch project's own key.

Result: type into the Scratch space's Home, click away, click the space name (or the Home tab / plus) → getDraftSessionByLogicalProjectKey(spaceKey) is null, so it calls openNew instead of resuming the written draft. The same mismatch keeps spaceActive (Sidebar.tsx:5313, activeDraftThread.logicalProjectKey === header.projectKey) from ever lighting the Scratch header. Look the draft up by the space's member project refs (or derive the key with groupScratchProjects: true on both sides).

[NoahHendrickson]

Fixed in 7ff76e6. useOpenSpaceHome takes the space and finds its Home among the drafts whose project is a member of the space. The header's lit state uses the same membership test (isSpaceDraft). Scratch now resumes and lights.

[NoahHendrickson]

Archived tabs off screen are never pruned. filterSidebarV2VisibleThreads drops archivedAt !== null shells before resolveSpaceTabs runs, so an archived thread that isn't selected never reaches byKey, never lands in closedKeys, and its stored key is treated as "another space / not loaded yet". The closed: … || shell.archivedAt !== null branch only fires for the thread on screen.

Repro: open A as a tab, navigate to B, archive A from the sidebar. A's tab disappears, but its key stays in t3code:fork:space-tabs:v1; unarchiving A later brings the tab back unasked. Deleted threads behave the same. Keys pile up until the cap evicts live tabs. Computing closed over all of the space's shells (before the visibility filter) would fix it.

[NoahHendrickson]

Fixed in 7ff76e6. closed is computed over all of the space's shells: archived, settled, or hidden and not on screen. Stored keys for those are pruned. Deleted threads have no shell, so they still wait for the cap; that's left as a follow-up.

[NoahHendrickson]

Split view: trailing pane's panel controls sit on top of the shared tab row. This drop only applies to [data-chat-column]:has(> [data-fork-space-tab-row]). In a split, SplitSpaceTabRow is rendered by SplitThreadPanes as a sibling before the panes, outside every data-chat-column, so each pane keeps --workspace-controls-top: 0. ChatView's panelLayoutControls are fixed top-[var(--workspace-controls-top)] right-[…] (ChatView.tsx:8516), so they render at the window's top-right over the 44px tab row, covering the plus / last tabs and taking their clicks, and no longer line up with the pane headers below. Reasoned from code, not checked in a client.

[NoahHendrickson]

Not reproducible: in a split, each pane contains its own fixed controls. Measured in the dev app with a split open: both [data-workspace-titlebar-controls] sit at y=44, the top of each pane's header, below the 44px tab row (x 679–803 and 1184–1308). They do not overlap the shared row.

[NoahHendrickson]

Wrong space when the focused split pane is a draft. A draft has no thread shell, so focusedShell is null and shell falls back to the partner's. If the draft belongs to project X and the partner thread to project Y, the row draws Y's tabs, lights Y's Home (homeActive is true via focusedIsDraft), and the plus/Home open Y's draft while the user is composing in X. The focused draft's project is available from the composer draft store (getDraftSessionByRef / the draft session's project ref) and should win.

[NoahHendrickson]

Fixed in 7ff76e6. SplitSpaceTabRow names the row after the focused pane: its shell, else its draft session (getDraftSessionByRef), and only then the partner.

[NoahHendrickson]

PRs are listed once per machine in a multi-environment space. A space is explicitly "a repository checked out on several machines", and the targets query every member environment for the same repository. mergePullRequestLists concatenates per-environment answers without deduping, so Open pull requests / Recently merged here (and the Changelog at ChangelogPage.tsx:84) show each PR twice when the repo is on, say, the local Mac and a remote host. The React keys include environmentId so nothing warns. The sidebar's spaceOpenPullRequests already dedupes by host/repository#number; these lists should too (before the SECTION_LIMIT slice, so duplicates don't eat the limit).

[NoahHendrickson]

Fixed in 7ff76e6. New useSpacePullRequests / spacePullRequestEntries in spacePullRequests.ts filter by the space, sort newest first, and dedupe by host/repository#number before the section limit. Home's two PR sections and the Changelog share it. Test added.

[NoahHendrickson]

Duplicated placeholder rows. SpaceAutomations renders once per environment (line 68), and each instance returns its own Loading… / No automations.. A two-environment space with no automations shows "No automations." twice; with tasks on one env only, the list gets a stray "No automations." from the other. Fetch per environment but decide the empty/loading state once in the parent.

[NoahHendrickson]

Fixed in 7ff76e6. Each environment draws only its rows, or one pending row while it loads (only the first pending row shows). A single only: empty row stands for the whole section.

[NoahHendrickson]

Perf: the tab row re-renders on every streamed token in the space. useThreadShellsForProjectRefs is the non-quiet shell list, and the row also subscribes to the whole threadLastVisitedAtById map. Each update reruns the visibility filter, the status resolution per tab, rankSpaceTabs, and the signature joins, in the chat column while an agent streams. spaceProjects.ts deliberately avoids exactly this ("reading every thread shell … would re-render them on every streamed token"). Worth a quiet selector (the sameApartFromStreaming approach used by quietThreadShellAtom) or a memoized derived atom for the row's inputs. SpaceThreads in SpaceOverview has the same shape.

[NoahHendrickson]

Declining for this PR. Upstream's BranchToolbar subscribes to the same non-quiet useThreadShellsForProjectRefs in the same chat column. A quiet multi-project variant needs a new atom in packages/client-runtime, which is shared code outside this client-only fork change. Worth a follow-up that fixes both.

[NoahHendrickson]

Nit: week sections are keyed by week.label ("Week of Oct 5"), which has no year. If the 100 merged PRs span more than a year and two Mondays share a date, React gets a duplicate key and the reader sees two identical headings. Key by week.start, and consider adding the year to labels outside the current year.

[NoahHendrickson]

Fixed in 7ff76e6: weeks are keyed by their Monday (week.start). Adding the year to old labels is left as a follow-up.

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

⚠️ This PR changes transfer ceilings:

• Codex Live turn WebSocket decoded: 29.3 KiB → 24.4 KiB
• Claude Live turn WebSocket decoded: 29.3 KiB → 24.4 KiB

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	5.0 KiB	5.0 KiB	+62 B (+1.2%)	6.8 KiB	✅
Codex	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Codex	Live turn WebSocket wire	1.2 KiB	1.2 KiB	+62 B (+5.1%)	2.0 KiB	✅
Codex	Live turn WebSocket decoded	20.9 KiB	21.6 KiB	+715 B (+3.3%)	24.4 KiB	✅
Codex	Live turn messages	2	2	0 (0.0%)	8	✅
Claude	Total thread wire	5.0 KiB	5.1 KiB	+67 B (+1.3%)	6.8 KiB	✅
Claude	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Claude	Live turn WebSocket wire	1.2 KiB	1.3 KiB	+67 B (+5.5%)	2.0 KiB	✅
Claude	Live turn WebSocket decoded	21.2 KiB	21.9 KiB	+727 B (+3.3%)	24.4 KiB	✅
Claude	Live turn messages	2	2	0 (0.0%)	8	✅

Baseline: 6ec3228 · PR result: 838c9a2 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.