mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

[INFRA-014] Integration with M4.1 coordinator #176

New Issue
Closed
opened 2026-02-01 07:25:46 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-02-01 07:25:46 +00:00
Owner
Copy Link

Summary

Integrate the M4.2 infrastructure with M4.1 Non-AI Coordinator orchestration logic.

Integration Points

From Coordinator to Infrastructure

  • Coordinator dispatches jobs via runner-jobs API
  • Coordinator applies agent profiles (runner/weaver/inspector/herald)
  • Coordinator sets job priority based on issue priority

From Infrastructure to Coordinator

  • Job events inform coordinator of progress
  • Quality gate results trigger coordinator decisions
  • Context usage reported for 50% rule enforcement

Tasks

  • Create integration interface between coordinator and stitcher
  • Map coordinator agent profiles to OpenClaw constraints
  • Forward job events to coordinator for context tracking
  • Integrate quality gate results with coordinator rejection loop
  • Test full flow: issue -> coordinator -> stitcher -> worker -> completion

Files to Create

  • apps/api/src/stitcher/integrations/coordinator.integration.ts

Files to Modify

  • apps/api/src/stitcher/stitcher.service.ts
  • Coordinator module (from M4.1)

Acceptance Criteria

  • Coordinator can dispatch jobs
  • Jobs execute with correct agent profile constraints
  • Events flow back to coordinator
  • Quality gate failures trigger coordinator retry logic

Related

## Summary Integrate the M4.2 infrastructure with M4.1 Non-AI Coordinator orchestration logic. ## Integration Points ### From Coordinator to Infrastructure - Coordinator dispatches jobs via runner-jobs API - Coordinator applies agent profiles (runner/weaver/inspector/herald) - Coordinator sets job priority based on issue priority ### From Infrastructure to Coordinator - Job events inform coordinator of progress - Quality gate results trigger coordinator decisions - Context usage reported for 50% rule enforcement ## Tasks - [ ] Create integration interface between coordinator and stitcher - [ ] Map coordinator agent profiles to OpenClaw constraints - [ ] Forward job events to coordinator for context tracking - [ ] Integrate quality gate results with coordinator rejection loop - [ ] Test full flow: issue -> coordinator -> stitcher -> worker -> completion ## Files to Create - apps/api/src/stitcher/integrations/coordinator.integration.ts ## Files to Modify - apps/api/src/stitcher/stitcher.service.ts - Coordinator module (from M4.1) ## Acceptance Criteria - Coordinator can dispatch jobs - Jobs execute with correct agent profile constraints - Events flow back to coordinator - Quality gate failures trigger coordinator retry logic ## Related - Epic: #162 - Depends on: All M4.2 issues - Integrates with: M4.1 Non-AI Coordinator (#142)
jason.woltje added this to the M4.2-Infrastructure (0.0.4) milestone 2026-02-01 07:25:46 +00:00
jason.woltje added the apiapip0phase-5 labels 2026-02-01 07:25:46 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label api api p0 phase-5
Milestone
No items
No Milestone M4.2-Infrastructure (0.0.4)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#176
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?