unbreak the linux light profile: classify officer-gitea

`ecosystem.light.config.cjs` did not mention officer-gitea, so `defineProfile` threw while the file was
being loaded and pm2 could start NOTHING from it — not the app, not the agent, not the terminal. The
profile has been dead on arrival since gitea was added to ecosystem.config.cjs and to the mac profile
but not to this one.

That is the drift check doing its job rather than a flaw in it: the alternative is a light install that
silently starts less than it claims. The cost is that adding a sidecar breaks every profile until each
one classifies it, which is the trade the file already documents.

Included rather than excluded, matching the mac profile's reasoning: this sidecar fronts a REMOTE Gitea
whose URL and token live in `service_connections`, so it installs nothing locally. That is the line
between it and the excluded sidecars, which supervise a local daemon or container.

Both light profiles now load and contain the same six processes.

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

ecosystem.light.config.cjs

@@ -26,6 +26,11 @@ module.exports = defineProfile({
     'officer-agent', // spawns `claude` — chat is dead without it
     'officer-opencode', // the alternative agent
     'officer-pty', // the terminal
+    // Included even though a light host runs no Gitea: this sidecar fronts a REMOTE instance. Its URL
+    // and token live in `service_connections`, set from /gitea, so it needs nothing installed here.
+    // That is what separates it from the sidecars below, which supervise a local daemon or container.
+    // Same reasoning as the mac light profile, which has included it since it was added.
+    'officer-gitea',
   ],
 
   // Excluded by CHOICE rather than by platform limits — every one of these would run on a Linux host.