Skip to content

v3.21.5

Choose a tag to compare

@Jaggerxtrm Jaggerxtrm released this 20 Aug 14:40
· 667 commits to master since this release

[3.21.5] - 2026-08-20

Patch focused on observability truthfulness and Pi vendored-tooling parity. sp log default output now filters agent-internal events (turn/tool/model.token_usage) that were drowning the 2-3 real lifecycle rows per job; the corresponding monitor recipes in using-specialists/references/monitoring.md are corrected to read from .forensic_event and to distinguish terminal (job.completed|failed|cancelled) from attention (waiting, process_health.stale_detected, error.*) states — the prior recipe silently matched nothing and coordinators read the silence as "still running". Background specialist dispatch now surfaces launch errors instead of returning a misleading ok envelope. Two Pi extension vendored-fork fixes bring read-line-numbers behavior in line with the Core implementation (EOF model + real-blank-line handling).

Fixed

  • Mirror Core read-line-numbers blank-line fix in vendored fork (unitAI-nx80v) (#265) (d2785cf)
  • Correct vendored read-line-numbers fork to Pi EOF model (unitAI-gajax) (#266) (3760cf4)
  • Surface launch errors in the background envelope (xtrm-5kwk2) (#267) (daba619)
  • Sp log default forensic path emits every agent-internal event (unitAI-mkkjk) (#268) (7a13d63)

Project maintenance

  • V3.21.4 release-path followups (unitAI-ip5jz) (588593d)
  • Stop the boundary-rule test depending on bd + a real bead (1ce1006)
  • Sp log --json envelope shape + correct monitor recipes (unitAI-nhl6x) (#269) (bcdbd30)