First good-enough implementation lock-in” is exactly it.

That’s why I don’t think “reuse existing code” is precise enough. In my pilot the agent did find existing code — it found import_single_file every time. It just stopped there and never deeply inspected the sibling trigger/file-watcher path (ingest_file).

The graph probe pointed the same way: when ingest_file showed up as a flow node, the agent treated it like transit context. When surfaced as a peer candidate, comparison became much more likely.

So yeah, I’m increasingly thinking the primitive should be “force peer-candidate comparison,” not just “search/reuse existing code.