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

[ORCH-104] Monorepo build pipeline for orchestrator #205

New Issue
Closed
opened 2026-02-02 18:58:25 +00:00 by jason.woltje · 1 comment
jason.woltje commented 2026-02-02 18:58:25 +00:00
Owner
Copy Link

Update TurboRepo configuration to include orchestrator in build pipeline.

Acceptance Criteria

  • turbo.json updated with orchestrator tasks
  • Build order: packages/* → coordinator → orchestrator → api → web
  • Root package.json scripts updated (dev:orchestrator, docker:logs)
  • npm run build builds orchestrator
  • npm run dev runs orchestrator in watch mode

Dependencies

  • Blocked by: #ORCH-101

Technical Notes

See ORCHESTRATOR-MONOREPO-SETUP.md Section 3.2 for turbo.json configuration.

Update TurboRepo configuration to include orchestrator in build pipeline. ## Acceptance Criteria - [ ] turbo.json updated with orchestrator tasks - [ ] Build order: packages/* → coordinator → orchestrator → api → web - [ ] Root package.json scripts updated (dev:orchestrator, docker:logs) - [ ] `npm run build` builds orchestrator - [ ] `npm run dev` runs orchestrator in watch mode ## Dependencies - Blocked by: #ORCH-101 ## Technical Notes See `ORCHESTRATOR-MONOREPO-SETUP.md` Section 3.2 for turbo.json configuration.
jason.woltje added this to the M6-AgentOrchestration (0.0.6) milestone 2026-02-02 18:58:25 +00:00
jason.woltje added the orchestrator label 2026-02-02 18:58:25 +00:00
jason.woltje commented 2026-02-02 23:01:39 +00:00
Author
Owner
Copy Link

Duplicate of #239 which was completed. Closing duplicate issue.

Duplicate of #239 which was completed. Closing duplicate issue.
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 orchestrator
Milestone
No items
No Milestone M6-AgentOrchestration (0.0.6)
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#205
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?