[teamleaderleo]

Summary

Takes back #22819: it merged at ef6e1b2 without no SHIP review receipt on the head.

Opened by merge-audit (leo-workspace tools/merge_audit.py), which never merges it. To keep #22819 instead, add the missing evidence for ef6e1b2 on #22819 (an independent review's Review (subagent, correctness first): SHIP at <head> comment, a green compile, a risk tier; for a compile the router skipped, land-now from a maintainer); the next audit pass then closes this PR. Otherwise review and land it.

Changelog

none

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Reverts #22819, so the agent chat pane's bottom stack (composer, questions, notices, queue) is no longer a no-scroll zone. A wheel or trackpad scroll over those parts now scrolls the transcript again, as in the Claude and Codex apps; parts that scroll themselves (a long prompt, the queue, a menu) keep the wheel at their ends. Removes the overscroll-behavior: contain rule and the composer's no-scroll special case, and updates the pass-through tests.

^{Written for commit 62390d3. Summary will update on new commits.}

[github-actions]

cmux status _{(one comment, edited in place; each line is updated by the job that owns it)}

Review 62390d3: HQ feed card · gallery before/after runs · checks

App of this head (app.zip, kept 1 day)

gh workflow run reload-build.yml -R manaflow-ai/cmux --ref feat-cmux-next -f tag=pr23136 -f ref=revert/pr-22819 -f platform=macos -f backend_mode=local

Yours to fix: agent-pane-wheel-pass-through.test.ts (a file this PR changes), agent-pane-wheel-pass-through.test.ts (a file this PR changes). Seen on other PRs too (likely flaky): agent-pane-queue-steer.test.ts, composer-location-strip.test.ts, composer-location-strip.test.ts and 18 more.

CI failed on 62390d394b (run 39562077267 attempt 1): 4 code, 1 unknown.

Job	Verdict	Why
web / react-apps-check (2)	code	a web test failed
web / react-apps-check (3)	code	a web test failed
web / react-apps-check (4)	code	a web test failed
web / react-apps-check (1)	code	a web test failed
web / react-apps-check	unknown	no known signature; failed step: Check webview test shards

Failures:

• seen on other PRs agent-pane-queue-steer.test.ts queued and steering prompts > the queue takes its own place in the stack: nothing is cut off or draw...: failed (job)
• seen on other PRs composer-location-strip.test.ts the chat composer at 420 px: the strip's marks line up with the prompt's edges: failed (job)
• seen on other PRs composer-location-strip.test.ts the chat composer at 760 px: the strip's marks line up with the prompt's edges: failed (job)
• seen on other PRs composer-mention.test.ts @ then letters lists the chat's matching files and Return writes the path: failed (job)
• seen on other PRs composer-mention.test.ts after picking a path markdown escapes, typing on leaves the picker closed: failed (job)
• seen on other PRs composer-mention.test.ts @proje lists other chats, then folders, then the chat folder's files: failed (job)
• seen on other PRs composer-mention.test.ts a chat named for a long prompt does not take @app from the file: failed (job)
• seen on other PRs composer-mention.test.ts a bare @ lists the most recent other chats: failed (job)
• seen on other PRs composer-mention.test.ts an @ inside a word opens nothing and asks the host for nothing: failed (job)
• yours agent-pane-wheel-pass-through.test.ts chromium > the wheel over a long draft stops at its ends and moves nothing else: failed (job)
• ... 13 more in the job logs

Matched log lines

web / react-apps-check (2): (fail) queued and steering prompts > the queue takes its own place in the stack: nothing is cut off or drawn over [1582.09ms]
web / react-apps-check (3): (fail) @ then letters lists the chat's matching files and Return writes the path [2219.10ms]
web / react-apps-check (4): (fail) chromium > the wheel over a long draft stops at its ends and moves nothing else [4110.29ms]
web / react-apps-check (1): (fail) with no running call, Ctrl-B stays the composer's and asks nothing [1085.73ms]

Not re-run automatically: web / react-apps-check (2), web / react-apps-check (3), web / react-apps-check (4), web / react-apps-check (1), web / react-apps-check are not machine failures.

Written by scripts/ci/classify_failures.py (ci-failure-attribution.yml); signatures are its SIGNATURES table. A machine verdict is the runner's fault, not this PR's; yours means the failing file is one this PR changes, also red on main that main's latest full suite fails the same way, seen on other PRs that it failed on another pull request's run lately.

red: web / Web status; NEW: green on the base 1e2bcb7; do not merge until green; see lane-rules
red: web / react-apps-check; no finished base run on 1e2bcb7 to compare; do not merge until green; see lane-rules
red: web / react-apps-check (1); no finished base run on 1e2bcb7 to compare; do not merge until green; see lane-rules
red: web / react-apps-check (2); no finished base run on 1e2bcb7 to compare; do not merge until green; see lane-rules
red: web / react-apps-check (3); no finished base run on 1e2bcb7 to compare; do not merge until green; see lane-rules
red: web / react-apps-check (4); no finished base run on 1e2bcb7 to compare; do not merge until green; see lane-rules

CI fast guards failed on 62390d394b (https://github.com/manaflow-ai/cmux/actions/runs/39562077267). It does not block the merge; a red guard merged into main breaks it for every open PR.
The log named no failed step; see the run.

Agents: python3 scripts/ci/guard_attribution.py fix applies the mechanical fixes locally.

[blacksmith-sh]

Found 27 test failures on Blacksmith runners:

Failures

Test	View Logs
.github/workflows/ nightly-next-tick.yml: triggers on the display names ['cmux-next', 'cmux-tui artifacts' ] and declares no SOURCE_WORKFLOW_PATHS, so renaming any of those workflows stops this one from ever triggering and nothing reports it	View Logs
main.IOSWiring.test_test_ios_macos_jobs_take_the_runner_jobs_pool/ test_test_ios_macos_jobs_take_the_runner_jobs_pool	View Logs
main.SideLanes.test_a_completed_failed_blacksmith_retry_is_not_watched_again/ test_a_completed_failed_blacksmith_retry_is_not_watched_again	View Logs
main.SideLanes.test_a_real_failure_on_cmux_next_attempt_two_is_not_rescued/ test_a_real_failure_on_cmux_next_attempt_two_is_not_rescued	View Logs
cmux-next.yml job swift-canary step 'Report the build fleet compile verdict' uses the t oolchain (swift) before scripts/select-ci-xcode.sh runs	View Logs
debug info {'CMUX_SWIFT_SANITIZE': 'address', 'CMUX_SWIFT_TEST_DEBUG_INFO': 'none'}: 's wift --version' lacks '-debug-info-format none'/ debug info {'CMUX_SWIFT_SANITIZE': 'address', 'CMUX_SWIFT_TEST_DEBUG_INFO': 'none'}: 's wift --version' lacks '-debug-info-format none'	View Logs
debug info {'CMUX_SWIFT_SANITIZE': 'address', 'CMUX_SWIFT_TEST_DEBUG_INFO': 'none'}: 's wift package resolve --package-path Packages/macOS/Pkg --scratch-path Packages/macOS/ Pkg/.build-sanitize-address' lacks '-debug-info-format none'	View Logs
debug info {'CMUX_SWIFT_SANITIZE': 'address', 'CMUX_SWIFT_TEST_DEBUG_INFO': 'none'}: wa nt one build and two suites: ['swift package resolve --package-path Packages/macOS/ Pkg --scratch-path Packages/macOS/Pkg/ .build-sanitize-address', 'swift --version', 'swift build --build-tests -c debug -debug -info-format none --sanitize=address --scratch-path Packages/macOS/Pkg/ .build-sanitize-address -Xlinker -no_compact_unwind --package-path Packages/macOS/ Pkg', 'swift test -c debug -debug-info-format none --sanitize=address --scratch-path Pa ckages/macOS/Pkg/ .build-sanitize-address -Xlinker -no_compact_unwind --package-path Packages/macOS/ Pkg --skip-build --filter ATests', 'swift test -c debug -debug-info-format none --sanit ize=address --scratch-path Packages/macOS/Pkg/ .build-sanitize-address -Xlinker -no_compact_unwind --package-path Packages/macOS/ Pkg --skip-build --filter BTests']	View Logs
debug info {'CMUX_SWIFT_SANITIZE': 'address'}: want one build and two suites: ['swift p ackage resolve --package-path Packages/macOS/Pkg --scratch-path Packages/macOS/Pkg/ .build-sanitize-address', 'swift --version', 'swift build --build-tests -c debug --sani tize=address --scratch-path Packages/macOS/Pkg/ .build-sanitize-address -Xlinker -no_compact_unwind --package-path Packages/macOS/ Pkg', 'swift test -c debug --sanitize=address --scratch-path Packages/macOS/Pkg/ .build-sanitize-address -Xlinker -no_compact_unwind --package-path Packages/macOS/ Pkg --skip-build --filter ATests', 'swift test -c debug --sanitize=address --scratch-pa th Packages/macOS/Pkg/ .build-sanitize-address -Xlinker -no_compact_unwind --package-path Packages/macOS/ Pkg --skip-build --filter BTests']	View Logs
debug info {'CMUX_SWIFT_TEST_DEBUG_INFO': 'dwarf'}: want one build and two suites: ['sw ift package resolve --package-path Packages/macOS/ Pkg', 'swift --version', 'swift build --build-tests -c debug --package-path Packages/ macOS/Pkg', 'swift test -c debug --package-path Packages/macOS/ Pkg --skip-build --filter ATests', 'swift test -c debug --package-path Packages/macOS/ Pkg --skip-build --filter BTests']	View Logs

...and 17 more test failures. View all on Blacksmith

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[teamleaderleo]

Bead cx-f2vz0 created for this PR by the cmux coordinator.

[teamleaderleo]

Owned by composer-scroll-2 on cosmic-gray · session

[teamleaderleo]

Closing: #22819 keeps its change. Its missing evidence is now on it: an independent review's SHIP receipt at the merged head ef6e1b2 (#22819 (comment)). Risk tier risk:normal; webviews only, so no compile applies; the new browser test passed on CI at that head. Nothing to revert.