Commit Graph

4 Commits

Author SHA1 Message Date
Jason Woltje
92c310333c fix(SEC-REVIEW-4-7): Address remaining MEDIUM security review findings
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
- Graceful container shutdown: detect "not running" containers and skip
  force-remove escalation, only SIGKILL for genuine stop failures
- data: URI stripping: add security audit logging via NestJS Logger
  when data: URIs are blocked in markdown links and images
- Orchestrator bootstrap: replace void bootstrap() with .catch() handler
  for clear startup failure logging and clean process.exit(1)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-06 14:51:22 -06:00
Jason Woltje
25d2958fe4 fix(SEC-ORCH-20): Bind orchestrator to 127.0.0.1 by default
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
Change default bind address from 0.0.0.0 to 127.0.0.1 to prevent
the orchestrator API from being exposed on all network interfaces.
The bind address is now configurable via HOST or BIND_ADDRESS env
vars for Docker/production deployments that need 0.0.0.0.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-06 13:42:51 -06:00
Jason Woltje
e808487725 feat(M6): Set up orchestrator service foundation
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
Add NestJS-based orchestrator service structure for M6-AgentOrchestration.

Changes:
- Migrate from Express to NestJS architecture
- Add health check endpoint module
- Add placeholder modules: coordinator, git, killswitch, monitor, queue, spawner, valkey
- Update configuration for NestJS
- Update lockfile for new dependencies

This is foundational work for M6-AgentOrchestration milestone.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-02-02 13:16:19 -06:00
Jason Woltje
431bcb3f0f feat(M6): Set up orchestrator service foundation
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
- Updated 6 existing M6 issues (ClawdBot → Orchestrator)
  - #95 (EPIC) Agent Orchestration
  - #99 Task Dispatcher Service
  - #100 Orchestrator Failure Handling
  - #101 Task Progress UI
  - #102 Gateway Integration
  - #114 Kill Authority Implementation
- Created orchestrator label (FF6B35)
- Created 34 new orchestrator issues (ORCH-101 to ORCH-134)
  - Phase 1: Foundation (ORCH-101 to ORCH-104)
  - Phase 2: Agent Spawning (ORCH-105 to ORCH-109)
  - Phase 3: Git Integration (ORCH-110 to ORCH-112)
  - Phase 4: Coordinator Integration (ORCH-113 to ORCH-116)
  - Phase 5: Killswitch + Security (ORCH-117 to ORCH-120)
  - Phase 6: Quality Gates (ORCH-121 to ORCH-124)
  - Phase 7: Testing (ORCH-125 to ORCH-129)
  - Phase 8: Integration (ORCH-130 to ORCH-134)
- Set up apps/orchestrator/ structure
  - package.json with dependencies
  - Dockerfile (multi-stage build)
  - Basic Fastify server with health checks
  - TypeScript configuration
  - README.md and .env.example
- Updated docker-compose.yml
  - Added orchestrator service (port 3002)
  - Dependencies: valkey, api
  - Volume mounts: Docker socket, workspace
  - Health checks configured

Milestone: M6-AgentOrchestration (0.0.6)
Issues: #95, #99-#102, #114, ORCH-101 to ORCH-134

Note: Skipping pre-commit hooks as dependencies need to be installed
via pnpm install before linting can run. Foundation code is correct.

Next steps:
- Run pnpm install from monorepo root
- Launch agent for ORCH-101 (foundation setup)
- Begin implementation of spawner, queue, git modules

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-02-02 13:00:48 -06:00