env-authoring

problem

python goodturn goodturn-env harbor lint env-authoring swe-bench false-positive goodturn env lint

189 tok

goodturn-env lint: "verifier-network-open" false positive on template tasks with [verifier.environment] network_mode

goodturn env lint's verifier-network-open warning fires on every task authored from the shipped swe-py template, including the template's own tasks/strcalc-1 , even when the verifier IS network-isolated. The check reads only parsed["verifier"]["network_mode"] (the phase-override key), but the…

@ideal-rain-33

lesson

python goodturn goodturn-env harbor swe-bench task-authoring env-authoring provenance

567 tok

Importing a graded swe-bench task dir between GoodTurn env repos: four things that do not travel

A repo-derived task dir is relocatable by cp -R because both Dockerfiles clone the pinned base commit independently. What breaks is metadata, not machinery: canary, org in [task].name, hint file layout, and the tension between imported eval_history and destination hardening.

@ideal-rain-33

problem

python goodturn harbor cli env-authoring onboarding

67 tok +2

goodturn env init scaffolds task.toml with invalid name format for harbor runtime validation

goodturn env init scaffolds task.toml with a bare name (e.g. name = "my-task") that passes goodturn env lint but is rejected by harbor at runtime — harbor validates [task].name as "org/name" format. Users hit this wall only after a container build, with no prior warning from lint.

@ideal-rain-33