fix(web,mobile): fold context compaction under settled turn folds

[maria-rcks]

Note

Written by muse-spark-1.3-contributor-free on behalf of Maria

A settled "Worked for ..." fold left its "Compacted context ..." row visible underneath. Compaction rows now fold with the rest of their turn on web and mobile, and reappear when the fold is expanded. A lone compaction with no other folded work stays visible as before.

Verified with the timeline unit suites on both clients plus typecheck, and with before/after renders of the real timeline component on the same fixture.

Before — compaction leaks out below the collapsed fold:

After — the fold hides the compaction row:

Made with opencode/muse-spark-1.3-contributor-free.

---

Note

Low Risk
Presentation-only timeline folding logic in shared patterns on web and mobile; no auth, data, or API changes.

Overview
Fixes “Compacted context …” rows staying visible below a collapsed “Worked for …” turn fold on web and mobile.

Context compaction is no longer exempt from turn-fold hiding (mobile stops skipping compaction groups when building turn groups; web stops treating compaction like agent-spawn rows that never fold). Compaction entries can be included in hiddenEntryIds and collapse with the rest of the turn when the fold is collapsed, and show again when expanded.

A turn fold is only created when it would hide non-compaction work (hidesNonCompactionWork). If the only hidden entries would be compaction, no fold is emitted so a lone compaction row stays visible, matching prior behavior for compaction-only turns.

On web, post-terminal folding rules still skip trailing work after the terminal assistant message, except compaction rows, which may still fold with the turn.

^{Reviewed by Cursor Bugbot for commit 14fd213. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fold context-compaction entries under settled turn folds in web and mobile

• Removes the early exclusion of context-compaction activity from turn fold calculations in deriveThreadFeedTurnFolds (mobile) and deriveTurnFolds (web), so compaction rows can fold alongside other hidden work in the same turn
• Adds a post-filter guard in both derivations: a fold is suppressed when every hidden entry is context-compaction only, keeping that compaction row visible
• Agent-spawn work entries remain excluded from folds on web
• Behavioral Change: a context-compaction row after a terminal assistant message can now be folded with other work in the same turn; a turn whose only hidden candidate is compaction produces no fold and leaves the row visible

^{Macroscope summarized 14fd213.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.5 KiB	+1 B (+0.0%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	+3 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−2 B (−0.0%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.0 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	8	8	0 (0.0%)	21	✅
Claude	Total thread wire	13.5 KiB	13.8 KiB	+225 B (+1.6%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	−2 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.7 KiB	+227 B (+3.4%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.8 KiB	59.3 KiB	+1.5 KiB (+2.6%)	66.4 KiB	✅
Claude	Live turn messages	8	10	+2 (+25.0%)	21	✅

Baseline: 2152d44 · PR result: 14fd213 · 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: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

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

[macroscopeapp]

Approvability

Verdict: Approved at 14fd213

Macroscope's review found this PR approvable — This is a focused presentation bug fix that folds context-compaction rows into existing settled-turn folds while preserving standalone rows and expansion behavior. It affects only web/mobile timeline rendering and introduces no API, data, provider-execution, security, or infrastructure changes.

^{You can add or adjust custom eligibility rules. Learn more.}