Fix critical port conflict: move portfolio off Gitea's port 3000

Host port 3000 is Gitea (git.soroushasadi.com proxies to :3000). The
portfolio was publishing 3000:3000 AND the deploy had a "Free Port 3000"
step that force-removed every container on :3000 — which evicted the
Gitea container.

- compose: publish 3020:3000 instead of 3000:3000
- deploy: delete the "Free Port 3000" step entirely; compose recreates
  only our own named container and must never touch other stacks

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

.gitea/workflows/deploy.yml

@@ -40,20 +40,13 @@ jobs:
       - name: Build Container
         run: docker compose build
 
-      - name: Free Port 3000
-        run: |
-          # Remove any container publishing :3000 (old Next.js container,
-          # orphans from a previously-named compose project, etc.)
-          OLD=$(docker ps -a --filter publish=3000 -q)
-          if [ -n "$OLD" ]; then
-            echo "Removing containers on :3000 -> $OLD"
-            docker rm -f $OLD || true
-          fi
-          # Belt and suspenders: also remove by our known name.
-          docker rm -f soroushasadi-site 2>/dev/null || true
-
       - name: Deploy
-        run: docker compose up -d --remove-orphans
+        # Compose recreates ONLY our own container (container_name:
+        # soroushasadi-site, project: soroushasadi). It must never touch
+        # other stacks. Do NOT add any step that removes containers by
+        # published port — port 3000 is Gitea and 5xxx/3xxx belong to
+        # other apps on this host.
+        run: docker compose up -d
 
       - name: Wait For Health Check
         run: |