feat: Task completion summary/proof/guide/tests

[stavarc]

"SInce we know that vibe coding is know to break existing code It would be nice to also have a summary description on the implementation that was done which led to the task being marked as DONE along with some tests"

Motivation

This will serve as a proof and guide of completion and can be used as future reference to quickly "repair" if something went wrong. This way we can re-validate if a certain task still qualifies as DONE.

Proposed Solution

Maybe include tests that could validate/invalidate the task status

Example Workflow

Provide a clear, concrete example demonstrating the feature:

unit, component or e2e tests should be defined for each completed task that could evaluate if teh task is still in the DONE state

[Crunchyman-ralph]

I like this, and it goes with our roadmap. thanks for the issue

[eyaltoledano]

Agreed. I have this in my notes as a "progress" command -- I'll issue it soon. Thanks!