soryu, branch makima/task-task-21748e1d-21748e1d

[WIP] Heartbeat checkpoint - 2026-01-31 22:51:47 UTC

2026-01-31T22:51:47+00:00

[WIP] Heartbeat checkpoint - 2026-01-31 22:48:28 UTC

2026-01-31T22:48:28+00:00

[WIP] Heartbeat checkpoint - 2026-01-31 22:47:42 UTC

2026-01-31T22:47:42+00:00

[WIP] Heartbeat checkpoint - 2026-01-31 22:46:47 UTC

2026-01-31T22:46:47+00:00

Fix download for hf TTS model

2026-01-30T02:54:51+00:00

Support both tokenizor.json and vocab.json+merges.txt formats

2026-01-30T02:16:45+00:00

Rename to command mode and update worktree to show committed changes

2026-01-29T17:23:03+00:00

Add autodetection of master for PR creation

2026-01-29T17:23:03+00:00

Fix Red Team UI visibility by adding red_team_enabled to ContractSummary

2026-01-29T17:23:03+00:00

The Red Team toggle was implemented in the frontend but not visible because the backend API's ContractSummary response struct was missing the red_team_enabled field. The frontend relies on this field to: 1. Show the red team badge in the contract list view 2. Show the red team badge and tab in the contract detail view Changes: - Add red_team_enabled field to ContractSummary struct in models.rs - Update list_contracts_for_owner SQL query to include red_team_enabled - Update get_contract_summary_for_owner SQL query to include red_team_enabled - Update all fallback ContractSummary constructions in contracts.rs handler Co-Authored-By: Claude Opus 4.5

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

2026-01-29T17:14:09+00:00

* 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 * 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 --------- Co-authored-by: Claude Opus 4.5