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

Build Completion Verification Engine #136

New Issue
Closed
opened 2026-01-30 23:42:41 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-01-30 23:42:41 +00:00
Owner
Copy Link

Implement gate execution engine that runs quality checks programmatically.

Objective: Execute quality gates and return pass/fail results without AI decision-making.

Gate Executors:

  • BuildGate: Run build command, check exit code
  • LintGate: Run linter, count errors/warnings vs thresholds
  • TestGate: Run test suite, check pass rate
  • CoverageGate: Parse coverage report, check thresholds
  • CustomGate: Run arbitrary script, check exit code

Engine API:

  • runGates(workspace, context) -> GateResults
  • GateResults.allPassed() -> boolean
  • GateResults.failures -> Gate[]
  • Each failure includes: gate name, expected, actual, message

Implementation:

  • Pure TypeScript service (no AI)
  • Executes commands via child_process
  • Parses output for metrics
  • Returns deterministic pass/fail

Related: L-015, #134 (orchestrator), #135 (gate config)

Acceptance Criteria:

  • All gate types implemented
  • Gates execute in isolated environment
  • Results are deterministic and parseable
  • Timeout handling for long-running gates
  • Clear failure messages for agent prompts
  • Tests for all gate executors
Implement gate execution engine that runs quality checks programmatically. Objective: Execute quality gates and return pass/fail results without AI decision-making. Gate Executors: - BuildGate: Run build command, check exit code - LintGate: Run linter, count errors/warnings vs thresholds - TestGate: Run test suite, check pass rate - CoverageGate: Parse coverage report, check thresholds - CustomGate: Run arbitrary script, check exit code Engine API: - runGates(workspace, context) -> GateResults - GateResults.allPassed() -> boolean - GateResults.failures -> Gate[] - Each failure includes: gate name, expected, actual, message Implementation: - Pure TypeScript service (no AI) - Executes commands via child_process - Parses output for metrics - Returns deterministic pass/fail Related: L-015, #134 (orchestrator), #135 (gate config) Acceptance Criteria: - All gate types implemented - Gates execute in isolated environment - Results are deterministic and parseable - Timeout handling for long-running gates - Clear failure messages for agent prompts - Tests for all gate executors
jason.woltje added the p0apiapi labels 2026-01-30 23:42:41 +00:00
jason.woltje added this to the M4-LLM (0.0.4) milestone 2026-01-30 23:45:33 +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
Milestone
No items
No Milestone M4-LLM (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#136
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?