Fetch from origin before creating worktrees for local repos (#49)

* Add comprehensive Red Team system specification

Defines the adversarial review feature for contracts that monitors work tasks
in real-time to catch quality issues, plan deviations, and standards violations.

Key components specified:
- Contract configuration (red_team_enabled, red_team_prompt)
- Red team task lifecycle and spawning logic
- makima red-team notify CLI command for supervisor alerts
- Task output subscription for real-time monitoring
- Database schema changes (contracts, tasks, notifications table)
- API endpoints for notification and status
- System prompt template for red team behavior
- Security considerations and access control

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

* Task completion checkpoint

* Task completion checkpoint

* Task completion checkpoint

* feat: fetch from origin for local repos before creating worktrees

When a supervisor creates worktrees from a local repository that tracks
a remote origin, it may use stale data. This change ensures that for
local repositories with an origin remote configured, we explicitly
fetch from origin before creating worktrees.

Changes:
- Check if 'origin' remote exists using `git remote get-url origin`
- If origin exists, fetch from it with `git fetch origin`
- Log appropriately whether it's a remote-backed or local-only repository
- Keep the behavior non-fatal (don't fail if fetch fails, just log)
- Keep existing `git fetch --all --prune` as fallback for other remotes

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

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

0 files changed, 0 insertions, 0 deletions