feat: scale scout bot traffic loop and route into main stack

docker-compose.yml

@@ -13,6 +13,8 @@ services:
       - "5432:5432"
     volumes:
       - agent_bounty_pgdata:/var/lib/postgresql/data
+    networks:
+      - agent-bounty-network
     healthcheck:
       test: ["CMD-SHELL", "pg_isready -U agent"]
       interval: 5s
@@ -39,6 +41,37 @@ services:
     # We use a command override to run database push before starting next.js
     command: >
       sh -c "npx prisma@6.4.1 db push --schema=apps/web/prisma/schema.prisma --skip-generate && node apps/web/server.js"
+    networks:
+      - agent-bounty-network
+
+  scout-bot:
+    build:
+      context: .
+      dockerfile: apps/scout-bot/Dockerfile
+    container_name: agent_bounty_scout_bot
+    restart: unless-stopped
+    depends_on:
+      web:
+        condition: service_started
+    environment:
+      - NODE_ENV=production
+      - VIBEWORK_API_URL=http://agent_bounty_web:3000/api
+      - SCOUT_API_KEY=${SCOUT_API_KEY:-dev_scout_key}
+      - SCOUT_AGENT_ID=scout_official_1
+      # Optional: add more discovery repos via env (comma separated "owner/repo"), e.g. openai/swarm,significant-gravitas/autogpt
+      - SCOUT_TARGET_REPOS=${SCOUT_TARGET_REPOS}
+      - SCOUT_ISSUE_LABEL=${SCOUT_ISSUE_LABEL:-good first issue}
+      # Higher frequency for phase-1 bootstrapping; tune this safely after data stabilizes.
+      - SCOUT_CRON_EXPRESSION=${SCOUT_CRON_EXPRESSION:-*/10 * * * *}
+      # GitHub token should be provided in deployment env for real posting.
+      - GITHUB_TOKEN=${GITHUB_TOKEN}
+    networks:
+      - agent-bounty-network
+
+networks:
+  agent-bounty-network:
+    driver: bridge
+    name: agent-bounty-network
 
 volumes:
   agent_bounty_pgdata: