delete api routes with no consumers

from a full audit of all 179 route definitions under src/servers/api, tracing
consumers through useClient, raw fetch, EventSource, the capabilities repo and
the mobile monorepo. only routes with zero consumers anywhere are removed.

  server-settings/applications.ts   whole file — an app install/update registry
                                    with no settings section to drive it
  server-settings/claude-code.ts    whole file — the ai settings screen talks
                                    to chat-providers/* exclusively
  GET  browser/extension-download   superseded by a static asset; BrowserRelay
                                    links at /browser-relay-extension.zip
  GET  integrations/                a stub returning []
  GET  chat-providers/auth          /api-keys says the same thing with more detail
  GET  desktop/vnc-status           and with it the vnc:status command and reply,
                                    which existed only to serve this route.
                                    docs/sidecar-audit-2026-07.md called this
                                    one dead months ago

deliberately KEPT, because "no caller" turned out not to mean "dead":

  POST activity/announce      not orphaned — it is the missing PRODUCER for the
                              detached[] list GET activity/tasks already returns
                              and ActivityScreen already renders. an unbuilt
                              feature, not dead code, and finishing or dropping
                              it is a product decision.
  GET  agents/runs            three days old. part of agent grounds, still being
                              built. "not yet consumed" is not "dead".
  PUT/GET vault/unlock-key    six days old, storage half of a feature whose
                              client half is unwritten. the vault is off limits.
  DELETE integrations/google/connection   caller exists but is deliberately
                              commented out of the tree. dormant on purpose.

vnc-manager's getSession is now orphaned too, but it is sidecar-internal and
was not in scope; noted rather than chased.

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

This commit is contained in:

pastilhas

2026-08-04 03:19:37 +00:00

co-authored by

Claude Opus 5

parent ccd104a28b

commit 36c7b1f3fd

10 changed files with 14 additions and 347 deletions

									
										src/servers/api/server-settings/chat-providers.ts
									
		+2
		-5
	
												View File
												
				@@ -370,11 +370,8 @@ chatProvidersRouter.get('/providers', async (ctx) => {

				  return ctx.json(PROVIDERS);

				});

				chatProvidersRouter.get('/auth', async (ctx) => {

				  const auth = await readAuthJson();

				  const providers = PROVIDERS.filter((p) => auth[p.providerId]?.key?.trim()).map((p) => p.key);

				  return ctx.json({ authenticated: providers.length > 0, providers });

				});

				// GET /auth reported which providers had a key set. No caller — AIHarnessesSection reads /api-keys and

				// /api-keys/health instead, which say the same thing with more detail.

				const maskValue = (value: string) => {

				  if (value.length <= 8) return '***';