[teamleaderleo]

Two identical attention requests can share the same millisecond timestamp. A stale acknowledgement can then clear a replacement mark. Each new mark now carries a persisted, owner-issued opaque request_id, independent of wall time and row lifetime.

tab-attention-request-id-v1 advertises transactional compare-and-clear: tab.update accepts attention:null with the captured attention_request_id. A stale token is a successful no-op returning the current tab. Invalid guards fail validation. The existing unconditional clear remains compatible for legacy callers; new consumers must require the capability and token and never fall back to timestamp matching or unconditional clearing.

Valid pre-token marks acquire an identity once on store open. The JSON addition remains readable by older builds. Risk: upgrading assigns new identities to legacy marks; clients must invalidate cached tokenless actions. No Swift or FFI ABI change is included. Native consumers require the daemon release advertising this capability. The derived app FFI input list excludes all changed paths, so no app FFI release or binary-target repin applies.

Validation at final head f5502f81b211965630e621060a4d741eea02db9d: Linux run 40954356328 passed the workspace/all-targets compile, all 10 attention tests, resource boundary/spec inventory, both Rust adapter clippy and test commands, MCP cancellation, and all 107 release-notary guards. Independent Sol high whole-diff review and primary integration inspection both returned SHIP at that exact head.

The only focused failure is workspace formatting in two unchanged base files (surface_parity.rs and resource/wire_name_tests.rs). Focused baseline 40956888289 runs the same command on base 6fbb57eb3ff3da62aa1f2443db0213782c1e2c88 and reproduces those exact diffs. It also reproduces the hosted No-SwiftUI diagnostics for HomeChatColorsPanel.swift and HomeChatColorsView.swift; the other continuing checks execute. Neither failure comes from this PR. No native UI or FFI artifact changes are included.

Agent session: agent session

[blacksmith-sh]

Found 1 test failure on Blacksmith runners:

Failure

Test	View Logs
test_live_raw_v12_layout_and_history_contracts_are_exact (test_ir.IrTests.test_live_raw _v12_layout_and_history_contracts_are_exact) (command='new-pane-right')/ test_live_raw_v12_layout_and_history_contracts_are_exact (test_ir.IrTests.test_live_raw _v12_layout_and_history_contracts_are_exact) (command='new-pane-right')	View Logs

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

[github-actions]

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

Review 2d04c81: 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=pr27497 -f ref=lane/attention-request-identity -f platform=macos -f backend_mode=local

red: cmux-next checks (god files, concurrency, crash safety, l10n); base red: the same failure on the base 6fbb57e; does not block

[teamleaderleo]

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

[teamleaderleo]

The conformance adapters' --locked base red is fixed on feat-cmux-next by #27517 (merge c9e4f75); both adapter jobs pass there. Re-running those jobs after the next base update clears them.

[github-actions]

The feat-cmux-next push run https://github.com/manaflow-ai/cmux/actions/runs/40958340569 at c587e68 failed: cmux-next checks (god files, concurrency, crash safety, l10n).
Those jobs last passed at e3d7290. This pull request is one of 2 merged since: #27524, #27497.
If the failure is in your change, fix forward on feat-cmux-next. Pull requests run only the tiers their paths reach (docs/ci/cmux-next-tiers.md); label a batch PR full-ci to run them all before merging.

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4096337330601 (4400b7aaef)
• cmux NEXT nightly 1.0.0-nightly.4096721596601 (e4fc50922c)