- applySuggestion's catch path now restores exactly the keys the apply
  touched, with their original values (or undefined when the key was
  added by this apply). updateBlockAttributes is a partial merge —
  passing currentAttributes alone left newly-added keys stuck on the
  block at their applied value when the server rejected the status
  update.
- MAX_DIFF_LENGTH dropped from 5000 → 2000. Two 2KB strings already
  produce a 4M-cell DP table; 5000² is too costly for an interactive
  sidebar render.
- Add a wordDiff segmentation test covering the in-place replacement
  case.

The merge of trunk's Notes refactor (#77614) into phase-3 ported a
SuggestionActionButtons reference into the new note.js, but that named
export does not exist on phase-3 — only `SuggestionActions` (default)
ships in this phase. Header-slot icon buttons are a downstream
refinement and will arrive in a later phase.

Removes the unused named import and the header-slot usage so the
package build no longer fails with 'No matching export'.

Trunk's new `@wordpress/use-recommended-components` lint rule flags
`__experimentalHStack`/`__experimentalVStack` and (via
`@wordpress/use-import-as`) requires the `__experimentalText`
import to use the `WCText` alias.

Switch HStack/VStack/VisuallyHidden to the `@wordpress/ui` Stack and
VisuallyHidden, rename `Text` → `WCText`, and add the two
suggestion files to the lint suppressions baseline alongside
existing entries (e.g. pagination/index.js) so the deferred
`Text → @wordpress/ui` migration does not block this PR.

…estion

In Suggest mode, `applySuggestion` calls `updateBlockAttributes` to
write the proposed attribute values onto the live block. The store
interceptor was reverting that dispatch the same way it reverts a
user edit, so the comment status flipped to "applied" but the block
content never actually changed. Reject worked because it only saves
the comment status.

Add a ref-based bypass set on the overlay context that the apply
flow can opt into. The interceptor checks the set before diffing,
adopts the current attributes as its new snapshot baseline, and
skips the revert. Clearing the overlay entry resets the per-block
suggestion tracking so a subsequent edit re-baselines from the
post-apply attributes. Outside Suggest mode the interceptor isn't
running and the calls are no-ops.

…tData diffs are detected

Two equality helpers — `isAttributeEqual` in provider.js and
`shallowAttributeEquals` in store-interceptor.js — short-circuited
on `RichTextData` (and similar wrapper) values. RichTextData holds
its content in private class fields, so `Object.keys()` returns an
empty array and the structural compare was vacuously equal regardless
of the underlying text or formatting. The string/object branch also
returned false outright when one side was a plain string (the
JSON-deserialized 'before' from a stored suggestion) and the other a
RichTextData instance from the live store, so content-attribute
diffs registered as "changed" even when nothing had moved.

Fix: when both sides have zero enumerable keys, or when only one
side is an object, fall back to `String(a) === String(b)`. This
preserves equality across the wrapper/string boundary and across
RichTextData instances, so content suggestions are detected and
applied correctly.

…terceptor

In collaborative editing, an applied suggestion lands on the live block
on the accepter's tab and propagates through the sync layer to the
suggester. Without a complement to the accepter-side interceptor bypass,
the suggester's store interceptor sees the incoming attributes as a
drift from its snapshot, reverts them back to baseline, and that revert
round-trips back through sync — undoing the apply on the accepter's
screen a moment after they clicked.

Detect the case explicitly: when every changed attribute on a block
linked to one or more notes matches the after value declared in those
notes' suggestion payloads, adopt the change as the new baseline rather
than reverting. The check is purely local (no comment-status watcher,
no race with the apply dispatch) and only fires when the live store
exactly matches a known suggestion payload.

Tighten shallowAttributeEquals to compare across the wrapper/primitive
boundary so a JSON-decoded after string and a live RichTextData wrapper
read as equal — without it, content suggestions never match and the new
branch never fires.

The suppression entry mirrors the pattern from the broader react-hooks
sweep on add-suggestion-mode and covers four pre-existing ref-write
violations in this file.

…gestionDiff

Document the public action arguments and surface the suggestion-diff
component's input shape, edge cases (MAX_DIFF_LENGTH fallback, wrapper
values), and rendering semantics so reviewers don't have to trace the
helper functions to understand the contract.

…st-mode-phase-3

Remove 17 stale bulk-suppression entries for files that are byte-identical
to trunk (which carries no suppression for them), so the suppressed
violations no longer occur. Resolves the failing "All" lint job which
reported leftover suppressions via --prune-suppressions.