gitea, extracted into plugins/gitea — the platform half

Eleventh extraction, and the only one that deleted its UI instead of moving it.
Seventeen files under apps/Gitea/ reimplemented a fraction of an interface
Gitea already has; the plugin renders the real one in an iframe over a
same-origin proxy.

Deleting rather than moving removed a platform change nobody now has to build:
useGiteaLocation read :owner/:name/:tab/:item from five route patterns where a
plugin gets two, so an as-is extraction would have required teaching the plugin
system to declare extra route patterns. Nothing inside an iframe needs a route.

Nothing working was lost. The router had been commented out of hono.ts since
2026-08-13 with api: [], and officer-gitea was running nowhere — the screen
rendered and every request 404'd, like soulseek, jellyfin and invoices before
it.

Gitea also stops being a CORE DOCK ITEM. It was hardcoded in CORE_DOCK_ITEMS,
the only installable feature that was, on the reasoning that it fronts a remote
instance and installs nothing locally. As a plugin its tile arrives from
assets/icon.png like every other — which is also why the icon added to
public/icons/ this morning was reverted rather than kept.

'gitea' stays in the ServiceName union: the connection lives in core
service_connections, and gitea is the reason that table has its "member rows
carry only a token and inherit the owner's URL" shape at all.

registry.test.ts's grantable-permission test named gitea as "the case this was
built for"; a plugin's permissions are registered at install and are never in
that compile-time list, so it now names a core one. catalogue.test.ts
re-anchored to vnc/notify.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/servers/app-store/catalogue.test.ts

@@ -111,7 +111,7 @@ describe('member provisioning is declared for every entry', () => {
     // against an API that does not exist. Transmission was an example until 2026-08-18 and slskd until
     // 2026-08-19, when they became `plugins/transmission/` and `plugins/soulseek/` — hence the list
     // rather than a single id: it must stay non-empty, or this assertion passes by iterating nothing.
-    for (const id of ['vnc', 'notify', 'gitea']) expect(byId(id)!.members).toBe('none');
+    for (const id of ['vnc', 'notify']) expect(byId(id)!.members).toBe('none');
   });
 
   // A test asserting the vault is invite-only lived here until 2026-08-18, when it left to become

src/servers/app-store/catalogue.ts

@@ -196,34 +196,6 @@ export const CATALOGUE: CatalogueEntry[] = [
   // Deleting the entry is REQUIRED, not tidying — see the note where photos used to sit, and the trap in
   // `EXTRACTING-A-PLUGIN.md`. A leftover entry makes the permission permanently `unavailable`, because
   // `permissionAvailability()` derives from `sidecar_installs` and a plugin never gets a row there.
-  {
-    id: 'gitea',
-    ui: { name: 'Gitea', icon: 'GitBranch', color: '#34d399', rootRoute: '/gitea', routes: ['/gitea'] },
-    process: 'officer-gitea',
-    label: 'Gitea',
-    summary: 'Repositories, issues and pull requests from your own Gitea account',
-    // 'none' because there is nothing for the INSTALLER to provision, not because Gitea is single-tenant —
-    // it is the most per-user service here. The owner's connection carries the instance URL; every member
-    // adds their own access token from /gitea and acts only as themselves upstream, with Gitea's own
-    // permissions as the second and real gate. A provisioner could not do that part for them without
-    // holding an admin token and minting tokens on their behalf, which is more authority than this needs.
-    members: 'none',
-    // `existing` only, and there is no compose template. Gitea here is always something the owner already
-    // runs — on this machine, on another, or hosted. Provisioning one would mean owning the migration,
-    // backup and upgrade story for a service that is nobody's side feature.
-    modes: ['existing'],
-    permission: 'gitea',
-    existingFields: [
-      { key: 'url', label: 'Gitea URL', type: 'url', required: true, placeholder: 'https://gitea.example.com' },
-      {
-        key: 'secret',
-        label: 'Your access token',
-        type: 'secret',
-        required: true,
-        help: 'A personal access token from your own Gitea account. Members add their own from /gitea.',
-      },
-    ],
-  },
   // Headscale was here until 2026-08-14. It became a core sidecar, and then on 2026-08-15 it left the
   // repository entirely: it is the `offscale` PLUGIN now, installed from the marketplace, and neither
   // this catalogue nor `CORE_PROCESSES` mentions it. The note below is kept because the FAILURE it