Wayfinder tasks can bypass the implementation workflow

What happened

A wayfinder:task was allowed to modify production code after execution was enabled in the map Notes.

The work happened inside Wayfinder rather than the implementation flow, so TDD, code review, and explicit seam/design checks were not guaranteed.

Expected

Wayfinder tasks should resolve decisions or prerequisites, not implement production changes.

When tracked implementation is required, Wayfinder should hand off to the implementation flow so the usual TDD, review, and design safeguards are preserved, unless execution was explicitly requested by the human.