docs(gui): add Qt6 status page

[Liam-Deacon]

Problem

Issues #9 and #26 require a Qt6 modernization plan and clarity on the current GUI stack.

Solution

• Add a Sphinx page documenting GUI status, Qt6 preference, and the legacy PyQt4 state.
• Wire the page into the main documentation index.

Testing

• Not run (documentation-only change).

Follow-ups

• Decide on the primary GUI stack (C++ Qt6 vs Python PySide6).
• Plan the actual migration of Qt4/PyQt4 code and remove deprecated dependencies.

Summary by Sourcery

Document current GUI technology stack and Qt6 migration plans in the Sphinx docs.

Documentation:

• Add a GUI status documentation page describing Qt6 preference and legacy PyQt4 usage.
• Link the new GUI status page into the main Sphinx documentation index.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/issue-9-26-qt6

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Documents the current GUI technology stack and Qt6 migration direction in Sphinx, and wires the new page into the main docs index.

File-Level Changes

Change	Details	Files
Add a dedicated Sphinx page describing GUI status and Qt6 migration preferences.	Create a new documentation page explaining the current GUI stacks, the preferred move to Qt6, and the legacy PyQt4 situation Document known open questions and follow‑up work around choosing the primary GUI stack and planning migration	doc/gui_status.rst
Expose the new GUI status documentation page from the main docs index.	Update the main Sphinx index to include the GUI status page in the toctree so it appears in the rendered docs navigation	doc/index.rst

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[Liam-Deacon]

Clarifications for #9/#26:

• Which GUI stack should we prioritize for the actual migration (C++ Qt6 vs Python PySide6)?
• Do you want to keep the legacy PyQt4 GUI code for reference, or remove it once a new stack lands?
• Should we add a CI job that toggles WITH_QT=ON to validate Qt6 builds, or keep GUI tests local for now?

[codacy-production]

Codacy's Analysis Summary

0 new issue (≤ 0 issue)
0 new security issue

Review Pull Request in Codacy →

✨ AI Reviewer available: add the codacy-review label to get contextual insights without leaving GitHub.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud