feat(website): Edit individual accession on revise page using form

[tombch]

Summary

• Adds a tab to the revise page to 'Revise individual sequence entry using a form'.
• This displays a search bar, where a user can enter the accession (optionally with version) of the sequence entry they want to revise. Guidance on finding the correct sequence entry from the 'released sequences page' is also provided, in inspiration from feat(website): Add tab on revise page pointing to per-sequence revise button #6504.
• Once a valid accession (and optional version) is entered, renders the existing EditPage component and form, populating the form with the metadata from the get-data-to-edit endpoint, fetching data for the latest version of the sequence entry unless a specific version was provided.
• Updates the existing 'Revise sequence' button to redirect to this page with the accession and version filled in.
• Adds a warning when a user is attempting to revise from a version which is not the latest.
• Updates the naming of the 'Submit' button in the EditPage - now displays either Submit edits and proceed to Approval or Upload and proceed to Approval depending on whether the user is editing/revising.

Screenshot

Revising from an earlier version:

PR Checklist

• All necessary documentation has been adapted.
• The implemented feature is covered by appropriate, automated tests.
• Any manual testing that has been done is documented (i.e. what exactly was tested?)

🚀 Preview: https://edit-on-revise-page.loculus.org

[theosanderson]

@theosanderson-agent inspired by this try making a version that has this tab but where this tab just has docs information that tells users that there is a revise button at the bottom of each of their sequences on the sequence details page, and which links to "my sequences" to allow them to browse. Make a separate PR.

[theosanderson-agent]

Opened #6504 as an alternative: same tabbed layout, but the "Revise individual sequence entry using a form" tab just shows a short info panel that points users to the Revise this sequence button under Sequence management on each sequence details page, plus a button linking to My sequences for browsing. No accession lookup or embedded EditPage in that variant.

[claude]

Claude finished @tombch's task in 4m 1s —— View job

---

Code Review

• Gather context (read changed files, diff against origin/main)
• Understand the request (code review requested)
• Review code quality, security, performance, testing, docs
• Post inline comments for actionable issues
• Post final summary review

I reviewed the diff (origin/main...HEAD), focusing on the new IndividualRevisionForm, the RevisionForm/DataUploadForm routing changes, and SubmissionRoute.ts. Two inline comments posted:

• website/src/routes/SubmissionRoute.ts:82 — accessionVersion is concatenated into the URL without encodeURIComponent, which can break the query string or allow parameter injection if it contains reserved characters.
• website/src/components/Submission/RevisionForm.tsx:42 — the action === 'revise' + inputMode === 'form' branch in DataUploadForm/FormOrUploadWrapper is now unreachable dead code, since RevisionForm always routes 'form' to the new IndividualRevisionForm.

General observations

• Authorization: Confirmed the backend's get-data-to-edit endpoint already rejects accessions that don't belong to the caller's group (GetDataToEditEndpointTest.kt), so letting users type an arbitrary accessionVersion client-side isn't a new security hole — the group check happens server-side and the form surfaces the resulting error correctly.
• URL state syncing: window.history.replaceState usage in IndividualRevisionForm follows the same pattern used elsewhere in the codebase (e.g. useStateSyncedWithUrlQueryParams.ts), so this is consistent.
• Component reset on new search: Keying EditPage on `${data.accession}.${data.version}` is a nice touch — it correctly remounts the form state instead of leaking edits between different searched sequences.
• Testing: No automated tests were added for the new IndividualRevisionForm component (the parsing of accessionVersion input, and the distinction between a parse error vs. a backend/API error). The PR description already flags this itself ("heavily clauded ... would need some work"). Given this component has non-trivial logic (input parsing, URL syncing, conditional rendering of EditPage), some basic tests (e.g. valid/invalid accession input, API error rendering) would be valuable before merging.
• Everything else (routing changes in revise.astro/submit.astro, routes.ts, EditPage.tsx button/label changes, SequenceDataUI.tsx) looked correct and consistent with existing conventions.

Note: I was unable to run npm run check-types / CI=1 npm run test in this sandbox (commands required approval that wasn't available), so please make sure those pass per the website AGENTS.md checklist before merging.

[anna-parker]

When I try searching for an accession that does not exist the spinner keeps spinning for a long period and I see that the page is doing a lot of network calls with errors (probably still trying to find the accession):

Screen.Recording.2026-07-06.at.09.34.53.mov

I find this a bit odd

[anna-parker]

amazing! I just tested this out and it feels really smooth!