refactor: summary-task-status-scatter

[kacieje]

Description

This PR removes an unused coffee component summary-task-status-scatter. No references to this visualisation could be found for initialisation and it could not be triggered in testing.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Triggering of the component was tested by searching through the code base for references to the component (summary-task-status-scatter and summaryTaskStatusScatter). The component itself (summary-task-status-scatter.coffee) and the visualations template (visualisation.tpl.html were located but no triggers for actual use. Once the changes in this PR were applied, various visualisations were tested and no changes to their functionality were identified.

Testing Checklist:

• Tested in latest Chrome
• Tested in latest Edge
• Tested in latest Safari
• Tested in latest Firefox

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[JeffySam]

The PR removes the CoffeeScript component summary-task-status-scatter, which has been correctly identified as unused. A search of the codebase for both summary-task-status-scatter and summaryTaskStatusScatter confirms that there are no references that initialise or trigger this visualisation. Although the component file (summary-task-status-scatter.coffee) and its associated visualisation template (visualisation.tpl.html) exist, no active usage or entry points were found.

The reasoning for removal is sound, as unused components increase maintenance overhead and add unnecessary complexity to the codebase. Removing this component improves maintainability without impacting existing functionality.

Testing has been clearly described and is appropriate for the scope of the change. After applying the PR, other visualisations were tested and no functional changes or regressions were observed. Cross-browser testing was completed in the latest versions of Chrome, Edge, Safari, and Firefox, providing confidence that the change is non-breaking.

The PR is correctly categorised as a non-breaking bug fix. The checklist has been completed, a self-review was performed, documentation considerations were addressed, and no new warnings were introduced.

Conclusion:
This is a safe, well-tested cleanup change. I see no issues with this PR and support merging it.