Go repos with a deterministic loop

• go 1.24
• setup and test as the primary repo loop
• Go runtime ownership through toolchains.go

• it turns a repo pattern into something humans, CI, and agents can read the same way
• it makes the next command obvious instead of implied by README drift
• it keeps readiness, setup, and execution explainable in receipts and diagnostics

This example keeps the Go path short: fetch dependencies, run tests, and keep the repo honest with one verification task.

version: 1project:  name: basic-gotoolchains:  go:    version: "1.24"tasks:  setup:    internal: true    command:      exe: go      args:        - mod        - download  test:    command:      exe: go      args:        - test        - ./...agent:  entrypoint: setup  default_task: test  safe_tasks:    - setup    - test  verify_after_changes:    - test