Steps to replicate the issue (include links if applicable):

• From the CX unified dashboard, using a desktop computer, select a draft translation
• From the confirmation screen, select "Continue translation"
• From the desktop translation editor, refresh the page

What happens?:

• a "editor_close" event is logged but it's invalid because published_revision_id is formatted as string
• a "editor_open" event is logged but it's invalid because published_revision_id is formatted as string

What should have happened instead?:

• a valid "editor_close" event is logged with published_revision_id formatted as a number
• a valid "editor_open" event is logged with published_revision_id formatted as a number

Software version (on Special:Version page; skip for WMF-hosted wikis like Wikipedia):

Other information (browser name/version, screenshots, etc.):

Derived Requirement

Ensure that the .published_revision_id field in the CX unified dashboard instrumentation is logged as an integer. Both editor_open and editor_close events must include published_revision_id formatted as a number, not a string, to ensure validity of the events.

Test Steps

Test Case 1: Validate published_revision_id is an integer on editor open

1. Open the CX unified dashboard on a desktop computer.
2. Select a draft translation.
3. On the confirmation screen, select "Continue translation".
4. Open the browser developer console or use instrumentation logs to capture events.
5. ✅❓❌⬜ AC1: Confirm that the editor_open event is logged and published_revision_id is formatted as a number (integer), not a string.

Test Case 2: Validate published_revision_id is an integer on editor close

1. In the desktop translation editor, refresh the page or close the editor.
2. Capture the instrumentation logs for the editor_close event.
3. ✅❓❌⬜ AC2: Confirm that the editor_close event is logged and published_revision_id is formatted as a number (integer), not a string.

QA Results - TestWiki