Skip to content

v0.5.15 - taskmaster preflight + per-task test scoping

Choose a tag to compare

View all tags
@tranquocthong tranquocthong released this 20 Jul 18:12
· 34 commits to main since this release
v0.5.15
8003332

Two related fixes found while investigating why a 15-task SD's /sf:phase run was taking very long.

0.5.14 - Task Master model preflight + resilience

  • New taskmaster-model-check command: zero-cost preflight that flags any Task Master role (main/research/fallback) on a keyed provider with no matching API key in env/.env, before the per-task loop can burn time on it. Wired into /sf:phase right after use-tag.
  • update-task --append failures are now non-blocking: surface once, then proceed to trace-link/set_task_status instead of retrying in a loop or halting the phase.
  • wave-plan's ready set is now checked before next_task; file-disjoint task batches can run in parallel instead of strictly one-at-a-time.

0.5.15 - Per-task test scoping

  • The single biggest cost on a multi-task SD: verify-code's tests check ran the FULL test suite on every task close. New --task / --files "a,b" flags scope this to just the files a task touched (java-spring/java-maven derive a --tests/-Dtest= filter automatically; other stacks can configure verify.taskTestCommand). Wired into hybrid-executor's RED check and phase.md's per-task gate. The full suite now runs once, at phase close-out, instead of once per task.

Tests: 117 (110 + 7 new). See CHANGELOG.md for full detail.

Assets 2
Loading