summaryrefslogtreecommitdiff
path: root/makima
Commit message (Collapse)AuthorAgeFilesLines
* Remove directive mechanismsoryu2026-02-0827-5950/+35
|
* Fix directive evaluation and add to frontendsoryu2026-02-086-57/+282
|
* Fix directive evaluationsoryu2026-02-081-13/+30
|
* Fix directive deletion and stop local only on contractssoryu2026-02-084-235/+264
|
* Fix INT4/INT8 type mismatch in create_directive_chainsoryu2026-02-081-2/+2
|
* Fixes for directive chain initsoryu2026-02-089-106/+278
|
* Fixes for directive chain creationsoryu2026-02-072-7/+158
|
* Check on completion for contractssoryu2026-02-072-1/+143
|
* Fix directive page stylingsoryu2026-02-072-61/+78
|
* Add repo suggestions for directivessoryu2026-02-071-28/+170
|
* Change directive pagesoryu2026-02-072-102/+123
|
* Add directive monitor contractssoryu2026-02-0716-144/+1739
|
* Show directive init on frontendsoryu2026-02-075-29/+209
|
* Add directive init mechanismsoryu2026-02-0715-9/+1185
|
* Add new directive initial implementationsoryu2026-02-0720-17/+2084
|
* Remove directives for reimplementationsoryu2026-02-0739-11241/+336
|
* Fix: Link directives and contractssoryu2026-02-063-7/+114
|
* Fix: Cleanup old chain codesoryu2026-02-0638-4815/+2119
|
* Fix: Directives fixessoryu2026-02-063-111/+348
|
* Fix: Directives APIsoryu2026-02-063-30/+251
|
* Fix: Directive page and remove chain pagesoryu2026-02-068-2131/+3
|
* Fixup: pnpm lockfilesoryu2026-02-061-1257/+1636
|
* Sync CreateChainRequest with backendsoryu2026-02-061-0/+1
| | | | | | | Add repositoryUrl field to frontend CreateChainRequest for backwards compatibility with backend. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Add directive-first chain system redesignsoryu2026-02-0539-4153/+9115
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Redesigns the chain system with a directive-first architecture where Directive is the top-level entity (the "why/what") and Chains are generated execution plans (the "how") that can be dynamically modified. Backend: - Add database migration for directive system tables - Add Directive, DirectiveChain, ChainStep, DirectiveEvent models - Add DirectiveVerifier and DirectiveApproval models - Add orchestration module with engine, planner, and verifier - Add comprehensive API handlers for directives - Add daemon CLI commands for directive management - Add directive skill documentation - Integrate contract completion with directive engine - Add SSE endpoint for real-time directive events Frontend: - Add directives route with split-view layout - Add 6-tab detail view (Overview, Chain, Events, Evaluations, Approvals, Verifiers) - Add React Flow DAG visualization for chain steps - Add SSE subscription hook for real-time event updates - Add useDirectives and useDirectiveEventSubscription hooks - Add directive types and API functions Fixes: - Fix test failures in ws/protocol, task_output, completion_gate, patch - Fix word boundary matching in looks_like_task() - Fix parse_last() to find actual last completion gate - Fix create_export_patch when merge-base equals HEAD - Clean up clippy warnings in new code Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Add repository selection to chain creation modalsoryu2026-02-053-10/+265
| | | | | | | | | | | | | | - Update CreateChainModal to include repository input fields - Add repository suggestions from history using getRepositorySuggestions - Support both remote (URL) and local (path) repositories - First repository added becomes primary automatically - Pass repositories to CreateChainRequest Also includes backend changes: - Copy chain repositories to contracts when created from definitions - Add created_at field to ChainContractDetail Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Fixup: SQL typesoryu2026-02-051-0/+11
|
* Fixup: overlapping migration timestampssoryu2026-02-051-0/+0
|
* Add makima directivessoryu2026-02-0512-18/+3579
|
* Add multi-repository support for chainssoryu2026-02-059-61/+1030
| | | | | | | | | | | | | | | | | | | | | | Chains can now have multiple repositories attached, with one marked as primary. Repositories are used by contracts created from chain definitions. Backend changes: - Add chain_repositories table migration - Add ChainRepository model with CRUD operations - Add API endpoints for listing, adding, deleting repositories - Add endpoint to set a repository as primary - Update Chain and ChainEditorData models to use repositories - Update chain parser to support repositories in YAML format - Remove deprecated repository_url/local_path from Chain Frontend changes: - Add ChainRepository interface and API functions - Add repository section to ChainEditor showing attached repos - Add modal for adding new repositories (remote or local) - Support setting primary repository and removing repositories Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Replace custom DAG editor with React Flow librarysoryu2026-02-053-1158/+707
| | | | | | | | | - Install @xyflow/react for smooth node-based UI - Create custom DefinitionNode and ContractNode components - Use React Flow's built-in drag-and-drop, edge drawing, pan/zoom - Removes laggy custom implementation Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Add makima skillssoryu2026-02-047-0/+557
|
* Improve chain DAG editor UXsoryu2026-02-042-9/+114
| | | | | | | | | | - Fix drag lag by disabling CSS transitions during drag - Add canvas right-click context menu to create definitions at position - Auto-find free grid space for new definitions to avoid overlap - Fix startChain API to send empty JSON body (backend expects JSON) - Add PlusIcon for context menu Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Add interactive DAG editor for chain definitionssoryu2026-02-041-11/+408
| | | | | | | | | | - Add drag-and-drop to reposition definition nodes - Add edge drawing from connector dot to create dependencies - Add right-click context menu with delete and dependency management - Show visual hints in footer for available interactions - Update node positions and dependencies via API on change Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Remove chain supervisor capabilitysoryu2026-02-048-367/+18
| | | | | | | | | | | | Chains no longer spawn a supervisor task. Checkpoint contracts will be automatically run as part of the DAG execution when dependencies complete. - Remove supervisor task creation from start_chain handler - Remove chain supervisor CLI commands - Remove supervisor_task_id from StartChainResponse - Remove withSupervisor option from frontend Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Fix buildsoryu2026-02-041-1/+2
|
* Fix default chain statussoryu2026-02-041-0/+12
|
* Add chain checkpoint contractssoryu2026-02-0412-51/+1088
|
* Allow chain creation via web interfacesoryu2026-02-038-105/+1886
|
* Add 'Discuss Contract' feature to listen page (#57)soryu2026-02-0312-3/+2167
|
* Fix: FE type errorsoryu2026-02-033-9/+8
|
* Reorganize makima navbarsoryu2026-02-033-114/+97
|
* Add makima chain mechanismsoryu2026-02-0326-12/+4627
|
* Fix downloading too many modelssoryu2026-02-021-3/+21
|
* Release in makima reposoryu2026-02-0210-2545/+11
| | | | Also remove all other TTS models
* Make makima more opinionated and structuredsoryu2026-02-0234-3017/+297
|
* Use chatterbox TTSsoryu2026-02-016-52/+35
|
* Merge pull request #55 from soryu-co/makima/contract-management-phase3soryu2026-02-019-27/+2136
|\ | | | | feat: Implement Phase 3 - Supervisor Resilience and State Management
| * feat: Implement Phase 3.5 - Supervisor Status APImakima/contract-management-phase3soryu2026-02-014-0/+557
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | - Add SupervisorStatusResponse for status endpoint - Add SupervisorHeartbeatEntry and history response types - Add SupervisorSyncResponse for sync endpoint - Add HeartbeatHistoryQuery for pagination - Resolve merge conflict keeping both API types and unit tests Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
| | * feat: Add Supervisor Status API endpoints (Phase 3 Task 3.5)soryu2026-02-014-0/+557
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Implement REST API endpoints for querying supervisor status: - GET /api/v1/contracts/{id}/supervisor/status Returns current supervisor status including task_id, state, phase, current_activity, progress, last_heartbeat, and pending_task_ids - GET /api/v1/contracts/{id}/supervisor/heartbeats?limit=10 Returns paginated supervisor activity history from history_events - POST /api/v1/contracts/{id}/supervisor/sync Triggers a sync to refresh the supervisor's last_activity timestamp New types added: - SupervisorStatusResponse - Status endpoint response - SupervisorHeartbeatEntry - Individual heartbeat history entry - SupervisorHeartbeatHistoryResponse - Heartbeat history with pagination - SupervisorSyncResponse - Sync endpoint response - HeartbeatHistoryQuery - Query params for heartbeats endpoint Repository helpers: - get_supervisor_status() - Combined info from supervisor_states and tasks - get_supervisor_activity_history() - Activity timeline from history_events - count_supervisor_activity_history() - Total count for pagination - sync_supervisor_state() - Refresh last_activity timestamp Error handling: - 404 for contract not found (CONTRACT_NOT_FOUND) - 404 for no supervisor (SUPERVISOR_NOT_FOUND) - Proper fallback when supervisor_state record doesn't exist but task does Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
| * | feat: Implement Phase 3 Tasks 3.3 and 3.4 - Supervisor State Persistence and ↵soryu2026-02-016-25/+1057
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Restoration Task 3.3: Supervisor State Persistence - Add migration 20260201000001_enhanced_supervisor_state.sql with new columns: - state (supervisor state enum) - current_activity (description) - progress (0-100) - error_message (for failed states) - spawned_task_ids (tasks created by supervisor) - pending_questions (questions awaiting user response) - restoration_count, last_restored_at, restoration_source (restoration tracking) - Update SupervisorState model with new fields - Add PendingQuestion struct for tracking unanswered questions - Add SupervisorRestorationContext for returning restoration info - Add StateValidationResult and StateRecoveryAction for state validation State persistence functions in repository.rs: - update_supervisor_detailed_state() - Update state, activity, progress - add_supervisor_spawned_task() - Track spawned tasks - add_supervisor_pending_question() - Track pending questions - remove_supervisor_pending_question() - Clear answered questions - save_supervisor_state_full() - Full state save (UPSERT) - mark_supervisor_restored() - Increment restoration count - get_supervisors_with_pending_questions() - Find supervisors with pending questions - get_supervisor_state_for_restoration() - Load state for restoration - validate_spawned_tasks() - Validate task consistency - update_supervisor_phase() - Update on phase change - update_supervisor_heartbeat_state() - Lightweight heartbeat update State save points: - On task spawn (save_state_on_task_spawn) - On question asked (save_state_on_question_asked) - On question answered (clear_pending_question) - On phase change (save_state_on_phase_change) - On heartbeat (update_supervisor_heartbeat_state) Task 3.4: Supervisor Restoration Protocol - Add restoration detection when supervisor starts with existing state - Implement validate_supervisor_state() for state consistency checks - Implement restore_supervisor() with validation and context generation - Add redeliver_pending_questions() for re-delivering questions after crash - Add generate_restoration_context_message() for Claude context injection - Update resume_supervisor endpoint to return RestorationInfo - Re-deliver pending questions when supervisor resumes Restoration flow: 1. Daemon restarts or task reassigned 2. Load supervisor state from supervisor_states 3. If NOT FOUND: Start fresh, log warning 4. If FOUND: Validate state consistency 5. If INVALID: Start from last checkpoint 6. If VALID: Restore conversation history 7. Check for pending questions - re-deliver to user 8. Check for waiting tasks - resume waiting state 9. Send restoration context to Claude 10. Resume execution from last state Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
generated by cgit v1.2.3 (git 2.39.1) at 2026-05-21 16:38:23 +0000