TINYDOC-3526: Suggested Edits API should not be tied to the existence of the suggested edits toolbar button

[kemister85]

Ticket: TINYDOC-3526 (TINYMCE-13256)

Site: Staging

Changes:

• Added release note entry for TINYMCE-13256 to modules/ROOT/pages/8.7.0-release-notes.adoc (Accompanying Premium plugin changes → Suggested Edits): the SuggestedEditsHasChangesUpdate event now fires whenever the hasChanges API value changes, including on review completion.

---

Pre-checks:

• Branch is correctly prefixed (release-note branch)
• modules/ROOT/nav.adoc has been updated (if applicable).
• Files have been included where required (if applicable).
• Files removed have been deleted, not just excluded from the build (if applicable).
• Files added for New product features include a release note entry.
• Major or minor version changes have updated the supported-versions.adoc table.
• Build passes without console errors, warnings, or issues.

[MitchC1999]

Suggested change

Previously, the `SuggestedEditsHasChangesUpdate` event only fired alongside other editor events, such as typing, selecting, or focusing. Completing a review did not fire the event on its own, so the value returned by the `hasChanges` API could become outdated. An integration that used the API through a custom button, rather than the built-in `suggestededits` toolbar button, did not receive an update when a review finished.

Previously, the `SuggestedEditsHasChangesUpdate` event only fired alongside other editor events, such as typing, selecting, or focusing. Completing a review did not fire the event on its own, so the value returned by the `hasChanges` API could become outdated. As a result, any integration that relied upon the API would not receive an update when a review finished.

[MitchC1999]

Suggested change

	In {productname} {release-version}, the `SuggestedEditsHasChangesUpdate` event fires whenever the value returned by the `hasChanges` API changes, including when a review completes. The `hasChanges` API no longer depends on the presence of the `suggestededits` toolbar button, so a custom integration stays in sync with the document state.
	In {productname} {release-version}, the `SuggestedEditsHasChangesUpdate` event fires whenever the value within the `hasChanges` API changes, including when a review completes.