POC of a Vue.js-based frontend rewrite (served alongside existing Flutter UI)

[Vultaire]

NOTE: This is not ready for review! This is a largely vibe-coded POC; the code needs to be properly reviewed and cleaned up before it's ready to be merged, even in its current incomplete form.

Description

This PR (building upon #518) reimplements much of the Flutter UI using Vue.js.

It captures much of the existing UI's functionality for browsing and searching for test runs and issues.

Notable gaps are:

• Issue creation and test attachment rules
• "Reported issues"
• Rerun buttons and other "action" buttons
• Filters don't fully work the same way as the Flutter UI; some changes are intentional, and some details are deltas that still need to be worked through to resolve.
• Styling has changed and was largely auto-generated by the LLM; if we want to move forward with this beyond as a POC, we will probably want to make modifications to make it more in line with the Flutter version.

It can be test-driven by running e.g. podman compose up and connecting to http://localhost/30001/vue_poc/. Note that the trailing / must be there or else it will navigate to the Flutter UI.

This addresses the following concerns:

• Multiple concerns related to the Flutter app rendering as HTML canvas rather than DOM, such as the lack of normal right-clickable hyperlinks.
• Limited developer familiarity with Flutter, instead leveraging the more widely known JavaScript - albeit in this case with a specific JS framework, Vue.js, which does admittedly have its own learning curve but at least remains in the JavaScript space.
• Relatively slow build and rebuild times for Flutter in comparison to JavaScript.

Resolved issues

• Test Observer experimental non-flutter rewrite work

Documentation

At present this is purely a POC, although a fairly highly functional one. It does not interfere with the existing UI and its existance is not yet widely communicated.

Again, for those that want to test drive the UI, just run podman compose up to build and spin up the containers locally and then connect to http://localhost/30001/vue_poc/. This is not a concern for normal users of Test Observer and thus I don't think this is a detail that belongs in the main documentation at this time.

Web service API changes

No API changes.

Tests

• podman compose up
• Connect to http://localhost/30001/vue_poc/ and compare to http://localhost/30001/. (While not at feature parity, the UIs are strikingly close to each other.)

[Vultaire]

This is in draft state, blocking on:

• Moved Flutter sources to "src" subdir and reworked Dockerfile #518
• A personal review of the code here, as this was largely vibe coded and I have not sufficiently reviewed the generated code yet.

[Vultaire]

Initial self-review completed.

[Vultaire]

I "trusted" the LLM with this change when I noted a rendering time delta, but I want to review the Flutter sources here and verify that this is appropriate.

[Vultaire]

The JSON simply has a simple string, e.g. "2026-01-12", for due_date values. Loading to a new Date() works, but it shows the date in local time which, for me, ends up being off-by-one. Using the UTC functions does seem like the right way to handle this.

> date = new Date("2026-01-12")
Date Sun Jan 11 2026 16:00:00 GMT-0800 (Pacific Standard Time)
> date.getDate()
11
> date.getUTCDate()
12