…ssed (#20220)

Summary of the issue:

When nvdaController_speakSsml is called with asynchronous=False, a race condition can cause the call to block indefinitely. onSpeechCanceled was registered inside prefixCallback, a CallbackCommand that runs on the synth thread only after the sequence starts. If speechCanceled fires in the window between queueHandler.queueFunction returning and the synth reaching that CallbackCommand, the signal is missed and markQueue.get() never unblocks.
Description of user facing changes:

No change under normal operation. Fixes a hang that could occur when speech is cancelled immediately after being queued via the controller client.
Description of developer facing changes:

speech.speechCanceled.register(onSpeechCanceled) is now called directly before queueHandler.queueFunction, ensuring the handler exists before any cancel signal can fire. onDoneSpeaking stays in prefixCallback because synthDoneSpeaking fires per sequence — registering it earlier would catch a previous sequence still finishing when priority is Next.
Description of development approach:

Minimal repositioning of one register call. No logic changes.
Testing strategy:

Call nvdaController_speakSsml with asynchronous=False and cancel speech immediately after queuing, repeatedly. Before this fix the call would occasionally hang; after it should always return promptly with ERROR_CANCELLED.

#20225)

<!-- Please read and fill in the following template, for an explanation
of the sections see:

https://github.com/nvaccess/nvda/blob/master/projectDocs/dev/githubPullRequestTemplateExplanationAndExamples.md
Please also note that the NVDA project has a Citizen and Contributor
Code of Conduct which can be found at
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md. NV
Access expects that all contributors and other community members read
and abide by the rules set out in this document while participating or
contributing to this project. This includes creating or commenting on
issues and pull requests.

Please initially open PRs as a draft.
When you would like a review, mark the PR as "ready for review".
See
https://github.com/nvaccess/nvda/blob/master/.github/CONTRIBUTING.md.
-->

### Link to issue number:
<!-- Use Closes/Fixes/Resolves #xxx to link this PR to the issue it is
responding to. -->
None
### Summary of the issue:
The heading level of some magnifier options in the user guide is
incorrect.
### Description of user facing changes:
Fix the heading level error for the magnifier option in the user guide
### Description of developer facing changes:
Fix the heading level error for the magnifier option in the user guide
### Description of development approach:
Document changes
### Testing strategy:
Check the built documentation
### Known issues with pull request:
None
### Code Review Checklist:

<!--
This checklist is a reminder of things commonly forgotten in a new PR.
Authors, please do a self-review of this pull-request.
Check items to confirm you have thought about the relevance of the item.
Where items are missing (eg unit / system tests), please explain in the
PR.
To check an item `- [ ]` becomes `- [x]`, note spacing.
You can also check the checkboxes after the PR is created.
A detailed explanation of this checklist is available here:

https://github.com/nvaccess/nvda/blob/master/projectDocs/dev/githubPullRequestTemplateExplanationAndExamples.md#code-review-checklist
-->

- [x] Documentation:
  - Change log entry
  - User Documentation
  - Developer / Technical Documentation
  - Context sensitive help for GUI changes
- [x] Testing:
  - Unit tests
  - System (end to end) tests
  - Manual testing
- [x] UX of all users considered:
  - Speech
  - Braille
  - Low Vision
  - Different web browsers
  - Localization in other languages / culture than English
- [x] API is compatible with existing add-ons.
- [x] Security precautions taken.

Fixes #19493
Fixes #20110
Fixes #20149
Summary of the issue:

Magnifier zoom, filter and full screen mode were not persisted when set via keyboard gestures
Description of user facing changes:

Persist Magnifier zoom, filter and full screen mode in settings
Description of developer facing changes:

none
Description of development approach:

Settings Synchronization and Immediate Application:

    Added _applyCurrentSettingsToConfigAndRuntime method to MagnifierPanel, which applies the current UI control values to both the configuration and the active magnifier instance, ensuring settings changes are reflected immediately. Immediate updates are now handled for zoom, pan step, filter, fullscreen mode, "true centered", follow focus, and "keep mouse centered" settings.
    The onSave and onDiscard methods now use the new synchronization logic, improving reliability when saving or discarding changes. Initial values are stored and restored as needed.

Magnifier Runtime Updates:

    When toggling filter, fullscreen mode, or zoom, the corresponding runtime setter (setFilter, setFullscreenMode, setZoomLevel) is now called to ensure the running magnifier instance is updated immediately.

Codebase Cleanup and Modernization:

    Removed unused getDefaultFullscreenMode and setDefaultFullscreenMode functions from the config module, a

Testing Improvements:

    The magnifier test setup now explicitly sets default values for zoomLevel and _filterType, improving test reliability and clarity.