You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 4, 2026. It is now read-only.
Repository navigation
Commit d79858c
Browse filesBrowse the repository at this point in the historyBrowse files
fix mcp test generation stability and recovery (#5)
* fix mcp test generation stability and recovery
Made-with: Cursor
* fix ci failures for new cleanup tool
Made-with: Cursor
* fix post-review robustness for test generation flow
Tighten answer_ext normalization and retry semantics, clear stale generated outputs before final writes, and make cleanup/semantic checks more resilient across platforms and generator branch styles.
Made-with: Cursor
* fix cleanup checkpoint safety and polygon answer-ext sanitization
Preserve checkpoint metadata when cleaning tracked generator PIDs, add POSIX PID termination support, and sanitize/escape manifest-derived answer extensions in Polygon XML output.
Made-with: Cursor
Copy file name to clipboardExpand all lines: agents/autocode-workflow.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,8 @@ Always work through this sequence unless the task is explicitly outside problem
25
25
26
26
When the user asks for a later step directly, explain which prerequisite step is missing and complete the missing work first.
27
27
28
-
When running `problem_generate_tests`, enforce test quality: final test data should contain at least half limit-oriented cases (`type=3` extreme + `type=4` tle) when candidate availability allows.
28
+
When running `problem_generate_tests`, enforce test quality: final test data should contain at least half limit-oriented cases (`type=3` extreme + `type=4` tle) when candidate availability allows. Also enforce that generator logic for type=3 and type=4 is semantically different (type=4 should include targeted worst-case patterns, not only max-parameter scaling).
29
+
30
+
For long-running `problem_generate_tests`, warn that new user messages can interrupt MCP execution. If interrupted, prefer resuming with checkpoint (`resume=true`) rather than restarting from scratch.
29
31
30
32
Treat hook feedback as authoritative. If a hook denies a tool call, fix the workflow gap instead of retrying the same call.
"When running long problem_generate_tests tasks, avoid sending new chat messages because that can interrupt MCP calls; if interrupted, resume with checkpoint state (resume=true). "
276
+
"Generator quality gate: ensure type=3 and type=4 branches are semantically different, and type=4 includes targeted worst-case patterns rather than only max parameters. "
275
277
"If a hook blocks a step, complete the missing prerequisite instead of retrying blindly."
0 commit comments