feat(website): show sequence specific filters without requiring an associated segment

[anna-parker]

resolves #5993

Screenshot

tested on preview, integration tests are failing due to issues with pulling the docker images - I will restart them

🚀 Preview: https://allowsequencedatawithouts.loculus.org

[claude]

Claude finished @anna-parker's task in 1m 38s —— View job

---

Code Review

• Gather context
• Review changes
• Post feedback

---

The website logic looks correct. The 'ALL' key is used as a virtual bucket for isSequenceFilter fields that don't have a relatesToSegment value, and they're rendered at the top of the Sequence Filters section before the per-segment content. The guards added to renderSegmentContents (segmentName !== 'ALL') correctly prevent the ReferenceSelector and MutationField from being rendered for that virtual segment (since segmentAndGeneInfo['ALL'] would be undefined anyway, the mutation field guard was arguably redundant but adding it explicitly is clearer).

One thing to be aware of: for single-segment organisms, 'ALL' fields will appear above the single segment's content. Depending on UX intent, this seems fine.

kubernetes/loculus/values.yaml: The isSequenceFilter: true # revert after testing line on hostNameScientific is a testing artifact — left an inline comment. This must be removed before merging.

[theosanderson]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2bfc5b3160

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[maverbiest]

Looks good!

Not blocking, but I personally find the 'ALL' keyword slightly confusing. Would something like 'UNASSIGNED' or 'NO_SEGMENT' be an option?

[anna-parker]

I switched to NO_ASSIGNED_SEGMENT :-)

[anna-parker]

goodness the integration tests are so flaky!