fix(clients): show feedback results in composer banners

[juliusmarminge]

/feedback inserted synthetic user and assistant messages into the conversation. It now shows upload progress and the result beside the composer, with Copy ID and dismissal controls. This applies to web, desktop, and mobile; submitting feedback no longer scrolls the web conversation.

Verification: 140 focused tests passed, plus web, mobile, and client-runtime typechecks. Targeted lint passed with existing warnings in the large chat screens. Browser verification covered upload progress, success, draft preservation, and dismissal. Native mobile was typechecked, not simulator-tested.

The captures use the actual base (98469159dd9) and head (7bfbaf327ff), identical disposable fixture data, and a 1440 × 1000 viewport. The feedback RPC was intercepted with a test response; no conversation was uploaded to OpenAI.

Before:

After:

Upload, draft preservation, and dismissal:

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/9d357eeb3b9da60c/feedback-flow.mp4

CI passed on 7bfbaf327ff. No unresolved review findings. Macroscope approvability finished neutral: its eligibility verdict was “Would Approve,” but correctness review was unavailable because the workspace reached its monthly spending limit. Automated review completion remains unavailable.

Model: GPT-6. Harness: Codex.

[macroscopeapp]

Approvability

Verdict: Would Approve

Macroscope's review found this PR approvable — This is a focused presentation fix that moves existing feedback upload statuses into the established composer-banner UI on web and mobile while preserving the underlying submission flow. The change is isolated, tested at the shared notice/state layer, and introduces no schema, deployment, security, billing, default, or static-analysis configuration changes.

Not approved because:

• Monthly spending limit reached (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

[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	+14 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	+2 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+12 B (+0.2%)	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.6 KiB	13.5 KiB	−17 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.1 KiB	7.0 KiB	−7 B (−0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−10 B (−0.2%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.8 KiB	57.8 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	8	8	0 (0.0%)	21	✅

Baseline: 9846915 · PR result: 7bfbaf3 · 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.9 KiB
• Claude decoded thread snapshot: 114.6 KiB

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