Skip to content

Now

core 2.26.26

  • A work-loop close can now record a specific, real piece of leftover work that is genuinely blocked, instead of losing it. When a defect, an open question, or a decision is blocked on someone else's call, an instrument you don't have, elapsed time, or a dependency, the close captures it as a work-item — with what "done" looks like and why it couldn't be finished now — rather than dropping it or writing a vague note that a later reader can't act on.
  • A work item is checked before it's written, not after. Each one runs through a cold review with no memory of the session that noticed it; an item that isn't real, isn't necessary, or is missing what its shape requires is refused with a specific reason instead of being written silently.
  • A blocked defect may carry its own reproduction command, bounded to a small, read-only set of tools (cat, wc, grep, ls) with no options and no path traversal, so a captured item can point at exactly how to confirm it without granting the record any power to write or execute.

Release notes for core 2.26.26