A repository's Settings page moves it to another owner, as the API and terminal already do #10118

A repository admin can now move a repository to another owner from its Settings page. The new tests and the tests around Settings pass, tsc and bun scripts/design-lint.ts are clean, and the branch is pushed.

I didn't run bun scripts/fast.ts: it reports the diff as too broad, so I ran the Settings and transfer test files by name instead. Its exit code printed as 0, but that was the echo after the $(…). I also didn't take the 390px look on the pull, because the sandbox can't run a browser, and I didn't run bun scripts/gate.ts to the end (its output was cut off by the timeout). The forge's check will run the gate; the 390px look still needs someone to take it.

• Settings block: a "Move to another owner" block sits beside Archive in src/web/pages/settings.ts, shown only to an admin. It has one "New owner" field and a "Move" button.
• Confirmation: "Move" opens the existing /-/confirm page, the same step Delete uses. I added a "Move … to another owner?" entry to its table in src/web/pages/search.ts. That page now carries the typed owner through to the final POST.
• Route: POST /:owner/:name/settings/transfer (transferSubmit, registered in src/http/server.ts) calls transferRepository and never touches core. It is same-origin only. Anyone who doesn't administer the repository gets 404. On success it redirects to Settings at the new path with "Moved to owner/name."
• Refusals: a refusal re-renders Settings with the TRANSFER_SAID sentence under the field, the field kept, and the action's status (409, 403 or 422). An owner name that isn't a valid username is treated as an unknown owner.
• Tests and docs: test/repo-transfer-web.test.ts covers the move, all four refusals, the 404 for a reader, a cross-origin post, and that the block is hidden from non-admins. docs/features/repo-transfer.md now names the page.

I added nothing to core/transfer.ts.

Closes #10099

A repository admin can now move a repository to another owner from its Settings page. The new tests and the tests around Settings pass, tsc and bun scripts/design-lint.ts are clean, and the branch is pushed.

I didn't run bun scripts/fast.ts: it reports the diff as too broad, so I ran the Settings and transfer test files by name instead. Its exit code printed as 0, but that was the echo after the $(…). I also didn't take the 390px look on the pull, because the sandbox can't run a browser, and I didn't run bun scripts/gate.ts to the end (its output was cut off by the timeout). The forge's check will run the gate; the 390px look still needs someone to take it.

• Settings block: a "Move to another owner" block sits beside Archive in src/web/pages/settings.ts, shown only to an admin. It has one "New owner" field and a "Move" button.
• Confirmation: "Move" opens the existing /-/confirm page, the same step Delete uses. I added a "Move … to another owner?" entry to its table in src/web/pages/search.ts. That page now carries the typed owner through to the final POST.
• Route: POST /:owner/:name/settings/transfer (transferSubmit, registered in src/http/server.ts) calls transferRepository and never touches core. It is same-origin only. Anyone who doesn't administer the repository gets 404. On success it redirects to Settings at the new path with "Moved to owner/name."
• Refusals: a refusal re-renders Settings with the TRANSFER_SAID sentence under the field, the field kept, and the action's status (409, 403 or 422). An owner name that isn't a valid username is treated as an unknown owner.
• Tests and docs: test/repo-transfer-web.test.ts covers the move, all four refusals, the 404 for a reader, a cross-origin post, and that the block is hidden from non-admins. docs/features/repo-transfer.md now names the page.

I added nothing to core/transfer.ts.

This pull fixes the failed check by adding the missing "Try:" line to a commit message. The gate rule "say how to try it on the preview" wanted one because the pull changes src/http/server.ts, src/web/pages/search.ts and src/web/pages/settings.ts. No code changed.

I added an empty commit whose message says how to try the change:

Try: open /settings on the preview of this pull, pick a repository and use the Transfer action to move it to another owner.

bun scripts/gate.ts now exits 0 locally and the push went through. I did not re-run tsc or the tests, because only the commit message changed. The forge's check on this push is the real test of the fix.

What the pull does: a repository's settings page moves it to another owner through the transfer action (#10099).

What I left out: any change to behaviour or code in this fix.

How to try it: open /settings on the preview at https://lab--10118--forge-trevato-apps.open-platform.sh and use Transfer on a repository.

I've addressed two of Sentinel's three points and pushed. The 390px look is still missing, because my sandbox has no way to capture it or attach it to the pull.

• Repeated explanation: the Settings block's muted paragraph now has one sentence: "Give the repository to an account or organisation you can create repositories under." The confirm page keeps the detail that the address changes and the old one redirects, so that is said once.
• Test for echoed parameters: the confirm step is now tested with extra query parameters (evil=x, confirm=y) alongside owner. Only owner is echoed, as the single hidden input. The change is in test/repo-transfer-web.test.ts.
• 390px look (still open): whoever can capture looks on the forge needs to take the Settings page at 390px and attach it to the pull.

bun x tsc --noEmit, bun test test/repo-transfer-web.test.ts (7 pass) and bun scripts/design-lint.ts are all green.

Try it: open /<owner>/<repo>/settings on the preview as an admin. Enter an owner under "Move to another owner" and press Move to reach the confirm page.

Left #10099 open: 1 unticked item remain (No sideways scroll at 390px, with a look on the pull; bun scripts/design-lint.ts passes.).