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

[COORD-009] Test rejection loop #149

New Issue
Closed
opened 2026-01-31 21:04:35 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-01-31 21:04:35 +00:00
Owner
Copy Link

Objective

Validate quality gates prevent premature completion through simulated rejection scenarios.

Implementation Details

Test the completion state machine from Part 2:

Simulate scenarios:

  • Agent claims done with failing tests
  • Agent claims done with linting errors
  • Agent claims done with low coverage
  • Agent claims done with build errors

Verify that:

  • Rejection occurs for each failure type
  • Forced continuation prompt is generated
  • Agent cannot bypass gates
  • Loop continues until gates pass

Context Estimate

  • Files to modify: 2 (integration test file, test report)
  • Implementation complexity: low (10,000 tokens)
  • Test requirements: high (15,000 tokens)
  • Documentation: medium (3,000 tokens)
  • Total estimated: 40,300 tokens
  • Recommended agent: glm

Difficulty

low

Dependencies

  • Blocked by: #154 (COORD-008)

Acceptance Criteria

  • Test: Failing tests trigger rejection and continuation
  • Test: Linting errors trigger rejection and continuation
  • Test: Low coverage triggers rejection and continuation
  • Test: Build errors trigger rejection and continuation
  • Test: All gates passing allows completion
  • Forced continuation prompt verified for each failure type
  • Tests pass (85% coverage minimum)

Testing Requirements

  • Create mock scenarios for each gate failure
  • Verify rejection behavior
  • Verify continuation prompt injection
  • Test that gates cannot be bypassed
  • Coverage: 85% minimum
## Objective Validate quality gates prevent premature completion through simulated rejection scenarios. ## Implementation Details Test the completion state machine from Part 2: Simulate scenarios: - Agent claims done with failing tests - Agent claims done with linting errors - Agent claims done with low coverage - Agent claims done with build errors Verify that: - Rejection occurs for each failure type - Forced continuation prompt is generated - Agent cannot bypass gates - Loop continues until gates pass ## Context Estimate - Files to modify: 2 (integration test file, test report) - Implementation complexity: low (10,000 tokens) - Test requirements: high (15,000 tokens) - Documentation: medium (3,000 tokens) - **Total estimated: 40,300 tokens** - **Recommended agent: glm** ## Difficulty low ## Dependencies - Blocked by: #154 (COORD-008) ## Acceptance Criteria - [ ] Test: Failing tests trigger rejection and continuation - [ ] Test: Linting errors trigger rejection and continuation - [ ] Test: Low coverage triggers rejection and continuation - [ ] Test: Build errors trigger rejection and continuation - [ ] Test: All gates passing allows completion - [ ] Forced continuation prompt verified for each failure type - [ ] Tests pass (85% coverage minimum) ## Testing Requirements - Create mock scenarios for each gate failure - Verify rejection behavior - Verify continuation prompt injection - Test that gates cannot be bypassed - Coverage: 85% minimum
jason.woltje added the apiapip0phase-3 labels 2026-01-31 21:04:35 +00:00
jason.woltje added this to the M4.1-Coordinator (0.0.4) milestone 2026-01-31 21:10:03 +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-3
Milestone
No items
No Milestone M4.1-Coordinator (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#149
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?