Loom harness names adopt another group's code interpreter
Harness code-interpreter names drop a trailing code_interpreter suffix and leave out the agent id. list_code_interpreters is account-wide and has no group check. A demo agent:write harness named billing_code_interpreter stored the interpreter id of harness billing in group payments, and DELETE with cleanup_aws deleted that id. GET of the payments agent stayed 403. Labbed only on v1.10.3. AWS was stubbed. The demo admin did not read the other group's agent, and code execution as that group's role was not labbed.