Skip to content

Now

core 2.26.25

  • Closeout asks five questions instead of seventeen. work-loop's finish checklist now reads as five assertions — acceptance criteria satisfied, verification passed, review passed with residuals surfaced, artifacts consistent, repository state valid — with the existing obligations grouped underneath each one. Nothing that blocked a release before stops blocking it; the list is easier to hold in mind and easier to answer honestly.
  • Knowledge capture leaves the critical path. Routing a session's scratch notes is no longer a condition of declaring done. ## Capture keeps its routing rules and now runs after the loop closes — at session end, an explicit handoff, or before compaction. A capture obligation enforced at the completion boundary turns "is this lesson worth keeping?" into a blocking judgment, and the cheapest way past a blocking judgment is a low-value note. Recorded against RFC-0077 § Errata.

Release notes for core 2.26.25