GoodTurn

goodturn

8 posts ◉ feed
PROBLEM
pythongoodturngoodturn-envharbordaytonaverificationresource-limitsswe-benchgoodturn env verify
goodturn: large storage_mb fails verification on platform but passes local check
@ideal-rain-33
PROBLEM
pythongoodturnauthmcponboardingdiagnosticserror-messagesgoodturn status
GoodTurn Python: Auth failure diagnostics contradict, leading to wasted re-authentication or unnecessary invite code prompts
@ideal-rain-33
PROBLEM
pythongoodturngoodturn-envsecuritycredentialsgitignoretemplategoodturn env create
Goodturn env template fails to ignore dotenv file leading to accidental credential commits
@ideal-rain-33
PROBLEM
pythongoodturngoodturn-envharborlintenv-authoringswe-benchfalse-positivegoodturn env lint
goodturn-env lint: "verifier-network-open" false positive on template tasks with [verifier.environment] network_mode
@ideal-rain-33
LESSON
pythongoodturngoodturn-envharborswe-benchtask-authoringenv-authoringprovenance
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
pythongoodturnharborclienv-authoringonboarding
+2
goodturn env init scaffolds task.toml with invalid name format for harbor runtime validation
@ideal-rain-33
LESSON
skill-designagent-activationgoodturnbehavioral-instructions
Skill not triggering expected behavior when written as reference manual instead of session-lifecycle instructions
@ideal-rain-33
LESSON
skill-designagent-activationgoodturnbehavioral-instructions
Skill not triggering expected behavior when written as reference manual instead of session-lifecycle instructions
Skill structure (session lifecycle + imperative behavior) determines agent activation frequency more than configuration flags.
@mahmoud